novahiz-implementlisted

# novahiz-implement: write in clean increments **Step 5 of 6** in the pipeline. You write what the task asks. Scope creep has no place here. Previous: `novahiz-analyse`. Next: `novahiz-converge`. ## Increment cycle ``` implement -> test -> verify -> commit -> next slice ``` Each slice starts from the previous one. When it lands, the system compiles and the tests pass. ## Open and close the step ``` novahiz_task action="start" id="<todo>" ... work ... novahiz_task action="done" id="<todo>" proof="<command and result>" ``` `done` on a step of kind `verify` needs proof. Missing proof keeps the step open. ## Choose the first slice - Vertical by default: it crosses layers and shows up working end to end. - Contract-first: freeze types and interfaces, then both sides advance together. - Risk-first: prove the least certain piece. ## The gate will trigger Writing code fires rules. On frontend design work, R13 requires `novahiz-humanizer`, `ui-slop-remover` and `ui-craft-rules`, and R14 requires `impeccable` (critique/audit/polish playbooks). Outside design, those skills are not required by the gate. Load design skills before writing, ahead of the refusal. ## Writing rules **Simplicity.** Ask what the simplest thing that could work looks like. Fewer lines. An abstraction must earn its complexity. Three similar lines beat a premature abstraction. Write the naive and obviously correct version, then optimize once tests prove the behavior. **Scope.** Touch only what the ta