@thinkingai/ae-cli 6.0.22 → 6.0.24

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

@@ -0,0 +1,15 @@
+# analysis dashboard share
+
+Use when the user explicitly wants to add, remove, or batch modify dashboard sharing.
+
+Do not use to read sharing only. Use `dashboard share-info`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard share --project-id <project_id> --dashboard-id <dashboard_id> [--member-authorities '{...}'] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and either `member_authorities` or a backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard share-info
+
+Use when the user needs to inspect a dashboard's current sharing configuration.
+
+Do not use to modify sharing. Use `dashboard share`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard share-info --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains dashboard sharing members and permissions.

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

@@ -0,0 +1,15 @@
+# analysis dashboard task-status
+
+Use when the user needs scheduled task status for a dashboard.
+
+Do not use to update daily report configuration. Use `dashboard-daily-report update`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard task-status --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains scheduled task status.

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

@@ -0,0 +1,16 @@
+# analysis dashboard update
+
+Use when the user wants to update dashboard settings in batch or upsert a dashboard note.
+
+Do not use for moving/copying dashboards. Use `dashboard copy`, `dashboard handover`, or the relevant project-space/folder command.
+
+Command:
+
+```bash
+ae-cli analysis dashboard update --project-id <project_id> --operation settings --dashboard-ids '[1001,1002]' [--zone-offset 8] [--payload '{...}'] --yes
+ae-cli analysis dashboard update --project-id <project_id> --operation note-upsert --dashboard-id <dashboard_id> [--note-id <note_id>] [--note-title <title>] [--description <text>] --yes
+```
+
+Input sends `project_id`, `operation`, optional dashboard identifiers, setting fields (including `zone_offset` as hours, e.g. `8` for UTC+8), note fields, and optional `payload`.
+
+Output is the gateway envelope. `data` contains the update result.

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

@@ -0,0 +1,15 @@
+# analysis favorite add
+
+Use when the user wants to favorite one dashboard, BI panel, or folder.
+
+Do not use for sharing or moving assets.
+
+Command:
+
+```bash
+ae-cli analysis favorite add --project-id <project_id> [--asset-id <id>] [--asset-type dashboard|bi_panel|folder] [--space-id <space_id>] [--id <backend_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` and asset identity fields or backend-compatible `payload`.
+
+Output is the gateway envelope. `data` contains the favorite result.

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

@@ -0,0 +1,15 @@
+# analysis favorite remove
+
+Use when the user wants to remove favorite from one dashboard, BI panel, or folder.
+
+Do not use to delete the asset itself.
+
+Command:
+
+```bash
+ae-cli analysis favorite remove --project-id <project_id> [--asset-id <id>] [--asset-type dashboard|bi_panel|folder] [--space-id <space_id>] [--id <backend_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` and asset identity fields or backend-compatible `payload`.
+
+Output is the gateway envelope. `data` contains the remove-favorite result.

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

@@ -0,0 +1,15 @@
+# analysis folder create
+
+Use when the user explicitly wants to create a folder in personal space or a project space.
+
+Do not use to create a project space. Use `project-space create`.
+
+Command:
+
+```bash
+ae-cli analysis folder create --project-id <project_id> --folder-name <name> [--space-id <space_id>] [--parent-folder-id <folder_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `folder_name`, and optional `space_id`, `parent_folder_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the created folder result.

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

@@ -0,0 +1,15 @@
+# analysis folder delete
+
+Use when the user explicitly wants to delete one or more folders.
+
+Do not use for deleting dashboards or BI panels inside a folder. Use the asset delete command.
+
+Command:
+
+```bash
+ae-cli analysis folder delete --project-id <project_id> [--folder-id <folder_id>] [--folder-ids '[1,2]'] [--space-id <space_id>] --yes
+```
+
+Input sends `project_id`, either `folder_id` or `folder_ids`, and optional `space_id`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis folder members
+
+Use when the user needs to inspect folder members.
+
+Do not use to modify members. Use `folder share`.
+
+Command:
+
+```bash
+ae-cli analysis folder members --project-id <project_id> --folder-id <folder_id>
+```
+
+Input sends `project_id` and `folder_id`.
+
+Output is the gateway envelope. `data` contains folder members.

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

@@ -0,0 +1,15 @@
+# analysis folder share
+
+Use when the user wants to add, remove, or batch modify folder sharing members.
+
+Do not use to inspect members only. Use `folder members`.
+
+Command:
+
+```bash
+ae-cli analysis folder share --project-id <project_id> --folder-id <folder_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `folder_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis project-space create
+
+Use when the user explicitly wants to create a project space.
+
+Do not use to create folders inside a space. Use `folder create`.
+
+Command:
+
+```bash
+ae-cli analysis project-space create --project-id <project_id> [--space-name <name>] [--space-desc <text>] [--avatar-type <type>] [--color-key <key>] [--avatar <value>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` plus optional space metadata and `payload`.
+
+Output is the gateway envelope. `data` contains the created project-space result.

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

