@thinkingai/ae-cli 6.0.37 → 6.0.39

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

@@ -24,9 +24,9 @@ ae-cli engage-scene strategy update --project-id <project_id> \
 # Query a strategy's log
 ae-cli engage-scene strategy log --project-id <project_id> --strategy-uuid <uuid>
 
-# Predict custom-audience size (mix QP)
+# Predict custom-audience size
 ae-cli engage-scene strategy predict --project-id <project_id> \
-  --qp '<targetClusterQp JSON string>' \
+  --definition-request '{"type":"condition","conditions":{...}}' \
   --zone-offset 8 \
   [--strategy-uuid <uuid>]
 
@@ -48,7 +48,7 @@ ae-cli engage-scene strategy manage --project-id <project_id> --config-id <confi
 | create | `--project-id`, `--payload` | payload = `ConfigStrategyAddDTO`. |
 | update | `--project-id`, `--payload` | payload = `ConfigStrategyModifyDTO` (`strategyUuid` + fields). |
 | log | `--project-id`, `--strategy-uuid` | read. |
-| predict | `--project-id`, `--qp`, `--zone-offset` | Optional `--strategy-uuid`, `--request-id`. read. |
+| predict | `--project-id`, `--definition-request`, `--zone-offset` | Optional `--strategy-uuid`, `--request-id`. read. |
 | batch-copy | `--project-id`, `--config-id`, `--strategy-ids` | `--op-mode` optional (default `batch`). |
 | manage | `--project-id`, `--config-id`, `--action` | Lifecycle actions require `--strategy-uuid-list`; review actions require `--strategy-list`; write. |
 
@@ -67,10 +67,10 @@ ae-cli engage-scene strategy manage --project-id <project_id> --config-id <confi
 - Discover real strategy UUIDs / config IDs first; never invent IDs.
 - **Custom audience (`targetClusterType=1`)** — follow [`scene-strategy-audience.md`](scene-strategy-audience.md) end-to-end:
   1. Preflight every **用户满足** user property and **用户行为** event via `analysis-meta property get` / `event get`; if missing, **stop** and list available properties — never invent or drop.
-  2. Assemble mix QP with **two-block layout**: `totalCFilter.filts[0]` = 用户满足, `totalCFilter.filts[1]` = 用户行为; `totalCFilter.relation` = 且/或 between them. **Never** nest `event` inside user-side `COMPOUND`.
-  3. `JSON.stringify` → `targetClusterQp`; then `strategy create|update`.
+  2. Build an Analysis-compatible semantic condition in `payload.definitionRequest`.
+  3. Reuse the same definition with `strategy predict --definition-request`.
   4. **Do not** call `analysis user-cluster create` unless the user explicitly asks for an existing/named cluster.
-  - Full QP spec + examples A/B/C: [`scene-strategy-audience.md`](scene-strategy-audience.md).
+  - Semantic contract and examples: [`scene-strategy-audience.md`](scene-strategy-audience.md).
 - **`create` requires an enabled template** on the same config item. Enable workflow: `config-param batch-add` → `template create` → `template update` (non-empty `config[]` with real `paramId`) → `template update-status --status 1`. Otherwise `create` returns `TEMPLATE_ENABLE`.
 - `create` output field is `data.strategy_uuid` (not `strategy_id`).
 - `manage` supports `online`, `offline`, `suspend`, `delete`, `approve`, `deny`, and `cancel`; it is a write operation.

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

@@ -5,6 +5,16 @@ Query the details of a single task.
 
 Mapped command: `ae-cli engage-task task get`
 
+For a custom target audience, the response hides persisted `qp` and returns:
+
+- `definition_status`: `AVAILABLE`, `UNAVAILABLE`, or `NOT_APPLICABLE`
+- `definition_request`: the Analysis-compatible semantic audience definition when available
+- `definition_unavailable_reason`: present only when a historical QP cannot be reversed
+
+Reuse `definition_request` as `req.targetConfig.definitionRequest` when updating a task.
+Soft-deleted tasks are treated as unavailable and return `TASK_NOT_FOUND`, matching task-list
+visibility.
+
 ## Flags
 
 | Flag | Type | Required | Description |

package/skills/ae-engage/references/task-submit-approval.md

