@thinkingai/ae-cli 6.0.24 → 6.0.28

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

@@ -0,0 +1,26 @@
+# analysis property hide-update
+
+Use when the user needs to batch hide or show properties.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis property hide-update --project-id <project_id> --table-type <table_type> --prop-names '{}' --is-hide true
+ae-cli analysis property hide-update --dry-run
+```
+
+Capability id: `metadata.property.hide_update`.
+
+Input sends `project_id`, `table_type`, `prop_names`, `is_hide`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--table-type` | Yes | Property table type. |
+| `--prop-names` | Yes | Property names JSON array, or a JSON string accepted by common-service. |
+| `--is-hide` | Yes | Whether to hide the properties. |

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

@@ -0,0 +1,25 @@
+# analysis property influence-list
+
+Use when the user needs to list assets affected by property changes.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis property influence-list --project-id <project_id> --table-type <table_type> --prop-name <prop_name>
+ae-cli analysis property influence-list --dry-run
+```
+
+Capability id: `metadata.property.influence_list`.
+
+Input sends `project_id`, `table_type`, `prop_name`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--table-type` | Yes | Property table type. |
+| `--prop-name` | Yes | Property column name. |

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

@@ -0,0 +1,24 @@
+# analysis property list
+
+Use when the user needs to list event or user properties.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis property list --project-id <project_id> --table-type <table_type>
+ae-cli analysis property list --dry-run
+```
+
+Capability id: `metadata.property.list`.
+
+Input sends `project_id`, `table_type`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--table-type` | Yes | Property table type. |

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

@@ -0,0 +1,24 @@
+# analysis property related-events
+
+Use when the user needs to list events related to one event property.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis property related-events --project-id <project_id> --prop-name <prop_name>
+ae-cli analysis property related-events --dry-run
+```
+
+Capability id: `metadata.property.related_events`.
+
+Input sends `project_id`, `prop_name`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--prop-name` | Yes | Event property column name. |

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

@@ -0,0 +1,25 @@
+# analysis property relation-update
+
+Use when the user needs to update property type, connection relation, or event mapping.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis property relation-update --project-id <project_id> --table-type <table_type> --payload '{}'
+ae-cli analysis property relation-update --dry-run
+```
+
+Capability id: `metadata.property.relation_update`.
+
+Input sends `project_id`, `table_type`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--table-type` | Yes | Property table type. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,27 @@
+# analysis property update
+
+Use when the user needs to update property display names and remarks.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis property update --project-id <project_id> --table-type <table_type> --prop-name <prop_name> --prop-desc <prop_desc> --prop-remark <prop_remark>
+ae-cli analysis property update --dry-run
+```
+
+Capability id: `metadata.property.update`.
+
+Input sends `project_id`, `table_type`, `prop_name`, `prop_desc`, `prop_remark`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--table-type` | Yes | Property table type. |
+| `--prop-name` | Yes | Property column name. |
+| `--prop-desc` | No | Property display name. |
+| `--prop-remark` | No | Property remark. |

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

@@ -0,0 +1,22 @@
+# analysis run inspect
+
+Use after an export command returns `run_id`.
+
+Do not use for MCP query cancellation or old `request_id` lifecycle. This is only for capability-gateway export `run_id`.
+
+Command:
+
+```bash
+ae-cli analysis run inspect --run-id <run_id>
+```
+
+Input sends `run_id`.
+
+Output is the gateway envelope. `data` contains run status, artifact status, and error fields when the run failed.
+
+Polling rule:
+
+- Continue polling while status is running or pending.
+- Treat `COMPLETED` or `SUCCEEDED` as success.
+- Treat `FAILED`, `CANCELED`, or `CANCELLED` as terminal failure.
+- After success, download with `ae-cli analysis artifact download --run-id <run_id> --artifact-id <artifact_id> --output <file>`.

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

@@ -0,0 +1,36 @@
+# analysis super-metadata export
+
+Use when the user needs to export super event and super property configuration.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis super-metadata export --project-id <project_id>
+ae-cli analysis super-metadata export --project-id <project_id> --request-id cli_0123456789abcdef0123456789abcdef --timeout-seconds 3600
+ae-cli analysis super-metadata export --dry-run
+```
+
+Capability id: `metadata.super_metadata.export`.
+
+Input sends `project_id`, and optional `request_id`, `timeout_seconds`.
+
+Output is the gateway envelope. `data` contains an async export descriptor with `run_id`, `artifact_id`, status fields, and expiration fields. It does not expose inspect/download API paths; use the CLI commands below.
+
+Follow-up workflow:
+
+1. Save `data.run_id` and `data.artifact_id` from the export response.
+2. Poll status with `ae-cli analysis run inspect --run-id <run_id>`.
+3. Continue polling while status is running or pending. Treat `COMPLETED` or `SUCCEEDED` as success, and `FAILED`, `CANCELED`, or `CANCELLED` as terminal failure.
+4. On success, download with `ae-cli analysis artifact download --run-id <run_id> --artifact-id <artifact_id> --output <file>.xlsx`.
+5. If the export is no longer needed, cancel with `ae-cli analysis query cancel --run-id <run_id> --yes`.
+
+Do not write custom Python/curl for polling or download unless the CLI command itself is unavailable.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--request-id` | No | Optional `cli_<32 lowercase hex>` request ID. |
+| `--timeout-seconds` | No | Timeout in seconds, 1 to 7200. Default 3600. |

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