@@ -0,0 +1,15 @@
+# analysis project-space delete
+
+Use when the user explicitly wants to delete one or more project spaces.
+
+Do not use for removing dashboard or folder membership. Use the matching resource command.
+
+Command:
+
+```bash
+ae-cli analysis project-space delete --project-id <project_id> [--space-id <space_id>] [--space-ids '[1,2]'] --yes
+```
+
+Input sends `project_id` and either `space_id` or `space_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,18 @@
+# analysis project-space get
+
+Use when the user needs one project space detail or name.
+
+Do not use to list all spaces. Use `project-space list`.
+
+Command:
+
+```bash
+ae-cli analysis project-space get --project-id <project_id> --space-id <space_id> [--fields '["spaceId","spaceName"]']
+```
+
+Input sends `project_id`, `space_id`, and optional `fields`.
+
+Supported fields are `spaceId`, `spaceName`, `spaceDesc`, `avatarType`, `colorKey`, `avatar`,
+`allAuthUserAuthority`, `createTime`, `updateTime`, and `owner`.
+
+Output is the gateway envelope. `data` contains project-space detail with snake_case field names.

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

@@ -0,0 +1,15 @@
+# analysis project-space list
+
+Use when the user needs project spaces they can access.
+
+Do not use for project lookup or project ID verification. Use `analysis_common +list_projects`.
+
+Command:
+
+```bash
+ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
+
+Output is the gateway envelope. `data` contains project-space summaries.

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

@@ -0,0 +1,15 @@
+# analysis project-space members
+
+Use when the user needs to inspect project-space members.
+
+Do not use to modify members. Use `project-space share`.
+
+Command:
+
+```bash
+ae-cli analysis project-space members --project-id <project_id> --space-id <space_id>
+```
+
+Input sends `project_id` and `space_id`.
+
+Output is the gateway envelope. `data` contains project-space members.

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

@@ -0,0 +1,15 @@
+# analysis project-space share
+
+Use when the user wants to add, remove, or batch modify project-space sharing members.
+
+Do not use to inspect members only. Use `project-space members`.
+
+Command:
+
+```bash
+ae-cli analysis project-space share --project-id <project_id> --space-id <space_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `space_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis public-link create
+
+Use when the user explicitly wants to generate a public link for a dashboard or BI panel.
+
+Do not use for internal resource URLs. Use `analysis_common +get_resource_url` when applicable.
+
+Command:
+
+```bash
+ae-cli analysis public-link create --project-id <project_id> --resource-type dashboard --resource-id <id> --effective-at "2026-07-08 00:00:00" --expires-at "2026-08-08 00:00:00" [--access-controls '{...}'] [--remark <text>] [--company-id <company_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `resource_type`, `resource_id`, `effective_at`, `expires_at`, and optional public-link fields.
+
+Output is the gateway envelope. `data` contains the generated public-link result.

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

@@ -0,0 +1,15 @@
+# analysis public-link delete
+
+Use when the user explicitly wants to delete one or more public links.
+
+Do not use to temporarily stop access while keeping records. Use `public-link offline`.
+
+Command:
+
+```bash
+ae-cli analysis public-link delete --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>] --yes
+```
+
+Input sends `project_id`, optional `company_id`, and either `link_id` or `link_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis public-link list
+
+Use when the user needs public links in a project.
+
+Do not use for dashboard or BI panel asset listing. Use the matching list command.
+
+Command:
+
+```bash
+ae-cli analysis public-link list --project-id <project_id> [--query <keyword>] [--fields '["id","resource_id"]'] [--limit 20] [--offset 0]
+```
+
+Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
+
+Output is the gateway envelope. `data` contains public-link summaries.

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

@@ -0,0 +1,15 @@
+# analysis public-link offline
+
+Use when the user wants to take one or more public links offline without deleting records.
+
+Do not use to permanently delete links. Use `public-link delete`.
+
+Command:
+
+```bash
+ae-cli analysis public-link offline --project-id <project_id> [--link-id <link_id>] [--link-ids '[1,2]'] [--company-id <company_id>] --yes
+```
+
+Input sends `project_id`, optional `company_id`, and either `link_id` or `link_ids`.
+
+Output is the gateway envelope. `data` contains the offline result.

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

