sidekick-golisted

Get a **sidekick**: a dedicated helper agent that lives in its own pane for as long as you need it, so you can go back and forth with the *same* agent — review, fix, re-review — without it forgetting round one by round three. That persistence is the whole point: a fresh subagent (Agent/Task tool) starts cold every call and has to be re-briefed each time; a sidekick remembers. This skill only works **inside a supported multiplexer session** (herdr or zellij; the transport is selected automatically, herdr by default). If no multiplexer session is active, stop and tell the user to start herdr (or zellij) first. You (the caller) don't launch anything for yourself — you're already running in a live pane. `dispatch.mjs` finds that pane, opens the sidekick's pane next to it, and wires messaging between the two via the shared bus (the same mechanism `launch-team` uses for its teammates). ## Step 1 — Decide the role and write the brief Pick a role for the sidekick (e.g. "Code Reviewer", "Second Opinion", "Investigator"). Write a **brief**: a self-contained description of its first task. Save it to the OS temp directory (not the workspace) and capture its **absolute path**. - Reference existing artifacts (diffs, plans, issues) by path/URL instead of pasting them. - Redact secrets. Done when: the brief is saved, its absolute path is captured, and a role is chosen. ## Step 2 — Dispatch Run the dispatcher using its **absolute path** — do NOT `cd` into the skill directory first. Al