dispatch-panelisted

# dispatch-pane Delegate a scoped task to a sibling pane and stay watching until it finishes — then report once, with the result already verified. ## When to use - The user explicitly asks for collab / fan-out to another pane. - The current pane is one agent (you) and the target is another (codex, claude, etc.) hosting a separate session. - The task has a definable end state: a commit, a `[xxx done]` sentinel, an artifact file, or an idle pane. Do NOT use for: trivial one-shot inputs to a peer (just `pharos send` directly), or for foreground Bash commands you can run yourself. ## Prerequisite Every command in this skill talks to the pharos socket. **The Pharos app must be running.** If anything errors with `cannot connect to Pharos`, surface that to the user — don't retry blindly. Quick health check: ```bash pharos identify # returns active workspace + focusedPane on success ``` ## Anchor on self workspace Most pharos pane commands (`list-panes`, `send`, `send-key`, `read-screen`, `wait`) default to the **active workspace**. The user can switch workspaces at any time — if you rely on the default, your sibling lookup silently retargets the user's new ws and fails with `pane not found`. Anchor every pane operation to the dispatcher's own ws via `$PHAROS_WORKSPACE_ID` (set at pty spawn, stable for the dispatcher's lifetime). Guard once at entry: ```bash : "${PHAROS_WORKSPACE_ID:?dispatch-pane must run inside a pharos pane}" : "${PHAROS_PANE_ID:?dispatch-pane must ru