verification-before-completion

To prevent claiming build completion without verification evidence, enforce a structured verification gate requiring fresh outputs from tests or CI checks before declaring success.

To verify CI tests before a pull request, execute a defined sequence: identify required checks, run tests, read outputs, verify results, and report explicit evidence.

You need fresh verification outputs for release readiness checks whenever claiming tests, builds, or feature delivery success to ensure traceability and prevent error-prone declarations.

Yes, you can use evidence-based verification workflows for code reviews. They guide users through identify-run-read-verify steps to ensure completion claims are grounded in fresh outputs.

Reporting completion without running a defined verification sequence bypasses the evidence gate, leading to dishonest, error-prone claims that lack traceability for CI and PR checks.