@thinkingai/ae-cli 6.0.33 → 6.0.35

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

@@ -1,49 +0,0 @@
-# analysis +update_alert (Update Alert)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata queries**
-
-## Use Cases
-- Precondition helper: call `+get_alert_definition_schema` to get the structure before using this tool.
-- Update an existing alert. All fields in the definition will replace existing values. See get_alert_definition_schema for the parameter structure.
-- Update an existing alert.
-
-## Mandatory prerequisites (MUST)
-- Before constructing a new `--definition`, you must first read and follow:
-  - [`./get_alert_definition_schema.md`](./get_alert_definition_schema.md)
-- Do not submit the new `definition` until the documentation review and schema call are complete.
-
-## Prerequisite call chain (required for updating definition)
-1. Read `get_alert_definition_schema.md` to understand the return structure of `+get_alert_definition_schema`.
-2. Call `ae-cli analysis +get_alert_definition_schema` to get the schema.
-3. Build a new `definition` from the schema, then call `+update_alert`.
-
-## Command
-```bash
-ae-cli analysis +update_alert --project_id <project_id> --alert_id 1 --definition '{}'
-ae-cli analysis +update_alert --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--alert_id` / `-a` | Yes | Alert ID to update |
-| `--definition` | Yes | Alert definition JSON with updated fields. MUST call `+get_alert_definition_schema` first and strictly follow the returned structure. |
-
-## Decision Rules
-- `definition` cannot be written from experience alone: it must satisfy the alert schema structure constraints.
-- On the first run, start with only the required parameters (`--project_id`, `--alert_id`, `--definition`) and add optional parameters after confirming the path works.
-- Wrap JSON parameters in single quotes (for example `--definition '{}'`) to avoid shell escaping issues.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`, `--alert_id`, `--definition`).
-- If `Invalid JSON` appears, first check the schema required fields and enumeration values, then add fields incrementally.
-- If the result after writing does not match expectations, immediately read back the corresponding list/get interface to compare before and after.
-
-## Recommended chaining
-- +get_alert_definition_schema -> +update_alert
-- +list_alerts -> +get_alert -> +update_alert

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

@@ -1,40 +0,0 @@
-# analysis_meta +update_project_mark_time (Update Project Date Marker)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Update an existing project date marker. Returns the updated marker ID, timestamp, content, and visibility status.
-- Update an existing project date marker.
-- Do not use it to create a marker or change analysis data; use `+create_project_mark_time` for a new marker.
-
-## Command
-```bash
-ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id <project_id> --marked_at '2026-04-09 10:00' --content demo
-ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id <project_id> --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
-ae-cli analysis_meta +update_project_mark_time --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--mark_time_id` | Yes | Marker ID |
-| `--project_id` / `-p` | Yes | Project ID |
-| `--marked_at` | Yes | Marker timestamp. Format: yyyy-MM-dd HH:mm |
-| `--zone_offset` | No | Marker time zone offset |
-| `--content` | Yes | Marker content |
-| `--is_visible` | No | Whether the marker is visible. Default: 1 |
-
-## Decision Rules
-- The smallest valid request also includes required `--content`; use `--dry-run` with `--mark_time_id`, `--project_id`, `--marked_at`, and `--content` before executing.
-- For date/time ranges, first validate with a short range, then expand the range step by step.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps After Failure
-- If required parameters are missing, supply `--mark_time_id`, `--project_id`, `--marked_at`, and `--content` before retrying.
-- If the result after writing is not as expected, immediately read back the corresponding list/get interface for a before-and-after comparison.
-
-## Recommended Chaining
-- +list_project_mark_times -> +update_project_mark_time

package/skills/ae-analysis-global/references/list_query_clusters.md

@@ -1,68 +0,0 @@
-# analysis +list_query_clusters (Query Cluster Options)
-
-> **Prerequisite:** Use this reference only after `ae-analysis-global` confirms local multi-cluster mode is enabled. This command is added by the global overlay, not by the base `ae-analysis` skill.
-
-Domain: **Multi-Cluster Query Routing**
-
-## Use Cases
-
-- List the query cluster options accessible to the current account in the project.
-- Answer user questions such as "cluster info", "available query clusters", or "current cluster". Localized examples include "集群信息" and "有哪些集群".
-- Decide whether a later report/dashboard/ad-hoc query should use the current self cluster, global aggregated data, or one specific slave cluster.
-- Resolve country, region, game server, service shard, site, market, or deployment area wording to an accessible slave cluster before passing `cluster_query_scope=SLAVE`.
-
-This command is not for audience/user segment clusters. For cohort, audience, or segment assets, use `analysis user-cluster list`.
-
-## Commands
-
-```bash
-ae-cli analysis +list_query_clusters --project_id <project_id>
-ae-cli analysis +list_query_clusters --dry-run
-```
-
-## Parameters
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID used to resolve the current account's cluster query permissions. |
-
-## Output Shape
-
-The result data follows the server DTO used by `list_query_clusters`:
-
-| Field | Description |
-|---|---|
-| `globalQueryEnabled` | Whether global query is enabled by server config. |
-| `currentCluster` | The current self query cluster. Fields: `clusterId`, `clusterName`, `clusterDesc`. |
-| `slaveClusters` | Accessible slave query clusters for this account and project. Each item has `clusterId`, `clusterName`, `clusterDesc`. |
-| `permissions` | Permission summary for choosing query scope. |
-| `permissions.canQueryCurrent` | Whether the user can query the current self cluster. Usually true. |
-| `permissions.canQueryGlobal` | Whether `cluster_query_scope=GLOBAL` is allowed. |
-| `permissions.canQueryAllSlaveClusters` | Whether any enabled slave cluster may be queried. |
-| `permissions.allowedSlaveClusterIds` | Slave cluster IDs this account may use. |
-| `permissions.allowedClusterQueryParams` | Human-readable allowed query parameter combinations, e.g. `omit clusterQueryScope`, `clusterQueryScope=GLOBAL`, or `clusterQueryScope=SLAVE, slaveClusterId in [...]`. |
-
-## Decision Rules
-
-- For query-cluster inventory or cluster-info questions, call this command and answer with "query clusters", not "audience clusters".
-- Default query behavior is to omit `cluster_query_scope`, which queries the current self cluster or follows the tool-specific default.
-- Pass `--cluster_query_scope GLOBAL` only when the user clearly asks for global, all clusters, all servers, cross-cluster aggregation, or equivalent aggregate wording, and `permissions.canQueryGlobal=true`.
-- Pass `--cluster_query_scope SLAVE --slave_cluster_id <clusterId>` only after this command confirms a requested country, region, server, site, market, or deployment maps to an accessible `slaveClusters[]` item.
-- Match slave intent only against `slaveClusters[].clusterId`, `slaveClusters[].clusterName`, and `slaveClusters[].clusterDesc`.
-- If the requested scope is not allowed, do not guess forbidden parameters. Explain `permissions.allowedClusterQueryParams`.
-- Unified ad-hoc gateway commands (`analysis adhoc run/export`) do not expose `cluster_query_scope`; if a global/slave ad-hoc query is requested, report that the gateway contract does not support it yet instead of using removed ad-hoc commands or hidden flags.
-- For SQL model analysis, never pass `cluster_query_scope`; SQL model analysis only supports the current self cluster in the current gateway contract.
-
-## Recommended Chains
-
-- Cluster inventory / cluster info -> `analysis +list_query_clusters`
-- Query DAU for Japan server -> `analysis +list_query_clusters` -> match JP/Japan slave cluster -> use only commands that explicitly expose cluster routing; the current report/dashboard/ad-hoc gateway data commands do not.
-- Query all-cluster aggregated DAU -> `analysis +list_query_clusters` -> if `permissions.canQueryGlobal=true`, use only commands that explicitly expose cluster routing; otherwise stop and report the capability gap.
-- View audience cohorts or user segments -> `analysis user-cluster list` instead
-
-## Response Wording
-
-- Use "current query cluster" for `currentCluster`.
-- Use "accessible slave query clusters" for `slaveClusters`.
-- Use "allowed query-scope parameters" for `permissions.allowedClusterQueryParams`.
-- Do not call `analysis user-cluster list` results query clusters; those are audience clusters or user segments.

package/skills/ae-engage/references/config-channel-detail.md

@@ -1,31 +0,0 @@
-# ae-engage +config_channel_detail
-
-
-Query config channel details.
-
-Mapped command: `ae-cli engage +config_channel_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | config channel ID |
-
-## Common enums in the response
-
-### `channelType`
-
-- `0`: `WEBHOOK`
-- `1`: `CLIENT`
-
-### `channelStatus`
-
-- `1`: enabled
-- `2`: disabled
-
-## Examples
-
-```bash
-ae-cli engage +config_channel_detail --project_id 1 --channel_id <channel_id>
-```

