You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Changeset: integer provider budgets for summarizer calls #18
A changeset that ships the integer-budget fix as a patch, written for a reader who has not seen the report: what a user loses today (a quarter of stored memory mechanically clipped on an affected route), what changed, and what stays the same (no config, no migration, no metric schema change). It rides the existing release PR rather than opening a new one.
The repo's release policy requires a changeset for user-visible change, and this fix is invisible until it is named, since the symptom is degraded recall rather than an error a user can see.
Acceptance criteria
One changeset file exists for the affected package or packages, at patch level
The entry describes the user-visible effect and the fix in the repo's prose style, with no em dashes
The entry states that no config, migration or metric schema change is required
The existing release PR picks the entry up without a new release PR being opened
vp check passes
Blocked by
The seam ticket and the pass-level regression ticket in this set, so the entry describes shipped behavior.
No duplicates. Searched changeset, integer, budget, summarizer, patch, release, seam, and regression. Only matches are the parent #15 and siblings #16 (seam coercion) and #17 (pass level regression) in the same set. This issue is the changeset child of #15, blocked by #16 and #17.
Existing entries such as .changeset/mechanical-noisy-tier.md and .changeset/recall-search-upgrades.md show the house shape: frontmatter listing affected packages, then plain prose with no em dashes.
Write the body for a reader who has not seen Summarizer requests carry fractional max_tokens, so strict providers reject every call and memory falls to the truncate #15: today a quarter of stored memory on strict provider routes is mechanically clipped because fractional max_tokens values are rejected and the ladder falls to the truncate; after the fix every summarizer request carries an integer budget so calls are accepted and stored as summaries. State explicitly that no config, migration, or metric schema change is required.
Keep prose in repo style: no em dashes, name the agent Pi only if mentioned, match the terse factual tone of current entries.
Run vp check (acceptance gate for this issue). Do not open a new release PR; verify the existing version packages PR picks the entry up.
Committed in 0c70748 as .changeset/whole-token-budgets.md: patch on lossless-core, pi-lossless and opencode-lossless. It names no config key, migration or metric row change. It rides release PR #13 into 0.1.3.
Activity
pullfrog commentedon Nov 6, 2026
No duplicates. Searched
changeset,integer,budget,summarizer,patch,release,seam, andregression. Only matches are the parent #15 and siblings #16 (seam coercion) and #17 (pass level regression) in the same set. This issue is the changeset child of #15, blocked by #16 and #17.Related context:
packages/core/src/llm.ts:435inrequestOf(round to nearest, clamp to at least 1, coerce non-finite, keepREASONING_HEADROOMplacement). Pass-level regression: odd chunk budget never reaches a provider as a fraction #17 owns the pass level regression over leaf, tiled chunk, condensed, and heal..changeset/mechanical-noisy-tier.mdand.changeset/recall-search-upgrades.mdshow the house shape: frontmatter listing affected packages, then plain prose with no em dashes.Plan:
.changeset/integer-provider-budgets.mdwith patch frontmatter forlossless-core,pi-lossless, andopencode-lossless(confirm names inpackages/*/package.json; prior user visible engine fixes list all three).max_tokensvalues are rejected and the ladder falls to the truncate; after the fix every summarizer request carries an integer budget so calls are accepted and stored as summaries. State explicitly that no config, migration, or metric schema change is required.vp check(acceptance gate for this issue). Do not open a new release PR; verify the existing version packages PR picks the entry up.muse-spark-1.3-contributor| 𝕏SutuSebastian commentedon Nov 6, 2026
Committed in 0c70748 as .changeset/whole-token-budgets.md: patch on lossless-core, pi-lossless and opencode-lossless. It names no config key, migration or metric row change. It rides release PR #13 into 0.1.3.