session-noteslisted

# 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 `references/config-schema.md`. Tool-routing (MCP for writes, CLI for reads/search) in `references/tool-routing.md`. Frontmatter template in `assets/session-template.md`. ## When to Trigger - After completing a feature / PR / fix - After significant research session - Manually via `/mnemo:session` - Do NOT trigger for trivial tasks (typo fix, one-liner) ## Workflow ### Step 1: Summarize Current Session Analyze the conversation: what was done, key decisions, commits/PRs created, findings. Derive a **planned filename**: `{session_prefix}{YYYY-MM-DD} {short descriptive topic}`. Topic should be specific enough to disambiguate from other sessions the same day (include PR number, Linear ticket, branch name, or primary keyword). **Naming:** the topic must NOT contain `#`, `.`, or `/` — they break wikilinks (`#`→heading anchor) or the CLI (`.`→truncation). Write `PR 387`, not `PR #387`. See `references/tool-routing.md` (naming rules). ### Step 2: Duplicate Check (two-level, parallel) **Run Level 1 and Level 2 in parallel — single assistant message with two Bash tool uses.** ~185ms total instead of ~370ms sequential. **Level 1 — exact filename:** ```bash obsidian read file="{planned-filena