novahiz-initlisted

# novahiz-init One entry point to bring Novahiz into the current project: scaffold first, then deepen with an agent read. ## When to run - `/novahiz init` or `novahiz init` in the project root - A new repo needs docs + `project-memory/` - Docs or memory are missing after a clone Do **not** use this to install Novahiz on the machine. That stays `novahiz setup` / `install.mjs`. ## Pipeline ``` 1. CLI scaffold novahiz init [--dry-run] [--docs-only|--memory-only] 2. Deep read novahiz-analyse on the real code 3. Fill docs novahiz-docs templates already created by CLI 4. Seed memory memory_write a baseline slot from findings 5. Cleanup review confirm list, then novahiz init --apply --json ``` ### 1. Scaffold (CLI, deterministic) From the project root: ``` novahiz init --dry-run --json ``` Review the plan, then run without `--dry-run` unless the user only wanted a preview. Flags: | Flag | Effect | |---|---| | `--dry-run` | Print steps and cleanup candidates, write nothing | | `--docs-only` | Only `novahiz-docs/` | | `--memory-only` | Only `project-memory/` | | `--no-seed` | Create memory root without the baseline slot | | `--apply` | Delete the listed cleanup candidates (never without review) | | `--json` | Machine-readable result | The CLI creates: - `project-memory/index.json` + `slots/` (plus one baseline slot unless `--no-seed`) - `novahiz-docs/{ARCHITECTURE,CONVENTIONS,DECISIONS,STANDARDS}.md` from the `novahiz-docs` templates when the fol