@thinkingai/ae-cli 6.0.30 → 6.0.31

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

@@ -2,20 +2,21 @@
 
 Use when the user needs to delete a metric.
 
-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.
+Do not use it to remove a metric from one report or to delete by guessed ID; resolve and inspect the metric first.
 
 Command:
 
 ```bash
-ae-cli analysis-meta metric delete --project-id <project_id> --metric-id <metric_id>
-ae-cli analysis-meta metric delete --dry-run
+ae-cli analysis-meta metric delete --project-id <project_id> --metric-id <metric_id> --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
+ae-cli analysis-meta metric delete --project-id <project_id> --metric-id <metric_id> --yes
 ```
 
 Capability id: `metadata.metric.delete`.
 
 Input sends `project_id`, `metric_id`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output is a successful gateway envelope with no business data. Verify with `metric list|get`.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 Use when the user needs to get metric definition, events, and params.
 
-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.
+Do not use it to query metric values or trends; it returns the saved metric definition only.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.metric.get`.
 
 Input sends `project_id`, `metric_id`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.metric` contains the saved metric definition, or no metric when the ID does not resolve.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 Use when the user needs to list project metrics.
 
-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.
+Do not use it to calculate metric values; use report/dashboard/ad-hoc data routing for result queries.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.metric.list`.
 
 Input sends `project_id`, `ignore_authentication`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.metrics[]` contains project metric summaries and authentication decoration unless explicitly skipped.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,23 +2,29 @@
 
 Use when the user needs to update metric definition, name, and remark.
 
-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.
+Do not use it to query metric values. Use `analysis_meta +update_metric` only when the gateway capability is unavailable.
 
 Command:
 
 ```bash
-ae-cli analysis-meta metric update --project-id <project_id> --payload '{}'
-ae-cli analysis-meta metric update --dry-run
+ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-desc 'New display name' --metric-remark 'New remark'
+ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-desc 'New display name' --dry-run
 ```
 
 Capability id: `metadata.metric.update`.
 
-Input sends `project_id`, `payload`.
+Input sends typed snake_case fields.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.metric` contains the updated summary for a full-definition update containing `metric_events`. A display-name/remark-only edit succeeds without business data.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--payload` | Yes | Capability payload JSON. |
+| `--metric-id` | Yes | Metric ID. |
+| `--metric-name` | No | Metric technical name for a full-definition update. |
+| `--metric-desc` | No | Metric display name. |
+| `--metric-remark` | No | Metric remark. |
+| `--metric-mode` | No | Metric model mode for a full-definition update. |
+| `--metric-events` | No | Metric event-analysis QP JSON array for a full-definition update. |
+| `--metric-params` | No | Metric params JSON object. |

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

@@ -0,0 +1,25 @@
+# analysis-governance operation-record export
+
+Use when the user needs to export one asset batch operation record result through the capability gateway.
+
+Do not use it to list records or export asset rows; resolve one real `record_id` first, then export that operation's result as XLSX.
+
+Command:
+
+```bash
+ae-cli analysis-governance operation-record export --project-id <project_id> --payload '{}'
+ae-cli analysis-governance operation-record export --dry-run --project-id <project_id>
+```
+
+Capability id: analysis_meta.asset_operation_record.export.
+
+Input sends project_id, payload, record_id. Payload keys must follow the common-service snake_case input schema; do not send camelCase aliases.
+
+Output `data` is an async XLSX descriptor with `run_id`, `artifact_id`, status, and expiry fields. Inspect and download that exact export.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| --project-id | Yes | Numeric project ID. |
+| --record-id | No | Operation record ID; required unless provided inside payload. |
+| --payload | No | Optional snake_case object carrying the same fields. Use this for complex governance filters or backend-shaped payloads. |

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

@@ -0,0 +1,31 @@
+# analysis-governance operation-record list
+
+Use when the user needs to list asset batch operation records through the capability gateway.
+
+Do not use it to submit a new batch operation; use it to find and inspect records produced by prior asset governance actions.
+
+Command:
+
+```bash
+ae-cli analysis-governance operation-record list --project-id <project_id> --payload '{}'
+ae-cli analysis-governance operation-record list --dry-run --project-id <project_id>
+```
+
+Capability id: analysis_meta.asset_operation_record.list.
+
+Input sends project_id, payload, type, status, query, sort_field, sort_order, limit, offset. Payload keys must follow the common-service snake_case input schema; do not send camelCase aliases.
+
+Output `data` is the paged batch-operation record result. Use record status to distinguish submitted, running, successful, and failed work before taking another action.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| --project-id | Yes | Numeric project ID. |
+| --type | No | Batch operation type. |
+| --status | No | Operation status JSON array. |
+| --query | No | Keyword filter. |
+| --sort-field | No | Sort field. |
+| --sort-order | No | Sort order: asc or desc. |
+| --limit | No | Inline page size. |
+| --offset | No | Zero-based page offset. |
+| --payload | No | Optional snake_case object carrying the same fields. Use this for complex governance filters or backend-shaped payloads. |

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

