@thinkingai/ae-cli 6.1.6 → 6.1.8

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-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.

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

@@ -1,54 +0,0 @@
-# metadata property get (Super-Property Detail)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md) (`ae-metadata` skill).
->
-> Capability id: `metadata.property.get` · Domain: `metadata` (capability gateway REST, not MCP `analysis_meta`).
-
-## Use Cases
-
-- Fetch **one** super-property metadata record (event scope or user scope).
-- Inspect virtual property definition (`definition.expression`, `dependencies`).
-- Read-only; requires metadata **view** permission in the target project.
-
-## Commands
-
-```bash
-ae-cli metadata property get --project-id <project_id> --property-name <name> --property-scope event
-ae-cli metadata property get --project-id <project_id> --property-name <name> --property-scope user --dry-run
-```
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--property-name` | Yes | Super-property technical name. |
-| `--property-scope` | Yes | `event` (super event properties) or `user` (super user properties). |
-
-Gateway request body uses snake_case `input`:
-
-```json
-{
-  "project_id": 1,
-  "property_name": "price",
-  "property_scope": "event"
-}
-```
-
-## Decision Rules
-
-- Prefer **`metadata property get`** over `analysis-meta property list` when you need **full detail + virtual definition**, not browsing or fuzzy search.
-- Use `ae-analysis` → `analysis-meta property list` first when the property name is unknown or you need keyword search / pagination.
-- `property_scope` must be exactly `event` or `user` (backend accepts case-insensitive).
-- Virtual / dict / exchange-rate properties are addressed by `property-name` only; do not pass legacy `prop_name`.
-- Event-scoped names like `#account_id` must be passed literally (quote in shell when `#` is present).
-
-## Recommended Chaining
-
-- `ae-analysis`: `analysis-meta property list` (discover name + scope) → `metadata property get` (detail)
-- `metadata event get` → `metadata property get` (follow properties from event detail)
-
-## Next Steps After Failure
-
-- Not found: confirm scope (`event` vs `user`) and exact name from `analysis-meta property list`.
-- Permission error: confirm metadata view permission in the project.

package/dist/{te-community-WXGB6IOX.js → te-community-QOYIYEJI.js}

@@ -1,6 +1,3 @@
-import {
-  registerCapabilityGatewayRoute
-} from "./chunk-PTE56QPL.js";
 import {
   callMcpTool,
   parseMcpResult,
@@ -8,6 +5,9 @@ import {
   resolveMcpUrl
 } from "./chunk-CPVTECJ3.js";
 import "./chunk-LCXU3AAT.js";
+import {
+  registerCapabilityGatewayRoute
+} from "./chunk-PTE56QPL.js";
 import "./chunk-E7UXXHO3.js";
 import "./chunk-IR4ZLVPW.js";
 import "./chunk-V6FR6WTW.js";

package/dist/{te-community-X2AHXGCA.js → te-community-UFKI6ONP.js}

@@ -1,6 +1,3 @@
-import {
-  registerCapabilityGatewayRoute
-} from "./chunk-PTE56QPL.js";
 import {
   callMcpTool,
   parseMcpResult,
@@ -8,6 +5,9 @@ import {
   resolveMcpUrl
 } from "./chunk-3P3562ZX.js";
 import "./chunk-LCXU3AAT.js";
+import {
+  registerCapabilityGatewayRoute
+} from "./chunk-PTE56QPL.js";
 import "./chunk-E7UXXHO3.js";
 import "./chunk-IR4ZLVPW.js";
 import "./chunk-V6FR6WTW.js";