@thinkingai/ae-cli 6.0.30 → 6.0.32

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

@@ -0,0 +1,98 @@
+# 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).
+
+Activity topics and tasks under a topic. `copy` loads the source topic, renames it, and re-creates (no dedicated backend copy API).
+
+## Commands
+
+```bash
+# Remove a task from its topic (high-risk)
+ae-cli engage-activity topic remove-task --project-id <project_id> --task-id <task_id> --yes
+
+# Delete a topic (high-risk)
+ae-cli engage-activity topic delete --project-id <project_id> --topic-id <topic_id> --yes
+
+# Get a topic detail
+ae-cli engage-activity topic get --project-id <project_id> --topic-id <topic_id>
+
+# Copy a topic (loads detail, renames, re-creates)
+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 |
+|---|---|---|
+| 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
+
+TEXT (rich text) params inside `groupContentList[].contentList[].content` need both `value` and Slate `config` (JSON string). If `config` is omitted, Hermes copy 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.
+
+## Output
+
+- `get`: `data.topic` (includes `topicClusterKey` for topic audience).
+- `remove-task` / `delete` / `copy`: `data.success`.
+- `copy` may include `data.trigger_time_stale=true` when source schedule-single time is already past.
+
+## Decision Rules
+
+- `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`.
+- Prefer `topic get` as a template when inspecting channel/content fields.
+
+## 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.":
+
+| code | when |
+|---|---|
+| `TOPIC_NOT_FOUND` | source `topic_id` missing |
+| `TOPIC_PROJECT_MISMATCH` | topic exists but not in `--project-id` |
+| `ACTIVITY_ID_REQUIRED` | source topic detail has no `activityId` |
+| `ACTIVITY_NOT_FOUND` | parent activity missing / deleted / wrong project |
+| `TOPIC_TASKS_REQUIRED` | source topic has no tasks |
+| `ACTIVITY_STATUS_INVALID` | parent activity is approving/working/complete |
+| `TOPIC_COUNT_LIMIT` | activity topic count limit exceeded |
+| `CHANNEL_NOT_FOUND` | source channel missing / type mismatch |
+| `TASK_COUNT_LIMIT` | project task count limit exceeded |
+| `RCC_SERVER_REQUIRED` | client push (`channelType=3`) but RCC server is not installed |
+| `TRIGGER_TIME_REQUIRED` | schedule-single missing `triggerTime` |
+
+Past `triggerTime` no longer fails copy; check `data.trigger_time_stale` and fix before approval.
+
+## remove-task errors
+
+| code | when |
+|---|---|
+| `TASK_NOT_FOUND` | `--task-id` missing |
+| `TASK_PROJECT_MISMATCH` | task exists but not in `--project-id` |
+| `NOT_TOPIC_TASK` | task has no `topicId` (standalone); use `engage-task task delete` |
+| `TASK_WORKING` | topic task `mappingStatus=working`; pause/end first |
+| `TASK_APPROVING` | topic task pending approval; withdraw first |

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

@@ -0,0 +1,26 @@
+# engage-setting approval-approver delete
+
+> Capability id: `engage-setting.approval-approver.delete` · Domain: `engage`.
+
+## Command
+
+```bash
+ae-cli engage-setting approval-approver delete --project-id <project_id> --approver <open_id> --yes
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--approver` | Yes | OpenID of the approver to remove. |
+
+## Output
+
+- `data.success`: whether the approver was removed.
+
+## 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.
+- Risk is `high-risk-write`; the CLI confirmation gate requires `--yes` (or interactive confirmation) before executing.

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

@@ -14,10 +14,11 @@ 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 '{...}'`.
-3. If the guide says QP-derived fields are required, call:
+3. If the guide says an audience or QP-derived fields are required, create the audience directly and read it back:
 
 ```bash
-ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
+ae-cli analysis user-cluster create --project-id <projectId> --cluster-name <condition_cluster_name> --display-name <display_name> --definition-request '<semantic-definition-json>'
+ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<condition_cluster_name>"]'
 ```
 
 4. Build the final grouped `save_task.req`.
@@ -25,8 +26,8 @@ ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
 
 Important:
 