@@ -0,0 +1,24 @@
+# analysis super-metadata import
+
+Use when the user needs to pre-import and confirm-import super event and super property configuration.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis super-metadata import --project-id <project_id> --payload '{}'
+ae-cli analysis super-metadata import --dry-run
+```
+
+Capability id: `metadata.super_metadata.import`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | No | Optional capability payload JSON. |

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

@@ -0,0 +1,25 @@
+# analysis virtual-event create
+
+Use when the user needs to create a virtual event from events and filters.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-event create --project-id <project_id> --override true --payload '{}'
+ae-cli analysis virtual-event create --dry-run
+```
+
+Capability id: `metadata.virtual_event.create`.
+
+Input sends `project_id`, `override`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--override` | No | Whether to override an existing virtual event rule. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-event delete
+
+Use when the user needs to delete a virtual event rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-event delete --project-id <project_id> --v-event-id <v_event_id>
+ae-cli analysis virtual-event delete --dry-run
+```
+
+Capability id: `metadata.virtual_event.delete`.
+
+Input sends `project_id`, `v_event_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--v-event-id` | Yes | Virtual event ID. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-event get
+
+Use when the user needs to get virtual event rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-event get --project-id <project_id> --v-event-id <v_event_id>
+ae-cli analysis virtual-event get --dry-run
+```
+
+Capability id: `metadata.virtual_event.get`.
+
+Input sends `project_id`, `v_event_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--v-event-id` | Yes | Virtual event ID. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-property create
+
+Use when the user needs to create a SQL virtual event or user property.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-property create --project-id <project_id> --payload '{}'
+ae-cli analysis virtual-property create --dry-run
+```
+
+Capability id: `metadata.virtual_property.create`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,25 @@
+# analysis virtual-property sql-rule-delete
+
+Use when the user needs to delete or revoke SQL virtual property rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-property sql-rule-delete --project-id <project_id> --v-prop-id <v_prop_id> --operation <operation>
+ae-cli analysis virtual-property sql-rule-delete --dry-run
+```
+
+Capability id: `metadata.virtual_property.sql_rule_delete`.
+
+Input sends `project_id`, `v_prop_id`, `operation`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--v-prop-id` | Yes | Virtual property ID. |
+| `--operation` | No | Delete operation. Use revoke to revoke instead of delete. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-property sql-rule-update
+
+Use when the user needs to update SQL virtual property rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-property sql-rule-update --project-id <project_id> --payload '{}'
+ae-cli analysis virtual-property sql-rule-update --dry-run
+```
+
+Capability id: `metadata.virtual_property.sql_rule_update`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

package/skills/ae-dataops/references/dataops-flow-create.md

@@ -120,7 +120,7 @@ ae-cli dataops_operations +get_flow_instance_detail --spaceCode "${spaceCode}" \
   --flowCode ${flowCode} --flowInstanceId ${flowInstanceId}
 ae-cli dataops_operations +get_task_instance_detail --spaceCode "${spaceCode}" \
   --flowCode ${flowCode} --flowInstanceId ${flowInstanceId} \
-  --taskName "${taskName}" --includeLog true
+  --taskInstanceId ${taskInstanceId} --includeLog true
 ```
 
 ---
@@ -139,7 +139,7 @@ ae-cli dataops_operations +get_task_instance_detail --spaceCode "${spaceCode}" \
 | `+get_task_params` | View DEV task parameter list | `--spaceCode` `--flowCode` `--taskCode` |
 | `+execute_flow` | Manual PROD execution | `--spaceCode` `--flowCode` `[--baseDate]` |
 | `dataops_operations +get_flow_instance_detail` | View operations instance DAG and task statuses | `--spaceCode` `--flowCode` `--flowInstanceId` |
-| `dataops_operations +get_task_instance_detail` | View operations task detail and optional logs | `--spaceCode` `--flowCode` `--flowInstanceId` (`--taskCode` or `--taskName`) `[--includeLog]` |
+| `dataops_operations +get_task_instance_detail` | View operations task detail and optional logs | `--spaceCode` `--flowCode` `--flowInstanceId` (`--taskInstanceId` or `--taskCode` or `--taskName`) `[--includeLog]` |
 | `+preview_release_flow` | Preview pending DEV-to-PROD release changes without publishing | `--spaceCode` `--flowCode` |
 | `+release_flow` | Submit DEV-to-PROD release | `--spaceCode` `--flowCode` |
 

