verification-before-completion

Preventing unverified completion claims requires running full build and test commands, inspecting their output for success, and attaching that evidence to your pull request. This enforces validation of results before making any success assertions.

Build validation before a release is the process of executing your verification commands on the latest changes and confirming successful output. It maintains an auditable trail of results to justify success statements in releases.

Enforcing fresh verification evidence involves running the full verification command on your latest changes and inspecting the output for adequacy before committing. This process ensures evidence is gathered before assertions are made.

Running tests before creating a pull request is required to validate results and prevent dishonesty. You must execute the full command, read its output, and verify success before claiming work is fixed or passing.

Maintaining an auditable trail of build validation results is achieved by running full verification commands and confirming their output before making completion claims. This justifies your success statements in PRs and releases.

Automated verification for completion claims should not be used when you cannot execute full commands or inspect their output. The process relies entirely on reading fresh command output to confirm success before asserting work is complete.