Skip to content

test: host-compaction cache proof across all four wires (#2695) - #2720

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-11_proof-hostcompact-wires
Oct 11, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-11_proof-hostcompact-wires

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

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)

  • The chat-only test is refactored into 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.
  • Per-wire payload builders/parsers (the judge upstream already spoke all four).
  • Zombie carrier identity is block-granular (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).
  • The settling window extends one body past the last zombie sighting (the pair that DROPS the final zombie is itself the bounded healing), then strict append-stability resumes; on google the eviction lands between two growth bodies rather than on a fold round-2 boundary.

Evidence

All four wires:

proof[chat]       REAP ok blocks=b2 content-retained coverage-stripped  VERDICT bodies=26 decimIdx=14 folds=4 unexplainedDivergences=0
proof[anthropic]  REAP ok blocks=b2 ... VERDICT bodies=26 decimIdx=14 folds=4 unexplainedDivergences=0
proof[responses]  REAP ok blocks=b2 ... VERDICT bodies=26 decimIdx=14 folds=4 unexplainedDivergences=0
proof[google]     REAP ok blocks=b2 ... VERDICT bodies=26 decimIdx=14 folds=4 unexplainedDivergences=0

Config surface / kernel boundary

  • No config changes.
  • No kernel/ changes — test-only commit.

Refs #2695 (the proof guards the fix shipped there), #2658 (the lane-drift lesson that motivated covering every wire).

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-11_proof-hostcompact-wires (ecbe810)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2950-pr.2720.05d7b06

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr2720.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit 0fa5fd5 into master Oct 11, 2026
14 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.252-master.0fa5fd5 (rolling master tag).

npm install -g billion-context@0.0.252-master.0fa5fd5  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

@ranxianglei
ranxianglei deleted the 2026-10-11_proof-hostcompact-wires branch October 15, 2026 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant