Repository navigation
[PR] fix: retire persistently-unmatched fold coverage after 3 evidence-less passes (#3849) — relay of stranded branch - #5398
ranxianglei wants to merge 8 commits into
Conversation
(ai: vllm-qwen/qwen3.8-27b) 查重:不重复。 本条是 [PR] relay issue,对应已开出的 PR #5398(#3849 滞留分支的接力:cherry-pick 标签:bug / scope/kernel / p1 / pr(与原始 issue #3849 同域——缓存命中带塌陷的成本爆炸类按 owner 10-19 政策判 p1;正文不涉及特定宿主客户端,客户端标签不打)。 核验状态(本会话独立核对):
行动:把 PR 分支 rebase 到当前 master、解冲突、本地 typecheck + 定向套件验证后推回同一分支(不动 master),完成后按八问汇报并附 CI 结论。 |
0a84db6 to
a129ffc
Compare
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.10978-pr.5398.daeafecThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5398.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) Rebase 完成,PR #5398 已可合并(等 CI)。 新 head: 冲突解决(7 处,全部是「两个机制各加各的字段」型,按并集解,不丢任何一侧语义):
关键交叉语义核查(#5142 × #3849,不是文本能看出来的部分): 我担心过 master 的 expected-rebase id 会被 PR 的 absence-streak 误伤(它们每轮都 missing,3 轮后会被 retire,可能打掉 #5142 的 本地验证(rebased head): typecheck 干净;定向套件 99/99( 八问
行为变更披露(PR 正文已载,重申):永久 unmatched 残留旧行为 = 永远留在覆盖集里反复 warn;新行为 = 连续 3 个无证据 pass 后退役,其后 #2202 账本分母收敛到存活基底。原因:这类 id 的字节在当前投影下永不复现,留着只有噪音和卡死的分母。 收工判定:代码侧就绪,mergeable=true;等 CI 绿即可由人工合并(PR #5398,Closes #3849)。CI 结果出来我补一条跟进。 |
b295753 to
5936de8
Compare
5936de8 to
73b7e19
Compare
|
(ai: vllm-qwen/qwen3.8-27b)
八问
非阻塞观察
门禁判定
判定:APPROVE(建议批准)代码正确、守卫齐全(repair-only + reap 之后 + majority-present 保护 + presence-reset)、测试有牙(真断言钉住退役时机/出现复位/claim 豁免/class-agnostic/warn-mode 零变更/reap 共存/仅退持久缺席子集保序)、行为变更已披露旧值→新值+原因、无 kernel/config/安全面。等 CI 全量 test 矩阵确认绿即可由人工合并(PR #5398,Closes #3849)。 |
(ai: vllm-qwen/qwen3.8-27b) 独立 review 完成(PR #5398 tip |
0908f69 to
0288daa
Compare
…-majority doctrine The absent-retire protection counted presence over ALL covered ids (reasoning included) against a hard-only denominator, and protected only when strictly below half were present. Both deviate from the doctrine: - a block whose hard (text) loss was masked by surviving reasoning cores was not protected (numerator inflated by reasoning presence), so its missing hard ids retired after 3 passes and the episode turned into a clean pass that reset foldDriftStreak/epoch-confirm; - exactly half present is NOT a strict majority (#5715 boundary), yet the strict < left such blocks unprotected for the same reason. Count presence over hard ids alone (claims still count as evidence, like the z-accrual's p+r) and protect unless a STRICT hard majority is present (2*prHard <= hard.length). The stale 'same majority test as the z-accrual' comment is rewritten to state the doctrine it now mirrors. Red on PR #5398 shards test(win22 s5)/test(ubu22 s2)/test(ubu24 s2): fold-anchor-doctrine subtests 7+8. All issue3849-absent-retire fixtures keep retiring (each has a strict hard majority present).
[bot] (ai: vllm-qwen/qwen3.8-27b) 进度汇报:CI 红项已修复并推送(head 7773869),冲突核对为不存在,等 CI 在新 head 上重跑。 排查结论
根因(#3849 的退役保护门
修法:保护门对齐 #5715 教义边界——只在非 reasoning id 集合上统计在场(claims 仍计为证据,与 z-accrual 的 p+r 一致),且「非严格多数在场即保护」( 行为变更披露:#3849 absent-retire 的触发面收窄——「恰好一半在场」和「reasoning 幸存者掩盖文本损失」两类块以前会被错误收缩,现在受保护(交给升级/reap 机制处理);健康块(严格多数在场)的退役行为完全不变。这是修 bug 而非语义漂移:旧行为直接打红了 master 既有的 #5715 教义测试。 验证:本地定向套件全绿——fold-anchor-doctrine 16 项(含此前失败的 2 个 subtest)+ issue3849-absent-retire 8 项(逐一核过 fixture,均为严格多数在场,退役照常发生)+ fold-reconcile/issue2202/issue2915 共 91 项 + issue5142 13 项;typecheck 干净。全量回归交给 CI。 八问
判定:红项已处理、冲突确认不存在;等新 head 7773869 的 CI 结果,镜像缓存尚未取到新 run(仍显示旧 head 的红状态),跑完我再跟进汇报。零 kernel 改动(PR body 已声明 No kernel change),合并按惯例留给人工。 |
[bot] (ai: vllm-qwen/qwen3.8-27b) CI 更新:新 head 7773869 全绿——镜像缓存 summary 30 项:failed 0 / pending 0。此前红的三个 shard(test win22-s5 / ubu22-s2 / ubu24-s2)全部转 success,其余测试 shard、static-gates(双平台)、mysql-contract、config-surface-guard、gate、pi-subagents-guard 均 success,e2e 车道按门控跳过。 收工判定:#5400 交代的「红项 + 冲突一次处理」已完成——红项根因修复(退役保护门对齐 #5715 教义)并验证,冲突核对为不存在(master 前进的 11 个提交与本 PR 零路径重叠)。PR #5398 现处于可合并状态,合并按惯例留给人工。 |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 收工确认(本条为最终状态,详情见上方两条汇报): 已完成:#5400 交代的「红项 + 冲突一次处理」全部落地。
行为变更披露:absent-retire 触发面收窄——「恰好一半在场」「reasoning 幸存者掩盖文本损失」两类块不再被误收缩(交给升级/reap 机制),健康块退役行为不变;属修 bug 而非语义漂移。 剩余与风险:无未验证项。PR #5398 处于可合并状态,合并按惯例留给人工。零 kernel 改动。 |
[ework] CI fix verified green ✓ |
1 similar comment
[ework] CI fix verified green ✓ |
7773869 to
c5a878a
Compare
…-majority doctrine The absent-retire protection counted presence over ALL covered ids (reasoning included) against a hard-only denominator, and protected only when strictly below half were present. Both deviate from the doctrine: - a block whose hard (text) loss was masked by surviving reasoning cores was not protected (numerator inflated by reasoning presence), so its missing hard ids retired after 3 passes and the episode turned into a clean pass that reset foldDriftStreak/epoch-confirm; - exactly half present is NOT a strict majority (#5715 boundary), yet the strict < left such blocks unprotected for the same reason. Count presence over hard ids alone (claims still count as evidence, like the z-accrual's p+r) and protect unless a STRICT hard majority is present (2*prHard <= hard.length). The stale 'same majority test as the z-accrual' comment is rewritten to state the doctrine it now mirrors. Red on PR #5398 shards test(win22 s5)/test(ubu22 s2)/test(ubu24 s2): fold-anchor-doctrine subtests 7+8. All issue3849-absent-retire fixtures keep retiring (each has a strict hard majority present).
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 冲突已解决并推送(新 head 本次做了什么
验证(本地定向,全量交给 CI)
八问
剩余:新 head |
…-majority doctrine The absent-retire protection counted presence over ALL covered ids (reasoning included) against a hard-only denominator, and protected only when strictly below half were present. Both deviate from the doctrine: - a block whose hard (text) loss was masked by surviving reasoning cores was not protected (numerator inflated by reasoning presence), so its missing hard ids retired after 3 passes and the episode turned into a clean pass that reset foldDriftStreak/epoch-confirm; - exactly half present is NOT a strict majority (#5715 boundary), yet the strict < left such blocks unprotected for the same reason. Count presence over hard ids alone (claims still count as evidence, like the z-accrual's p+r) and protect unless a STRICT hard majority is present (2*prHard <= hard.length). The stale 'same majority test as the z-accrual' comment is rewritten to state the doctrine it now mirrors. Red on PR #5398 shards test(win22 s5)/test(ubu22 s2)/test(ubu24 s2): fold-anchor-doctrine subtests 7+8. All issue3849-absent-retire fixtures keep retiring (each has a strict hard majority present).
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 冲突已解,新 head 本次做了什么(live 验证,非记忆)
七问
判定:PR #5398 在 head |
|
(ai: vllm-qwen/qwen3.8-27b) Re-review at head 63935d6 (rebased) — APPROVE stands. The PR was rebased onto a newer master (base
No new findings. CI for this head is still settling (0 failed, 13 pending, 1 in_progress at last mirror read); the code is byte-identical to the previously-green head Verdict unchanged: APPROVE (human merge) — no kernel/ or config-surface or security touch; §7.4 auto-merge not applicable (the change sits on the fold-reconcile identity/ledger surface). |
复审确认(head 63935d6,已 rebase 到新 master base 77fe0b1):PR 代码与我上次完整复审(#6903234752)逐字节一致(git diff 为空,master 未动 src/fold-reconcile.ts,#3849 修复 + #5715 对齐 + 我补的 2 个测试全部原样适用);唯一新 commit 63935d6 是机械 golden 重钉(仅 stateDigest/stateDigestAligned/metadata 摘要字段,无 wire 字节变更),原因是 master #6947 direction-C 存储改动改变了持久化 reply 状态。无新发现,无 kernel/config/安全面。CI 仍在跑(0 失败)。APPROVE 维持(人工 merge)。详见 PR #5398 复审评论(#6949179603)。 |
[ework] CI fix verified green ✓ |
1 similar comment
[ework] CI fix verified green ✓ |
63935d6 to
be377e9
Compare
…-majority doctrine The absent-retire protection counted presence over ALL covered ids (reasoning included) against a hard-only denominator, and protected only when strictly below half were present. Both deviate from the doctrine: - a block whose hard (text) loss was masked by surviving reasoning cores was not protected (numerator inflated by reasoning presence), so its missing hard ids retired after 3 passes and the episode turned into a clean pass that reset foldDriftStreak/epoch-confirm; - exactly half present is NOT a strict majority (#5715 boundary), yet the strict < left such blocks unprotected for the same reason. Count presence over hard ids alone (claims still count as evidence, like the z-accrual's p+r) and protect unless a STRICT hard majority is present (2*prHard <= hard.length). The stale 'same majority test as the z-accrual' comment is rewritten to state the doctrine it now mirrors. Red on PR #5398 shards test(win22 s5)/test(ubu22 s2)/test(ubu24 s2): fold-anchor-doctrine subtests 7+8. All issue3849-absent-retire fixtures keep retiring (each has a strict hard majority present).
(bot) 🏷 (ai: vllm-qwen/qwen3.8-27b) 冲突已解,新 head 本次做了什么(live 验证,非记忆)
七问
判定:冲突已解(mergeable=True/blocked),CI 在新 head |
(bot) 🏷 (ai: vllm-qwen/qwen3.8-27b) 本次触发核对为陈旧阻塞——冲突已在上一条回复(约 3 分钟前)解决并推送,本 run 全部 live 复核:
无新工作要做;七问总结见上一条回复。等 CI 全量矩阵出结果我再跟进汇报。 |
[ework] CI fix verified green ✓ |
|
(ai: vllm-qwen/qwen3.8-27b) Re-review at head be377e9 — APPROVE stands. The PR was rebased onto a newer master (base 77fe0b1 → a446a3c), now 7 commits. I verified the PR's code is byte-identical to the full review at c5a878a:
The only new commit (be377e9) is a mechanical golden re-pin: master's compress-success receipt reword (#7105, 497efc7) and the #6775 persisted-field work moved the persisted message shas and state digests. The 4 storage-render goldens were regenerated on the final rebased tree — wire shas are now byte-identical to master's pins (no PR-induced wire-body change); the only delta vs master is this PR's own post-retire persist contract (retired-id anchor swap + digest fields). No Verdict: APPROVE (human merge — fold-reconcile identity/ledger surface, §7.4 auto-merge N/A). The full 8-question review stands at the c5a878a comment. |
[review-worker-r1] 复审 head be377e9 完成:PR 又 rebase 到更新的 master(base 77fe0b1 → a446a3c,7 commits),代码与全量评审逐字节一致(#5715 retire-guard 原样在 src/fold-reconcile.ts:2495-2497),唯一新 commit be377e9 是机械 golden 重钉(master #7105 回执改词 + #6775 持久化字段,只动 wire sha/digest,无 PR 引入的 wire-body 变更)。无 kernel/配置/安全面。判定维持 APPROVE(人工 merge)。PR 确认已贴:#5398 (comment) |
(ai: vllm-qwen/qwen3.8-27b) Re-verified at head Independent spot-check of the re-review claims (not taken on faith):
CI (mirror cache, fetched 2026-11-18T21:49Z, sha 八问(结论,中文):
Verdict: APPROVE (human merge) — fold-reconcile identity/ledger surface, §7.4 auto-merge N/A. Full 8-question review stands at the c5a878a comment. |
[ework] CI fix verified green ✓ |
…s passes (#3849) A mid-session wire/dialect switch can leave covered ids whose old-dialect bytes never reappear under the new projection (standalone reasoning items, rewritten wrappers). Those ids lived in the block coverage set forever: the generic drift warn repeated on every turn and the block's p/r/t denominator stayed wedged above what the wire can ever satisfy again (#2202 ledger accrual frozen at the text fraction). Each unmatched covered id now carries a consecutive-absence streak (metadata foldAbsentStreaks, rebuilt per pass so presence or a claim resets it); after ABSENT_RETIRE_PASSES=3 evidence-less passes the id is retired from every block's effective/direct id lists and its anchor is dropped. Retiring makes no identity claim - surviving content rides unfolded until the next fold re-covers it under the current dialect. Guards keep the pre-existing terminal mechanisms intact: repair mode only (warn stays observe-only); runs AFTER the #2695 reap so majority-absent blocks are reaped whole first (retiring first would starve the z-streak denominator); only MAJORITY-PRESENT blocks are touched - majority-absent blocks belong to the escalation/reap machinery (#2193/#2695/#2903), and shrinking their denominator would also turn the episode into a clean pass that resets foldDriftStreak/foldDriftEscalated; class-agnostic by design (sanctioned reasoning drops converge too); both lanes (plugin + proxy). New conflict-ledger kind absent-retire; one info line per retirement event. FoldReconcileResult gains a retired counter. Behavior change (disclosed): permanently-unmatched residuals previously stayed listed and warned forever; they now retire after three passes, with #2202 ledger accrual converging to the surviving substrate afterwards.
The #3849 absent-residual retire intentionally changes the persisted end-state of the scripted golden scenario: the mid-history edited id (h_ce9559b8e1773afc) stays missing with no anchor match and retires from fold coverage after three evidence-less passes. Per wire: block effective/direct id lists 15 -> 14, its fold anchor dropped, foldCoverageByBlock.b1.t 15 -> 14, one absent-retire conflict event + foldAbsentStreaks bookkeeping, cache-ledger requestsAfter converging to 88/15, and stateShape.coveredRefSample spliced at the per-wire position (chat 5, anthropic 6, responses 7, google 2) with the next id taking the tail slot. Pinned fields per golden: stateDigest, stateDigestAligned, sectionDigests.state/.metadata, stateKeyDigests.blocks, stateShape.coveredRefSample. Re-pinned on current master (upstream has regenerated these goldens several times since the original pin, so neither side's values were valid for the merged tree): regenerated locally with scripts/update-storage-render-goldens.ts. Local fidelity proven by a pure-master control regeneration that reproduces the committed goldens byte-for-byte on all four wires, and by the regenerated records' per-turn wire digests being byte-identical to master's pins - the persisted-state delta is exactly the retire effect above. coveredRefSample ids are content-hash derived (machine-invariant); each new sample verified structurally equal to the pre-retire sample minus the retired id plus the displaced tail id, all counts unchanged.
…-majority doctrine The absent-retire protection counted presence over ALL covered ids (reasoning included) against a hard-only denominator, and protected only when strictly below half were present. Both deviate from the doctrine: - a block whose hard (text) loss was masked by surviving reasoning cores was not protected (numerator inflated by reasoning presence), so its missing hard ids retired after 3 passes and the episode turned into a clean pass that reset foldDriftStreak/epoch-confirm; - exactly half present is NOT a strict majority (#5715 boundary), yet the strict < left such blocks unprotected for the same reason. Count presence over hard ids alone (claims still count as evidence, like the z-accrual's p+r) and protect unless a STRICT hard majority is present (2*prHard <= hard.length). The stale 'same majority test as the z-accrual' comment is rewritten to state the doctrine it now mirrors. Red on PR #5398 shards test(win22 s5)/test(ubu22 s2)/test(ubu24 s2): fold-anchor-doctrine subtests 7+8. All issue3849-absent-retire fixtures keep retiring (each has a strict hard majority present).
The rebase onto f648217 (which carries #6705's fold-coverage linear rewrite, the instruction-preservation reconcile fixes, and 7402629's OpenAI cache-attribution golden regen) changes the persisted state the drive produces. Regenerated with the sanctioned scripts/update-storage-render-goldens.ts; only digest values move (stateDigest/stateDigestAligned, stats/metadata sections) — no wire body or structural change.
…lf + hard-only) Two regression tests for the #3849 absent-retire guard's #5715 alignment: the exactly-half boundary (2*prHard <= hard.length now protects) and the hard-only numerator (reasoning survivors cannot inflate the majority). Both fail under the pre-#5715 guard and pass under the aligned one. Fixture reasoningIds now mint genuine reasoning cores so present survivors keep their class through the anchor refresh.
…on-C storage, #6947) Master 80daffc (fix(storage): keep the reply stash out of the messages table, direction C1, #6947) changed the persisted reply state; the four storage-render goldens' digest fields (stateDigest/stateDigestAligned/ metadata) were regenerated via scripts/update-storage-render-goldens.ts against the final post-rebase code. Digest values only — no wire-body change.
…eceipt reword + #6775 persisted fields) Master's compress success receipt change (497efc7, PR #7105) and the #6775 persisted-field work moved the persisted message shas and state digests. Regenerated all four storage-render goldens on the final rebased tree with scripts/update-storage-render-goldens.ts: wire shas are now byte-identical to master's pins; the only remaining delta vs master is this PR's own post-retire persist contract (retired-id anchor swap + digest fields).
…atch2 systemFp head probe) Master's b18d596 (#7149 batch2) persists a 256-char change-probe head in the systemFp/canonicalSysFp metadata, moving the state digests. Regenerated all four storage-render goldens on the final rebased tree with scripts/update-storage-render-goldens.ts: wire shas are byte-identical to master's pins; the only remaining delta vs master is this PR's own post-retire persist contract (retired-id anchor swap + digest fields).
be377e9 to
32ebec4
Compare
(bot) 🏷 (ai: vllm-qwen/qwen3.8-27b) 冲突已解,新 head 本次做了什么(live 验证,非记忆)
七问
判定:冲突已解(mergeable=True/blocked),CI 在新 head |
[ework] CI fix verified green ✓ |
(ai: vllm-qwen/qwen3.8-27b) Re-review at head End-to-end review at the new head, done independently (full PR diff re-read, not carried from prior rounds): What changed since the last reviewed head (
Independent verification at
Regression inventory (existing behaviors audited, per ②)
Small findings: none — the code is byte-identical to the previously approved state and the sole new commit is a verified mechanical re-pin; nothing to fix on the spot, nothing below the fix-effort bar to drop. 八问(结论,中文)
Verdict: APPROVE (human merge) — fold-reconcile identity/ledger surface, §7.4 auto-merge N/A. CI fully green on the final head; mergeable, no conflicts. |
(ai: vllm-qwen/qwen3.8-27b) Re-review at head The PR was rebased onto a newer master (base Diff identity check — The single new commit Code state at
Regression inventory (existing behaviors audited at this head): #5142 expected-id partition (streak caps at 1, no double-retirement) — holds; #2695 reap ordering (retirement strictly after reap) — holds; #2202 denominator convergence (disclosed behavior change, old: wedged + warn loop → new: converges after 3 evidence-less passes); warn mode zero mutation; steady-state zero work; CI (mirror cache, sha 八问(中文)
Verdict: APPROVE (human merge) — fold-reconcile identity/ledger surface, §7.4 auto-merge N/A. The full 8-question review stands at the c5a878a comment; this round confirms the rebased head is code-identical with a verified mechanical golden re-pin. |
[ework] CI fix verified green ✓ |
Relay of the completed-but-unpushed work from #3849. The original session implemented and tested the fix (commit 65b945f1d on local branch 2026-10-20_absent-residual-retire) but its push was killed by an egress outage on 2026-10-19/20 and no PR was ever opened; the fix has been sitting off-master ever since while the same symptom family kept landing (e.g. #5395). This branch cherry-picks that commit onto current master.
What it does
A covered id that stays missing with NO anchor match every pass (mid-session wire/dialect switch whose old-dialect bytes never reappear under the new projection; host-side byte mutation such as tool-result pruning) used to live in the block coverage set forever: the generic drift warn repeated on every turn and the block's p/r/t denominator stayed wedged above what the wire can ever satisfy again (freezing the #2202 ledger accrual).
Each such id now carries a consecutive-absence streak (metadata foldAbsentStreaks, rebuilt per pass so presence or a claim resets it); after ABSENT_RETIRE_PASSES=3 evidence-less passes the id is retired from every block's effective/direct id lists and its anchor dropped. Retiring makes NO identity claim — surviving content rides unfolded until the next fold re-covers it under the current dialect. Class-agnostic by design (reasoning-dominated residuals retire identically). One info line + conflict-ledger entry (new kind absent-retire) per retirement event.
Ordering guards keep the pre-existing terminal machinery intact: repair mode only (warn stays observe-only); runs AFTER the #2695 reap so majority-absent blocks are reaped whole first (retiring first would starve the z-streak denominator); touches ONLY majority-present blocks — majority-absent blocks belong to the escalation/reap machinery (#2193/#2695/#2903) and shrinking their denominator would turn the episode into a clean pass that resets foldDriftStreak/foldDriftEscalated. Both lanes (plugin + proxy).
Rebase notes (conflicts resolved against current master)
Verification
Behavior change (disclosed)
Permanently-unmatched covered ids previously stayed listed and warned forever (the #3849 17x-per-hour warn loop; the #5395 614-id steady-state residual). They now retire after three consecutive evidence-less passes; afterwards the #2202 coverage ledger denominator converges to the surviving substrate (accrual transitions from the text fraction to full-on-survivors once the drop proves permanent). No user-facing config added. No kernel change.
Fixes #3849
Cross-link: #5395 (same symptom family via host tool-result pruner mutation — that issue additionally carries the shape-aware re-anchor + conflicts-visibility work)
Rebased onto current master (2026-11-01) + golden pin update
The relay cherry-pick was cut against master 5594c13; master advanced to 7578e81 (incl. v0.1.210 and the #5142 expected-rebase series) before this branch could push. The branch now carries two commits on 7578e81:
a129ffc18— the fix itself. Conflicts resolved by union:FoldReconcileResultliterals keep both the [Performance][dsh] Mega-sessions pay an ever-growing O(full-history) fold-reconcile tax every turn: expected host churn (one-shot carrier retirement, image/offload retroactive rewrites) misclassified as drift | 大会话每轮付不断增长的 O(全史) fold-reconcile 税:合法宿主变更(o… #5142expectedRetiredand the [Bug] Mid-session wire/dialect switch leaves a permanent unmatched-id residual that rides the wire unfolded and taxes the prefix cache every turn (v0.1.201) #3849retiredfields;resetFoldDriftStateclears both latch metadata keys; the clean-pass early return keeps master's post-accounting condition so an already-classified host-rebase pass still short-circuits before streak bookkeeping. Cross-mechanism probe (T1 replica, repair mode, 40 turns): [Performance][dsh] Mega-sessions pay an ever-growing O(full-history) fold-reconcile tax every turn: expected host churn (one-shot carrier retirement, image/offload retroactive rewrites) misclassified as drift | 大会话每轮付不断增长的 O(全史) fold-reconcile 税:合法宿主变更(o… #5142-classified ids never enterplan.unmatched, so absence-streaks stay 0 whileexpectedRetiredaccrues monotonically — the two mechanisms partition the missing-id space, no double counting.5936de85c— storage-render golden pin update (justified below).Golden update justification (
tests/golden/storage-render/*.json)The scripted scenario contains one mid-history edit (editedAt 12); the edited-away covered id is exactly the #3849 residual shape, so the fix retires it after 3 evidence-less passes. Intended persist-contract change, per wire:
blocks.0direct/effective lists droph_ce9559b8e1773afc(15→14), its fold anchor removed,foldCoverageByBlock.b1.t15→14, anabsent-retireconflict event recorded,foldAbsentStreaksset, cache-ledger accrual converges (requestsAfter88/15). Wire bodies,turns[], block contents and stats sections are byte-invariant (A/B state dump between pre/post heads shows only those fields differ).Digests were taken from CI-observed runner output (byte-identical across all four runner cells in two consecutive runs), not local regeneration: this dev container produces machine-specific nudge/tsStamps/stats digests that no local build can make match the runners (pure master is red locally / green on CI today; TZ, node version, stale committed dist, timestamp leaks all ruled out). A locally-regenerated golden would bake unreproducible values — the non-hermetic suite itself is filed separately.
Verification on rebased head
issue3849-absent-retire8 tests,fold-reconcile,issue2202-coverage-accrual,issue2915-order-centric-reconcile), plusissue5142-expected-rebase11/11 and conflict-lifecycle/remediation 15/15.