Dashboard › craft › Require rigorous read-only, evidence-ba…
01a08237-8611-7345-b86b-19f7a9cb5df2| Project | Hits | Last recalled |
|---|---|---|
| opencode-lore | 10 | 1h ago |
| cli | 2 | 7d ago |
| opencode | 2 | 9d ago |
Before declaring a release-critical PR merge-ready, approving, or merging, conduct an independent, adversarial, read-only audit of the exact current head against its explicit base. Inspect the complete diff, changed and relevant unchanged source, callers, tests, docs, workflows, and generated artifacts. Verify requested behavior, security and compatibility invariants, edge/error cases, regression coverage, CI/bot and review requirements, and diff hygiene with file:line evidence. Treat scope drift, unrelated churn, broad error suppression, silently ignored unexpected states, and inadequate regression evidence as merge blockers. Report severity-ranked findings, explicit PASS/FAIL coverage and gaps, and a definitive merge verdict; re-audit after every fix or commit.