alivecreate-walnut

# Create Scaffold a new walnut — any type, any ALIVE domain. Understand it first, map where its context lives, then scaffold. Optionally bring in existing content (Step 7 — only if the human has files to migrate). Not a setup wizard (that's `world/setup.md` — first-time only). Not opening an existing walnut (that's `alive:load-context`). --- ## Template Locations The squirrel MUST read these templates before writing — not reconstruct from memory. Templates live relative to the plugin install path. ``` templates/walnut/key.md → _kernel/key.md templates/walnut/key-codebase.md → _kernel/key.md (codebase variant, Step 2b) templates/walnut/log.md → _kernel/log.md templates/walnut/insights.md → _kernel/insights.md ``` ### Placeholders **Used in `key.md` and `key-codebase.md`:** | Placeholder | Source | |------------|--------| | `{{type}}` | Step 1 selection | | `{{goal}}` | Extracted from Step 2 free text | | `{{name}}` | Kebab-case slug derived from Step 2 | | `{{date}}` | Current ISO date (YYYY-MM-DD) | | `{{description}}` | The human's free text from Step 2, lightly cleaned | **Additional placeholders in `key-codebase.md` (Step 2b only):** | Placeholder | Source | |------------|--------| | `{{repo}}` | Repository URL from Step 2b | | `{{local_path}}` | Local clone path from Step 2b | | `{{github_account}}` | GitHub account or org from Step 2b | | `{{stack}}` | Tech stack summary from Step 2b | | `{{branch}}` | Default branch name from Ste...