@thinkingai/ae-cli 6.0.45 → 6.0.47

package/skills/ae-engage/references/build-task-save-guide.md

@@ -36,12 +36,16 @@ compounds when reusing `definition_request`; flattening them changes audience se
 For the second sequence step, omit `relative_to_first` or set it to `false`; use `true` only
 from the third step onward when its window must be measured from step 1.
 
-For existing-cluster audiences (`targetClusterType=2`), you may copy server-authored definitions via:
+For server-side existing-cluster audiences (`targetClusterType=2`), you may copy server-authored definitions via:
 
 ```bash
 ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<cluster_name>"]'
 ```
 
+Server-side channels allow custom (`1`) or existing (`2`) audiences and reject all users (`3`).
+`client_push` (`channelType=3`) allows custom (`1`) or all users (`3`) and rejects existing (`2`).
+Always pass `channelType` in `context` so the guide can validate this matrix.
+
 4. Build the final grouped `save_task.req`.
 5. Submit with `ae-cli engage-task task save --project-id <projectId> --req '{...}'`.
 
@@ -229,6 +233,8 @@ When experiment mode is enabled (`context.enableExp=true` or draft `expConfig.en
 - capability `engage-task.task.build-save-guide` enriches `handoff.reqTemplate.channelConfig.groupContentList`
   so each entry carries `expGroupName`, `expGroupType`, `percentageInExperiment`, `order`, and `contentList`
 - do not drop those association fields when filling content; they must stay aligned with `expConfig.expGroupList`
+- copy the complete group tuple (`expGroupName`, `expGroupType`, `percentageInExperiment`, `order`)
+  into both lists; matching only by list position is not sufficient
 
 ### 4.8 `fieldRules`
 
@@ -300,6 +306,11 @@ Apply this rule only to
 `completionIndicatorDef.completionIndicators[].eventDefinition.filters`. Trigger-event filters have
 their own scenario rules and are not subject to this completion-filter restriction.
 
+For `completionIndicatorType=0`, also read and preserve `requiredMainGoalFields` and
+`touchCycleRule`. A valid main goal includes `touch_cycle_num` and `touch_cycle_num_unit`; use `1`
+and `day` when no custom completion window is requested. Do not rely on static `--validate` alone
+because the save service performs this additional business validation.
+
 ### 4.9 `handoff`
 
 This is the final section before `save_task`.
@@ -336,6 +347,8 @@ Recommended usage pattern:
    definition directly
 7. omit `clientConfig.clientQp`; partial updates preserve the server-authored value
 8. call `engage-task task save`
+9. after an experiment save succeeds, call `engage-task task get` and verify that both
+   `exp_config.exp_group_list` and `group_content_list` contain the expected group tuples
 
 ---
 

package/skills/ae-engage/references/save-task.md

@@ -245,6 +245,12 @@ Use the guide to decide which audience shape applies:
 - `targetClusterType=2`: existing cluster, requires `clusterKey`
 - `targetClusterType=3`: all users, forbids `definitionRequest` and `clusterKey`
 
+Audience availability depends on delivery side:
+
+- Server-side channels support `targetClusterType=1` (custom) and `2` (existing), but not `3` (all users).
+- `client_push` (`channelType=3`) supports `targetClusterType=1` (custom) and `3` (all users), but not `2` (existing).
+- Determine the delivery side from the selected real channel; do not infer audience support from `triggerType` alone.
+
 For a custom audience, pass the semantic definition directly. Do not create an intermediate
 cluster or copy persisted QP.
 
@@ -426,6 +432,11 @@ When the guide points to event-based completion or experiment-driven main-goal r
 Read `fieldRules.blocks.controlConfig.completionIndicatorDef.filterPropertySelectTypes` and exclude
 every property type listed under `excluded` before constructing its `filters`.
 
+For a main goal (`completionIndicatorType=0`), always include `touch_cycle_num` and
+`touch_cycle_num_unit`. If the user does not request another completion window, use
+`touch_cycle_num=1` and `touch_cycle_num_unit="day"`. Static Capability validation may accept a
+main goal without these fields, but the Hermes save service rejects it.
+
 Important constraints that still apply:
 
 - `doNotDisturb.enableDoNotDisturb=true` requires `startTime` and `endTime` in `HH:mm`
@@ -444,6 +455,81 @@ compatibility field, and partial task updates preserve the existing server value
 client-side condition has no semantic field in the current contract, stop and report that it cannot
 be safely authored through this Capability.
 
+### 4.7 Verified A/B Task Template
+
+Use this shape as the starting point for a server-channel split experiment. Replace every
+placeholder with metadata discovered from the current project.
+
+```json
+{
+  "baseInfo": {
+    "taskName": "<taskName>",
+    "taskDesc": "<taskDescription>",
+    "tzOffset": "<projectTimezoneOrDefaultSentinel>"
+  },
+  "channelConfig": {
+    "channelType": 1,
+    "channelId": "<verifiedChannelId>",
+    "groupContentList": [
+      {
+        "expGroupName": "Control",
+        "expGroupType": 1,
+        "percentageInExperiment": 50,
+        "order": 0,
+        "contentList": [{ "pushLanguageCode": "default", "content": "<channelContentJsonString>" }]
+      },
+      {
+        "expGroupName": "Experiment A",
+        "expGroupType": 2,
+        "percentageInExperiment": 50,
+        "order": 1,
+        "contentList": [{ "pushLanguageCode": "default", "content": "<channelContentJsonString>" }]
+      }
+    ]
+  },
+  "targetConfig": {
+    "targetClusterType": 1,
+    "definitionRequest": "<semanticAudienceDefinition>"
+  },
+  "triggerConfig": { "triggerType": 2 },
+  "controlConfig": {
+    "completionIndicatorDef": {
+      "completionIndicators": [
+        {
+          "completionIndicatorType": 0,
+          "touch_cycle_num": 1,
+          "touch_cycle_num_unit": "day",
+          "eventDefinition": {
+            "type": "event",
+            "event": "<verifiedGoalEvent>",
+            "aggregation": "count",
+            "operator": "gte",
+            "value": 1
+          }
+        }
+      ]
+    },
+    "frequencyLimits": { "enableFrequencyLimits": false, "ruleList": [] }
+  },
+  "expConfig": {
+    "enableExp": true,
+    "expType": 1,
+    "percentageInLayer": 100,
+    "expIndicatorBizType": 1,
+    "controlGroupSkipPush": false,
+    "expGroupList": [
+      { "expGroupName": "Control", "expGroupType": 1, "percentageInExperiment": 50, "order": 0 },
+      { "expGroupName": "Experiment A", "expGroupType": 2, "percentageInExperiment": 50, "order": 1 }
+    ]
+  }
+}
+```
+
+The experiment group tuple (`expGroupName`, `expGroupType`, `percentageInExperiment`, `order`)
+must be identical between each `expConfig.expGroupList` entry and its corresponding
+`channelConfig.groupContentList` entry. Validate the final request, save it, then call `task get`
+and verify both persisted lists; a successful task ID alone is not sufficient verification.
+
 ---
 
 ## 5. Final Self-Check Before `engage-task task save`
@@ -461,6 +547,8 @@ Before submission, verify:
 9. No unsupported `triggerType=6` is used.
 10. Ordered steps contain `eventDefinition` and sequence metadata, not persisted aggregate fields.
 11. No placeholder IDs or fabricated resource names remain in the request.
+12. Every main goal includes `touch_cycle_num` and `touch_cycle_num_unit`.
+13. For experiments, `expGroupList` and `groupContentList` contain identical group tuples.
 
 ---
 

package/skills/ae-kb/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ae-kb
 version: 1.0.0
-description: "AE/TE knowledge base CLI manual for creating, querying, LLM-powered ask, listing accessible knowledge bases, deterministic index/grep/read retrieval, checking status, uploading, compiling, schema generation, URL sources, source deletion, and knowledge base deletion. Use when the user asks to manage TE/AE/ThinkingEngine knowledge bases, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, list accessible knowledge bases, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, or delete a knowledge base. To choose which knowledge base is worth searching, use the ae-kb-discovery skill first; this skill runs the retrieval once a target is chosen. Must use ae-cli kb commands and must not guess knowledge base names, scopes, page paths, source display names, JSON payload shapes, or URL formats."
+description: 'AE/TE knowledge base CLI manual for creating, importing read-only compiled snapshots, querying, LLM-powered ask, listing accessible knowledge bases and their sources, deterministic index/grep/read retrieval, checking status, uploading, compiling, schema generation, URL sources, source deletion, and knowledge base deletion. Use when the user asks to manage TE/AE/ThinkingEngine knowledge bases, import a compiled Markdown ZIP snapshot, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, list accessible knowledge bases or source metadata, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, or delete a knowledge base. To choose which knowledge base is worth searching, use the ae-kb-discovery skill first; this skill runs the retrieval once a target is chosen. Must use ae-cli kb commands and must not guess knowledge base names, scopes, page paths, source IDs, source display names, JSON payload shapes, or URL formats.'
 ---
 
 # ae-kb
@@ -14,11 +14,11 @@ ae-cli kb +<command> [options]
 
 ## Global Rules
 
-- Use this skill for TE/AE knowledge base tasks: create, query, ask with LLM, list accessible knowledge bases, inspect indexes, grep pages, read pages, check status, upload sources, add URL sources, generate schema, compile, remove source files, and delete knowledge bases.
+- Use this skill for TE/AE knowledge base tasks: create, import a compiled snapshot, query, ask with LLM, list accessible knowledge bases and their sources, inspect indexes, grep pages, read pages, check status, upload sources, add URL sources, generate schema, compile, remove source files, and delete knowledge bases.
 - **Searching a knowledge base for an answer is the most common task. If that is what you are doing, go straight to [Explore Knowledge Base Pages](#explore-knowledge-base-pages) and read [`references/query-workflow.md`](references/query-workflow.md) first — it is the retrieval procedure. The other commands below are for managing knowledge bases, not answering from them.**
 - Read operations can run directly after required inputs are known. Write operations require explicit user intent and normally keep the confirmation prompt unless the user asks to bypass it.
 - Prefer `--dry-run` before destructive or broad writes when the user has not already validated the target.
-- Do not invent knowledge base names, scopes, source display names, or JSON payloads. Ask the user or query known context when values are missing.
+- Do not invent knowledge base names, scopes, source IDs, source display names, or JSON payloads. Ask the user or query known context when values are missing.
 - When building a `--sources` ref (or `+read --source`), copy the exact `scope` and `name` from `+list` output — run `ae-cli kb +list` first when the scope of a named knowledge base is unknown.
 - JSON flags must be valid JSON strings, usually wrapped in single quotes in shell commands.
 - Successful commands return JSON by default. Use `--format table` only when a table is easier for a human to scan. Envelope may include optional `_notice.host_compat`.
@@ -33,16 +33,19 @@ ae-cli kb +<command> [options]
 | `+ask` | read | LLM-powered Q&A over knowledge bases; for multi-page synthesis or multi-hop questions. |
 | `+ask-status` | read | Query the current status of an ask execution by `--execution-id` without polling. |
 | `+list` | read | List accessible knowledge bases filtered by buildStatus (default: compiled). |
+| `+list-sources` | read | List source metadata for one knowledge base so exact source identifiers can be discovered safely. |
 | `+index` | read | List accessible knowledge bases and their `index.md` navigation maps. |
 | `+grep` | read | Keyword-search knowledge base pages and return matched lines with context. |
 | `+read` | read | Read a full knowledge base page, a line window, or (with `--outline`) only the page heading tree. |
 | `+new` | write | Create a new personal or company knowledge base. |
+| `+import` | write | Import a compiled Markdown ZIP as a personal read-only snapshot. |
+| `+import-status` | read | Query one snapshot import task by `--request-id` without polling. |
 | `+add` | write | Upload local files, a non-recursive directory, or HTTP(S) pages converted to markdown. |
 | `+url` | write | Upload a URL source directly with optional display name and parsing instruction. |
 | `+schema` | write | Generate the compile schema for a knowledge base. |
 | `+compile` | write | Compile a knowledge base in incremental or full mode. |
 | `+status` | read | Query the current status of a knowledge base. |
-| `+rm-source` | write | Delete one source file from a knowledge base by display name. |
+| `+rm-source` | high-risk-write | Delete one source from a knowledge base by stable ID; exact display name is legacy compatibility only. |
 | `+remove` | write | Delete an entire knowledge base. |
 
 ## Common Workflows
@@ -67,6 +70,36 @@ Optional fields:
 - `--project-id`: optional project ID to bind.
 - `--project-name`: optional project display name.
 
+### Import a Compiled Snapshot
+
+Use `+import` only for a ZIP whose root contains `index.md` and at least one
+`wiki/**/*.md` page. The server validates all archive paths, limits, UTF-8 text, and Wiki links.
+
+```bash
+ae-cli kb +import \
+  --file ./knowledge-base.zip \
+  --name "Imported handbook" \
+  --description "Compiled documentation snapshot" \
+  --tags '["docs","handbook"]'
+
+# The submission returns requestId + queued. Query one snapshot later:
+ae-cli kb +import-status --request-id <requestId>
+```
+
+- The result is always a `personal` read-only snapshot; there is no `--scope`, `--force`, or replace option.
+- Imported snapshots support list, Index/Wiki reading, grep/read, Ask, and deletion. They do not expose source, Schema, usage, compile, member, settings, ownership-transfer, or company-publish operations.
+- The ZIP is limited to 50 MB and supports Markdown text only. Local images, attachments, other binaries, broken Wiki links, and ambiguous Wiki links are rejected by the server.
+- Submission returns `{requestId, status: "queued"}` immediately. It does not wait for ZIP validation or publication.
+- `+import-status` returns one of `queued`, `running`, `succeeded`, or `failed`; success includes `knowledgeBaseId`, and failure includes a stable error code/message.
+- If a `requestId` was returned, query it before retrying. If no request ID was received, run `ae-cli kb +list` before retrying the same name. A repeated same-name import is rejected.
+
+- Transition status: transitional
+- Owning module: te-claude External Knowledge Base Import API
+- Current transport: authenticated KB external REST through `kbUpload` for submission and `kbApi` for status lookup.
+- Gateway target: TBD (`kb.snapshot.import` proposed)
+- Review after: 2026-12-01
+- Exit condition: migrate to a typed Gateway capability when the equivalent multipart import capability is available, or remove this command if dynamic Gateway execution provides the same file-handling and output contract.
+
 ### Upload Files or Directories
 
 Use `+add` when sources are local files, local directories, or pages that should be fetched and converted to markdown before upload.
@@ -97,7 +130,7 @@ ae-cli kb +url \
   --parse-instruction "Keep headings and code blocks"
 ```
 
-`--url` must be `http(s)`.
+`--url` must be `http(s)`. The server detects the platform from the URL automatically: URLs on a `*.feishu.cn` or `*.larksuite.com` subdomain are parsed with the Feishu pipeline (including sub-documents, using the server's own Feishu parsing instruction — `--parse-instruction` is ignored for them); all other URLs are fetched as regular web pages.
 
 ### Generate Schema and Compile
 
@@ -107,7 +140,17 @@ Generate the schema first when the knowledge base needs a compile schema.
 ae-cli kb +schema --name engineering-handbook
 ```
 
-Use `--force` only to recover a stuck `generating` status. Use `--model` only when the user provides the model display name.
+Use `--force` only when `+status` reports `schema_generating` and the user explicitly wants to replace the current generation attempt. The replacement may consume additional tokens. Use `--model` only when the user provides the model display name.
+
+To add one-time guidance for this generation without changing stored knowledge base metadata, pass `--custom-instructions`. The server trims the value, treats whitespace-only input as absent, and accepts up to 10,000 Unicode characters. Do not include secrets or credentials.
+
+```bash
+ae-cli kb +schema \
+  --name engineering-handbook \
+  --custom-instructions "Prioritize troubleshooting workflows and preserve command examples"
+```
+
+Use `--dry-run` to inspect the request body before sending it. While generation is running, a request without `--force` is idempotent only when it supplies no new model or effective custom instructions; otherwise it fails with `KB_SCHEMA_GENERATION_IN_PROGRESS`. With `--force`, the selected model and custom instructions apply to the replacement attempt. Invalid text fails with `KB_SCHEMA_CUSTOM_INSTRUCTIONS_INVALID`.
 
 Compile after sources and schema are ready:
 
@@ -213,9 +256,34 @@ ae-cli kb +read \
   --limit 60
 ```
 
+### List Sources
+
+List sources first to discover the stable identifier for the intended source:
+
+```bash
+ae-cli kb +list-sources --name engineering-handbook
+```
+
+Copy the exact `id` from the response into `+rm-source`. Do not guess a source ID from a local filename, URL, display name, or an older upload response.
+
+- Transition status: transitional
+- Owning module: te-claude External Knowledge Base Sources API
+- Current transport: authenticated KB external REST through `kbApi`.
+- Gateway target: TBD (`kb.source.list` proposed)
+- Review after: 2026-12-03
+- Exit condition: migrate to a typed Gateway capability when an equivalent source-list capability is available, or remove this command if dynamic Gateway execution provides the same discoverability and safe output contract.
+
 ### Remove One Source
 
-Use `+rm-source` only when the source display name is known exactly.
+Use `+rm-source --id` with the exact ID returned by the current `+list-sources` response. This is a `high-risk-write`; keep the interactive confirmation unless the user has explicitly authorized `--yes`.
+
+```bash
+ae-cli kb +rm-source \
+  --name engineering-handbook \
+  --id cm-source-id
+```
+
+`--display-name` is retained for legacy compatibility only when a stable source ID is unavailable:
 
 ```bash
 ae-cli kb +rm-source \
@@ -223,7 +291,7 @@ ae-cli kb +rm-source \
   --display-name kb-1780046712-guide.md
 ```
 
-If the user only gives a loose source name, do not guess. Ask for the exact uploaded display name.
+If the user only gives a loose source name, do not guess a source ID. Run `+list-sources`, identify the intended row from returned metadata, and ask only when multiple rows remain ambiguous.
 
 ### Delete a Knowledge Base
 
@@ -316,6 +384,30 @@ ae-cli kb +new --name "<name>" [--scope personal|company] [--description "..."]
 ae-cli kb +add --name "<name>" --files '["./a.md","./docs","https://example.com/page"]'
 ```
 
+### `+import`
+
+```bash
+ae-cli kb +import --file "./knowledge-base.zip" --name "<name>" [--description "..."] [--tags '["t1","t2"]'] [--project-id "..."]
+```
+
+- `--file`: required local `.zip` file.
+- `--name`: required personal knowledge-base name, up to 30 characters.
+- `--description`: optional, up to 200 characters.
+- `--tags`: optional JSON array, max 2 unique tags, each up to 15 characters.
+- `--project-id`: optional project binding.
+- Scope and terminal build state are generated by the server and cannot be supplied by the client.
+- Output: `{requestId, status: "queued"}`. Use `+import-status`; the command does not poll.
+
+### `+import-status`
+
+```bash
+ae-cli kb +import-status --request-id <requestId>
+```
+
+- `--request-id`: required ID returned by `+import`.
+- Output: `{requestId, status, knowledgeBaseId?, errorCode?, errorMessage?}`.
+- Returns a single snapshot and does not poll. A failed import is returned as `status: "failed"` with its stable error code/message; an unknown or inaccessible request exits non-zero.
+
 ### `+url`
 
 ```bash
@@ -325,9 +417,14 @@ ae-cli kb +url --name "<name>" --url "https://example.com/page" [--display-name
 ### `+schema`
 
 ```bash
-ae-cli kb +schema --name "<name>" [--force] [--model "<model displayName>"]
+ae-cli kb +schema --name "<name>" [--force] [--model "<model displayName>"] [--custom-instructions "<one-time guidance>"]
 ```
 
+- `--custom-instructions`: Optional per-run schema-generation guidance. It is not persisted; whitespace-only input is omitted. The server allows at most 10,000 Unicode characters and rejects disallowed control characters. Do not include secrets or credentials.
+- `--force`: Replace the current attempt only when schema generation is already running and the user explicitly requests the replacement. The selected model and custom instructions apply to the new attempt, which may consume additional tokens.
+- `--dry-run`: Shows the same `customInstructions` request field that execution will send.
+- Errors: `KB_SCHEMA_CUSTOM_INSTRUCTIONS_INVALID` means the field failed validation. `KB_SCHEMA_GENERATION_IN_PROGRESS` means generation is active and a request without `--force` supplied a new model or effective custom instructions.
+
 ### `+compile`
 
 ```bash
@@ -340,12 +437,26 @@ ae-cli kb +compile --name "<name>" [--mode incremental|full]
 ae-cli kb +status --name "<name>"
 ```
 
+### `+list-sources`
+
+```bash
+ae-cli kb +list-sources --name "<name>"
+```
+
+- `--name`: required knowledge base name.
+- Output: Safe source metadata including the stable `id` needed by `+rm-source`; raw paths, hashes, credentials, and source content are not returned.
+- Copy the exact `id` from the current response before deleting a source; never guess it.
+
 ### `+rm-source`
 
 ```bash
-ae-cli kb +rm-source --name "<name>" --display-name "<uploaded source display name>"
+ae-cli kb +rm-source --name "<name>" --id "<source-id>"
 ```
 
+- `--id`: preferred stable source identifier copied from `+list-sources`.
+- `--display-name`: legacy compatibility selector used only when an ID is unavailable.
+- If both are supplied, `--id` wins. The command removes one source only.
+
 ### `+remove`
 
 ```bash

package/skills/ae-system/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ae-system
-version: 1.1.0
-description: "AE Agent system administration CLI for root and agent administrators. Use when the user asks to manage Agent members, sandboxes and shared tools, company model visibility/defaults/pricing, usage statistics and exports, cost quotas, balance alerts, or IM channels. Must use ae-cli system commands, discover real IDs before writes, and never attempt to bypass a permission denial."
+version: 1.2.0
+description: "AE Agent system administration CLI for root and agent administrators. Use when the user asks to manage Agent members, sandboxes and shared tools, company model visibility/defaults/pricing, usage statistics and exports, cost quotas, balance alerts, IM channels, channel routing, WhatsApp Web linking, or Feishu user bindings. Must use ae-cli system commands, discover real IDs before writes, and never attempt to bypass a permission denial."
 ---
 
 # ae-system
@@ -10,12 +10,13 @@ Use the `system` domain for Agent system administration:
 
 ```bash
 ae-cli system +<command> [options]
+ae-cli system <resource> <action> [options]
 ```
 
 ## Mandatory Rules
 
 - These commands are only for users whose Agent role is `root` or `agent_admin`.
-- The te-agent `/api/admin/**` endpoint is the final authorization boundary. A member receives a permission error (HTTP 403). Do not retry login or attempt a different endpoint after a 403.
+- The te-agent `/api/admin/**` and `/api/cli/channel/v1/**` endpoints are the final authorization boundaries. A member receives a permission error (HTTP 403). Do not retry login or attempt a different endpoint after a 403.
 - Run `ae-cli auth login --host <host>` before using this domain. System administration requires a user access-token session; sandbox identity headers are not an authorization substitute.
 - `+npm-install` is the exception that must also run inside a Linux te-agent sandbox because it packages the installed Linux files. It still requires the logged-in user to be `root` or `agent_admin`.
 - Discover real IDs with a list command before any update or delete. Never guess a user, sandbox, model, quota rule, or channel ID.
@@ -353,41 +354,38 @@ Rules:
 
 ### Channels
 
+For channel setup, routing, WhatsApp Web linking, or Feishu user binding, read [references/channel-management.md](references/channel-management.md) before taking action. It defines the two confirmation phases and the `ae-cli` plus Feishu OpenAPI MCP workflow.
+
 | Command | Risk | Purpose |
 | --- | --- | --- |
-| `+list-channels` | read | List Feishu, Lark, and Slack channels. |
+| `+list-channels` | read | List all configured channels. |
+| `channel get` | read | Read one channel, its verification state, and endpoints. |
 | `+create-channel` | write | Create one channel. |
 | `+update-channel` | write | Update channel settings, credentials, model, prompt, or enabled state. |
 | `+remove-channel` | high-risk-write | Delete a channel, unbind users, and stop its connection. |
-
-Always use `@file` for channel payloads when they contain credentials:
+| `channel verify` | write | Verify credentials and discover endpoints. |
+| `channel routing get` | read | Read one endpoint's group message routing. |
+| `channel routing set` | write | Replace one endpoint's group message routing. |
+| `channel whatsapp-web status` | read | Read a WhatsApp Web link state and QR data. |
+| `channel whatsapp-web start` | write | Start or resume WhatsApp Web QR linking. |
+| `channel whatsapp-web unlink` | high-risk-write | Unlink WhatsApp Web and remove stored credentials. |
+| `channel binding list` | read | List channel user bindings. |
+| `channel binding bind-feishu` | write | Bind one Feishu user. |
+| `+bind-feishu-users` | write | Bind 1-100 Feishu users and optionally assign Agents. |
+| `channel binding unbind` | high-risk-write | Delete one channel user binding. |
+| `channel binding set-agent` | write | Set or clear one binding's private-chat default Agent. |
+
+Use canonical snake_case request fields. The four original commands also accept their legacy camelCase JSON fields for compatibility. Always use `@file` for credentials and batch rosters:
 
 ```bash
 ae-cli system +create-channel --channel @channel.json
 ae-cli system +update-channel --id <channel-id> --channel @channel-update.json
+ae-cli system +bind-feishu-users \
+  --channel-id <channel-id> \
+  --endpoint-id <endpoint-id> \
+  --bindings @bindings.json
 ```
 
-Create schema:
-
-```json
-{
-  "name": "Required display name",
-  "type": "feishu",
-  "config": {
-    "appId": "Feishu/Lark",
-    "appSecret": "Feishu/Lark",
-    "botToken": "Slack",
-    "appToken": "Slack",
-    "clientId": "optional",
-    "clientSecret": "optional"
-  },
-  "model": "optional Model.id or modelId::scope",
-  "systemPrompt": "optional"
-}
-```
-
-Update accepts a partial object with `name`, `config`, `model`, `systemPrompt`, `enabled`, or `unbindUsers`. Channel type is immutable after creation. Dry-run replaces secret values with `***`.
-
 ## Permission Errors
 
 A permission response looks like:
@@ -412,9 +410,9 @@ An authenticated `root` or `agent_admin` is still scoped to their own company. T
 
 ## Transport Status
 
-This is a Transitional L2 domain backed by te-agent `/api/admin/**`.
+This is a Transitional domain backed by te-agent `/api/admin/**` and `/api/cli/channel/v1/**`.
 
-- Maintainer: te-agent admin routes and `src/commands/te-system/**`.
-- Migration target: system Capability Gateway.
+- Maintainer: te-agent admin/channel-management routes and `src/commands/te-system/**`.
+- Migration target: system and channel Capability Gateways.
 - Review date: 2026-10-24.
 - Exit condition: migrate after equivalent gateway schema, auth, risk, dry-run, and output contracts are stable.