@thinkingai/ae-cli 6.0.27 → 6.0.28

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

@@ -0,0 +1,36 @@
+# analysis super-metadata export
+
+Use when the user needs to export super event and super property configuration.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis super-metadata export --project-id <project_id>
+ae-cli analysis super-metadata export --project-id <project_id> --request-id cli_0123456789abcdef0123456789abcdef --timeout-seconds 3600
+ae-cli analysis super-metadata export --dry-run
+```
+
+Capability id: `metadata.super_metadata.export`.
+
+Input sends `project_id`, and optional `request_id`, `timeout_seconds`.
+
+Output is the gateway envelope. `data` contains an async export descriptor with `run_id`, `artifact_id`, status fields, and expiration fields. It does not expose inspect/download API paths; use the CLI commands below.
+
+Follow-up workflow:
+
+1. Save `data.run_id` and `data.artifact_id` from the export response.
+2. Poll status with `ae-cli analysis run inspect --run-id <run_id>`.
+3. Continue polling while status is running or pending. Treat `COMPLETED` or `SUCCEEDED` as success, and `FAILED`, `CANCELED`, or `CANCELLED` as terminal failure.
+4. On success, download with `ae-cli analysis artifact download --run-id <run_id> --artifact-id <artifact_id> --output <file>.xlsx`.
+5. If the export is no longer needed, cancel with `ae-cli analysis query cancel --run-id <run_id> --yes`.
+
+Do not write custom Python/curl for polling or download unless the CLI command itself is unavailable.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--request-id` | No | Optional `cli_<32 lowercase hex>` request ID. |
+| `--timeout-seconds` | No | Timeout in seconds, 1 to 7200. Default 3600. |

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

@@ -0,0 +1,24 @@
+# analysis super-metadata import
+
+Use when the user needs to pre-import and confirm-import super event and super property configuration.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis super-metadata import --project-id <project_id> --payload '{}'
+ae-cli analysis super-metadata import --dry-run
+```
+
+Capability id: `metadata.super_metadata.import`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | No | Optional capability payload JSON. |

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

@@ -0,0 +1,25 @@
+# analysis virtual-event create
+
+Use when the user needs to create a virtual event from events and filters.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-event create --project-id <project_id> --override true --payload '{}'
+ae-cli analysis virtual-event create --dry-run
+```
+
+Capability id: `metadata.virtual_event.create`.
+
+Input sends `project_id`, `override`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--override` | No | Whether to override an existing virtual event rule. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-event delete
+
+Use when the user needs to delete a virtual event rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-event delete --project-id <project_id> --v-event-id <v_event_id>
+ae-cli analysis virtual-event delete --dry-run
+```
+
+Capability id: `metadata.virtual_event.delete`.
+
+Input sends `project_id`, `v_event_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--v-event-id` | Yes | Virtual event ID. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-event get
+
+Use when the user needs to get virtual event rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-event get --project-id <project_id> --v-event-id <v_event_id>
+ae-cli analysis virtual-event get --dry-run
+```
+
+Capability id: `metadata.virtual_event.get`.
+
+Input sends `project_id`, `v_event_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--v-event-id` | Yes | Virtual event ID. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-property create
+
+Use when the user needs to create a SQL virtual event or user property.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-property create --project-id <project_id> --payload '{}'
+ae-cli analysis virtual-property create --dry-run
+```
+
+Capability id: `metadata.virtual_property.create`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,25 @@
+# analysis virtual-property sql-rule-delete
+
+Use when the user needs to delete or revoke SQL virtual property rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-property sql-rule-delete --project-id <project_id> --v-prop-id <v_prop_id> --operation <operation>
+ae-cli analysis virtual-property sql-rule-delete --dry-run
+```
+
+Capability id: `metadata.virtual_property.sql_rule_delete`.
+
+Input sends `project_id`, `v_prop_id`, `operation`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--v-prop-id` | Yes | Virtual property ID. |
+| `--operation` | No | Delete operation. Use revoke to revoke instead of delete. |

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