@@ -4,15 +4,14 @@ Use when the user explicitly wants to create a project space.
 
 Do not use to create folders inside a space. Use `analysis.folder.create` via capability run.
 
-This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md), then:
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md) (on-demand validate/dry-run table), then:
 
 ```bash
 ae-cli capability inspect analysis.project_space.create
-ae-cli capability dry-run analysis.project_space.create --input '{"project_id":1,"space_name":"lds-test-071301","avatar_type":1}'
 ae-cli capability run analysis.project_space.create --input '{"project_id":1,"space_name":"lds-test-071301","avatar_type":1}'
 ```
 
-`risk=write` — no chat confirmation required after dry-run succeeds.
+`risk=write` — no chat confirmation required.
 
 Input uses snake_case JSON. Common fields:
 

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

@@ -7,9 +7,11 @@ Do not use for project lookup or project ID verification. Use `analysis_common +
 Command:
 
 ```bash
-ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 50] [--offset 0]
 ```
 
 Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
 
+When `has_more=true`, continue only with the returned `next_offset`; do not calculate the next page locally.
+
 Output is the gateway envelope. `data` contains project-space summaries.

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

@@ -4,15 +4,14 @@ Use when the user wants to modify project-space sharing members.
 
 Do not use to inspect members only. Use `analysis.project_space.members` via `capability search/inspect/run`; see [`analysis_gateway_assets.md`](analysis_gateway_assets.md) L3 members section.
 
-This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md), then:
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md) (on-demand validate/dry-run table), then:
 
 ```bash
 ae-cli capability inspect analysis.project_space.share
-ae-cli capability dry-run analysis.project_space.share --input '{"project_id":1,"space_id":10,"payload":{...}}'
 ae-cli capability run analysis.project_space.share --input '{"project_id":1,"space_id":10,"payload":{...}}'
 ```
 
-`risk=write` — no chat confirmation required after dry-run succeeds.
+`risk=write` — no chat confirmation required. Compose nested `payload` from the inspect `input_schema`.
 
 Input uses snake_case JSON. Common fields:
 

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

@@ -2,7 +2,7 @@
 
 Use when the user needs to list property metadata change logs.
 
-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.
+Do not use it for the current property definition or historical data values; use `property get` or an analysis query.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.changelog_list`.
 
 Input sends `project_id`, `table_type`, `prop_name`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.changelogs[]` contains metadata change records for the property.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,12 +2,12 @@
 
 Use when the user needs to create event or user properties and optionally associate events.
 
-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.
+Do not use it for virtual properties or description-only updates. Choose `table-type event|user` first because the two payload variants differ.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property create --project-id <project_id> --table-type <table_type> --payload '{}'
+ae-cli analysis-meta property create --project-id <project_id> --table-type event --payload '{"prop_name":"amount","prop_desc":"Amount","select_type":"number","common_prop":false,"super_event_ids":[<event_id>]}'
 ae-cli analysis-meta property create --dry-run
 ```
 
@@ -15,11 +15,11 @@ Capability id: `metadata.property.create`.
 
 Input sends `project_id`, `table_type`, `payload`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output is a successful gateway envelope with no business data. Read back with `property get` using the same table type.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--table-type` | Yes | Property table type. |
-| `--payload` | Yes | Capability payload JSON. |
+| `--payload` | Yes | Event form requires `prop_name`, `select_type`; optional `prop_desc`, `prop_remark`, `common_prop`, `super_event_ids`, `source_event_prop`. User form requires `prop_name`, `select_type`; optional `prop_desc`, `prop_remark`, `source_user_prop`. Source objects use `prop_name`, `source_type`, optional `source_route_code`. |

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

@@ -2,20 +2,21 @@
 
 Use when the user needs to batch delete properties or virtual 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.
+Do not use it before `property influence-list` is reviewed for every target, and do not mix event/user table types.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property delete --project-id <project_id> --table-type <table_type> --prop-names '{}'
-ae-cli analysis-meta property delete --dry-run
+ae-cli analysis-meta property delete --project-id <project_id> --table-type event --prop-names '["amount"]' --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
+ae-cli analysis-meta property delete --project-id <project_id> --table-type event --prop-names '["amount"]' --yes
 ```
 
 Capability id: `metadata.property.delete`.
 
 Input sends `project_id`, `table_type`, `prop_names`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output is a successful gateway envelope with no business data. Verify with `property list`.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 Use when the user needs to get one event or user property metadata detail.
 
