verification-before-completion

You can enforce evidence-based completion by executing full verification commands, interpreting their outputs, and requiring explicit evidence of passing tests and builds before declaring success or merging a PR.

Evidence-based verification is a strict workflow that executes commands, reads outputs, and requires explicit proof of passing tests and builds before allowing status updates, PRs, or releases to be declared complete.

To stop misleading status updates, apply a step-by-step verification workflow that blocks completion claims until full CI commands have run, outputs are reviewed, and explicit passing evidence is verified.

Yes, you can use this verification workflow for both testing and release processes, as it applies to any software development workflow requiring evidence-based claims before PRs, releases, or status updates are finalized.

The best way to attach test output as evidence before a release is to run full verification commands, review the results against the output, and only state the outcome after verifying the evidence proves the claim.