Streamline CI preflight and focused verification - #130
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
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.
What changed
CI previously repeated committed-range hygiene in every shard, and the contribution guide maintained a second expanded test inventory. Run hygiene once before the four existing shards, preserve their fail-closed aggregate, and list commands directly from the canonical registry. Add safe rejection context and selectable remediation groups for focused development.
The installed-package integration suite exercises the real CLI with a synthetic worker, checks candidate edits and scope rejection, and explicitly characterizes the existing outside-write gap. It does not fix or claim containment for that gap; product remediation follows this process-only change.
Verification
No provider or account calls are involved. Existing four shard assignments and the historical receipt-v1 binding remain unchanged; the new integration stage belongs to other-a.