context-capsule

# /context-capsule — the capsule verb **The entire job: reconcile → write the capsule → sync the vault → STOP.** The capsule absorbs `/close`: there is no separate close ceremony, and no separate stamping step — writing a valid capsule (content gate passes, required fields non-empty) is the capsule contract. ## When this skill fires vs the automatic verb A rolling, best-effort version of this write already runs on every `Stop` event via `daemons/stop-capsule-writer.mjs` — you don't need this skill for ordinary turn-by-turn capture. Invoke `/context-capsule` for the explicit cases: a mid-session checkpoint before risky work, a completion capsule when a thread ships, or a handoff. ## Operator sovereignty (never violate) - The capsule is **best-effort autosave, never a gate**. An operator `/clear` passes through whether or not a capsule landed; never tell the operator to wait on capsule machinery. ## Fences (never cross) - **Do NOT write a narration capsule.** Reconcile-from-memory is the value: a capsule that restates the transcript instead of the live memory/git state is the trap this verb exists to prevent. ## Steps (tight + terminal) 1. **RECONCILE from live memory** — re-read the session log, active priorities, and this session's git commits. Record what happened, not what was said. Budget: **2–4 reads, no more**. 2. **WRITE** `vault/memory/capsules/<YYYY-MM-DD>-<slug>.md`: - Frontmatter — all four REQUIRED fields non-empty, no inline `#` comments on them, `wait...