experience-capturelisted

# Experience capture Turn what this session produced into durable, reusable knowledge — but only what was actually proven. ## Gate first Capture **only after a green verify** (tests/build/checks passed, or a concrete verified before/after). If nothing was verified, or nothing reusable emerged, do nothing and say so. Never record unverified guesses. ## What counts as reusable A learning worth filing generalizes beyond this one repo: a reusable **pattern**, a **gotcha** (trap + how to avoid), a **verifier** recipe (how to check a stack), an **environment** recipe (how to run/observe a stack), or a **methodology** insight → `Wiki/experience/`. Volatile, single-repo facts (a path, current bug state, a queued task) go to that project's per-project memory — not the wiki. If something valuable emerged but isn't verified yet (an open question, a correction, in-progress reasoning), it belongs in `Wiki/journal/sessions/`, not experience. The **librarian** routes per `WIKI_PROTOCOL.md` (experience / knowledge / journal / adr / guardrails). ## Procedure 1. Briefly list the candidate learnings you see in the session and which look reusable vs project-specific. 2. **Dedupe gate (before any write):** for each candidate, run the `knowledge-recall` MCP's `search_notes` first. If an existing page already covers the topic, the instruction to the librarian is **extend that page**, not create a new one — pass the hit paths along. Only genuinely uncovered learnings become ne