captain-capturelisted

# Captain capture A decision was just accepted in conversation. Persist it — this is the moment that makes the Captain the one who "remembers everything". ## Steps 1. Determine: decision title, domain(s), impact (high/medium/low), which existing entities it touches, and whether it supersedes a previous decision (check `tsubasa query "<topic>"` first). **Also check `tsubasa goal list`** — every plan/design must state, in one line, how it aligns or conflicts with each relevant open goal ("supports goal-decommission-legacy-sso" / "⚠ conflicts with goal-x because…"). Link supporting work with a `--relation <adr>:works_toward:<goal-id>`. 2. **Validation gate** — one line, before writing anything: `Saving: adr-<slug>, links to <entities>[, supersedes <old>]. OK?` If it supersedes something recent or load-bearing, ask the one question that captures the WHY (e.g. "that ADR chose Kafka for ordering — has that requirement changed?") and put the answer in the event body. 3. On confirmation: - Draft the ADR at `docs/adr/adr-<slug>.md` (title, status: accepted, date, context, decision, consequences — cite prior incidents/ADRs from the graph). - `tsubasa event add --type decision --title "..." --impact <i> --domains <d> \ --ref adr:adr-<slug> [--supersedes <old-entity-id>] \ --entity adr-<slug>:adr:"<title>":"<one-line>" --body "..."` 4. Tell the user the branch convention: include `adr-<slug>` in the branch or PR name so the w