-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.
+Do not use it for property values or fuzzy discovery; use an analysis query or `property list`.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.get`.
 
 Input sends `project_id`, `table_type`, `prop_name`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.property` contains the event/user property metadata detail.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,12 +2,12 @@
 
 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.
+Do not use it for deletion: this keeps the property but changes metadata visibility. Keep all targets in one table type.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property hide-update --project-id <project_id> --table-type <table_type> --prop-names '{}' --is-hide true
+ae-cli analysis-meta property hide-update --project-id <project_id> --table-type event --prop-names '["amount"]' --is-hide true
 ae-cli analysis-meta property hide-update --dry-run
 ```
 
@@ -15,7 +15,7 @@ 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.
+Output is a successful gateway envelope with no business data. Verify with `property list|get`.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 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.
+Do not use it as mutation or as proof that deletion is safe without reviewing every returned dependency.
 
 Command:
 
@@ -15,7 +15,7 @@ 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.
+Output is the snake_case property influence object returned by Common, including dependent assets and operation constraints.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 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.
+Do not use it for property values or across mixed table types; select the event/user scope explicitly.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.list`.
 
 Input sends `project_id`, `table_type`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.properties[]` contains property metadata for the selected table type.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 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.
+Do not use it for user properties or for event result data; it resolves event metadata related to one event property.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.related_events`.
 
 Input sends `project_id`, `prop_name`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.events[]` contains super events related to the event property.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,12 +2,12 @@
 
 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.
+Do not use it for display-name/remark-only edits; use `property update`. Choose the same table type and payload variant as the existing property.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property relation-update --project-id <project_id> --table-type <table_type> --payload '{}'
+ae-cli analysis-meta property relation-update --project-id <project_id> --table-type event --payload '{"prop_name":"amount","select_type":"number","super_event_ids":[<event_id>]}'
 ae-cli analysis-meta property relation-update --dry-run
 ```
 
@@ -15,11 +15,11 @@ 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.
+Output is a successful gateway envelope with no business data. Read back with `property get`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--table-type` | Yes | Property table type. |
-| `--payload` | Yes | Capability payload JSON. |
+| `--payload` | Yes | Complete event/user property object in the same shape documented by `property create`; relation/source fields replace the current definition rather than patching one nested field. |

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

@@ -2,7 +2,7 @@
 
 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.
+Do not use it to change source/event relations or select type; use `property relation-update` with the complete definition.
 
 Command:
 
@@ -15,7 +15,7 @@ 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.
+Output is a successful gateway envelope with no business data. Read back with `property get`.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -7,7 +7,7 @@ Do not use for internal resource URLs. Use `analysis_common +get_resource_url` w
 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
+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 '{...}']
 ```
 
 Input sends `project_id`, `resource_type`, `resource_id`, `effective_at`, `expires_at`, and optional public-link fields.

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

@@ -7,6 +7,8 @@ Do not use to temporarily stop access while keeping records. Use `public-link of
 Command:
 
 ```bash
+ae-cli analysis public-link delete --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>] --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
 ae-cli analysis public-link delete --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>] --yes
 ```
 

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

@@ -7,9 +7,11 @@ Do not use for dashboard or BI panel asset listing. Use the matching list comman
 Command:
 
 ```bash
-ae-cli analysis public-link list --project-id <project_id> [--query <keyword>] [--fields '["id","resource_id"]'] [--limit 20] [--offset 0]
+ae-cli analysis public-link list --project-id <project_id> [--query <keyword>] [--fields '["id","resource_id"]'] [--limit 50] [--offset 0]
 ```
 
 Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
 
+When `has_more=true`, continue only with the returned `next_offset`; do not calculate the next page locally.
+
 Output is the gateway envelope. `data` contains public-link summaries.

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

@@ -7,7 +7,7 @@ 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
+ae-cli analysis public-link offline --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>]
 ```
 
 Input sends `project_id`, optional `company_id`, and either `link_id` or `link_ids`.

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

