@thinkingai/ae-cli 6.1.23 → 6.1.24

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkingai/ae-cli",
-  "version": "6.1.23",
+  "version": "6.1.24",
   "description": "CLI tool for ThinkingAI (AE) analytics platform",
   "type": "module",
   "bin": {

package/skills/ae-analysis/SKILL.md

@@ -67,7 +67,7 @@ Report review details must explain calculation logic and statistical measures, n
 
 Scripts may build the transport file, preserve IDs, copy evidence, normalize links, and run deterministic completeness checks. Scripts must not author page-visible `ai_summary.summary`, `analysis_explanation.*.statement`, limitations, open questions, or approval rationale by filling reusable sentence templates. Those fields must be Agent-written interpretation from the current asset/report evidence; if many submitted items share the same narrative shape after only asset names or numbers change, flag a quality failure and follow the bounded correction/warning procedure in `references/agent_review_preflight.md`.
 
-Page-visible review text is for human asset reviewers, not implementers. In `item.ai_summary.summary`, visible statements, and open questions, write plain business Chinese: what the asset is for, how it is calculated, which filters/date windows matter, and what the reviewer should confirm. Saved business event names and field names such as `agent_session_message_send`, `session_id`, and `response_duration` may appear when they help the reviewer verify the 口径. Do not expose internal evidence, parser terms, temporary SQL aliases, or runtime parameter names such as `SAVED_REPORT_ONLY`, `DYNAMIC`, `REPORT`, `T1`, `a0`, `a1`, `Variable2`, `selector3`, `PartDate date1`, `source_path`, `evidence_snapshot`, raw JSON, raw SQL, hash/revision details, dashboard override warnings, timezone-not-saved notes, or claims about query execution unless the user explicitly asks for debug evidence. Convert internal values before display, for example `T1`/`day` becomes `按天`, and dynamic SQL caveats become business confirmation items such as “确认参数含义、默认日期范围和是否包含测试数据”.
+Page-visible review text is for human asset reviewers, not implementers. In `item.ai_summary.summary`, visible statements, and open questions, write plain business Chinese: what the asset is for, how it is calculated, which filters/date windows matter, and what the reviewer should confirm. Use event and property names from the current asset definition when they help the reviewer verify the calculation definition. Do not expose internal evidence, parser terms, temporary SQL aliases, or runtime parameter names such as `SAVED_REPORT_ONLY`, `DYNAMIC`, `REPORT`, `T1`, `a0`, `a1`, `Variable2`, `selector3`, `PartDate date1`, `source_path`, `evidence_snapshot`, raw JSON, raw SQL, hash/revision details, dashboard override warnings, timezone-not-saved notes, or claims about query execution unless the user explicitly asks for debug evidence. Convert internal values before display, for example `T1`/`day` becomes `按天`, and dynamic SQL caveats become business confirmation items such as “确认参数含义、默认日期范围和是否包含测试数据”.
 
 For real review-page submission, start with `analysis-meta governance-recommendation export --limit 20`. This is the initial candidate pool, not a required submission count. Follow the rejection filtering and bounded expansion procedure in `references/governance_recommendation_export.md`: hide each same-definition rejected dashboard's entire display branch, retain shared assets only under other retained dashboards, filter out already completed/authenticated, deferred, or in-flight assets as pending work, and expand an insufficient pool from 20 to 50 to 100, then stop. Expansion is for business-domain coverage, not unlimited workload: for recurring daily batches, target about 20-50 pending review assets, hard cap around 80, and balance roughly 3-6 visible domains with per-domain quotas before adding context. Use the latest successful export as the drafting evidence and report the actual reviewed scope plus overflow left for later batches. Do not compress eligible coverage into a few representative themes or submit only the first work unit unless the user requests a sample or diagnostic batch. Business themes organize the retained dashboard set; they do not replace its coverage. For recurring recommendation jobs, submit only business domains that still contain pending review assets; authenticated assets are supporting context under those visible domains, not standalone work. Do not write long Agent summaries for hidden domains or pure authenticated context.
 

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

@@ -131,7 +131,7 @@ Scripts may build the transport file, preserve IDs, copy evidence, normalize lin
 
 For dashboard, report, and SQL report drafts, write the page-visible explanation with the same intent as the project-KB source file's single `Agent 使用摘要`: business purpose, calculation caliber, input/date/filter meaning, output fields or measures, applicable questions, non-applicable questions, and concrete reviewer confirmations. The review page does not need a second SQL-specific section or a source-code reading note. If the packaged evidence includes SQL, use the SQL only as source material for business interpretation; keep raw SQL, parser output, and unresolved parameter tokens in `evidence_snapshot.analysis`. If a fact is not supported, write the business-facing unknown or confirmation question, for example "确认日期参数默认范围和是否包含测试数据", instead of copying `${PartDate:...}`, `selector3`, `parse_status`, or `DYNAMIC`.
 
-Write all page-visible review text for a business reviewer. `item.ai_summary.summary`, `business_purpose`, `calculations`, `filters`, `time_scope`, `limitations`, `open_questions`, and presentation labels must use plain Chinese that explains purpose, calculation 口径, date/filter choices, and reviewer action. Saved business event names and field names such as `agent_session_message_send`, `session_id`, and `response_duration` may appear when they help the reviewer verify the 口径. While drafting, avoid template copy such as “保存定义摘要”, “审核时需确认口径”, “本草稿不改写 SQL”, “其下报表和依赖元数据已随同提交审核”, or a sentence that only repeats asset name + heat + 未认证. Such copy is a quality finding handled by the bounded correction/warning procedure, not an unconditional dispatch ban. The item reason must answer why this exact asset is worth reviewing now, which saved definition facts support it, and what concrete risk remains. Keep implementation vocabulary out of visible text: do not show `SAVED_REPORT_ONLY`, `DYNAMIC`, `REPORT`, `T1`, temporary SQL aliases such as `a0`/`a1`, runtime parameter names such as `Variable2`/`selector3`/`PartDate date1`, `source_path`, `evidence_snapshot`, raw JSON, raw SQL, projection/select-column jargon, hash/revision values, dashboard-override limitations, timezone-not-saved notes, or “query not proven/executed/returned rows” caveats. Convert them to reviewer decisions only when material: for example `T1`/`day` means `按天`, and dynamic SQL parameter uncertainty becomes “确认参数含义、默认日期范围和是否包含测试数据”.
+Write all page-visible review text for a business reviewer. `item.ai_summary.summary`, `business_purpose`, `calculations`, `filters`, `time_scope`, `limitations`, `open_questions`, and presentation labels must use plain Chinese that explains purpose, calculation 口径, date/filter choices, and reviewer action. Use event and property names from the current asset definition when they help the reviewer verify the calculation definition. While drafting, avoid template copy such as “保存定义摘要”, “审核时需确认口径”, “本草稿不改写 SQL”, “其下报表和依赖元数据已随同提交审核”, or a sentence that only repeats asset name + heat + 未认证. Such copy is a quality finding handled by the bounded correction/warning procedure, not an unconditional dispatch ban. The item reason must answer why this exact asset is worth reviewing now, which saved definition facts support it, and what concrete risk remains. Keep implementation vocabulary out of visible text: do not show `SAVED_REPORT_ONLY`, `DYNAMIC`, `REPORT`, `T1`, temporary SQL aliases such as `a0`/`a1`, runtime parameter names such as `Variable2`/`selector3`/`PartDate date1`, `source_path`, `evidence_snapshot`, raw JSON, raw SQL, projection/select-column jargon, hash/revision values, dashboard-override limitations, timezone-not-saved notes, or “query not proven/executed/returned rows” caveats. Convert them to reviewer decisions only when material: for example `T1`/`day` means `按天`, and dynamic SQL parameter uncertainty becomes “确认参数含义、默认日期范围和是否包含测试数据”.
 
 ## Normal Submission Workflow
 

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

@@ -86,13 +86,13 @@ Tag and cluster result-date policy:
 - `AUTO` dynamically matches the computed result for each analysis date. Use it for historical daily analysis that must evaluate each day against that day's tag or cluster state.
 - `SPECIFIED` uses one fixed result date and requires `specified_cluster_date` in `yyyy-MM-dd` format. Do not send `specified_cluster_date` with `LATEST` or `AUTO`.
 
-For example, the following filter evaluates `tag_pay_level != 非R` against each analysis day's tag result:
+For example, the following filter evaluates `<verified_tag_name> != <excluded_tag_value>` against each analysis day's tag result:
 
 ```json
 {
-  "field": {"name": "tag_pay_level", "type": "tag"},
+  "field": {"name": "<verified_tag_name>", "type": "tag"},
   "operator": "neq",
-  "values": ["非R"],
+  "values": ["<excluded_tag_value>"],
   "cluster_date_policy": "AUTO"
 }
 ```

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

@@ -31,10 +31,10 @@ The KB description is part of Agent auto-loading and source selection, not a cas
 <project_name><asset_scope_label>项目语义知识库，用于辅助 Agent 在分析前召回业务域、资产口径、SQL 报表语义和治理边界。
 ```
 
-For example:
+For example, using a fictional project name:
 
 ```text
-产品雷达已认证资产项目语义知识库，用于辅助 Agent 在分析前召回业务域、资产口径、SQL 报表语义和治理边界。
+示例项目的已认证资产语义知识库，帮助 Agent 在分析前查阅业务域、资产口径、SQL 报表含义和治理边界。
 ```
 
 ```bash

package/skills/ae-analysis/scripts/project-semantic-knowledge-wiki/default-compile-rules.md

@@ -15,7 +15,7 @@ These rules guide Schema generation for project semantic knowledge bases built f
 
 The generated top-level `index.md` must be a decision-oriented navigation page. It may contain only module navigation, common-entry guidance, and a compact category/count overview. Do not append a complete page list, sitemap, individual asset files, metadata property pages, numeric report IDs, numeric dashboard IDs, source container IDs, or raw source filenames to the top-level page. Top-level navigation should link to project overview, business domains, recall cards, asset category indexes, decisions, and review pages. List individual assets only inside the matching asset index page, domain page, dashboard page, source-container page, or search result context. If the compiler wants to expose a full sitemap, put it under `wiki/index.md` or category index pages, never in root `index.md`.
 
-When linking to an individual asset, use its business title as the visible link text and keep the numeric ID only as supporting identity beside the title, for example `近期客户成员聊天数量（report 13270719）`. Do not render bare numeric links such as `13270719` as navigation items.
+When linking to an individual asset, use its business title as the visible link text and keep the numeric ID only as supporting identity beside the title, for example `示例报表（report 1001）`. Do not render bare numeric links such as `1001` as navigation items.
 
 ## Precompiled source contract
 

package/skills/ae-data-integration-helper/references/cpp_server_sdk_faq.md

@@ -72,7 +72,7 @@ unique_ptr<TAConsumer> getDebugConsumer() {
 ```cpp
 //上传事件
 TaSDK::PropertiesNode event_properties;
-event_properties.SetString("name1", "XZ_debug");//上报字符串类型属性
+event_properties.SetString("name1", "example");//上报字符串类型属性
 event_properties.SetNumber("test_number_int", 3);//上报数值类型属性
 event_properties.SetBool("test_bool", true);//上报布尔类型属性
 //上报列表型属性SetList
@@ -82,7 +82,7 @@ list.emplace_back("item21");
 event_properties.SetList("test_list1", list);
 //上报对象类型属性SetObject
 PropertiesNode properties;
-properties.SetString("name2", "logBugs");
+properties.SetString("name2", "example");
 properties.SetString("#uuid", "1234567890");
 properties.SetNumber("test_number_int", 3);
 properties.SetNumber("test_number_double", 3.14);

package/skills/ae-data-integration-helper/references/logbus2_parser_plugin.md

@@ -201,13 +201,13 @@ class ParserServicer(parser_pb2_grpc.ParserServicer):
                 parse_data = json.loads(raw_data_list[1])
                 new_parse_data = {}
                 new_parse_data["properties"] = parse_data.copy()
-                new_parse_data["#account_id"] = parse_data["ACCOUNTID"]
-                new_parse_data["#distinct_id"] = parse_data["OSTYPE"]
+                new_parse_data["#account_id"] = parse_data["user_id"]
+                new_parse_data["#distinct_id"] = parse_data["distinct_id"]
                 new_parse_data["#type"] = "track"
-                new_parse_data["#ip"] = parse_data["IP"]
-                new_parse_data["#uuid"] = parse_data["UID"]
-                new_parse_data["#time"] = parse_data["LOGTM"]
-                new_parse_data["#event_name"] = "event_" + str(parse_data["CODE"])
+                new_parse_data["#ip"] = parse_data["ip"]
+                new_parse_data["#uuid"] = parse_data["event_id"]
+                new_parse_data["#time"] = parse_data["event_time"]
+                new_parse_data["#event_name"] = "event_" + str(parse_data["event_code"])
                 return_data_list.append(json.dumps(new_parse_data))
             except Exception as ve:
                 return_data_list.append('{}')

package/skills/ae-data-integration-helper/references/sdk_log_guide.md

@@ -52,7 +52,7 @@ mode：表示SDK使用的模式
   "#type" : "track",
   "#uuid" : "DB2B97A5-183A-439E-B8B2-FE9AF77D7421",
   "#distinct_id" : "E5ABB02F-EA10-47AC-AB6C-A8E47E55B4E9",
-  "#event_name" : "testA",
+  "#event_name" : "example_event",
   "#time" : "2022-10-25 14:30:29.256"
 }
 ```
@@ -108,7 +108,7 @@ code为0代表上传成功
   "#type" : "track",
   "#uuid" : "0ECCD33B-8076-42A5-BA2B-89DE0773B84B",
   "#distinct_id" : "51C6265F-8F03-461E-91D3-D0FFB11DFCFD_2",
-  "#event_name" : "iOS_001",
+  "#event_name" : "example_event",
   "#time" : "2023-09-05 14:27:44.719"
 }
 ```
@@ -156,7 +156,7 @@ mode：表示SDK使用的模式
         "#type": "track",
         "#time": "2022-10-26 10:56:54.285",
         "#distinct_id": "04af1a3d-56b2-4c8f-a54a-2b6f655b8286",
-        "#event_name": "testA",
+        "#event_name": "example_event",
         ...
     }
 ```
@@ -193,7 +193,7 @@ TDAnalytics.enableLog(true);
         "#type": "track",
         "#time": "2023-09-14 10:09:52.445",
         "#distinct_id": "b86de4eb-12b8-4ce4-924a-54cd12b5fa25",
-        "#event_name": "android_001",
+        "#event_name": "example_event",
         ...
     }
 ```

package/skills/ae-engage/references/add-channel.md

@@ -23,8 +23,8 @@ Create a new Engage **运营设置** push channel (not config-center channels; t
 | `pushIdType` | string | Yes | prefixed property code — **rules differ by channel kind** |
 | `config` | string | Yes | channel config JSON **string** — **shape differs by channel kind** |
 | `enableTouchEvent` | number | Yes | reach funnel: `0` off · `1` on |
-| `eventClickName` | string | Yes when funnel on | click event (e.g. `ops_click`) |
-| `eventDeliveryName` | string | Yes when funnel on | delivery event (e.g. `ops_view`) |
+| `eventClickName` | string | Yes when funnel on | click event (e.g. `click`) |
+| `eventDeliveryName` | string | Yes when funnel on | delivery event (e.g. `delivery`) |
 | `touchEventSource` | string | Yes | usually `custom` for custom event names |
 
 The outer Capability input uses `project_id` and `req`; fields inside `req` keep the native camelCase DTO shape. The Hermes Capability handler assigns the outer `--project-id` to `req.projectId`.
@@ -110,7 +110,7 @@ Do **not** put `client:…` in webhook `userParamsList` unless you have confirme
 
 ```bash
 ae-cli engage-setting channel create --project-id 1 \