@@ -0,0 +1,45 @@
+# engage-task task submit-approval
+
+Submit an existing draft engagement task for approval. The legacy full save-and-submit request remains supported.
+This is a regular write operation.
+
+> Capability id: `engage-task.task.submit-approval` · Domain: `engage`.
+
+```bash
+ae-cli engage-task task submit-approval --project-id <project_id> --task-id <task_id>
+```
+
+## Parameters
+
+| Flag | Required | Notes |
+|---|---|---|
+| `--project-id` / `-p` | yes | Numeric project ID. |
+| `--task-id` | conditional | Existing draft task ID. Recommended after `task save`. |
+| `--request` | conditional | Legacy `ApprovalSaveAndSubmitDTO` / `OperationTaskOpDTO` JSON (camelCase or snake_case). |
+
+Provide exactly one of `--task-id` or `--request`.
+
+## Output
+
+- `data.task_id`
+
+## Request notes
+
+- Prefer `task save` followed by `submit-approval --task-id`. The server loads the persisted draft, validates its
+  trigger rule, and reuses the existing save-and-submit approval workflow.
+- Do not reconstruct or pass `trigger_rule`. It is an internal persisted field.
+- The legacy `--request` mode remains available for existing callers.
+- Required body fields (server validates): `task_name`, `channel_type`, `channel_id`, `group_content_list`, `target_cluster_type`, `trigger_type`, `completion_indicator_def`, `frequency_limits`, `enable_channel_touch_limits`, `group_id`, `trigger_time_strategy`.
+- Missing `expConfig` is auto-filled as `{"enableExp":false}` (same as activity task create/update).
+- TEXT channel params missing `config` are auto-filled with Slate.js JSON from `value`.
+- For schedule-single (`triggerType=0`), include a future `triggerTime` (and `tzOffset` / `triggerTimeStrategy` as needed).
+- Prefer save → submit by task ID; do not invent `taskId` / `channelId`.
+
+## Common Errors
+
+| code | when |
+|---|---|
+| `APPROVAL_INPUT_INVALID` | neither or both of `task_id` and `request` supplied |
+| `REQUEST_REQUIRED` | `--request` missing or not an object |
+| `REQUEST_FIELDS_REQUIRED` | required body fields absent/blank |
+| `CAPABILITY_EXECUTION_FAILED` | unmapped domain failure; check `invocation_id` / Hermes logs |

package/skills/ae-engage/references/validate-flow-node-config.md

@@ -30,7 +30,7 @@ Use `--operation-mode save_flow` for the current exposed MCP protocol. Use `save
 Important current rules:
 
 - `event_trigger` / `event_judge` A segment: use `periodStart`, `periodEnd`, `periodTimeSymbol`; do not use branch-style `delayTime`.
-- `event_split_flow` branch segment: use `delayTime`, `delayTimeSymbol`, `targetClusterType`; omit `triggerRule` on default branches.
+- `event_split_flow` branch segment: use `delayTime`, `delayTimeSymbol`, `targetClusterType`; omit `triggerDefinition` on default branches.
 - `event_trigger targetUserType=2` is invalid.
 - Push `OBJ_ARRAY.value` must be a JSON array, not a stringified array.
 - Push `contentList[].content` should be a JSON array, but a JSON-stringified array is accepted for compatibility.

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

@@ -91,12 +91,12 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
 **⚠️ Key: SERVER_URL and APP_ID are independent config items. Even if draft.json has project_id and host, you MUST resolve and confirm them. `project_id` ≠ `APP_ID`, `host` ≠ `SERVER_URL`.**
 
 1. **APP_ID** — Prefer automatic lookup before asking:
-   - If `meta.project_id` is known, run `ae-cli analysis project info list` once for the current host.
+   - If `meta.project_id` is known, run `ae-cli project info list` once for the current host.
    - Find the project whose `projectId` matches `meta.project_id`.
    - If the matched project has `appId`, ask: **"I found APP_ID `<appId>` for project `<projectId>`. Use it? yes / enter new value"**
    - 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 project info get --project-id <project_id>` once.
