handofflisted

# Session Handoff The user's context window is filling up (typically 40-50%). The current task is NOT finished — analysis is done but implementation remains. Create a handoff document that enables a fresh session to continue without re-exploration. ## Create `handoff.md` in the project root. ### Document structure: #### Background 2-3 sentences: What is the task? What is the goal? No history, no conversation recap — just the objective. #### Already Done What was already implemented in THIS session or earlier. Include concrete code references (file, method, pattern). This serves as a **few-shot example** for the remaining work — the next session will use it to understand the expected solution style. #### TODO For each remaining fix/change: 1. **Title** — one-line description 2. **File and method** — exact location with line numbers 3. **Current code** — the actual snippet that needs changing 4. **Problem** — why it's wrong (one sentence) 5. **Proposed fix** — concrete code or pseudocode 6. **Complexity** — Very low / Low / Medium / High 7. **Risk** — None / Performance / Breaking change / etc. Be specific. Vague TODOs waste context in the next session. #### Key Files to Read Table format: | File | Why | |------|-----| Each entry: file path + one sentence explaining what the next session needs from this file. Only include files that are NECESSARY for the remaining work. Not everything that was read — only what matters. #### Architecture Context If the task requ