verification-before-completion

To verify a bug fix before claiming completion, you must run the full verification command, read the output and exit code, and confirm the result. This evidence-first workflow prevents false completion claims by requiring fresh execution proof.

Evidence-first verification is a workflow that forces a run-read-verify sequence before any success statement is made. It applies to tests, builds, bug fixes, regression checks, commits, and pull requests where status must be proven with exact command output.

To stop false completion claims when creating a pull request, require fresh verification evidence before announcing a fix. Run the relevant verification command, read the output, and confirm the result instead of relying on assumptions that the work is done.

Yes, you need to run the full verification command to prove regression checks are passing. Reading the output and exit code confirms the result with exact execution evidence, ensuring the status is verified before reporting completion.

Yes, you can use this verification process for both builds and linting checks. It applies to common delivery steps including tests, linting, builds, regression checks, commits, and pull requests where status must be proven with fresh execution evidence.

Verifying completion claims without execution evidence leads to false success statements based on assumptions. Bypassing the run-read-verify sequence for tests or builds risks reporting unproven statuses, making it impossible to confirm if the work is actually done.