verification-before-completion

# Execute → About to claim "done", "passing", "fixed", "complete", "verified", "release-ready", or "ready to hand off"? → **Verify first, then claim only what the evidence supports.** 1. Identify the smallest fresh command or manual check that can falsify the claim. 2. Run or perform it completely. 3. Read output, exit status, failures, and covered scope. 4. Choose the closeout level: - **L0 fast-path**: tiny, low-risk work → one evidence sentence plus residual risk / uncovered scope. - **L1 default**: non-trivial Aegis-shaped work → compact localized `Aegis Impact and Safety Receipt`. - **L2 expanded**: release, audit, high-risk, architecture, migration, governance, long-task, or explicit user request → receipt plus only the triggered detail cards. 5. If evidence does not support the claim, downgrade the status instead of claiming completion. Done means: fresh verification evidence exists, covered and uncovered scope are explicit, residual risk is stated, confidence is graded, and any triggered baseline / complexity / retirement / ADR boundary has been folded into the single closeout surface or expanded because the risk requires it. # Verification Before Completion ## Purpose Prevent unsupported completion claims while keeping ordinary completion output compact. This workflow is advisory method-pack discipline; it does not grant runtime authority, authoritative `GateDecision`, `PolicySnapshot`, evidence sufficiency, or final completio...