channel-setup

# Channel Setup Activate a channel for local/tmux operation, adding the `config.json` entry first when there isn't one. This mirrors what `docker-setup` does for Docker users but targets the local environment. ## Plan ### 1. Read config and detect channels **Docker check (first):** read `.claude-code-hermit/state/runtime.json` if it exists. - If `runtime_mode == "docker"`: stop and redirect — > This project is running in Docker. Channel token and pairing must happen inside the container, not on the host. > Run `/claude-code-hermit:docker-setup` — it configures channels container-side. Stop. - If `runtime.json` is missing AND `.claude-code-hermit/docker/Dockerfile.hermit` exists (Docker scaffolded but not yet booted): same redirect. - Otherwise: proceed. Read `.claude-code-hermit/config.json`. Collect all entries under `channels` that are valid objects, tracking which are disabled (`enabled: false`). **Adding an entry.** Where a branch below says *create the entry*, run (`<name>` is the lowercase channel key — `discord`, `telegram` — never the capitalized option label): ``` echo '{"channels":{"<name>":{"enabled":true}}}' | bun ${CLAUDE_PLUGIN_ROOT}/scripts/hatch-config.ts "$(pwd)" --reinit >/dev/null ``` The script fills `enabled`, `dm_channel_id: null`, `default_chat_id: null`, and `state_dir` (`.claude.local/channels/<name>`), validates the whole config, preserves every other key, and merges onto an existing entry rather than replacing it. Discard stdout — it ...