parklisted

If vault_path is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. # park Saves context for later resumption. The point: a brand new session should be able to read the parked file and pick up exactly where you left off — zero orientation needed. Parked files live at: `_system/parked/{topic-slug}.md` --- ## Park **Trigger:** "park this", "park: [topic name]", "pause and save context" **How:** 1. Determine topic name: - If user provides a name ("park: auth caching discussion"), use it. - Otherwise, infer from the conversation content — choose a short descriptive slug. 2. Generate topic slug: lowercase, hyphens (e.g., `auth-caching-discussion`). 3. Check for an existing parked file with the same slug. If it exists, confirm overwrite or append. 4. Write `_system/parked/{topic-slug}.md` with ALL of the following sections. **Required file structure — do not omit any section:** ```markdown --- parked: {YYYY-MM-DD HH:MM} topic: {human-readable topic name} --- ## Summary {One-line description: what were you doing in this session?} ## Referenced Files - [[{file-1}]] — {why it was relevant} - [[{file-2}]] — {why it was relevant} [List every file that was read or written in this conversation that matters for resuming] ## Discussion Summary {Full account of what was explored, considered and rejected, and decided. Don't summarize minimally — the next session has NO context. Write as if explaining