verification-before-completion

To verify tests pass before claiming completion, you must run the verification command fully, parse the results, and report the status with fresh evidence. This prevents premature success claims by enforcing evidence-based validation across CI and PRs.

Evidence-based completion is a workflow that requires fresh verification before asserting work is fixed or passing. It prevents premature status updates by demanding that you run tests, linters, or builds and attach the resulting evidence to your status report.

To prevent premature status updates during CI or PR handoffs, enforce a structured verification workflow that identifies the verification command, runs it fully, and reports status with fresh evidence before any success is claimed.

Yes, you can use structured verification workflows for any software task involving claiming tests pass, builds succeed, or bugs are fixed. It applies broadly across CI, PRs, and handoffs to ensure evidence-based completion.

The best way to enforce proof of passing tests before a PR merge is to run the verification commands and attach fresh evidence to the status report. This structured workflow ensures no success claims are made without validated results.

Claiming a bug is fixed without evidence causes handoff problems because it skips verification, leading to premature status updates. Requiring fresh evidence from tests or builds ensures claims are validated and prevents downstream failures.