@thinkingai/ae-cli 6.1.11 → 6.1.13

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

@@ -6,12 +6,19 @@ Typical closed loop: find the dashboard -> inspect its reports -> resolve exact
 
 Routing: read [`analysis_data_retrieval.md`](analysis_data_retrieval.md) before choosing this `run` command instead of `dashboard-report-data export`.
 
-Do not use this command for full, unknown-size, larger than 1000-row, or long-running dashboard report data; use `dashboard-report-data export`.
+Do not use this command for full, unknown-size, larger than the current runtime synchronous maximum, or long-running dashboard report data; use `dashboard-report-data export`.
+
+The dashboard surface also applies its configured response payload row/character
+caps after each model query. When that payload cap is smaller than the model
+boundary, returned rows are trimmed to the payload cap and `has_more=true` is
+based on that observed trim. This is a real dashboard-response truncation, not
+a boundary guess. Direct `report-data run` does not apply the dashboard payload
+cap.
 
 Command:
 
 ```bash
-ae-cli analysis dashboard-report-data run --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--cluster-query-scope GLOBAL|SLAVE] [--slave-cluster-id <id>] [--limit 100] [--timeout-seconds 180]
+ae-cli analysis dashboard-report-data run --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--cluster-query-scope GLOBAL|SLAVE] [--slave-cluster-id <id>] [--preview-rows 100] [--timeout-seconds 180]
 ```
 
 Cluster routing is optional. Omit it to follow the dashboard's saved physical-cluster configuration; this differs from report/ad-hoc current-self default. `GLOBAL` explicitly aggregates and `SLAVE` requires one ID returned by `analysis query-cluster list`. SQL dashboard reports reject effective `GLOBAL` and are reported as unsupported rather than silently queried elsewhere.
@@ -24,8 +31,8 @@ Cluster routing is optional. Omit it to follow the dashboard's saved physical-cl
 
 Dashboard `filters`, `start_time`, and `end_time` do not apply to SQL reports. The query still succeeds and returns those SQL report results. Inspect `data.warnings[]`; `OVERRIDE_IGNORED_FOR_MODEL` contains the affected SQL `report_ids` and `ignored_fields`. To change SQL conditions, query the SQL report directly with `analysis report-data run` and saved `definition.params` through `--sql-params`.
 
-Output is the gateway envelope. Verify `data.actual_cluster_query_scope`, optional `data.actual_slave_cluster_id`, and `data.cluster_query_scope_source`; `DASHBOARD_CONFIGURATION` means the caller omitted an explicit scope. `data` also contains bounded inline report data, warnings, `query_context_id`, and per-report drilldown options.
+Output is the gateway envelope. Verify `data.actual_cluster_query_scope`, optional `data.actual_slave_cluster_id`, and `data.cluster_query_scope_source`; `DASHBOARD_CONFIGURATION` means the caller omitted an explicit scope. When at least one report exposes a follow-up action, `data` also contains `query_context_id` and compact per-report action summaries. Detailed coordinate options are available through `analysis query-context get`; a fully non-drillable dashboard result omits query context.
 
 An empty dashboard 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 dashboard batches keep successful data and return `meta.partial`, counts, and per-report `meta.failures`.
 
-Read [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md). Pass the selected report source and merge only its returned coordinate fragments for the advertised action. Do not pass raw QP.
+Read [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md). Fetch the selected report source with `analysis query-context get` and merge only its returned coordinate fragments for the advertised action. Do not pass raw QP.

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

@@ -7,18 +7,20 @@ Do not use it for one version's full definition or table row history; use `datat
 Command:
 
 ```bash
-ae-cli analysis-meta datatable version-list --project-id <project_id> --datatable-id <datatable_id>
+ae-cli analysis-meta datatable version-list --project-id <project_id> --datatable-id <datatable_id> --limit 50 --offset 0
 ae-cli analysis-meta datatable version-list --dry-run
 ```
 
 Capability id: `metadata.data_table_version.list`.
 
-Input sends `project_id`, `datatable_id`.
+Input sends `project_id`, `datatable_id`, `limit`, and `offset`.
 
-Output `data.versions[]` contains historical metadata versions for the data table.
+Output always uses the directory envelope: `data.items[]`, `total`, `limit`, `offset`, `has_more`, and `next_offset`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--datatable-id` | Yes | Data table ID. |
+| `--limit` / `-l` | No | Page size. Default: 50, maximum: 200. |
+| `--offset` / `-o` | No | Zero-based page offset. Default: 0. |

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

@@ -13,11 +13,11 @@ ae-cli analysis drilldown-entities run \
   [--source '{"report_id":1001}'] \
   --coordinate '<merged returned row/column/metric coordinate>' \
   [--properties '[{...}]'] \
-  [--limit 100] \
+  [--preview-rows 100] \
   [--timeout-seconds 120]
 ```
 