-- Do not treat the audience schema query as a fixed preflight step.
-- Call it only when the guide indicates that you need to construct:
+- Do not treat audience creation as a fixed preflight step.
+- Create/read the audience only when the guide indicates that you need to construct:
   - `targetConfig.qp`
   - `triggerConfig.triggerRule`
   - `clientConfig.clientQp`
@@ -175,7 +176,7 @@ This section describes the high-level contract:
 
 - final tool is `save_task`
 - required preflight is `query_channel_list -> build_task_save_guide`
-- QP-derived fields may require `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition`
+- QP-derived fields require a server-authored audience: direct `analysis user-cluster create`, followed by `analysis user-cluster get`
 - `save_task.req` must be a grouped JSON object
 
 ### 4.6 `scenario`
@@ -263,13 +264,14 @@ Recommended usage pattern:
 3. read `fieldRules.channelContentSchema`
 4. read `handoff.reqTemplate`
 5. fix everything in `blockingPlaceholders`
-6. if the guide points to QP-derived fields, call:
+6. if the guide points to an audience or QP-derived fields, call:
 
 ```bash
-ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
+ae-cli analysis user-cluster create --project-id <projectId> --cluster-name <condition_cluster_name> --display-name <display_name> --definition-request '<semantic-definition-json>'
+ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<condition_cluster_name>"]'
 ```
 
-7. fill those fields using the real condition schema
+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`
 
 ---
@@ -278,6 +280,6 @@ ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
 
 - `+build_task_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 audience schema query as mandatory for every task
+- do not treat the semantic cluster definition builder as mandatory for every task
 - do not invent `channelId`, `clusterKey`, content keys, or QP structures
 - if the guide exposes an unsupported scenario, correct it before calling `save_task`

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

