What it shows
The end of the loop in detail. After execution and the two report-only reviews, a script decides: it scans for secrets, applies the repository's governance rules, and the change's scope is checked against the diff.
Only then does the change reach a commit or a merge. The hook on the developer's machine and the CI job run the same script, so there is one answer to whether a change passes.
Key decisions
- Models review; a deterministic script decides.
- One script, two places: the pre-commit hook and CI cannot disagree.
- The spec-first reminder is opt-in and never blocks; the secret scan always does.