Strengthen unit shaping and repeated-review escape hatch - #14
Merged
Merged
Conversation
Boundary: is now a closed, case-sensitive vocabulary. When present it must be exactly filesystem, process, or network; unknown values fail structural validation instead of silently skipping risk accounting. Omitting Boundary: remains valid. Spec requirement and scenarios updated to state the rule explicitly.
Removes the unreachable strings.HasPrefix(baseDigest, "") assertion from TestBoundaryVocabularyAffectsUnitDigest and applies gofmt to internal/validate_queue_test.go, which this branch touched.
7 tasks done
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.
Summary
Boundary:vocabulary and account for five standard risksvalidatesuccess output now states structural-only scope and unverified implementation semantics across text, minimal, and JSON modesCloses #13.
Test plan