herdr-pairlisted

# Herdr Pair Pair Claude and Codex in one Herdr tab. Keep the pair and its `sid` alive across tasks, accepted work cycles, and context compaction. The user can read and interject in either pane. Keep protocol headers and identifiers literal. ## Preconditions Set `SKILL_DIR` to this skill directory and `PAIR_SCRIPT="$SKILL_DIR/scripts/herdr-pair.mjs"`. Always use that absolute path; the project cwd is unrelated to the installed skill path. Require `herdr` with the agent automation commands (`herdr agent start`, `herdr agent prompt`) and `trash` on `PATH`, `HERDR_ENV=1`, and an exact caller pane ID. If any command is missing, stop and tell the user to install or start (or update) Herdr. Set `SELF_AGENT` to the current agent (`claude` or `codex`) and `SELF_PANE` to the caller's exact live pane. Treat `HERDR_PANE_ID` only as a hint: inspect it with `herdr pane get`, and reject it if its agent does not equal `SELF_AGENT`. When the inherited ID is missing or stale, use `herdr agent list` and exact current-turn transcript evidence to identify the caller; never infer it only from cwd, focus, direction, labels, or pane order. Stop on ambiguity. Confirm the final binding: ```bash herdr pane get "$SELF_PANE" ``` Never use `herdr pane current` without an explicit `--pane`; it may resolve by UI focus and return a different workspace. If the confirmed caller pane exposes `agent_session.value`, set `SELF_SESSION` to that caller-owned value. Build one argument vector and use it for e