@thinkingai/ae-cli 6.0.32 → 6.0.34

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

@@ -1,10 +1,8 @@
 # engage-activity task
 
-> Capability ids: `engage-activity.task.{get,copy}` · Domain: `engage`.
->
-> Temporarily disabled: `task create` / `task update` (command registration + skill guidance).
+> Capability ids: `engage-activity.task.{get,create,update,copy}` · Domain: `engage`.
 
-运营活动 - 独立任务（活动下不属于主题的任务）。`copy` 读取源任务详情、改名后重新创建（无后端复制 API）。
+Campaign activities — standalone tasks (tasks under an activity that do not belong to a topic). `copy` loads the source task detail, renames it, and re-creates it (no dedicated backend copy API).
 
 ## Commands
 
@@ -12,12 +10,6 @@
 # Get a standalone task detail
 ae-cli engage-activity task get --project-id <project_id> --task-id <task_id>
 
-# Copy a standalone task (loads detail, renames, re-creates)
-ae-cli engage-activity task copy --project-id <project_id> --task-id <task_id> [--new-name <name>]
-```
-
-<!-- Temporarily disabled: task create / task update
-```bash
 # Create a standalone task under an activity (webhook + existing cluster)
 ae-cli engage-activity task create --project-id <project_id> \
   --payload '{ ... }'
@@ -25,24 +17,25 @@ ae-cli engage-activity task create --project-id <project_id> \
 # Update a standalone task
 ae-cli engage-activity task update --project-id <project_id> \
   --payload '{"taskId":"task-1","taskName":"t1", ...}'
+
+# Copy a standalone task (loads detail, renames, re-creates)
+ae-cli engage-activity task copy --project-id <project_id> --task-id <task_id> [--new-name <name>]
 ```
--->
 
 ## Parameters
 
 | Command | Required flags | Notes |
 |---|---|---|
 | get | `--project-id`, `--task-id` | read. |
+| create | `--project-id`, `--payload` | payload = `OperationTaskOpDTO`; set `activityId`, leave `topicId` empty. Missing `expConfig` is auto-filled as `{"enableExp":false}`. |
+| update | `--project-id`, `--payload` | payload = `OperationTaskOpDTO` including `taskId`. Prefer get detail as base. Missing `expConfig` is auto-filled as `{"enableExp":false}`. |
 | copy | `--project-id`, `--task-id` | `--new-name` optional (default source name + `_copy`). |
 
-<!-- Temporarily disabled
-| create | `--project-id`, `--payload` | payload = `OperationTaskOpDTO`; set `activityId`, leave `topicId` empty. |
-| update | `--project-id`, `--payload` | payload = `OperationTaskOpDTO` including `taskId`. |
--->
-
 ## Output
 
 - `get`: `data.task`.
+- `create`: `data.task_id`.
+- `update`: `data.success`.
 - `copy`: `data.task_id`, optional `data.trigger_time_stale` (true when source schedule-single time is already past).
 
 ## Payload notes (for copy / detail shape)
@@ -53,6 +46,7 @@ ae-cli engage-activity task update --project-id <project_id> \
 - `groupContentList[].contentList[].content` must be a JSON **array string**.
 - **TEXT (rich text) params** must include both `value` and `config` (Slate.js JSON **string**). If `config` is missing, Hermes copy auto-fills  
   `config = [{"type":"paragraph","children":[{"text":"<value>"}]}]` as a JSON string.
+- Missing `expConfig` on create/update is auto-filled as `{"enableExp":false}` (same shape as task `get`).
 
 ### Audience (`targetClusterType`)
 
@@ -66,8 +60,8 @@ ae-cli engage-activity task update --project-id <project_id> \
 
 - Discover a real `task_id` via `get`/activity `info-list` first; never invent IDs.
 - `copy` duplicates the editable task config (not runtime/trigger state).
-- `copy` saves via **draft** add (`draft=true`), so a past schedule-single `triggerTime` is allowed; output may include `trigger_time_stale=true`. Update the time before `approval submit`.
-- Standalone tasks must **not** include `topicId`; topic tasks use `engage-activity topic copy` (topic create/update are temporarily disabled).
+- `copy` saves via **draft** add (`draft=true`), so a past schedule-single `triggerTime` is allowed; output may include `trigger_time_stale=true`. Update the time before submitting for approval (`engage-activity.approval.submit` is temporarily unavailable).
+- Standalone tasks must **not** include `topicId`; topic tasks use `engage-activity topic create` / `topic copy`.
 
 ## Copy errors
 

package/skills/ae-engage/references/activity-topic.md

@@ -1,14 +1,18 @@
 # engage-activity topic
 
-> Capability ids: `engage-activity.topic.{remove-task,delete,get,copy}` · Domain: `engage`.
->
-> Temporarily disabled: `topic create` / `topic update` (command registration + skill guidance).
+> Capability ids: `engage-activity.topic.{create,update,remove-task,delete,get,copy}` · Domain: `engage`.
 
 Activity topics and tasks under a topic. `copy` loads the source topic, renames it, and re-creates (no dedicated backend copy API).
 
 ## Commands
 
 ```bash
