sendlisted

Write the follow-up packet content to a file (same rules as `/relay:spawn` — task-specific content only, GATES/REPORT FORMAT are auto-appended), then run: `${CLAUDE_PLUGIN_ROOT}/bin/relay send $session_id $packet` (Call relay via `${CLAUDE_PLUGIN_ROOT}/bin/relay` — Claude Code substitutes the plugin's absolute path — not bare `relay`, which often isn't on the Bash tool's non-interactive PATH.) This types into the SAME tab/process — same conversation context, no cold start. `relay` refuses only `busy`/`stalled` (mid-turn — injecting risks corrupting it) and `superseded` (abandoned) targets. A `reported`/idle session is sent to in place. A **`closed` or `dead`** session that still has its captured Claude conversation is **automatically resumed** and delivered the packet in one shot (full context + staged work back) — so you do NOT need `/relay:resume` first; just send. Only a closed/dead session with NO captured conversation needs a fresh `/relay:spawn`. Run `/relay:check $session_id` first if unsure of status. **Terminal.app backend note**: Terminal cannot type into a running session (no iTerm `write text` equivalent), so there `relay send` automatically closes the old window and reopens the SAME conversation via `claude --resume` in a fresh window with the packet delivered — context is fully preserved; it just costs a new window instead of reusing the tab in place. **Ownership follows the send.** Sending into an executor also **adopts** it — re-points its auto-wake to th