channel-setup

# Channel Setup Activate a channel, adding the `config.json` entry first when there isn't one. Local/tmux pairing is this skill's own flow; a Docker hermit is routed by the check below. ## Plan ### 1. Read config and detect channels **Runtime routing (first):** evaluate in this order. 1. **Inside the container.** Run `[ -f /.dockerenv ] || [ -f /run/.containerenv ] && echo container || echo host`. If `container`: read `.claude-code-hermit/config.json`. For each enabled channel object, resolve `state_dir` as step 4 does (config `state_dir`, default `.claude.local/channels/<channel>`; if relative, make it absolute against the project root) and print that absolute path literally. Print and stop: > DM the bot for a code, then run `/claude-code-hermit:channel-setup` from a normal host session at the project root. If no enabled channel, print only the host-run sentence and stop. No `AskUserQuestion` on this path. 2. **No compose file.** If `docker-compose.hermit.yml` is absent at the project root, continue with the local/tmux flow below. 3. **Live tmux hermit.** Run `bun ${CLAUDE_PLUGIN_ROOT}/scripts/docker-preflight.ts "$(pwd)"`. If its `liveOwner` is non-null, a host tmux hermit owns this project despite the compose file: continue with the local/tmux flow below. 4. **Compose present.** Run `docker compose -f docker-compose.hermit.yml ps --status running --format '{{.Service}}'`. Non-zero exit → print its output, stop. If `hermit` is absent from the output: after cha...