Repository navigation
[PR] test: pin the live session-resolve ladder (live twins + live-state resets) — #2989 - #2991
ranxianglei wants to merge 2 commits into
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3388-pr.2991.d145a4dThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2991.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
Follow-up commit a3f64b5 (小问题直接修, found during the pre-merge sweep): the #841 cold-load test in |
a3f64b5 to
223e755
Compare
…es that exercise it (#2989) The #2815 stack rewired production session identity to personaConversationOrder (src/session-resolve.ts) and retired src/persona-anchor.ts from the wiring, but the proof surface kept driving the retired module: three suites pin its ladder, six suites reset only its (now inert) anchor map while the LIVE order skeletons never reset, and nothing pinned the new resolver's contract directly. - tests/session-resolve-twins.test.ts: live twins for the full ladder (claim/shallow tag claim/|sub:aux, match/ride, fork-lane byte continuity vs a locally computed sha256-16 so persisted pre-upgrade lanes keep their keys, grown/compacted reanchor, line-confined model switch migration, post-restart chain-race rescue + control, head truncation, #150 task lane) plus the two DESIGNED divergences from the retired ladder pinned explicitly: (a) header-corroborated absorption is looser (any persona change + declared model switch), (b) tag-less shallow first sight derives |sub:aux. - Old-vs-new parity was probed exhaustively first: every scenario the retired pins cover agrees at the key level except (a)/(b). - Mark the three retired-module suites as retired pins; do not extend. - resetSessionOrderForTest() beside every resetPersonaAnchorsForTest() call site (incl. dsh-persona-fingerprint's startRig) so test isolation covers the live state. Refs #2989
…nified store's top-level index.db broke the scan)
223e755 to
5a03ab9
Compare
|
Rebased onto master (663fdb2) after #2990 landed in parallel — same issue, overlapping surface. Resolution = union of intent:
Verification on the rebased head: twins + all affected suites 106/106 green, session-continuity-proof e2e 9/9, |
Upstream conflict resolved — rebased onto current master and pushed ( What conflicted. Master moved while the branch sat open: #2990 (the sibling half of the #2989 stack) merged first and already did the rig-hygiene cleanup in the same 7 suites this PR touches — replacing the dead Resolution. Rebased onto master ( Verification on the rebased head (local, targeted):
State. Merge conflict cleared (mergeable=true; 结构化结论(八问):
判定:冲突已解除,CI 全绿后即可由人合并(按规则我不执行 merge)。 |
Confirmed the final head (
State: mergeable=true, conflict-free ( |
CI update on What failed (one test, unrelated to this PR): Why it's not this PR's fault:
No action needed on the PR itself — conflict resolved, tests verified locally (51/51 targeted + gate + typecheck), CI green after rerun. Per repo rules the merge stays with you. |
|
(ai: zhipuai-lb/glm-5.3) 孤儿票清理:标题指向的 issue 已关闭,修复已由其他路径落地。关单;误判请 reopen。 |
What
The #2815 stack rewired production session identity to
personaConversationOrder(src/session-resolve.ts, ddf366b) and retiredsrc/persona-anchor.tsfrom the wiring. The proof surface kept driving the retired module: three suites pin its ladder, six suites reset only its (now inert) anchor map while the LIVE order skeletons never reset, and nothing pinned the new resolver's contract directly (#2988 finding ① class).Changes
tests/session-resolve-twins.test.ts(new, 14 tests) — live twins pinning the ladder where it runs:|sub:aux(never claims raw)<raw>|sub:<fp>asserted against a locally computedsha256(system)[0..16]— persisted pre-upgrade fork lanes keep their sessions across the Inbound markers: one declarative strip engine for all four wires (#2789, #2798, #2811 plan B) #2815 swap; the pin survives persona-anchor's eventual removal|sub:task:<skel8>(Codex 集成:guardian 审批请求进入压缩管线,导致明确授权无法被识别 #150 guard)_sub:会话不继承父会话 fold 块:上游上下文从 ~83K 瞬间膨胀到 794K、命中归 0、节省转负(0.1.187/0.1.188) #2817); the retired module required a line-confined diff and forked this shape — the pin says: if this looseness ever mis-absorbs, tighten there first|sub:auxinstead of riding raw (会话身份:顺序+自铸id 为认领主判,hash 降级为防漂移护栏(通用规则,取代 persona-fp 阶梯) #2944)dsh-persona-continuity,issue2601-persona-fork-lineage,issue2601-model-drift-absorption(the last notes divergence (a) explicitly: its strict "extra changed lines keep forking" cases migrate in the live resolver). Do-not-extend markers.resetSessionOrderForTest()beside everyresetPersonaAnchorsForTest()call site (durable-tool-identity, issue2481/2446/2447/2419, responses-instructions-drift) and in dsh-persona-fingerprint'sstartRig— previously these suites reset only the inert module, leaving the live skeletons map un-reset across tests.Regression check (the issue's third ask)
Test evidence
tests/issue2944-neutral-skeleton.test.tsunchanged and green.Refs #2989