verification

To verify a bug fix is complete, you must execute validation commands, review the outputs, and confirm the results before reporting the work as finished. This enforces an evidence-based validation workflow preventing unsupported completion claims.

Evidence-based validation in software engineering is a mechanism that requires fresh verification proof, such as passing tests or successful builds, before asserting that development work is complete or successful.

Running completion safety checks involves identifying the appropriate validation commands for your regressions and builds, executing them, reading the outputs, and confirming successful results before making any completion assertions.

Yes, you can use this to validate requirements, tests, and agent-produced changes before commits or pull requests. It requires executing the relevant validation commands and confirming the results before reporting success.

Reporting a bug as fixed fails without verification evidence because this workflow prevents false completion claims. It requires running validation commands and reviewing the actual outputs to confirm the fix before reporting success.

The best way to prevent unsupported completion claims is enforcing a workflow that requires identifying, running, reading, and confirming verification commands before making any status assertions about tests, builds, or bug fixes.