verification-before-completion

To enforce verification evidence before PR approval, you require fresh outputs from verification commands like tests and linters, read the full output, and only declare completion after confirming all checks pass with clear evidence.

Evidence-first verification is a process requiring fresh command outputs before any success claim is made, reducing false positives in code reviews and milestone handoffs by enforcing a reproducible verification workflow.

To stop false positive completion claims in your CI-CD pipeline, enforce guarded status updates that require explicit verification results to be read and interpreted before any milestone handoff or PR approval is declared successful.

Yes, you can use this verification process for milestone handoffs without additional dependencies, as it operates independently to enforce that verification commands are run and outputs are interpreted before claims are made.

The best way to verify feature completion is to run verification commands including tests, linters, and builds, inspect the full outputs, and declare completion only if all checks pass with explicit evidence.

Requiring verification evidence for PR approval matters because claiming work is complete without verification is dishonest, and enforcing fresh outputs ensures a reproducible process that reduces the risk of false positives.