@thinkingai/ae-cli 6.0.36 → 6.0.38

package/dist/{update-ER7VFU55.js → update-DKG6UXEM.js}

@@ -1,11 +1,13 @@
 import {
-  AE_CLI_SKILLS_REPO,
-  OPEN_SOURCE_AE_CLI_PACKAGE,
+  buildVersionInstallPlan,
   fetchCliConfig,
+  friendlyVersionSyncFailure,
   getCachedCompatForHost,
+  installVersion,
   printError,
-  printOutput
-} from "./chunk-JTKMDN4A.js";
+  printOutput,
+  recordVersionSyncResult
+} from "./chunk-KTYR3U6D.js";
 import {
   peekCliToken
 } from "./chunk-E7UXXHO3.js";
@@ -17,7 +19,6 @@ import {
 import "./chunk-LYVNONC4.js";
 
 // src/commands/update.ts
-import { spawnSync } from "child_process";
 var HOST_OPTION_DESC = "Override active AE host URL (e.g., https://ta.thinkingdata.cn)";
 var SEMVER_RE = /^\d+\.\d+\.\d+(?:[-+].*)?$/;
 function registerUpdate(program) {
@@ -30,9 +31,40 @@ function registerUpdate(program) {
       await printOutput({ action: "update", dryRun: true, ...plan }, program.opts().format || "json", program.opts().jq);
       return;
     }
-    runCommand("npm", ["i", "-g", `${OPEN_SOURCE_AE_CLI_PACKAGE}@${target}`]);
-    runCommand("npx", ["skills", "add", `${AE_CLI_SKILLS_REPO}#v${target}`, "-g", "-y"]);
-    await printOutput({ action: "update", dryRun: false, ...plan }, program.opts().format || "json", program.opts().jq);
+    const result = installVersion(target, {
+      progress: (message) => process.stderr.write(`${message}
+`)
+    });
+    if (host) {
+      recordVersionSyncResult(host, target, result);
+    }
+    if (!result.ok) {
+      const message = result.skillsPending ? `ae-cli ${target} was installed, but Skills synchronization failed.` : `Could not install ae-cli ${target}.`;
+      printError(
+        "config",
+        message,
+        `${friendlyVersionSyncFailure(result)} Check access and run: ae-cli update`,
+        "AE_CLI_UPDATE_FAILED",
+        {
+          target,
+          stage: result.stage,
+          cause: result.cause,
+          skillsPending: result.skillsPending
+        }
+      );
+      process.exitCode = 1;
+      return;
+    }
+    await printOutput(
+      {
+        action: "update",
+        dryRun: false,
+        ...plan,
+        skillsSource: result.skillsSource
+      },
+      program.opts().format || "json",
+      program.opts().jq
+    );
   });
 }
 async function resolveTargetVersion(program, opts) {
@@ -74,24 +106,14 @@ function resolveUpdateHost(program, opts) {
   return raw ? normalizeUrl(raw) : void 0;
 }
 function buildUpdatePlan(target, host) {
+  const installPlan = buildVersionInstallPlan(target);
   return {
-    target,
+    target: installPlan.target,
     ...host ? { host } : {},
-    commands: [
-      `npm i -g ${OPEN_SOURCE_AE_CLI_PACKAGE}@${target}`,
-      `npx skills add ${AE_CLI_SKILLS_REPO}#v${target} -g -y`
-    ]
+    commands: installPlan.commands,
+    skillsSources: installPlan.skillsSources
   };
 }
-function runCommand(command, args) {
-  const result = spawnSync(command, args, { stdio: "inherit" });
-  if (result.error) {
-    throw result.error;
-  }
-  if (result.status !== 0) {
-    process.exit(result.status ?? 1);
-  }
-}
 function failUpdate(message, hint) {
   printError("config", message, hint);
   process.exitCode = 1;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkingai/ae-cli",
-  "version": "6.0.36",
+  "version": "6.0.38",
   "description": "CLI tool for ThinkingAI (AE) analytics platform",
   "type": "module",
   "bin": {
@@ -41,13 +41,15 @@
     "verify:agent-tools": "node scripts/verify-agent-tools.mjs && npm run verify:sandbox-tools",
     "verify:system-tools": "node scripts/verify-system-tools.mjs && npx tsx tests/system-domain.test.ts && npx tsx tests/sandbox-tool-package.test.ts",
     "verify:sandbox-tools": "tsx test/sandbox-tools.test.ts",
-    "verify:tracking-tools": "node test/tracking-client.test.mjs && node test/tracking-skill-flow.test.mjs && node test/tracking-commands.test.mjs",
+    "verify:tracking-tools": "tsx test/tracking-client.test.mjs && tsx test/tracking-skill-flow.test.mjs && node test/tracking-commands.test.mjs && tsx tests/tracking-display-name-sync.test.ts",
     "verify:self-check-overlay": "node test/self-check-overlay.test.mjs",
     "verify:update-check": "npx tsx test/update-check.test.mjs",
+    "verify:version-sync": "npx tsx tests/version-sync.test.ts",
     "qa-changed": "node scripts/qa-changed.mjs",
     "self-check": "node self-check/scan.mjs",
     "check:release": "node self-check/release-gate.mjs",
-    "sync:skills-to-db": "node scripts/sync-skills-to-db.mjs",
+    "sync:skills-to-system": "node scripts/sync-skills-to-system.mjs",
+    "verify:system-skills-sync": "node --test test/sync-system-skills.test.mjs",
     "check:agents-docs": "node scripts/check-agents-docs-sync.mjs",
     "prepublishOnly": "npm run check:release && npm run build",
     "start": "node dist/index.js",
@@ -86,7 +88,6 @@
     "@types/turndown": "^5.0.6",
     "@types/ws": "^8.5.0",
     "jszip": "^3.10.1",
-    "mysql2": "^3.22.6",
     "tsup": "^8.0.0",
     "tsx": "^4.0.0",
     "typescript": "^5.5.0"

package/skills/ae-agent/SKILL.md

@@ -76,8 +76,8 @@ If the user's intent is data analysis, audience management, metadata governance,
 ### Automations (3)
 
 - `+list-automations` ([doc](references/list-automations.md)) — list current user's Agent automation tasks
-- `+create-automation` ([doc](references/create-automation.md)) — create an Agent automation task (hourly/daily/weekly/monthly or cron)
-- `+update-automation` ([doc](references/update-automation.md)) — update an automation's name, instruction, schedule, or enabled state
+- `+create-automation` ([doc](references/create-automation.md)) — create an Agent automation task (hourly/daily/weekly/monthly or cron; optional continuous conversation)
+- `+update-automation` ([doc](references/update-automation.md)) — update an automation's name, instruction, schedule, enabled state, or conversation mode
 
 ### Models (6)
 

package/skills/ae-agent/references/create-automation.md

@@ -8,6 +8,7 @@ Domain: **Automations / write**
 - Create an Agent automation task that runs on a schedule (hourly / daily / weekly / monthly or cron).
 - Returns the newly created automation object including its `id` and initial `status`.
 - Automations are **enabled by default**; pass `--enabled false` only when the user explicitly asks to create the task without enabling it.
+- Automations create a new conversation for every run by default. Pass `--reuse-conversation true` only when the user explicitly wants future runs to continue in one conversation.
 
 ## Mandatory Rules (MUST)
 - `--name` and `--message` are required.
@@ -43,6 +44,14 @@ ae-cli agent +create-automation \
   --message "Summarize yesterday's AI news" \
   --enabled false
 
+# Keep future runs in one visible conversation
+ae-cli agent +create-automation \
+  --name "Daily AI Brief" \
+  --schedule-kind daily \
+  --time 09:00 \
+  --message "Summarize yesterday's AI news" \
+  --reuse-conversation true
+
 # Weekly schedule on Sunday
 ae-cli agent +create-automation \
   --name "Weekly Report" \
@@ -76,6 +85,7 @@ ae-cli agent +create-automation --dry-run --name "Test" --message "x" --schedule
 | `--agent-name` | No | Agent name; use only after `+list-agents` discovery |
 | `--model` | No | Model record ID; defaults to current selected model |
 | `--enabled` | No | `true` (default) \| `false` |
+| `--reuse-conversation` | No | `true` to continue in one conversation; `false` (default) to create one per run |
 | `--conversation-id` | No | Conversation ID fallback for resolving current Agent |
 
 \* One of `--cron` or `--schedule-kind` is required.
@@ -84,6 +94,7 @@ ae-cli agent +create-automation --dry-run --name "Test" --message "x" --schedule
 - If the user provides a natural-language schedule ("every day at 9am"), translate it to `--schedule-kind daily --time 09:00`.
 - If the user wants a cron-only schedule not covered by the kinds, use `--cron`.
 - If no Agent is specified, the automation targets the current conversation's Agent; verify with `+list-agents` when in doubt.
+- Set `--reuse-conversation true` only when the user explicitly requests continuity across runs. The platform may rotate the underlying provider session while retaining the visible conversation history.
 - Use `--dry-run` first to verify the request shape before executing.
 
 ## Next Steps on Failure

package/skills/ae-agent/references/update-automation.md

@@ -5,13 +5,13 @@
 Domain: **Automations / write**
 
 ## Use Cases
-- Update an existing Agent automation task's name, instruction, schedule, or enabled state.
+- Update an existing Agent automation task's name, instruction, schedule, enabled state, or conversation mode.
 - Used to pause (`--enabled false`) or resume (`--enabled true`) an automation, or to change its schedule/message.
 - Obtain the automation `id` via `+list-automations` — never guess.
 
 ## Mandatory Rules (MUST)
 - `--id` is required. Obtain the real ID via `+list-automations` — do not guess.
-- At least one update field must be provided (`--name`, `--message`, `--enabled`, `--cron`, or a `--schedule-kind` with its time/day fields).
+- At least one update field must be provided (`--name`, `--message`, `--enabled`, `--reuse-conversation`, `--cron`, or a `--schedule-kind` with its time/day fields).
 - `--cron` and `--schedule-kind` are mutually exclusive.
 - This is an ordinary `write` operation and does not require CLI confirmation.
 - Do not surface raw automation IDs, raw JSON, or concrete detail paths in user-facing replies.
@@ -32,6 +32,12 @@ ae-cli agent +update-automation --id <automation-id> --enabled false
 # Resume an automation
 ae-cli agent +update-automation --id <automation-id> --enabled true
 
+# Reuse the most recent valid conversation on future runs
+ae-cli agent +update-automation --id <automation-id> --reuse-conversation true
+
+# Return to creating a new conversation for every run
+ae-cli agent +update-automation --id <automation-id> --reuse-conversation false
+
 # Rename and change the instruction
 ae-cli agent +update-automation \
   --id <automation-id> \
@@ -59,6 +65,7 @@ ae-cli agent +update-automation --dry-run --id <automation-id> --enabled false
 | `--name` | No | New automation task name |
 | `--message` | No | New instruction sent to the Agent |
 | `--enabled` | No | `true` to enable, `false` to pause |
+| `--reuse-conversation` | No | `true` to reuse one conversation, `false` to create one per run; omit to keep unchanged |
 | `--cron` | No | Cron expression (mutually exclusive with `--schedule-kind`) |
 | `--schedule-kind` | No | `hourly` \| `daily` \| `weekly` \| `monthly` |
 | `--time` | No | Time in `HH:mm` for daily/weekly/monthly |
@@ -68,12 +75,13 @@ ae-cli agent +update-automation --dry-run --id <automation-id> --enabled false
 
 ## Decision Rules
 - If the user wants to pause/resume, use `--enabled false` / `--enabled true` (no other fields needed).
+- If the user wants future runs to share one conversation, use `--reuse-conversation true`; use `false` to restore one conversation per run.
 - If the user wants to change the schedule, provide `--schedule-kind` with its required time/day fields, or `--cron`.
 - At least one update field is required; a bare `--id` is rejected.
 - Use `--dry-run` first to verify the request shape before executing.
 
 ## Next Steps on Failure
-- `至少提供一个更新字段`: add at least one of `--name` / `--message` / `--enabled` / `--cron` / `--schedule-kind`.
+- `至少提供一个更新字段`: add at least one of `--name` / `--message` / `--enabled` / `--reuse-conversation` / `--cron` / `--schedule-kind`.
 - `必须提供 --cron 或 --schedule-kind`: if schedule detail flags (`--time` / `--minute` / `--weekday` / `--day-of-month`) are present, a `--schedule-kind` (or `--cron`) must accompany them.
 - `--time 格式必须是 HH:mm`: use 24-hour `HH:mm` (e.g. `09:00`).
 

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

@@ -239,6 +239,10 @@ This is the exhaustive command and flag inventory for the analysis skill. Read t
 | `ae-cli tracking check list` | tracking.check.list | read | `--project-id` (number; required) — Numeric project ID. | [check_list.md](check_list.md) |
 | `ae-cli tracking check retry` | tracking.check.retry | write | `--project-id` (number; required) — Numeric project ID.<br>`--uuid` (string; required) — Tracking check task UUID.<br>`--request-id` (string; optional) — Optional caller-supplied cli_<32 lowercase hex> lifecycle ID. ae-cli generates and prints one before dispatch when omitted.<br>`--timeout-seconds` (number; optional) — Optional capability execution timeout in seconds. | [check_retry.md](check_retry.md) |
 | `ae-cli tracking check run` | tracking.check.run | write | `--project-id` (number; required) — Numeric project ID.<br>`--check-scope` (json; required) — Tracking check scope JSON object.<br>`--result-scope` (json; optional) — Optional tracking check result scope JSON object. | [check_run.md](check_run.md) |
+| `ae-cli tracking debug-data list` | tracking.debug_data.list | read | `--project-id` (number; required) — Numeric project ID.<br>`--device-id` (string; required) — Debug device ID reported by the SDK as #device_id.<br>`--start-time` (string; optional) — Query start time in YYYY-MM-DD HH:mm:ss local time. Defaults to one hour ago.<br>`--event-name` (string; optional) — Optional event name filter. | [debug_data_list.md](debug_data_list.md) |
+| `ae-cli tracking debug-device add` | tracking.debug_device.add | write | `--project-id` (number; required) — Numeric project ID.<br>`--device-id` (string; required) — Debug device ID reported by the SDK as #device_id.<br>`--device-name` (string; required) — Human-readable name for the Debug device. | [debug_device_add.md](debug_device_add.md) |
+| `ae-cli tracking debug-device list` | tracking.debug_device.list | read | `--project-id` (number; required) — Numeric project ID. | [debug_device_list.md](debug_device_list.md) |
+| `ae-cli tracking debug-device select` | tracking.debug_device.select | write | `--project-id` (number; required) — Numeric project ID.<br>`--device-id` (string; required) — Debug device ID reported by the SDK as #device_id. | [debug_device_select.md](debug_device_select.md) |
 | `ae-cli tracking event-blacklist add` | tracking.event_blacklist.add | write | `--project-id` (number; required) — Numeric project ID.<br>`--event-names` (json; required) — JSON array of event names. | [event_blacklist_add.md](event_blacklist_add.md) |
 | `ae-cli tracking event-blacklist list` | tracking.event_blacklist.list | read | `--project-id` (number; required) — Numeric project ID. | [event_blacklist_list.md](event_blacklist_list.md) |
 | `ae-cli tracking event-blacklist update` | tracking.event_blacklist.update | write | `--project-id` (number; required) — Numeric project ID.<br>`--event-names` (json; required) — JSON array of event names.<br>`--type` (number; required) — Blacklist event config type: 0 or 1. | [event_blacklist_update.md](event_blacklist_update.md) |
@@ -252,6 +256,7 @@ This is the exhaustive command and flag inventory for the analysis skill. Read t
 | `ae-cli tracking plan get` | tracking.plan.get | read | `--project-id` (number; required) — Numeric project ID. | [plan_get.md](plan_get.md) |
 | `ae-cli tracking plan import-excel` | tracking.plan.import_excel | write | `--project-id` (number; required) — Numeric project ID.<br>`--input-file` (string; optional) — Local tracking-plan XLSX path. The CLI uploads it with purpose track.program.xlsx before import.<br>`--input-file-id` (string; optional) — Existing input_file_id returned by `analysis input-file upload --purpose track.program.xlsx`.<br>`--lang` (string; optional) — Excel language: zh, en, ja, ko, zh_CN, en_US, ja_JP, or ko_KR. | [plan_import_excel.md](plan_import_excel.md) |
 | `ae-cli tracking plan save-items` | tracking.plan.save_items | write | `--project-id` (number; required) — Numeric project ID.<br>`--events` (json; optional) — Optional JSON array of tracking events.<br>`--event-props` (json; optional) — Optional JSON array of tracking event properties.<br>`--user-props` (json; optional) — Optional JSON array of tracking user properties.<br>`--common-event-props` (json; optional) — Optional JSON array of common tracking event properties. | [plan_save_items.md](plan_save_items.md) |
+| `ae-cli tracking plan sync-display-names` | gateway lifecycle | write | `--project-id` (number; required) — Numeric project ID.<br>`--draft` (string; required) — Local tracking-plan draft.json containing event/property display_name values. | [plan_sync_display_names.md](plan_sync_display_names.md) |
 | `ae-cli tracking plan sync-from-meta` | tracking.plan.sync_from_meta | write | `--project-id` (number; required) — Numeric project ID. | [plan_sync_from_meta.md](plan_sync_from_meta.md) |
 | `ae-cli tracking plan-change-log export` | tracking.plan_change_log.export | read | `--project-id` (number; required) — Numeric project ID.<br>`--log-id` (number; required) — Tracking plan change log ID.<br>`--request-id` (string; optional) — Optional caller-supplied cli_<32 lowercase hex> lifecycle ID. ae-cli generates and prints one before dispatch when omitted.<br>`--timeout-seconds` (number; optional, min=1, max=21600) — Async runtime in seconds. Default and max: 21600 (6 hours); cancel earlier with analysis query cancel --run-id <run_id>. | [plan_change_log_export.md](plan_change_log_export.md) |
 | `ae-cli tracking plan-change-log list` | tracking.plan_change_log.list | read | `--project-id` (number; required) — Numeric project ID. | [plan_change_log_list.md](plan_change_log_list.md) |

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

@@ -0,0 +1,28 @@
+# tracking debug-data list
+
+Use this command to query Debug data received from one device and verify an SDK reporting flow.
+
+Command:
+
+```bash
+ae-cli tracking debug-data list \
+  --project-id <project_id> \
+  --device-id <device_id> \
+  --start-time "YYYY-MM-DD HH:mm:ss" \
+  [--event-name <event_name>]
+```
+
+Capability id: `tracking.debug_data.list`.
+
+Input sends `project_id`, `device_id`, `start_time`, and optional `event_name`. When omitted, `start_time` defaults to one hour ago in local time.
+
+The normalized result includes `has_data`, `event_count`, `data_count`, `event_list`, and `device_data_list`. Treat validation as successful only when `has_data` is true and the returned event names, property structures, and error fields are correct.
+
+## Parameters
+
+| Parameter      | Required | Description                                                                |
+| -------------- | -------- | -------------------------------------------------------------------------- |
+| `--project-id` | Yes      | Numeric AE project ID.                                                     |
+| `--device-id`  | Yes      | Debug device ID used by the reporting client.                              |
+| `--start-time` | No       | Query start time in local `YYYY-MM-DD HH:mm:ss`; defaults to one hour ago. |
+| `--event-name` | No       | Exact event name filter.                                                   |

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

@@ -0,0 +1,23 @@
+# tracking debug-device add
+
+Use this command to create or update a Debug device for one AE project.
+Do not use it to select the active device or query Debug data; use `debug-device select` and `debug-data list` for those actions.
+
+Command:
+
+```bash
+ae-cli tracking debug-device add --project-id <project_id> --device-id <device_id> --device-name <device_name>
+```
+
+Capability id: `tracking.debug_device.add`.
+
+Input sends `project_id`, `device_id`, and `device_name`. Prefer a stable device ID that the validation script can reuse. After creation, select the same device with `tracking debug-device select`.
+The result confirms that the device was created or updated; use `debug-device list` to verify the saved device before selecting it.
+
+## Parameters
+
+| Parameter       | Required | Description                                          |
+| --------------- | -------- | ---------------------------------------------------- |
+| `--project-id`  | Yes      | Numeric AE project ID.                               |
+| `--device-id`   | Yes      | Stable Debug device ID used by the reporting client. |
+| `--device-name` | Yes      | Human-readable Debug device name.                    |

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

@@ -0,0 +1,19 @@
+# tracking debug-device list
+
+Use this command to list Debug devices for one AE project and identify the device selected by the current CLI user.
+
+Command:
+
+```bash
+ae-cli tracking debug-device list --project-id <project_id>
+```
+
+Capability id: `tracking.debug_device.list`.
+
+Input sends `project_id`. The result contains the available Debug devices and current selection. Use the returned device IDs for `debug-device select` and `debug-data list`; do not invent an ID.
+
+## Parameters
+
+| Parameter      | Required | Description            |
+| -------------- | -------- | ---------------------- |
+| `--project-id` | Yes      | Numeric AE project ID. |

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

@@ -0,0 +1,22 @@
+# tracking debug-device select
+
+Use this command to select the active Debug device for the current CLI user.
+Do not use it to create a missing device or retrieve Debug events.
+
+Command:
+
+```bash
+ae-cli tracking debug-device select --project-id <project_id> --device-id <device_id>
+```
+
+Capability id: `tracking.debug_device.select`.
+
+Input sends `project_id` and `device_id`. The device must come from `tracking debug-device list` or a successful `tracking debug-device add`.
+The result confirms the selected device; follow it with `debug-data list` only after the reporting client has sent Debug data with the same ID.
+
+## Parameters
+
+| Parameter      | Required | Description                         |
+| -------------- | -------- | ----------------------------------- |
+| `--project-id` | Yes      | Numeric AE project ID.              |
+| `--device-id`  | Yes      | Existing Debug device ID to select. |

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

@@ -0,0 +1,28 @@
+# tracking plan sync-display-names
+
+Use this local orchestration command after uploading a tracking plan, and rerun it after the first Debug or production data arrives.
+Do not use it to rename metadata that already has a display name, create missing metadata, or replace the tracking-plan upload flow.
+
+Command:
+
+```bash
+ae-cli tracking plan sync-display-names \
+  --project-id <project_id> \
+  --draft <draft.json>
+```
+
+The command reads localized `display_name` values from the local tracking-plan draft, lists the project's event, event-property, and user-property metadata, then calls `metadata.super_metadata.batch_edit` in bounded batches.
+
+Safety and result rules:
+
+- Only blank metadata display names are filled.
+- Existing non-empty AE display names are never overwritten.
+- `missing_in_metadata` means an event/property has not appeared in project metadata yet; rerun after data arrives.
+- `missing_display_name_in_draft` means the draft is incomplete; add the localized display name, regenerate and validate the xlsx, then retry.
+
+## Parameters
+
+| Parameter      | Required | Description                                                                       |
+| -------------- | -------- | --------------------------------------------------------------------------------- |
+| `--project-id` | Yes      | Numeric AE project ID.                                                            |
+| `--draft`      | Yes      | Local tracking-plan `draft.json` containing event/property `display_name` values. |

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

@@ -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)
 
@@ -256,7 +258,7 @@ Without `.ae-cli/draft.json` or `.ae-cli/remote-plan.json`:
 **SDK document paths**:
 - Do not use hard-coded wiki paths from this section.
 - Always read `references/sdk-index.md` first and use the path listed there for the selected SDK.
-- If the path from `references/sdk-index.md` does not exist in the local wiki mirror, search under `~/.ae-cli/wiki/te-docs/raw/` with SDK-specific keywords and use the best matching latest main document.
+- If the path from `references/sdk-index.md` does not exist in the local wiki mirror, search under `~/.ae-cli/wiki/raw/` with SDK-specific keywords and use the best matching latest main document.
 
 ---
 
@@ -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
@@ -669,14 +685,14 @@ All output mode rules are in `references/*.md`. This SKILL.md only handles phase
 - User guide: https://docs-v2.thinkingdata.cn/?version=latest&code=logbus2_installation&lan=en-US
 - Download link is in the official doc's "二、Download LogBus2" section
 
-**Wiki directory structure** (see `~/.ae-cli/wiki/te-docs/schema.md`):
-- `~/.ae-cli/wiki/te-docs/raw/` — AE official documentation mirror (read-only, maintained by crawler)
-- `~/.ae-cli/wiki/te-docs/synthesis/` — LLM-synthesized overview documents
+**Wiki directory structure** (see `~/.ae-cli/wiki/schema.md`):
+- `~/.ae-cli/wiki/raw/` — AE official documentation mirror (read-only, maintained by crawler)
+- `~/.ae-cli/wiki/synthesis/` — LLM-synthesized overview documents
 
 **Document reading order during code generation**:
 1. Read `references/sdk-index.md` to find the selected SDK's main document and advanced guide paths.
 2. Verify the main document path exists in the local wiki mirror before reading it.
-3. If the indexed path is missing, search under `~/.ae-cli/wiki/te-docs/raw/` with SDK-specific keywords such as SDK name, platform name, language name, and `main doc`; choose the latest main document, not historical/versioned documents.
+3. If the indexed path is missing, search under `~/.ae-cli/wiki/raw/` with SDK-specific keywords such as SDK name, platform name, language name, and `main doc`; choose the latest main document, not historical/versioned documents.
 4. Read the wiki main doc first (initialization, imports, package names, basic API).
 5. Read the advanced guide only after the main doc (LoggerConsumer, user properties, auto-track, preset properties, etc.).
 6. Check advanced guide sub-documents if needed.

package/skills/ae-generate-tracking-code/references/autotrack-enum.md

@@ -177,7 +177,7 @@ TDAnalytics.enableAutoTrack(context,
 ## Cocos2d-x / CocosCreator / LayaAir / Unreal
 
 游戏引擎 SDK 的自动采集枚举值请直接读取对应 wiki 文档：
-- `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/game-engine/cocos2d-x/cocos2d-x-advanced/automatic-event-tracking.md`
-- `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/game-engine/cocoscreator/cocoscreator-advance/automatic-event-tracking.md`
-- `~/.ae-cli/wiki/te-docs/raw/客户端-sdk/游戏引擎/layaair/进阶指南/自动采集.md`
-- `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/game-engine/unreal/unreal-advanced/automatic-event-tracking.md`
+- `~/.ae-cli/wiki/raw/data-ingestion-guide/client-sdk/game-engine/cocos2d-x/cocos2d-x-advanced/automatic-event-tracking.md`
+- `~/.ae-cli/wiki/raw/data-ingestion-guide/client-sdk/game-engine/cocoscreator/cocoscreator-advance/automatic-event-tracking.md`
+- `~/.ae-cli/wiki/raw/客户端-sdk/游戏引擎/layaair/进阶指南/自动采集.md`
+- `~/.ae-cli/wiki/raw/data-ingestion-guide/client-sdk/game-engine/unreal/unreal-advanced/automatic-event-tracking.md`

package/skills/ae-generate-tracking-code/references/client-sdk-insert.md

@@ -16,7 +16,7 @@
 3. Choose integration method based on project characteristics:
    - Has `package.json` + build tool → npm integration
    - Plain HTML / no build tool → CDN method
-4. Read `~/.ae-cli/wiki/te-docs/synthesis/sdk-selection.md` to confirm appType's npm package name and init signature
+4. Read `~/.ae-cli/wiki/synthesis/sdk-selection.md` to confirm appType's npm package name and init signature
 5. Read the corresponding cheatsheet (e.g. `js-sdk-cheatsheet.md`) for additional details
 
 **⚠️ Prohibited**: Skipping Stage 0 and writing code directly, guessing integration methods, using unverified CDN URLs