verification-before-completion

To prevent false completion claims, enforce a verification gate before committing code by running the project's exact test command, inspecting the full output and exit code, and including that evidence before asserting success.

Requiring fresh verification means executing the proving command completely, reading full stdout/stderr and exit codes, and only then making success claims to prevent false or premature statements that work is fixed or passing.

Before opening a pull request, run the project's build and test commands, confirm zero failures and exit code 0, and paste the command output evidence to verify outputs before claiming completion.

Apply a verification gate in QA workflows before creating pull requests, merging branches, marking tasks done, or accepting agent-reported results to ensure observable verification evidence confirms actual completion.

Marking a task complete fails because without executing the exact verification command and inspecting its exit code and full output, you lack the observable evidence required to prevent false or premature completion claims.