Iterative plan hardening with adversarial waves Use when a plan survives initial drafting but repeated adversarial review keeps returning MAJOR. Especially useful for detector/contract plans where correctness depends on exact status semantics, source boundaries, scheduler behavior, and output contracts. When this fits - The issue is reopened or preserved for re-file after earlier MAJOR reviews. - You already have one or more concrete review artifacts from Codex/Gemini. - The plan is still draft-only and must NOT move to yet. - The productive path is iterative tightening, not implementation. C…