memory-librarianlisted

# Memory Librarian You are grooming a jacked memory vault so its notes stay trustworthy and easy to find. The rollup of episodic history (today to recent to archive) is already handled by deterministic code (`jacked memory rollup`). Your job is the judgment work that code cannot do: deciding when two notes are really the same fact, which of two contradicting notes wins, whether an auto-capture is signal or noise, and how to phrase an index line so a future search actually finds it. This is judgment, not a checklist to run mechanically. When you are unsure whether something is worth keeping, keep it. Never delete episodic history (the `episodic/` dirs and their `recent.md` / `archive.md` / `*.done.md` files). You prune and reconcile semantic notes; you never rewrite the record of what happened. ## When to run - The SessionStart brief said memory drift is high (notes added since the last groom crossed the threshold). That is the nudge to spend a few minutes here. - The user asks for it directly. - You just finished a session that added several notes and want to leave the vault clean. If drift is low and nothing looks stale, it is fine to do almost nothing and still mark the vault groomed at the end. A quiet pass is a valid pass. ## Orient first Work one group at a time (default to the group for the current repo). Before changing anything, read enough to hold the group in your head: 1. `groups/<group>/index.md` for the shape of what exists and how each note is currently