vault-note-capturelisted

# Vault note capture The user keeps cross-session notes in `~/Vault/Notes/` (a SilverBullet space; persisted to R2; ingested into the unified graphify graph by the vault-monitor daemon). When they ask you to capture something, write a file - don't just acknowledge. ## Workflow 1. **Infer category** from the content. Create the folder if absent: - Reminder / TODO / "remind me to X" → `Notes/Reminders/` - Architectural / product decision → `Notes/Decisions/` - Reading notes / article / paper summary → `Notes/Reading/` - API / library / vendor reference → `Notes/References/` - Debugging finding → `Notes/Debugging/` - Project-specific → `Notes/Projects/<project>/` - Unclear → ask once, or default to `Notes/Misc/`. 2. **Filename**: `YYYY-MM-DD-<short-kebab-slug>.md`. Date prefix enables chronological scan; slug is 3-6 words capturing the gist. 3. **Body shape** (tight - user will edit in SilverBullet if needed): ```markdown # <Short title> <One-paragraph capture in the user's framing.> ## Why <1-2 sentences on context or motivation.> ## Links - [[ConceptOne]] - [[ConceptTwo]] - <prose ref to file paths / PRs / URLs> ``` 4. **Wikilink convention**: - `[[PascalCaseConcept]]` for things you want the unified graph to dedup across notes and code (named patterns, product names, function names that are also concepts). - File paths, snake_case symbols, PR/issue URLs → leave as prose. They namespace per-project; auto-linkin