+   - If `meta.project_id` is known, you may try `ae-cli project info get --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`, `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"**
@@ -105,7 +105,9 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
 
 **host handling** (optional):
 - If you need to fetch plan from AE (no local draft.json) → ask for host
-- If local draft.json exists → host is not required; only hint user to open AE Debug page during validation phase
+- If local draft.json exists → host is not required for code generation
+- Before Debug validation, run `ae-cli config current` and confirm the active host matches the target AE environment; if it does not, run `ae-cli config set-host <AE_HOST>`
+- Complete Debug validation with `ae-cli tracking debug-device` and `ae-cli tracking debug-data` by default; only hint the user to open the AE Debug page when those CLI capabilities are unavailable
 
 ### If only xlsx file exists (no draft.json)
 
@@ -605,16 +607,30 @@ Provide validation guidance based on selected platforms:
 
 ```
 Validation steps:
-1. Run validation script:
+1. Confirm the active AE environment:
+   ae-cli config current
+
+2. List existing Debug devices:
+   ae-cli tracking debug-device list --project-id <project_id>
+
+3. Create the script's stable device ID if it is missing, then select it:
+   ae-cli tracking debug-device add --project-id <project_id> --device-id <device_id> --device-name <name>
+   ae-cli tracking debug-device select --project-id <project_id> --device-id <device_id>
+
+4. Run validation script:
    - Client: run .ae-cli/output/te-debug-client.<ext>
    - Server: run .ae-cli/output/te-debug-server.<ext>
 
-2. Open AE Debug page:
-   https://<host>/#/data/debug
+5. Query the most recent hour of Debug data:
+   ae-cli tracking debug-data list --project-id <project_id> --device-id <device_id>
+
+6. Confirm has_data=true, then inspect event names, property structures, and error fields.
+   If needed, add --event-name <event_name> or --start-time "YYYY-MM-DD HH:mm:ss".
 
-3. Filter by distinct_id=claude-test to view uploaded data
+7. Only if the CLI capability is unavailable, open the AE Debug page:
+   https://<host>/#/data/debug
 
-4. For LogBus2:
+8. For LogBus2:
    - Copy daemon.json to LogBus2 conf/ directory
    - Start: ./logbus start
    - Official docs: https://docs-v2.thinkingdata.cn/?version=latest&code=logbus2_installation&lan=en-US

package/skills/ae-generate-tracking-code/references/debug-script.md

@@ -3,28 +3,33 @@
 > **Terminology**: 校验脚本 = validation/debug script | 设备绑定 = device binding | Debug 模式 = debug mode | TDDebugConsumer = debug mode consumer (validates data format, does NOT persist to production) | 实时调试 = real-time debugging | 代表业务事件 = representative business events | SDK 日志打印 = SDK log printing
 
 ## Deliverable
+
 `te-debug.<ext>` single file; used to quickly verify SDK configuration is correct.
 
 ---
 
 ## Debug Mode Verification
 
-When using debug mode, you must add the debug device ID in AE Admin before data will appear on the AE **Debug Data** page.
+When using debug mode, register and select the debug device with `ae-cli` before sending events. The Agent can then query the received Debug data directly, without asking the user to return to the AE page.
 
 ### Verification Steps
 
