Fix privacy preflight with exact v2 review for all findings - #17
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.
Closes #8. Migration privacy preflight now offers a value-free, exact-snapshot v2 approval token for all scanner categories. Approval is required before target writes and applies only to the migration; public-tree detection and pre-push Gitleaks remain unchanged. Includes mixed-category, scanner self-match, stale v1 token, snapshot drift, rollback, scanner parity, and non-UTF-8 path regression coverage. Bumps the packaged skill to 0.9.9.
Validation: release gate 12/12; source/package skill validators, Codex plugin validator, strict Claude plugin and marketplace validators, and Claude tag dry-run passed.