@thinkingai/ae-cli 6.0.30 → 6.0.32

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

@@ -1,24 +1,39 @@
 # analysis-meta property list
 
-Use when the user needs to list event or user properties.
+Use when the user needs to browse or search event/user property metadata.
 
-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. Use this command only when the user explicitly wants to inspect metadata or when a prior compiler error asks for disambiguation.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property list --project-id <project_id> --table-type <table_type>
+ae-cli analysis-meta property list --project-id <project_id>
+ae-cli analysis-meta property list --project-id <project_id> --scope event --event-name purchase --query demo
+ae-cli analysis-meta property list --project-id <project_id> --query demo --fields '["prop_id","prop_name","prop_desc","prop_remark","select_type","table_type","authentication_status"]' --limit 20 --offset 0
 ae-cli analysis-meta property list --dry-run
 ```
 
 Capability id: `metadata.property.list`.
 
-Input sends `project_id`, `table_type`.
+Input sends `project_id` and optional `table_type`, `scope`, `event_name`, `query`, `fields`, `limit`, `offset`, `authenticated_only`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.properties[]` contains property metadata. When `limit` or `offset` is provided, output also includes `total`, `limit`, `offset`, and `has_more`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--table-type` | Yes | Property table type. |
+| `--table-type` | No | Optional property table type: `event` or `user`. |
+| `--scope` | No | Optional property scope: `event` or `user`. If omitted, all scopes are queried. |
+| `--event-name` | No | Optional event name filter for event properties. |
+| `--query` | No | Optional keyword filter. Fuzzy match is applied to property name, description, and remark. |
+| `--fields` | No | Optional fields to return as a JSON array. Supported fields: `prop_id`, `prop_name`, `prop_desc`, `prop_remark`, `select_type`, `table_type`, `sub_table_type`, `authentication_status`. |
+| `--limit` | No | Optional page size. |
+| `--offset` | No | Optional zero-based page offset. |
+| `--authenticated-only` | No | When true, return only authenticated properties. |
+
+## Decision Rules
+
+- Prefer `--scope event` or `--scope user` when the user needs a specific table type.
+- Use `--authenticated-only true` only when the user explicitly asks for authenticated assets.
+- For ad-hoc analysis, pass the user's property wording in the AI-facing `definition` instead of pre-querying property metadata.

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

@@ -2,12 +2,12 @@
 
 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.
+Do not use for internal resource URLs. Use `analysis-meta asset url-get` 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
+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,29 @@
+# analysis query create-result-cluster
+
+Save the user or custom-entity population behind one selected synchronous-preview cell as that subject's reusable result cluster.
+
+Read [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md) first. The selected metric/action must advertise `create_result_cluster`. `EVENT_LIST` and `NONE` analysis angles cannot be saved as a result cluster.
+
+## Command
+
+```bash
+ae-cli analysis query create-result-cluster \
+  --query-context-id <sync_preview_query_context_id> \
+  [--source '{"report_id":1001}'] \
+  --coordinate '<merged returned row/column/metric coordinate>' \
+  --cluster-name <unique_name> \
+  [--display-name <display_name>] \
+  [--zone-offset 8] \
+  [--timeout-seconds 180]
+```
+
+## Input rules
+
+- `--query-context-id`, `--source`, and all coordinate fragments must come from the same synchronous `adhoc run`, `report-data run`, or `dashboard-report-data run` response.
+- Match the desired visible row and column in `source.drilldown.row_options`/`column_options`, select the correct metric option, and shallow-merge only their `coordinate` fragments.
+- Never pass `target_id`, raw QP, display-only dates, option presentation fields, or data from an export/download. Exports do not create query contexts.
+- `--cluster-name` must be unique in the project and contain the backend-supported identifier characters.
+
+The saved cluster subject is `source.drilldown.subject` or the selected event metric's `subject`. `USER_LIST` creates a user result cluster. `ENTITY_LIST` creates a result cluster for that custom entity; do not relabel it as a user cluster.
+
+The response must contain the backend cluster creation result. A successful capability envelope without a created cluster identifier/result is not sufficient evidence of completion.

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.

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

@@ -0,0 +1,29 @@
+# analysis report create
+
+Use when the user explicitly wants to create a saved analysis report from an AI QP definition.
+
+Do not use raw QP, `analysis_query`, `events`, `event_view`, or `visual_view`. The gateway accepts `model_type` plus AI QP `definition`.
+
+Read [`ai_models.md`](ai_models.md) for the single AI-facing model registry. Report create supports the 12 analysis models plus `tag` for saved tag report data.
+
+Command:
+
+```bash
+ae-cli analysis report create --project-id <project_id> --report-name "Demo" --model-type event --definition '{...}' [--report-desc "..."] [--dashboard-ids "[1001]"]
+```
+
+Input sends `project_id`, `report_name`, `model_type`, `definition`, optional `report_desc`, `cache_seconds`, `query_duration_ms`, and `dashboard_ids`.
+
+Output is the gateway envelope. `data` contains the created `report_id`, creation status, normalized `model_type`, AI QP `definition`, and optional resolution warnings.
+
+## SQL dynamic parameter shortest path
+
+When a SQL report contains a `${...}` placeholder, define its saved default in the same AI-facing `definition`. Example:
+
+```bash
+ae-cli analysis report create --project-id <project_id> --report-name "Recent SQL" --model-type sql --definition '{"sql":"select * from events where ${PartDate:ds} limit 100","params":[{"name":"ds","type":"part_date","recent_day":"1-7"}]}'
+```
+
+After creation, keep the `report_id` returned by this exact create response. To verify the report, query the saved default first with `analysis report-data run` and omit `--sql-params`; then make one second query with a value-only `--sql-params` override. Do not rebuild internal `sqlViewParams` or guess an ID.
+
+After any successful report create, call `analysis-meta asset url-get` with that returned `report_id` and output its `markdown_link`.

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

@@ -0,0 +1,37 @@
+# analysis report-data export
+
+Submit saved report data as a downloadable async artifact. It covers the 12 analysis report models from `ai_models.md` plus tag report data; tags are report-data only and are not ad-hoc `model_type` values.
+
+Before adding overrides, call `analysis report get` for every report. The model matrix is the same as `report-data run`: SQL accepts only saved `definition.params` names through `--sql-params`; non-SQL analysis models accept filters/group/time overrides; tag executes its saved definition. Never put generic overrides and `--sql-params` in one homogeneous-model request.
+
+Routing: read [`analysis_data_retrieval.md`](analysis_data_retrieval.md) before choosing this `export` command instead of `report-data run`.
+
+Do not use this command for bounded inline previews; use `report-data run` when the requested result fits the sync data retrieval rule.
+
+Command:
+
+```bash
+# Non-SQL analysis report
+ae-cli analysis report-data export --project-id <project_id> --report-ids '[1001]' --filters '{"relation":"and","items":[{"field":{"name":"country","type":"user_property"},"operator":"eq","values":["US"]}]}' --artifact-format jsonl
+
+# SQL report
+ae-cli analysis report-data export --project-id <project_id> --report-ids '[2001]' --sql-params '[{"name":"platform","value":"ios"}]' --artifact-format jsonl
+```
+
+Input sends `project_id`, `report_ids`, optional `request_id`, `filters`, `group_by`, `sql_params`, `start_time`, `end_time`, `time_granularity`, `use_cache`, artifact `format`, and `timeout_seconds`. Async export has no inline row limit. Runtime defaults to and is capped at 21600 seconds (6 hours); cancel earlier with `analysis query cancel --run-id <run_id>`. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+
+Override model:
+
+- `filters`: AI-facing intent object `{relation:"and|or", items:[{field:{name,type?}, operator, values?}]}`. `field.type` supports `event_property`, `user_property`, `cluster`, and `tag`; omit it only when the field name is unambiguous. Use field names from `analysis report get` definition output or metadata commands. Do not pass raw QP fields such as `taFilters`, `junctionKind`, `columnName`, `tableType`, or `selectType`.
+- `group-by`: AI-facing intent array `[{field:{name,type?}}]`. Use the same field model as report definitions. Do not pass raw `TaGroupByVo`. Time granularity is controlled by `--time-granularity`, not by `--group-by`.
+- `sql-params`: SQL report dynamic parameter value overrides. First read `analysis report get`; every name must exist in every target SQL report's `definition.params`. Time fields require a saved `part_date` or time parameter. Send only override values; do not send definition fields.
+
+Mixed-model export batches are best-effort rather than rejected only for being mixed. Prefer one model per overridden export because artifact formats cannot surface submission-time warnings as prominently as inline `meta.warnings`.
+
+Output is the gateway envelope. `data` contains opaque `run_id` and `artifact_id`, lifecycle status and expiration, and effective timeout/deadline fields. Exports do not create `query_context_id`. Inspect/download through the dedicated CLI commands using the IDs.
+
+Keep `run_id` and `artifact_id` from the same export response. Inspect that exact `run_id`, then download only that paired `artifact_id`; never combine IDs from different exports.
+
+An empty artifact is a successful query and means the requested time range has no data. If every requested report explicitly fails, the run reaches `FAILED` instead of completing an error-only artifact. Mixed exports may contain explicit per-report error markers alongside successful report data.
+
+Never use the export response or downloaded rows as a drilldown/result-cluster source. Run a bounded synchronous preview containing the desired cell first.

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

@@ -0,0 +1,45 @@
+# analysis report-data run
+
+Execute bounded inline data from one or more saved reports.
+
+Routing: read [`analysis_data_retrieval.md`](analysis_data_retrieval.md) before choosing this `run` command instead of `report-data export`.
+
+Do not use this command for full, unknown-size, larger than 1000-row, or long-running report data; use `report-data export`.
+
+This gateway report-data capability executes saved reports with model-specific overrides. It covers the 12 analysis report models from `ai_models.md` plus tag report data; tags are report-data only and are not ad-hoc `model_type` values.
+
+Before adding any query-condition override, call `analysis report get` for every `report_id` and branch on `data.model_type`:
+
+| Saved report model | Valid query-condition overrides |
+|---|---|
+| `sql` | Only `--sql-params`. SQL time conditions must be saved `definition.params` items of type `part_date` or time and overridden there. |
+| Non-SQL analysis model | `--filters`, `--group-by`, `--start-time`, `--end-time`, `--time-granularity` |
+| `tag` | No generic report-data override. Execute the saved tag definition or use `analysis history-tag-data run` for a tag-specific view. |
+
+Command:
+
+```bash
+# Non-SQL analysis report
+ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]' --filters '{"relation":"and","items":[{"field":{"name":"country","type":"user_property"},"operator":"eq","values":["US"]}]}' --start-time 2026-07-01 --end-time 2026-07-09 --limit 20
+
+# SQL report, after analysis report get confirms definition.params contains platform
+ae-cli analysis report-data run --project-id <project_id> --report-ids '[2001]' --sql-params '[{"name":"platform","value":"ios"}]' --limit 20
+```
+
+Input sends `project_id`, `report_ids`, optional `request_id`, `filters`, `group_by`, `sql_params`, `start_time`, `end_time`, `time_granularity`, `use_cache`, `limit`, and `timeout_seconds`. Control defaults: `--limit` default 100 / max 1000, `--timeout-seconds` default 120 / max 180. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+
+Override model:
+
+- `filters`: AI-facing intent object `{relation:"and|or", items:[{field:{name,type?}, operator, values?}]}`. `field.type` supports `event_property`, `user_property`, `cluster`, and `tag`; omit it only when the field name is unambiguous. Use field names from `analysis report get` definition output or metadata commands. Do not pass raw QP fields such as `taFilters`, `junctionKind`, `columnName`, `tableType`, or `selectType`.
+- `group-by`: AI-facing intent array `[{field:{name,type?}}]`. Use the same field model as report definitions. Do not pass raw `TaGroupByVo`. Time granularity is controlled by `--time-granularity`, not by `--group-by`.
+- `sql-params`: SQL report dynamic parameter value overrides. First read `analysis report get`; saved SQL params are exposed as AI-facing `definition.params`. Every name must exist in every target SQL report because one batch shares the override. Send only override values for existing parameter names: `[{"name":"platform","value":"ios"}]`, `[{"name":"server_id","operator":"contains","value":"s1"}]`, `[{"name":"level","operator":"eq","values":["42"]}]`, `[{"name":"amount","operator":"between","values":["10","20"]}]`, `[{"name":"part_date","start_time":"2026-07-01 00:00:00","end_time":"2026-07-09 23:59:59"}]`, or `[{"name":"part_date","recent_day":"1-7"}]`. Time fields require a saved `part_date` or time parameter. Operators `eq`/`in`, `neq`/`not_in`, and `between` use `values`; comparison/like/contains operators use single `value`. Do not send definition fields.
+
+A homogeneous SQL request that includes `filters`, `group_by`, `start_time`, `end_time`, or `time_granularity` fails with `INVALID_OVERRIDE_FOR_MODEL`. A homogeneous non-SQL request with `sql_params` also fails. Mixed-model batches are best-effort: data still returns and `meta.warnings[]` uses `OVERRIDE_IGNORED_FOR_MODEL`, `model_type`, `report_ids`, and `ignored_fields` to identify fields that did not apply. Do not discard these warnings.
+
+For a newly created or updated dynamic SQL report, omit `--sql-params` to execute the saved default first. After that succeeds, then make one second call with `--sql-params` to change only the requested value. This separates a broken saved default from a broken override and avoids repeating the same query.
+
+Output is the gateway envelope. `data` contains bounded inline report result items plus `query_context_id` and `sources[].drilldown` when the returned preview exposes follow-up actions. Each source is evaluated independently; SQL and other unsupported models have no actions.
+
+An empty batch or report result with no rows is a successful query: it means the requested time range has no data. The command fails only when every returned report entry contains an explicit execution error. Mixed batches keep successful items and return `meta.partial`, counts, and per-report `meta.failures` for partial-result handling.
+
+Read [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md). Select only returned row/column/metric options and call only the advertised event, entity, or result-cluster action. Do not pass raw QP.

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

@@ -0,0 +1,17 @@
+# analysis report delete
+
+Use when the user explicitly wants to delete one or more saved reports.
+
+Do not use without first confirming the target report IDs through `report list` or user-provided exact IDs.
+
+Command:
+
+```bash
+ae-cli analysis report delete --project-id <project_id> --report-ids '[1001,1002]' --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
+ae-cli analysis report delete --project-id <project_id> --report-ids '[1001,1002]' --yes
+```
+
+Input sends `project_id` and `report_ids`. Use an array even for one report.
+
+Output is the gateway envelope. `data` contains deleted `report_ids` and `deleted_count`.

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

@@ -0,0 +1,23 @@
+# analysis report get
+
+Use when the user needs one saved report definition as AI QP without executing the report.
+
+Do not use as a workaround after a builder-supported ad-hoc QP builder fails. For builder failure, stop and handle the structured error or ask for clarification.
+
+Command:
+
+```bash
+ae-cli analysis report get --project-id <project_id> --report-id <report_id>
+```
+
+Input sends `project_id` and `report_id`.
+
+Output is the gateway envelope. `data` contains `version`, `model_type`, `definition`, report metadata, and dashboard membership in snake_case. Use `data.version` as `--report-version` when updating the same report. Raw frontend `events`, `event_view`, `visual_view`, and raw QP are not returned.
+
+For a saved non-SQL report with a time granularity, `data.definition` returns the agent-facing `time_particle_size` spelling, such as `day`, `hour`, or `total`; internal `T0` through `T9` codes must never leak. If `time_particle_size` is absent, the saved definition has no readable granularity. Do not infer a granularity from the number of result rows; execute the saved report as-is or use an explicit ad-hoc definition when the user requires a specific granularity.
+
+This read is mandatory before applying report-data overrides. Branch on `data.model_type`:
+
+- `sql`: only `--sql-params` is valid. Every override name must already exist in `data.definition.params`; time values may be overridden only through a saved `part_date` or time parameter.
+- non-SQL analysis models: use `--filters`, `--group-by`, `--start-time`, `--end-time`, or `--time-granularity`; do not send `--sql-params`.
+- `tag`: report-data executes the saved tag definition. For a different tag view, use `analysis history-tag-data run/export`.

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

@@ -0,0 +1,17 @@
+# analysis report list
+
+Use when the user needs to find reports they can access in a project, with optional keyword search, semantic model filtering, field projection, and inline pagination.
+
+Do not use for report data execution or report definition writes. Use `report-data run/export` for data and `report create/update` for writes.
+
+Command:
+
+```bash
+ae-cli analysis report list --project-id <project_id> [--query <keyword>] [--model-types '["event","sql","tag","revenue"]'] [--fields '["report_id","report_name","report_desc","report_model","version"]'] [--limit 50] [--offset 0]
+```
+
+Input sends `project_id`, optional `query`, `model_types`, `fields`, `limit`, and `offset` as snake_case gateway input. `limit` defaults to 50 and must be 1..200; out-of-range values are rejected rather than silently clamped.
+
+Output is the gateway envelope. `data` contains report summaries, `total`, effective `limit`, `offset`, `has_more`, and nullable `next_offset`. When `has_more` is true, use exactly `next_offset` for the next call; stop when it is false. Include `version` in `--fields` when the next step is `analysis report update`.
+
+When locating one report, narrow with `--query` or `--model-types` before paging and stop when the required report is found; do not enumerate every report page when the server-side filters can identify the target.

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

@@ -0,0 +1,15 @@
+# analysis report list-export
+
+Use when the user needs to export the full accessible report catalog or a larger catalog than inline pagination should return.
+
+Do not use for report data values. Use `report-data export` when the output should be report result data, not catalog metadata.
+
+Command:
+
+```bash
+ae-cli analysis report list-export --project-id <project_id> [--query <keyword>] [--model-types '["event","sql","tag","revenue"]'] [--fields '["report_id","report_name"]'] [--artifact-format jsonl] [--request-id cli_0123456789abcdef0123456789abcdef] [--timeout-seconds 21600]
+```
+
+Input sends `project_id`, optional `query`, semantic `model_types`, `fields`, lifecycle `request_id`, artifact `format`, and `timeout_seconds`. ae-cli generates and announces `request_id` before dispatch when it is omitted.
+
+Output is the gateway envelope. `data` contains an async artifact descriptor including `run_id`, `artifact_id`, status, and expiration fields. Inspect and download through the dedicated CLI commands using those opaque IDs.

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

@@ -0,0 +1,22 @@
+# analysis report update
+
+Use when the user explicitly wants to update saved report metadata or replace its AI QP definition.
+
+Do not use raw QP, `qp`, `report_model`, or `analysis_query`. When changing the definition, pass `model_type` and AI QP `definition` together.
+
+Read [`ai_models.md`](ai_models.md) for the single AI-facing model registry. Report update supports the 12 analysis models plus `tag` for saved tag report data.
+
+Command:
+
+```bash
+ae-cli analysis report update --project-id <project_id> --report-id <report_id> --report-version <version> --report-name "New name"
+ae-cli analysis report update --project-id <project_id> --report-id <report_id> --report-version <version> --model-type event --definition '{...}'
+```
+
+Input sends `project_id`, `report_id`, `version` from CLI `--report-version`, and at least one of `report_name`, `report_desc`, or `definition`. Read `version` from `analysis report get` before updating. `model_type` is required when `definition` is provided.
+
+Output is the gateway envelope. `data` contains update status, `report_id`, and the normalized AI QP definition when a definition was updated.
+
+For the shortest safe update, read the current `version` exactly once with `analysis report get` immediately before the write; do not reuse a version from an older list or conversation turn. If a SQL dynamic parameter definition changed, query the saved default before applying an override so default persistence and override behavior are verified separately.
+
+After a successful update, call `analysis-meta asset url-get` with the updated `report_id` and output its `markdown_link`.

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

@@ -0,0 +1,15 @@
+# analysis report-version rollback
+
+Use when the user explicitly wants to rollback one report to a previous history version.
+
+Do not use without first identifying the target version from `report-change-log list` or an exact user-provided version.
+
+Command:
+
+```bash
+ae-cli analysis report-version rollback --project-id <project_id> --report-id <report_id> --target-version <version>
+```
+
+Input sends `project_id`, `report_id`, and target `version` from CLI `--target-version`.
+
+Output is the gateway envelope. `data` contains `report_id`, `rolled_back`, `target_version`, and `previous_version`.

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

@@ -0,0 +1,27 @@
+# analysis-governance rule create
+
+Use when the user needs to create an asset governance rule through the capability gateway.
+
+Do not use it when a matching saved rule already exists; list rules first and use `rule-update` for an existing `rule_id`.
+
+Command:
+
+```bash
+ae-cli analysis-governance rule create --project-id <project_id> --payload '{}'
+ae-cli analysis-governance rule create --dry-run --project-id <project_id>
+```
+
+Capability id: analysis_meta.asset_rule.create.
+
+Input sends project_id, payload, rule_name, comment, rule. Payload keys must follow the common-service snake_case input schema; do not send camelCase aliases.
+
+Output `data.rule_id` is the created governance rule identity. Preserve it for later update/delete operations.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| --project-id | Yes | Numeric project ID. |
+| --rule-name | No | Rule name; required unless provided inside payload. |
+| --comment | No | Rule comment. |
+| --rule | No | Governance Filter JSON; 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/rule_delete.md

@@ -0,0 +1,26 @@
+# analysis-governance rule delete
+
+Use when the user needs to delete an asset governance rule through the capability gateway.
+
+Do not use it to disable a rule or with a guessed ID; resolve the saved rule, dry-run the final deletion, and require explicit confirmation.
+
+Command:
+
+```bash
+ae-cli analysis-governance rule delete --project-id <project_id> --payload '{}' --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
+ae-cli analysis-governance rule delete --project-id <project_id> --payload '{}' --yes
+```
+
+Capability id: analysis_meta.asset_rule.delete.
+
+Input sends project_id, payload, rule_id. Payload keys must follow the common-service snake_case input schema; do not send camelCase aliases.
+
+Output `data.deleted` reports whether the identified rule was deleted; `false` must not be presented as a successful deletion.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| --project-id | Yes | Numeric project ID. |
+| --rule-id | No | Rule 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/rule_list.md

@@ -0,0 +1,24 @@
+# analysis-governance rule list
+
+Use when the user needs to list asset governance rules through the capability gateway.
+
+Do not use it to discover rule field syntax; use `rule-schema` for construction metadata and this command for existing rule IDs and definitions.
+
+Command:
+
+```bash
+ae-cli analysis-governance rule list --project-id <project_id>
+ae-cli analysis-governance rule list --dry-run --project-id <project_id>
+```
+
+Capability id: analysis_meta.asset_rule.list.
+
+Input sends project_id, payload. Payload keys must follow the common-service snake_case input schema; do not send camelCase aliases.
+
+Output `data` is the saved governance rule collection for the project. Resolve a real `rule_id` from this result before update or delete.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| --project-id | Yes | Numeric project ID. |
+| --payload | No | Optional snake_case object carrying the same fields. Use this for complex governance filters or backend-shaped payloads. |