Vault Close

---
name: vault-close
description: Close a working session the NeXgen way, distilling durable outcomes into the KnowledgeVault and verifying they landed. Use at the end of a work session or when the user asks to wrap up.
---

# Close the session

Any text after the command is an optional hint about what mattered most in
the session.

1. Distill the session into durable outcomes only, following the vault
   hygiene rules in AGENTS.md: current state, decisions taken, verified
   commands, rollback notes, open risks. No transcripts, no raw logs, no
   play-by-play history.
2. Write through the `vault-library` MCP: prefer updating the existing
   canonical note on the topic (`update_section` with its per-section hash
   when the change fits one heading, `update_note` with `expected_hash` for
   whole-note rewrites, or `append_note` for additive updates). Create a
   new note only for a
   genuinely new stable topic, and then add an inbound pointer to it in
   `00-START-HERE.md` so it stays discoverable. In Local-Only mode (no
   remote, no MCP) there is no `vault-library` to write through: edit the
   Markdown note directly and commit it with plain `git` instead — that is
   the correct and only path there, not a fallback
   (`03-INFRA/vault-write-architecture.md`).
3. If the session touched infra files (scripts, manifests, instructions),
   publish them with `vault-push`; notes written through `vault-library` are
   already committed.
4. Verify the writes landed (read the note back or check
   `recent_activity`), then report what was saved as one short list.
5. If `agent-doctor` or git reports any quarantine branch (`quarantine/*`),
   inspect its diff with `git diff main..<branch>`, reconcile the intended
   changes into canonical files, publish with `vault-push`, and remove the
   quarantine branch with `git branch -D <branch>`.

In Cloud-Server mode, if the `vault-library` MCP is genuinely unreachable,
say so and stop: durable facts must not be persisted anywhere else in the
meantime (report the outage, do not fall back to raw git). In Local-Only
mode there is no server to be unreachable — the vault is a local folder;
write and commit it directly as in step 2.