-`--project-id` must be the project used by the synchronous preview and must match the stored query context. The context, source, and coordinate must all come from that same preview. Select a visible row from `row_options`, a drillable column from `column_options`, and the relevant metric option; shallow-merge their coordinate fragments. Never send `row_index`, `column_index`, `values`, `label`, `target_id`, raw QP, or a coordinate derived from an export file.
+`--project-id` must be the project used by the synchronous preview and must match the stored query context. The context, source, and coordinate must all come from that same preview. First call `analysis query-context get`; select a visible row from its `row_options`, a drillable column from `column_options`, and the relevant metric option, then shallow-merge their coordinate fragments. Never send `row_index`, `column_index`, `values`, `label`, `target_id`, raw QP, or a coordinate derived from an export file.
 
 Property support depends on the returned subject:
 
@@ -26,9 +26,9 @@ Property support depends on the returned subject:
 
 ## Output and next intent
 
-The response contains `subject`, `items`, `total`, `returned_rows`, and `truncated`.
+The response contains `subject`, `items`, exact `total` when available, `returned_rows`, and `has_more`.
 
 - `subject.type=user`: items include canonical `user_id`; `attributes` always includes `#user_id`, `#account_id`, and `#distinct_id`, followed by requested user properties. `#user_id` is an internal association key that customers normally do not care about. In user-facing tables or summaries, show account ID and visitor ID by default and keep `#user_id` only for machine linkage or explicit troubleshooting. If `drilldown_context_id` and the user-event follow-up are present, the Agent may ask for one returned user's event sequence with `analysis drilldown-user-events run|export`.
 - `subject.type=entity`: items contain `entity_value`; do not call user-event commands because non-user entities have no event sequence.
-- When `truncated=true` or complete membership is requested, repeat the same context/source/coordinate with `analysis drilldown-entities export`. Do not page this command.
+- When `has_more=true` or complete membership is requested, repeat the same context/source/coordinate with `analysis drilldown-entities export`. Do not page this command.
 - Creating a result cluster is a sibling action from the original analysis cell, not from an entity row. Use the original `query_context_id`, source, and coordinate with `analysis query create-result-cluster` only if that action was advertised.

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

@@ -13,7 +13,7 @@ ae-cli analysis drilldown-events run \
   [--source '{"report_id":1001}'] \
   --coordinate '{"group_values":["Beijing"],"date":"2026-07-16","metric_index":0}' \
   [--properties '[{...}]'] \
-  [--limit 100] \
+  [--preview-rows 100] \
   [--timeout-seconds 120]
 ```
 
@@ -21,4 +21,4 @@ ae-cli analysis drilldown-events run \
 
 `--properties` is an optional exact event-property projection. Omit it for default columns; string arrays such as `["#event_time"]` are invalid. Each item uses the backend field names `columnName` and `tableType`, for example `[{"columnName":"<event_property_name>","tableType":"event"}]`. `tableType` uses the documented name `event`, not a numeric enum code. Required system event columns remain present, but unrelated event properties must not be returned.
 
-The response contains at most `limit` event rows from that selected preview cell. `total` is the exact number of matching events, `returned_rows` is the number included in this response, and `truncated=true` means more matching events exist. This command has no paging offset. When complete event detail is required, call `analysis drilldown-events export` once with the same returned context/source/coordinate; that sibling capability uses the backend full-download stream and does not page or enlarge the synchronous selection boundary.
+The response contains at most `preview_rows` event rows from that selected preview cell. `total` is the exact number of matching events, `returned_rows` is the number included in this response, and `has_more=true` means more matching events exist. This command has no paging offset. When complete event detail is required, call `analysis drilldown-events export` once with the same returned context/source/coordinate; that sibling capability uses the backend full-download stream and does not page or enlarge the synchronous selection boundary.

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

@@ -19,7 +19,7 @@ ae-cli analysis drilldown-user-events export \
 
 The nested backend keys are exactly `columnName` and `tableType`, and the table type is the named value `event`. String-name arrays, numeric enum codes, and snake_case rewrites are invalid. With an explicit projection, the artifact retains `#user_id`, account ID, visitor ID, event name, and event time and appends exactly the requested event properties. `#user_id` is internal; Agents should normally present account ID and visitor ID to customers.
 
-Use the exact `drilldown_context_id` and canonical `user_id` returned by a user-subject `analysis drilldown-entities run`. Do not use a custom entity, an entity export artifact, or a guessed identity. Export does not accept `--limit`, `--offset`, `--page-num`, or `--page-size`; Common builds the same authorized event-sequence query without the synchronous 1000-row preview cap and streams one `csv.gz` artifact. The platform full-download ceiling (`model_full_download_limit`) still applies.
+Use the exact `drilldown_context_id` and canonical `user_id` returned by a user-subject `analysis drilldown-entities run`. Do not use a custom entity, an entity export artifact, or a guessed identity. Export does not accept `--limit`, `--offset`, `--page-num`, or `--page-size`; Common builds the same authorized event-sequence query without the synchronous preview boundary and streams one `csv.gz` artifact. The platform full-download ceiling (`model_full_download_limit`) still applies.
 
 For a `scope=total` source coordinate, there is no single selected date. Common
 preserves the machine date coordinates returned by the source query together

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

