wolfpack-tailnet-controllisted

# Wolfpack Session Control Use the canonical CLI. Do not discover or reconstruct browser/private HTTP flows. Wolfpack uses its ordinary global API auth policy and adds no inter-session authorization layer. ## Fast path A **top-level** project session: ```bash wolfpack session create <project> --harness <pi|claude|codex|gemini|cursor> --prompt '<instruction>' --json ``` A same-harness **child** of the current agent: ```bash wolfpack agent spawn <project> --plan .plans/000-task.md --notify-parent --json ``` `wolfpack session open` is only a deprecated child-spawn alias. Never use it for a top-level request. Both creation commands perform one server-owned request and pass startup instructions without inheriting parent transcript/context. Prefer `--plan <file>` for plan work: Wolfpack generates the compact handoff prompt and verifies the file exists without copying plan contents into the parent transcript. Use `--prompt-file <file>` for long bespoke instructions. Use raw `--prompt` only for one short prompt sentence. Do NOT paste repository policy, architecture context, or full plans into the launch command. ## Structured inspection and control ```bash wolfpack list --json wolfpack session status <session-or-id> --json wolfpack session read <session-or-id> --json wolfpack session send <session-or-id> '<text>' --json wolfpack session wait <session-or-id> '<text>' --json ``` Treat session selectors as opaque handles. Prefer the stable `sessionId` returned by create/spawn