@thinkingai/ae-cli 6.0.20 → 6.0.24

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

@@ -0,0 +1,32 @@
+# metadata data-table sql-write
+
+> Capability id: `metadata.data_table.sql_write` · Domain: `metadata`.
+
+## Command
+
+```bash
+ae-cli metadata data-table sql-write --project-id <project_id> --operation create --table-name datatable_<project_id>_<name> --columns '<columns_json>' --qp '<qp_json>' --zone-offset 8 --strategy overwrite --yes
+ae-cli metadata data-table sql-write --project-id <project_id> --operation update --data-table-id <id> --columns '<columns_json>' --qp '<qp_json>' --yes
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--operation` | Yes | `create` or `update`. |
+| `--columns` | Yes | Column definitions JSON array. Preferred fields are `column_name`, `column_type`, and `column_desc`; CLI also accepts `name`, `type`, and `display_name` aliases. |
+| `--qp` | Yes | SQL data table query plan JSON. |
+| `--data-table-id` | For update | Existing data table ID. |
+| `--table-name` | For create | Technical table name. Use `datatable_<project_id>_<name>`. |
+| `--display-name` | No | Human-readable name. |
+| `--remarks` | No | Table remarks. |
+| `--zone-offset` | No | Time zone offset in hours. For example, UTC+8 is `8` and UTC-5 is `-5`. Valid range: -12 to 14. |
+| `--strategy` | No | `overwrite` or `insert`. |
+| `--update-cron` | No | Scheduled update cron. |
+
+## Decision Rules
+
+- This is a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.
+- Keep `columns` and `qp` as valid JSON; do not pass raw SQL unless the server schema requires it inside `qp`.
+- If you provide a table name, it must include the project segment, for example `datatable_2_orders_sql`.

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

@@ -0,0 +1,52 @@
+# 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 +list_events` when you need **full detail + virtual definition**, not browsing or fuzzy search.
+- Use `ae-analysis` → `analysis_meta +list_events` 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 +list_events` (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 `+list_events`.
+- 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_input_file_upload.md

@@ -0,0 +1,29 @@
+# metadata input-file upload
+
+> Capability endpoint: `POST /api/cli/metadata/v1/input-files` · Domain: `metadata`.
+
+## Use Cases
+
+- Upload a local CSV file before `metadata data-table csv-write`.
+- Get an `input_file_id` such as `ifile_<32 lowercase hex>`.
+
+## Command
+
+```bash
+ae-cli metadata input-file upload --project-id <project_id> --purpose data_table.csv --file <local_file> --yes
+ae-cli metadata input-file upload --project-id <project_id> --purpose data_table.csv --file <local_file> --dry-run
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--purpose` | Yes | Input-file purpose. Use `data_table.csv` for data table CSV imports. |
+| `--file` | Yes | Local file path to upload. |
+
+## Decision Rules
+
+- Run `--dry-run` first to verify the gateway URL and multipart fields.
+- Use the returned `input_file_id` in CSV data-table write or create-and-bind commands.
+- This is a write command; non-dry-run execution requires `--yes`.

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

@@ -0,0 +1,27 @@
+# metadata property bind-existing-dimension-table
+
+> Capability id: `metadata.property.bind_existing_dimension_table` · Domain: `metadata`.
+
+## Command
+
+```bash
+ae-cli metadata property bind-existing-dimension-table --project-id <project_id> --property-name <name> --property-scope user --data-table-id <id> --yes
+ae-cli metadata property bind-existing-dimension-table --project-id <project_id> --property-name <name> --property-scope event --data-table-id <id> --dict-columns '["display_name"]' --yes
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--property-name` | Yes | Property technical name. |
+| `--property-scope` | Yes | Property owner table, for example `event` or `user`. |
+| `--data-table-id` | Yes | Existing dimension data table ID. |
+| `--timestamp-join-format` | No | Timestamp join format. |
+| `--dict-columns` | No | Dictionary column names JSON array. |
+
+## Decision Rules
+
+- Confirm the property with `metadata property get` or `analysis_meta +list_properties`.
+- Confirm the data table with `metadata data-table get`.
+- This is a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.

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

@@ -0,0 +1,32 @@
+# metadata property create-and-bind-csv-dimension-table
+
+> Capability id: `metadata.property.create_and_bind_csv_dimension_table` · Domain: `metadata`.
+
+## Command
+
+```bash
+ae-cli metadata property create-and-bind-csv-dimension-table --project-id <project_id> --property-name <name> --property-scope user --input-file-id <input_file_id> --data-table-name datatable_<project_id>_<name> --columns '<columns_json>' --yes
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--property-name` | Yes | Property technical name. |
+| `--property-scope` | Yes | Property owner table, for example `event` or `user`. |
+| `--input-file-id` | Yes | ID returned by `metadata input-file upload`. |
+| `--data-table-name` | No | Optional technical data table name. If supplied, use `datatable_<project_id>_<name>`. |
+| `--display-name` | No | Human-readable table name. |
+| `--description` | No | Table description. |
+| `--columns` | No | Column definitions JSON array. Preferred fields are `column_name`, `select_type`, and `column_desc`; CLI also accepts `name`, `type`, and `display_name` aliases. |
+| `--timestamp-join-format` | No | Timestamp join format. |
+| `--dict-columns` | No | Dictionary column names JSON array. |
+
+## Decision Rules
+
+- Upload the CSV first with `metadata input-file upload --purpose data_table.csv`.
+- Do not invent `input_file_id`; use the value returned by upload.
+- If you provide `--data-table-name`, it must include the project segment, for example `datatable_2_user_dict`.
+- Use this one-step command when the user wants a new CSV dimension table bound to a property.
+- This is a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.

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

@@ -0,0 +1,54 @@
+# 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 +list_properties` when you need **full detail + virtual definition**, not browsing or fuzzy search.
+- Use `ae-analysis` → `analysis_meta +list_properties` 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 +list_properties` (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 `+list_properties`.
+- Permission error: confirm metadata view permission in the project.

package/dist/auth-DYC2BGLM.js

@@ -1,21 +0,0 @@
-import {
-  clearToken,
-  getAuthStatus,
-  getToken,
-  loadToken,
-  resolveHost,
-  saveToken,
-  setTokenManual,
-  validateToken
-} from "./chunk-RSHMZ3LG.js";
-import "./chunk-6W4QOZAL.js";
-export {
-  clearToken,
-  getAuthStatus,
-  getToken,
-  loadToken,
-  resolveHost,
-  saveToken,
-  setTokenManual,
-  validateToken
-};