verification-before-completion

To verify a successful build or test run, you must execute the exact verification command fresh, capture stdout/stderr and exit code, and quote the precise results as evidence before declaring success.

Fresh verification evidence in software quality assurance is the exact stdout, stderr, and exit code captured from a newly executed command, providing direct proof that tests, builds, or lints pass before completion.

Prevent premature completion claims by enforcing a verification gate that requires running the exact test or build command fresh, capturing the output, and citing it as evidence before marking the bug fix as complete.

No, you cannot use existing test output to prove your build is ready. You must execute the verification command fresh and capture the current stdout, stderr, and exit code to directly confirm the claim with verifiable evidence.

The best way to validate that a linting task has passed is to execute the lint command fresh, capture the exact stdout/stderr and exit code, and declare success only when the fresh output directly confirms the claim.

Your verification process fails because declaring success requires fresh output as evidence. Without executing the exact command and quoting the precise stdout, stderr, and exit code, there is no verifiable proof to confirm the claim.