fix: finalize channels rename cleanup

docs/gateway/configuration.md

@@ -1148,7 +1148,7 @@ See [Messages](/concepts/messages) for queueing, sessions, and streaming context
 ```
 
 `responsePrefix` is applied to **all outbound replies** (tool summaries, block
-streaming, final replies) across providers unless already present.
+streaming, final replies) across channels unless already present.
 
 If `messages.responsePrefix` is unset, no prefix is applied by default.
 Set it to `"auto"` to derive `[{identity.name}]` for the routed agent (when set).
@@ -1160,7 +1160,7 @@ WhatsApp inbound prefix is configured via `channels.whatsapp.messagePrefix` (dep
 agent has `identity.name` set.
 
 `ackReaction` sends a best-effort emoji reaction to acknowledge inbound messages
-on providers that support reactions (Slack/Discord/Telegram). Defaults to the
+on channels that support reactions (Slack/Discord/Telegram). Defaults to the
 active agent’s `identity.emoji` when set, otherwise `"👀"`. Set it to `""` to disable.
 
 `ackReactionScope` controls when reactions fire:

docs/gateway/doctor.md

@@ -69,7 +69,7 @@ cat ~/.clawdbot/clawdbot.json
 - Sandbox image repair when sandboxing is enabled.
 - Legacy service migration and extra gateway detection.
 - Gateway runtime checks (service installed but not running; cached launchd label).
-- Provider status warnings (probed from the running gateway).
+- Channel status warnings (probed from the running gateway).
 - Supervisor config audit (launchd/systemd/schtasks) with optional repair.
 - Gateway runtime best-practice checks (Node vs Bun, version-manager paths).
 - Gateway port collision diagnostics (default `18789`).
@@ -209,8 +209,8 @@ creation in automation.
 Doctor runs a health check and offers to restart the gateway when it looks
 unhealthy.
 
-### 14) Provider status warnings
-If the gateway is healthy, doctor runs a provider status probe and reports
+### 14) Channel status warnings
+If the gateway is healthy, doctor runs a channel status probe and reports
 warnings with suggested fixes.
 
 ### 15) Supervisor config audit + repair
@@ -234,7 +234,7 @@ running, SSH tunnel).
 
 ### 17) Gateway runtime best practices
 Doctor warns when the gateway service runs on Bun or a version-managed Node path
-(`nvm`, `fnm`, `volta`, `asdf`, etc.). WhatsApp + Telegram providers require Node,
+(`nvm`, `fnm`, `volta`, `asdf`, etc.). WhatsApp + Telegram channels require Node,
 and version-manager paths can break after upgrades because the daemon does not
 load your shell init. Doctor offers to migrate to a system Node install when
 available (Homebrew/apt/choco).

docs/gateway/logging.md

@@ -101,7 +101,7 @@ Behavior:
 - **Subsystem prefixes** on every line (e.g. `[gateway]`, `[canvas]`, `[tailscale]`)
 - **Subsystem colors** (stable per subsystem) plus level coloring
 - **Color when output is a TTY or the environment looks like a rich terminal** (`TERM`/`COLORTERM`/`TERM_PROGRAM`), respects `NO_COLOR`
-- **Shortened subsystem prefixes**: drops leading `gateway/` + `providers/`, keeps last 2 segments (e.g. `whatsapp/outbound`)
+- **Shortened subsystem prefixes**: drops leading `gateway/` + `channels/`, keeps last 2 segments (e.g. `whatsapp/outbound`)
 - **Sub-loggers by subsystem** (auto prefix + structured field `{ subsystem }`)
 - **`logRaw()`** for QR/UX output (no prefix, no formatting)
 - **Console styles** (e.g. `pretty | compact | json`)

docs/platforms/mac/health.md

@@ -5,7 +5,7 @@ read_when:
 ---
 # Health Checks on macOS
 
-How to see whether the linked provider is healthy from the menu bar app.
+How to see whether the linked channel is healthy from the menu bar app.
 
 ## Menu bar
 - Status dot now reflects Baileys health:
@@ -18,7 +18,7 @@ How to see whether the linked provider is healthy from the menu bar app.
 ## Settings
 - General tab gains a Health card showing: linked auth age, session-store path/count, last check time, last error/status code, and buttons for Run Health Check / Reveal Logs.
 - Uses a cached snapshot so the UI loads instantly and falls back gracefully when offline.
-- **Connections tab** surfaces provider status + controls for WhatsApp/Telegram (login QR, logout, probe, last disconnect/error).
+- **Connections tab** surfaces channel status + controls for WhatsApp/Telegram (login QR, logout, probe, last disconnect/error).
 
 ## How the probe works
 - App runs `clawdbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages.

