Repository navigation
feat: add auditable batch content scanning - #12
Merged
Merged
Conversation
This was referenced Aug 24, 2026
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.
Change summary
Upgrade the content gate from a single-draft preflight into an auditable batch workflow while preserving the existing API and CLI contract.
preflight(), existing CLI flags and JSON fields,release_approved=false, and exit codes 0/1/2Evidence and design
The implementation draws lightweight practices from Vale, textlint, reviewdog, Ruff, Conftest, Argo Workflows, and Prefect. The fixed-commit and official-document evidence, tradeoffs, and follow-up roadmap are in
docs/github-landscape.md.Validation
ruff check src testspython3 -m compileall -q src testspython3 -m unittest discover -s tests -v(23 tests)python3 src/content_guard.py --self-test--fail-on-issuespython3 src/repository_checks.py .Compatibility and safety
The runtime remains Python standard-library only. Warnings and notes do not block human review; errors do. Automation never approves publication. Rollback is a single squash revert, and no data migration is involved.