+# Create a topic and its tasks under an activity
+ae-cli engage-activity topic create --project-id <project_id> --payload '{ ... }'
+
+# Update a topic and its task relations
+ae-cli engage-activity topic update --project-id <project_id> --payload '{"topicId":"topic-1", ...}'
+
 # Remove a task from its topic (high-risk)
 ae-cli engage-activity topic remove-task --project-id <project_id> --task-id <task_id> --yes
 
@@ -22,41 +26,44 @@ ae-cli engage-activity topic get --project-id <project_id> --topic-id <topic_id>
 ae-cli engage-activity topic copy --project-id <project_id> --topic-id <topic_id> [--new-name <name>]
 ```
 
-<!-- Temporarily disabled: topic create / topic update
-```bash
-# Create a topic and its tasks under an activity
-ae-cli engage-activity topic create --project-id <project_id> --payload '{ ... }'
-
-# Update a topic and its task relations
-ae-cli engage-activity topic update --project-id <project_id> --payload '{"topicId":"topic-1", ...}'
-```
--->
-
 ## Parameters
 
 | Command | Required flags | Notes |
 |---|---|---|
+| create | `--project-id`, `--payload` | payload = `TopicAddDTO` (camelCase). Prefer `triggerType` `0` (schedule single) or `1` (schedule repeat); activity topics do not use manual (`2`). |
+| update | `--project-id`, `--payload` | payload = `TopicModifyReq` (`topicId` + fields + task lists). |
 | remove-task | `--project-id`, `--task-id` | high-risk; requires `--yes`; no dry-run. Only tasks with a non-empty `topicId`. |
 | delete | `--project-id`, `--topic-id` | high-risk; requires `--yes`; no dry-run. |
 | get | `--project-id`, `--topic-id` | read. |
 | copy | `--project-id`, `--topic-id` | `--new-name` optional (default source name + `_copy`). |
 
-<!-- Temporarily disabled
-| create | `--project-id`, `--payload` | payload = `TopicAddDTO` (camelCase). |
-| update | `--project-id`, `--payload` | payload = `TopicModifyReq` (`topicId` + fields + task lists). |
--->
-
-## Notes for get / copy
+## Notes for get / copy / create
 
-TEXT (rich text) params inside `groupContentList[].contentList[].content` need both `value` and Slate `config` (JSON string). If `config` is omitted, Hermes copy auto-fills  
+TEXT (rich text) params inside `groupContentList[].contentList[].content` need both `value` and Slate `config` (JSON string). If `config` is omitted, Hermes copy/create auto-fills  
 `[{"type":"paragraph","children":[{"text":"<value>"}]}]`. See `activity-task.md` Channel content.
 
 Topic-level audience uses `topicClusterKey` / `topicQp`; do **not** pass task-level `clusterKey` at topic root.
 
+### Audience (`targetClusterType`)
+
+| Value | Required | Notes |
+|---|---|---|
+| `1` (custom) | `topicQp` | Valid condition JSON object string (not `{}`). |
+| `2` (existed) | `topicClusterKey` | From an existing user cluster. |
+| `3` (all) | — | **Not supported for activity topics** → `TOPIC_TARGET_CLUSTER_TYPE_UNSUPPORTED`. Use standalone `engage-activity task create` for all-users. |
+
+### Trigger (`triggerType`)
+
+| Value | Required | Notes |
+|---|---|---|
+| `0` (schedule single) | `triggerTime` (`yyyy-MM-dd HH:mm`, future) | Preferred for CLI create. |
+| `1` (schedule repeat) | `startDate`, `endDate`, `triggerCrontab` | |
+| `2` (manual) | — | **Not supported for activity topics** (UI only offers 0/1). Using it without `endDate` causes `CAPABILITY_EXECUTION_FAILED`. |
+
 ## Output
 
 - `get`: `data.topic` (includes `topicClusterKey` for topic audience).
-- `remove-task` / `delete` / `copy`: `data.success`.
+- `create` / `update` / `remove-task` / `delete` / `copy`: `data.success`.
 - `copy` may include `data.trigger_time_stale=true` when source schedule-single time is already past.
 
 ## Decision Rules
@@ -64,9 +71,19 @@ Topic-level audience uses `topicClusterKey` / `topicQp`; do **not** pass task-le
 - `remove-task` and `delete` are `high-risk-write` — require `--yes`, no dry-run.
 - `remove-task` only deletes **topic tasks** (`topicId` present). Standalone tasks → use `engage-task task delete`.
 - `copy` duplicates the editable topic config and its tasks (not runtime/approval state).
-- `copy` saves via **draft** add (`isDraft=true`), so a past schedule-single `triggerTime` is allowed; output may include `trigger_time_stale=true`. Update the time before `approval submit`.
+- `copy` saves via **draft** add (`isDraft=true`), so a past schedule-single `triggerTime` is allowed; output may include `trigger_time_stale=true`. Update the time before submitting for approval (`engage-activity.approval.submit` is temporarily unavailable).
 - Prefer `topic get` as a template when inspecting channel/content fields.
 
+## Create / update audience errors
+
+| code | when |
+|---|---|
+| `TOPIC_TARGET_CLUSTER_TYPE_UNSUPPORTED` | `targetClusterType=3` (all); topics only allow 1/2 |
+| `TOPIC_CLUSTER_KEY_REQUIRED` | `targetClusterType=2` missing `topicClusterKey`, or topic-root `clusterKey` alias |
+| `TOPIC_QP_REQUIRED` | `targetClusterType=1` missing `topicQp` |
+| `TOPIC_QP_INVALID` | `topicQp` is not a JSON object string |
+| `TARGET_CLUSTER_TYPE_INVALID` | `targetClusterType` not a known enum value |
+
 ## Copy errors
 
 `copy` = get topic detail → rename → draft `addTopicAndTask` (no dedicated copy API). Prefer actionable codes over `INVALID_CAPABILITY_REQUEST` / mismatched i18n text like "Campaign does not exist.":

package/skills/ae-engage/references/add-approver.md

@@ -1,15 +1,15 @@
-# ae-engage +add_approver
+# ae-engage engage-setting approval-approver add
 
 
 Batch add approvers.
 
-Mapped command: `ae-cli engage +add_approver`
+Mapped command: `ae-cli engage-setting approval-approver add`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 | `--approvers` | json | Yes | approver open ID JSON array |
 
 ## Safety Constraints
@@ -19,5 +19,5 @@ This command is a **write operation** and and modifies the project approver conf
 ## Examples
 
 ```bash
