@thinkingai/ae-cli 6.0.35 → 6.0.37

package/skills/ae-analysis/references/dashboard_daily_report_send_status.md

@@ -0,0 +1,22 @@
+# analysis dashboard-daily-report send-status
+
+Use after `dashboard-daily-report send` to inspect the actual delivery result.
+Do not use it to read or change the saved daily report configuration.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-daily-report send-status --project-id <project_id> --task-id <task_id>
+```
+
+The normalized `status` is one of:
+
+- `queued`
+- `rendering`
+- `sending`
+- `succeeded`
+- `partially_succeeded`
+- `failed`
+- `canceled`
+
+Output also includes `progress`, `message`, and per-channel status when the backend task contains channel details.

package/skills/ae-analysis/references/dashboard_daily_report_update.md

@@ -1,19 +1,26 @@
 # analysis dashboard-daily-report update
 
-Use when the user wants to update a dashboard daily report configuration.
+Use when the user wants to create or update a dashboard daily report configuration.
 
 Do not use to send immediately. Use `dashboard-daily-report send`.
 
 Command:
 
 ```bash
-ae-cli analysis dashboard-daily-report update --project-id <project_id> --dashboard-id <dashboard_id> [--enable-send true] [--send-time <time>] [--send-title <title>] [--send-content <content>] [--payload '{...}']
+ae-cli analysis dashboard-daily-report update --project-id <project_id> --dashboard-id <dashboard_id> [--enable-send true] [--send-time <time>] [--enable-email true] [--email-new <emails>] [--payload '{...}']
 ```
 
-Input sends `project_id`, `dashboard_id`, and optional daily report fields or `payload`.
+The command is a patch-style upsert:
 
-When `--payload` is absent, the command sends safe defaults expected by the gateway: `need_csv=false`, empty `host_url`, all channel switches false, `send_date=1,2,3,4,5,6,7`, `send_time=09:00`, `lang=zh-CN`, `screen_type=normal`, `zone_offset=0`, and `enable_send=false`. When `--payload` is present, payload values remain authoritative; pass top-level flags only for fields you intentionally want to override.
+- If the dashboard has no saved configuration, the backend creates one and applies defaults for omitted fields.
+- If a configuration exists, omitted fields remain unchanged.
+- Pass an explicit boolean to enable or disable a saved channel.
+- Pass an empty string or array to clear a saved destination.
 
-When enabling Feishu, pass `--enable-feishu true --feishu-info '{"app_id":"cli_xxx","app_secret":"secret_xxx","webhook":["https://open.feishu.cn/open-apis/bot/v2/hook/..."]}'`. All three fields are required because the backend uploads the dashboard image before calling the group-bot webhook. Treat `app_secret` as sensitive input.
+SMTP transport is not caller-selectable. For direct email addresses, the backend uses company SMTP when configured and otherwise uses the default mail service.
 
-Output is the gateway envelope. `data` contains the daily report configuration update result.
+When enabling Feishu, pass `--enable-feishu true --feishu-info '{"app_id":"cli_xxx","app_secret":"secret_xxx","webhook":["https://open.feishu.cn/open-apis/bot/v2/hook/..."]}'`. Treat `app_secret` and webhook URLs as sensitive.
+
+Use `dashboard-daily-report get` before a selective update when the current state matters. The get response redacts secrets and webhook URLs, so do not copy the full response back as an update payload.
+
+Output is the gateway envelope. `data` contains the saved daily report configuration result.

package/skills/ae-analysis/references/drilldown_user_events_export.md

@@ -21,6 +21,11 @@ The nested backend keys are exactly `columnName` and `tableType`, and the table
 
 Use the exact `drilldown_context_id` and canonical `user_id` returned by a user-subject `analysis drilldown-entities run`. Do not use a custom entity, an entity export artifact, or a guessed identity. Export does not accept `--limit`, `--offset`, `--page-num`, or `--page-size`; Common builds the same authorized event-sequence query without the synchronous 1000-row preview cap and streams one `csv.gz` artifact. The platform full-download ceiling (`model_full_download_limit`) still applies.
 
+For a `scope=total` source coordinate, there is no single selected date. Common
+preserves the machine date coordinates returned by the source query together
+with that query's time granularity, such as daily, weekly, or monthly. Do not
+construct dates outside that context or force a daily granularity.
+
 Inspect the returned `run_id` with `analysis run inspect`, then download the completed artifact with `analysis artifact download`.
 
 Output is an async run/artifact descriptor. The complete event rows exist only in the downloaded artifact; they cannot be used as new analysis coordinates.

package/skills/ae-analysis/references/drilldown_user_events_run.md

@@ -29,6 +29,12 @@ ae-cli analysis drilldown-user-events run \
 
 Do not use raw QP, `query_context_id`, or guessed user IDs for this command.
 
+For a `scope=total` source coordinate, there is no single selected date. Common
+preserves the machine date coordinates returned by the source query together
+with that query's time granularity, such as daily, weekly, or monthly. Do not
+invent `target_dates`, force a daily granularity, or replace the returned
+`drilldown_context_id`.
+
 Do not call this command merely because an entity row looks like a user. The explicit subject and follow-up context are the authority.
 
 ## Output

package/skills/ae-analysis/references/super_metadata_batch_create.md

@@ -0,0 +1,29 @@
+# analysis-meta super-metadata batch-create
+
+Use this command to create effective system metadata in batch through the capability gateway: super events, event properties, and user properties.
+
+Do not use it for ordinary event/property CRUD, metadata import from XLSX, or asset governance. Use the dedicated event/property commands, event-property-bundle import, or governance commands instead.
+
+Command:
+
+```bash
+ae-cli analysis-meta super-metadata batch-create --project-id <project_id> --events '[{"event_name":"purchase","event_desc":"Purchase"}]' --event-properties '[{"prop_name":"amount","select_type":"number","super_event_names":["purchase"]}]' --dry-run
+```
+
+Capability id: `metadata.super_metadata.batch_create`.
+
+Input sends `project_id` plus any non-empty JSON arrays among `events`, `event_properties`, and `user_properties`. Use snake_case object fields exactly as documented by the common-service schema:
+
+- Event items: `event_name`, optional `event_desc`, optional `remark`, optional `super_event_prop_names`.
+- Event property items: `prop_name`, `select_type`, optional `prop_desc`, optional `prop_remark`, optional `common_prop`, optional `super_event_names`.
+- User property items: `prop_name`, `select_type`, optional `prop_desc`, optional `prop_remark`.
+
+Output returns `created.events`, `created.event_properties`, and `created.user_properties` with created names and IDs, plus count metadata. If common-service rejects a duplicate, bad reference, or invalid type, preserve the gateway error code and message.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--events` | No | Super event JSON array. |
+| `--event-properties` | No | Event property JSON array. |
+| `--user-properties` | No | User property JSON array. |

