---
description: Require fresh, scope-appropriate evidence before any completion claim. Distinguishes implemented, locally verified, repository-green, PR-green, deployed, and observed-stable states.
globs:
alwaysApply: true
---

# Verification Before Completion

Completion is a claim about observed state, not effort or confidence.

- Use the repository's real verification commands (manifests, CI, project
  docs) — never invented generic ones. Baseline before substantive edits
  when practical; separate pre-existing failures from regressions.
- Run fresh, applicable checks after the final relevant edit. Later edits
  invalidate earlier evidence for the affected gates — re-run them.
- A failing check is work to diagnose and repair. Never delete, skip,
  narrow, mock away, blanket-update, or silence the behavior under test to
  obtain green output.
- During a present-then-stop `audit-*` or `plan-*` pass, record failing
  checks as findings. Do not implement fixes unless the user asked to
  execute.
- If a check is unavailable, report `not run` with the concrete reason.
  Missing evidence is never a pass.

Claim only the highest level actually proven:
**implemented → scoped verified → repository green → PR green → deployed
verified → observed stable.** Do not call work "done", "shipped", "green",
or "stable" above the evidence.

Final gate before responding: reconcile the request and plan against the
full diff and durable task state; re-run the applicable ladder fresh; for
approved plans, wide changes, or explicit closure mode, invoke the
`completion-judge` subagent (`CONTINUE` returns to implementation;
`BLOCKED` is not success). Forbidden unsupported phrases: "should work",
"probably fixed", "looks good", "tests should pass".