Skip to content

test: regen storage-render goldens for the #3090 fold-turn stop signal - #3092

Merged
ranxianglei merged 2 commits into
masterfrom
2026-10-14_golden-tail-regen
Oct 14, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-10-14_golden-tail-regen

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Master's test matrix is red on all four legs: storage-engine-proofs compares wire digests against goldens committed before #3090. #3090 intentionally changed the fold-turn receipt (stop signal replaces a sub-threshold advertised range — the receipt is resent history, so the wire body legitimately changed).

Diff scope (all four wires): only turn 9 (the fold turn) body digest/bytes (chat −417 B), plus the state-view section digests that cover the tail content (stats/metadata/stateDigest). Landmarks (foldAt/editedAt/summaryFrom) and every other turn are byte-identical. Both restart legs (legacy/full, keepFile/dropFile) agree pairwise — this is a pure golden refresh, no behavior delta beyond #3090's intent.

Local: engine-proofs 12/12 + golden-render 5/5 with the new goldens. Merging this unblocks master (and #3070's stack).

…op signal (#3090 follow-up)

#3090 made the post-compress tail honor the kernel's shouldInject
verdict: at the drive's fold turn the leftover sits below the kernel's
threshold, so the receipt now ends with the stop signal instead of
advertising a sub-threshold range. Wire-visible by design (the receipt
text is resent history): turn-9 body digests shrink accordingly
(-417 B on chat) and the persisted-view section digests (stats/
metadata/stateDigest) shift with the tail content they cover.
Landmarks (foldAt/editedAt/summaryFrom) and all other turns are
byte-identical. Restores the master test matrix (#3090's CI legs were
red on the stale goldens).
@github-actions

github-actions Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-14_golden-tail-regen (4f53552)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.3522-pr.3092.1840d39

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-pr3092.tgz
npm install -g package

Install instructions are refreshed on each push.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.393-master.b7ec3d0 (rolling master tag).

npm install -g billion-context@0.0.393-master.b7ec3d0  # 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.

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