package/skills/ae-dataops/references/dataops-flow-monitor.md

@@ -55,7 +55,7 @@ ae-cli dataops_operations +get_flow_instance_detail --spaceCode "${spaceCode}" \
 # Step 2: View task detail and logs
 ae-cli dataops_operations +get_task_instance_detail --spaceCode "${spaceCode}" \
   --flowCode ${flowCode} --flowInstanceId ${flowInstanceId} \
-  --taskName "${taskName}" --includeLog true
+  --taskInstanceId ${taskInstanceId} --includeLog true
 
 # Step 3: Re-execute after fixing
 ae-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
@@ -105,7 +105,7 @@ ae-cli dataops_flow +get_flow_overview --spaceCode "${spaceCode}" \
 | `+execute_flow` | Manual PROD execution | `--spaceCode` `--flowCode` `[--baseDate]` |
 | `dataops_operations +search_flow_instances` | Search operations workflow instances | `--spaceCode` `[--keyword]` `[--startDate]` `[--endDate]` `[--status]` `[--pageNum]` `[--pageSize]` |
 | `dataops_operations +get_flow_instance_detail` | Operations instance DAG and task statuses | `--spaceCode` `--flowCode` `--flowInstanceId` |
-| `dataops_operations +get_task_instance_detail` | Operations task detail and optional logs | `--spaceCode` `--flowCode` `--flowInstanceId` (`--taskCode` or `--taskName`) `[--includeLog]` |
+| `dataops_operations +get_task_instance_detail` | Operations task detail and optional logs | `--spaceCode` `--flowCode` `--flowInstanceId` (`--taskInstanceId` or `--taskCode` or `--taskName`) `[--includeLog]` |
 | `dataops_operations +stop_flow_instance` | Stop a running execution | `--spaceCode` `--flowCode` exactly one of `--executeId` or `--flowInstanceId` |
 | `+get_task_params` | DEV task parameter list | `--spaceCode` `--flowCode` `--taskCode` |
 | `+update_flow` | Update DEV workflow name and/or remark | `--spaceCode` `--flowCode` `[--flowName]` `[--remark]` |
@@ -118,7 +118,7 @@ ae-cli dataops_flow +get_flow_overview --spaceCode "${spaceCode}" \
 - **Flow update**: `+update_flow` requires `--spaceCode`, `--flowCode`, and at least one of `--flowName` or `--remark`. It returns `action/result/status`; `result` is an array with items containing `flowCode`, `operationStatus`, `nameChanged`, and optional `flowName`.
 - **High-frequency release flows**: `+list_high_frequency_release_flows` requires `--spaceCode`; `--days`, `--topN`, `--minCount`, and `--status` are optional. Defaults are `days=30`, `topN=10`, and `status=SUCCESS`. It returns `period`, `filters`, `flows`, `returnedCount`, and `nextAction`; flow items include `rank`, `flowCode`, `flowName`, `releaseCount`, `lastReleaseTime`, and `avgIntervalHours`.
 - **Operations instance search**: `dataops_operations +search_flow_instances` requires `--spaceCode`; `--keyword`, `--startDate`, `--endDate`, `--status`, `--pageNum`, and `--pageSize` are optional. `--keyword` fuzzy-matches `flowName` or `flowCode`. `pageNum` defaults to `1`; `pageSize` defaults to `20` and maxes at `100`. It returns `totalCount`, `returnedCount`, `pageNum`, `pageSize`, `hasMore`, `instances`, `statusCounts`, `triggerTypeCounts`, and `ownerCounts`.
-- **Task instance detail**: `dataops_operations +get_task_instance_detail` requires `--spaceCode`, `--flowCode`, `--flowInstanceId`, and either `--taskCode` or exact `--taskName`. `--taskCode` takes precedence when both are passed. `--includeLog` is optional and defaults to `false`. It returns `success`, `flowInstanceId`, `taskCode`, `taskName`, `taskInstanceId`, `status`, `task`, `taskInstance`, `definition`, and `log` only when requested.
+- **Task instance detail**: `dataops_operations +get_task_instance_detail` requires `--spaceCode`, `--flowCode`, `--flowInstanceId`, and one selector: `--taskInstanceId`, `--taskCode`, or exact `--taskName`. Prefer `--taskInstanceId` because retries can create multiple instances with the same task code/name. `--includeLog` is optional and defaults to `false`. It returns `success`, `flowInstanceId`, `taskCode`, `taskName`, `taskInstanceId`, `status`, `task`, `taskInstance`, `definition`, and `log` only when requested.
 - **env**: `DEV` (development) | `PROD` (production, instance list defaults to PROD)
 - **flow list paging**: `+list_flows` requires `--spaceCode`; `--keyword`, `--pageNum`, and `--pageSize` are optional. It returns `flows`, `totalCount`, `returnedCount`, `pageNum`, `pageSize`, and `hasMore`; flow items include `latestProductionInstance` only when available. `pageSize` defaults to `20` and maxes at `100`.
 - **Task parameters**: `+get_task_params` requires `--spaceCode`, `--flowCode`, and `--taskCode`; it has no optional flags. It queries DEV and returns `data` as an array. Items include fields such as `paramKey`, `paramType`, `paramDataType`, `paramFrom`, and built-in flags like `isBd`.

