direct-handofflisted

# Direct Handoff Hand off the current task to a fresh Claude session in a terminal-multiplexer sidecar pane. The receiving session gets full context through updated durable docs + task list + a minimal ephemeral handoff for anything that doesn't have a permanent home. ## Why Direct Handoff (Not /clear or /compact) Direct handoff creates a **new session alongside the old one**. The old session stays open and accessible — scroll up, re-read context, copy information. This is better than `/clear` (destroys context) or `/compact` (lossy compression) because: - **Old context is preserved intact** while the new session ramps up - **Graceful transition** — verify the new session is running smoothly before abandoning the old one - **Rollback** — if the handoff goes wrong, the old session is still there - **Session sequence** — named sessions (e.g., `feature-x`, `feature-x-1`, `feature-x-2`) form a clear lineage The old session can be closed once the new one is confirmed working. ## Core Principle: Update Existing Docs, Don't Create New Ones The handoff doc is a **last resort**, not the primary mechanism. Before creating any handoff content: 1. **Update memory files** — decisions, patterns, team roles belong in `memory/` 2. **Update project docs** — research findings, specs, architecture docs belong in their permanent homes 3. **Update specs** — requirement changes discovered during the session belong in the spec files 4. **Task list is the coordination backbone** — the receiv