verification-before-completion

To verify a bug fix before reporting completion, re-execute the exact validation command and inspect the fresh output to confirm the evidence supports the stated result. This prevents false claims by requiring proof of success rather than relying on assumptions or stale data.

Evidence-first verification for software builds is the process of forcing a full re-execution of validation commands and reading the complete output before claiming success. It gates completion claims by requiring fresh exit-code evidence to prove build readiness.

To run pre-commit checks and validate test runs, fully re-execute the relevant testing commands and read the complete output. You must confirm that the fresh command output and exit codes support the stated test success before announcing completion.

No, you cannot use stale output to claim release readiness. Completion gating requires a full re-execution of validation commands to generate fresh evidence, ensuring that the build or fix status is actually proven before reporting success.

You need to re-run validation commands for QA whenever you are about to announce test success, build success, bug fixes, or PR readiness. Re-execution is required to prove the latest result with fresh command output and exit-code evidence.

The best way to prevent false completion claims in CI is to enforce completion gating by reading complete fresh output from re-executed validation commands. This approach ensures that every positive status update is backed by current exit-code evidence.