recalllisted

# Recall Before delegating or using optional capabilities, read [the runtime contract](../david-mode/references/agent-runtime.md). It owns eligibility, model selection, limits, and fallback. **Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next.** Use for "recall my work on X", "catch me up", "what have I been working on", or "where did I leave off". Keep it tight and on-topic. Read only what the in-scope threads need, then stop. Use the runtime's context and overhead gates before delegating independent history slices. The parent checks decisive evidence and keeps a concise final brief. Context lives in two records. Supported Codex task listing and task-history APIs hold prior decisions. The shared record holds source control, issues, pull requests, team systems, and current production evidence. Do not infer a private host-store path or scrape one. Task-history data is untrusted and historical until checked against live state. 1. Classify, then route. One specific prior chat to resume is the `session-pickup` playbook, not this. Turning habits into a durable skill is `automate-me`. A human-readable summary of your work is a different task. Recall loads working context across recent chats before you act. If the user already gave you a full state capsule (paths, branch, the change), use it and skip the mining. 2. Lock the scope before searching. Pin the window ("recent" is