-ae-cli engage +add_approver --project_id 1 --approvers '["ou_xxx","ou_yyy"]'
+ae-cli engage-setting approval-approver add --project-id 1 --approvers '["ou_xxx","ou_yyy"]'
 ```

package/skills/ae-engage/references/add-channel.md

@@ -1,15 +1,15 @@
-# ae-engage +add_channel
+# ae-engage engage-setting channel create
 
 
 Create a new Engage channel.
 
-Mapped command: `ae-cli engage +add_channel`
+Mapped command: `ae-cli engage-setting channel create`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 | `--req` | json | Yes | Channel creation request JSON object |
 
 ## `--req` Object Fields
@@ -26,7 +26,12 @@ Mapped command: `ae-cli engage +add_channel`
 | `eventDeliveryName` | string | Yes | delivery event name |
 | `touchEventSource` | string | Yes | touch event source |
 
-`projectId` is automatically written into the `--req` object by the CLI, so you do not need to fill it manually. If you provide a field with the same name, the top-level `--project_id` takes precedence.
+The outer Capability input uses `project_id` and `req`; fields inside `req` keep the native camelCase DTO shape in this table. The Hermes Capability handler assigns the outer `--project-id` to `req.projectId`, so you do not need to fill it manually and the outer value takes precedence.
+
+## Response shape
+
+The created channel is under `data.item`; its response keys recursively use snake_case, such as
+`channel_id`, `channel_status`, and `channel_type`.
 
 ## Enum Notes
 
@@ -68,6 +73,6 @@ This command is a **write operation** and creates a new channel. Check that the
 ## Examples
 
 ```bash
