novahiz-planlisted

# novahiz-plan: decide the direction **Step 1 of 6** in the `novahiz-planner` pipeline. Nothing in the application changes here. The product of this step is a plan. Next: `novahiz-clarify`, then `novahiz-task`. ## When you arrive The request already has a category. No file has been touched yet. ## Record the plan in the ledger Log it where it survives context loss: ``` novahiz_task action="new" title="<the request in one sentence>" novahiz_task action="plan" todos=[...] ``` `todowrite` keeps the list visible on screen; `novahiz_task` keeps the durable record. ## What belongs in the plan - **Done**: one sentence describing the final state anyone can observe. - **Scope**: what you include, what you leave out. - **Approach**: the route you picked, plus the routes you dropped and why each one lost. - **Dependency order**: what has to exist before what. - **Splitting strategy**: vertical slices by default; freeze contracts first when several consumers share an interface; attack the riskiest unknown first when one dominates. - **Risks**: what each one costs and how you blunt it. - **Checkpoints**: where you stop to prove progress. ## Stay read-only Open the code, the manifests, the conventions already in the repo. You write nothing in this phase, not even a small fix to prepare the ground. A plan earns its keep by the rewrites it prevents. ## Order of work Walk the dependency graph from the bottom up: foundations first, then the surface. An API sketched before its sc