verification-before-completion

Verifying task completion with fresh command output requires running explicit verification commands to validate passing status claims. This replaces stale output with concrete command results to ensure accuracy before merging.

CI/CD reports tests passing when stale output masks failures because success claims lack fresh command evidence. Validating assertions with current execution context confirms actual test status before declaring completion.

Validating test passing status claims requires running exact verification commands to generate fresh execution evidence. This confirms specific assertions about fixes using current command output rather than intuition or stale results.

Preventing false completion claims before a merge requires validating success assertions with explicit verification commands and current execution context. This evidence-based approach ensures accuracy by replacing stale output with fresh results.

Explicit verification commands for quality assurance are needed when an agent is about to make a success claim before a PR or merge. This ensures assertions like tests passing are backed by fresh command output.