Repository navigation
test: host-compaction cache proof across all four wires (#2695) - #2720
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2950-pr.2720.05d7b06This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2720.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.252-master.0fa5fd5 # 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.
What
Extends the host-compaction cache proof (introduced with the #2695 fix in #2707, chat wire only) to all four wires: anthropic, responses, google in addition to chat. This closes proof gap #2 from the cache-coverage audit: #2658 taught us that a compaction fix landing on some lanes but not others ships broken — the proof matrix must exercise every wire, not just the one the bug was found on.
Harness changes (test-only, no runtime code touched)
driveHostCompact(wire, ctx)+ four thin per-wire tests (chat 200K / anthropic 400K / responses 200K / google 1M windows), driving the same scenario: seed 12 turns → two folds → unframed host decimation of mid-history → regrowth → assert zombie carrier eviction is bounded, the fold re-arms, and growth is append-stable outside the healing window.elBlocks/bodyBlocks): on chat the carrier renders as its own message element, but on anthropic/google it is APPENDED to the anchor message's content array/parts — element-level comparison is anchor-prefix-sensitive and misses it. Carrier identity = exact text-block equality against the pre-decimation seed carrier set (no fuzzy matching).Evidence
All four wires:
npm run typecheckclean.Config surface / kernel boundary
kernel/changes — test-only commit.Refs #2695 (the proof guards the fix shipped there), #2658 (the lane-drift lesson that motivated covering every wire).