verification-before-completion

To prevent false completion claims, require fresh verification evidence by running tests and lint, then attaching the logs as documented output before claiming completion.

Evidence-driven verification identifies the verification command, executes it fully, reads the output, and confirms it supports the claimed state across pre-commit, pre-PR, and release workflows.

Enforce a verification process by identifying the build or test command, running it fully, reading and validating the results, and reporting the outcome with documented evidence.

Yes, it applies standard lint and test commands to generate verifiable success, requiring you to run the full verification command and attach resulting evidence before completion.

The best way to document quality-assurance evidence is to execute verification commands fully during release workflows and attach the resulting logs as documented outputs to confirm verifiable success.

You need to run verification commands fully because evidence-first validation requires reading and validating the actual output to prevent false completion claims and ensure verifiable success.