Codex Guard v1.12.0
Honest content-scan coverage
Codex Guard now distinguishes no findings from not scanned.
- reports scanned / eligible changed-file coverage
- returns a neutral, non-blocking warning when GitHub omits a textual patch
- lists affected paths with bounded, sanitized output
- exposes coverage in Action outputs,
findings-json, and sweep reports - reports uncertainty at GitHub's 3,000-file pull-request API limit
- declares and tests the existing
ci-failure-countoutput
This design borrows the mature-tool principle of separating visibility from enforcement: incomplete coverage is impossible to mistake for a complete clean scan, but it does not suddenly break existing users.
Full changelog: v1.11.0...v1.12.0