@@ -0,0 +1,37 @@
+# engage-setting channel test-send
+
+> Capability id: `engage-setting.channel.test-send` · Domain: `engage`.
+
+## Command
+
+```bash
+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"}]' \
+  [--user-params-list '<json_array>'] [--push-environment dev|pro] \
+  [--mock-push] [--channel-template-id <id>]
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-id` | Yes | Channel ID to test. |
+| `--push-id` | Yes | Recipient send ID (e.g. a test device id). |
+| `--content-list` | Yes | JSON array of key/value content pairs, e.g. `[{"key":"title","value":"hello"}]`. |
+| `--user-params-list` | No | JSON array of custom user params for the test push. |
+| `--push-environment` | No | Push environment: `dev` or `pro`. |
+| `--mock-push` | No | Mock the push (build request only, do not send). |
+| `--channel-template-id` | No | WeChat channel template ID. |
+
+## Output
+
+- `data.push_succeeded`: whether the test push succeeded.
+
+## 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.
+- `--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-touch-limits-batch-update.md

@@ -0,0 +1,28 @@
+# engage-setting channel-touch-limits batch-update
+
+> Capability id: `engage-setting.channel-touch-limits.batch-update` · Domain: `engage`.
+
+## Command
+
+```bash
+ae-cli engage-setting channel-touch-limits batch-update \
+  --project-id <project_id> \
+  --items '[{"rule_id":"r1","enable":true,"rule_def":"[]"},{"rule_id":"r2","enable":false,"rule_def":"[]"}]'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--items` | Yes | JSON array of rule updates. Each item: `rule_id`, `enable` (boolean), `rule_def` (rule definition JSON string). |
+
+## Output
+
+- `data.success`: whether the batch update succeeded.
+
+## Decision Rules
+
+- Use this command when the user asks to batch edit/update multiple touch-limit (fatigue-control) rules at once.
+- Discover existing rule IDs with `ae-cli engage-setting channel-touch-limits list --project-id <project_id>` first; never invent rule IDs.
+- Risk is `write`; ordinary update, no confirmation gate.

package/skills/ae-engage/references/channel-touch-limits-save.md

@@ -0,0 +1,37 @@
+# engage-setting channel-touch-limits save
+
+> Capability id: `engage-setting.channel-touch-limits.save` · Domain: `engage`.
+
+## Command
+
+```bash
+# Create a new touch-limit rule (omit --rule-id)
+ae-cli engage-setting channel-touch-limits save \
+  --project-id <project_id> --channel-biz-type <biz_type> \
+  --rule-def '<rule_def_json>' --enable true
+
+# Update an existing touch-limit rule (provide --rule-id)
+ae-cli engage-setting channel-touch-limits save \
+  --project-id <project_id> --channel-biz-type <biz_type> \
+  --rule-def '<rule_def_json>' --enable false --rule-id <rule_id>
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-biz-type` | Yes | Channel business type the rule belongs to. |
+| `--rule-def` | Yes | Touch-limit rule definition (JSON string, see ChannelTouchLimitRuleDTO). |
+| `--enable` | Yes | Whether the touch-limit rule is enabled. |
+| `--rule-id` | No | Existing rule ID. When omitted a new rule is created. |
+
+## Output
+
+- `data.success`: whether the save succeeded.
+
+## Decision Rules
+
+- Use this command when the user asks to create or update a single touch-limit (fatigue-control) rule.
+- For updates, discover the real rule ID with `ae-cli engage-setting channel-touch-limits list --project-id <project_id>` first.
+- Risk is `write`; ordinary write, no confirmation gate.

package/skills/ae-engage/references/channel-touch-limits-toggle.md

@@ -0,0 +1,28 @@
+# engage-setting channel-touch-limits toggle
+
+> Capability id: `engage-setting.channel-touch-limits.toggle` · Domain: `engage`.
+
+## Command
+
+```bash
+ae-cli engage-setting channel-touch-limits toggle \
+  --project-id <project_id> --rule-id <rule_id> --enable <true|false>
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--rule-id` | Yes | Touch-limit rule ID to enable/disable. |
+| `--enable` | Yes | Whether the touch-limit rule is enabled. |
+
+## Output
+
+- `data.success`: whether the toggle succeeded.
+
+## Decision Rules
+
+- Use this command when the user asks to enable or disable a single touch-limit (fatigue-control) rule.
+- Discover the real rule ID with `ae-cli engage-setting channel-touch-limits list --project-id <project_id>` first.
+- Risk is `write`; ordinary update, no confirmation gate.

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

@@ -0,0 +1,36 @@
+# engage-setting channel update-config
+
+> Capability id: `engage-setting.channel.update-config` · Domain: `engage`.
+
+## Command
+
+```bash
+ae-cli engage-setting channel update-config \
+  --project-id <project_id> --channel-id <channel_id> --enable-touch-event <0|1> \
+  [--channel-name <name>] [--push-id-type <prop>] [--config '<json_string>'] \
+  [--touch-event-source <src>] [--event-delivery-name <name>] [--event-click-name <name>]
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-id` | Yes | Channel ID to update. |
+| `--enable-touch-event` | Yes | Reach funnel toggle: `1` enabled, `0` disabled. |
+| `--channel-name` | No | New channel name. |
+| `--push-id-type` | No | User property used as the push ID. |
+| `--config` | No | Channel-specific JSON config string (see ChannelConfigDTO). |
+| `--touch-event-source` | No | Reach event source. |
+| `--event-delivery-name` | No | Actual delivery event name. |
+| `--event-click-name` | No | Click event name. |
+
+## Output
+
+- `data.success`: whether the channel config was updated.
+
+## 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.
+- Risk is `write`; ordinary update, no confirmation gate.

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

@@ -0,0 +1,29 @@
+# engage-setting channel-touch-limits list
+
+> Capability id: `engage-setting.channel-touch-limits.list` · Domain: `engage`.
+
+## Command
+
+```bash
+ae-cli engage-setting channel-touch-limits list --project-id <project_id>
+ae-cli engage-setting channel-touch-limits list --project-id <project_id> --dry-run
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+
+## Output
+
+- `data.items`: complete touch-limit rule list for the project.
+- `data.total`: number of returned rules.
+- Each item can contain `project_id`, `rule_id`, `channel_biz_type`, `enable`, `rule_def`, `channel_name`, `channel_type`, and `channel_list`.
+- Each `channel_list` item contains `channel_id` and `channel_name`.
+
+## 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.
+- If `items` is empty, do not invent rule IDs or channel IDs; report that no touch-limit rules were returned for the project.

