verification-before-completion

You can require verification before a pull request by running the change's verification command, capturing full output, and only declaring completion if the output confirms success with concrete evidence.

Evidence-based completion means you cannot declare a task, commit, or handoff complete until verification results are executed, outputs are read, failures are counted, and conclusions are drawn only when supported by the evidence.

No, if verification fails you must not declare success; instead, provide auditable evidence of the failure and resolve the issues before claiming completion for the pull request or commit.

To verify code changes before a feature handoff, run the verification command for the current change, read the results to count any failures, and only declare completion if the output confirms success with auditable evidence.

The best way to prevent false completion claims is to enforce an evidence-first workflow where commands are executed, outputs are inspected, failures are counted, and conclusions are drawn only when verification results support them.