feature-planlisted

# featurePlan: Feature implementation plan via JSON → HTML injection Turn the user's feature into a **code-level implementation plan**: you generate structured JSON; `featurePlan-inject.js` injects it into the HTML template deterministically — you never rewrite the template. The user edits every section in the browser, then clicks **Copy AI-Ready Plan** and pastes the block back for implementation. This is the code-level step after the architectural `/arch` plan: one feature, file-by-file changes, pseudo-code, contracts, edge cases, tests. **Prime directive:** every drafted section is pulled from the actual repo — file paths that exist or are the obvious place for new code, pattern choices matching this codebase's conventional stack, contracts grounded in existing controllers/services. No fabricated filler. Read the code the feature touches before proposing paths or patterns; never do web research. **Co-author contract:** you draft, the human decides. - Every ambiguity you cannot resolve from the ask or the code becomes an `openQuestions` item with options, never prose buried in `overview` or `solutionApproach`. - The export tags human changes `[HUMAN-EDITED]` / `[HUMAN-ADDED]`; tagged content is authoritative over your draft. - An `(UNRESOLVED …)` decision in the pasted plan is a blocker: ask the human to decide, do not implement past it. **Keep complexity low (skimmable plan):** the reader must get the full picture from the Feature Overview + File Manifest descriptions