package/skills/ae-engage/references/client-param.md

@@ -0,0 +1,58 @@
+# engage-setting client-param
+
+> Capability ids: `engage-setting.client-param.{update,delete,list}` · Domain: `engage`. (`create` temporarily disabled in CLI.)
+
+## Commands
+
+```bash
+# Update a custom client param
+ae-cli engage-setting client-param update \
+  --project-id <project_id> --column-name <name> --column-type <type> --select-type <select> \
+  [--column-desc <desc>]
+
+# Delete a custom client param (high-risk)
+ae-cli engage-setting client-param delete --project-id <project_id> --column-name <name> --yes
+
+# List custom client params
+ae-cli engage-setting client-param list --project-id <project_id>
+```
+
+## Parameters
+
+### update
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--column-name` | Yes | Client param column name. |
+| `--column-type` | Yes | Column type (see ColumnTypeEnum). |
+| `--select-type` | Yes | Select type (see SelectTypeEnum). |
+| `--column-source` | No | Param source: preset or custom. |
+| `--column-desc` | No | Display name of the param. Defaults to an empty string. |
+| `--column-remark` | No | Description/remark for the param. |
+| `--alternative-val` | No | JSON array of alternative values. |
+| `--system-id-param` | No | Whether this is a system identifier param. |
+
+### delete
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--column-name` | Yes | Client param column name to delete. |
+
+### list
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+
+## Output
+
+- `update`: `data.success` — whether the operation succeeded.
+- `delete`: `data.success` and `data.task_list` (tasks still referencing the param, which block deletion; each item has `task_id`, `task_name`).
+- `list`: `data.items` (each with `column_name`, `column_type`, `select_type`, `column_source`, `column_desc`, `column_remark`, `alternative_val`, `system_id_param`) and `data.total`.
+
+## Decision Rules
+
+- Use these commands when the user asks to manage custom client params (客户端参数).
+- `delete` is `high-risk-write` and requires `--yes` (or interactive confirmation). When `data.success` is false, `data.task_list` lists tasks that still reference the param — report them instead of forcing deletion.

package/skills/ae-engage/references/common-metric.md

@@ -0,0 +1,75 @@
+# engage-setting common-metric
+
+> Capability ids: `engage-setting.common-metric.{list,get,update,delete}` · Domain: `engage`. (`create` temporarily disabled in CLI.)
+
+## Commands
+
+```bash
+# List common metrics
+ae-cli engage-setting common-metric list --project-id <project_id>
+
+# Get a common metric detail
+ae-cli engage-setting common-metric get --project-id <project_id> --metric-name <name>
+
+# Update a common metric
+ae-cli engage-setting common-metric update \
+  --project-id <project_id> --metric-type <type> --metric-name <name> --metric-qp <qp> \
+  --metric-window-num <num> --metric-window-time-unit DAY --display-name <display>
+
+# Delete a common metric (high-risk)
+ae-cli engage-setting common-metric delete --project-id <project_id> --metric-name <name> --yes
+```
+
+## Parameters
+
+### list
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+
+### get / delete
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--metric-name` | Yes | Metric name. |
+
+### update
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--metric-type` | Yes | Metric type (see MetricTypeEunm). |
+| `--metric-name` | Yes | Metric name. |
+| `--metric-qp` | Yes | Metric qp (event/property expression). |
+| `--metric-window-num` | Yes | Metric window number. |
+| `--metric-window-time-unit` | Yes | Metric window time unit (MINUTE/HOUR/DAY). |
+| `--display-name` | Yes | Display name of the metric. |
+| `--note` | No | Metric note/remark. |
+| `--order-id` | No | Sort order id. |
+| `--metric-setting-id` | No | Metric setting id (when binding to a setting). |
+| `--metric-params` | No | Metric params JSON string. |
+
+## Output
+
+- `list`: `data.items` (each with `project_id`, `metric_type`, `metric_name`, `metric_qp`, `metric_window_num`, `metric_window_time_unit`, `note`, `last_editer`, `last_update_time`, `order_id`, `display_name`, `metric_setting_id`, `metric_params`) and `data.total`.
+- `get`: `data.metric` — a single metric object with the same fields, or `null`.
+- `update` / `delete`: `data.success`.
+
+## Preflight for config-metric batch-add
+
+`engage-scene config-metric batch-add --ta-metric-ids` requires TA common metrics to exist in the project. List them first:
+
+```bash
+ae-cli engage-setting common-metric list --project-id <project_id>
+```
+
+If `items` is empty, common metrics must be created in the Engage console before binding them to a config item, or treat the case as environment-blocked.
+
+## Decision Rules
+
+- Use these commands when the user asks to manage common metrics (常用指标) for the analysis workbench.
+- Discover existing metric names with `common-metric list` first; never invent names for `get`/`update`/`delete`.
+- `--metric-qp` must be a complete metric QP expression; do not pass `{}` as a placeholder.
+- `delete` is `high-risk-write` and requires `--yes` (or interactive confirmation).

