verification-before-completion

Verification requires running the full build command fresh, reading the complete output, and confirming the result matches your claim. Document the command and output as evidence before marking completion; stale or partial results don't count as verified.

Fresh verification catches environment changes, dependency shifts, and code modifications that cached or partial results miss. Running the full test suite end-to-end produces current evidence that your claim is actually valid.

Identify the verification command for your deployment target, run it completely, read all output, confirm it matches your expected state, then cite the specific output as evidence. Never claim deployment success without fresh verification output.

No. Verification before completion requires running full fresh tests, reading complete results, and confirming output matches the fix claim. Partial or stale test runs don't provide the evidence needed to claim completion.

Capture the full output from your verification command—tests, linting, builds, deployments—and explicitly cite it when claiming completion. This evidence trail ensures every completion claim in your CI/CD pipeline is backed by fresh, verifiable results.

Valid evidence is output from running your full verification suite after the change: passing tests, successful builds, clean linting reports. Include the specific command run and complete output. Anything incomplete or cached doesn't qualify as evidence.