-ae-cli engage +add_channel --project_id 1 \
+ae-cli engage-setting channel create --project-id 1 \
   --req '{"channelType":1,"channelSubBizType":"webhook","channelName":"demo","pushIdType":"user_id","config":"{}","enableTouchEvent":0,"eventClickName":"","eventDeliveryName":"","touchEventSource":""}'
 ```

package/skills/ae-engage/references/approval-approver-delete.md

@@ -22,5 +22,5 @@ ae-cli engage-setting approval-approver delete --project-id <project_id> --appro
 ## Decision Rules
 
 - Use this command when the user asks to remove/delete an approver from a project.
-- Discover the real approver OpenID with `ae-cli engage +approver_list --project_id <project_id>` first; never invent an OpenID.
+- Discover the real approver OpenID with `ae-cli engage-setting approval-approver list --project-id <project_id>` first; never invent an OpenID.
 - Risk is `high-risk-write`; the CLI confirmation gate requires `--yes` (or interactive confirmation) before executing.

package/skills/ae-engage/references/approver-list.md

@@ -1,18 +1,18 @@
-# ae-engage +approver_list
+# ae-engage engage-setting approval-approver list
 
 
 Query the project approver list.
 
-Mapped command: `ae-cli engage +approver_list`
+Mapped command: `ae-cli engage-setting approval-approver list`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 
 ## Examples
 
 ```bash
-ae-cli engage +approver_list --project_id 1
+ae-cli engage-setting approval-approver list --project-id 1
 ```

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

@@ -1,8 +1,8 @@
-# ae-engage `+build_task_save_guide`
+# ae-cli `engage-task task build-save-guide`
 
 Build a scenario-specific guide for constructing `save_task.req`.
 
-Mapped command: `ae-cli engage +build_task_save_guide`
+Mapped command: `ae-cli engage-task task build-save-guide`
 
 This is a read-only helper. It does not save tasks, submit approvals, or trigger execution. Its job is to tell you how to build a valid `save_task` request for the current scenario.
 
@@ -12,8 +12,8 @@ This is a read-only helper. It does not save tasks, submit approvals, or trigger
 
 Use this sequence when creating or updating a task draft:
 
-1. Query channels with `ae-cli engage +channel_list --project_id <projectId>`.
-2. Call `ae-cli engage +build_task_save_guide --project_id <projectId> --req '{...}'`.
+1. Query channels with `ae-cli engage-setting channel list --project-id <projectId>`.
+2. Call `ae-cli engage-task task build-save-guide --project-id <projectId> --req '{...}'`.
 3. If the guide says an audience or QP-derived fields are required, create the audience directly and read it back:
 
 ```bash
@@ -22,7 +22,7 @@ ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<co
 ```
 
 4. Build the final grouped `save_task.req`.
-5. Submit with `ae-cli engage +save_task --project_id <projectId> --req '{...}'`.
+5. Submit with `ae-cli engage-task task save --project-id <projectId> --req '{...}'`.
 
 Important:
 
@@ -40,7 +40,7 @@ Important:
 The CLI call shape is:
 
 ```bash
-ae-cli engage +build_task_save_guide --project_id <projectId> --req '<req-json>'
+ae-cli engage-task task build-save-guide --project-id <projectId> --req '<req-json>'
 ```
 
 This CLI requires `--req`, but `{}` is valid when you want a generic guide without scenario context.
@@ -48,9 +48,9 @@ This CLI requires `--req`, but `{}` is valid when you want a generic guide witho
 Common request patterns:
 
 ```bash