package/skills/ae-engage/references/config-channel-list.md

@@ -1,26 +0,0 @@
-# ae-engage +config_channel_list
-
-
-Query the config channel list.
-
-Mapped command: `ae-cli engage +config_channel_list`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_type` | number | No | config channel type |
-
-## Enum Notes
-
-### `--channel_type`
-
-- `0`: `WEBHOOK`
-- `1`: `CLIENT`
-
-## Examples
-
-```bash
-ae-cli engage +config_channel_list --project_id 1
-```

package/skills/ae-engage/references/config-item-detail.md

@@ -1,29 +0,0 @@
-# ae-engage +config_item_detail
-
-
-Query config item details.
-
-Mapped command: `ae-cli engage +config_item_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-
-## Common enums in the response
-
-### `channelType`
-
-- `1`: `WEBHOOK`
-- `2`: `APP_PUSH`
-- `3`: `CLIENT_PUSH`
-- `4`: `WECHAT`
-- `5`: `DOU_YIN`
-
-## Examples
-
-```bash
-ae-cli engage +config_item_detail --project_id 1 --config_id cfg_123
-```

package/skills/ae-engage/references/config-item-list.md

@@ -1,18 +0,0 @@
-# ae-engage +config_item_list
-
-
-Query the list of config items in a project.
-
-Mapped command: `ae-cli engage +config_item_list`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-
-## Examples
-
-```bash
-ae-cli engage +config_item_list --project_id 1
-```

