verification-before-completion

To verify a build and test run before a pull-request claim, execute the relevant command, read the full output and exit code, and use that fresh evidence to confirm the work is passing before declaring completion.

Evidence-first verification prevents false completion claims by requiring fresh test or build output and exit codes before allowing any statement that a code change, bug fix, or regression check is finished and passing.

To stop unverified bug fix claims before a pre-commit update, run the specific verification command for the fix, review the actual output, and only report success after confirming the evidence proves the issue is resolved.

Yes, you can use automated verification commands to check code changes before reporting task completion by executing the build or test command, reading the full output, and confirming the exit code indicates success before making any claims.

The best way to ensure status integrity when reporting regression test results is to execute the test suite, review the complete output and exit code, and base your passing claim strictly on that fresh verification evidence.

Requiring fresh verification evidence for pull-request status updates matters because it prevents false completion claims by forcing you to run the build or test command, read the actual output, and prove the work is passing before sharing results.