@@ -14,7 +14,7 @@ ae-cli analysis drilldown-user-events run \
   --drilldown-context-id <drilldown_context_id> \
   --user-id <user_id> \
   [--sort-order desc] \
-  [--limit 100] \
+  [--preview-rows 100] \
   [--timeout-seconds 120]
 ```
 
@@ -39,4 +39,4 @@ Do not call this command merely because an entity row looks like a user. The exp
 
 ## Output
 
-The response contains at most `limit` event rows. When `truncated=true`, use `analysis drilldown-user-events export`; do not attempt to fetch another page.
+The response contains at most `preview_rows` event rows. When `has_more=true`, use `analysis drilldown-user-events export`; do not attempt to fetch another page.

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

@@ -10,7 +10,7 @@ Use this command for the first small entity detail preview that fits inline. It
 ae-cli analysis entity-detail run \
   --project-id <project_id> \
   --definition '{"entity":"user","cohort":{"relation":"and","items":[{"field":{"name":"level","type":"user_property"},"operator":"gte","values":[1]}]},"properties":[{"name":"country","type":"user_property"}],"sort":[{"field":"#user_id","order":"asc"}]}' \
-  --limit 100
+  --preview-rows 100
 ```
 
 Input:
@@ -19,7 +19,7 @@ Input:
 - `--request-id` optional `cli_<32 lowercase hex>` lifecycle ID.
 - `--use-cache` optional boolean.
 - `--zone-offset` optional number.
-- `--limit` first inline preview rows, default 100, max 1000.
+- `--preview-rows` bounds returned business rows. Omit it to use the current cluster synchronous limit; explicit values are checked against that runtime maximum. Agents should normally pass 100.
 - `--timeout-seconds` sync timeout, default 120, max 180.
 
 `entity` may be `"user"` for the default user entity or `{ "id": 123 }` in multi-entity projects.
@@ -50,8 +50,8 @@ Supported `cohort.items[].field.type` values are `user_property`, `tag`, and `cl
 
 Do not put raw QP at the capability top level. Use `properties` items as strings or `{ "name": "...", "type": "user_property" }`, not `columnName/tableType`.
 
-Do not use this command for full, unknown-size, or later-page detail retrieval. Use `analysis entity-detail export` and check its artifact metadata for `truncated`.
+Do not use this command for full, unknown-size, or later-page detail retrieval. Use `analysis entity-detail export` and inspect its artifact metadata.
 
 Output:
 
-Returns JSON with `items`, `total`, `limit`, `returned_rows`, `truncated`, `column_meta`, and `request_id`. `truncated=true` means the preview hit its row cap or the backend reported more rows; use `analysis entity-detail export` instead of trying to page or claiming completeness.
+Returns JSON with `items`, exact `total` when available, `returned_rows`, `has_more`, `column_meta`, and `request_id`. `has_more=true` means more rows exist; use `analysis entity-detail export` instead of trying to page or claiming completeness.

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

@@ -9,7 +9,7 @@ ae-cli analysis entity id-import-options --project-id <project_id> --entity-id <
 If the entity ID is not already known, discover it first instead of guessing:
 
 ```bash
-ae-cli project entity list --project-id <project_id> --fields '["entityId","entityName","columnName","entityType"]'
+ae-cli project entity list --project-id <project_id> --fields '["entity_id","entity_name","column_name","select_type"]'
 ```
 
 - `match_mode=user_property`: `--association-property` is required and must be copied from `association_properties`; `#user_id` is forbidden.

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

@@ -10,7 +10,7 @@ Use this command for the first small event detail preview that fits inline. It i
 ae-cli analysis event-detail run \
   --project-id <project_id> \
   --definition '{"event":"login","time_range":{"mode":"absolute","start_time":"2026-07-01 00:00:00","end_time":"2026-07-01 23:59:59"},"properties":["#event_time",{"name":"country","type":"user_property"}],"sort":[{"field":"#event_time","order":"desc"}]}' \