@@ -0,0 +1,24 @@
+# analysis virtual-property sql-rule-update
+
+Use when the user needs to update SQL virtual property rule.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis virtual-property sql-rule-update --project-id <project_id> --payload '{}'
+ae-cli analysis virtual-property sql-rule-update --dry-run
+```
+
+Capability id: `metadata.virtual_property.sql_rule_update`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

package/skills/ae-generate-tracking-code/SKILL.md

@@ -97,7 +97,8 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
    - If the project is missing, ambiguous, or has no `appId`, ask the user to copy APP_ID from AE Admin → "Project Settings" → "Integration Config".
 2. **SERVER_URL** — Data ingestion endpoint (**different from web URL**; go to AE Admin → "Project Settings" → "Integration Config" → fill in "Public URL")
    - If `meta.project_id` is known, you may try `ae-cli analysis_meta +get_project_config --project_id <project_id>` once.
-   - Use the returned value only if the response explicitly contains a receiver URL field such as `serverUrl`, `pushUrl`, `push_url`, `receiverUrl`, `publicUrl`, or equivalent ingestion endpoint field.
+   - Use the returned value only if the response explicitly contains a receiver URL field such as `serverUrl`, `pushUrl`, `push_url`, `receiverUrl`, `publicUrl`, `publicReceiverAddress`, `privateReceiverAddress`, or equivalent ingestion endpoint field.
+   - If both `publicReceiverAddress` and `privateReceiverAddress` are present, prefer `publicReceiverAddress` as `SERVER_URL` for generated snippets unless the user explicitly needs an internal/private-network receiver.
    - If a value is found, ask: **"I found SERVER_URL `<url>` for project `<projectId>`. Use it? yes / enter new value"**
    - ⚠️ "Public URL" only shows if previously filled in; if empty, this field won't display
    - Solution: ask ops for the URL, or **skip this step** (use `SERVER_URL` or `PUSH_URL` placeholder in code)
@@ -507,6 +508,20 @@ Upload list rules:
 - Include generated debug scripts if the user selected the debug option.
 - Do not upload files inserted directly into the user's project; only upload generated output artifacts.
 
+### Attachment upload compatibility
+
+The Agent attachment backend accepts a limited document MIME set. Code/config artifacts such as `.java`, `.kt`, `.swift`, `.m`, `.ets`, `.cs`, `.py`, `.go`, `.ts`, `.js`, `.php`, and `.json` may be rejected if uploaded directly.
+
+Before running `ae-cli agent +add-attachment`, prepare the upload list as follows:
+- Keep every original generated file unchanged under `.ae-cli/output/`.
+- For each generated text artifact whose extension may be unsupported by the attachment backend, create an upload-only sibling copy by appending `.txt` to the filename.
+  - Example: `.ae-cli/output/java-sdk.java` → `.ae-cli/output/java-sdk.java.txt`
+  - Example: `.ae-cli/output/daemon.json` → `.ae-cli/output/daemon.json.txt`
+- The `.txt` copy must have identical content to the original file. Do not wrap it in markdown fences, do not add headers, and do not change line endings intentionally.
+- Upload the `.txt` compatibility copies instead of the unsupported originals.
+- Keep `.md`, `.txt`, and `.csv` artifacts in the upload list as-is.
+- In the final response, list the original deliverable paths first, then mention any `.txt` compatibility copies used only for attachment upload.
+
 If upload succeeds, include the attachment upload result in the final response and tell the user the files are available from the file/attachment management entry. If upload fails because Agent attachment credentials are unavailable, keep the local `.ae-cli/output/` files and tell the user the upload did not complete.
 
 ### All snippets

package/skills/ae-generate-tracking-code/references/snippet-delivery.md

@@ -247,6 +247,22 @@ Upload list must include:
 
 Only upload generated output artifacts. Do not upload files inserted directly into the user's project.
 
+### Upload Compatibility for Code and Config Files
+
+The attachment upload endpoint accepts a limited document MIME set. Many generated tracking artifacts are valid text files but have extensions that may be rejected by the backend when uploaded directly, including `.java`, `.kt`, `.swift`, `.m`, `.ets`, `.cs`, `.py`, `.go`, `.ts`, `.js`, `.php`, and `.json`.
+
+Before calling `ae-cli agent +add-attachment`, build an upload-safe file list:
+
+1. Keep the original generated files unchanged in `.ae-cli/output/`.
+2. For each unsupported text artifact, create a sibling upload-only copy with `.txt` appended to the original filename.
+   - `.ae-cli/output/android-sdk-java.java` → `.ae-cli/output/android-sdk-java.java.txt`
+   - `.ae-cli/output/daemon.json` → `.ae-cli/output/daemon.json.txt`
+3. Copy the content exactly. Do not add markdown fences, comments, titles, or any extra bytes beyond the original text content.
+4. Upload the `.txt` compatibility copies instead of the unsupported originals.
+5. Upload already-supported text artifacts such as `.md`, `.txt`, and `.csv` directly.
+
+The final deliverable list should still point users to the original generated files. Mention the `.txt` files only as attachment-upload compatibility copies.
+
 If upload succeeds, report that the files are available from the file/attachment management entry. If upload fails because Agent attachment credentials are unavailable, preserve the local output files and report the upload failure separately.
 
 ---
@@ -325,7 +341,7 @@ After generation, perform language style checks on each output file:
 
 #### Step 5: Upload Generated Artifacts
 
-Upload all generated `.ae-cli/output/` artifacts to the Agent attachment library using `ae-cli agent +add-attachment --yes --files '<json-array>'`.
+Prepare upload compatibility copies for unsupported code/config extensions, then upload the safe file list to the Agent attachment library using `ae-cli agent +add-attachment --yes --files '<json-array>'`.
 
 ---
 

package/skills/ae-generate-tracking-plan/SKILL.md

@@ -82,7 +82,7 @@ Phase 0 → 1 → 2 → 3 → 4, do not skip steps.
 > Determine `<user_lang>` from user's input language: Chinese→`zh`, English→`en`, Japanese→`ja`, Korean→`ko`. Other languages default to `en`.
 > All subsequent CLI commands must be prefixed with `AE_LANG=<user_lang>` to ensure CLI output and generated xlsx headers match the user's language.
 
-Collect the following **5 items** sequentially, **do NOT ask all at once**:
+Collect the following **4 items** sequentially, **do NOT ask all at once**:
 
 ### Item 1 — Application Scenario
 
@@ -122,15 +122,16 @@ Reply with number(s), e.g. 1 or 1,3. Select up to 2.
 ```
 
 Do not rewrite this source material list as unnumbered bullets, cards, or prose. The user must be able to reply with the visible numbers.