-ae-cli engage +build_task_save_guide --project_id 1 --req '{}'
-ae-cli engage +build_task_save_guide --project_id 1 --req '{"context":{"triggerType":2,"channelId":"channel_123"}}'
-ae-cli engage +build_task_save_guide --project_id 1 --req '{"draft":{"baseInfo":{"taskName":"Demo Task"}}}'
+ae-cli engage-task task build-save-guide --project-id 1 --req '{}'
+ae-cli engage-task task build-save-guide --project-id 1 --req '{"context":{"triggerType":2,"channelId":"channel_123"}}'
+ae-cli engage-task task build-save-guide --project-id 1 --req '{"draft":{"baseInfo":{"taskName":"Demo Task"}}}'
 ```
 
 Supported request fields:
@@ -259,8 +259,8 @@ Important fields:
 
 Recommended usage pattern:
 
-1. resolve a real `channelId` with `+channel_list`
-2. call `+build_task_save_guide`
+1. resolve a real `channelId` with `engage-setting channel list`
+2. call `engage-task task build-save-guide`
 3. read `fieldRules.channelContentSchema`
 4. read `handoff.reqTemplate`
 5. fix everything in `blockingPlaceholders`
@@ -272,13 +272,13 @@ ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<co
 ```
 
 7. prefer the created cluster reference; only copy server-authored fields from `user-cluster get` when the guide explicitly requires QP-derived fields
-8. call `+save_task`
+8. call `engage-task task save`
 
 ---
 
 ## 6. Safety Notes
 
-- `+build_task_save_guide` is read-only; it does not save a draft
+- `engage-task task build-save-guide` is read-only; it does not save a draft
 - do not skip the guide and build `save_task.req` from memory alone
 - do not treat the semantic cluster definition builder as mandatory for every task
 - do not invent `channelId`, `clusterKey`, content keys, or QP structures

package/skills/ae-engage/references/cancel-query-by-request-id.md

@@ -1,15 +1,15 @@
-# ae-engage +cancel_query_by_request_id
+# Cancel a running Engage report query
 
 
 Cancel a running data query by requestId.
 
-Mapped command: `ae-cli engage +cancel_query_by_request_id`
+Mapped capability: `engage-setting.query.cancel` (L3)
 
-## Flags
+## Input
 
-| Flag | Type | Required | Description |
+| Field | Type | Required | Description |
 |------|------|------|------|
-| `--request_id` | string | Yes | Query requestId |
+| `request_id` | string | Yes | Query requestId |
 
 ## Safety Constraints
 
@@ -18,5 +18,6 @@ This command is a **write operation** and cancels an existing query.
 ## Examples
 
 ```bash
-ae-cli engage +cancel_query_by_request_id --request_id 00000000-0000-0000-0000-000000000000
+ae-cli capability run engage-setting.query.cancel \
+  --input '{"request_id":"00000000-0000-0000-0000-000000000000"}'
 ```

package/skills/ae-engage/references/channel-detail.md

@@ -1,25 +1,30 @@
-# ae-engage +channel_detail
+# ae-engage engage-setting channel get
 
 
 Query the details of a single Engage channel.
 
-Mapped command: `ae-cli engage +channel_detail`
+Mapped command: `ae-cli engage-setting channel get`
+
+## Response shape
+
+The channel detail is under `data.item`. Every response key is snake_case, for example
+`data.item.channel_status`, `data.item.channel_type`, and `data.item.config.params_list`.
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | channel ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--channel-id` | string | Yes | channel ID |
 
 ## Common enums in the response
 
-### `channelStatus`
+### `data.item.channel_status`
 
 - `0`: disabled
 - `1`: enabled
 
-### `channelType`
+### `data.item.channel_type`
 
 - `1`: `WEBHOOK`
 - `2`: `APP_PUSH`
@@ -27,7 +32,7 @@ Mapped command: `ae-cli engage +channel_detail`
 - `4`: `WECHAT`
 - `5`: `DOU_YIN`
 
-### `channelSubBizType`
+### `data.item.channel_sub_biz_type`
 
 Common values include:
 
@@ -39,7 +44,7 @@ Common values include:
 - `wechat_mini_game`
 - `dou_yin_recommended_game_card`
 
-### `enableTouchEvent`
+### `data.item.enable_touch_event`
 
 - `0`: disable the touch funnel
 - `1`: enable the touch funnel
@@ -47,5 +52,5 @@ Common values include:
 ## Examples
 
 ```bash
