Repository navigation
[PR] fix(preflight): converge view-vs-rebuild fit judgment at the window edge (#5974) - #5983
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8769-pr.5983.1152e13This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5983.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重 (dedup): not a duplicate. Checked all open [PR] rows on the mirror plus GitHub preflight/reconstruction searches — no other open PR targets view-vs-rebuild fit convergence. Same-symptom relatives with DIFFERENT mechanisms (linked, not merged): #5899 (overflow-arm evidence-floor disarm + anthropic-lane egress clamp; disjoint files), #4294/#4938/#4771 (opposite direction — preventing over-folding when already fitting). 标签: bug + dsh + scope/kernel + p1 — defect fix in the compression engine core, dsh evidence lane per source issue #5974, p1 because window-edge sessions become unusable. The upstream PR already carries Review scope. Full diff read (3 files, +425/−51), every downstream outcome arm traced, targeted suites run locally, CI checked on head Mechanism (as implemented). After pass 1 folds and exits early-fit with ranges left behind, Regression audit (existing behaviors touched, item by item):
Test quality. Both directions present per #3617; assertions sharp except one flaw: case 3's second assertion was tautological (mathematically guaranteed by the preceding Local verification. Targeted runs: new file + #1841 (futility) + #1933 (calibration) + #4185 (forward arms) + #3918 (progress verdict) + #2952 (tier recovery) + #4079 (egress fuse) = 33/33 pass; typecheck clean. Full suite rides CI. CI (head Behavior change disclosure (old → new). NEW bounded capability: after an early-fit exit, one corrective preflight pass can run when the fresh rebuild measures over the window by ≥ max(10K tok, 2% of window). Previously such a turn forwarded once for upstream arbitration (#1839 arm) regardless of how far over the rebuild was — the ~5k-tokens/round crawl. Outcome contracts (#1839 arm, #3146/#4185 gate, egress fuse) all keep their existing behavior. No config surface change: 结构化八问(中文)
判定:review 通过,无阻塞项。代码与行为均符合预期条款②;CI 在旧头 |
|
冲突 |
… view and rebuild diverge (#5974) blind processTurn view while the outbound reconstruction measured over the window (fold-reconcile switch-pass id churn re-enters unfolded mass the two pipelines disagree about) — every turn under-folded by exactly the divergence, the ~5k tokens/round crawl in the issue title. When a fresh full-pipeline rebuild measures over the window by at least max(10K tok, 2% of window), run ONE bounded corrective second pass seeded with the measured divergence (viewDeltaCorrection): every fit judgment in that pass — exit bar, futility deficit, relax triggers, tier-distillation funnel, final fitsWindow — runs on the corrected scale. Absent/zero correction stays byte-identical to the legacy walk; when no corrective fold happens the probe rebuild is reused as the final rebuild (no extra prepare). The #1839 forward-once arm, the #3146/#4185 post-compress gate and the relay egress fuse keep their contracts unchanged.
76d0de1 to
0372399
Compare
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复——本任务是既有 PR 的冲突修复车道,无平行立项;但发现一次并发同款 rebase(见下)。 结论先行:冲突已解决并验证通过,本次未再 push——远程分支上已存在一个与我的解法逐字节相同的 rebase(并发运行先推),按 push 纪律不抢分支、不覆盖正在跑的 CI。 本轮做了什么:
实时状态(镜像缓存,05:45Z 抓取,非记忆):head 结构化八问(中文)
判定:冲突解决完成且经独立验证(类型检查 + 定向测试 + 树同构比对),CI 在 |
[bot] 🏷 状态补充(实时核对,不重复前两条已说过的修复细节):
|
[ework] CI fix verified green ✓ |
…e too The pre-walk #1841 gate measures its deficit as payloadEstimate + viewDeltaCorrection - limit, but the mid-walk bail kept the uncorrected payloadEstimate - limit while its comment claimed parity with the pre-walk gate. In a corrective pass (non-zero viewDeltaCorrection) the bail therefore understated the gap and could burn summarization calls on ranges that cannot close the true window gap. Pass 1 (correction 0) is byte-identical; pass 2 now matches the declared invariant that every fit judgment in that pass runs on the corrected scale.
ranxianglei
left a comment
There was a problem hiding this comment.
(ai: vllm-qwen/qwen3.8-27b)
Verdict: APPROVE — independent end-to-end review of head 0372399e00, rebased onto master 5c3c2688f8 (= current master tip, no base drift). The fix does what source issue #5974 expectation clause ② asks: fit judgment is forced through the post-reconstruction single source of truth. One non-blocking finding was fixed on the spot (below). No kernel/ change, no kernel-change declaration → outside the human-only tier.
Direction (issue audit). #5974: at the window edge the preflight walk judges fit on the blind client view while egress is metered on the rebuilt body — two pipelines, systematic positive delta, ~5k tokens/round crawl. The PR implements clause ② as a bounded probe → at most one corrective pass, without touching either pipeline's own accounting. It fixes the judgment at the decision point — not by filtering payloads or fudging meters. Correct layer.
Mechanism verified (independent re-read at src/server.ts:4296–4335 / 4355–4400 and every preflight.ts correction site):
- Probe fires only when
compressedRanges>0 && !unknownBaseline && failure===undefined && rangesRemaining>0— pass 1 exited early-fit with live foldable mass left (rangesRemaining= viable foldable ranges at walk end, src/preflight.ts:2312). Unknown-baseline sessions (#553 upper-bound regime) stay fully excluded. - Probe formula ≡ final-gate formula, byte-identical structure (
estimateCoreMessages(msgs)+overheadEstimate→applyEstimateCalibration(…, kFactor, kOrigin, currentOrigin) + imageTokens) — the probe predicts exactly what the measured gate computes. Inner gate adds a noise floordivergence >= max(10_000, round(limit*0.02)): estimator jitter cannot trigger a corrective pass. - Exactly ONE corrective pass;
viewDeltaCorrectionclamped ≥ 0; every fit site inside the pass runs on the corrected scale (textTarget init + both relax resets, tier-distill funnel/fit-break/cap/recovered/overBy, pre-walk futility deficit, both relax triggers, futility-bail escape, finalfitsWindow).result.payloadEstimateitself stays the honest raw blind-view measure — downstream arms read an un-inflated number. - Egress still goes through the normal rebuild + measured gate (
rebuiltCalibrated < limitfor known-baseline sessions, src/server.ts:4395): the corrective pass works by folding MORE until the reconstruction actually fits — the gate itself is never loosened. - Client hold spans both passes (probe + corrective sit inside the existing try/finally hold, src/server.ts:4298–4336) — one continuous "compressing", no new deadline exposure.
- Stats accounting balances in all four branches: every prepare entry does
++session.stats.requests(src/server/prepare-openai.ts:80, prepare-responses.ts:71/744, prepare-google.ts:88, prepare-anthropic.ts:79); the probe decrements immediately (src/server.ts:4303), a fresh rebuild decrements at its own site (src/server.ts:4362), probe-reuse adds zero. Net +1 per client request, identical to legacy. The common case (folded, no divergence over the noise floor) adds ZERO extra prepares — the probe replaces the rebuild the legacy path always did after a folding pass.
Regression audit (existing behaviors touched, item by item):
- Legacy zero-correction walk — byte-identical (every site reduces to the old expression at correction=0); pinned field-for-field by test case 4.
- #1839 forward-once arm (src/server.ts:4505) — condition byte-unchanged; the corrective pass only changes how much folds before the arm evaluates, and its
payloadEstimateoperand is ≤ pass-1's — strictly less-over views reach the arm. Safe direction. - #3146/#4185 post-compress recheck gate + measured doom tiers — untouched; the
lastInputTokenswrite still happens before the arms evaluate in both old and new code, so the #4185noUpstreamEvidencepopulation is unchanged. - Relay egress fuse (#5932 measured tiers, relay.ts) — not touched.
- Two-tier limit doctrine (#3450/#3738) and growth mode — unchanged; the probe triggers against the same server-side wall the final gate uses, and only when the rebuild measures ≥ that wall — no lean-target over-folding.
lastInputTokensafter a corrective fold — retains the PROBE measurement (max-only bump) instead of the final rebuild size; intended conservative direction, self-corrects at the next upstream usage report. Disclosed below.
Tests. New suite tests/issue5974-preflight-view-divergence.test.ts (5 cases): legacy baseline / positive corrected-fit (strictly more folds than uncorrected) / negative exhaustion (failure-kind pin ∈ {undefined, "exhausted"}) / zero-correction field-for-field identity / full-server common path asserting EXACTLY ONE forward. Both directions present per #3617; assertions have teeth (fixture self-checks overflow; the full-server case distinguishes summary calls from forwards by their task prefix). Local: 41/41 across the nine preflight-related suites + typecheck clean, at the original head AND after my fix commit. Full-suite verdict rides CI (green at 0372399e00; re-running at 691ab4a72f).
Finding fixed on the spot (non-blocking). The mid-walk #1841 futility bail (src/preflight.ts:2793) computed its deficit as payloadEstimate - limit while its comment claimed parity with the pre-walk gate — which this PR had moved to the corrected scale (payloadEstimate + viewDeltaCorrection - limit, src/preflight.ts:2353). In a corrective pass the bail therefore understated the gap and could burn summarization calls on ranges that cannot close the true gap. Safe direction (availability preserved, final fitsWindow unaffected), but it broke the PR's own stated invariant that every fit judgment in the corrective pass runs on the corrected scale. Fix: one line onto the corrected scale + marker comment; pass 1 (correction=0) byte-identical; 41/41 + typecheck green after the fix.
已顺手修:mid-walk futility bail 的 deficit 未走修正尺度(与其注释声称的 pre-walk gate parity 不一致,纠正 pass 里会低估缺口多烧 summary 调用)→ 已对齐修正尺度,pass-1 字节不变 + commit 691ab4a
Behavior change disclosure (old → new):
- NEW bounded capability: after an early-fit exit with live foldable mass left, one throwaway probe rebuild plus at most one corrective pass may run when the probe measures ≥ window AND divergence ≥ max(10k tok, 2%×window). Old: such turns forwarded once for upstream arbitration regardless of how far over the rebuild was — the ~5k/round crawl. Bounded: one pass, gated, unknown-baseline excluded.
session.stats.lastInputTokens: old = the single post-pass rebuild size, written once; new = max(old, probe measurement) written before the corrective pass — when the corrective pass folds further, the probe measurement (slightly larger than what ships) is retained. Conservative direction (earlier compression trigger, leaner context); self-corrects at the next upstream usage report.- No config surface change:
viewDeltaCorrectionis an internalPreflightDepsfield set only by the corrective orchestration — no new config key, env var, or CLI flag.
结构化八问(中文)
- 是什么问题:窗口边缘会话每轮压缩都「视图达标、出站重建仍超窗」——preflight 行走用盲视图判 fit,出站按重建后的真实体量计量,两者系统性差 ~5k token,每轮只推进 ~5k,长会话反复压缩直至整轮被拒。
- 什么原因导致的:fit 判定与出站计量走两条不同流水线、不同米制:行走读客户端重发数组(每轮同一份),出站走重建产物;id 抖动把未折叠质量反复送进分歧区,行走每轮「以为达标」提前退出。修法落在判定层(决策点校准),不是载荷过滤或米制造假——层次正确。
- 影响范围与严重程度:触发条件 = 已知基线会话 + 首轮折过且池子有剩余 + 探针实测 ≥ 窗口且分歧 ≥ max(10K tok, 2%×窗口)。修复前该场景 p1(特定条件下不可用:~5k/轮爬升直至整轮拒绝);修复后一轮收敛。无数据丢失、无 wire 破坏。
- 怎么修复的:首轮早退且池子有剩余时,跑一次全流水线重建当探针(公式与终局门逐字一致),超噪声底则跑一次有界纠正 pass,该 pass 内所有 fit 判定改在修正尺度上运行,折到「预测重建能装下」或诚实声明装不下为止;终局出站仍走正常重建 + 实测门(measured < limit),门本身从未放松。
- 是否有回归问题:逐项审过——零纠正旧路径(字节等价,case 4 字段级钉死);#553 unknown-baseline(整体排除出探针);#1839 forward-once 臂(条件逐字未动,operand ≤ 首轮值,方向安全);#3146/#4185 复检门 + doom 分层(路径未触碰,lastInputTokens 写入时序不变);relay 出口熔断(未触碰);stats.requests 四分支记账平衡(净 +1/请求);growth 模式与两层 limit 教义(未变)。有意变更两处已按 old→new 披露(见上)。未发现无意回归。
- 是否破坏缓存:不涉及——前缀缓存锚点/affinity/session-order 均未触碰;唯一新增开销是纠正 pass 的 summary 调用(有界至一个 pass),属修复必要成本。
- 是否改了设计方向:没有转向——正是落地源 issue 期望条款②(视图读取强制走重建后单一事实源);机制留在 preflight 编排层的内部字段,不跨模块边界。
- 是否引入了新的配置:无。
viewDeltaCorrection为内部字段,仅由纠正编排赋值;无新 config key / env var / CLI flag。
判定:APPROVE。PR 不触碰 kernel/、无 kernel-change 声明,不属人工评审档;一处非阻塞发现已当场修掉(commit 691ab4a,CI 在新头复跑中,当前 0 failed)。CI 全绿后由 owner 合并即可。
(ai: vllm-qwen/qwen3.8-27b) Review posted (GitHub API rejected the APPROVE event with "Can not approve your own pull request" — this account IS the PR author, so the verdict rides as a review comment on the PR thread): #5983 (review) Verdict: APPROVE — independent end-to-end review of head Direction (issue audit). #5974: at the window edge the preflight walk judges fit on the blind client view while egress is metered on the rebuilt body — two pipelines, systematic positive delta, ~5k tokens/round crawl. The PR implements clause ② as a bounded probe → at most one corrective pass, without touching either pipeline's own accounting. It fixes the judgment at the decision point — not by filtering payloads or fudging meters. Correct layer. Mechanism verified (independent re-read at src/server.ts:4296–4335 / 4355–4400 and every preflight.ts correction site):
Regression audit (existing behaviors touched, item by item):
Tests. New suite tests/issue5974-preflight-view-divergence.test.ts (5 cases): legacy baseline / positive corrected-fit (strictly more folds than uncorrected) / negative exhaustion (failure-kind pin ∈ {undefined, "exhausted"}) / zero-correction field-for-field identity / full-server common path asserting EXACTLY ONE forward. Both directions present per #3617; assertions have teeth (fixture self-checks overflow; the full-server case distinguishes summary calls from forwards by their task prefix). Local: 41/41 across the nine preflight-related suites + typecheck clean, at the original head AND after my fix commit. Full-suite verdict rides CI (green at Finding fixed on the spot (non-blocking). The mid-walk #1841 futility bail (src/preflight.ts:2793) computed its deficit as Behavior change disclosure (old → new):
结构化八问(中文)
判定:APPROVE。PR 不触碰 kernel/、无 kernel-change 声明,不属人工评审档;一处非阻塞发现已当场修掉(commit 691ab4a,CI 在新头复跑中,当前 0 failed)。CI 全绿后由 owner 合并即可。 |
[ework] CI fix verified green ✓ |
ranxianglei
left a comment
There was a problem hiding this comment.
Reviewed in a fresh clone (head 691ab4a7 against 5c3c2688).
What I verified
- New suite
tests/issue5974-preflight-view-divergence.test.ts: 5/5 pass. - Pinned neighbors (#1841 futility, #1933 calibration, #4185 forward arms, #3918 progress verdicts, #2952 tier recovery, #4079 egress fuse, #1839 ghost denominator): 31/31 pass.
tsc --noEmitclean (after buildingkernel+pi-subagents, the two pretypecheck subprojects),check:test-import-graphandtest-suite-lock gateboth ok. CI is green on head.
Correctness walk-through
- Pass 1 (correction = 0) is byte-identical to the legacy walk: every touched site in src/preflight.ts is gated on
+ viewDeltaCorrection(textTarget :1784, tier-distill loop/fit/cap :2025–2151, both relax resets :2376/:2419, pre-walk + mid-walk futility deficits :2353/:2794, futile-bail escape :3164, final fitsWindow :3255). - The probe gate (src/server.ts:4299) fires only when pass 1 exited early-fit with foldable mass left AND the session has a known baseline — unknown-baseline sessions keep the #553 upper-bound regime, and failed / no-fold passes fall through to the legacy arms untouched.
stats.requestsaccounting balances on all three paths: initial prepare +1; probe +1/−1; fresh rebuild +1/−1 (the probe-reuse path decrements zero times). Net +1 per client request in every case.- The probe's
lastInputTokensanchor (src/server.ts:4307–4310) mirrors the #1987 block exactly (same processedMessages fallback, same "estimate" source). The "estimate" source does NOT floor the corrective walk's baseline (src/preflight.ts:2207–2209 floors only "usage"/"overflow-arm"), so the probe can't accidentally pin the second pass. - Worst case = one extra bounded pass (fresh per-call budgets), capped by the #1841 futility gate on the corrected scale. The final forward/fail-fast still judges on the measured rebuild (
fits = rebuiltCalibrated < limit), so the corrective pass can never make a forward decision the measured body contradicts — at worst it lands on the #1839 forward-once / measured-413 arms, i.e. the legacy outcome plus one bounded attempt. - A probe whose kernel transform failed (empty
processedMessages→originalMessagesfallback) measures the same raw messages pass 1 saw, so the divergence ≈ 0 and the gate stays silent — no spurious corrective pass on that path.
Minor observations (non-blocking)
- The e2e case pins only the NEGATIVE side of the server gate (divergence below the noise floor → no corrective pass, probe rebuild reused). The positive firing path — gate arithmetic, verdict merge, probe-reuse vs fresh-rebuild, the requests decrement — is not directly pinned by a test. Synthesizing a deterministic view/rebuild divergence through the full server is hard, so pinning the preflight side at unit level (as done here) is reasonable; noting the gap for the record.
- The corrective pass assumes the view/rebuild divergence stays constant across its folds. If the true divergence shrinks as the pass folds (the re-entering mass stops re-entering), the pass folds a little more than strictly needed — conservative and bounded. If it grows, the final gate re-measures and falls back to the #1839 arm. Both directions safe by construction; noting the assumption is doing real work.
- When the divergence comes from mass the blind view cannot see (exactly the fold-reconcile re-entry case), the corrected-scale futility gate compares the blind view's foldable mass against the TRUE deficit and may bail "exhausted" even though folding would have helped the rebuild. The request then rides the #1839 forward-once / measured-413 — same as legacy — after one bounded attempt. That's the inherent limit of the approach (you can't fold what the view can't see) and the fallback is correct; noting it so the behavior is expected, not surprising, when it happens.
LGTM — the design keeps every legacy arm reachable and makes the post-reconstruction measurement the source of truth for the fit judgment.
Live sample: 29.5% view-vs-rebuild divergence, and pass 1 finished with
|
| Source | Tokens |
|---|---|
| cold-load baseline | 245,405 |
preflight view (deficit 0) |
676,385 |
| bili overflow estimate after 400 | 919,133 |
| upstream actual | 875,906 |
875,906 − 676,385 = 199,521 → 29.5% under-estimate, and because it came as deficit 0 pass 1 declared fit and never folded the remaining 75 viable ranges. It only folded one T1 range (20,790 tok) for the nudge, then sent. Note the internal spread too: preflight 676,385 vs the post-400 overflow estimate 919,133 — 36% apart, two estimates of the same body.
Useful contrast (same session, later restart)
| cold-load | blocks | baseline | preflight | outcome |
|---|---|---|---|---|
| 01:53 | 51 | 245,405 | 676,385 vs 750,000 → deficit 0 | 400, session dead |
| 13:05 | 8 | 635,557 | 748,880 vs 744,000 → deficit 4,880 | folded, request succeeded |
The 13:05 restart behaved, so this is not "old block count" — it is specifically the case where the view never computes a positive deficit.
Relation to the current fix
PR #5983 triggers the bounded corrective pass when pass 1 folded something and exited on an early fit while foldable budget remains. Here pass 1 did fold one range (m14732–m14814, 20,790 tok) and exited with deficit 0, then the rebuilt body measured 875,906 ≥ 750,000 — well past the max(10K, 2% window) noise floor. Two questions:
- Does the
deficit 0exit path count as "early fit" for the corrective-pass trigger? In this capturedeficit 0came from the view before the T1 injection was reflected; the injection then moved the reported number to750000 → 657414while the real body stayed at 875,906. - Where does the 676,385 view come from when the same request is later estimated at 919,133? If the 242,748 spread is in
estimateCoreMessagesinput rather than the estimator, it may be the same root as #5914 (cold-load dropslastUsagePayloadUpper/contextEstimateTokens), which this session also exhibits (kept=0, 2155 restamped refs).
Reproduce
Any session with 40–50 bili blocks, 160+ turns and a 20–30 万-token steady state: kill DSH after a restart-free stretch, wait ≥1 h, reopen the session. Watch for kept=0 / DIGEST DRIFT, then a preflight line with deficit 0 followed by a 400 whose message count is 25–30% above the view. Full session capture: session-572ee904-e897-4c5d-b647-f9584ca35af0 (166 turns, 21,021 events).
[bot] 🏷 Thanks — that's the largest measured view-vs-rebuild gap on record (29.5%), and it exercises exactly the path this PR changes. Both questions answered from the code at the current branch head; related existing thread for Q2: #5914 (open). Q1 — does the The probe gate is
Then the probe rebuilds the actual outbound once and measures it with the trusted meter family; your numbers give probe ≈ 875,906 ≥ window 750,000, divergence ≈ 875,906 − 657,414 ≈ 218K ≫ noise floor max(10K, 2%·750K = 15K) → the bounded corrective pass fires with that divergence as its exit bar, and every fit judgment inside it (exit comparator, futility deficit, relax triggers, final Your specific worry — "the injection moved the reported number while the real body stayed at 875,906" — is exactly what the design neutralizes: the trigger never trusts any reported or view-side number. The probe measures the reconstructed bytes themselves, and the divergence is built from that fresh measurement. Bookkeeping drift in the view cannot mask the trigger. Two honest boundaries:
Q2 — where does 676,385 come from when the same body is later estimated at 919,133? I can't attribute the 242,748 spread from here without the session files, but your hypothesis maps cleanly onto an existing open issue: #5914 — "buildSession loses persisted context estimation and usage-payload anchor after reload" (bug/p2/scope/storage). Its signature — One deliberate design note: #5983 is not supposed to depend on knowing why the view undershoots. Id-churn re-entry (#4543 family), anchor loss (#5914 family), estimator drift — whichever degrades the blind view, the corrective design absorbs it by forcing the fit judgment through the post-reconstruction measurement. Also worth separating: 676,385 (preflight core-messages meter) and 919,133 (overflow-path estimate after the 400) are two different meters with different inclusion rules — that internal spread is a metering-consistency question best pursued in the #5914 analysis rather than asserted in either direction here. Live state (just verified): branch head is now Nothing further needed from me on this thread; the merge call is yours. |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1162-master.a61c55c # this exact build
npm install -g billion-context@master # always the newest merged build
|
What
#4543 residual ① (carved out of the PR #5932/#5973 scope ruling — fold-reconcile domain, not gate metering): at the window edge the preflight walk judged fit on its own BLIND view (
processTurnon the client re-send, the same array every round) while the OUTBOUND reconstruction measured over the window. Fold-reconcile switch-pass id churn re-enters unfolded mass the two pipelines disagree about, so each turn under-folded by exactly the divergence — the ~5k-tokens/round crawl from the issue title ("view meets target but outbound reconstruction exceeds window").How
Issue expectation clause ②: force the fit judgment through the post-reconstruction single source of truth.
preflightCompressIfNeedednow runs the full-pipeline rebuild ONCE and measures it with the same meter family the system already trusts (estimateCoreMessages+ wire overhead + image reserve + the session's k̂ calibration).viewDeltaCorrectiononPreflightDeps). Every fit judgment inside that pass — exit comparator, futility deficit, both relax triggers/resets, tier-distillation funnel, finalfitsWindow— runs on the corrected scale, so the walk keeps folding until the RECONSTRUCTION is predicted to fit, or says honestly that it cannot.Behavior change (old → new)
NEW capability: a bounded corrective second preflight pass can run after an early-fit exit when the fresh rebuild measures over the window by ≥ max(10K tok, 2% window). Previously such a turn forwarded once for upstream arbitration (#1839 arm) regardless of how far over the rebuild was — the crawl. Outcome contracts unchanged: the #1839 forward-once arm, the #3146/#4185 post-compress recheck gate and the relay egress fuse (measured tiers from #5932) all keep their existing behavior. No config surface change:
viewDeltaCorrectionis an internalPreflightDepsfield set only by the corrective orchestration — no new config key, env var, or CLI flag.Tests
New
tests/issue5974-preflight-view-divergence.test.ts, both directions per #3617:viewDeltaCorrection: 0reproduces case 1 field-for-field;Targeted local runs green: the new file plus issue1841 (futility), issue1933 (calibration), issue4185 (forward arms), issue3918 (progress verdict), issue2952 (tier recovery), issue4079 (egress fuse) — 28/28 adjacent tests pass; typecheck clean. Full suite rides CI.
Closes #5974