+When translating this prompt, preserve the numeric prefixes and line breaks exactly. Every visible option MUST be on its own line and MUST begin with `1 -`, `2 -`, `3 -`, etc. Never place two numbered options in the same paragraph or visual line. If a Markdown renderer may collapse soft line breaks, use Markdown hard line breaks (two trailing spaces before newline) rather than blank lines. Translation may change only the option text, not the numbering prefix or one-option-per-line structure.
 
 User can multi-select (max 2). Interpret numbers by the **visible list shown to the user**, not by the non-sandbox canonical list.
 
-Canonical source material options:
+Canonical source material options (non-sandbox numbering):
 
-- **Product document** (local path, sandbox workspace path, uploaded attachment, URL, image file, or folder) — Extract events and properties from product docs; supports md/pdf/docx/URL/images (png/jpg/jpeg/webp)
-- **Detailed description** (conversational) — Describe app business flow, core features, user behaviors, monetization model, etc.
-- **Codebase** (local project path; hidden in sandbox) — Analyze source code to extract events and properties
-- **Pre-built template** (built-in industry and game genre templates) — Select a built-in template (run `AE_LANG=<user_lang> ae-cli tracking plan list-templates --json` to see available templates)
+1. **Product document** ****(****local path, sandbox workspace path, uploaded attachment, URL, image file, or folder) — Extract events and properties from product docs; supports md/pdf/docx/URL/images (png/jpg/jpeg/webp)
+2. **Detailed description** (conversational) — Describe app business flow, core features, user behaviors, monetization model, etc.
+3. **Codebase** (local project path; hidden in sandbox) — Analyze source code to extract events and properties
+4. **Pre-built template** (built-in industry and game genre templates) — Select a built-in template (run `AE_LANG=<user_lang> ae-cli tracking plan list-templates --json` to see available templates)
 
 Based on user selection, determine source material type and record to `meta.source_type`:
 
@@ -143,8 +144,29 @@ Based on user selection, determine source material type and record to `meta.sour
 | Any two-item combo | Join two types with `_` | First as baseline, second as supplement (priority: template → codebase → prd → chat) |
 
 **Follow-up questions** (ask in selection order):
-- Product doc → if not in a sandbox environment, ask **"What is the product document path? You can provide one or more paths, separated by commas or newlines (local paths, URLs, image files, or folders)"**
-- Product doc → if in a sandbox environment, ask **"What is the product document path? You can provide one or more sandbox workspace paths, uploaded attachment paths, URLs, image files, or folders. You can also attach/upload relevant files here, and I will read them from the sandbox workspace if available."**
+- Product doc → if not in a sandbox environment, ask exactly:
+  ```text
+  What is the product document path?
+
+  You can provide one or more items, separated by commas or newlines:
+  1. Local file path
+  2. URL
+  3. Image file path
+  4. Folder path
+  ```
+- Product doc → if in a sandbox environment, ask exactly:
+  ```text
+  What is the product document path?
+
+  You can provide one or more items, separated by commas or newlines:
+  1. Sandbox workspace path
+  2. Uploaded attachment path
+  3. URL
+  4. Image file path
+  5. Folder path
+
+  You can also attach/upload relevant files here, and I will read them from the sandbox workspace if available.
+  ```
 - Detailed description → If too vague, follow up on core features, user behaviors, business flows, monetization
 - Codebase → ask **"What is the project directory path?"**, then scan source to extract business logic
 - Pre-built template → display matching templates for user confirmation