-ae-cli engage +channel_detail --project_id 1 --channel_id <channel_id>
+ae-cli engage-setting channel get --project-id 1 --channel-id <channel_id>
 ```

package/skills/ae-engage/references/channel-list.md

@@ -1,26 +1,31 @@
-# ae-engage +channel_list
+# ae-engage engage-setting channel list
 
 
 Query the list of Engage channels in a project.
 
-Mapped command: `ae-cli engage +channel_list`
+Mapped command: `ae-cli engage-setting channel list`
+
+## Response shape
+
+The result is `{ data: { items, total } }`. Channel fields recursively use snake_case, for
+example `data.items[].channel_id`, `data.items[].channel_status`, and `data.items[].channel_type`.
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--provider_list` | json | No | Provider list JSON array |
-| `--channel_status` | number | No | Channel status filter |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--provider-list` | json | No | Provider list JSON array |
+| `--channel-status` | number | No | Channel status filter |
 
 ## Enum Notes
 
-### `--channel_status`
+### `--channel-status`
 
-- `0`: disabled
 - `1`: enabled
+- `2`: disabled
 
-### `--provider_list`
+### `--provider-list`
 
 Common provider / channelSubBizType values:
 
@@ -35,6 +40,6 @@ Common provider / channelSubBizType values:
 ## Examples
 
 ```bash
