"""Remote terminals (Windows and Linux/macOS) and the Warpgate channel. The transport classes build the scripts; a *channel* carries them (design ยง9): - WarpgateChannel (`transport: warpgate-ssh`, also the direct-ssh fallback): the server-access relay client agent-access.py --config run --target --timeout N -- The client shlex-joins argv and the target account's login shell runs it (cmd.exe on Windows); stdin is /dev/null (agent-access.py run_remote uses stdin=DEVNULL), so everything travels in argv. `relay()` is the single place that builds that call. - DirectChannel (`transport: direct-ssh`, agentd/transports/direct_ssh.py): OpenSSH over Tailscale; the script goes on stdin, so every operation (including a launch with its prompt) is one call. - os linux / darwin -> PosixWarpgateTransport: every operation is one `bash -c '