verification-before-completionlisted

# Verification Before Completion Require fresh evidence before any completion claim. ## Core Rule Do not claim that work is complete, fixed, passing, ready, or safe to merge unless the proving command or check ran after the final relevant edit and its output was read. Evidence comes before claims. ## Gate Before claiming status: 1. Identify the command or check that proves the claim. 2. Run the full command or complete the full check. 3. Read the output, exit code, and failure count. 4. Compare the evidence to the claim. 5. Report the actual status with the evidence. If the evidence does not prove the claim, report the gap instead of softening the wording. ## Required Evidence | Claim | Required evidence | |---|---| | Tests pass | Fresh test output with a passing exit code and no failures | | Lint is clean | Fresh lint output with a passing exit code | | Build succeeds | Fresh build output with a passing exit code | | Bug is fixed | The original symptom or regression test now passes | | Regression test is valid | Red, green, and restored-green evidence | | Agent completed work | VCS diff plus relevant verification, not the agent report alone | | Requirements are met | Re-read checklist or spec and verify each item | | PR is ready | Local verification plus any required pre-PR checks | ## Red Flags Stop and verify before using wording like: - "done" - "complete" - "fixed" - "passes" - "ready" - "green" - "safe to merge" - "should work" - "looks good" Also stop bef