-  --limit 100
+  --preview-rows 100
 ```
 
 Input:
@@ -19,7 +19,7 @@ Input:
 - `--request-id` optional `cli_<32 lowercase hex>` lifecycle ID.
 - `--use-cache` optional boolean.
 - `--zone-offset` optional number, for example `8` for UTC+8.
-- `--limit` first inline preview rows, default 100, max 1000.
+- `--preview-rows` bounds returned business rows. Omit it to use the current cluster synchronous limit; explicit values are checked against that runtime maximum. Agents should normally pass 100.
 - `--timeout-seconds` sync timeout, default 120, max 180.
 
 Definition shape:
@@ -53,8 +53,8 @@ Do not pass raw QP, `eventView`, `taFilters`, `columnName`, or `tableType`.
 
 When `definition.properties` is present, it is an exact projection: required system event columns remain, requested properties are appended, and unrelated properties must not be returned.
 
-Do not use this command for full, unknown-size, or later-page detail retrieval. Use `analysis event-detail export` and check its artifact metadata for `truncated`.
+Do not use this command for full, unknown-size, or later-page detail retrieval. Use `analysis event-detail export` and inspect its artifact metadata.
 
 Output:
 
-Returns JSON with `items`, `total`, `limit`, `returned_rows`, `truncated`, `column_meta`, and `request_id`. `truncated=true` means the preview hit its row cap or the backend reported more rows; use `analysis event-detail export` instead of trying to page or claiming completeness.
+Returns JSON with `items`, exact `total` when available, `returned_rows`, `has_more`, `column_meta`, and `request_id`. `has_more=true` means more rows exist; use `analysis event-detail export` instead of trying to page or claiming completeness.

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

@@ -0,0 +1,21 @@
+# analysis-meta event export
+
+Use when the user explicitly needs every accessible event, optionally filtered or projected, in one local file.
+
+Do not use it for paginated discovery, raw tracked events, or analysis result data.
+
+Command:
+
+```bash
+ae-cli analysis-meta event export --project-id <project_id> --output <temporary_path>/events.json
+ae-cli analysis-meta event export --project-id <project_id> --queries '["login","sign in"]' --fields '["event_name","event_desc"]' --output <temporary_path>/events.json
+ae-cli analysis-meta event export --dry-run
+```
+
+Capability id: `metadata.event.export`.
+
+Input: the gateway receives `project_id` plus optional `queries`, `fields`, and `authenticated_only`; `output` is local-only.
+
+Output: a successful response must prove `complete=true` and `total` equal to the row count before the CLI atomically publishes a private-mode `.json` array.
+
+Do not use pagination or repeated `list` calls to recreate this behavior. Search the output file locally and keep full rows out of model context.

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

@@ -8,24 +8,25 @@ Command:
 
 ```bash
 ae-cli analysis-meta event list --project-id <project_id>
-ae-cli analysis-meta event list --project-id <project_id> --query login --fields '["event_name","event_desc","authentication_status"]' --limit 20 --offset 0 --authenticated-only
+ae-cli analysis-meta event list --project-id <project_id> --queries '["login","sign in"]' --fields '["event_name","event_desc","authentication_status"]' --limit 50 --offset 0 --authenticated-only
 ae-cli analysis-meta event list --dry-run
 ```
 
 Capability id: `metadata.event.list`.
 
-Input sends `project_id`, `query`, `fields`, `limit`, `offset`, and `authenticated_only`.
+Input sends `project_id`, `queries`, `fields`, `limit`, `offset`, and `authenticated_only`.
 
 Use snake_case projection fields: `event_id`, `event_name`, `event_desc`, `remark`, `event_tag`, `authentication_status`. Do not send legacy camelCase field names.
 
-Output `data.events[]` contains project super-event metadata records.
+Output always uses the directory envelope: `data.items[]`, `total`, `limit`, `offset`, `has_more`, and `next_offset`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--query` / `-q` | No | Optional keyword filter. Fuzzy match is applied to `event_name`, `event_desc`, and `remark`. |
+| `--queries` | No | JSON array of 1-20 keyword filters. A row is returned when any keyword matches `event_name`, `event_desc`, or `remark`. |
 | `--fields` / `-f` | No | Optional JSON array of snake_case fields to return. |
-| `--limit` / `-l` | No | Optional page size. When omitted, existing full-list behavior is preserved. Maximum: 50. |
-| `--offset` / `-o` | No | Optional zero-based page offset. |
+| `--limit` / `-l` | No | Page size. Default: 50, maximum: 200; values outside 1..200 are rejected. |
+| `--offset` / `-o` | No | Zero-based page offset. Default: 0; negative values are rejected. |
 | `--authenticated-only` | No | When true, return only authenticated events and include `authentication_status` when projected. |
+For a complete result, use `analysis-meta event export`; do not page repeatedly to synthesize an export.

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

@@ -7,17 +7,19 @@ Do not use it to validate or persist proposed rules; use `exchange rule-validate
 Command:
 
 ```bash
