@thinkingai/ae-cli 6.0.31 → 6.0.33

package/skills/ae-community/references/community-data-report.md

@@ -0,0 +1,301 @@
+# Community Data Reporting
+
+Use `ae-cli community data report` to validate, normalize, and submit community records directly to an authorized Iris ingress endpoint. This is an ingestion data-plane command, not an AE analysis-host command.
+
+## Contents
+
+- [Safety and delivery contract](#safety-and-delivery-contract)
+- [Endpoint and identifiers](#endpoint-and-identifiers)
+- [Input modes](#input-modes)
+- [Chat example](#chat-example)
+- [Mixed payload example](#mixed-payload-example)
+- [Common record rules](#common-record-rules)
+- [Schemas](#schemas)
+- [Normalization](#normalization)
+- [Dry-run and output](#dry-run-and-output)
+- [Errors and retry policy](#errors-and-retry-policy)
+- [Privacy](#privacy)
+
+## Safety and delivery contract
+
+- The command has `risk: write`. A clear user request to report the data is sufficient; do not add `--yes` or ask for a second confirmation.
+- Run a redacted `--dry-run` before the first submission of a dataset.
+- A successful response means only that Iris queued the request. It does not prove that every record passed asynchronous processing or reached durable storage.
+- Never describe `status: "queued"` as accepted, imported, persisted, or queryable.
+- The client makes at most one POST, never follows redirects, and never retries automatically.
+- After a timeout, the delivery state is unknown. Check the downstream query or storage side before deciding whether a manual resubmission is safe.
+
+## Endpoint and identifiers
+
+The endpoint precedence is:
+
+1. `--endpoint`
+2. `AE_IRIS_SYNC_ENDPOINT`
+
+The endpoint must be a complete `http` or `https` URL whose path ends in `/sync_content`. It must not contain credentials, a query string, or a fragment. Never guess, concatenate, or derive this URL from `--host`; `--host` is unrelated to this command.
+
+Verify all three identifiers with the user or an authoritative system:
+
+| Flag | Iris field | Contract |
+|------|------------|----------|
+| `--space-id` | `game_id` | Positive signed int64 |
+| `--channel-id` | `channel_id` | Positive signed int64 |
+| `--source-id` | `source_id` | Positive signed int64 |
+
+The CLI reads these flags as strings to preserve precision, then emits JSON numeric values without quotes. It fixes `source_type` to `#standard` and `version` to `5.0.0`. `--zone-id` defaults to `Asia/Shanghai` and accepts a valid IANA time-zone ID.
+
+The reporting command does not provide a `--game-id` alias. It also does not accept `zone_offset` or top-level `timestamp`/`datetime` request overrides.
+
+## Input modes
+
+Choose exactly one mode:
+
+```text
+--data-type <type> --data <inline|path|@path|->
+--payload <inline|path|@path|->
+```
+
+`--data` accepts one record object or a non-empty record array. `--payload` accepts one segment object or a non-empty segment array. A segment has this shape:
+
+```json
+{
+  "data_type": "chat",
+  "data": [
+    { "chat_uuid": "example" }
+  ]
+}
+```
+
+Supported `data_type` values are `post`, `video`, `reply`, `danmu`, `live_room`, `live_interaction`, `chat`, and `interaction`.
+
+Before constructing records, run `ae-cli community data report --help`. The installed command's schema summary is the source of truth for the required fields of every supported `data_type`; use the schema sections below for field limits and normalization behavior.
+
+For either input flag:
+
+- Inline JSON is accepted for non-sensitive examples.
+- `@path/to/file.json` is the preferred, unambiguous file form.
+- A plain existing path is also accepted.
+- `-` reads JSON from stdin.
+- JSONL is not supported.
+
+## Chat example
+
+Store records in `chat.json` so message content does not enter shell history:
+
+```json
+[
+  {
+    "chat_uuid": "wecom-chat-0001",
+    "user_id": "user-001",
+    "user_name": "Example User",
+    "chat_room_type": "wecom_group",
+    "chat_room_id": "room-001",
+    "chat_room": "Example support group",
+    "content": "Example redacted message",
+    "publish_time": "2026-07-21 09:30:00",
+    "extras": {
+      "source": "wecom"
+    }
+  }
+]
+```
+
+Run the redacted preview, then submit only if the endpoint and IDs are verified:
+
+```bash
+ae-cli --dry-run community data report \
+  --endpoint https://<iris-ingress>/sync_content \
+  --space-id <space-id> \
+  --channel-id <channel-id> \
+  --source-id <source-id> \
+  --data-type chat \
+  --data @chat.json
+
+ae-cli community data report \
+  --endpoint https://<iris-ingress>/sync_content \
+  --space-id <space-id> \
+  --channel-id <channel-id> \
+  --source-id <source-id> \
+  --data-type chat \
+  --data @chat.json
+```
+
+## Mixed payload example
+
+Use `--payload` when one request contains multiple data types. For example, `mixed.json` can contain a post with a sidecar interaction plus a standalone interaction snapshot:
+
+```json
+[
+  {
+    "data_type": "post",
+    "data": [
+      {
+        "post_uuid": "post-0001",
+        "user_id": "author-001",
+        "title": "Example post",
+        "content": "Example body",
+        "publish_time": "2026-07-21 10:00:00",
+        "interaction": {
+          "collect_time": "2026-07-21 10:05:00",
+          "metrics": {
+            "views": 100,
+            "likes": 8
+          }
+        }
+      }
+    ]
+  },
+  {
+    "data_type": "interaction",
+    "data": [
+      {
+        "content_uuid": "post-0001",
+        "content_type": 0,
+        "collect_time": "2026-07-21 11:00:00",
+        "metrics": {
+          "views": "125",
+          "comments": 3
+        }
+      }
+    ]
+  }
+]
+```
+
+```bash
+AE_IRIS_SYNC_ENDPOINT=https://<iris-ingress>/sync_content \
+  ae-cli --dry-run community data report \
+  --space-id <space-id> --channel-id <channel-id> --source-id <source-id> \
+  --payload @mixed.json
+```
+
+## Common record rules
+
+- Each record and segment must be a JSON object; arrays must be non-empty.
+- Text fields accept only JSON strings. Numbers and booleans are not coerced to text.
+- Optional `null` fields are treated as omitted.
+- Unknown record fields are preserved.
+- Signed int64 inputs may be JSON integer numbers or canonical decimal strings. The wire body contains lossless, unquoted JSON numbers.
+- Fields constrained to non-negative int64 reject negative values, fractions, and values above `9223372036854775807`.
+- Date/time strings accept only `yyyy-MM-dd HH:mm:ss`, `yyyy-MM-dd HH:mm:ss.SSS`, `yyyy-MM-dd HH:mm`, or `yyyy-MM-dd` where the field permits a date-only value.
+- `extras` and `user_extra` accept an object or a JSON-encoded object string. Missing, null, or invalid values normalize to `{}`. Serialized `user_extra` must not exceed 1024 UTF-16 code units.
+- `subtitle` accepts an object array or a JSON-encoded object array. Every element must be an object.
+- Lengths and truncation use UTF-16 code units, matching Iris/Java string behavior.
+- A field with an Iris truncation fallback is truncated and counted in normalization statistics. An overlong field without a fallback is rejected.
+
+## Schemas
+
+Only the key ingestion constraints are listed below. Unknown fields remain on the record after validation.
+
+### `post`
+
+Required: `post_uuid`, a string no longer than 32 UTF-16 code units.
+
+Optional normalized fields include `user_id` (64), `user_name` (80), `title` (200), `content` (65533), `publish_time`, and `extras`. Values in parentheses are truncation limits. An optional `interaction` sidecar requires `collect_time` and a non-empty `metrics` object using the same metric rules as standalone `interaction` with `content_type=0`.
+
+### `video`
+
+Required: `video_uuid`, a string no longer than 32 UTF-16 code units.
+
+Optional normalized fields include `user_id` (64), `user_name` (80), `title` (1000), `description` (65533), `publish_time`, `subtitle`, and `extras`. An optional `interaction` sidecar uses the standalone metric rules with `content_type=1`.
+
+### `reply`
+
+Required: `reply_uuid` (maximum 32), `root_id` (maximum 32), and `root_type`, which must be `post`, `video`, or `live`.
+
+Optional normalized fields include `user_id` (64), `user_name` (80), `content` (65533), `publish_time`, `parent_id` (32), and `extras`.
+
+### `danmu`
+
+Required: `danmu_uuid` (maximum 32), non-negative int64 `timestamp`, `root_id` (maximum 32), and `root_type`, which must be `post`, `video`, or `live`.
+
+Optional normalized fields include `user_id` (64), `user_name` (80), `content` (65533), and `publish_time`.
+
+### `live_room`
+
+Required: non-negative int64 `uuid`, `room_id` (maximum 32), `room_name` (maximum 80), `room_avatar` (maximum 65533), non-negative int64 `fans`, and date/time `timestamp`.
+
+Optional room/stream fields include `room_type` (truncated to 128), `stream_cover` (65533), `stream_title` (80), `stream_status`, `stream_start_time`, `stream_end_time`, and `stream_notice` (maximum 255, rejected if longer). Missing or `2` `stream_status` becomes `0`; only normalized values `0` and `1` are allowed.
+
+The optional metrics `online`, `heat`, `noble_count`, `guardian_count`, `diamond_fan_count`, and `dfans_count` are non-negative int64 values. At most one of the three guardian aliases may be present. If stream details or metrics are present, `stream_start_time` is required and must include a time component; a date-only value is rejected. The derived `stream_id` must not exceed 64 UTF-16 code units, and every derived metric ID (`uuid * 5 + metric_type`) must remain within signed int64 range.
+
+### `live_interaction`
+
+Required: non-negative int64 `uuid`, `activity_type`, `activity_content`, `room_id`, `stream_start_time`, and date/time `timestamp`.
+
+`activity_type` must be `danmu`, `gift`, `superchat`, or `premium`. `activity_content` is truncated to 1024. `room_id` is at most 32. `stream_start_time` must include a time component. Optional normalized fields include `user_id` (80), `user_name` (80), and `user_extra`.
+
+### `chat`
+
+The six required string fields are:
+
+| Field | Limit |
+|-------|-------|
+| `chat_uuid` | 36 UTF-16 code units; overlong values are truncated |
+| `user_id` | 80 |
+| `chat_room_type` | 16; no enum restriction |
+| `chat_room_id` | 80 |
+| `content` | 65533 |
+| `publish_time` | One supported date/time format |
+
+Optional normalized fields are `user_name`, `chat_room`, `chat_server`, and `chat_server_id` (each 80), plus `extras`.
+
+`chat_uuid` is a required JSON string. If it exceeds 36 UTF-16 code units, the client keeps the first 36 units and reports the change under `chat.chat_uuid` in the normalization statistics; it does not reject the record for length. Supply source identifiers that already fit the limit to avoid truncation changing record identity or collapsing distinct identifiers to the same normalized value.
+
+### `interaction`
+
+Required: `content_uuid` (maximum 32), integer `content_type` from 0 through 7, `collect_time`, and a non-empty `metrics` object.
+
+Every metric value must be a non-negative int64. A single invalid metric rejects the whole record; it is never silently dropped. Metric names must match `content_type`:
+
+| `content_type` | Meaning | Allowed metric names |
+|----------------|---------|----------------------|
+| `0`, `1` | post, video | `views`, `likes`, `comments`, `shares`, `favorites`, `coins`, `danmaku`, `dislikes` |
+| `2`-`6` | live, chat, comment, reply, danmu | `favorites`, `coins`, `danmaku`, `dislikes` |
+| `7` | user | `followers`, `total_views`, `total_likes` |
+
+## Normalization
+
+The CLI normalizes the input before dry-run or submission:
+
+- A single record becomes a one-element `data` array; a single segment becomes a one-element `payload` array.
+- Fixed request metadata is `source_type: "#standard"` and `version: "5.0.0"`.
+- Integer strings become lossless JSON numeric literals.
+- Optional `null` properties are removed.
+- Fields with Iris truncation fallbacks are truncated by UTF-16 code units.
+- Invalid or missing `extras`/`user_extra` becomes `{}`; encoded objects and `subtitle` arrays become native JSON structures.
+- Missing or legacy `stream_status: 2` becomes `0`.
+
+The summary counts truncated, defaulted, and integer-converted fields without exposing their original values.
+
+## Dry-run and output
+
+`--dry-run` performs local parsing, schema validation, and normalization, but sends no network request. Its redacted output contains endpoint, data types, segment/record counts, encoded byte count, and normalization statistics. It never prints the business payload.
+
+A successful live submission has these semantics:
+
+```json
+{
+  "status": "queued",
+  "persistence_verified": false,
+  "next_step": "After asynchronous processing, verify the submitted record identifiers through an authorized downstream query or storage path before treating this submission as persisted."
+}
+```
+
+The complete output also reports submission counts and normalization statistics. Treat them as submitted-to-queue counts, not per-record acceptance counts. Iris does not currently return a query URL or trace ID in this response, so the CLI does not invent one; use the submitted identifiers with an authorized downstream query or storage path.
+
+## Errors and retry policy
+
+- Input, schema, file, identifier, and endpoint failures use a `validation` error envelope. Locations identify segment, record, and field but do not echo the invalid business value.
+- Iris HTTP 400 errors expose the safe `return_message` when available.
+- HTTP 5xx responses, non-JSON responses, missing `return_code`, non-zero `return_code`, redirects, and buffer-full responses use a standard API error envelope. Server stack traces are not echoed.
+- The request timeout is 30 seconds. A timeout does not establish whether Iris queued the request.
+- Never automate a retry. For timeout or ambiguous transport failure, check downstream state first and ask the user before any deliberate resubmission.
+
+## Privacy
+
+- Prefer `@file` or stdin for chat text, usernames, identifiers, and other sensitive content. Inline JSON can remain in shell history or process listings.
+- The reporting client sends only `Content-Type: application/json` and `Accept: application/json`. It does not send AE access tokens, CLI tokens, or custom authorization headers.
+- Request and response bodies are excluded from CLI HTTP logs. Logs contain only endpoint, status, and byte counts.
+- Dry-run output is redacted by default. Do not paste raw records into reports or error explanations.
+- An endpoint URL must not contain embedded credentials, query parameters, or fragments.

package/skills/ae-dataops/SKILL.md

@@ -39,8 +39,9 @@ Global parameters:
 | `--host <url>` | Override the active AE host. Available on every command and may be placed after the subcommand, e.g. `ae-cli dataops_ide +<command> --host <url>`. |
 
 Output and errors:
-- Successful commands return machine-readable JSON by default.
+- Successful commands return machine-readable JSON by default. Envelope may include optional `_notice.host_compat`.
 - Failed commands return `{ "ok": false, "error": { "type": "...", "message": "...", "hint": "..." } }` and exit non-zero.
+- **CRITICAL — Host compat (do this first):** After each `ae-cli` run, check stderr and `_notice.host_compat`. If either is present, open the user reply with a short ⚠️ version warning and **quote the `npm i -g` / `npx skills add` (or update-cluster) lines verbatim**, then present the business result. Soft tip; `ok: true` can still carry the notice.
 
 Safety constraints:
 - Read commands can execute directly after required IDs and references are verified.

package/skills/ae-engage/SKILL.md

@@ -21,8 +21,9 @@ Global parameters:
 | `--host <url>` | Override the active AE host. Available on every command and may be placed after the subcommand, e.g. `ae-cli engage +<command> --host <url>`. |
 
 Output and errors:
-- Successful commands return machine-readable JSON by default.
+- Successful commands return machine-readable JSON by default. Envelope may include optional `_notice.host_compat`.
 - Failed commands return `{ "ok": false, "error": { "type": "...", "message": "...", "hint": "..." } }` and exit non-zero.
+- **CRITICAL — Host compat (do this first):** After each `ae-cli` run, check stderr and `_notice.host_compat`. If either is present, open the user reply with a short ⚠️ version warning and **quote the `npm i -g` / `npx skills add` (or update-cluster) lines verbatim**, then present the business result. Soft tip; `ok: true` can still carry the notice.
 
 Safety constraints:
 - Read commands can execute directly after required IDs and references are verified.
@@ -76,6 +77,53 @@ ae-cli engage +config_channel_list --project_id 1
 
 # Query project channel touch-limit rules
 ae-cli engage-setting channel-touch-limits list --project-id <project_id>
+
+# Update a channel's config / reach-funnel settings
+ae-cli engage-setting channel update-config --project-id <project_id> --channel-id <channel_id> --enable-touch-event 1
+
+# Send a test message to a channel
+ae-cli engage-setting channel test-send --project-id <project_id> --channel-id <channel_id> --push-id <send_id> --content-list '[{"key":"title","value":"hello"}]'
+
+# Batch update / toggle / save channel touch-limit (fatigue-control) rules
+ae-cli engage-setting channel-touch-limits batch-update --project-id <project_id> --items '[{"rule_id":"r1","enable":true,"rule_def":"[]"}]'
+ae-cli engage-setting channel-touch-limits toggle --project-id <project_id> --rule-id <rule_id> --enable false
+ae-cli engage-setting channel-touch-limits save --project-id <project_id> --channel-biz-type <biz_type> --rule-def '[]' --enable true
+
+# Remove an approver from a project
+ae-cli engage-setting approval-approver delete --project-id <project_id> --approver <open_id> --yes
+
+# Whitelist add / update / delete / verify
+ae-cli engage-setting whitelist add --project-id <project_id> --prop-code <prop_code> --column-name <column_name> --column-type string --whitelist-list '[{"entity_id":"u1","source_value":"v1"}]'
+ae-cli engage-setting whitelist update --project-id <project_id> --whitelist-id <id> --note-name <name>
+ae-cli engage-setting whitelist delete --project-id <project_id> --whitelist-ids '["wl-1"]' --yes
+ae-cli engage-setting whitelist verify --project-id <project_id> --prop-code <prop_code> --column-type string --whitelist-prop-list '["v1"]'
+
+# Push-language (本地化) get / set
+ae-cli engage-setting push-language get --project-id <project_id>
+ae-cli engage-setting push-language set --project-id <project_id> --push-language-column <prop_code>
+
+# Client param (客户端参数) update / delete / list
+ae-cli engage-setting client-param update --project-id <project_id> --column-name level --column-type string --select-type single --column-desc Level
+ae-cli engage-setting client-param delete --project-id <project_id> --column-name level --yes
+ae-cli engage-setting client-param list --project-id <project_id>
+
+# Config table (配置表) upload / save / list / query-data / update-data / delete
+ae-cli engage-setting config-table upload --project-id <project_id> --request-id <rid> --file-name data.csv --file-content "$(base64 -i data.csv)"
+ae-cli engage-setting config-table save --project-id <project_id> --request-id <rid> --info-name <table_name>
+ae-cli engage-setting config-table list --project-id <project_id>
+ae-cli engage-setting config-table query-data --project-id <project_id> --info-id <info_id>
+ae-cli engage-setting config-table update-data --project-id <project_id> --request-id <rid> --info-name <table_name> --info-id <info_id>
+ae-cli engage-setting config-table delete --project-id <project_id> --info-id <info_id> --yes
+
+# Preset event (预置事件) list / update
+ae-cli engage-setting preset-event list --project-id <project_id>
+ae-cli engage-setting preset-event update --project-id <project_id> --add-event-desc <qp>
+
+# Common metric (常用指标) list / get / update / delete
+ae-cli engage-setting common-metric list --project-id <project_id>
+ae-cli engage-setting common-metric get --project-id <project_id> --metric-name <name>
+ae-cli engage-setting common-metric update --project-id <project_id> --metric-type <type> --metric-name <name> --metric-qp <qp> --metric-window-num 1 --metric-window-time-unit DAY --display-name <display>
+ae-cli engage-setting common-metric delete --project-id <project_id> --metric-name <name> --yes
 ```
 
 ### 2. task
@@ -122,7 +170,7 @@ ae-cli engage +flow_list --project_id 1
 ae-cli engage +flow_detail --project_id 1 --flow_uuid flow_uuid_123
 
 # Query flow operation records and application logs
-ae-cli engage-flow operation-log query --project-id 1 --flow-uuid flow_uuid_123
+ae-cli engage-flow operation-log query --project-id 1 --flow-id flow_id_123
 
 # Query flow versions and task push records
 ae-cli engage-flow version list --project-id 1 --flow-id flow_id_123
@@ -132,12 +180,123 @@ ae-cli engage-task segment-list query --project-id 1 --task-id task_id_123
 ae-cli engage-task group list --project-id 1
 ae-cli engage-task metric list --project-id 1 --task-id task_id_123
 ae-cli engage-task channel-ref stats --project-id 1 --channel-id channel_123
-ae-cli engage-task ops delete --project-id 1 --task-id task_id_123 --yes
+ae-cli engage-task task delete --project-id 1 --task-id task_id_123 --yes
 
 # Query the node schema
 ae-cli engage +flow_node_config_schema --node_type message_push
 ```
 
+### 5. scene (场景管理 / 配置中心)
+
+New capability-gateway command group `engage-scene` covers 配置中心 (config center): config items, params, groups, preset/related metrics, config channels, strategies, and templates. Complex DTOs are passed with `--payload` (native camelCase JSON).
+
+```bash
+# Config item (配置项) list / create / update
+ae-cli engage-scene config-item list --project-id <project_id>
+ae-cli engage-scene config-item create --project-id <project_id> --config-id <config_id> --config-name <name> --business-type params
+ae-cli engage-scene config-item update --project-id <project_id> --config-id <config_id> --config-name <name>
+
+# Config param (配置项参数) list / batch-add / update / batch-delete
+ae-cli engage-scene config-param list --project-id <project_id> --config-id <config_id>
+ae-cli engage-scene config-param batch-add --project-id <project_id> --config-id <config_id> --params '[{"param_name":"a","param_type":"string"}]'
+ae-cli engage-scene config-param update --project-id <project_id> --config-id <config_id> --param-id <param_id> --param-name a
+ae-cli engage-scene config-param batch-delete --project-id <project_id> --param-ids '[1,2]' --yes
+
+# Config group (配置项分组) list / batch-add / update / batch-delete
+ae-cli engage-scene config-group list --project-id <project_id>
+ae-cli engage-scene config-group batch-add --project-id <project_id> --group-names '["g1"]'
+ae-cli engage-scene config-group update --project-id <project_id> --group-id <group_id> --group-name g2
+ae-cli engage-scene config-group batch-delete --project-id <project_id> --group-ids '[1,2]' --yes
+
+# Preset metric (预置指标) get / set
+ae-cli engage-scene preset-metric get --project-id <project_id> --config-id <config_id>
+ae-cli engage-scene preset-metric set --project-id <project_id> --config-id <config_id> --impression-event-qp '<qp>'
+
+# Config metric (关联指标) list / get / batch-add / update-rule / batch-delete
+ae-cli engage-scene config-metric list --project-id <project_id> --config-id <config_id>
+ae-cli engage-scene config-metric get --project-id <project_id> --metric-id <metric_id>
+ae-cli engage-scene config-metric batch-add --project-id <project_id> --config-id <config_id> --ta-metric-ids '[1,2]'
+ae-cli engage-scene config-metric update-rule --project-id <project_id> --metric-id <metric_id> --event-list '[{"event_name":"e1","filter":"true"}]'
+ae-cli engage-scene config-metric batch-delete --project-id <project_id> --config-id <config_id> --metric-ids '[1,2]' --yes
+
+# Config channel (配置通道) create / update / query-log
+ae-cli engage-scene config-channel create --project-id <project_id> --channel-name <name> --channel-type 0 --config '<json>'
+ae-cli engage-scene config-channel update --project-id <project_id> --channel-id <channel_id> --channel-name <name> [--config '<json>']
+ae-cli engage-scene config-channel query-log --project-id <project_id> --channel-id <channel_id>
+
+# Strategy (策略) create / update / log / batch-copy
+ae-cli engage-scene strategy create --project-id <project_id> --payload '{"configId":"cfg-1","templateId":"tpl-1","strategyName":"s1"}'
+ae-cli engage-scene strategy update --project-id <project_id> --payload '{"strategyUuid":"uuid-1"}'
+ae-cli engage-scene strategy log --project-id <project_id> --strategy-uuid <uuid>
+ae-cli engage-scene strategy batch-copy --project-id <project_id> --config-id <config_id> --strategy-ids '["s1"]'
+
+# Template (模板) list / get / create / update / update-status / delete
+ae-cli engage-scene template list --project-id <project_id> --config-id <config_id>
+ae-cli engage-scene template get --project-id <project_id> --config-id <config_id> --template-id <template_id>
+ae-cli engage-scene template create --project-id <project_id> --payload '{"configId":"cfg-1","templateId":"tpl-1","templateName":"t1"}'
+ae-cli engage-scene template update --project-id <project_id> --payload '{"configId":"cfg-1","templateId":"tpl-1","config":[]}'
+ae-cli engage-scene template update-status --project-id <project_id> --config-id <config_id> --template-id <template_id> --status 1
+ae-cli engage-scene template delete --project-id <project_id> --config-id <config_id> --template-id <template_id> --yes
+```
+
+### 6. activity (运营活动)
+
+New capability-gateway command group `engage-activity` covers 运营活动: activities, approval workflow, topics, activity types, and standalone tasks. Complex DTOs are passed with `--payload` (native camelCase JSON).
+
+```bash
+# Activity (运营活动) create / update / delete / list / get / pause / end / stats / info-list
+ae-cli engage-activity activity create --project-id <project_id> --payload '{"activityName":"a1","activityType":"other_type","tzOffset":8,"periodType":0}'
+ae-cli engage-activity activity update --project-id <project_id> --payload '{"activityId":"act-1","activityName":"a1","activityType":"other_type","tzOffset":8,"periodType":0}'
+ae-cli engage-activity activity delete --project-id <project_id> --activity-id <activity_id> --yes
+ae-cli engage-activity activity list --project-id <project_id> --page 1 --page-size 20
+ae-cli engage-activity activity get --project-id <project_id> --activity-id <activity_id>
+ae-cli engage-activity activity pause --project-id <project_id> --activity-id <activity_id>
+ae-cli engage-activity activity end --project-id <project_id> --activity-id <activity_id>
+ae-cli engage-activity activity stats --project-id <project_id>
+ae-cli engage-activity activity info-list --project-id <project_id> --activity-id <activity_id>
+
+# Approval (活动审批) submit / approve / reject / cancel
+ae-cli engage-activity approval submit --project-id <project_id> --activity-id <activity_id>
+ae-cli engage-activity approval approve --project-id <project_id> --activity-id <activity_id>
+ae-cli engage-activity approval reject --project-id <project_id> --activity-id <activity_id> --reason <reason>
+ae-cli engage-activity approval cancel --project-id <project_id> --activity-id <activity_id>
+
+# Topic (活动主题) remove-task / delete / get / copy
+# Temporarily disabled: topic create / topic update
+# See references/activity-topic.md for topicClusterKey vs task clusterKey and remaining commands.
+# ae-cli engage-activity topic create --project-id <project_id> --payload '{"activityId":"act-1","topicName":"t1","targetClusterType":2,"topicClusterKey":"<cluster>","channelType":1,"channelId":"c1","triggerType":0,"enableChannelTouchLimits":false,"frequencyLimits":"{}","tasks":[...]}'
+# ae-cli engage-activity topic update --project-id <project_id> --payload '{"topicId":"topic-1", ...}'
+ae-cli engage-activity topic remove-task --project-id <project_id> --task-id <task_id> --yes
+ae-cli engage-activity topic delete --project-id <project_id> --topic-id <topic_id> --yes
+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>]
+
+# Activity type (活动类型) list / batch-add / update / batch-delete
+ae-cli engage-activity activity-type list --project-id <project_id>
+ae-cli engage-activity activity-type batch-add --project-id <project_id> --type-names '["t1","t2"]'
+ae-cli engage-activity activity-type update --project-id <project_id> --id <type_id> --type-name t3
+ae-cli engage-activity activity-type batch-delete --project-id <project_id> --ids '["id1","id2"]' --yes
+
+# Standalone task (独立任务) get / copy
+# Temporarily disabled: task create / task update
+ae-cli engage-activity task get --project-id <project_id> --task-id <task_id>
+# ae-cli engage-activity task create --project-id <project_id> --payload '{"taskName":"t1","activityId":"act-1", ...}'
+# ae-cli engage-activity task update --project-id <project_id> --payload '{"taskId":"task-1", ...}'
+ae-cli engage-activity task copy --project-id <project_id> --task-id <task_id> [--new-name <name>]
+```
+
+### 7. workbench (工作台)
+
+New capability-gateway command group `engage-workbench` covers 工作台 metric slots (指标卡槽): each user configures up to 4 metric cards per project. Slots are per-user; `update`/`delete` only affect the caller's own slots. The first `list` auto-initialises 4 default slots.
+
+```bash
+# Workbench slot (工作台卡槽) list / add / update / delete
+ae-cli engage-workbench workbench list --project-id <project_id>
+ae-cli engage-workbench workbench add --project-id <project_id> --metric-type <metric_type> --date-type <date_type> --order-id 1
+ae-cli engage-workbench workbench update --project-id <project_id> --slot-id <slot_id> --metric-type <metric_type> --date-type <date_type> --order-id 1
+ae-cli engage-workbench workbench delete --project-id <project_id> --slot-id <slot_id> --yes
+```
+
 ## `+save_flow` Critical Constraints
 
 When the user wants to "create a flow / generate a flow canvas / save a flow", do not treat `+save_flow` as a normal single command. You must follow the workflow below.
@@ -215,6 +374,32 @@ More detailed single-command guidance is available in the business-oriented `ref
 
 - `references/channel-list.md`
 - `references/channel_touch_limits_list.md` (`engage-setting.channel-touch-limits.list`)
+- `references/channel-touch-limits-batch-update.md` (`engage-setting.channel-touch-limits.batch-update`)
+- `references/channel-touch-limits-toggle.md` (`engage-setting.channel-touch-limits.toggle`)
+- `references/channel-touch-limits-save.md` (`engage-setting.channel-touch-limits.save`)
+- `references/channel-update-config.md` (`engage-setting.channel.update-config`)
+- `references/channel-test-send.md` (`engage-setting.channel.test-send`)
+- `references/approval-approver-delete.md` (`engage-setting.approval-approver.delete`)
+- `references/whitelist.md` (`engage-setting.whitelist.{add,update,delete,verify}`)
+- `references/push-language.md` (`engage-setting.push-language.{get,set}`)
+- `references/client-param.md` (`engage-setting.client-param.{update,delete,list}`; create temporarily disabled)
+- `references/config-table.md` (`engage-setting.config-table.{upload,save,list,query-data,update-data,delete}`)
+- `references/preset-event.md` (`engage-setting.preset-event.{list,update}`)
+- `references/common-metric.md` (`engage-setting.common-metric.{list,get,update,delete}`; create temporarily disabled)
+- `references/scene-config-item.md` (`engage-scene.config-item.{list,create,update}`)
+- `references/scene-config-param.md` (`engage-scene.config-param.{list,batch-add,update,batch-delete}`)
+- `references/scene-config-group.md` (`engage-scene.config-group.{list,batch-add,update,batch-delete}`)
+- `references/scene-preset-metric.md` (`engage-scene.preset-metric.{get,set}`)
+- `references/scene-config-metric.md` (`engage-scene.config-metric.{list,get,batch-add,update-rule,batch-delete}`)
+- `references/scene-config-channel.md` (`engage-scene.config-channel.{create,update,query-log}`)
+- `references/scene-strategy.md` (`engage-scene.strategy.{create,update,log,batch-copy}`)
+- `references/scene-template.md` (`engage-scene.template.{list,get,create,update,update-status,delete}`)
+- `references/activity-activity.md` (`engage-activity.activity.{create,update,delete,list,get,pause,end,stats,info-list}`)
+- `references/activity-approval.md` (`engage-activity.approval.{submit,approve,reject,cancel}`)
+- `references/activity-topic.md` (`engage-activity.topic.{remove-task,delete,get,copy}`; create/update temporarily disabled)
+- `references/activity-activity-type.md` (`engage-activity.activity-type.{list,batch-add,update,batch-delete}`)
+- `references/activity-task.md` (`engage-activity.task.{get,copy}`; create/update temporarily disabled)
+- `references/workbench-workbench.md` (`engage-workbench.workbench.{list,add,update,delete}`)
 - `references/build-task-save-guide.md`
 - `references/save-task.md`
 - `references/task-list.md`
@@ -226,7 +411,7 @@ More detailed single-command guidance is available in the business-oriented `ref
 - `references/push-record-query.md` (`engage-task.push-record.query`)
 - `references/segment-list-query.md` (`engage-task.segment-list.query`)
 - `references/group-list.md` (`engage-task.group.list`)
-- `references/ops-delete.md` (`engage-task.ops.delete`)
+- `references/task-delete.md` (`engage-task.task.delete`)
 
 This split documentation structure is easier to extend later, because commands with more complex object inputs can stay centralized in the `references/` root directory.
 
@@ -234,18 +419,29 @@ This split documentation structure is easier to extend later, because commands w
 
 ### setting
 
-`channel-touch-limits list` (via `engage-setting`), `+channel_list`, `+channel_detail`, `+update_channel_status`, `+delete_channel`, `+add_channel`, `+whitelist_list`, `+add_approver`, `+approver_list`, `+cancel_query_by_request_id`, `+config_channel_detail`, `+config_channel_list`, `+delete_config_channel`, `+update_config_channel_status`
+`channel-touch-limits list` / `channel-touch-limits batch-update` / `channel-touch-limits toggle` / `channel-touch-limits save` / `channel update-config` / `channel test-send` / `approval-approver delete` / `whitelist add` / `whitelist update` / `whitelist delete` / `whitelist verify` / `push-language get` / `push-language set` / `client-param update` / `client-param delete` / `client-param list` / `config-table upload` / `config-table save` / `config-table list` / `config-table query-data` / `config-table update-data` / `config-table delete` / `preset-event list` / `preset-event update` / `common-metric list` / `common-metric get` / `common-metric update` / `common-metric delete` (via `engage-setting`), `+channel_list`, `+channel_detail`, `+update_channel_status`, `+delete_channel`, `+add_channel`, `+whitelist_list`, `+add_approver`, `+approver_list`, `+cancel_query_by_request_id`, `+config_channel_detail`, `+config_channel_list`, `+delete_config_channel`, `+update_config_channel_status`
 
 ### task
 
-`operation-log query` / `push-record query` / `segment-list query|get|rename` / `ops delete|modify-group` / `metric list|update` / `channel-ref stats` / `group list|create|update` (via `engage-task`), `+task_data_overview`, `+task_data_detail`, `+task_metric_detail`, `+task_experiment_report`, `+task_detail`, `+task_list`, `+task_stats`, `+build_task_save_guide`, `+save_task`, `+manage_task`
-
-> Temporarily disabled engage-task commands (do not use): `group delete`, `segment-list set-visibility`, `ops submit-approval`, `race release`.
+`operation-log query` / `push-record query` / `segment-list *` / `ops *` / `metric *` / `race release` / `channel-ref stats` / `group *` (via `engage-task`), `+task_data_overview`, `+task_data_detail`, `+task_metric_detail`, `+task_experiment_report`, `+task_detail`, `+task_list`, `+task_stats`, `+build_task_save_guide`, `+save_task`, `+manage_task`
 
 ### config
 
 `+config_item_trigger_report`, `+config_item_analysis_report`, `+config_item_strategy_comparison`, `+config_item_list`, `+config_item_detail`, `+delete_config_item`, `+copy_config_template`, `+strategy_list`, `+strategy_detail`, `+manage_strategy`
 
+### scene
+
+`config-item list` / `config-item create` / `config-item update` / `config-param list` / `config-param batch-add` / `config-param update` / `config-param batch-delete` / `config-group list` / `config-group batch-add` / `config-group update` / `config-group batch-delete` / `preset-metric get` / `preset-metric set` / `config-metric list` / `config-metric get` / `config-metric batch-add` / `config-metric update-rule` / `config-metric batch-delete` / `config-channel create` / `config-channel update` / `config-channel query-log` / `strategy create` / `strategy update` / `strategy log` / `strategy batch-copy` / `template list` / `template get` / `template create` / `template update` / `template update-status` / `template delete` (via `engage-scene`), capability ids `engage-scene.config-item.{list,create,update}`, `engage-scene.config-param.{list,batch-add,update,batch-delete}`, `engage-scene.config-group.{list,batch-add,update,batch-delete}`, `engage-scene.preset-metric.{get,set}`, `engage-scene.config-metric.{list,get,batch-add,update-rule,batch-delete}`, `engage-scene.config-channel.{create,update,query-log}`, `engage-scene.strategy.{create,update,log,batch-copy}`, `engage-scene.template.{list,get,create,update,update-status,delete}`
+
+### activity
+
+`activity create` / `activity update` / `activity delete` / `activity list` / `activity get` / `activity pause` / `activity end` / `activity stats` / `activity info-list` / `approval submit` / `approval approve` / `approval reject` / `approval cancel` / `topic remove-task` / `topic delete` / `topic get` / `topic copy` / `activity-type list` / `activity-type batch-add` / `activity-type update` / `activity-type batch-delete` / `task get` / `task copy` (via `engage-activity`), capability ids `engage-activity.activity.{create,update,delete,list,get,pause,end,stats,info-list}`, `engage-activity.approval.{submit,approve,reject,cancel}`, `engage-activity.topic.{remove-task,delete,get,copy}`, `engage-activity.activity-type.{list,batch-add,update,batch-delete}`, `engage-activity.task.{get,copy}`
+<!-- Temporarily disabled: topic create / topic update / task create / task update -->
+
+### workbench
+
+`workbench list` / `workbench add` / `workbench update` / `workbench delete` (via `engage-workbench`), capability ids `engage-workbench.workbench.{list,add,update,delete}`
+
 ### flow
 
 `operation-log query` / `version list` (via `engage-flow`), `+save_flow`, `+flow_node_config_schema`, `+flow_detail`, `+flow_list`, `+flow_node_overview_report`, `+manage_flow`, `+flow_ab_split_node_report`, `+flow_process_report`, `+validate_flow_node_config`, `+flow_node_detail_report`, `+delete_flow`, `+modify_flow_base_info`

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

@@ -0,0 +1,42 @@
+# engage-activity activity-type
+
+> Capability ids: `engage-activity.activity-type.{list,batch-add,update,batch-delete}` · Domain: `engage`.
+
+运营活动 - 活动类型（系统 + 自定义）。批量增删在 capability service 内循环调用现有单条后端方法（无批量后端 API）。
+
+## Commands
+
+```bash
+# List activity types
+ae-cli engage-activity activity-type list --project-id <project_id>
+
+# Batch-add custom activity types
+ae-cli engage-activity activity-type batch-add --project-id <project_id> --type-names '["t1","t2"]'
+
+# Update a custom activity type name
+ae-cli engage-activity activity-type update --project-id <project_id> --id <type_id> --type-name t3
+
+# Batch-delete custom activity types (high-risk)
+ae-cli engage-activity activity-type batch-delete --project-id <project_id> --ids '["id1","id2"]' --yes
+```
+
+## Parameters
+
+| Command | Required flags | Notes |
+|---|---|---|
+| list | `--project-id` | read. |
+| batch-add | `--project-id`, `--type-names` | `--type-names` = JSON array of names. |
+| update | `--project-id`, `--id`, `--type-name` | write. |
+| batch-delete | `--project-id`, `--ids` | high-risk; `--ids` = JSON array; requires `--yes`; no dry-run. |
+
+## Output
+
+- `list`: `data.total`, `data.items`.
+- `batch-add`: `data.total`, `data.ids`.
+- `update`: `data.success`.
+- `batch-delete`: `data.total`, `data.deleted`.
+
+## Decision Rules
+
+- `batch-delete` is `high-risk-write` — requires `--yes`, no dry-run; loops single delete (non-atomic).
+- Only custom types are editable; system types are read-only.