agent-deck-recall

# Recall Recall is agent-deck's memory of what every session was for and what happened in it. Human intent (hints, tags) lives in the profile's state.db and survives everything; the transcript index (recall.db) is disposable and arrives in the next phases. Full design: `docs/recall.md` in the repo. ## Phase 1 (available now): hints and tags Hints are single-valued per key (setting a key again replaces it). Tags are a set. Well-known keys: `purpose`, `ticket`, `why`, `decision`, `outcome`, `note`, `parent`; any identifier-shaped key works. ### At creation (`add` and `launch`) ```bash agent-deck add . -c claude --hint purpose="fix flaky auth test" --ticket SB-412 --tag auth --tag flaky --why "3rd regression" agent-deck launch . -c claude --ticket SB-412 -m "Fix the flaky auth test" ``` - `launch` derives `purpose` from the first line of `-m` and both commands derive `parent=<parent id>` for a child; an explicit `--hint purpose=` wins. - `conductor setup <name>` records `purpose=conductor <name>`. - `--json` echoes `hints` and `tags`. ### Afterwards (`session annotate`) ```bash agent-deck session annotate <id> --decision "root cause was clock skew" --outcome worked --tag clock-skew agent-deck session annotate <id> --set-hint ticket=SB-413 --remove-tag flaky --unset why agent-deck session annotate --self --outcome worked # your own session (AGENTDECK_INSTANCE_ID) agent-deck session annotate --self --note-stdin < summary.md # free-text note, 8 KiB cap agent-...