@thinkingai/ae-cli 6.0.31 → 6.0.33

package/dist/{te-meta-MAAUHFQO.js → te-meta-VHCN4Q62.js}

@@ -2,12 +2,13 @@ import {
   callMcpTool,
   parseMcpResult,
   resolveMcpUrl
-} from "./chunk-PKRD2IEM.js";
-import "./chunk-KGJQCYVC.js";
-import "./chunk-NOO24N7W.js";
-import "./chunk-2NDGFQHW.js";
-import "./chunk-AJTH7LT3.js";
-import "./chunk-YCLVYFK7.js";
+} from "./chunk-3P3562ZX.js";
+import "./chunk-LCXU3AAT.js";
+import "./chunk-E7UXXHO3.js";
+import "./chunk-IR4ZLVPW.js";
+import "./chunk-V6FR6WTW.js";
+import "./chunk-24BAVOX3.js";
+import "./chunk-LYVNONC4.js";
 
 // src/commands/te-meta/shared.ts
 function createMcpCommand(config) {
@@ -42,72 +43,14 @@ function optionalNumber(ctx, name) {
   const value = ctx.str(name);
   return value === "" ? void 0 : Number(value);
 }
-function optionalBoolean(ctx, name) {
-  const value = ctx.str(name);
-  return value === "" ? void 0 : ctx.bool(name);
-}
 function optionalJson(ctx, name) {
   const value = ctx.str(name);
   return value === "" ? void 0 : ctx.json(name);
 }
-function optionalJsonString(ctx, name) {
-  const value = optionalJson(ctx, name);
-  return value === void 0 ? void 0 : JSON.stringify(value);
-}
 function requiredJsonString(ctx, name) {
   return JSON.stringify(ctx.json(name));
 }
 
-// src/commands/te-meta/meta/list-events.ts
-var listEvents = createMcpCommand({
-  command: "+list_events",
-  description: "List events in the project. Use for explicit metadata inspection, not as a pre-step for event/retention/funnel/prop_analysis ad-hoc builders; the builders resolve event names internally. Query performs fuzzy matching on eventName, eventDesc, and remark. Supports authenticated asset filtering plus fields/limit/offset payload governance. Default returned fields: eventId, eventName, eventDesc, remark, authenticationStatus.",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "query", type: "string", required: false, desc: "Optional keyword filter. Fuzzy match is applied to eventName, eventDesc, and remark; if omitted, all events are returned.", alias: "q" },
-    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported fields: eventId, eventName, eventDesc, remark, eventTag, authenticationStatus. Default fields when omitted: eventId, eventName, eventDesc, remark, authenticationStatus.", alias: "f" },
-    { name: "limit", type: "number", required: false, desc: "Optional page size. Default: 50, maximum: 200.", alias: "l", min: 1, max: 200 },
-    { name: "offset", type: "number", required: false, desc: "Optional page offset. Default: 0.", alias: "o" },
-    { name: "authenticated_only", type: "boolean", required: false, desc: "When true, return only authenticated events." }
-  ],
-  risk: "read",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    query: optionalString(ctx, "query"),
-    fields: optionalJson(ctx, "fields"),
-    limit: optionalNumber(ctx, "limit"),
-    offset: optionalNumber(ctx, "offset"),
-    authenticatedOnly: optionalBoolean(ctx, "authenticated_only")
-  })
-});
-
-// src/commands/te-meta/meta/list-properties.ts
-var listProperties = createMcpCommand({
-  command: "+list_properties",
-  description: "List properties in the project. Use for explicit metadata inspection, not as a pre-step for event/retention/funnel/prop_analysis ad-hoc builders; the builders resolve property names internally. Query performs fuzzy matching on propName, propDesc, and remark. Supports authenticated asset filtering plus fields/limit/offset payload governance. Default returned fields: propId, propName, propDesc, remark, selectType, tableType, authenticationStatus.",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "scope", type: "string", required: false, desc: "Property scope: event or user" },
-    { name: "event_name", type: "string", required: false, desc: "Optional event name filter" },
-    { name: "query", type: "string", required: false, desc: "Optional keyword filter. Fuzzy match is applied to propName, propDesc, and remark; if omitted, all accessible properties are returned.", alias: "q" },
-    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported fields: propId, propName, propDesc, remark, selectType, tableType, subTableType, authenticationStatus. Default fields when omitted: propId, propName, propDesc, remark, selectType, tableType, authenticationStatus.", alias: "f" },
-    { name: "limit", type: "number", required: false, desc: "Optional page size. Default: 50, maximum: 200.", alias: "l", min: 1, max: 200 },
-    { name: "offset", type: "number", required: false, desc: "Optional page offset. Default: 0.", alias: "o" },
-    { name: "authenticated_only", type: "boolean", required: false, desc: "When true, return only authenticated properties." }
-  ],
-  risk: "read",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    scope: optionalString(ctx, "scope"),
-    eventName: optionalString(ctx, "event_name"),
-    query: optionalString(ctx, "query"),
-    fields: optionalJson(ctx, "fields"),
-    limit: optionalNumber(ctx, "limit"),
-    offset: optionalNumber(ctx, "offset"),
-    authenticatedOnly: optionalBoolean(ctx, "authenticated_only")
-  })
-});
-
 // src/commands/te-meta/meta/batch-edit-metadata.ts
 var batchEditMetadata = createMcpCommand({
   command: "+batch_edit_metadata",
@@ -146,185 +89,10 @@ var batchCreateMetadata = createMcpCommand({
   })
 });
 
