Repository navigation
[PR] release v0.1.210 - #5373
Merged
Merged
Conversation
This was referenced Oct 31, 2026
ranxianglei
pushed a commit
that referenced
this pull request
Nov 11, 2026
A fresh overflow-only session (resume-miss sub-session, no usage history) could never publish the calibration ring while every forward kept overflowing: publication needs >=2 agreeing samples on one origin+model slot that any foreign settle clobbers, and the armed prefold comparator could not fit-exit under a clamped arm. Local judgments therefore stayed raw-estimate calibre forever and each forward re-400'd — a permanent loop (incident 2026-10-31, dsh lane). - armOverflowShrink retains clamp(stated/local-est, [0.25, 4]) per origin+model as stats.overflowBias (persisted, validated on restore); a ratio outside the band flags the record 'mismatched' (the stated count describes payload bili does not hold, #3450 shape) and such a record does not steer. - new util.effectiveCalibration picks the factor allowed to steer THIS route: ring k-hat when applicable to the decision origin, else the un-mismatched bias, else absent; all application sites (trigger, preflight mass/target, relay overhead, output clamp x3 lanes) now use it. - the armed preflight comparator exits on the calibrated round text when a factor applies (folds until est*k <= budget instead of burning an unsatisfiable floor comparison); legacy behavior when no factor applies. - ingest/settle/arm now log accept/reject reasons (the learning path was silent before, which made the incident undiagnosable from production logs). - the post-fold summary line quotes savings from its own endpoints instead of the floor-clamped meter ('~0 tokens saved (913329 -> 875788)' can no longer happen); the meter field itself is unchanged (consumed by the #3444 backoff gate). Tests: tests/issue5373-overflow-bias.test.ts (unit gates for effectiveCalibration/calibrationOriginApplies incl. the mismatch guard; e2e mechanism + regression through DeepSeek-shaped overflows with a billing mock).
ranxianglei
pushed a commit
that referenced
this pull request
Nov 11, 2026
A fresh overflow-only session (resume-miss sub-session, no usage history) could never publish the calibration ring while every forward kept overflowing: publication needs >=2 agreeing samples on one origin+model slot that any foreign settle clobbers, and the armed prefold comparator could not fit-exit under a clamped arm. Local judgments therefore stayed raw-estimate calibre forever and each forward re-400'd — a permanent loop (incident 2026-10-31, dsh lane). - armOverflowShrink retains clamp(stated/local-est, [0.25, 4]) per origin+model as stats.overflowBias (persisted, validated on restore); a ratio outside the band flags the record 'mismatched' (the stated count describes payload bili does not hold, #3450 shape) and such a record does not steer. - new util.effectiveCalibration picks the factor allowed to steer THIS route: ring k-hat when applicable to the decision origin, else the un-mismatched bias, else absent; all application sites (trigger, preflight mass/target, relay overhead, output clamp x3 lanes) now use it. - the armed preflight comparator exits on the calibrated round text when a factor applies (folds until est*k <= budget instead of burning an unsatisfiable floor comparison); legacy behavior when no factor applies. - ingest/settle/arm now log accept/reject reasons (the learning path was silent before, which made the incident undiagnosable from production logs). - the post-fold summary line quotes savings from its own endpoints instead of the floor-clamped meter ('~0 tokens saved (913329 -> 875788)' can no longer happen); the meter field itself is unchanged (consumed by the #3444 backoff gate). Tests: tests/issue5373-overflow-bias.test.ts (unit gates for effectiveCalibration/calibrationOriginApplies incl. the mismatch guard; e2e mechanism + regression through DeepSeek-shaped overflows with a billing mock).
ranxianglei
pushed a commit
that referenced
this pull request
Nov 11, 2026
A fresh overflow-only session (resume-miss sub-session, no usage history) could never publish the calibration ring while every forward kept overflowing: publication needs >=2 agreeing samples on one origin+model slot that any foreign settle clobbers, and the armed prefold comparator could not fit-exit under a clamped arm. Local judgments therefore stayed raw-estimate calibre forever and each forward re-400'd — a permanent loop (incident 2026-10-31, dsh lane). - armOverflowShrink retains clamp(stated/local-est, [0.25, 4]) per origin+model as stats.overflowBias (persisted, validated on restore); a ratio outside the band flags the record 'mismatched' (the stated count describes payload bili does not hold, #3450 shape) and such a record does not steer. - new util.effectiveCalibration picks the factor allowed to steer THIS route: ring k-hat when applicable to the decision origin, else the un-mismatched bias, else absent; all application sites (trigger, preflight mass/target, relay overhead, output clamp x3 lanes) now use it. - the armed preflight comparator exits on the calibrated round text when a factor applies (folds until est*k <= budget instead of burning an unsatisfiable floor comparison); legacy behavior when no factor applies. - ingest/settle/arm now log accept/reject reasons (the learning path was silent before, which made the incident undiagnosable from production logs). - the post-fold summary line quotes savings from its own endpoints instead of the floor-clamped meter ('~0 tokens saved (913329 -> 875788)' can no longer happen); the meter field itself is unchanged (consumed by the #3444 backoff gate). Tests: tests/issue5373-overflow-bias.test.ts (unit gates for effectiveCalibration/calibrationOriginApplies incl. the mismatch guard; e2e mechanism + regression through DeepSeek-shaped overflows with a billing mock).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.
Changes since v0.1.209
compress.modelContextLimit(1,150,000) andproviders.<url>.models.deepseek-flash.context(1,300,000) yield inconsist |compress.modelContextLimit（1,150,000）和providers.<url>.models.deepseek-flash.context（1,300,000）两判定不一致 #5191)model_catalog_jsoninstalls still fall back to the 272K window — #2600 fix only reads models_cache.json #5243 export never consumed; master self-red on unused-exports)unresolvable(502) until process restart #5221)model_catalog_jsoninstalls still fall back to the 272K window — #2600 fix only reads models_cache.json #5243)rejected- ~550 false warn lines a day #5161)includeRetired. | 导出的会话少了回滚掉的历史消息:export 读取没带 includeRetired #4664 union)Open objectivesis lost → model misidentifies | [Design][dsh] 压缩摘要正文对后续轮次不可见 →Open objectives丢失 → 模型误判当前目标重答历史问题 #4154)