HAC-335: regenerate the registry, which kept a superseded capture SHA - #36
Merged
Merged
Conversation
`capturedFromSha` on the four cockpit captures said 7d62f6f. The captures were last taken at 07e1a93, which is what capture-manifest.json records and what build-registry.mjs reads. The registry was simply not regenerated after that recapture, so a judge-facing provenance field named the wrong commit. Found by rebuilding every generated artifact and diffing. The HAC-334 model, masters and PDFs, the HAC-341 view model, and the HAC-343 judge export are all byte-identical on rebuild; this was the only drift. The package gate did not catch it because it verifies capture freshness against the render-source digest — whether the frames are stale relative to the surface they came from — and not whether the registry agrees with the manifest about which commit was being served. Recorded rather than fixed: closing that gap is a gate change, and this pass is a freshness audit. Generated, not hand-edited, and idempotent on a second rebuild. pnpm run check exit 0, 658 tests, typecheck and build clean.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
capturedFromShaon the four cockpit captures said7d62f6f. The captures were last taken at07e1a93, which is whatcapture-manifest.jsonrecords and whatbuild-registry.mjsreads. The registry was simply not regenerated after that recapture, so a judge-facing provenance field named the wrong commit.How it was found
Bounded freshness audit — rebuilt every generated artifact and diffed:
Why the gate missed it
The package gate verifies capture freshness against the render-source digest — whether the frames are stale relative to the surface they came from. It does not check whether the registry agrees with the manifest about which commit was being served.
Recorded rather than fixed: closing that gap is a gate change, and this pass is a freshness audit.
Scope
Generated, not hand-edited. Idempotent on a second rebuild. Single file, staged by explicit path.
pnpm run checkexit 0 · 658 tests · typecheck · build — all clean.