verification-contractlisted

# Verification Contract (internal) Single owner of the delivery finish line. Planning freezes it; executors may strengthen coverage but cannot move it; review checks the same bytes. ## Artifact Every new feature/fix carries `ACCEPTANCE.md` beside its SPEC. Copy the matching repository template. Required parts: `Status: frozen`; one stable ID per SPEC criterion; `Required outcome`; named `Validator`; literal quality floor; project commands. Prefer commands, otherwise use `read-verified: <evidence>` or `manual: <exact observation>`. Unlabelled prose is invalid. A planned test may name its future project runner; it cannot substitute a narrower runner later. **Validator stability.** A validator must never gate on a surface other workflow actors mutate — the branch diff as a whole, the session log, progress entries, review ledgers, or forge state — because any out-of-unit commit (a session-log append, another unit's fold) then re-fails a frozen criterion on a finished unit and re-opens its review loop. Grep the unit's own files and outputs; a diff-based validator enumerates the unit's paths or excludes the workflow-mutated surfaces explicitly (docs/LOGS.md, the unit's own docs directory, harness/toolstate). ## Freeze and receipt At first execution run `git hash-object <unit>/ACCEPTANCE.md` and append to the unit progress file: ```text ## Acceptance receipt v1 - Manifest: <path> · Blob: <sha> · Status: frozen · Verified: <date> ``` Before every phase and final review, recom