atomic-verifylisted

Verify before claim. No claim without fresh evidence in this turn. <trigger> - "done", "fixed", "passing", "complete", "ready to merge", "looks good" - "should work", "should pass", "this works" - "tests pass", "build green", "lint clean", "typecheck green" - "bug fixed", "regression resolved" - Any phrase implying success not preceded by verification output IN THIS TURN. </trigger> <workflow> ## The gate 1. **IDENTIFY** — what command proves this claim? 2. **RUN** — execute it fresh in this turn. 3. **READ** — full output, check exit code. 4. **VERIFY** — output matches the claim? 5. **ONLY THEN** — state the claim, WITH evidence. Skip any step = lying, not verifying. ## Claim → required check | Claim | Required verification | |-------|----------------------| | tests pass | run test command, see 0 failures | | build green | run build, exit 0 | | lint clean | run lint, 0 errors | | typecheck green | run typecheck (tsc/mypy/etc), 0 errors | | bug fixed | run repro that failed before, see it pass now | | agent task complete | check VCS diff for actual changes | | regression test works | red → fix → green sequence verified | ## Verification discipline Every completion claim needs a fresh command run in this turn. Watch for these moments: - Before saying "done" or "fixed" — run the proof command first - Before committing or pushing — verify all signals are green - After a subagent reports success — check the artifacts yourself - Partial checks (one test out of N) are