-ae-cli analysis-meta exchange rule-list --project-id <project_id>
+ae-cli analysis-meta exchange rule-list --project-id <project_id> --limit 50 --offset 0
 ae-cli analysis-meta exchange rule-list --dry-run
 ```
 
 Capability id: `metadata.exchange_rule.list`.
 
-Input sends `project_id`.
+Input sends `project_id`, `limit`, and `offset`.
 
-Output `data.rules[]` contains the project's current exchange rules.
+Output always uses the directory envelope: `data.items[]`, `total`, `limit`, `offset`, `has_more`, and `next_offset`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
+| `--limit` / `-l` | No | Page size. Default: 50, maximum: 200. |
+| `--offset` / `-o` | No | Zero-based page offset. Default: 0. |

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

@@ -1,13 +1,15 @@
 # analysis history-tag-data-drilldown export
 
-Export all users for one value/bucket returned by `history-tag-data run/export` as an async jsonl artifact.
+Stream the native full user download for one value/bucket returned by `history-tag-data run/export` as an async gzip artifact.
 
 Do not use it for an inline sample or for a group value that did not come from the upstream statistics response. Output is an async descriptor with `run_id` and `artifact_id`, not the user rows themselves.
 
-Flags: `--project-id`, `--tag-name`, `--snapshot-date`, `--group-col`, `--view` required. Optional: `--property-names`, `--fields`, `--query`, `--use-cache`, `--request-id`, `--artifact-format jsonl`, `--timeout-seconds`.
+Flags: `--project-id`, `--tag-name`, `--snapshot-date`, `--group-col`, `--view` required. Optional: `--property-names`, `--request-id`, `--artifact-format jsonl|csv`, `--timeout-seconds`. The default format is `jsonl`.
 
 Use the same `--view` that produced the statistic row. `--group-col` must be the exact statistic value or bucket label. Download the artifact only after `analysis run inspect` reports success.
 
+Common executes the native history-tag full-download SQL once and streams rows as `jsonl.gz` or `csv.gz`; it does not concatenate preview pages.
+
 ```bash
 ae-cli analysis history-tag-data-drilldown export --project-id <project_id> --tag-name user_level --snapshot-date 2026-07-01 --group-col VIP --view '{"recent_day":"0-31","time_particle_size":"T1","first_day_of_week":1,"interval_type":"default","array_group_type":"array_item_group"}' --artifact-format jsonl
 ae-cli analysis run inspect --run-id <run_id>

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

@@ -4,10 +4,10 @@ Run a bounded inline user drilldown for one value/bucket returned by `history-ta
 
 Do not use it for complete or unknown-size drilldown data. Output contains only the bounded inline user result; use export when truncation would change the answer.
 
-Flags: `--project-id`, `--tag-name`, `--snapshot-date`, `--group-col`, `--view` required. Optional: `--property-names`, `--fields`, `--query`, `--use-cache`, `--request-id`, `--limit`, `--timeout-seconds`.
+Flags: `--project-id`, `--tag-name`, `--snapshot-date`, `--group-col`, `--view` required. Optional: `--property-names`, `--fields`, `--query`, `--use-cache`, `--request-id`, `--preview-rows`, `--timeout-seconds`.
 
 Use the same `--view` that produced the statistic row. `--group-col` must be the exact statistic value or bucket label. Use export for full drilldown users; this command has no next-page contract.
 
 ```bash
-ae-cli analysis history-tag-data-drilldown run --project-id <project_id> --tag-name user_level --snapshot-date 2026-07-01 --group-col VIP --view '{"recent_day":"0-31","time_particle_size":"T1","first_day_of_week":1,"interval_type":"default","array_group_type":"array_item_group"}' --limit 100
+ae-cli analysis history-tag-data-drilldown run --project-id <project_id> --tag-name user_level --snapshot-date 2026-07-01 --group-col VIP --view '{"recent_day":"0-31","time_particle_size":"T1","first_day_of_week":1,"interval_type":"default","array_group_type":"array_item_group"}' --preview-rows 100
 ```

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

@@ -4,12 +4,12 @@ Run a bounded inline history tag statistics query. Read `analysis_data_retrieval
 
 Output is bounded history-tag statistics, not member rows. Use `history-tag-data-drilldown run/export` for users behind a returned value or bucket.
 
-Flags: `--project-id`, `--tag-name`, `--view` required. Optional: `--request-id`, `--limit`, `--timeout-seconds`.
+Flags: `--project-id`, `--tag-name`, `--view` required. Optional: `--request-id`, `--preview-rows`, `--timeout-seconds`.
 
 If you provide `--request-id`, use `cli_<32 lowercase hex>`. Omit it unless you need to correlate logs or cancel a known running query.
 
 `--view` is AI-facing history tag view JSON. It must include a history date range (`recent_day` or `start_time`/`end_time`) and `time_particle_size:"T1"`. Optional fields include `interval_type`, `property_range`, `time_particle`, `array_group_type`, and `column_splited_str`. Do not pass raw frontend wrapper DTOs.
 
 ```bash
-ae-cli analysis history-tag-data run --project-id <project_id> --tag-name user_level --view '{"recent_day":"0-31","time_particle_size":"T1","first_day_of_week":1,"interval_type":"default","array_group_type":"array_item_group"}' --limit 100
+ae-cli analysis history-tag-data run --project-id <project_id> --tag-name user_level --view '{"recent_day":"0-31","time_particle_size":"T1","first_day_of_week":1,"interval_type":"default","array_group_type":"array_item_group"}' --preview-rows 100
 ```

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

