Repository navigation
test: pin the re-fold generation cache contract across all four wires (#2741, #2733) - #2762
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3028-pr.2762.e4f98f0This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2762.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.274-master.5c86fa7 # this exact build
npm install -g billion-context@master # always the newest merged build
|
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.
Closes the corpus gap surfaced while investigating #2741: the cache-proof suite only ever exercised first-generation forward folds (
makeProofTriggeralways citesrefs[2]..refs[len-6]of the current body). Production sessions chain re-folds rooted at old anchors constantly (session 01a126aa in the #2733 log re-foldsm00007–m00023after pushing into them02400s) — exactly the geometry that produced the per-fold prefix collapse fixed by #2755 (kernel 0.0.117), which had no byte-level proof at all.What the new phase proves
driveRefoldChain(all four wires: chat / anthropic / responses / google):m00001, the pinned first user message) — the 192版本缓存命中率低codex #2733 production geometry. The trigger anchorsfirstRefon the pin message itself (NOTparseRefIds(body)[0], which is the tool-doc example tagm00175present in every body).Assertions at the re-fold boundary:
[Compressed conversation section]byte occurs after the pin marker. Pre-fix(kernel): fold summaries may never precede the pinned first user message (#2733) #2755 on anthropic/google the carrier merged into the pin's content array ahead of the pin part — same head-stab, different wire shape; only the byte-order form catches it.+1rule ofcheckFoldPre); head bytes stable; bytes before the replaced carrier unchanged; the swallowed generation-1 carrier must not render beside its successor (stale-copy leak, 192版本缓存命中率低codex #2733); core shrinks.unexplainedDivergences=0.Teeth (A/B, kernel rebuilt in place)
db96692c^..d4133a85reverted)All four pre-fix failures carry the exact production signature (summary precedes the pin).
Harness notes
isRound2Bodyfinds the round-2 via the compress call;refoldIdxadditionally requires the rooted summary text.Compression FAILEDcheck) after the first A/B round caught exactly that (badfirstRefcited the tool-doc example ref).input[0], so its pin index is 1, like chat; anthropropic/google hoist the system out of the array.Config surface
None — test-only change.
Kernel boundary
No
kernel/change. The fix under proof is the already-merged #2755 (kernel 0.0.117); this PR adds the missing bili-side byte-level regression proof.Refs #2741, #2733, #2755.