maintenance: verify published v0.1.0 proof on current main - #149
Merged
Merged
Conversation
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
1 participant
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.
Maintenance goal
Treat the already-published v0.1.0 proof artifacts as an external compatibility fixture.
The new regression gate downloads the public GitHub Release assets, verifies their pinned SHA-256 digests and release source commit, then runs the current IndependentExecutionProof and Acceptance Artifact verifiers against the published bytes.
This catches maintenance regressions that ordinary current-tree tests cannot: a verifier/API change that silently makes v0.1.0 public proof artifacts unreadable.
Boundary
No new runtime, policy, provider semantics, lifecycle phase, proof format, or product surface.