package/skills/ae-engage/references/copy-config-template.md

@@ -1,28 +0,0 @@
-# ae-engage +copy_config_template
-
-
-Copy a template from the source config item to the target config item.
-
-Mapped command: `ae-cli engage +copy_config_template`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--source_project_id` | number | Yes | source Project ID |
-| `--source_config_id` | string | Yes | source config item ID |
-| `--source_template_id` | string | Yes | source template ID |
-| `--project_id` / `-p` | number | Yes | target Project ID |
-| `--config_id` | string | Yes | target config item ID |
-
-## Safety Constraints
-
-This command is a **write operation** and and copies the template and dependent resources.
-
-## Examples
-
-```bash
-ae-cli engage +copy_config_template \
-  --source_project_id 1 --source_config_id src_cfg --source_template_id tpl_1 \
-  --project_id 2 --config_id dst_cfg
-```

package/skills/ae-engage/references/delete-config-channel.md

@@ -1,23 +0,0 @@
-# ae-engage +delete_config_channel
-
-
-Delete a config channel.
-
-Mapped command: `ae-cli engage +delete_config_channel`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | config channel ID |
-
-## Safety Constraints
-
-This command is a **write operation** and and deletes a config channel.
-
-## Examples
-
-```bash
-ae-cli engage +delete_config_channel --project_id 1 --channel_id <channel_id>
-```

package/skills/ae-engage/references/delete-config-item.md

@@ -1,24 +0,0 @@
-# ae-engage +delete_config_item
-
-
-Delete a config item.
-
-Mapped command: `ae-cli engage +delete_config_item`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--open_id` | string | Yes | operator open ID |
-
-## Safety Constraints
-
-This command is a **write operation** and deletes a config item.
-
-## Examples
-
-```bash
-ae-cli engage +delete_config_item --project_id 1 --config_id cfg_123 --open_id ou_xxx
-```

package/skills/ae-engage/references/engage-scene-config-item.md

