verification-before-completion

Identify the command that proves your claim, run it fresh and completely, read the full output including exit code, then state your claim with that evidence. Never commit based on previous runs or assumptions.

Proof is the actual test command output showing zero failures from a run executed in the current session. Previous runs, partial checks, or statements like "should pass" do not qualify as verification evidence.

No, a linter passing does not prove compilation succeeds. Linters check style and syntax patterns but do not verify that the code compiles or builds, so you must run the actual build command and confirm exit code zero.

Use the red-green cycle: write the test, run it to confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

No, agent success reports must be independently verified. Check the version control diff to confirm actual changes were made and run relevant verification commands yourself before reporting the true state.