@@ -0,0 +1,15 @@
+# analysis public-link update
+
+Use when the user wants to edit an existing public link.
+
+Do not use to take a link offline. Use `public-link offline`.
+
+Command:
+
+```bash
+ae-cli analysis public-link update --project-id <project_id> --link-id <link_id> --effective-at "2026-07-08 00:00:00" --expires-at "2026-08-08 00:00:00" [--access-controls '{...}'] [--remark <text>] [--company-id <company_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `link_id`, effective/expiration time, and optional public-link fields.
+
+Output is the gateway envelope. `data` contains the update result.

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

@@ -0,0 +1,15 @@
+# analysis query cancel
+
+Use to cancel an async capability-gateway query or export by `run_id`.
+
+Do not use for MCP query cancellation by `request_id`; use `analysis +cancel_query`.
+
+Command:
+
+```bash
+ae-cli analysis query cancel --run-id <run_id> [--reason <reason>] --yes
+```
+
+Input sends `run_id` and optional `reason`.
+
+Output is the gateway envelope. `data` contains the cancellation result.

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

@@ -5,7 +5,7 @@
 ## Command
 
 ```bash
-ae-cli metadata data-table csv-write --project-id <project_id> --operation create --input-file-id <input_file_id> --data-table-name <name> --columns '<columns_json>' --yes
+ae-cli metadata data-table csv-write --project-id <project_id> --operation create --input-file-id <input_file_id> --data-table-name datatable_<project_id>_<name> --columns '<columns_json>' --yes
 ae-cli metadata data-table csv-write --project-id <project_id> --operation incremental_update --data-table-id <id> --input-file-id <input_file_id> --yes
 ae-cli metadata data-table csv-write --project-id <project_id> --operation replace_update --data-table-id <id> --input-file-id <input_file_id> --yes
 ```
@@ -18,12 +18,14 @@ ae-cli metadata data-table csv-write --project-id <project_id> --operation repla
 | `--operation` | Yes | `create`, `incremental_update`, or `replace_update`. |
 | `--input-file-id` | Yes | ID returned by `metadata input-file upload`. |
 | `--data-table-id` | For updates | Existing data table ID. |
-| `--data-table-name` | For create | Technical data table name. |
+| `--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. |
+| `--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. |
 
 ## Decision Rules
 
 - Upload the CSV first with `metadata input-file upload --purpose data_table.csv`.
+- Do not invent `input_file_id` or `data_table_id`; use upload/list outputs.
+- If you provide `--data-table-name`, it must include the project segment, for example `datatable_2_orders`.
 - This is a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.

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

@@ -5,7 +5,7 @@
 ## Command
 
 ```bash
-ae-cli metadata data-table sql-write --project-id <project_id> --operation create --table-name <name> --columns '<columns_json>' --qp '<qp_json>' --strategy overwrite --yes
+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
 ```
 
@@ -15,13 +15,13 @@ ae-cli metadata data-table sql-write --project-id <project_id> --operation updat
 |---|---|---|
 | `--project-id` / `-p` | Yes | Numeric project ID. |
 | `--operation` | Yes | `create` or `update`. |
-| `--columns` | Yes | Column definitions JSON array. |
+| `--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. |
+| `--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 such as `+08:00`. |
+| `--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. |
 
@@ -29,3 +29,4 @@ ae-cli metadata data-table sql-write --project-id <project_id> --operation updat
 
 - 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_property_dimension_table_create_and_bind_csv.md

@@ -5,7 +5,7 @@
 ## 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 <table_name> --columns '<columns_json>' --yes
+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
@@ -16,15 +16,17 @@ ae-cli metadata property create-and-bind-csv-dimension-table --project-id <proje
 | `--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 | Technical data table name. |
+| `--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. |
+| `--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/dist/auth-I2G7OAU2.js

@@ -1,19 +0,0 @@
-import {
-  clearToken,
-  getAuthStatus,
-  getToken,
-  loadToken,
-  resolveHost,
-  saveToken,
-  validateToken
-} from "./chunk-U6QPKCN3.js";
-import "./chunk-WPXHCP4A.js";
-export {
-  clearToken,
-  getAuthStatus,
-  getToken,
-  loadToken,
-  resolveHost,
-  saveToken,
-  validateToken
-};

package/dist/{chunk-WPXHCP4A.js → chunk-65DKFJZB.js}

@@ -143,9 +143,6 @@ function readSandboxCliTokenEntry() {
   }
   return null;
 }
-function ensureDir() {
-  if (!fs3.existsSync(CONFIG_DIR)) fs3.mkdirSync(CONFIG_DIR, { recursive: true });
-}
 function forceMigrateFromFallback() {
   const entry = readSandboxCliTokenEntry();
   if (!entry) return null;
@@ -159,6 +156,9 @@ function getFallbackCliToken(hostUrl) {
   if (entries.length === 1) return entries[0];
   return null;
 }
+function ensureDir() {
+  if (!fs3.existsSync(CONFIG_DIR)) fs3.mkdirSync(CONFIG_DIR, { recursive: true });
+}
 function loadConfig() {
   try {
     if (fs3.existsSync(CONFIG_FILE)) {