capturelisted

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. # capture Routes user-entered data to the right vault destinations. One capture can produce multiple entries — one per destination. Nothing is silently dropped. ## 📋 Before You Start Read at session start: - `_system/config/workspace.yaml` — user identity, role, and timezone - `_system/config/projects.yaml` — project names, aliases - `_system/config/people.yaml` — person names, aliases, relationship tiers - `_system/config/tags.yaml` — tagging rules --- ## 🔀 Routing Logic When the user says "capture: [text]", decompose the input into its components and route each one: | Content type | Destination | |-------------|-------------| | Recognition or praise about a person | `People/{person-slug}.md` → Recognition section | | Observation about a person (strength, growth area) | `People/{person-slug}.md` → Observations section | | Project update, decision, blocker, risk | `Projects/{project-slug}.md` → Timeline section | | Task or action item | `Projects/{project-slug}.md` or daily note (if no project) | | Your own contribution | `Journal/contributions-{YYYY-MM-DD}.md` (Monday date) | | Personal note unrelated to projects/people | Daily note or user specifies | | Ambiguous destination | Review queue (`ReviewQueue/review-work.md` or `review-people.md`) | **Every relevant destination gets its own entry.** If the same capture maps to thre