@@ -7,7 +7,7 @@ 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
+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 '{...}']
 ```
 
 Input sends `project_id`, `link_id`, effective/expiration time, and optional public-link fields.

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

@@ -7,7 +7,7 @@ Do not use for MCP query cancellation by `request_id`; use `analysis +cancel_que
 Command:
 
 ```bash
-ae-cli analysis query cancel --run-id <run_id> [--reason <reason>] --yes
+ae-cli analysis query cancel --run-id <run_id> [--reason <reason>]
 ```
 
 Input sends `run_id` and optional `reason`.

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

@@ -0,0 +1,47 @@
+# analysis query create-result-cluster
+
+Precondition: the upstream response must have `result_cluster_available=true` and the selected source must contain `target_contract`. If either is absent, do not call this command or reconstruct a target from display text.
+
+Save users matched by a previous analysis result target as a reusable result cluster.
+
+Use this after any analysis data command that returns `query_context_id`:
+
+- `analysis adhoc run`
+- `analysis adhoc export`
+- `analysis report-data run`
+- `analysis report-data export`
+- `analysis dashboard-report-data run`
+- `analysis dashboard-report-data export`
+
+Do not pass raw QP.
+
+## Command
+
+```bash
+ae-cli analysis query create-result-cluster \
+  --query-context-id <query_context_id> \
+  --target '<json>' \
+  --cluster-name <cluster_name> \
+  [--display-name <display_name>] \
+  [--zone-offset 8] \
+  [--timeout-seconds 60]
+```
+
+## Input
+
+- `--query-context-id`: returned by an analysis data run/export submit response, or by the first metadata line of a JSONL artifact.
+- `--target`: pass the selected source's `target_contract.default_target` directly, or copy it and replace only fields named by `target_contract.copy_from_selected_result` for a specific row or cell.
+- `--cluster-name`: result cluster name.
+- `--display-name`: optional display name.
+
+Do not use raw QP or reconstruct the first query request. The server resolves the source QP from Redis by `query_context_id`.
+
+## Target
+
+`--target` uses the same machine-readable `sources[].target_contract` contract as [`drilldown_users_run.md`](drilldown_users_run.md).
+
+If one `query_context_id` contains multiple report sources, include `report_id`. If it contains multiple BI chart sources, include `chart_id`. BI SQL chart contexts normally return `result_cluster_available=false`; do not create a result cluster unless the first response explicitly says `result_cluster_available=true`.
+
+## Output
+
+The response contains the result cluster creation result from the analysis service.

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

@@ -0,0 +1,15 @@
+# analysis report-abnormal get
+
+Use when the user needs abnormal dependency information for one saved report.
+
+Do not use for dashboard-level abnormal information. Use `dashboard abnormal-get` for dashboard dependencies.
+
+Command:
+
+```bash
+ae-cli analysis report-abnormal get --project-id <project_id> --report-id <report_id>
+```
+
+Input sends `project_id` and `report_id`.
+
+Output is the gateway envelope. `data` contains report abnormal asset summary and node details when returned by the gateway.

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

@@ -0,0 +1,15 @@
+# analysis report-change-log get
+
+Use when the user needs a specific report change log detail, including AI QP definition when available.
+
+Do not use for rollback. Use `report-version rollback` after choosing a version from `report-change-log list`.
+
+Command:
+
+```bash
+ae-cli analysis report-change-log get --project-id <project_id> --report-id <report_id> [--history-version <version>]
+```
+
+Input sends `project_id`, `report_id`, and optional `version` from CLI `--history-version`.
+
+Output is the gateway envelope. `data` contains change log fields and may include `model_type` plus AI QP `definition`.

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

@@ -0,0 +1,15 @@
+# analysis report-change-log list
+
+Use when the user needs the change history of one saved report.
+
+Do not use for current report definition. Use `report get` for the current AI QP definition.
+
+Command:
+
+```bash
+ae-cli analysis report-change-log list --project-id <project_id> --report-id <report_id>
+```
+
+Input sends `project_id` and `report_id`.
+
+Output is the gateway envelope. `data` contains change log summaries and `total`. Raw report QP fields are not returned in the list.