-// src/commands/te-meta/meta/create-virtual-event.ts
-var createVirtualEvent = createMcpCommand({
-  command: "+create_virtual_event",
-  description: "Create a virtual event by combining multiple events with optional filters",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "event_name", type: "string", required: true, desc: "Virtual event name. Must start with 'ta@' and follow the naming constraints in the schema" },
-    { name: "event_desc", type: "string", required: true, desc: "Virtual event description" },
-    { name: "remark", type: "string", required: false, desc: "Optional remark" },
-    { name: "events", type: "json", required: true, desc: "JSON array of events to combine" },
-    { name: "filter", type: "json", required: false, desc: "Optional global filter JSON" },
-    { name: "override", type: "boolean", required: false, desc: "Whether to override if the event already exists. Default: false" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    eventName: ctx.str("event_name"),
-    eventDesc: ctx.str("event_desc"),
-    remark: optionalString(ctx, "remark"),
-    events: requiredJsonString(ctx, "events"),
-    filter: optionalJsonString(ctx, "filter"),
-    override: optionalBoolean(ctx, "override")
-  })
-});
-
-// src/commands/te-meta/meta/create-virtual-property.ts
-var createVirtualProperty = createMcpCommand({
-  command: "+create_virtual_property",
-  description: "Create a SQL-based virtual property",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "property_name", type: "string", required: true, desc: "Property name. Must start with '#vp@' and follow the naming constraints in the schema" },
-    { name: "property_desc", type: "string", required: false, desc: "Display name/description" },
-    { name: "table_type", type: "string", required: true, desc: "Table type: event or user" },
-    { name: "select_type", type: "string", required: true, desc: "Select type: string, number, bool, or datetime" },
-    { name: "sql_expression", type: "string", required: true, desc: "SQL expression for computing the property" },
-    { name: "sql_event_relation_type", type: "string", required: true, desc: "SQL event relation type: relation_default, relation_always, or relation_by_setting" },
-    { name: "related_events", type: "json", required: false, desc: "Optional related events JSON array. Required when sql_event_relation_type is relation_by_setting" },
-    { name: "property_remark", type: "string", required: false, desc: "Optional property remark" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    propertyName: ctx.str("property_name"),
-    propertyDesc: optionalString(ctx, "property_desc"),
-    tableType: ctx.str("table_type"),
-    selectType: ctx.str("select_type"),
-    sqlExpression: ctx.str("sql_expression"),
-    sqlEventRelationType: ctx.str("sql_event_relation_type"),
-    relatedEvents: optionalJsonString(ctx, "related_events"),
-    propertyRemark: optionalString(ctx, "property_remark")
-  })
-});
-
-// src/commands/te-meta/meta/list-metrics.ts
-var listMetrics = createMcpCommand({
-  command: "+list_metrics",
-  description: "List metric metadata in the project. Use for metric metadata inspection/management. For AI-facing analysis definitions, reference saved metrics by verified metric name in the analysis definition instead of calling old QP builders. Query performs fuzzy matching on metricName, metricDesc, and metricRemark. Supports authenticated asset filtering plus fields/limit/offset pagination. Default returned fields: metricId, metricName, metricDesc, metricRemark, metricMode, authenticationStatus.",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "query", type: "string", required: false, alias: "q", desc: "Optional keyword filter. Fuzzy match on metricName, metricDesc, metricRemark." },
-    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported: metricId, metricName, metricDesc, metricRemark, metricMode, authenticationStatus, openId, creator, creatorLoginName, updateOpenId, updateCreator, updateLoginName, createTime, updateTime. Default fields when omitted: metricId, metricName, metricDesc, metricRemark, metricMode, authenticationStatus." },
-    { name: "limit", type: "number", required: false, desc: "Optional limit. Default: 50, maximum: 200.", min: 1, max: 200 },
-    { name: "offset", type: "number", required: false, desc: "Optional offset. Default: 0." },
-    { name: "authenticated_only", type: "boolean", required: false, desc: "When true, return only authenticated metrics." }
-  ],
-  risk: "read",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    query: optionalString(ctx, "query"),
-    fields: optionalJson(ctx, "fields"),
-    limit: optionalNumber(ctx, "limit"),
-    offset: optionalNumber(ctx, "offset"),
-    authenticatedOnly: optionalBoolean(ctx, "authenticated_only")
-  })
-});
-
-// src/commands/te-meta/meta/get-metric.ts
-var getMetric = createMcpCommand({
-  command: "+get_metric",
-  description: "Get the definition details of a single metric. Use for metric metadata inspection/management. For AI-facing analysis definitions, reference saved metrics by verified metric name instead of calling old QP builders.",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "metric_id", type: "number", required: true, alias: "m", desc: "Metric ID" }
-  ],
-  risk: "read",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    metricId: ctx.num("metric_id")
-  })
-});
-
-// src/commands/te-meta/meta/create-metric.ts
-var createMetric = createMcpCommand({
-  command: "+create_metric",
-  description: "Create a metric from analysis configuration",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "name", type: "string", required: true, desc: "Metric name. Must start with a lowercase letter and contain only lowercase letters, digits, and underscores. Maximum length: 80." },
-    { name: "display_name", type: "string", required: true, desc: "Metric display name" },
-    { name: "remark", type: "string", required: false, desc: "Optional metric remark" },
-    { name: "model_type", type: "string", required: true, desc: "Metric model type: event or retention" },
-    { name: "events", type: "json", required: true, desc: "Metric events JSON. Follow the create_metric reference for the metric event contract." },
-    { name: "params", type: "json", required: true, desc: "Metric parameters JSON. For event, use format config; for retention, use the eventView configuration." }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    name: ctx.str("name"),
-    displayName: ctx.str("display_name"),
-    remark: optionalString(ctx, "remark"),
-    modelType: ctx.str("model_type"),
-    events: requiredJsonString(ctx, "events"),
-    params: requiredJsonString(ctx, "params")
-  })
-});
-
-// src/commands/te-meta/meta/update-metric.ts
-var updateMetric = createMcpCommand({
-  command: "+update_metric",
-  description: "Update a metric definition",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "metric_id", type: "number", required: true, alias: "m", desc: "Metric ID" },
-    { name: "name", type: "string", required: true, desc: "Metric name. Must start with a lowercase letter and contain only lowercase letters, digits, and underscores. Maximum length: 80." },
-    { name: "display_name", type: "string", required: true, desc: "Metric display name" },
-    { name: "remark", type: "string", required: false, desc: "Optional metric remark" },
-    { name: "model_type", type: "string", required: true, desc: "Metric model type: event or retention" },
-    { name: "events", type: "json", required: true, desc: "Metric event definition JSON" },
-    { name: "params", type: "json", required: false, desc: "Metric parameter definition JSON" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    metricId: ctx.num("metric_id"),
-    name: ctx.str("name"),
-    displayName: ctx.str("display_name"),
-    remark: optionalString(ctx, "remark"),
-    modelType: ctx.str("model_type"),
-    events: requiredJsonString(ctx, "events"),
-    params: optionalJsonString(ctx, "params")
-  })
-});
-
-// src/commands/te-meta/meta/delete-metric.ts
-var deleteMetric = createMcpCommand({
-  command: "+delete_metric",
-  description: "Delete a metric by metricId",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "metric_id", type: "number", required: true, desc: "Metric ID to delete" }
-  ],
-  risk: "high-risk-write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    metricId: ctx.num("metric_id")
-  })
-});
-
 // src/commands/te-meta/meta/index.ts
 var commands = [
-  listEvents,
-  listProperties,
   batchEditMetadata,
-  batchCreateMetadata,
-  createVirtualEvent,
-  createVirtualProperty,
-  listMetrics,
-  getMetric,
-  createMetric,
-  updateMetric,
-  deleteMetric
+  batchCreateMetadata
 ];
 var meta_default = commands;
 

