wraplisted

# Wrap Long sessions accumulate durable facts — decisions, gotchas, root causes, config locations, task/status changes, edits discussed-but-not-made — that are easy to leave un-written. Per the **memory policy** (`procedures.md`), durable context must live in `procedures.md`, a project `context.md`, Notion, or the code — **never** in per-Claude-Code memory. `/wrap` is the end-of-session checklist that catches what didn't make it home. --- ## Step 1 — Scan the session Review this session's transcript for durable items produced or discovered. Look for: - **Decisions locked** (design / architecture / process) not yet written to Notion or the rulebook. - **Rules / conventions** the human asked to "remember." - **Gotchas, root causes, non-obvious facts** discovered (a bug's mechanism, where a config lives, a fragile invariant). - **Notion / task changes** made or agreed but not applied (status flips, `Depends On` edits, tasks to file). - **`procedures.md` / `context.md` edits** discussed but never made. - **Code fixes** identified but neither applied nor filed as a task. ## Step 2 — Classify each item by its correct home Per the memory policy, propose exactly one home per item: - **`procedures.md`** — a universal, cross-project rule. - **project `context.md`** — a per-project fact or specific. - **Notion** — decisions, task definitions, source-of-truth docs (task page / architecture page / project context). - **the code** — if it's verifiable-in-source and belongs