@m8t-stack/cli 0.2.34 → 0.2.36

package/README.md

@@ -121,12 +121,14 @@ Key flags: `--client-id <appId>` (reuse an existing app reg + skip **all** Micro
 
 ## Binding management — `m8t bind`
 
-Wire channel bots (Telegram, Slack, Teams) to Foundry workers. F4 ships
-the management API + CLI scaffolding; the actual adapters (which deliver
-inbound messages from each channel) ship in later features.
+Wire channel bots (Telegram, Slack, Teams) to Foundry workers. The binding
+management API + CLI cover all three channels; a channel can only complete
+a bind once its adapter (which delivers inbound messages from that
+channel) is registered at gateway startup — Telegram ships built in, Slack
+and Teams adapters are not registered yet.
 
 ```bash
-# Create a binding (requires the channel adapter — Telegram ships in F6)
+# Create a binding (Telegram's adapter ships built in)
 m8t bind add telegram \
   --worker cmo \
   --bot-token <from-botfather> \
@@ -152,17 +154,18 @@ m8t bind cleanup --all-orphaned
 
 > `--worker` is the **case-sensitive, lowercase** Foundry agent name as deployed (e.g. `cmo`). A wrong name isn't rejected at bind time — it surfaces later as an orphaned binding on the first message.
 
-### Pre-F6 behavior
+### Binding a channel with no registered adapter
 
-`m8t bind add telegram ...` currently fails with:
+`m8t bind add slack ...` (or `teams`) currently fails with:
 
 ```text
-error: no adapter for channel 'telegram'. This is expected for F4 alone;
-       the channel-specific adapter ships in a later feature.
+error: no adapter for channel 'slack'. The channel-specific adapter is not
+       registered in this build.
 ```
 
-This is correct. F6 (Telegram adapter) will register the adapter at
-startup and unlock the create flow.
+This is correct — Slack and Teams adapters aren't registered yet. Once a
+channel's adapter registers at gateway startup, binding creation for that
+channel unlocks.
 
 ### Cascade-delete idempotency