chat-recall-resumelisted

# Resuming work with chat-recall Goal: reconstruct the state of prior work so you can continue seamlessly. ## Default move `mcp__chat-recall__recall_smart_resume` returns a structured bundle: what was done, what's pending, files touched, budget, and current knowledge-graph facts. This is the best single call for "continue". **It REQUIRES `session_id` — there is no "latest session" default, and calling it bare is a validation error, not a lucky guess.** So resuming is always two steps unless the user handed you an id: 1. Get the id. `mcp__chat-recall__recall_recent` (`project_filter`, `since_hours`) lists candidates newest-first — the right call for a plain "continue". Use `mcp__chat-recall__recall_search` with `include_outcome: true` instead when the user described the TASK rather than the timing; the outcome line (shipped / interrupted / abandoned) tells you whether that session is even worth resuming. 2. Pass that id to `recall_smart_resume`. `recall_smart_resume` also takes no project filter. Scope the SEARCH in step 1 (`project_filter` on `recall_recent`), not the resume call. ## Cold start (new session, unclear task) - `mcp__chat-recall__recall_wake_up` — identity blurb + high-importance decisions/preferences/milestones + a knowledge-graph snapshot. Fast "who am I, what's true right now". Add a project filter to scope it. - `mcp__chat-recall__recall_project_context` — when the user is clearly working in one project and wants its full picture