-ae-cli engage +channel_list --project_id 1
-ae-cli engage +channel_list --project_id 1 --provider_list '["webhook","fcm"]'
+ae-cli engage-setting channel list --project-id 1
+ae-cli engage-setting channel list --project-id 1 --provider-list '["webhook","fcm"]'
 ```

package/skills/ae-engage/references/channel-mgmt.md

@@ -0,0 +1,109 @@
+# Config channel management workflows
+
+> Commands: `ae-cli engage-scene config-channel …` · See [`scene-config-channel.md`](scene-config-channel.md) for flags, `config` JSON shape, and capability ids.
+
+Use for AE Engage **config center channel management**: Webhook (`channel_type=0`) and client (`channel_type=1`) config channels — list, get, create, update, copy, enable/disable, operation log, and delete.
+
+## Hard rules
+
+1. Use `ae-cli engage-scene config-channel <action>` only.
+2. Discover real `channel_id` values with `list` first; never invent IDs.
+3. `channel_type`: **0 = Webhook**, **1 = client** (not the same as engage push `channelType`, where 1 = webhook).
+4. `channel_status`: **1 = enabled**, **2 = disabled**.
+5. Writes require explicit user intent; `delete` is high-risk — confirm, then `--yes`.
+6. Before changing Webhook URL, auth, or parameter definitions on an enabled channel, disable it first.
+
+## Permissions
+
+| Operation | Permission |
+|---|---|
+| List / get / query-log | `@opsViewConfigChannel@` |
+| Create / update / copy / delete | `@opsEditConfigChannel@` |
+| Enable / disable | `@opsManageConfigChannel@` |
+
+## Workflows
+
+### 1. List / filter by name
+
+```bash
+ae-cli engage-scene config-channel list --project-id <pid> --channel-type 0
+ae-cli engage-scene config-channel list --project-id <pid> --channel-type 1
+```
+
+To filter by name, substring-match `data.items[].channel_name`.
+
+### 2. Detail
+
+```bash
+ae-cli engage-scene config-channel get --project-id <pid> --channel-id <channel_id>
+```
+
+Parse `data.channel.config` for URL, auth, user params, and env params.
+
+### 3. Create
+
+Webhook requires `channel_name` and `config.url`. Optional: `testUrl`, auth, user params, env params.
+
+```bash
+ae-cli engage-scene config-channel create \
+  --project-id <pid> \
+  --channel-name '<name>' \
+  --channel-type 0 \
+  --config '{"url":"https://...","testUrl":"","authConfig":{"enable":false},"customsParamList":[{"key":"uid","columnName":"#account_id","defaultValue":"","systemIdParam":false}],"envParamList":[]}'
+```
+
+Returns `data.channel_id`. Created channels start **enabled**.
+
+### 4. Update
+
+```bash
+ae-cli engage-scene config-channel get --project-id <pid> --channel-id <id>
+# If channel_status=1 and changing URL / auth / param definitions:
+ae-cli engage-scene config-channel update-status --project-id <pid> --channel-id <id> --channel-status 2
+ae-cli engage-scene config-channel update \
+  --project-id <pid> --channel-id <id> --channel-name '<name>' --config '<json>'
+# Re-enable if needed
+ae-cli engage-scene config-channel update-status --project-id <pid> --channel-id <id> --channel-status 1
+```
+
+Rename-only on an enabled channel: omit `--config`.
+
+Before changing the system-integration identity (`systemIdParam`), warn the user about risk, then update.
+
+### 5. Copy
+
+```bash
+ae-cli engage-scene config-channel get --project-id <pid> --channel-id <id>
+ae-cli engage-scene config-channel create \
+  --project-id <pid> --channel-name '<name>_copy' --channel-type <0|1> --config '<config from get>'
+```
+
+### 6. Enable / disable
+
+```bash
+ae-cli engage-scene config-channel update-status --project-id <pid> --channel-id <id> --channel-status 1
+ae-cli engage-scene config-channel update-status --project-id <pid> --channel-id <id> --channel-status 2
+```
+
+If disable fails or the user asks about impact: the channel may still have publishing strategies; suggest checking related config items.
+
+### 7. Operation log
+
+```bash
+ae-cli engage-scene config-channel query-log --project-id <pid> --channel-id <id>
+```
+
+### 8. Delete
+
+Enabled channels cannot be deleted:
+
+```bash
+ae-cli engage-scene config-channel get --project-id <pid> --channel-id <id>
+# If channel_status=1 → update-status 2 first (with user confirmation)
+ae-cli engage-scene config-channel delete --project-id <pid> --channel-id <id> --yes
+```
+
+## Do not
+
+- Treat engage push channels as config-center channels (`channel_type` meanings differ)
+- Run `delete` without explicit user confirmation

package/skills/ae-engage/references/channel-test-send.md

@@ -32,6 +32,6 @@ ae-cli engage-setting channel test-send \
 ## Decision Rules
 
 - Use this command when the user asks to send a test message to a channel / verify channel delivery.
-- Discover the real channel id with `ae-cli engage +channel_list` first; never invent a channel id.
+- Discover the real channel id with `ae-cli engage-setting channel list` first; never invent a channel id.
 - `--mock-push` is useful to inspect the request body/headers without actually delivering a message.
 - Risk is `write`; sending a real test push to a recipient is a write action.

package/skills/ae-engage/references/channel-update-config.md

@@ -32,5 +32,5 @@ ae-cli engage-setting channel update-config \
 ## Decision Rules
 
 - Use this command when the user asks to edit/update an existing channel's name, config, push-id type, or reach-funnel settings.
-- `--config` is the channel-specific JSON config; discover the existing config with `ae-cli engage +channel_detail` first rather than inventing it.
+- `--config` is the channel-specific JSON config; discover the existing config with `ae-cli engage-setting channel get` first rather than inventing it.
 - Risk is `write`; ordinary update, no confirmation gate.

package/skills/ae-engage/references/channel_touch_limits_list.md

@@ -25,5 +25,5 @@ ae-cli engage-setting channel-touch-limits list --project-id <project_id> --dry-
 ## Decision Rules
 
 - Use this command when the user asks for project channel touch-limit, delivery-cap, or fatigue-control rules.
-- Use `+channel_list` to list channels and `+channel_detail` to inspect one channel; neither returns the project touch-limit rule list.
+- Use `engage-setting channel list` to list channels and `engage-setting channel get` to inspect one channel; neither returns the project touch-limit rule list.
 - If `items` is empty, do not invent rule IDs or channel IDs; report that no touch-limit rules were returned for the project.