docs/providers/index.md

@@ -9,6 +9,8 @@ read_when:
 Clawdbot can use many LLM providers. Pick a provider, authenticate, then set the
 default model as `provider/model`.
 
+Looking for chat channel docs (WhatsApp/Telegram/Discord/Slack/etc.)? See [Channels](/channels).
+
 ## Quick start
 
 1) Authenticate with the provider (usually via `clawdbot onboard`).

docs/start/faq.md

@@ -1428,15 +1428,15 @@ Notes:
 
 Block streaming only sends **completed text blocks**. Common reasons you see a single message:
 - `agents.defaults.blockStreamingDefault` is still `"off"`.
-- `telegram.blockStreaming` is set to `false`.
-- `telegram.streamMode` is `partial` or `block` **and draft streaming is active**
+- `channels.telegram.blockStreaming` is set to `false`.
+- `channels.telegram.streamMode` is `partial` or `block` **and draft streaming is active**
   (private chat + topics). Draft streaming disables block streaming in that case.
 - Your `minChars` / coalesce settings are too high, so chunks get merged.
 - The model emits one large text block (no mid‑reply flush points).
 
 Fix checklist:
 1) Put block streaming settings under `agents.defaults`, not the root.
-2) Set `telegram.streamMode: "off"` if you want real multi‑message block replies.
+2) Set `channels.telegram.streamMode: "off"` if you want real multi‑message block replies.
 3) Use smaller chunk/coalesce thresholds while debugging.
 
 See [Streaming](/concepts/streaming).
@@ -1444,17 +1444,17 @@ See [Streaming](/concepts/streaming).
 ### Discord doesn’t reply in my server even with `requireMention: false`. Why?
 
 `requireMention` only controls mention‑gating **after** the channel passes allowlists.
-By default `discord.groupPolicy` is **allowlist**, so guild channels must be explicitly enabled.
+By default `channels.discord.groupPolicy` is **allowlist**, so guild channels must be explicitly enabled.
 
 Fix checklist:
-1) Set `discord.groupPolicy: "open"` **or** add the guild/channel allowlist.
-2) Use **numeric channel IDs** in `discord.guilds.<guildId>.channels`.
-3) Put `requireMention: false` **under** `discord.guilds` (global or per‑channel).
-   Top‑level `discord.requireMention` is not a supported key.
+1) Set `channels.discord.groupPolicy: "open"` **or** add the guild/channel allowlist.
+2) Use **numeric channel IDs** in `channels.discord.guilds.<guildId>.channels`.
+3) Put `requireMention: false` **under** `channels.discord.guilds` (global or per‑channel).
+   Top‑level `channels.discord.requireMention` is not a supported key.
 4) Ensure the bot has **Message Content Intent** and channel permissions.
-5) Run `clawdbot providers status --probe` for audit hints.
+5) Run `clawdbot channels status --probe` for audit hints.
 
-Docs: [Discord](/providers/discord), [Providers troubleshooting](/providers/troubleshooting).
+Docs: [Discord](/channels/discord), [Channels troubleshooting](/channels/troubleshooting).
 
 ### Cloud Code Assist API error: invalid tool schema (400). What now?
 

docs/start/getting-started.md

@@ -111,7 +111,7 @@ Dashboard (local loopback): `http://127.0.0.1:18789/`
 If a token is configured, paste it into the Control UI settings (stored as `connect.params.auth.token`).
 
 ⚠️ **Bun warning (WhatsApp + Telegram):** Bun has known issues with these
-providers. If you use WhatsApp or Telegram, run the Gateway with **Node**.
+channels. If you use WhatsApp or Telegram, run the Gateway with **Node**.
 
 ## 4) Pair + connect your first chat surface