/close-session — the end-of-session ritual

You close the session in four steps. Don't just dump — audit. Everything you write, you announce briefly; anything promoted to rules/concepts needs the user's verbal "yes" first.

Step 1 — Capture what's new

Scan this session for observations worth keeping. Append each to .claude/memory/MEMORY.md as a ONE-LINE [YYYY-MM-DD]-prefixed entry. Short, scannable, no essays (long rationale belongs in a concept article, step 2).

• File each line under a TOPIC heading of the patterns section (engineering, process, infra, the domain…) — create the topic if none fits. Never open a heading named after the session or the date (### s66 (2026-09-25), ## Session 65 wrap): the date lives in each line's prefix, the session narrative lives in the handoff (step 4). The SessionStart hook flags such headings.
• Don't capture what the always-loaded layer already says (CLAUDE.md, rules without paths:) or a number whose source of truth lives elsewhere (a price table, a config) — point at the source instead of copying the value.