@thinkingai/ae-cli 6.0.22 → 6.0.27

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

@@ -0,0 +1,15 @@
+# analysis dashboard get
+
+Use when the user needs one dashboard detail, including basic metadata such as creator and create/update time, settings, reports, notes, and sharing information.
+
+Do not use to query report result data. Use `dashboard-report-data run` or `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard get --project-id <project_id> --dashboard-id <dashboard_id> [--use-cache true]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `use_cache`.
+
+Output is the gateway envelope. `data` contains the dashboard detail returned by the capability gateway.

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

@@ -0,0 +1,15 @@
+# analysis dashboard handover
+
+Use when the user explicitly wants to transfer one or more dashboards to another project user.
+
+Do not use to share dashboards without ownership transfer. Use `dashboard share`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard handover --project-id <project_id> --dashboard-ids '[1001,1002]' --to-user-id <user_id> --yes
+```
+
+Input sends `project_id`, `dashboard_ids`, and `to_user_id`.
+
+Output is the gateway envelope. `data` contains the handover result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard list
+
+Use when the user needs to find dashboards they can access, with optional keyword, owner, permission, favorite, or projection filters supported by the gateway payload.
+
+Do not use for dashboard report data. Use `dashboard-report-data run` or `dashboard-report-data export` instead.
+
+Command:
+
+```bash
+ae-cli analysis dashboard list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input uses `project_id` plus optional `query`, `fields`, `limit`, `offset`. Use `--payload` only when the dedicated gateway contract requires extra snake_case filters.
+
+Output is the gateway envelope. `data` contains dashboard summaries and paging metadata when returned by the gateway.

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

@@ -0,0 +1,25 @@
+# analysis dashboard-report-data export
+
+Use for dashboard report data queries that may be large or long-running.
+
+Do not use when the user needs a tiny immediate preview. Use `dashboard-report-data run` with a small `--limit`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-report-data export --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--start-time <time>] [--end-time <time>] [--artifact-format jsonl]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `format`. Use CLI flag `--artifact-format` for the gateway `format` input; `--format` is the CLI output formatter.
+
+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>`.
+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.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-report-data run
+
+Use for bounded inline dashboard report data queries when the expected result is small enough for immediate JSON output.
+
+Do not use for large or long-running result sets. Use `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-report-data run --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--start-time <time>] [--end-time <time>] [--limit 100] [--timeout-seconds 60]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `limit`.
+
+Output is the gateway envelope. `data` contains bounded inline report data.

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

@@ -0,0 +1,15 @@
+# analysis dashboard share
+
+Use when the user explicitly wants to add, remove, or batch modify dashboard sharing.
+
+Do not use to read sharing only. Use `dashboard share-info`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard share --project-id <project_id> --dashboard-id <dashboard_id> [--member-authorities '{...}'] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and either `member_authorities` or a backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard share-info
+
+Use when the user needs to inspect a dashboard's current sharing configuration.
+
+Do not use to modify sharing. Use `dashboard share`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard share-info --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains dashboard sharing members and permissions.

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

@@ -0,0 +1,15 @@
+# analysis dashboard task-status
+
+Use when the user needs scheduled task status for a dashboard.
+
+Do not use to update daily report configuration. Use `dashboard-daily-report update`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard task-status --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains scheduled task status.

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

@@ -0,0 +1,16 @@
+# analysis dashboard update
+
+Use when the user wants to update dashboard settings in batch or upsert a dashboard note.
+
+Do not use for moving/copying dashboards. Use `dashboard copy`, `dashboard handover`, or the relevant project-space/folder command.
+
+Command:
+
+```bash
+ae-cli analysis dashboard update --project-id <project_id> --operation settings --dashboard-ids '[1001,1002]' [--zone-offset 8] [--payload '{...}'] --yes
+ae-cli analysis dashboard update --project-id <project_id> --operation note-upsert --dashboard-id <dashboard_id> [--note-id <note_id>] [--note-title <title>] [--description <text>] --yes
+```
+
+Input sends `project_id`, `operation`, optional dashboard identifiers, setting fields (including `zone_offset` as hours, e.g. `8` for UTC+8), note fields, and optional `payload`.
+
+Output is the gateway envelope. `data` contains the update result.

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

@@ -0,0 +1,15 @@
+# analysis favorite add
+
+Use when the user wants to favorite one dashboard, BI panel, or folder.
+
+Do not use for sharing or moving assets.
+
+Command:
+
+```bash
+ae-cli analysis favorite add --project-id <project_id> [--asset-id <id>] [--asset-type dashboard|bi_panel|folder] [--space-id <space_id>] [--id <backend_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` and asset identity fields or backend-compatible `payload`.
+
+Output is the gateway envelope. `data` contains the favorite result.

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

@@ -0,0 +1,15 @@
+# analysis favorite remove
+
+Use when the user wants to remove favorite from one dashboard, BI panel, or folder.
+
+Do not use to delete the asset itself.
+
+Command:
+
+```bash
+ae-cli analysis favorite remove --project-id <project_id> [--asset-id <id>] [--asset-type dashboard|bi_panel|folder] [--space-id <space_id>] [--id <backend_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` and asset identity fields or backend-compatible `payload`.
+
+Output is the gateway envelope. `data` contains the remove-favorite result.

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

@@ -0,0 +1,15 @@
+# analysis folder create
+
+Use when the user explicitly wants to create a folder in personal space or a project space.
+
+Do not use to create a project space. Use `project-space create`.
+
+Command:
+
+```bash
+ae-cli analysis folder create --project-id <project_id> --folder-name <name> [--space-id <space_id>] [--parent-folder-id <folder_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `folder_name`, and optional `space_id`, `parent_folder_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the created folder result.

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

@@ -0,0 +1,15 @@
+# analysis folder delete
+
+Use when the user explicitly wants to delete one or more folders.
+
+Do not use for deleting dashboards or BI panels inside a folder. Use the asset delete command.
+
+Command:
+
+```bash
+ae-cli analysis folder delete --project-id <project_id> [--folder-id <folder_id>] [--folder-ids '[1,2]'] [--space-id <space_id>] --yes
+```
+
+Input sends `project_id`, either `folder_id` or `folder_ids`, and optional `space_id`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis folder members
+
+Use when the user needs to inspect folder members.
+
+Do not use to modify members. Use `folder share`.
+
+Command:
+
+```bash
+ae-cli analysis folder members --project-id <project_id> --folder-id <folder_id>
+```
+
+Input sends `project_id` and `folder_id`.
+
+Output is the gateway envelope. `data` contains folder members.

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

@@ -0,0 +1,15 @@
+# analysis folder share
+
+Use when the user wants to add, remove, or batch modify folder sharing members.
+
+Do not use to inspect members only. Use `folder members`.
+
+Command:
+
+```bash
+ae-cli analysis folder share --project-id <project_id> --folder-id <folder_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `folder_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis project-space create
+
+Use when the user explicitly wants to create a project space.
+
+Do not use to create folders inside a space. Use `folder create`.
+
+Command:
+
+```bash
+ae-cli analysis project-space create --project-id <project_id> [--space-name <name>] [--space-desc <text>] [--avatar-type <type>] [--color-key <key>] [--avatar <value>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` plus optional space metadata and `payload`. `avatar_type` defaults to `1` (word avatar) when omitted. When using `--payload`, put custom avatar fields in the payload or pass explicit top-level flags.
+
+Output is the gateway envelope. `data` contains the created project-space result.

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

@@ -0,0 +1,15 @@
+# analysis project-space delete
+
+Use when the user explicitly wants to delete one or more project spaces.
+
+Do not use for removing dashboard or folder membership. Use the matching resource command.
+
+Command:
+
+```bash
+ae-cli analysis project-space delete --project-id <project_id> [--space-id <space_id>] [--space-ids '[1,2]'] --yes
+```
+
+Input sends `project_id` and either `space_id` or `space_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,18 @@
+# analysis project-space get
+
+Use when the user needs one project space detail or name.
+
+Do not use to list all spaces. Use `project-space list`.
+
+Command:
+
+```bash
+ae-cli analysis project-space get --project-id <project_id> --space-id <space_id> [--fields '["spaceId","spaceName"]']
+```
+
+Input sends `project_id`, `space_id`, and optional `fields`.
+
+Supported fields are `spaceId`, `spaceName`, `spaceDesc`, `avatarType`, `colorKey`, `avatar`,
+`allAuthUserAuthority`, `createTime`, `updateTime`, and `owner`.
+
+Output is the gateway envelope. `data` contains project-space detail with snake_case field names.

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

@@ -0,0 +1,15 @@
+# analysis project-space list
+
+Use when the user needs project spaces they can access.
+
+Do not use for project lookup or project ID verification. Use `analysis_common +list_projects`.
+
+Command:
+
+```bash
+ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
+
+Output is the gateway envelope. `data` contains project-space summaries.

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

@@ -0,0 +1,15 @@
+# analysis project-space members
+
+Use when the user needs to inspect project-space members.
+
+Do not use to modify members. Use `project-space share`.
+
+Command:
+
+```bash
+ae-cli analysis project-space members --project-id <project_id> --space-id <space_id>
+```
+
+Input sends `project_id` and `space_id`.
+
+Output is the gateway envelope. `data` contains project-space members.

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

@@ -0,0 +1,15 @@
+# analysis project-space share
+
+Use when the user wants to add, remove, or batch modify project-space sharing members.
+
+Do not use to inspect members only. Use `project-space members`.
+
+Command:
+
+```bash
+ae-cli analysis project-space share --project-id <project_id> --space-id <space_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `space_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis public-link create
+
+Use when the user explicitly wants to generate a public link for a dashboard or BI panel.
+
+Do not use for internal resource URLs. Use `analysis_common +get_resource_url` when applicable.
+
+Command:
+
+```bash
+ae-cli analysis public-link create --project-id <project_id> --resource-type dashboard --resource-id <id> --effective-at "2026-07-08 00:00:00" --expires-at "2026-08-08 00:00:00" [--access-controls '{...}'] [--remark <text>] [--company-id <company_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `resource_type`, `resource_id`, `effective_at`, `expires_at`, and optional public-link fields.
+
+Output is the gateway envelope. `data` contains the generated public-link result.

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

@@ -0,0 +1,15 @@
+# analysis public-link delete
+
+Use when the user explicitly wants to delete one or more public links.
+
+Do not use to temporarily stop access while keeping records. Use `public-link offline`.
+
+Command:
+
+```bash
+ae-cli analysis public-link delete --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>] --yes
+```
+
+Input sends `project_id`, optional `company_id`, and either `link_id` or `link_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis public-link list
+
+Use when the user needs public links in a project.
+
+Do not use for dashboard or BI panel asset listing. Use the matching list command.
+
+Command:
+
+```bash
+ae-cli analysis public-link list --project-id <project_id> [--query <keyword>] [--fields '["id","resource_id"]'] [--limit 20] [--offset 0]
+```
+
+Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
+
+Output is the gateway envelope. `data` contains public-link summaries.

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

@@ -0,0 +1,15 @@
+# analysis public-link offline
+
+Use when the user wants to take one or more public links offline without deleting records.
+
+Do not use to permanently delete links. Use `public-link delete`.
+
+Command:
+
+```bash
+ae-cli analysis public-link offline --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>] --yes
+```
+
+Input sends `project_id`, optional `company_id`, and either `link_id` or `link_ids`.
+
+Output is the gateway envelope. `data` contains the offline result.

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

@@ -0,0 +1,15 @@
+# analysis public-link update
+
+Use when the user wants to edit an existing public link.
+
+Do not use to take a link offline. Use `public-link offline`.
+
+Command:
+
+```bash
+ae-cli analysis public-link update --project-id <project_id> --link-id <link_id> --effective-at "2026-07-08 00:00:00" --expires-at "2026-08-08 00:00:00" [--access-controls '{...}'] [--remark <text>] [--company-id <company_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `link_id`, effective/expiration time, and optional public-link fields.
+
+Output is the gateway envelope. `data` contains the update result.

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

@@ -0,0 +1,15 @@
+# analysis query cancel
+
+Use to cancel an async capability-gateway query or export by `run_id`.
+
+Do not use for MCP query cancellation by `request_id`; use `analysis +cancel_query`.
+
+Command:
+
+```bash
+ae-cli analysis query cancel --run-id <run_id> [--reason <reason>] --yes
+```
+
+Input sends `run_id` and optional `reason`.
+
+Output is the gateway envelope. `data` contains the cancellation result.

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-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>'
+```