package/skills/ae-analysis/references/super_metadata_batch_edit.md

@@ -0,0 +1,24 @@
+# analysis-meta super-metadata batch-edit
+
+Use this command to batch edit descriptions and remarks for effective system metadata through the capability gateway.
+
+Do not use it to create metadata, delete metadata, hide metadata, update event/property relations, or edit governance assets. Use batch-create or the dedicated metadata commands instead.
+
+Command:
+
+```bash
+ae-cli analysis-meta super-metadata batch-edit --project-id <project_id> --type event_property --items '[{"prop_name":"amount","prop_desc":"Amount","prop_remark":"Revenue amount"}]' --dry-run
+```
+
+Capability id: `metadata.super_metadata.batch_edit`.
+
+Input sends `project_id`, `type`, and `items`. For `type=event`, each item identifies the target with `event_name` and may set `event_desc` or `remark`. For `type=event_property` or `type=user_property`, each item identifies the target with `prop_name` and may set `prop_desc` or `prop_remark`.
+
+Output returns `type` and `updated_count`. Preserve validation errors from common-service, especially missing names, unsupported `type`, or empty `items`.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--type` | Yes | Metadata type to edit: `event`, `event_property`, or `user_property`. |
+| `--items` | Yes | Batch edit item JSON array. |

package/skills/ae-engage/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ae-engage
 version: 1.0.0
-description: "AE Engage MCP: config items, flows, channel settings, task data query, and management"
+description: "AE Engage capability gateway: config center, flows, push/config channels, strategies, templates, and task management. Trigger words: config center, scene config, push channel, config channel, operation strategy, operation task, template, config item, Engage, Hermes, engage-scene, engage-setting, engage-flow, engage-task."
 ---
 
 # ae-engage
@@ -43,6 +43,27 @@ Typical use cases include:
 - Querying config items and strategies, copying templates, and managing strategy status
 - Querying flow lists, node schemas, and flow reports, and saving or managing flows
 
+## Keyword Routing
+
+When the user mentions a product term below (including common Chinese UI labels), open the listed reference(s) first — do not guess commands or IDs.
+
+| Keyword | Product meaning | CLI domain | Primary reference | Related references |
+|---|---|---|---|---|
+| **Config center** | Engage scene management / config center overview | `engage-scene` | `references/scene-config-item.md` | `scene-config-param.md`, `scene-config-group.md`, `scene-preset-metric.md`, `scene-config-metric.md`, `scene-config-channel.md`, `channel-mgmt.md`, `scene-strategy.md`, `scene-template.md`; L3 reports: `config-item-trigger-report.md`, `config-item-analysis-report.md`, `config-item-strategy-comparison.md` |
+| **Scene config** | Same as config center; params, groups, metrics, channels, strategies, and templates under a config item | `engage-scene` | `references/scene-config-item.md` | Same as above; params/groups/metrics: `scene-config-param.md`, `scene-config-group.md`, `scene-preset-metric.md`, `scene-config-metric.md` |
+| **Config item** | A single config item in the config center | `engage-scene` | `references/scene-config-item.md` | `scene-config-param.md`, `scene-preset-metric.md`, `scene-config-metric.md`, `scene-strategy.md`, `scene-template.md` |
+| **Push channel** | Project-level message push channels (Webhook, FCM, APNS, etc.) | `engage-setting` | `references/channel-list.md` | `channel-detail.md`, `add-channel.md`, `update-channel-status.md`, `delete-channel.md`, `channel-update-config.md`, `channel-test-send.md`, `channel_touch_limits_list.md` |
+| **Config channel** | Config-center Webhook/client config channels (not the same as push channels) | `engage-scene` | `references/scene-config-channel.md` | `channel-mgmt.md` (create/enable-disable/copy/delete workflows). User params in `config.customsParamList` require `columnName` with `user:` prefix (e.g. `user:#account_id`); preflight names with ae-analysis `analysis-meta property list/get`. |
+| **Operation strategy** | Ops/delivery strategies under a config item | `engage-scene` | `references/scene-strategy.md` | Custom audience QP: [`scene-strategy-audience.md`](references/scene-strategy-audience.md) — **用户满足** `filts[0]` + **用户行为** `filts[1]` two-block mix QP; preflight props (stop + list if missing); examples A/B/C; template: `scene-template.md` |
+| **Operation task** | Hermes push/engagement tasks (list, save, lifecycle, reports) | `engage-task` | `references/task-list.md` | `task-detail.md` (get), `save-task.md`, `build-task-save-guide.md`, `task-stats.md`, `task-delete.md`, `push-record-query.md`, `task-data-overview.md`, `task-data-detail.md`, `task-metric-detail.md`, `task-experiment-report.md` |
+| **Template** | Strategy templates under a config item | `engage-scene` | `references/scene-template.md` | `scene-config-param.md` (template fields reference `paramId`); enable via `template update` then `template update-status` before strategy create |
+
+**Easy to confuse:**
+
+- **Push channel** → `ae-cli engage-setting channel …` (Hermes push channel settings)
+- **Config channel** → `ae-cli engage-scene config-channel …` (config-center channels; see `channel-mgmt.md`)
+- Flow / Task canvas nodes use `channelId` from **push channels**; config items bind `channel_id` from **config channels**
+
 ## Parameter Conventions
 
 - Use regular flags for simple parameters, for example `--project-id`, `--task-id`, and `--flow-uuid`
