session-handofflisted

# Session Handoff Produce a repeatable end-of-session summary so the user can start a fresh session (in Chat, Cowork, or Code) without losing continuity. The next session should be able to pick up by reading this summary alone — plus whatever files/links it points to. This is a **context-handoff artifact**, not a status report and not a retrospective. The audience is a future instance of you (or a colleague), not a client or stakeholder. The user's work is typically marketing, research, or automation — buyer personas, positioning, campaigns, SEO audits, briefs, decks, spreadsheets, scheduled tasks, connector-driven lookups. It is usually NOT software engineering. Do not assume git, code, or a dev environment. If a session genuinely did involve code (e.g. in Claude Code), fold that in using the "Key files & links" and "Automations & running state" sections below — don't force it into engineering-specific structure. ## When to invoke Only when the user asks. Trigger phrases: "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I switch", "summarize before I clear/reset". Do not invoke proactively — do not offer it unprompted, even if the conversation is long or the user mentions starting fresh. Wait to be asked. ## How to produce the summary 1. **Review the full conversation**, not just the last few turns. Handoffs miss things when they only summarize recent exchanges — pull from the whole session. 2. **Pull state from w