verify-before-complete

To prevent unverified completion claims in your CI workflow, you must require fresh verification evidence before marking any task or milestone complete. This blocks claims like "tests pass" until the latest command output confirms success.

A quality gate for code changes is a strict policy requiring verification evidence before marking task milestones complete. It prevents shipping unverified work by blocking any commit or PR until fresh command output confirms success.

You enforce running tests before pushing a commit by applying a verification-before-claim policy. This requires running a designated verification command after code changes and blocks commits or PRs until the latest output confirms success.

Yes, enforcing verification evidence before completion claims works with existing CI tests by applying to code changes, commits, PRs, and task milestones. It guides users to run verification commands and blocks claims until output confirms success.

You should require fresh evidence before claiming a task is complete to prevent unverified completion claims and maintain auditability. This guardrail ensures no claim like "it works" is made without current verification output confirming success.

Blocking completion claims without fresh verification output requires running a verification command after every code change. This strict policy means no task milestone or PR can proceed until the latest output confirms success, preventing unverified work from shipping.