-  --req '{"channelType":1,"channelSubBizType":"webhook","channelName":"demo_webhook","pushIdType":"user:#account_id","config":"{\"url\":\"https://example.com/hook\",\"paramsList\":[{\"key\":\"title\",\"keyName\":\"标题\",\"type\":\"STRING\",\"required\":0}],\"userParamsList\":[{\"key\":\"city\",\"columnName\":\"user:city\",\"defaultValue\":\"-\"}],\"authConfig\":{\"enable\":false}}","enableTouchEvent":1,"eventDeliveryName":"ops_view","eventClickName":"ops_click","touchEventSource":"custom"}'
+  --req '{"channelType":1,"channelSubBizType":"webhook","channelName":"demo_webhook","pushIdType":"user:#account_id","config":"{\"url\":\"https://example.com/hook\",\"paramsList\":[{\"key\":\"title\",\"keyName\":\"标题\",\"type\":\"STRING\",\"required\":0}],\"userParamsList\":[{\"key\":\"city\",\"columnName\":\"user:city\",\"defaultValue\":\"-\"}],\"authConfig\":{\"enable\":false}}","enableTouchEvent":1,"eventDeliveryName":"delivery","eventClickName":"click","touchEventSource":"custom"}'
 ```
 
 ---

package/skills/ae-engage/references/common-metric.md

@@ -51,13 +51,13 @@ Object-group filter example:
 ```json
 {
   "type": "object_group",
-  "field": "equipment_list",
+  "field": "items",
   "operator": "any_satisfy",
   "conditions": {
     "relation": "and",
     "items": [
       {
-        "field": "equipment_list.item_level",
+        "field": "items.quantity",
         "operator": "gte",
         "values": [10]
       }

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

@@ -135,13 +135,13 @@ property filter. Use an object-group filter and place only that parent's child p
 ```json
 {
   "type": "object_group",
-  "field": "equipment_list",
+  "field": "items",
   "operator": "any_satisfy",
   "conditions": {
     "relation": "and",
     "items": [
       {
-        "field": "equipment_list.item_level",
+        "field": "items.quantity",
         "operator": "gte",
         "values": [10]
       }

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

@@ -117,7 +117,7 @@ First, check if both `.ae-cli/draft.json` and `.ae-cli/draft.xlsx` exist:
 
 1. **Do you need to generate a tracking plan first?**
    - Yes → suggest using `ae-generate-tracking-plan` skill
-   - Reference: tracking plan document (Feishu: https://www.feishu.cn/docx/Jt0VdhNB6oSJ4TxISs1cq2Ebnmg)
+   - Reference: use a tracking plan document supplied by the user as source material.
 
 2. **If you already have a tracking plan**
    - Provide the xlsx file path and use `ae-cli tracking code import-template --template` to import