verification-before-completion

To prevent premature completion claims, you must run the full verification command and read its complete output to confirm the result against your claim before stating the work is done. This enforces an evidence-first workflow for releases and commits.

Evidence-first verification is a workflow mechanism that requires running the relevant command and inspecting actual output before making any success claims during testing, code review, or bug fixes, ensuring status updates are supported by concrete evidence.

To require fresh verification evidence before a pull request or merge, enforce a rule to run the full verification command and read the complete output, confirming the actual result against the work claim before proceeding.

Yes, this verification workflow applies to bug fixes, builds, testing, commits, and pull requests. It mandates running the verification command and confirming the actual output against the claim before any success statement is made.

You need to run verification commands before claiming work is fixed whenever you are preparing for a release, commit, merge, or status update. It ensures audit-friendly validation by confirming actual command output rather than relying on assumptions.