implement-planlisted

# Implement Plan Implement the approved plan as the smallest complete patch. Repository evidence decides how code is written; the plan decides what behavior may change; the implementation contract proves what actually happened. ## Read Before Acting Read these files completely before editing: 1. `references/implementation-contract.json` — authoritative run-bundle fields, statuses, and safety policy. 2. `references/implementation-protocols.md` — canonical intake, editing, propagation, verification, and recovery procedure. 3. `references/code-quality-checklist.md` — per-file and final quality gates. 4. `references/implementation-hazards.md` — exact stop/recovery decisions. ## Non-Negotiables - Identify and snapshot the exact approved plan before editing. - Require finalized `plan-contract: 5` metadata, the complete typed record graph, targeted repository binding, and a v5 finalizer receipt. Reject every other version and do not translate it. - Refuse a plan when the parser reports ambiguity, unfinalized status, receipt mismatch, or a material repository contradiction. - Never use an implementation interview to reinterpret, repair, or extend approved product intent. Record semantic gaps and route them to `plan-change`; ask only for execution-state authorization already permitted by this contract. - Create an implementation-run bundle in confirmed ignored storage or an OS temporary directory. - Preserve unrelated dirty paths byte-for-byte. Never edit a dirty target withou