sw-loadlisted

# Session Watcher Load Handoff Restore a previous session's handoff package into context so work can resume. ## Steps 0. **Resolve the token** — check these sources in order: - Skill `args` (if invoked with a token directly). - The user's message (e.g. `handoff：some-token-here`). - System-reminder containing `[Session Watcher] Handoff available (token: <token>, ...)` — extract the token from that line. 1. **Load the handoff via MCP `load_handoff` tool:** - Token known (single): call `load_handoff` with `load_token` → proceed directly. - Multiple tokens in system-reminder: list them with age/task preview, ask the user which to load. - Query search: call `load_handoff` with `query` → present results, user picks. - Auto-match: call `load_handoff` with no args → present what was found, user confirms before proceeding. Only the token-known path skips user confirmation — query and auto-match always require the user to confirm which handoff to load. If `found: false` → inform user the token is expired/invalid, ask for direction. Fallback (MCP unavailable or returns error): resolve the server URL from session-start additionalContext (`Session Watcher server: http://...`) or latest state file in `~/.session-watcher/`, then use `curl -s '<url>/api/handoff/load?load_token=<token>'`. 3. **Read kept paths** — see [`PATHS.md`](PATHS.md) for resolution and read-strategy rules. 4. **Load skills** — if `skills_to_keep` present, invoke each via the Skill t