Use scoped, evidence-backed, fail-first audits before merging

For security- or correctness-sensitive changes, perform narrowly bounded reviews against the current working copy and respect all excluded files, data, and parallel reviewer scopes. Keep audit passes read-only unless implementation is explicitly requested. Report findings first in severity order with exact current file-and-line evidence, deterministic adversarial probes or regression tests for every defect, commands and results, residual risks, and an explicit merge verdict. Reproduce issues with fail-first tests before making the smallest production fix, then run targeted and full verification. Treat malformed input and publication failures as fail-closed conditions, especially where stale open outputs, immutable-input integrity, path races, archive handling, or multi-file report coherence are involved. Replace repeatedly empty reviewers with smaller, disjoint scopes against the final code rather than overlapping active work or reviewing obsolete snapshots.