@@ -1,69 +0,0 @@
-# engage-scene config-item
-
-> Capability ids: `engage-scene.config-item.{list,create,update}` · Domain: `engage`.
-
-`config-item` 是配置中心（场景管理）里的配置项。create 走 multipart，可携带可选头像文件。
-
-## Commands
-
-```bash
-# List config items of a project
-ae-cli engage-scene config-item list --project-id <project_id>
-
-# Create a config item (business type, group, optional avatar)
-ae-cli engage-scene config-item create \
-  --project-id <project_id> --config-id <config_id> --config-name <name> \
-  --business-type <config_file|params> \
-  [--config-remark <remark>] [--group-id <group_id>] \
-  [--avatar-word '["A","B"]'] [--file-name avatar.png] [--file-content "$(base64 -i avatar.png)"]
-
-# Update a config item's basic info and bound channel
-ae-cli engage-scene config-item update \
-  --project-id <project_id> --config-id <config_id> \
-  [--config-name <name>] [--config-remark <remark>] [--business-type <type>] \
-  [--group-id <group_id>] [--channel-id <channel_id>]
-```
-
-## Parameters
-
-### list
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-
-### create
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--config-id` | Yes | Config item ID (unique within the project). |
-| `--config-name` | Yes | Config item display name (<=80 chars). |
-| `--business-type` | Yes | Business type: `config_file` or `params`. |
-| `--config-remark` | No | Remark (<=200 chars). |
-| `--group-id` | No | Group ID (0 = default group). |
-| `--avatar-word` | No | JSON array of avatar words for the icon. |
-| `--file-name` | No | Avatar file name incl. extension. |
-| `--file-content` | No | Base64-encoded avatar file content. |
-
-### update
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--config-id` | Yes | Config item ID to update. |
-| `--config-name` | No | New display name. |
-| `--config-remark` | No | New remark. |
-| `--business-type` | No | New business type. |
-| `--group-id` | No | New group ID. |
-| `--channel-id` | No | Config channel ID to bind. |
-
-## Output
-
-- `list`: `data.items` + `data.total`.
-- `create` / `update`: `data.success` — whether the operation succeeded.
-
-## Decision Rules
-
-- `create` / `update` are `write`; `list` is read.
-- Use `config-item list` (or `engage +config_item_list`) to discover existing config items first; never invent IDs.

package/skills/ae-engage/references/manage-strategy.md