@@ -0,0 +1,21 @@
+# analysis-meta metric export
+
+Use when the user explicitly needs every accessible metric, optionally filtered or projected, in one local file.
+
+Do not use it to calculate metric values or for paginated discovery.
+
+Command:
+
+```bash
+ae-cli analysis-meta metric export --project-id <project_id> --output <temporary_path>/metrics.json
+ae-cli analysis-meta metric export --project-id <project_id> --queries '["pay","revenue"]' --fields '["metric_name","metric_desc"]' --output <temporary_path>/metrics.json
+ae-cli analysis-meta metric export --dry-run
+```
+
+Capability id: `metadata.metric.export`.
+
+Input: the gateway receives `project_id` plus optional `ignore_authentication`, `queries`, `fields`, and `authenticated_only`; `output` is local-only.
+
+Output: a successful response must prove `complete=true` and `total` equal to the row count before the CLI atomically publishes a private-mode `.json` array.
+
+Do not use pagination or repeated `list` calls to recreate this behavior. Search the output file locally and keep full rows out of model context.

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

@@ -9,29 +9,30 @@ Command:
 ```bash
 ae-cli analysis-meta metric list --project-id <project_id>
 ae-cli analysis-meta metric list --project-id <project_id> --ignore-authentication true
-ae-cli analysis-meta metric list --project-id <project_id> --query pay
-ae-cli analysis-meta metric list --project-id <project_id> --query pay --fields '["metric_name","authentication_status"]' --limit 10 --offset 0 --authenticated-only true
+ae-cli analysis-meta metric list --project-id <project_id> --queries '["pay","revenue"]'
+ae-cli analysis-meta metric list --project-id <project_id> --queries '["pay","revenue"]' --fields '["metric_name","authentication_status"]' --limit 50 --offset 0 --authenticated-only true
 ae-cli analysis-meta metric list --dry-run
 ```
 
 Capability id: `metadata.metric.list`.
 
-Input sends `project_id`, `ignore_authentication`, `query`, `fields`, `limit`, `offset`, and `authenticated_only`.
+Input sends `project_id`, `ignore_authentication`, `queries`, `fields`, `limit`, `offset`, and `authenticated_only`.
 
-Output `data.metrics[]` contains project metric summaries. When `limit` or `offset` is present, output also includes `total`, `limit`, `offset`, and `has_more`.
+Output always uses the directory envelope: `data.items[]`, `total`, `limit`, `offset`, `has_more`, and `next_offset`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--ignore-authentication` | No | Whether to skip asset authentication status decoration. |
-| `--query` | No | Optional keyword filter. Fuzzy match on `metric_name`, `metric_desc`, and `metric_remark`. |
+| `--queries` | No | JSON array of 1-20 keyword filters. A row is returned when any keyword matches `metric_name`, `metric_desc`, or `metric_remark`. |
 | `--fields` | No | Optional result field projection JSON array. Supported fields: `metric_id`, `metric_name`, `metric_desc`, `metric_remark`, `metric_mode`, `authentication_status`, `open_id`, `creator`, `creator_login_name`, `update_open_id`, `update_creator`, `update_login_name`, `create_time`, `update_time`. |
-| `--limit` | No | Optional page size. Default: 20 when pagination is used, maximum: 50. |
-| `--offset` | No | Optional zero-based result offset. Default: 0. |
+| `--limit` | No | Page size. Default: 50, maximum: 200; values outside 1..200 are rejected. |
+| `--offset` | No | Zero-based page offset. Default: 0; negative values are rejected. |
 | `--authenticated-only` | No | When true, return only authenticated metrics. |
 
 ## Decision Rules
 - Do not call this just to prepare normal ad-hoc analysis. Pass saved metric wording directly in `analysis adhoc run/export --definition`; the backend compiler resolves saved metric names internally.
 - Use `--fields` to keep discovery responses compact.
 - Use `analysis-meta metric get` after this command when a full metric definition is needed.
+- For a complete result, use `analysis-meta metric export`; do not page repeatedly to synthesize an export.

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

@@ -0,0 +1,21 @@
+# analysis-meta property export
+
+Use when the user explicitly needs every accessible event or user property, including flat dimension-table and complex child rows, in one local file.
+
+Do not use it for paginated discovery, property values, or analysis result data.
+
+Command:
+
+```bash
+ae-cli analysis-meta property export --project-id <project_id> --scope event --output <temporary_path>/properties.json
+ae-cli analysis-meta property export --project-id <project_id> --scope event --event-name purchase --queries '["amount"]' --fields '["prop_name","prop_desc"]' --output <temporary_path>/properties.json
+ae-cli analysis-meta property export --dry-run
+```
+
+Capability id: `metadata.property.export`.
+
+Input: the gateway receives `project_id` plus optional `table_type`, `scope`, `event_name`, `queries`, `fields`, and `authenticated_only`; `output` is local-only.
+
+Output: a successful response must prove `complete=true` and `total` equal to the row count before the CLI atomically publishes a private-mode `.json` array.
+
+Do not use pagination or repeated `list` calls to recreate this behavior. Search the output file locally and keep full rows out of model context.

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

@@ -1,6 +1,6 @@
 # analysis-meta property list
 
-Use when the user needs to browse or search event/user property metadata.
+Use when the user needs to browse or search event/user property metadata, including dimension-table and complex child properties.
 
 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.
 
@@ -8,16 +8,16 @@ Command:
 
 ```bash
 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 --project-id <project_id> --scope event --event-name purchase --queries '["demo","sample"]'