package/skills/ae-dataops/references/dataops-integration.md

@@ -18,6 +18,7 @@ Use the `dataops_integration` subcommand to manage datasources and sync solution
 - sourceConfig/sinkConfig/channelConfig/fieldsMapping are all JSON strings
 - Sync solution updates are not partial patches: call `+get_sync_detail --withParams true` first, then submit complete sourceConfig and sinkConfig JSON. Pass channelConfig and fieldsMapping when keeping or updating them
 - Test datasource connection before creating sync solution
+- `sinkConfig.dataSaveMode` codes are fixed: `1 = APPEND_DATA` (insert/append new data; UI label `插入新数据`), `2 = OVERWRITE` (`DROP_DATA`; UI label `覆盖写入`). Never describe `dataSaveMode=1` as overwrite; use `2` for overwrite.
 
 ---
 

package/skills/ae-engage/references/flow-node-config-schema.md

@@ -1,7 +1,7 @@
 # ae-engage +flow_node_config_schema
 
 
-Query the configuration schema for a flow node type.
+Query the configuration schema for one flow node type before constructing a `save_flow` node config.
 
 Mapped command: `ae-cli engage +flow_node_config_schema`
 
@@ -9,13 +9,34 @@ Mapped command: `ae-cli engage +flow_node_config_schema`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--node_type` | string | Yes | node type |
+| `--node_type` | string | Yes | Flow node type |
+
+## When To Use
+
+Call this before writing any non-trivial `save_flow` `nodes[].config` or `nodeConfigs[].config`. The response is the source of truth for:
+
+- `required` and `conditional_required` fields
+- defaulted fields that can be omitted from draft input
+- enum values and allowed modes
+- `minimal_valid`, `full_valid`, and `common_invalid` examples
+- submit-time requirements for stricter `save_submit_flow` validation
+
+Do not use this command to build an old full `FlowSaveReqDTO`, `nodeList`, or `edgeList`. `save_flow` uses compact `nodes` / `edges`.
+
+## Recent Save Flow Notes
+
+- `event_trigger` supports `targetUserType=1` custom and `targetUserType=3` all users; existing cluster `targetUserType=2` is not supported for this node.
+- `event_trigger` and `event_judge` A-segment trigger rules are non-branch rules and use `periodStart`, `periodEnd`, and `periodTimeSymbol`.
+- `event_split_flow` branch rules use `delayTime` and `delayTimeSymbol`; `branchType=1` also needs `targetClusterType`, and non-all-user branches need `clusterKey`.
+- Push nodes default `processType=1`, `enableChannelTouchLimits=0`, and `isOccasionUp=false`.
+- The validator normalizes compatible inputs before schema validation: apostrophe-prefixed field aliases, case-insensitive property aliases, `enableChannelTouchLimits` booleans, string `"0"`/`"1"` QP relations inside `targetClusterQp`, and `clusterPredictCount: null`.
+- For push nodes, `contentList[].content` should be a JSON array; the validator also accepts a JSON-stringified array for compatibility. For push `OBJ_ARRAY` params, `value` must still be a JSON array and `objArray` must be copied from `query_channel_detail data.config.paramsList[].objArray`.
 
 ## Enum Notes
 
 ### `--node_type`
 
-Common node types include:
+Schema-backed node types include:
 
 - `single_trigger`
 - `repeat_trigger`
@@ -25,15 +46,10 @@ Common node types include:
 - `message_push`
 - `wechat_push`
 - `webhook_push`
-- `config_push`
-- `tag`
 - `time_control`
 - `feature_split_flow`
 - `event_split_flow`
-- `trigger_prop_split_flow`
-- `percent_split_flow`
 - `ab_split_flow`
-- `race_split_flow`
 - `exit_flow`
 
 ## Examples
@@ -41,3 +57,11 @@ Common node types include:
 ```bash
 ae-cli engage +flow_node_config_schema --node_type message_push
 ```
+
+Typical flow:
+
+```bash
+ae-cli engage +flow_node_config_schema --node_type event_trigger
+ae-cli engage +validate_flow_node_config \
+  --node_type event_trigger --operation_mode save_flow --config '<config-json-string>'
+```