package/dist/{te-team-OKCOX7OE.js → te-team-PDKKW7Q5.js}

@@ -1,15 +1,16 @@
 import {
   getAuthHeaders,
   kbApi
-} from "./chunk-MDJGDI6K.js";
+} from "./chunk-3KI3RRXX.js";
 import {
   printError,
   printOutput
-} from "./chunk-TNW2CI4W.js";
-import "./chunk-NOO24N7W.js";
-import "./chunk-2NDGFQHW.js";
-import "./chunk-AJTH7LT3.js";
-import "./chunk-YCLVYFK7.js";
+} from "./chunk-IMMGMU54.js";
+import "./chunk-E7UXXHO3.js";
+import "./chunk-IR4ZLVPW.js";
+import "./chunk-V6FR6WTW.js";
+import "./chunk-24BAVOX3.js";
+import "./chunk-LYVNONC4.js";
 
 // src/commands/te-team/shared.ts
 var API_PREFIX = process.env.AE_API_PREFIX ?? "/agent";

package/dist/tracking/i18n/resources/cli/en.json

@@ -94,9 +94,10 @@
     "raw_header": "# raw"
   },
   "code": {
-    "inferred_sdk_mode": "[import-xlsx] inferred sdk_integration_mode: {mode}",
-    "default_sdk_mode": "[import-xlsx] sdk_integration_mode: {mode} (default, xlsx has no platform info)",
-    "wrote_events": "[import-xlsx] wrote {count} events to {path}"
+    "inferred_sdk_mode": "[import-template] inferred sdk_integration_mode: {mode}",
+    "default_sdk_mode": "[import-template] sdk_integration_mode: {mode} (default, xlsx has no platform info)",
+    "wrote_events": "[import-template] wrote {count} events to {path}",
+    "xlsx_import_empty_warning": "[import-template] WARNING: No events imported from {path}. The file may not be an AE tracking plan xlsx (missing #-prefixed sheets like #event data)"
   },
   "wiki": {
     "sync_not_supported": "wiki sync: run in a repo checkout with scripts/wiki-plan.ts available;",

package/dist/tracking/i18n/resources/cli/ja.json

@@ -94,9 +94,10 @@
     "raw_header": "# 生データ"
   },
   "code": {
-    "inferred_sdk_mode": "[import-xlsx] sdk_integration_mode を推論: {mode}",
-    "default_sdk_mode": "[import-xlsx] sdk_integration_mode: {mode}（デフォルト、xlsx に platform 情報なし）",
-    "wrote_events": "[import-xlsx] {count} イベントを {path} に書き込みました"
+    "inferred_sdk_mode": "[import-template] sdk_integration_mode を推論: {mode}",
+    "default_sdk_mode": "[import-template] sdk_integration_mode: {mode}（デフォルト、xlsx に platform 情報なし）",
+    "wrote_events": "[import-template] {count} イベントを {path} に書き込みました",
+    "xlsx_import_empty_warning": "[import-template] ⚠️ 警告：{path} からイベントがインポートされませんでした。このファイルはAEトラッキングプランxlsxではない可能性があります（#イベントデータ などの # プレフィックスシートがありません）"
   },
   "wiki": {
     "sync_not_supported": "wiki sync: リポジトリのチェックアウト内で実行してください（scripts/wiki-plan.ts）；",

package/dist/tracking/i18n/resources/cli/ko.json

@@ -94,9 +94,10 @@
     "raw_header": "# 원시 데이터"
   },
   "code": {
-    "inferred_sdk_mode": "[import-xlsx] sdk_integration_mode 추론: {mode}",
-    "default_sdk_mode": "[import-xlsx] sdk_integration_mode: {mode} (기본값, xlsx에 platform 정보 없음)",
-    "wrote_events": "[import-xlsx] {count}개 이벤트를 {path}에 작성했습니다"
+    "inferred_sdk_mode": "[import-template] sdk_integration_mode 추론: {mode}",
+    "default_sdk_mode": "[import-template] sdk_integration_mode: {mode} (기본값, xlsx에 platform 정보 없음)",
+    "wrote_events": "[import-template] {count}개 이벤트를 {path}에 작성했습니다",
+    "xlsx_import_empty_warning": "[import-template] ⚠️ 경고: {path}에서 이벤트를 가져오지 못했습니다. 이 파일은 AE 트래킹 플랜 xlsx가 아닐 수 있습니다 (#이벤트 데이터 등 # 접두사 시트가 없습니다)"
   },
   "wiki": {
     "sync_not_supported": "wiki sync: 리포지토리 체크아웃 내에서 실행하세요 (scripts/wiki-plan.ts);",

package/dist/tracking/i18n/resources/cli/zh.json

@@ -94,9 +94,10 @@
     "raw_header": "# 原始数据"
   },
   "code": {
-    "inferred_sdk_mode": "[import-xlsx] 推断 sdk_integration_mode: {mode}",
-    "default_sdk_mode": "[import-xlsx] sdk_integration_mode: {mode}（默认，xlsx 无 platform 信息）",
-    "wrote_events": "[import-xlsx] 写入 {count} 个事件至 {path}"
+    "inferred_sdk_mode": "[import-template] 推断 sdk_integration_mode: {mode}",
+    "default_sdk_mode": "[import-template] sdk_integration_mode: {mode}（默认，xlsx 无 platform 信息）",
+    "wrote_events": "[import-template] 写入 {count} 个事件至 {path}",
+    "xlsx_import_empty_warning": "[import-template] ⚠️ 警告：未从 {path} 导入到任何事件。该文件可能不是 AE 埋点方案 xlsx（缺少 #事件数据 等带 # 前缀的 sheet）"
   },
   "wiki": {
     "sync_not_supported": "wiki sync: 需要在仓库 checkout 中运行（scripts/wiki-plan.ts）；",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkingai/ae-cli",
-  "version": "6.0.31",
+  "version": "6.0.33",
   "description": "CLI tool for ThinkingAI (AE) analytics platform",
   "type": "module",
   "bin": {
@@ -20,6 +20,7 @@
     "build": "tsup src/index.ts --format esm --outDir dist && node scripts/copy-tracking-assets.mjs",
     "generate:analysis-skill": "tsx scripts/generate-analysis-skill-index.mts",
     "verify:config": "node test/config-commands.test.mjs",
+    "verify:json-utils": "npx tsx tests/json-utils.test.ts",
     "verify:jq-output": "npx tsx test/jq-output.test.mjs",
     "verify:analysis-tools": "tsx scripts/verify-te-analysis-tools.mjs",
     "verify:analysis-skill": "tsx scripts/generate-analysis-skill-index.mts --check",
@@ -30,15 +31,18 @@
     "verify:analysis-cluster-routing": "node scripts/verify-analysis-cluster-routing.mjs",
     "verify:multi-cluster-mode": "node test/multi-cluster-mode.test.mjs",
     "verify:metadata-capability": "npx tsx test/metadata-capability-commands.test.mjs",
+    "verify:community-capability": "node test/community-capability-routing.test.mjs",
+    "verify:community-report": "npx tsx tests/community-report-standard-v5.test.ts && npx tsx tests/community-report-client.test.ts && npx tsx tests/community-report-framework.test.ts && npx tsx tests/community-data-report-command.test.ts && node test/community-data-report-skill.test.mjs",
     "verify:engage-capability": "tsx test/engage/engage-capability-command.test.mjs && node test/engage/engage-skill-capability.test.mjs",
     "verify:retired-analysis-commands": "node --test test/retired-analysis-commands.test.mjs",
     "verify:analysis-meta-tools": "node scripts/verify-te-meta-tools.mjs",
     "verify:analysis-common-tools": "node scripts/verify-te-common-tools.mjs",
     "verify:team-tools": "node scripts/verify-te-team-tools.mjs",
     "verify:agent-tools": "node scripts/verify-agent-tools.mjs",
-    "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 && node test/tracking-skill-flow.test.mjs && node test/tracking-commands.test.mjs",
     "verify:self-check-overlay": "node test/self-check-overlay.test.mjs",
     "verify:update-check": "npx tsx test/update-check.test.mjs",
+    "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",

package/skills/ae-agent/SKILL.md

@@ -47,8 +47,9 @@ ae-cli agent +create-automation --help
 
 ### Output and Errors
 
-- Successful commands return machine-readable JSON by default. Use `--format table` when a table is easier to scan.
+- Successful commands return machine-readable JSON by default. Use `--format table` when a table is easier to scan. Envelope may include optional `_notice.host_compat`.
 - Failed commands return `{ "ok": false, "error": { "type": "...", "message": "...", "hint": "..." } }` and exit non-zero.
+- **CRITICAL — Host compat (do this first):** After each `ae-cli` run, check stderr and `_notice.host_compat`. If either is present, open the user reply with a short ⚠️ version warning and **quote the `npm i -g` / `npx skills add` (or update-cluster) lines verbatim**, then present the business result. Soft tip; `ok: true` can still carry the notice.
 
 ## When to Use
 

package/skills/ae-analysis/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ae-analysis
-version: 4.0.2
-description: "Use ae-cli for AE/TE analysis-side data questions and asset operations: reports, dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata, project configuration, tracking plans, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, or inspect/create/update analysis assets."
+version: 4.0.3
+description: "Use ae-cli for AE/TE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata, project configuration, tracking plans, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, or inspect/create/update/govern analysis assets."
 ---
 
 # ae-analysis
@@ -12,7 +12,7 @@ This is the single entry skill for analysis intent and command execution.
 
 1. If the command family is already known, open its dedicated reference directly. Otherwise search only the matching row in [`references/command_index.md`](references/command_index.md) (for example with `rg`); do not read the exhaustive index end to end.
 2. Read the selected command's dedicated reference before composing it:
-   - `+list_events` -> `references/list_events.md`
+   - `event list` -> `references/event_list.md`
    - `analysis dashboard list` -> `references/dashboard_list.md`
    - replace hyphens with underscores in gateway filenames.
 3. For an AI-facing ad-hoc definition, also read [`references/ai_models.md`](references/ai_models.md).
@@ -27,8 +27,10 @@ Use this skill for these CLI services:
 
 - `analysis`: reports, dashboards, BI panels, ad-hoc analysis, drilldown, detail data, alerts, clusters, tags, and async runs/artifacts.
 - `analysis-meta`: gateway metadata assets, events, properties, virtual metadata, metrics, data tables, exchange rules, and super metadata.
+- `analysis-governance`: gateway asset governance operations, including governed asset lists/exports, lineage, dependency, impact, query history, rule schema/list/create/update/delete, batch asset actions, and operation records. Use this service for asset governance workflows, not for metadata event/property/metric CRUD.
+- `tracking`: gateway tracking plan, checking, ingest, live-data, and event blacklist operations. Some legacy tracking commands still exist under the same service; prefer the dedicated reference for the exact command form.
 - `analysis_meta`: metadata governance, metrics, virtual metadata, project config, tracking plans, mark times, and entity catalog.
-- `analysis_common`: project discovery and resource links.
+- `analysis_common`: project discovery.
 
 For metadata gateway detail outside the commands in the generated index, use the metadata skill. For Engage, DataOps, or Community work, use the corresponding skill.
 
@@ -46,6 +48,8 @@ ae-cli analysis_meta +<command> [options]
 ae-cli analysis_common +<command> [options]
 ae-cli analysis <resource> <action> [options]
 ae-cli analysis-meta <resource> <action> [options]
+ae-cli analysis-governance <resource> <action> [options]
+ae-cli tracking <resource> <action> [options]
 ae-cli capability search|inspect|validate|dry-run|run [options]
 ```
 
@@ -54,6 +58,7 @@ ae-cli capability search|inspect|validate|dry-run|run [options]
 - JSON values must be JSON string literals.
 - Global flags include `--host`, `--format json|table`, `--jq`, `--validate`, `--dry-run`, and `--yes`. Use `--validate` alone to normalize complex capability input; use `--dry-run` alone for execution or risk preview.
 - JSON is the default machine-readable output. On failure, preserve the structured error and non-zero exit.
+- **CRITICAL — Host compat (do this first):** After each `ae-cli` run, check stderr and `_notice.host_compat`. If either is present, your reply **MUST open with** a short ⚠️ version warning and **quote the `npm i -g` / `npx skills add` (or update-cluster) lines verbatim**, then present the business result. Never answer with only a project/table summary when a host_compat notice exists. Soft tip; `ok: true` can still carry the notice.
 - Never invent command names, flags, payload fields, projects, resource IDs, asset names, event/property names, metric definitions, or dates.
 - 中文时间表达必须按固定语义映射：最近7天/近7天 -> `mode=recent` -> QP `recentDay=0-7`，含今天；过去7天/前7天 -> `mode=previous` -> QP `recentDay=1-7`，不含今天。用户明确说明是否包含今天时，以该说明为准。完整映射见 [`references/ai_models.md`](references/ai_models.md)。
 
@@ -78,6 +83,14 @@ For every gateway command that exposes `--request-id`, ae-cli generates a `reque
 
 ## Mandatory routing
 
+### Product terminology gate
+
+- The Chinese product term `看板` means an analysis board backed by saved reports. Route it to `ae-cli analysis dashboard ...` and capability IDs under `analysis.dashboard.*`.
+- The Chinese product terms `仪表盘` and `BI 仪表盘` mean a BI dashboard with worksheets, charts, and pages. Route them to `ae-cli analysis bi-panel ...` and capability IDs under `analysis.bi_panel.*`.
+- These assets are not aliases. Never substitute an analysis board for a BI dashboard, or a BI dashboard for an analysis board.
+- The standalone English word `dashboard` is ambiguous in this product. Before a write, ask whether the user means an analysis board (`看板`) or a BI dashboard (`仪表盘`) unless the surrounding context already makes the product asset explicit.
+- If the requested BI-panel capability is unavailable or unauthorized, report that constraint. Do not fall back to creating an analysis board.
+
 ### Project gate
 
 Before a project-scoped command:
@@ -110,7 +123,7 @@ Do not call removed QP builders or schema helpers for ad-hoc analysis. `--defini
 - Metric value, trend, comparison, or anomaly -> saved report/dashboard first, then ad-hoc data.
 - Metric definition search/create/update -> metadata commands.
 - Event/entity rows -> `event-detail run|export` or `entity-detail run|export`.
-- User members from a query result -> follow the returned `query_context_id` and `sources[].target_contract`; never reconstruct raw QP.
+- Events/entities from a query result -> follow the returned synchronous `query_context_id` and `sources[].drilldown`; never reconstruct raw QP or use export rows as coordinates.
 - Cluster/tag definition -> matching gateway cluster/tag commands and matching model reference.
 - Alert/configuration/tracking-plan requests -> dedicated legacy command reference from the index.
 
@@ -118,8 +131,9 @@ Do not call removed QP builders or schema helpers for ad-hoc analysis. `--defini
 
 - `run` is a bounded inline preview for known-small work that can complete within the synchronous limits.
 - `export` is for complete, unknown-size, over-limit, or long-running results. It returns `run_id` and `artifact_id`.
+- Drilldown event/entity/user-event exports are `csv.gz` full-download streams bounded by `model_full_download_limit`; never pass or simulate `limit`, `offset`, `page_num`, or `page_size`.
 - Inspect with `analysis run inspect`, download with `analysis artifact download`, and cancel with `analysis query cancel`. Do not call raw lifecycle URLs.
-- Drilldown requires the context IDs and target contracts returned by a supported data result. If they are absent, report that drilldown/result-cluster creation is unavailable.
+- Drilldown requires a synchronous preview context and the selected source's returned row/column/metric coordinate options. If they are absent or the action is not advertised, report that drilldown/result-cluster creation is unavailable.
 
 ### Writes and destructive operations
 
@@ -127,7 +141,7 @@ Write only with explicit user intent. Use `--validate` alone while correcting co
 
 Project-space and folder create/delete/share are L3 capabilities rather than curated `analysis` commands. Read the matching command reference, then use `ae-cli capability inspect|dry-run|run`; discover `*.members` through `capability search|inspect|run` and [`references/analysis_gateway_assets.md`](references/analysis_gateway_assets.md). For `risk=high-risk-write`, dry-run first, summarize the impact, and execute with `--yes` only after a later explicit confirmation.
 
-After a successful create/update, if a resource ID and supported resource type are available, call `analysis_common +get_resource_url` and return the link. Explicitly state when link generation is skipped because no resource ID exists or when it fails.
+After a successful create/update, if a resource ID and supported resource type are available, call `analysis-meta asset url-get` and return the link. Explicitly state when link generation is skipped because no resource ID exists or when it fails.
 
 ## Analysis workflow
 

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

@@ -23,7 +23,7 @@ ae-cli analysis adhoc export \
 
 Read [`ai_models.md`](ai_models.md) for the single 12-model `model_type` registry, AI-facing `definition`, and SQL dynamic params contract.
 
-For SQL model definitions, do not invent table or column names. If the table is unknown, call `analysis sql-table list --project-id <project_id>`; then inspect the selected `table_ref` with `analysis sql-table columns --project-id <project_id> --table-ref <table_ref>` before writing SQL.
+For SQL model definitions, do not invent table or column names. If the table reference is known, inspect columns with `analysis-meta datatable columns-get`; if the table is unknown, ask for it instead of guessing.
 
 ## Definition contract
 
@@ -42,6 +42,8 @@ Async export has no inline row limit. Runtime defaults to and is capped at 21600
 
 Do not use raw QP, `events`, `event_view`, `visual_view`, removed ad-hoc QP builder outputs, or schema helper outputs as `--definition`.
 
+Timezone contract: fixed `--zone-offset` values are integers from `-12` through `14`. Use `--zone-offset 99` for local-time mode, which analyzes timestamps as stored local time without applying a fixed UTC offset conversion; it does not mean UTC+99. Omit the flag to use the project's analysis default.
+
 ## Output
 
 The response is an async artifact descriptor:
@@ -49,12 +51,9 @@ The response is an async artifact descriptor:
 - `run_id`: poll or cancel this run.
 - `artifact_id`: download this artifact after completion.
 - `status` / `artifact_status`: initial lifecycle states.
-- `format`: actual logical artifact format (`jsonl` or `csv`).
-- `compression` / `content_encoding`: actual compression/encoding; analysis ad-hoc exports currently return `gzip`.
-- `file_name` / `content_type`: actual downloadable file contract. Do not infer compression from `--artifact-format` alone.
 - `expires_at` / `expires_at_iso`: artifact expiration.
 - `effective_timeout_seconds`, `timeout_source`, `deadline_at`: effective lifecycle policy.
-- `query_context_id` / `query_context_expires_at`: reusable follow-up context when Redis context creation succeeds.
+- Export descriptors contain lifecycle/artifact metadata only. They do not create `query_context_id` or selectable drilldown options.
 
 Preserve the `run_id` and `artifact_id` from this exact submit response as one pair. Do not infer either ID from a path or reuse an ID from another export.
 
@@ -68,4 +67,4 @@ ae-cli analysis query cancel --run-id <run_id>
 
 If query execution fails, `run inspect` reaches `FAILED`; it must not produce a completed empty artifact. Download only after the successful terminal states documented in `analysis_data_retrieval.md`.
 
-Use the submit response `query_context_id` immediately with `analysis drilldown-users run` or `analysis query create-result-cluster` when present. JSONL artifacts repeat query context plus `format`, `compression`, `content_type`, and `content_encoding` in the first metadata line. Source metadata includes `effective_time_range`, `time_range_adjustments`, and `clipping_reasons`. Date rows expose stable `drilldown_date` and separate `display_date`; copy only `drilldown_date` into a drilldown target. CSV remains pure CSV and carries context/format metadata only in the submit and run-inspect descriptors. Do not pass raw QP.
+Exported rows are durable data, not interactive preview coordinates. Never drill down or create a result cluster from the submit response or downloaded artifact. Run a bounded synchronous preview containing the desired cell first.

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

@@ -25,7 +25,7 @@ ae-cli analysis adhoc run \
 
 Read [`ai_models.md`](ai_models.md) for the single 12-model `model_type` registry, AI-facing `definition`, and SQL dynamic params contract.
 
-For SQL model definitions, do not invent table or column names. If the table is unknown, call `analysis sql-table list --project-id <project_id>`; then inspect the selected `table_ref` with `analysis sql-table columns --project-id <project_id> --table-ref <table_ref>` before writing SQL.
+For SQL model definitions, do not invent table or column names. If the table reference is known, inspect columns with `analysis-meta datatable columns-get`; if the table is unknown, ask for it instead of guessing.
 
 ## Input
 
@@ -33,26 +33,24 @@ For SQL model definitions, do not invent table or column names. If the table is
 - `--model-type`: one of the 12 AI-facing model names from [`ai_models.md`](ai_models.md). Do not pass `scenario`, `history_tag`, or `cluster`; tags and cohorts/clusters are separate capabilities.
 - `--definition`: model-specific AI-facing definition JSON.
 
-Control defaults: `--limit` default 100 / max 1000, `--timeout-seconds` default 120 / max 180. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+Control defaults: `--limit` default 100 / max 1000, `--timeout-seconds` default 60 / max 180. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
 
 If the user asks for more than 1000 rows, or the SQL text requests `LIMIT 2000` (or any limit above 1000), go directly to `analysis adhoc export`. Do not lower the SQL limit to 1000, run a truncated sync query first, or loop over repeated `run` calls.
 
 Do not use raw QP, `events`, `event_view`, `visual_view`, removed ad-hoc QP builder outputs, or schema helper outputs as `--definition`.
 
+Timezone contract: fixed `--zone-offset` values are integers from `-12` through `14`. Use `--zone-offset 99` for local-time mode, which analyzes timestamps as stored local time without applying a fixed UTC offset conversion; it does not mean UTC+99. Omit the flag to use the project's analysis default.
+
 ## Output
 
 The response may include:
 
-- `query_context_id`: Redis-backed context for drilldown or result-cluster creation.
-- `drilldown_available`: whether the response contains a complete machine-readable follow-up target. When false, read `drilldown_unavailable_reason` and do not infer a target from display text.
-- `sources[].target_contract.default_target`: a complete target that can be passed directly to a follow-up command. Copy and replace only fields named by `copy_from_selected_result` when drilling into a different row or cell.
+- `query_context_id`: Redis-backed context for follow-ups from this bounded synchronous preview.
+- `sources[].drilldown`: finite row, column, and metric options plus allowed actions. The preview `limit` is the selection boundary.
 - `title` / `rows` / `total` / `returned_rows` / `truncated`: tabular preview fields. When truncated, use `adhoc export`; there is no next-page request.
 - `result`: direct result for non-tabular models.
 - `request_id`: lifecycle request id.
-- `effective_time_range`: the resolved query scope actually sent to execution. `clipping_reasons` is empty when the gateway applied no range cap.
-- `data_time_range`: the minimum/maximum machine dates present in returned rows when available. Compare it with `effective_time_range` to distinguish query-range clipping from missing data.
-- `row_metadata`: row-aligned machine fields. For date-drilldown rows, copy `drilldown_date`; `display_date` is presentation text only.
 
 Execution failures are returned as command failures with `request_id`; only the explicit project-no-data condition is a successful empty result. Do not interpret an empty object as evidence that a failed query succeeded.
 
-Use `query_context_id` with `analysis drilldown-users run` or `analysis query create-result-cluster` only when `drilldown_available=true` and the selected source includes `target_contract.default_target`. Do not pass raw QP or infer a target from display text.
+Read [`analysis_drilldown_contract.md`](analysis_drilldown_contract.md). Use the context only with an action advertised by the selected source/metric, and assemble the coordinate only from returned option fragments. Do not pass raw QP or infer a coordinate from display text.