judgment-day

## Activation Contract Load only when the user explicitly requests Judgment Day or equivalent dual/adversarial review for a concrete target. Judgment Day is a standalone developer tool: judges run whenever asked, on any runtime, and need no review transaction, runtime identity, or delivery-receipt machinery to start. It replaces ordinary 4R as the adversarial method for that target; never run both. ## Hard Rules - Resolve matching project skills before starting and pass the same paths to both judges (`jd-judge-a`, `jd-judge-b`) and the fix actor (`jd-fix-agent`). - Build one complete immutable target, then launch two blind read-only judges in parallel with identical scope and criteria. - Each judge returns one neutral findings result and terminates. Wait for both; never accept a partial judgment. - Never launch `review-refuter`; two-judge agreement is the corroboration mechanism. - Only the parent orchestrator merges/persists findings, launches the fix actor (`jd-fix-agent`), and launches scoped re-judgment. - Fix only severe findings confirmed by both judges. WARNING/SUGGESTION rows remain `info`. - Permit at most two fix rounds and two scoped re-judgments. Re-judgment sees only the frozen ledger plus fix delta and may record fix-caused defects. - The only terminal verdicts are `APPROVED | ESCALATED`; never reset or extend an exhausted round budget. - A judgment issues no receipt and carries no delivery authority: it satisfies no commit, push, PR, or release gate. When th...