-| Step | Action |
-|---|---|
-| 1 | Add debug device ID in AE Admin: Tracking Management → Debug Data → Add Device |
-| 2 | Run debug script to send test events |
-| 3 | Open AE Debug page: `https://<host>/#/data/debug` |
-| 4 | Filter by `distinct_id` or `device_id` to view uploaded data |
+| Step | Action                                                                                                                                             |
+| ---- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1    | List devices: `ae-cli tracking debug-device list --project-id <project_id>`                                                                        |
+| 2    | Add the script's device ID when missing: `ae-cli tracking debug-device add --project-id <project_id> --device-id <device_id> --device-name <name>` |
+| 3    | Select it: `ae-cli tracking debug-device select --project-id <project_id> --device-id <device_id>`                                                 |
+| 4    | Run the debug script to send test events                                                                                                           |
+| 5    | Query received data: `ae-cli tracking debug-data list --project-id <project_id> --device-id <device_id>`                                           |
+| 6    | If needed, filter one event with `--event-name <event_name>` or inspect it in AE at `https://<host>/#/data/debug`                                  |
 
 ### Common Notes for Client and Server SDKs
 
 - Both use **TDDebugConsumer** (or the platform's equivalent debug mode API)
-- Both require adding device ID in AE Admin to view data on the Debug page
+- Both require registering the same device ID with `ae-cli tracking debug-device add`
 - On validation failure, the SDK prints error logs or throws exceptions (behavior varies by language)
+- `debug-data list` defaults to the most recent hour and returns `has_data`, `event_count`, `data_count`, and the raw Debug records
+- Treat `has_data: true` as evidence that the receiver got Debug data; also inspect each record's error fields before declaring validation successful
 
 ---
 
@@ -32,32 +37,32 @@ When using debug mode, you must add the debug device ID in AE Admin before data
 
 ### Client SDK
 
-| SDK | Debug Mode API | Reference Doc |
-|---|---|---|
-| Unity SDK | `TDConfig config = new TDConfig(appId, serverUrl); config.mode = TDMode.DEBUG; TDAnalytics.Init(config);` | `data-ingestion-guide/client-sdk/game-engine/unity/unity-advanced/debugging-and-logging.md` |
-| Android SDK | `TDConfig config = new TDConfig(this, serverUrl, appId); config.setMode(TDConfig.Mode.DEBUG); TDAnalytics.init(this, config);` | `data-ingestion-guide/client-sdk/android/android-advanced/debugging-and-logging.md` |
-| iOS SDK | `TDConfig *config = [[TDConfig alloc] initWithAppId:appId serverUrl:serverUrl]; config.mode = TDModeDebug; [TDAnalytics startWithConfig:config];` | `data-ingestion-guide/client-sdk/ios/ios-advanced/debugging-and-logging.md` |
-| JavaScript SDK | `ta.init({ appId: appId, server_url: serverUrl, debug: true });` | `data-ingestion-guide/client-sdk/javascript/javascript-advanced/debugging-and-logging.md` |
-| Mini Program SDK | `ta.init({ appId: appId, server_url: serverUrl, debug: true });` | `客户端-sdk/小程序小游戏/进阶指南/实时调试.md` |
-| CocosCreator | See doc | `data-ingestion-guide/client-sdk/game-engine/cocoscreator/cocoscreator-advance/debugging-and-logging.md` |
-| Cocos2d-x | See doc | `data-ingestion-guide/client-sdk/game-engine/cocos2d-x/cocos2d-x-advanced/debugging-and-logging.md` |
-| Unreal SDK | See doc | `data-ingestion-guide/client-sdk/game-engine/unreal/unreal-advanced/debugging-and-logging.md` |
-| Flutter SDK | See doc | `data-ingestion-guide/client-sdk/cross-platform/flutter/flutter-advanced/debugging-and-logging.md` |
-| React Native | See doc | `data-ingestion-guide/client-sdk/cross-platform/react-native/reactnative-advanced/debugging-and-logging.md` |
+| SDK              | Debug Mode API                                                                                                                                    | Reference Doc                                                                                               |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
+| Unity SDK        | `TDConfig config = new TDConfig(appId, serverUrl); config.mode = TDMode.DEBUG; TDAnalytics.Init(config);`                                         | `data-ingestion-guide/client-sdk/game-engine/unity/unity-advanced/debugging-and-logging.md`                 |
+| Android SDK      | `TDConfig config = new TDConfig(this, serverUrl, appId); config.setMode(TDConfig.Mode.DEBUG); TDAnalytics.init(this, config);`                    | `data-ingestion-guide/client-sdk/android/android-advanced/debugging-and-logging.md`                         |
+| iOS SDK          | `TDConfig *config = [[TDConfig alloc] initWithAppId:appId serverUrl:serverUrl]; config.mode = TDModeDebug; [TDAnalytics startWithConfig:config];` | `data-ingestion-guide/client-sdk/ios/ios-advanced/debugging-and-logging.md`                                 |
+| JavaScript SDK   | `ta.init({ appId: appId, server_url: serverUrl, debug: true });`                                                                                  | `data-ingestion-guide/client-sdk/javascript/javascript-advanced/debugging-and-logging.md`                   |
+| Mini Program SDK | `ta.init({ appId: appId, server_url: serverUrl, debug: true });`                                                                                  | `客户端-sdk/小程序小游戏/进阶指南/实时调试.md`                                                              |
+| CocosCreator     | See doc                                                                                                                                           | `data-ingestion-guide/client-sdk/game-engine/cocoscreator/cocoscreator-advance/debugging-and-logging.md`    |
+| Cocos2d-x        | See doc                                                                                                                                           | `data-ingestion-guide/client-sdk/game-engine/cocos2d-x/cocos2d-x-advanced/debugging-and-logging.md`         |
+| Unreal SDK       | See doc                                                                                                                                           | `data-ingestion-guide/client-sdk/game-engine/unreal/unreal-advanced/debugging-and-logging.md`               |
+| Flutter SDK      | See doc                                                                                                                                           | `data-ingestion-guide/client-sdk/cross-platform/flutter/flutter-advanced/debugging-and-logging.md`          |
+| React Native     | See doc                                                                                                                                           | `data-ingestion-guide/client-sdk/cross-platform/react-native/reactnative-advanced/debugging-and-logging.md` |
 
 ### Server SDK
 
-| Language | DebugConsumer API | Reference Doc |
-|---|---|---|
-| Java | `new TDDebugConsumer(serverUrl, appId, deviceId)` | `data-ingestion-guide/server-sdk/java/java-advanced/debugging-and-logging.md` |
-| Python | `TDDebugConsumer(serverUrl, appId, device_id="...")` | `data-ingestion-guide/server-sdk/python/python-advanced/debugging-and-logging.md` |
-| Go | `NewDebugConsumerWithDeviceId(serverUrl, appId, false, deviceId)` | `data-ingestion-guide/server-sdk/golang/golang-advanced/debugging-and-logging.md` |
-| Node.js | `ThinkingData.initWithDebugMode(appId, serverUrl, { deviceId: "..." })` | `data-ingestion-guide/server-sdk/nodejs/nodejs-advanced/debugging-and-logging.md` |
-| PHP | `new TDDebugConsumer(serverUrl, appId, deviceId)` | `data-ingestion-guide/server-sdk/php/php-advanced/debugging-and-logging.md` |
-| Ruby | `TDDebugConsumer.new(serverUrl, appId, deviceId)` | `data-ingestion-guide/server-sdk/ruby/ruby-advanced/debugging-and-logging.md` |
-| Erlang | `tddebug_consumer:new(ServerUrl, AppId, DeviceId)` | `data-ingestion-guide/server-sdk/erlang/erlang-advanced/debugging-and-logging.md` |
-| Lua | `TDDebugConsumer.new(serverUrl, appId, deviceId)` | `data-ingestion-guide/server-sdk/lua/lua-advanced/debugging-and-logging.md` |
-| C | `td_debug_consumer_new(serverUrl, appId, deviceId)` | `data-ingestion-guide/server-sdk/c/c-advanced/debugging-and-logging.md` |
+| Language | DebugConsumer API                                                       | Reference Doc                                                                     |
+| -------- | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
+| Java     | `new TDDebugConsumer(serverUrl, appId, deviceId)`                       | `data-ingestion-guide/server-sdk/java/java-advanced/debugging-and-logging.md`     |
+| Python   | `TDDebugConsumer(serverUrl, appId, device_id="...")`                    | `data-ingestion-guide/server-sdk/python/python-advanced/debugging-and-logging.md` |
+| Go       | `NewDebugConsumerWithDeviceId(serverUrl, appId, false, deviceId)`       | `data-ingestion-guide/server-sdk/golang/golang-advanced/debugging-and-logging.md` |
+| Node.js  | `ThinkingData.initWithDebugMode(appId, serverUrl, { deviceId: "..." })` | `data-ingestion-guide/server-sdk/nodejs/nodejs-advanced/debugging-and-logging.md` |
+| PHP      | `new TDDebugConsumer(serverUrl, appId, deviceId)`                       | `data-ingestion-guide/server-sdk/php/php-advanced/debugging-and-logging.md`       |
+| Ruby     | `TDDebugConsumer.new(serverUrl, appId, deviceId)`                       | `data-ingestion-guide/server-sdk/ruby/ruby-advanced/debugging-and-logging.md`     |
+| Erlang   | `tddebug_consumer:new(ServerUrl, AppId, DeviceId)`                      | `data-ingestion-guide/server-sdk/erlang/erlang-advanced/debugging-and-logging.md` |
+| Lua      | `TDDebugConsumer.new(serverUrl, appId, deviceId)`                       | `data-ingestion-guide/server-sdk/lua/lua-advanced/debugging-and-logging.md`       |
+| C        | `td_debug_consumer_new(serverUrl, appId, deviceId)`                     | `data-ingestion-guide/server-sdk/c/c-advanced/debugging-and-logging.md`           |
 
 ---
 
@@ -67,7 +72,7 @@ When generating a debug script, the skill must:
 
 1. **First read the corresponding SDK's "Real-time Debug" doc** (see reference doc paths below) to confirm the SDK's debug mode API and usage (the table above is an index reference only; actual usage may differ)
 2. Use the corresponding platform's **TDDebugConsumer** or debug mode API
-3. Set `deviceId` (e.g. `claude-test-device`) for AE Admin device registration
+3. Set a stable `deviceId` (e.g. `agent-debug-<project_id>`) and register it with `ae-cli tracking debug-device add`
 4. Read `SERVER_URL` and `appId` from plan (NOT web host)
 5. Pick 3 representative business events from plan (if object array properties exist, construct them fully)
 6. Recommend enabling SDK log printing (for easier troubleshooting)
@@ -76,6 +81,7 @@ When generating a debug script, the skill must:
 ### Post-delivery Prompt
 
 **Platform filtering notes**:
+
 - xlsx "Platform" column values map to `platform` field:
   - `客户端` / `client` → `platform: "client"`
   - `服务端` / `server` → `platform: "server"`
@@ -86,16 +92,19 @@ When generating a debug script, the skill must:
 
 ```
 Verification steps:
-1. Add debug device ID in AE Admin: Tracking Management → Debug Data → Add Device (enter deviceId)
-2. Run debug script
-3. Open AE Debug page: https://<host>/#/data/debug
-4. Filter by distinct_id or device_id to view uploaded data
-5. Check event property structure correctness (especially object array properties)
+1. Run `ae-cli tracking debug-device list --project-id <project_id>`.
+2. If needed, run `ae-cli tracking debug-device add --project-id <project_id> --device-id <device_id> --device-name <name>`.
+3. Run `ae-cli tracking debug-device select --project-id <project_id> --device-id <device_id>`.
+4. Run the debug script.
+5. Run `ae-cli tracking debug-data list --project-id <project_id> --device-id <device_id>`.
+6. Confirm `has_data` is true and inspect error fields and event property structures.
+7. If no data appears, retry with an explicit `--start-time "YYYY-MM-DD HH:mm:ss"` and verify that the script reports the exact same device ID.
 ```
 
 ### Reference Doc Paths
 
 All SDK debug/logging docs are located at:
+
 - `~/.ae-cli/wiki/raw/data-ingestion-guide/client-sdk/<sdk>/<sdk>-advanced/debugging-and-logging.md`
 - `~/.ae-cli/wiki/raw/data-ingestion-guide/server-sdk/<language>/<language>-advanced/debugging-and-logging.md`
 

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

@@ -72,6 +72,8 @@ Phase 0 → 1 → 2 → 3 → 4, do not skip steps.
 > 
 > **Language rules**: For newly generated content, user-facing fields in draft.json (`display_name`, `event_desc`, `event_tag`,
 > property `display_name`, property `desc`, etc.) should be generated in the **user's input language**.
+> Every event, event property, common event property, and user property must have a non-empty `display_name`.
+> A canonical snake_case identifier is not a substitute for a user-facing display name.
 > For imported templates, do NOT translate those fields manually. Template sheet names, headers, property type display values,
 > CLI messages, and auto-track/i18n-owned labels must come from `src/tracking/i18n` via `AE_LANG=<user_lang>` and `draft.meta.lang`.
 > When a localized label is needed, inspect `src/tracking/i18n` and use the existing resource key/value; do not invent translations from the model.
@@ -969,6 +971,7 @@ User ok → **immediately execute archive command**, then proceed to Phase 3.
 - [ ] Do event/property names contain only letters, digits, and underscores (no Chinese, no spaces)?
 - [ ] Are there duplicate event names or synonymous events coexisting (e.g. `order_create` and `create_order`)?
 - [ ] Does the same property name map to multiple display names or types?
+- [ ] Does every event, event property, common event property, and user property have a non-empty `display_name` in the user's language?
 
 ### Revenue Model Required Events Check
 
@@ -1251,6 +1254,26 @@ AE_LANG=<user_lang> ae-cli tracking plan upload --project <projectId> --xlsx .ae
 
 On successful upload, prompt user to verify in AE Admin. **Provide the full URL** (tracking plan page URL format: `https://<host>/#/data/plan`).
 
+Then read the uploaded plan back through ae-cli and synchronize its display names to any event/property metadata
+that already exists in the project:
+
+```bash
+AE_LANG=<user_lang> ae-cli tracking plan get --project-id <projectId> --host <host>
+AE_LANG=<user_lang> ae-cli tracking plan sync-display-names \
+  --project-id <projectId> \
+  --draft .ae-cli/draft.json \
+  --host <host>
+```
+
+`sync-display-names` is intentionally safe to rerun:
+
+- It fills only blank event/property metadata display names.
+- It never overwrites a non-empty display name already maintained in AE.
+- `missing_in_metadata` means that the event/property has not appeared in project metadata yet; it is not an upload failure.
+  Report those names and rerun the same command after the first Debug or production data reaches AE.
+- `missing_display_name_in_draft` means the generated plan is incomplete. Add the missing localized `display_name`,
+  regenerate/validate the xlsx, and rerun the upload/synchronization flow.
+
 ---
 
 ### 4.4 Upload Failure Handling and Auto-fix
@@ -1289,7 +1312,9 @@ Fixed: Fixed object array sub-property inconsistency, Fixed display name duplica
 
 ### 4.5 Post-success Actions
 
-After successful upload, prompt user to verify in AE Admin. **Provide the full URL** (tracking plan page URL format: `https://<host>/#/data/plan`)
+After successful upload and display-name synchronization, prompt user to verify in AE Admin. **Provide the full URL**
+(tracking plan page URL format: `https://<host>/#/data/plan`). Include a short synchronization summary:
+updated counts, preserved existing counts, and any names still missing from project metadata.
 
 **Ask about generating tracking code**:
 

package/skills/ae-metadata/SKILL.md

@@ -53,7 +53,7 @@ ae-cli metadata property <dimension-table-action> [options]
 
 ## PROJECT_ID_GATE
 
-Same rules as `ae-analysis`: reuse verified project context in one conversation; otherwise `ae-cli analysis project info list` (or `ae-analysis` skill) to resolve `project_id`.
+Same rules as `ae-analysis`: reuse verified project context in one conversation; otherwise `ae-cli project info list` (or `ae-analysis` skill) to resolve `project_id`.
 
 ## Commands (10)
 

package/dist/config-BSSALXEN.js

@@ -1,128 +0,0 @@
-import {
-  GLOBAL_QUERY_CONFIG_KEY,
-  getAnalysisMappingPathForClusterMode,
-  getClusterInfoFilePath,
-  isGlobalQueryModeEnabled,
-  setGlobalQueryModeEnabled
-} from "./chunk-LCXU3AAT.js";
-import {
-  printError,
-  printOutput
-} from "./chunk-KTYR3U6D.js";
-import "./chunk-E7UXXHO3.js";
-import "./chunk-IR4ZLVPW.js";
-import {
-  addHost,
-  loadConfig,
-  normalizeUrl,
-  setActiveHost
-} from "./chunk-V6FR6WTW.js";
-import "./chunk-LYVNONC4.js";
-
-// src/commands/config.ts
-function registerConfig(program) {
-  const configCmd = program.command("config").description("AE host and environment configuration").action(() => {
-    printError("config", "Missing subcommand.", "Run: ae-cli config --help");
-    process.exit(1);
-  });
-  configCmd.command("list").description("List configured AE environments").action(async () => {
-    await printConfigList(program);
-  });
-  configCmd.command("current").description("Show the active AE environment").action(async () => {
-    await printCurrentConfig(program);
-  });
-  configCmd.command("use <env>").description("Switch active AE environment by exact URL or unique label").action(async (env) => {
-    await useConfigEnv(program, env);
-  });
-  configCmd.command("set-host <url>").description("Set the active AE host non-interactively (adds it if not already configured)").option("--label <label>", "Display label for this host (defaults to the host URL)").action(async (url, opts) => {
-    const normalized = normalizeUrl(url);
-    const label = opts.label || normalized;
-    addHost(normalized, label);
-    setActiveHost(normalized);
-    await printOutput({ activeHost: normalized, label }, program.opts().format || "json");
-  });
-  const clusterMode = configCmd.command("cluster-mode").description("Manage local multi-cluster analysis MCP mode").action(async () => {
-    await printClusterModeStatus(program);
-  });
-  clusterMode.command("status").description("Show local multi-cluster analysis MCP mode").action(async () => {
-    await printClusterModeStatus(program);
-  });
-  clusterMode.command("enable").description("Enable local multi-cluster analysis MCP mode").action(async () => {
-    setGlobalQueryModeEnabled(true);
-    await printClusterModeStatus(program);
-  });
-  clusterMode.command("disable").description("Disable local multi-cluster analysis MCP mode").action(async () => {
-    setGlobalQueryModeEnabled(false);
-    await printClusterModeStatus(program);
-  });
-}
-async function printClusterModeStatus(program) {
-  const enabled = isGlobalQueryModeEnabled();
-  await printOutput({
-    [GLOBAL_QUERY_CONFIG_KEY]: enabled,
-    path: getClusterInfoFilePath(),
-    analysisMappingPath: getAnalysisMappingPathForClusterMode(enabled)
-  }, program.opts().format || "json", program.opts().jq);
-}
-function readHostViews() {
-  const config = loadConfig();
-  const hosts = Object.entries(config.hosts).map(([url, entry]) => ({
-    url,
-    label: entry.label,
-    active: url === config.activeHost
-  }));
-  return { activeHost: config.activeHost, hosts };
-}
-async function printConfigList(program) {
-  const { activeHost, hosts } = readHostViews();
-  await printOutput({ activeHost, hosts }, program.opts().format || "json", program.opts().jq);
-}
-async function printCurrentConfig(program) {
-  const { activeHost, hosts } = readHostViews();
-  const current = hosts.find((h) => h.url === activeHost);
-  if (!current) {
-    failConfig("No active AE environment configured.", "Run: ae-cli config use <env> or ae-cli config list");
-    return;
-  }
-  await printOutput({ activeHost: current.url, label: current.label }, program.opts().format || "json", program.opts().jq);
-}
-async function useConfigEnv(program, env) {
-  const target = resolveHost(env);
-  if (target.status === "not-found") {
-    failConfig(
-      `No AE environment matched: ${env}`,
-      target.hosts.length > 0 ? `Available environments: ${formatHostOptions(target.hosts)}` : "Run: ae-cli config list"
-    );
-    return;
-  }
-  if (target.status === "duplicate-label") {
-    failConfig(
-      `Duplicate label: ${env}`,
-      `Rename duplicate labels first. Run: ae-cli config list \u2014 ${formatHostOptions(target.matches)}`
-    );
-    return;
-  }
-  setActiveHost(target.host.url);
-  await printOutput({ activeHost: target.host.url, label: target.host.label }, program.opts().format || "json", program.opts().jq);
-}
-function resolveHost(env) {
-  const raw = env.trim();
-  const selector = raw.startsWith("http://") || raw.startsWith("https://") ? normalizeUrl(raw) : raw;
-  const { hosts } = readHostViews();
-  const byUrl = hosts.find((h) => h.url === selector);
-  if (byUrl) return { status: "found", host: byUrl };
-  const byLabel = hosts.filter((h) => h.label === raw);
-  if (byLabel.length === 1) return { status: "found", host: byLabel[0] };
-  if (byLabel.length > 1) return { status: "duplicate-label", matches: byLabel };
-  return { status: "not-found", hosts };
-}
-function formatHostOptions(hosts) {
-  return hosts.map((h) => `${h.label} (${h.url})`).join(", ");
-}
-function failConfig(message, hint) {
-  printError("config", message, hint);
-  process.exitCode = 1;
-}
-export {
-  registerConfig
-};