tests: verify release input boundaries and forced full qualification - #591
Draft
bringhurst wants to merge 3 commits into
Draft
bringhurst wants to merge 3 commits into
bringhurst wants to merge 3 commits into
Conversation
bringhurst
added this pull request to stack #582
September 11, 2026 19:27
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.
Add positive and negative tests for every required release input, malformed/non-immutable identifiers, mismatched checksums and embedded source, missing source metadata, dirty tracked/untracked checkouts, wrong wrapper heads, forced full verification, and refusal to launch on invalid input. Fixtures use real temporary Git repositories and small synthetic archives; they are not release qualification evidence. All 80 Python tests pass. The guard also accepted the real retained metrics-gated archives and clean current checkouts in a separate identity-only probe, without claiming published-release or deployment approval.