forge-verifylisted

# forge-verify Confirm a unit is truly done before it's marked complete. "Done" means the spec's checklist passes, the project builds clean, and an adversarial review finds no in-scope problems. ## Argument Text after the command selects the unit to verify (e.g. `/forge-verify unit 04`). No argument → verify the unit currently "In Progress" (or just built) per the tracker; confirm if ambiguous. ## Inputs The unit's spec at `context/specs/NN-feature-name.md` (its "Verify when done" section) and `context/architecture.md` (invariants). ## What to run ### 1. Spec checklist Go through every item in the spec's "Verify when done" section and check it explicitly, per the loop contract (`${CLAUDE_PLUGIN_ROOT}/skills/forge-build/references/loop-contract.md`): every pass **cites its external evidence** — command + exit code for mechanical items, file:line or observed output for inspectable ones — from a **fresh** run, never from memory of an earlier one. Items with no obtainable external evidence are reported `UNVERIFIED — needs human check`, never self-attested; UNVERIFIED items are listed separately in the verdict. ### 2. The unit's tests Check the spec's **Tests** section: every listed test must exist and pass. If the spec defined tests but they were never written, that is a **FAIL** — implementation isn't complete without them. Check red evidence too: the tracker's In Progress entry should carry the `red: …` line from the tests-first step — tests with no record of ever fai