session-notes

# mnemo:session — Session Notes to Obsidian Create a human-readable session summary note in Obsidian after significant work. ## Prerequisites & config Obsidian must be open. Config at `~/.mnemo/config.json` — reads `vault`, `taxonomy.session`, `links_section`, `handoff_note`. Schema in `${CLAUDE_PLUGIN_ROOT}/references/config-schema.md`. Tool-routing (MCP for writes, CLI for reads/search) in `${CLAUDE_PLUGIN_ROOT}/references/tool-routing.md`. Frontmatter template in `${CLAUDE_PLUGIN_ROOT}/assets/session-template.md`. ## When to Trigger - After completing a feature / PR / fix - After significant research session - Manually via `/mn:session` - Do NOT trigger for trivial tasks (typo fix, one-liner). Research / exploration / personal-curiosity sessions are **NOT** trivial — they get a note even with zero code. When unsure, create: a session note is cheap, a lost session is not. ## Workflow ### Step 1: Summarize Current Session **Mid-task checkpoint vs end-of-session note.** If this is a mid-task checkpoint (a long run risks compaction and you're saving progress, not wrapping up) **and** a note for *this same session* already exists — match by the `session_id` you'd write in frontmatter (or the filename derived earlier this session) — **update that note in place** (`mcp__obsidian__str_replace` to refresh the summary and append new progress) plus refresh the handoff (Step 5). Do **not** create a second note for the same session — that fragments the record. Only a genuinely...