docs: complete channels rename sweep

docs/concepts/streaming.md

@@ -1,19 +1,19 @@
 ---
 summary: "Streaming + chunking behavior (block replies, draft streaming, limits)"
 read_when:
-  - Explaining how streaming or chunking works on providers
-  - Changing block streaming or provider chunking behavior
+  - Explaining how streaming or chunking works on channels
+  - Changing block streaming or channel chunking behavior
   - Debugging duplicate/early block replies or draft streaming
 ---
 # Streaming + chunking
 
 Clawdbot has two separate “streaming” layers:
-- **Block streaming (providers):** emit completed **blocks** as the assistant writes. These are normal provider messages (not token deltas).
+- **Block streaming (channels):** emit completed **blocks** as the assistant writes. These are normal channel messages (not token deltas).
 - **Token-ish streaming (Telegram only):** update a **draft bubble** with partial text while generating; final message is sent at the end.
 
-There is **no real token streaming** to external provider messages today. Telegram draft streaming is the only partial-stream surface.
+There is **no real token streaming** to external channel messages today. Telegram draft streaming is the only partial-stream surface.
 
-## Block streaming (provider messages)
+## Block streaming (channel messages)
 
 Block streaming sends assistant output in coarse chunks as it becomes available.
 
@@ -24,20 +24,20 @@ Model output
        │    └─ chunker emits blocks as buffer grows
        └─ (blockStreamingBreak=message_end)
             └─ chunker flushes at message_end
-                   └─ provider send (block replies)
+                   └─ channel send (block replies)
 ```
 Legend:
 - `text_delta/events`: model stream events (may be sparse for non-streaming models).
 - `chunker`: `EmbeddedBlockChunker` applying min/max bounds + break preference.
-- `provider send`: actual outbound messages (block replies).
+- `channel send`: actual outbound messages (block replies).
 
 **Controls:**
 - `agents.defaults.blockStreamingDefault`: `"on"`/`"off"` (default off).
-- Provider overrides: `*.blockStreaming` (and per-account variants) to force `"on"`/`"off"` per provider.
+- Channel overrides: `*.blockStreaming` (and per-account variants) to force `"on"`/`"off"` per channel.
 - `agents.defaults.blockStreamingBreak`: `"text_end"` or `"message_end"`.
 - `agents.defaults.blockStreamingChunk`: `{ minChars, maxChars, breakPreference? }`.
 - `agents.defaults.blockStreamingCoalesce`: `{ minChars?, maxChars?, idleMs? }` (merge streamed blocks before send).
-- Provider hard cap: `*.textChunkLimit` (e.g., `channels.whatsapp.textChunkLimit`).
+- Channel hard cap: `*.textChunkLimit` (e.g., `channels.whatsapp.textChunkLimit`).
 - Discord soft cap: `channels.discord.maxLinesPerMessage` (default 17) splits tall replies to avoid UI clipping.
 
 **Boundary semantics:**
@@ -54,7 +54,7 @@ Block chunking is implemented by `EmbeddedBlockChunker`:
 - **Break preference:** `paragraph` → `newline` → `sentence` → `whitespace` → hard break.
 - **Code fences:** never split inside fences; when forced at `maxChars`, close + reopen the fence to keep Markdown valid.
 
-`maxChars` is clamped to the provider `textChunkLimit`, so you can’t exceed per-provider caps.
+`maxChars` is clamped to the channel `textChunkLimit`, so you can’t exceed per-channel caps.
 
 ## Coalescing (merge streamed blocks)
 
@@ -68,7 +68,7 @@ progressive output.
   (final flush always sends remaining text).
 - Joiner is derived from `blockStreamingChunk.breakPreference`
   (`paragraph` → `\n\n`, `newline` → `\n`, `sentence` → space).
-- Provider overrides are available via `*.blockStreamingCoalesce` (including per-account configs).
+- Channel overrides are available via `*.blockStreamingCoalesce` (including per-account configs).
 - Default coalesce `minChars` is bumped to 1500 for Signal/Slack/Discord unless overridden.
 
 ## Human-like pacing between blocks
@@ -84,11 +84,11 @@ more natural.
 ## “Stream chunks or everything”
 
 This maps to:
-- **Stream chunks:** `blockStreamingDefault: "on"` + `blockStreamingBreak: "text_end"` (emit as you go). Non-Telegram providers also need `*.blockStreaming: true`.
+- **Stream chunks:** `blockStreamingDefault: "on"` + `blockStreamingBreak: "text_end"` (emit as you go). Non-Telegram channels also need `*.blockStreaming: true`.
 - **Stream everything at end:** `blockStreamingBreak: "message_end"` (flush once, possibly multiple chunks if very long).
 - **No block streaming:** `blockStreamingDefault: "off"` (only final reply).
 
-**Provider note:** For non-Telegram providers, block streaming is **off unless**
+**Channel note:** For non-Telegram channels, block streaming is **off unless**
 `*.blockStreaming` is explicitly set to `true`. Telegram can stream drafts
 (`channels.telegram.streamMode`) without block replies.
 
@@ -97,14 +97,14 @@ Config location reminder: the `blockStreaming*` defaults live under
 
 ## Telegram draft streaming (token-ish)
 
-Telegram is the only provider with draft streaming:
+Telegram is the only channel with draft streaming:
 - Uses Bot API `sendMessageDraft` in **private chats with topics**.
 - `channels.telegram.streamMode: "partial" | "block" | "off"`.
   - `partial`: draft updates with the latest stream text.
   - `block`: draft updates in chunked blocks (same chunker rules).
   - `off`: no draft streaming.
 - Draft chunk config (only for `streamMode: "block"`): `channels.telegram.draftChunk` (defaults: `minChars: 200`, `maxChars: 800`).
-- Draft streaming is separate from block streaming; block replies are off by default and only enabled by `*.blockStreaming: true` on non-Telegram providers.
+- Draft streaming is separate from block streaming; block replies are off by default and only enabled by `*.blockStreaming: true` on non-Telegram channels.
 - Final reply is still a normal message.
 - `/reasoning stream` writes reasoning into the draft bubble (Telegram only).