+ae-cli analysis-meta property list --project-id <project_id> --queries '["demo","sample"]' --fields '["prop_id","prop_name","prop_desc","prop_remark","select_type","table_type","authentication_status"]' --limit 50 --offset 0
 ae-cli analysis-meta property list --dry-run
 ```
 
 Capability id: `metadata.property.list`.
 
-Input sends `project_id` and optional `table_type`, `scope`, `event_name`, `query`, `fields`, `limit`, `offset`, `authenticated_only`.
+Input sends `project_id` and optional `table_type`, `scope`, `event_name`, `queries`, `fields`, `limit`, `offset`, and `authenticated_only`.
 
-Output `data.properties[]` contains property metadata. When `limit` or `offset` is provided, output also includes `total`, `limit`, `offset`, and `has_more`.
+Output always uses the directory envelope: `data.items[]`, `total`, `limit`, `offset`, `has_more`, and `next_offset`. Dimension-table and complex child properties are returned as independent flat rows, so keyword search, field projection, and pagination apply to them in the same way as top-level properties.
 
 ## Parameters
 | Parameter | Required | Description |
@@ -26,10 +26,10 @@ Output `data.properties[]` contains property metadata. When `limit` or `offset`
 | `--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. |
+| `--queries` | No | JSON array of 1-20 keyword filters. A row is returned when any keyword matches property name, description, or 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. |
+| `--limit` | No | Page size. Default: 50, maximum: 200; values outside 1..200 are rejected. |
+| `--offset` | No | Zero-based page offset. Default: 0; negative values are rejected. |
 | `--authenticated-only` | No | When true, return only authenticated properties. |
 
 ## Decision Rules
@@ -37,3 +37,4 @@ Output `data.properties[]` contains property metadata. When `limit` or `offset`
 - 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.
+- For a complete result, use `analysis-meta property export`; do not page repeatedly to synthesize an export.

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

@@ -0,0 +1,20 @@
+# analysis query-context get
+
+Read the full selectable coordinate options for one source from a bounded synchronous analysis preview.
+
+The primary `adhoc run`, `report-data run`, or `dashboard-report-data run` response intentionally returns only a compact `sources[]` summary. Call this command only when that response contains `query_context_id`, `query_context_options_capability_id=analysis.query.context_get`, and an advertised follow-up action.
+
+## Command
+
+```bash
+ae-cli analysis query-context get \
+  --project-id <project_id> \
+  --query-context-id <query_context_id> \
+  [--source '{"report_id":1001}']
+```
+
+`--project-id` must match the project stored by the context. For a context with multiple sources, copy exactly one `report_id` or `chart_id` selector from the compact primary response. Omit `--source` only when the context contains one source.
+
+The returned `source.drilldown` contains the complete `row_options`, `column_options`, and `metric_options` for the original synchronous preview. Select options and shallow-merge only their `coordinate` fragments as described in [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md). The command never reruns or expands the query and never makes export rows selectable.
+
+If the context is missing, expired, owned by another user, belongs to another project, or the caller no longer has source permission, the command fails. Do not reconstruct coordinates from display text.

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

@@ -22,7 +22,7 @@ ae-cli analysis query create-result-cluster \
 
 - `--project-id` must be the project used by the synchronous preview and must match the project stored by `query_context_id`.
 - `--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.
+- Call `analysis query-context get`, match the desired visible row and column in its `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, start with a lowercase letter, contain only lowercase letters, digits, and underscores, and be at most 24 characters. This legacy result-cluster path is stricter than ordinary cluster creation.
 - `--display-name`, when provided, must be at most 80 characters.

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

@@ -12,4 +12,4 @@ ae-cli analysis report-change-log list --project-id <project_id> --report-id <re
 
 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.
+Output is the gateway envelope. `data` contains change log summaries and `total`. Only items with `can_rollback=true` are valid rollback sources; pass that item's `target_version` to `report-version rollback --target-version`. Create and unpack records are not rollbackable. Raw report QP fields are not returned in the list.

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