package/skills/ae-engage/references/config-table.md

@@ -0,0 +1,92 @@
+# engage-setting config-table
+
+> Capability ids: `engage-setting.config-table.{upload,save,list,query-data,update-data,delete}` · Domain: `engage`.
+
+## Commands
+
+```bash
+# 1. Upload and parse a config table file (base64 content) → caches rows under request-id
+ae-cli engage-setting config-table upload \
+  --project-id <project_id> --request-id <request_id> --file-name data.csv \
+  --file-content "$(base64 -i data.csv)"
+
+# 2. Persist the parsed rows as a new config table
+ae-cli engage-setting config-table save \
+  --project-id <project_id> --request-id <request_id> --info-name <table_name>
+
+# List config tables
+ae-cli engage-setting config-table list --project-id <project_id>
+
+# Query rows of a config table
+ae-cli engage-setting config-table query-data --project-id <project_id> --info-id <info_id>
+
+# Replace an existing config table's data with a freshly uploaded file
+ae-cli engage-setting config-table update-data \
+  --project-id <project_id> --request-id <request_id> --info-name <table_name> --info-id <info_id>
+
+# Delete a config table and its data (high-risk)
+ae-cli engage-setting config-table delete --project-id <project_id> --info-id <info_id> --yes
+```
+
+## Parameters
+
+### upload
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--request-id` | Yes | Client-supplied request id used to cache parsed rows for the subsequent save/update-data. |
+| `--file-name` | Yes | Original file name including extension (.csv/.xlsx). |
+| `--file-content` | Yes | Base64-encoded file content. |
+
+### save
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--request-id` | Yes | Request id returned by a prior upload. |
+| `--info-name` | Yes | Config table name. |
+
+### list
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+
+### query-data
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--info-id` | Yes | Config table ID. |
+
+### update-data
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--request-id` | Yes | Request id returned by a prior upload. |
+| `--info-name` | Yes | Config table name. |
+| `--info-id` | Yes | Config table ID to update. |
+
+### delete
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--info-id` | Yes | Config table ID to delete. |
+
+## Output
+
+- `upload`: `data.file_name`, `data.data_num` (parsed row count), `data.data_list` (preview of up to 10 rows, each with `data_key`, `data_value`).
+- `save`: `data.info_id` — created config table ID.
+- `list`: `data.items` (each with `id`, `project_id`, `info_id`, `info_name`, `creator_open_id`, `login_name`, `create_time`, `update_time`) and `data.total`.
+- `query-data`: `data.items` (each with `project_id`, `info_id`, `data_key`, `data_value`) and `data.total`.
+- `update-data` / `delete`: `data.success`.
+
+## Decision Rules
+
+- Creating or replacing a config table is a two-step flow: `upload` (parse + cache by `request-id`) then `save` (new table) or `update-data` (replace existing). Always use a fresh `--request-id` per upload.
+- The upload cache is keyed by `project-id` + `request-id`, expires after 10 minutes, and is consumed after a successful `save` or `update-data`.
+- Discover existing `info_id` values with `config-table list` first; never invent them.
+- `delete` is `high-risk-write` and requires `--yes` (or interactive confirmation).