@@ -1,73 +0,0 @@
-# ae-engage +manage_strategy
-
-
-Batch manage strategy status or review actions.
-
-Mapped command: `ae-cli engage +manage_strategy`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--action` | string | Yes | action type |
-| `--strategy_uuid_list` | json | No | Strategy UUID JSON array |
-| `--strategy_list` | json | No | Review-entry JSON array |
-| `--reason` | string | No | review reason |
-
-## Enum Notes
-
-### `--action`
-
-- `online`: publish strategy, requires `--strategy_uuid_list`
-- `offline`: take strategy offline, requires `--strategy_uuid_list`
-- `suspend`: suspend strategy, requires `--strategy_uuid_list`
-- `delete`: delete strategy, requires `--strategy_uuid_list`
-- `approve`: review approved, requires `--strategy_list`
-- `deny`: review denied, requires `--strategy_list`
-- `cancel`: cancel review, requires `--strategy_list`
-
-## JSON Parameter Notes
-
-### `--strategy_uuid_list`
-
-Used for actions such as `online`, `offline`, `suspend`, and `delete` that batch-process items directly by UUID.
-
-```json
-["uuid_1", "uuid_2"]
-```
-
-### `--strategy_list`
-
-Used for review actions such as `approve`, `deny`, and `cancel`. Each array item is an object:
-
-| Field | Type | Required | Description |
-|------|------|------|------|
-| `strategyUuid` | string | Yes | strategy UUID |
-| `reason` | string | No | review reason for that strategy |
-
-Examples: 
-
-```json
-[
-  { "strategyUuid": "uuid_1", "reason": "approve by ops" }
-]
-```
-
-## Safety Constraints
-
-This command is a **write operation** and changes the strategy status.
-
-Different `action` values require different parameters:
-
-- `online` / `offline` / `suspend` / `delete`: must include `--strategy_uuid_list`
-- `approve` / `deny` / `cancel`: must include `--strategy_list`
-
-## Examples
-
-```bash
-ae-cli engage +manage_strategy \
-  --project_id 1 --config_id cfg_123 --action online \
-  --strategy_uuid_list '["uuid_1"]'
-```

package/skills/ae-engage/references/strategy-detail.md

@@ -1,72 +0,0 @@
-# ae-engage +strategy_detail
-
-
-Query the details of a single strategy.
-
-Mapped command: `ae-cli engage +strategy_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--strategy_uuid` | string | Yes | strategy UUID |
-
-## Common enums in the response
-
-### `status`
-
-- `0`: `DRAFT`
-- `1`: `ONLINE`
-- `2`: `SUSPEND`
-- `3`: `OFFLINE`
-
-### `mappingStatus`
-
-- `0`: `DRAFT`
-- `1`: `APPROVE`
-- `2`: `DENY`
-- `3`: `REGISTERING`
-- `4`: `REGISTER_FAIL`
-- `5`: `WAITING`
-- `6`: `ONLINE`
-- `7`: `SUSPEND`
-- `8`: `OFFLINE`
-
-### `targetClusterType`
-
-- `0`: `ALL_USERS`
-- `1`: `CUSTOM_CLUSTER`
-- `2`: `SINGLE_USER`
-
-### `realtime`
-
-- `0`: physical cluster, physical audience
-- `1`: virtual cluster, virtual audience
-
-### `triggerType`
-
-- `0`: `SCHEDULED_SINGLE`
-- `1`: `SCHEDULED_RECURRING`
-- `2`: `MANUAL`
-
-### `versionType`
-
-- `0`: history version
-- `1`: current version
-- `2`: update-content version
-
-### `channelType`
-
-- `1`: `WEBHOOK`
-- `2`: `APP_PUSH`
-- `3`: `CLIENT_PUSH`
-- `4`: `WECHAT`
-- `5`: `DOU_YIN`
-
-## Examples
-
-```bash
-ae-cli engage +strategy_detail --project_id 1 --config_id cfg_123 --strategy_uuid uuid_123
-```

package/skills/ae-engage/references/strategy-list.md

@@ -1,20 +0,0 @@
-# ae-engage +strategy_list
-
-
-Query the strategy list.
-
-Mapped command: `ae-cli engage +strategy_list`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | No | config item ID |
-| `--strategy_uuid_list` | json | No | strategy UUID JSON array |
-
-## Examples
-
-```bash
-ae-cli engage +strategy_list --project_id 1 --config_id cfg_123
-```

package/skills/ae-engage/references/update-config-channel-status.md

@@ -1,31 +0,0 @@
-# ae-engage +update_config_channel_status
-
-
-Update the status of a config channel.
-
-Mapped command: `ae-cli engage +update_config_channel_status`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | config channel ID |
-| `--channel_status` | number | Yes | config channel status |
-
-## Enum Notes
-
-### `--channel_status`
-
-- `1`: enabled
-- `2`: disabled
-
-## Safety Constraints
-
-This command is a **write operation** and and modifies the config channel status.
-
-## Examples
-
-```bash
-ae-cli engage +update_config_channel_status --project_id 1 --channel_id <channel_id> --channel_status 1
-```

package/skills/ae-metadata/references/metadata_event_get.md

@@ -1,52 +0,0 @@
-# metadata event get (Super-Event Detail)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md) (`ae-metadata` skill).
->
-> Capability id: `metadata.event.get` · Domain: `metadata` (capability gateway REST, not MCP `analysis_meta`).
-
-## Use Cases
-
-- Fetch **one** super-event metadata record by technical name (full detail, not a paginated list).
-- Inspect virtual event definition (`definition.sources`, filters, relation) when `event_kind=virtual_event`.
-- Read-only; requires metadata **view** permission (`VIEW_META`) in the target project.
-
-## Commands
-
-```bash
-ae-cli metadata event get --project-id <project_id> --event-name <event_name>
-ae-cli metadata event get -p <project_id> --event-name <event_name> --dry-run
-```
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--event-name` | Yes | Super-event technical name. Virtual events use the same field. |
-
-Gateway request body uses snake_case `input`:
-
-```json
-{
-  "project_id": 1,
-  "event_name": "purchase"
-}
-```
-
-## Decision Rules
-
-- Prefer **`metadata event get`** over `analysis-meta event list` when you need **full detail + virtual definition**, not browsing or fuzzy search.
-- Use `ae-analysis` → `analysis-meta event list` first when the event name is unknown or you need keyword search / pagination.
-- If the gateway returns `EVENT_NOT_FOUND`, verify `event_name` spelling and `project_id`; do not invent names.
-- Auth: `cli-token` header (ae-cli injects automatically in sandbox; local CLI uses `getCliToken()`).
-
-## Recommended Chaining
-
-- `ae-analysis`: `analysis-meta event list` (discover name) → `metadata event get` (detail)
-- `metadata event get` → `metadata property get` (inspect properties listed in response)
-
-## Next Steps After Failure
-
-- Empty or not found: confirm project id and exact `event_name` from `analysis-meta event list`.
-- Permission error: confirm metadata view permission in the project.
-- Gateway unavailable: confirm nginx routes `/api/cli/metadata/` and backend capability catalog is deployed.