@@ -9,14 +9,14 @@ Read [`ai_models.md`](ai_models.md) for the single AI-facing model registry. Rep
 Command:
 
 ```bash
-ae-cli analysis report create --project-id <project_id> --report-name "Demo" --model-type event --definition '{...}' [--report-desc "..."] [--dashboard-ids "[1001]"]
+ae-cli analysis report create --project-id <project_id> --report-name "Demo" --model-type event --definition '{...}' [--resolutions '<confirmed_resolution_json>'] [--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`.
+Input sends `project_id`, `report_name`, `model_type`, `definition`, optional user-confirmed `resolutions`, `report_desc`, `cache_seconds`, `query_duration_ms`, and `dashboard_ids`. `--resolutions` is not supported with `--model-type tag`.
 
 Output is the gateway envelope. `data` contains the created `report_id`, creation status, normalized `model_type`, AI QP `definition`, and optional resolution warnings.
 
-Report creation and its `--validate` / `--dry-run` paths use the same compiler contract. `AI_QP_COMPILE_FAILED` preserves `meta.compile_status`, full `meta.errors[]` (including `code`, `candidates`, and `suggestions`), `meta.resolved`, and `meta.warnings`. No report is created on this failure; select an exact returned candidate or ask the user before retrying.
+Report creation and its `--validate` / `--dry-run` paths use the same compiler contract. `AI_QP_COMPILE_FAILED` preserves the full structured error array. No report is created on this failure; follow [`../metadata_resolution.md`](../metadata_resolution.md), keep the definition unchanged, and pass `--resolutions` only after user confirmation.
 
 ## SQL dynamic parameter shortest path
 

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

@@ -6,7 +6,7 @@ Typical closed loop: discover a saved report -> verify its definition -> resolve
 
 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`.
+Do not use this command for full, unknown-size, larger than the current runtime synchronous maximum, 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.
 
@@ -22,19 +22,19 @@ 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
+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 --preview-rows 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
+ae-cli analysis report-data run --project-id <project_id> --report-ids '[2001]' --sql-params '[{"name":"platform","value":"ios"}]' --preview-rows 20
 
 # Explicit local-time mode (not UTC+99)
-ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]' --zone-offset 99 --limit 20
+ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]' --zone-offset 99 --preview-rows 20
 
 # One physical slave query cluster
-ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]' --cluster-query-scope SLAVE --slave-cluster-id jp --limit 20
+ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]' --cluster-query-scope SLAVE --slave-cluster-id jp --preview-rows 20
 ```
 
-Input also accepts optional `cluster_query_scope` and conditional `slave_cluster_id`. Omit both for current-self data. Use `GLOBAL` only for explicit cross-cluster aggregation; use `SLAVE` with exactly one ID returned by `analysis query-cluster list`. SQL reports reject `GLOBAL`. Control defaults: `--limit` default 100 / max 1000, `--timeout-seconds` default 120 / max 180.
+Input also accepts optional `cluster_query_scope` and conditional `slave_cluster_id`. Omit both for current-self data. Use `GLOBAL` only for explicit cross-cluster aggregation; use `SLAVE` with exactly one ID returned by `analysis query-cluster list`. SQL reports reject `GLOBAL`. Omit `--preview-rows` to use each report model's current cluster synchronous limit; explicit values must not exceed the runtime model limit. Agents should normally pass 100. `--timeout-seconds` defaults to 120 and has a maximum of 180.
 
 Timezone contract:
 
@@ -53,8 +53,8 @@ A homogeneous SQL request that includes `filters`, `group_by`, `start_time`, `en
 
 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[]`. Each source includes `effective_zone_offset`, the timezone value actually used for that query. When `zone_offset` is omitted, this is the resolved current-user timezone when available, otherwise the project default; when `zone_offset` is explicit, this is its resolved effective value. `sources[].drilldown` is present when the returned preview exposes follow-up actions. Each source is evaluated independently; SQL and other unsupported models have no actions.
+Output is the gateway envelope. When at least one report exposes a follow-up action, `data` contains bounded inline report result items plus `query_context_id` and compact `sources[]` summaries. Each source includes `effective_zone_offset`, the timezone value actually used for that query. When `zone_offset` is omitted, this is the resolved current-user timezone when available, otherwise the project default; when `zone_offset` is explicit, this is its resolved effective value. SQL-only and otherwise non-drillable results omit query context entirely. Use `analysis query-context get` to read the selected source's full coordinate options.
 
 `meta.actual_cluster_query_scope`, optional `meta.actual_slave_cluster_id`, and `meta.cluster_query_scope_source` describe the actual physical route. Verify them before comparing or drilling down. 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.
 
-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.
+Read [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md). Call `analysis query-context get`, select only its returned row/column/metric options, and call only the advertised event, entity, or result-cluster action. Do not pass raw QP.