verify-completionlisted

Don't claim work is done, fixed, or passing unless you've just run the thing that proves it and read the output. Saying it's complete when you haven't checked isn't optimism — it's reporting something you don't know to be true, and it breaks trust the moment it turns out wrong. ## The one rule **No completion claim without fresh verification.** If you haven't run the verifying command in this turn, you can't say it passes. "Should pass now", "I'm confident", "the logs looked fine" are not evidence — they're the feelings that precede unverified claims. ## The gate Before stating any status, or even expressing satisfaction ("great", "perfect", "done"): 1. **Identify** the command that would prove the claim. 2. **Run** it — the full command, fresh, start to finish. Not a partial check, not a remembered result from earlier. 3. **Read** the whole output: exit code, failure count, warnings. 4. **Decide.** Does the output actually confirm the claim? If not, state the real status with the evidence. If so, state the claim *with* the evidence. Skipping any of these steps turns a verification into a guess. ## What each claim actually requires | Claim | What proves it | What does *not* | |---|---|---| | Tests pass | A fresh test run showing 0 failures | A previous run; "should pass" | | Linter clean | Linter output, 0 errors | A partial check; extrapolating | | Build succeeds | Build command, exit 0 | Linter passing; logs "looking good" | | Bug fixed | The original symptom retest