@@ -230,6 +251,8 @@ ae-cli engage-scene config-metric update-rule --project-id <project_id> --metric
 ae-cli engage-scene config-metric batch-delete --project-id <project_id> --config-id <config_id> --metric-ids '[1,2]' --yes
 
 # Config channel list / get / create / update / update-status / delete / query-log
+# User params: verify each customsParamList columnName via ae-analysis property list/get first; then use user:<prop_name>
+# Strategy custom audience: scene-strategy-audience.md — mix QP filts[0]=用户满足, filts[1]=用户行为; strategy predict for 预估人数
 # Workflows: references/channel-mgmt.md · schema: references/scene-config-channel.md
 ae-cli engage-scene config-channel list --project-id <project_id> [--channel-type 0|1]
 ae-cli engage-scene config-channel get --project-id <project_id> --channel-id <channel_id>
@@ -243,6 +266,7 @@ ae-cli engage-scene config-channel query-log --project-id <project_id> --channel
 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 predict --project-id <project_id> --qp '<mix QP string>' --zone-offset 8 [--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
@@ -412,7 +436,8 @@ More detailed single-command guidance is available in the business-oriented `ref
 - `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.{list,get,create,update,update-status,delete,query-log}`)
 - `references/channel-mgmt.md` (config channel management workflows)
-- `references/scene-strategy.md` (`engage-scene.strategy.{list,get,create,update,log,batch-copy,manage}`)
+- `references/scene-strategy.md` (`engage-scene.strategy.{list,get,create,update,log,predict,batch-copy,manage}`)
+- `references/scene-strategy-audience.md` (custom audience mix QP: 用户满足/用户行为 two-block layout, preflight, worked examples A/B/C)
 - `references/scene-template.md` (`engage-scene.template.{list,get,copy,create,update,update-status,delete}`)
 - `references/config-item-trigger-report.md` (`engage-scene.report.config-item-trigger`, L3)
 - `references/config-item-analysis-report.md` (`engage-scene.report.config-item-analysis`, L3)
@@ -486,11 +511,13 @@ For task draft creation or update, use this workflow:
 
 1. `ae-cli engage-setting channel list --project-id <projectId>`
 2. `ae-cli engage-task task build-save-guide --project-id <projectId> --req '{...}'`
-3. If the guide says QP-derived fields are needed, create the audience with `analysis user-cluster create`, then read its server-authored definition with `analysis user-cluster get`
+3. If the guide says QP-derived fields are needed (`targetConfig.qp`, `triggerConfig.triggerRule`, `clientConfig.clientQp`, or `completionIndicatorDef.event`), call:
+   `ae-cli engage-setting query cluster-qp-skill --project-id <projectId>`
+   Use the returned skill text to build those fields. For existing-cluster audiences (`targetClusterType=2`), use `analysis user-cluster get` instead of hand-writing QP.
 4. `ae-cli engage-task task save --project-id <projectId> --req '{...}'`
 
 `engage-task task build-save-guide` is a read-only helper. It returns scenario-specific required fields, channel content schema, unsupported combinations, examples, and a handoff template for `save_task`.
 
-`engage-task task save` only saves a draft. It does not submit approval, does not start sending, and does not trigger task execution. If `req.taskId` is omitted it creates a new draft; if `req.taskId` is present it updates an existing draft. Update mode only supports draft tasks, and omitted fields can inherit from the existing draft before validation.
+`engage-task task save` creates or updates a task configuration. It does not submit approval, does not start sending, and does not trigger task execution. If `req.taskId` is omitted it creates a new draft; if `req.taskId` is present it updates an existing **draft or paused** task. Update mode rejects running/ended tasks with `invalid_status`. Omitted fields inherit from the existing task before validation (partial rename/update is supported).
 
-Audience creation is not a fixed preflight step. Use direct `analysis user-cluster create` only when the guide requires a condition audience, and prefer the returned `cluster_name`/`clusterKey`. If the Engage schema explicitly requires QP-derived fields such as `targetConfig.qp`, `triggerConfig.triggerRule`, `clientConfig.clientQp`, or `completionIndicatorDef.event`, read the saved server-authored definition with `analysis user-cluster get`; never assemble raw QP manually.
+Audience creation is not a fixed preflight step. When the guide requires QP-derived fields (`targetConfig.qp`, `triggerConfig.triggerRule`, `clientConfig.clientQp`, `completionIndicatorDef.event`), call `ae-cli engage-setting query cluster-qp-skill --project-id <projectId>` first and follow the returned skill definition; do not assemble raw QP manually. For existing-cluster audiences, use `analysis user-cluster get` to copy server-authored definitions when appropriate.

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

@@ -48,10 +48,14 @@ Topic-level audience uses `topicClusterKey` / `topicQp`; do **not** pass task-le
 
 | Value | Required | Notes |
 |---|---|---|
-| `1` (custom) | `topicQp` | Valid condition JSON object string (not `{}`). |
+| `1` (custom) | `topicQp` | Valid condition JSON object string (not `{}`). Use mix QP with `totalCFilter` (and optional `totalOutCFilter`). |
 | `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. |
 
+**`triggerMixQpVersion`:** For custom audience (`targetClusterType=1`) with mix QP (`totalCFilter` / `totalInCFilter`), set `"4.4"`. UI theme edit parses conditions only when this is `4.4`; missing/blank values make target-user filters render empty. Capability create/update/copy default blank to `"4.4"` (same as UI and standalone task MCP).
+
+Task-level extra conditions go in `taskQp` as mix QP under **`totalCFilter` only** (user attrs and/or events). Do not put task-owned conditions in `totalInCFilter` — that key is reserved for topic→task merge (topic `totalCFilter` is copied into task cluster `totalInCFilter` on save).
+
 ### Trigger (`triggerType`)
 
 | Value | Required | Notes |
@@ -60,6 +64,35 @@ Topic-level audience uses `topicClusterKey` / `topicQp`; do **not** pass task-le
 | `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`. |
 
+## Create Topic Orchestration
+
+Use this workflow when a topic has a shared audience plus one or more task-level audience splits, message variants, or completion goals.
+
+1. **Separate the intent before building the payload.** Record the parent activity, topic-level shared audience, task-level extra audience for each task, schedule, channel, message content, and completion goal/window as distinct fields. A completion goal is not an audience condition unless the user explicitly says so.
+2. **Resolve the parent activity.** Use `activity list|get` to verify the exact `activityId`, editable status, activity dates, and timezone. For a repeated topic, keep `startDate` and `endDate` inside the activity period and interpret the cron in the activity timezone.
+3. **Resolve a real channel.** Query `engage-setting channel list`, then inspect the selected channel before composing content. If several enabled channels match and the user has not specified a provider or an already-confirmed project default, ask which one to use instead of choosing an arbitrary ID.
+4. **Read the channel content contract.** Call `engage-task task build-save-guide` with the known trigger, audience, channel type, and `channelId`. Build every `groupContentList[].contentList[].content` item from `fieldRules.channelContentSchema`; do not infer App Push keys or parameter types from memory.
+5. **Prepare audience and completion inputs.** Resolve real event/property metadata and categorical values through the applicable Analysis workflow. Put the shared condition in `topicQp` or `topicClusterKey`, and only task-specific conditions in each `taskQp`. For a rolling condition such as "recent N days" that must be evaluated for future repeated sends, prefer a custom QP; use an existing cluster only after confirming that its refresh semantics match the send cadence. Build the completion goal separately in `completionIndicatorDef`.
+6. **Build one native `TopicAddDTO`.** Keep nested payload keys in camelCase. Ensure `tasks` is non-empty, `frequencyLimits` and QP fields are JSON strings where documented, each task has channel content, and Android/iOS or other variants map to the correct task audience and message.
+7. **Validate the complex payload.** Run `topic create ... --validate` while correcting the nested payload. Inspect `normalized_input` and confirm that the schedule, audience boundaries, message variants, and completion window retain the intended semantics. After `valid=true`, execute the same payload directly; do not add a redundant dry-run by default.
+8. **Create exactly once.** Run `topic create` with the validated payload. A successful response only reports `data.success`; it does not provide enough evidence to declare the whole orchestration complete.
+9. **Resolve IDs and verify the saved topic.** Call `activity info-list` for the parent activity, match the new topic and tasks by their names, then call `topic get` with the returned `topicId`. Verify the channel, dates, cron, topic audience, each task audience, content, completion goal, and draft status. For custom audiences, confirm that the saved task QP keeps task-owned conditions in `totalCFilter` and the shared topic condition appears only through the topic-to-task merge.
+10. **Verify generated audiences before reporting completion.** Read the generated topic/task cluster keys with the applicable cluster query and wait for terminal computation state. Require `refresh_status=success`, `progress=100`, `real_available=1`, and `cluster_valid=1`. A zero-user result may be valid, but reconcile it with the discovered categorical values and business expectation. If computation fails, correct only the verified cause and re-check; do not retry an unchanged request or report the topic as fully ready.
+
+Recommended command order:
+
+```text
+activity list/get
+-> channel list/get
+-> task build-save-guide
+-> prepare topic audience, task audiences, content, and completion goal
+-> topic create --validate
+-> topic create
+-> activity info-list
+-> topic get
+-> generated audience status checks
+```
+
 ## Output
 
 - `get`: `data.topic` (includes `topicClusterKey` for topic audience).

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

@@ -1,9 +1,8 @@
 # ae-engage engage-setting channel create
 
+> Trigger keywords: push channel · Mapped command: `ae-cli engage-setting channel create`
 
-Create a new Engage channel.
-
-Mapped command: `ae-cli engage-setting channel create`
+Create a new Engage push channel.
 
 ## Flags
 

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

@@ -14,11 +14,25 @@ Use this sequence when creating or updating a task draft:
 
 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:
+3. If the guide says QP-derived fields are required, fetch the skill definition first:
 
 ```bash
-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>"]'
+ae-cli engage-setting query cluster-qp-skill --project-id <projectId>
+# optional selectors:
+ae-cli engage-setting query cluster-qp-skill --project-id <projectId> --response-mode full --condition-subtype all
+```
+
+Use the returned `skill` text to build:
+
+- `targetConfig.qp`
+- `triggerConfig.triggerRule` (required for `triggerType=3/4/5`)
+- `clientConfig.clientQp`
+- `completionIndicatorDef.event`
+
+For existing-cluster audiences (`targetClusterType=2`), you may copy server-authored definitions via:
+
+```bash
+ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<cluster_name>"]'
 ```
 
 4. Build the final grouped `save_task.req`.

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

@@ -1,9 +1,8 @@
 # ae-engage engage-setting channel get
 
+> Trigger keywords: push channel · Mapped command: `ae-cli engage-setting channel get`
 
-Query the details of a single Engage channel.
-
-Mapped command: `ae-cli engage-setting channel get`
+Query the details of a single Engage push channel.
 
 ## Response shape
 

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

@@ -1,11 +1,8 @@
 # ae-engage engage-setting channel list
 
+> Trigger keywords: push channel · Mapped command: `ae-cli engage-setting channel list`
 
-Query the list of Engage channels in a project.
-
-Mapped command: `ae-cli engage-setting channel list`
-
-## Response shape
+Query the list of Engage push channels in a project.
 
 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`.

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

@@ -1,6 +1,6 @@
 # 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.
+> Trigger keywords: config center, config channel · 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.
 
@@ -12,6 +12,8 @@ Use for AE Engage **config center channel management**: Webhook (`channel_type=0
 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.
+7. In `config.customsParamList` (**user params**), every `columnName` must be prefixed with `user:` and point to a real user property, e.g. `user:#account_id`. `envParamList` entries do not use this prefix.
+8. Before create/update, use the **ae-analysis** skill to verify each intended user property exists (`analysis-meta property list --scope user`, then `property get` for exact match). Never invent `columnName` values.
 
 ## Permissions
 
@@ -44,18 +46,31 @@ Parse `data.channel.config` for URL, auth, user params, and env params.
 
 Webhook requires `channel_name` and `config.url`. Optional: `testUrl`, auth, user params, env params.
 
+**Preflight (user params):** for each intended `customsParamList[].columnName`, discover and verify the user property via ae-analysis first:
+
+```bash
+ae-cli analysis-meta property list --project-id <pid> --scope user --query <keyword> \
+  --fields '["prop_name","prop_desc","select_type"]' --limit 50
+ae-cli analysis-meta property get --project-id <pid> --table-type user --prop-name <prop_name>
+# → use columnName "user:" + prop_name, e.g. user:#account_id
+```
+
+Then create the channel:
+
 ```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":[]}'
+  --config '{"url":"https://...","testUrl":"","authConfig":{"enable":false},"customsParamList":[{"key":"uid","columnName":"user:#account_id","defaultValue":"","systemIdParam":false}],"envParamList":[]}'
 ```
 
 Returns `data.channel_id`. Created channels start **enabled**.
 
 ### 4. Update
 
+Re-verify any new or changed `customsParamList[].columnName` with `analysis-meta property list/get` (ae-analysis skill) before building `--config`.
+
 ```bash
 ae-cli engage-scene config-channel get --project-id <pid> --channel-id <id>
 # If channel_status=1 and changing URL / auth / param definitions:

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

@@ -1,6 +1,6 @@
 # engage-setting channel test-send
 
-> Capability id: `engage-setting.channel.test-send` · Domain: `engage`.
+> Trigger keywords: push channel · Capability id: `engage-setting.channel.test-send` · Domain: `engage`.
 
 ## Command
 

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

@@ -1,6 +1,6 @@
 # engage-setting channel update-config
 
-> Capability id: `engage-setting.channel.update-config` · Domain: `engage`.
+> Trigger keywords: push channel · Capability id: `engage-setting.channel.update-config` · Domain: `engage`.
 
 ## Command
 

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

@@ -1,9 +1,8 @@
 # ae-engage engage-setting channel delete
 
+> Trigger keywords: push channel · Mapped command: `ae-cli engage-setting channel delete`
 
-Delete an Engage channel.
-
-Mapped command: `ae-cli engage-setting channel delete`
+Delete an Engage push channel.
 
 ## Flags
 

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

@@ -33,8 +33,8 @@ You still organize user requirements into an intermediate intent first, then map
 ## 2. Workflow
 
 1. Identify the flow intent from the user input and produce a unified intent JSON.
-2. Build a semantic condition request from `ae-analysis/references/user_cluster_models.md`, create the audience directly with `analysis user-cluster create`, and prefer its `cluster_name`/`clusterKey`. Read the saved server-authored definition with `analysis user-cluster get` only when an Engage node schema explicitly requires QP-derived fields; never assemble raw QP.
-3. Run `ae-cli engage-setting channel list --project-id <projectId>` to get the available channels and match real `channel_id` values for touchpoint nodes. For `webhook_push`, also run `ae-cli engage-setting channel get` and use `data.item.config.params_list` to build request field `contentList`.
+2. Build a semantic condition request from `ae-analysis/references/user_cluster_models.md`, create the audience directly with `analysis user-cluster create`, and prefer its `cluster_name`/`clusterKey`. When node schema requires QP-derived fields (`targetClusterQp`, `triggerRule`, etc.), call `ae-cli engage-setting query cluster-qp-skill --project-id <projectId>` first; never assemble raw QP manually.
+3. Run `ae-cli engage-setting channel list --project-id <projectId>` to get the available channels and match real `channelId` values for touchpoint nodes. For `webhook_push`, also run `ae-cli engage-setting channel get` and use `data.item.config.params_list` to build request field `contentList` (camelCase; snake_case aliases are normalized during validate).
 4. Query `ae-cli engage-flow node-config schema --project-id <project_id> --node-type <type>` before constructing each non-trivial node config, then run `ae-cli engage-flow node-config validate --project-id <project_id> --node-type <type> --operation-mode save_flow --config '<config-json-string>'` before placing the config into `nodes` or `nodeConfigs`.
 5. Map the intent JSON to `nodes` and `edges` (compact form, see §7 / §8).
 6. `build` → resolve any `need_input` slot → `preview` → `commit`, then verify with `engage-flow flow get`.
@@ -460,7 +460,10 @@ The CLI injects `projectId` into both the top level and `req`; you do not write
 
 `need_input` is a **soft prompt**, not a hard error:
 
-- **`data.result.errors` empty + `data.result.next_slot` present** → server needs one more node config (trigger / channel / targetCluster). Answer with request fields `operation=build` + `draftId` + `expectedVersion` + `slotAnswer`. If response `next_slot.target_node_id` is present, request `slotAnswer.nodeConfig` may contain only `config`; otherwise include `nodeId` or `id`.
+- **`data.result.errors` empty + `data.result.next_slot` present** → server needs one more node config (trigger / channel / targetCluster). Answer with request fields `operation=build` + `draftId` + `expectedVersion` + `slotAnswer`. If response `next_slot.target_node_id` is present, request `slotAnswer.nodeConfig` may contain only `config`; otherwise include `nodeId` or `id`. **`slotAnswer.nodeConfig.config` merges into the existing node config** — send only the fields you are adding or changing, not the full config.
+- For existing-cluster entry nodes (`targetUserType=2`), use `targetClusterName` or `clusterId` alias.
+- For custom audiences, call `ae-cli engage-setting query cluster-qp-skill --project-id <projectId>` before filling `targetClusterQp`.
+- For `event_trigger`, `endDate` must be **strictly earlier than** `flowEndDate`.
 - **`data.result.errors` non-empty** → hard validation failure. Fix `nodes`/`edges` and `build` again (a new `data.result.draft_id` is issued; the stale draft is cleaned by TTL).
 
 ### 11.3 Minimal Working Example

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

@@ -10,13 +10,9 @@ Recommended workflow:
 
 1. `ae-cli engage-setting channel list --project-id <projectId>`
 2. `ae-cli engage-task task build-save-guide --project-id <projectId> --req '{...}'`
-3. If the guide indicates an audience or QP-derived fields are needed, create the audience directly and read it back:
-
-```bash
-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>"]'
-```
-
+3. If the guide indicates QP-derived fields, call `ae-cli engage-setting query cluster-qp-skill --project-id <projectId>` and build
+   `targetConfig.qp`, `triggerConfig.triggerRule`, `clientConfig.clientQp`, or `completionIndicatorDef.event`
+   from the returned skill text. For existing-cluster audiences, use `analysis user-cluster get`.
 4. Build the final grouped `req`
 5. `ae-cli engage-task task save --project-id <projectId> --req '{...}'`
 
@@ -40,7 +36,7 @@ For the full guide contract, request format, return sections, and handoff usage,
 The command supports two modes:
 
 - create mode: omit `req.taskId`
-- update mode: include `req.taskId` for an existing draft task
+- update mode: include `req.taskId` for an existing draft or paused task
 
 Regardless of mode, this tool only saves a draft:
 
@@ -59,8 +55,8 @@ Notes:
 - the outer Capability input uses `project_id` and `req`; fields inside `req` keep the native camelCase DTO shape shown below
 - Hermes assigns the outer `--project-id` to `req.projectId`; if `req.projectId` is also present, the outer value wins
 - the whole `req` must be a JSON object, not a stringified JSON string
-- for update mode, Hermes only allows modifying draft tasks
-- in update mode, omitted fields are backfilled from the existing draft before validation, so partial draft updates are allowed
+- for update mode, Hermes allows modifying **draft** or **paused** tasks (`status` 0 or 2); running/ended tasks are rejected with `invalid_status`
+- in update mode, omitted fields are backfilled from the existing task before validation, so partial updates (e.g. rename only) are allowed
 
 ### Response shape
 
@@ -160,12 +156,13 @@ Top-level notes:
 
 ### 4.1 `taskId`
 
-Use `taskId` only when you are updating an existing draft task.
+Use `taskId` only when you are updating an existing draft or paused task.
 
 - create mode: omit `taskId`
 - update mode: include `taskId`
-- update mode can send only the fields that need changing
-- update mode still fails if the referenced task is not in draft status
+- update mode can send only the fields that need changing (e.g. `baseInfo.taskName` for rename)
+- update mode fails with `invalid_status` if the task is running or ended
+- for paused tasks that already started pushing, Hermes rejects changes to key attributes (channel, trigger time/type, audience cluster, timezone, completion indicators); renames and other non-key fields remain allowed
 
 ### 4.2 `channelConfig`
 
@@ -273,7 +270,7 @@ Before submission, verify:
 5. `targetClusterType` matches the presence or absence of `clusterKey` / `qp`.
 6. `triggerType` matches the provided scheduling or event fields.
 7. `completionIndicatorDef` is present and structurally valid for the current scenario.
-8. `taskId` is omitted for create mode and present only for updating a draft.
+8. `taskId` is omitted for create mode and present only for updating a draft or paused task.
 9. No unsupported `triggerType=6` is used.
 10. No placeholder IDs or fabricated resource names remain in the request.
 
@@ -309,6 +306,6 @@ This command is a write operation.
 - Do not pass the whole `req` as a JSON string
 - Do not use `triggerType=6`
 - Do not invent `channelId`, `clusterKey`, audience definitions, or content keys
-- Do not use `taskId` for a non-draft task
+- Do not use `taskId` for a running or ended task
 - Do not pass `occasionKeys`; Hermes derives them from content
 - Do not call the semantic cluster definition builder as a reflex; call it only when guide output says QP-derived fields are needed

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

@@ -1,6 +1,6 @@
 # engage-scene config-channel
 
-> Capability ids: `engage-scene.config-channel.{list,get,create,update,update-status,delete,query-log}` · Domain: `engage`.
+> Trigger keywords: config center, scene config, config channel · Capability ids: `engage-scene.config-channel.{list,get,create,update,update-status,delete,query-log}` · Domain: `engage`.
 
 Scene / config center — **config channel management** (Webhook / client config channels).
 
@@ -102,7 +102,7 @@ ae-cli engage-scene config-channel query-log --project-id <project_id> --channel
   "customsParamList": [
     {
       "key": "user_id",
-      "columnName": "#account_id",
+      "columnName": "user:#account_id",
       "defaultValue": "",
       "systemIdParam": true
     }
@@ -114,10 +114,33 @@ ae-cli engage-scene config-channel query-log --project-id <project_id> --channel
 - `url` — production environment URL (required for webhook)
 - `testUrl` — optional test environment URL
 - `authConfig.enable` — channel auth switch; when true, `secretKey` is required; `secretType` **1 = basic**, **2 = advanced**
-- `customsParamList` — user params (field key / linked user property / default value / system-integration identity)
-- `envParamList` — environment params (from config tables)
+- `customsParamList` — **user params** (field key / linked user property / default value / system-integration identity). Each entry's `columnName` must use the `user:` prefix and reference a real user property code, e.g. `user:#account_id`, `user:#distinct_id`. Do **not** pass bare property names such as `#account_id`.
+- `envParamList` — **environment params** (from config tables). `columnName` here is the env-param field name and does **not** take the `user:` prefix.
 - At most one `systemIdParam=true` across user + env params
 
+When creating or updating a config channel (`create` / `update` with `--config`), normalize every `customsParamList[].columnName` to `user:<prop_code>` before submit. If `get` returns bare names, add the prefix when building the next update payload.
+
+## Preflight: verify user properties (ae-analysis)
+
+Before setting `customsParamList[].columnName`, use the **ae-analysis** skill to confirm each linked user property exists in the project. Do not invent property names.
+
+```bash
+# 1) Browse / search user properties
+ae-cli analysis-meta property list --project-id <project_id> --scope user \
+  --query <keyword> \
+  --fields '["prop_name","prop_desc","select_type","table_type"]' --limit 50
+
+# 2) Verify one exact property before submit (optional but recommended)
+ae-cli analysis-meta property get --project-id <project_id> --table-type user --prop-name <prop_name>
+```
+
+Decision rules:
+
+- Read `skills/ae-analysis/references/property_list.md` and `property_get.md` when unsure about flags or output shape.
+- Match a real `data.properties[].prop_name` (or confirmed `data.property.prop_name`) from metadata, then set `columnName` to `user:` + that name — e.g. `prop_name` `#account_id` → `columnName` `user:#account_id`.
+- If the property is not found after list + optional get, stop and tell the user; do not submit the channel config with a fabricated `columnName`.
+- `envParamList` names come from config-table / env-param setup, not from user-property metadata.
+
 ## Output
 
 - `list`: `data.items` + `data.total` (snake_case fields: `channel_id` / `channel_name` / `channel_type` / `channel_status` / `creator` / `updater` / `create_time` / `update_time`)
@@ -130,6 +153,7 @@ ae-cli engage-scene config-channel query-log --project-id <project_id> --channel
 
 - Risk: `list` / `get` / `query-log` = read; `create` / `update` / `update-status` = write; `delete` = high-risk-write (user confirmation + `--yes`)
 - Discover `channel_id` with `list` first; never invent IDs
+- **User params (`customsParamList`)**: `columnName` must be `user:<user_prop_code>` (e.g. `user:#account_id`). Applies to both webhook and client channels on create/update. Preflight each name with `ae-cli analysis-meta property list/get` (ae-analysis skill) before submit.
 - Enabled channel (`channel_status=1`): only limited fields such as name can change; disable first (`update-status --channel-status 2`) before changing URL, auth, or parameter definitions
 - Delete: disable first, then `delete --yes`
 - Copy: `get` → rename (often append `_copy`) → `create`

package/skills/ae-engage/references/scene-config-group.md

@@ -1,6 +1,6 @@
 # engage-scene config-group
 
-> Capability ids: `engage-scene.config-group.{list,batch-add,update,batch-delete}` · Domain: `engage`.
+> Trigger keywords: config center, scene config · Capability ids: `engage-scene.config-group.{list,batch-add,update,batch-delete}` · Domain: `engage`.
 
 Scene management / config center — config item group management.
 

package/skills/ae-engage/references/scene-config-item.md

@@ -1,6 +1,6 @@
 # engage-scene config-item
 
-> Capability ids: `engage-scene.config-item.{list,get,create,update,delete}` · Domain: `engage`.
+> Trigger keywords: config center, scene config, config item · Capability ids: `engage-scene.config-item.{list,get,create,update,delete}` · Domain: `engage`.
 
 Scene management / config center — config item management.