verify-before-donelisted

Hard rule: **Only evidence gathered after the last relevant change to the code, files, or environment, and directly sufficient to prove the claim, counts.** - Claiming completion without sufficient evidence = lying; running the full test suite for a typo = waste. - You may reuse evidence just gathered, but state when it was gathered and confirm that no code was changed, nothing was pulled, and the environment was not modified afterward. If you cannot say for sure, check again. ## Required checks (before any claim of success or completion) 1. What claim must be proven? What check is just sufficient (command output / diff / artifact inspection…)? 2. Was the evidence gathered after the last relevant change? Yes—state when. No / uncertain—**check again**. 3. If you ran a command, read all output, inspect the exit code, and count failures. If you inspected a diff or artifact, state what you checked and the result. 4. Does the evidence actually prove the claim? Yes—state the conclusion together with the evidence. No—report the true status. Skipping any step = lying, not verification. ## Could not run ≠ skipped If a command cannot run (missing environment, broken dependencies, timeout), **verification failed**. Report that verification could not be completed and what blocked it. Do not quietly mark the step green as “skipped,” and do not misreport an environment problem as a product failure. ## None of these counts as "verified" | Claimed evidence | Why it does not count | |---|