Multi-dimension adversarial review of code diffs

Deep pre-merge gate for high-risk changes (T3: migrations, RLS, coaching prompts, consent flows) where multiple correctness/security/perf/compliance angles must pass.

• · git ref (args.ref, default HEAD) — branch or PR head to review vs origin/main

• · findings per dimension (correctness, security-samd, perf-droplet, srs-compliance) with title, file, severity, detail
• · verdict per finding: isReal boolean, reason
• · confirmed findings (filtered to isReal=true)

• · git (to fetch origin/main and compute diff)

• · origin/main branch exists
• · .claude/rules/coaching.md, .claude/claude-security-guidance.md, .claude/rules/cv-pipeline.md present
• · docs/SRS.md and decisions.md (ADRs) available for SRS-compliance review

• · adversarial refutation step may miss subtle logic errors
• · false negatives if verifier cannot reproduce concern from code alone
• · dimension-specific rules may drift if docs are not updated

• · 4 parallel review dimensions: correctness, security-samd, perf-droplet, srs-compliance
• · adversarial verification: agent tries to REFUTE each finding
• · defaults to isReal=false if verifier cannot reproduce concern