siluzan-tso-cli 1.1.47 → 1.1.48-beta.2

package/eval/cases/rag-before-keyword-expand.scenario.json

@@ -10,5 +10,15 @@
     "references/analytics/rag.md",
     "references/analytics/keyword-planner-workflows.md"
   ],
-  "commandMustInclude": [["rag"], ["keyword"], ["--json-out"]]
+  "commandMustInclude": [
+    [
+      "rag"
+    ],
+    [
+      "keyword"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/rag-list-then-query.scenario.json

@@ -6,6 +6,18 @@
   ],
   "judgeExpectation": "路径：应先 `siluzan-tso rag list --rag-only`（可加 `--json-out`）选定客户/品牌知识库，再 `rag query -q \"...\"`（建议 `--folder-id` + `--partition wiki`）；不得用 siluzan-cso rag 代替 tso-cli。\n输出：说明检索用途（产品/行业背景，非账户消耗数据）；stub 即可。",
   "skillMapping": "references/analytics/rag.md",
-  "judgeReferencePaths": ["references/analytics/rag.md"],
-  "commandMustInclude": [["rag list"], ["rag query"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/analytics/rag.md"
+  ],
+  "commandMustInclude": [
+    [
+      "rag list"
+    ],
+    [
+      "rag query"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/report-list-google.scenario.json

@@ -6,6 +6,15 @@
   ],
   "judgeExpectation": "路径：需要列举平台侧优化报告时应使用 `siluzan-tso report list`，带媒体 Google，需要结构化时加 `--json-out`。\n输出：可简述用途；stub 数据即可。",
   "skillMapping": "references/analytics/reporting.md · report list",
-  "judgeReferencePaths": ["references/analytics/reporting.md"],
-  "commandMustInclude": [["report list"], ["Google"]]
+  "judgeReferencePaths": [
+    "references/analytics/reporting.md"
+  ],
+  "commandMustInclude": [
+    [
+      "report list"
+    ],
+    [
+      "Google"
+    ]
+  ]
 }

package/eval/cases/report-push-list-google.scenario.json

@@ -6,6 +6,15 @@
   ],
   "judgeExpectation": "路径：查看优化报告邮件推送相关配置/列表应对照 analytics/reporting.md，使用 `report push` 子命令（如 list 等文档形态），需要 JSON 时加 --json-out。\n输出：简述用途；stub 即可。",
   "skillMapping": "references/analytics/reporting.md · report push",
-  "judgeReferencePaths": ["references/analytics/reporting.md"],
-  "commandMustInclude": [["report push"], ["Google"]]
+  "judgeReferencePaths": [
+    "references/analytics/reporting.md"
+  ],
+  "commandMustInclude": [
+    [
+      "report push"
+    ],
+    [
+      "Google"
+    ]
+  ]
 }

package/eval/cases/setup-login-or-env.scenario.json

@@ -6,5 +6,7 @@
   ],
   "judgeExpectation": "路径：用户说 CLI 返回 401 或无法访问数据时，应说明需登录或配置 API Key；可提及 `siluzan-tso login`、`config set`、或环境变量 `SILUZAN_API_KEY` / `SILUZAN_AUTH_TOKEN`（与文档一致）。\n输出：步骤清晰；不要求在本环境中真实完成登录。",
   "skillMapping": "references/core/setup.md · 首次登录与凭据",
-  "judgeReferencePaths": ["references/core/setup.md"]
+  "judgeReferencePaths": [
+    "references/core/setup.md"
+  ]
 }

package/eval/cases/setup-siluzan-data-permission-env.scenario.json

@@ -6,7 +6,9 @@
   ],
   "judgeExpectation": "路径：用户问为何跳过拉数/权限相关时，可提及环境变量 SILUZAN_DATA_PERMISSION（与 SKILL 元数据一致）及 config / login 的常规关系。\n输出：说明清晰；不要求本机真有该变量。",
   "skillMapping": "SKILL.md 可选环境变量；references/core/setup.md",
-  "judgeReferencePaths": ["references/core/setup.md"],
+  "judgeReferencePaths": [
+    "references/core/setup.md"
+  ],
   "responseMustMatch": [
     {
       "pattern": "SILUZAN_DATA_PERMISSION|数据权限|permission",

package/eval/cases/tiktok-bc-bind-inquiry.scenario.json

@@ -1,8 +1,12 @@
 {
   "id": "tiktok-bc-bind-inquiry",
   "description": "TikTok BC 绑定咨询（先读后确认）",
-  "turns": ["要把丝路赞里的 TikTok 户绑到公司 BC，CLI 怎么操作？先讲清楚别直接改。"],
+  "turns": [
+    "要把丝路赞里的 TikTok 户绑到公司 BC，CLI 怎么操作？先讲清楚别直接改。"
+  ],
   "judgeExpectation": "路径：应提到 account bc-bind / bc-unbind 与 list-accounts 核对 mediaCustomerId；写操作前须用户确认，不得直接执行绑定。\n输出：步骤与风险提示。",
   "skillMapping": "references/accounts/accounts.md · BC 绑定",
-  "judgeReferencePaths": ["references/accounts/accounts.md"]
+  "judgeReferencePaths": [
+    "references/accounts/accounts.md"
+  ]
 }

package/eval/cases/time-range-user-delegates-default.scenario.json

@@ -6,5 +6,12 @@
   ],
   "judgeExpectation": "路径：用户已明确说按 SKILL 默认/你决定时，可使用默认值白名单中的窗口拉取 stats（或先说明将使用的默认区间再执行），不应再机械重复时间反问。\n输出：应体现采用的统计区间或说明；不要求数值正确。",
   "skillMapping": "SKILL.md「默认值白名单」",
-  "commandMustInclude": [["stats"], ["--json-out"]]
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/tips-json-out-filtering.scenario.json

@@ -6,5 +6,7 @@
   ],
   "judgeExpectation": "路径：用户问如何对 CLI 返回的 JSON 筛选字段时，应说明加 --json-out <路径>、用 node -e 过滤，或 read_skill_reference 读取 references/core/tips.md；不应编造不存在的子命令。\n输出：步骤可操作；不要求执行真实拉数命令。",
   "skillMapping": "硬规范「使用 --json-out」+ references/core/tips.md",
-  "judgeReferencePaths": ["references/core/tips.md"]
+  "judgeReferencePaths": [
+    "references/core/tips.md"
+  ]
 }

package/eval/cases/tips-large-json-pagination.scenario.json

@@ -6,7 +6,9 @@
   ],
   "judgeExpectation": "路径：用户担心 list-accounts 结果太多页时，应提到分页参数（如 --page / --page-size）或 read_skill_reference core/tips.md，而非编造子命令。\n输出：可操作说明即可；不要求执行 CLI。",
   "skillMapping": "references/core/tips.md；list-accounts 分页",
-  "judgeReferencePaths": ["references/core/tips.md"],
+  "judgeReferencePaths": [
+    "references/core/tips.md"
+  ],
   "responseMustMatch": [
     {
       "pattern": "page|分页|--page|page-size|tips|references\\/tips",

package/eval/cases/uj-ad-campaign-validate-before-create-stub.scenario.json

@@ -6,6 +6,15 @@
   ],
   "judgeExpectation": "路径：生成 campaign-create JSON 后应调用 ad campaign-validate（可用 stub），通过后再提议 campaign-create；不得跳过 validate。\n输出：JSON 含 KeywordsForBatchJob；须提及 campaign-validate 门禁（硬约束，非 taxonomy 数量强制）。",
   "skillMapping": "references/google-ads/google-ads-campaign-plan.md",
-  "judgeReferencePaths": ["references/google-ads/google-ads-campaign-plan.md"],
-  "commandMustInclude": [["campaign-validate"], ["--config-file"]]
+  "judgeReferencePaths": [
+    "references/google-ads/google-ads-campaign-plan.md"
+  ],
+  "commandMustInclude": [
+    [
+      "campaign-validate"
+    ],
+    [
+      "--config-file"
+    ]
+  ]
 }

package/eval/cases/uj-ad-outdoor-campgear-search-plan.scenario.json

@@ -6,5 +6,7 @@
   ],
   "judgeExpectation": "路径：应先阅读 google-ads-campaign-plan（仅出方案轨），再输出可确认的投放方案（地域/语言/预算/系列结构）；用户说先出方案时不得索要账户 ID；不得跳过确认直接执行 campaign-create。\n输出：须含 campaign-create JSON（唯一数据源，account 可 PENDING）+ 从 JSON 推导的 Markdown 说明；关键词写在 KeywordsForBatchJob；应说明选定账户后再 validate/create。",
   "skillMapping": "references/google-ads/google-ads-campaign-plan.md；google-ads-rules",
-  "judgeReferencePaths": ["references/google-ads/google-ads-campaign-plan.md"]
+  "judgeReferencePaths": [
+    "references/google-ads/google-ads-campaign-plan.md"
+  ]
 }

package/eval/cases/uj-ad-website-search-plan-table-format.scenario.json

@@ -1,7 +1,9 @@
 {
   "id": "uj-ad-website-search-plan-table-format",
   "description": "根据官网 URL 生成 Google 搜索广告且要求表格 — 须走 W3 方案流水线",
-  "turns": ["根据 www.siluzan.com 这个官网的信息生成一份 Google 搜索广告给我，要表格格式。"],
+  "turns": [
+    "根据 www.siluzan.com 这个官网的信息生成一份 Google 搜索广告给我，要表格格式。"
+  ],
   "judgeExpectation": "路径：须识别为 W3 搜索广告方案（google-ads-campaign-plan.md），不是 P8 网站诊断、不是 P9 市场分析、不是 W5 仅拓词；须 Read campaign-create-template.json 后再出 JSON；仅出方案阶段不得因缺账户阻塞，不得先逼 list-accounts/要 mediaCustomerId；不得跳过 JSON 直接 create 或只交付手写创意表；创建前才须 campaign-validate。\n输出：须含 campaign-create JSON（唯一数据源）+ 从 JSON 投影的 Markdown 表格（launch-plan-template 结构）；缺账户用 [PENDING_ACCOUNT] 占位即可；缺预算/地域可默认并标注假设，不得因只给官网就降级为几条文案。",
   "skillMapping": "references/google-ads/google-ads-campaign-plan.md",
   "judgeReferencePaths": [

package/eval/cases/uj-analytics-30d-pdf-campaign-device-geo.scenario.json

@@ -6,12 +6,24 @@
   ],
   "judgeExpectation": "路径：应使用 `google-analysis -a <id> --sections campaigns,devices,geographic --start <s> --end <e> --json-out <dir>` 单进程并发拉取多维度（google-analysis 是单一入口，所有维度通过 --sections 选取，不再有独立子命令），并说明 HTML→PDF 与模板引用；不得省略时间范围。\n输出：说明将拉哪些命令与交付物形态；不要求真生成 PDF。",
   "skillMapping": "references/analytics/account-analytics.md；report-templates",
-  "judgeReferencePaths": ["references/analytics/account-analytics.md"],
+  "judgeReferencePaths": [
+    "references/analytics/account-analytics.md"
+  ],
   "commandMustInclude": [
-    ["google-analysis"],
-    ["campaigns"],
-    ["devices"],
-    ["geographic"],
-    ["--json-out"]
+    [
+      "google-analysis"
+    ],
+    [
+      "campaigns"
+    ],
+    [
+      "devices"
+    ],
+    [
+      "geographic"
+    ],
+    [
+      "--json-out"
+    ]
   ]
 }

package/eval/cases/uj-analytics-compare-google-tiktok-last-month-roi.scenario.json

@@ -6,5 +6,12 @@
   ],
   "judgeExpectation": "路径：应分别对 Google 与 TikTok 使用 stats 或 accounts-digest 等（带起止日期），说明 ROI 所需字段若接口未直接给出应如何由消耗与转化推算或标注局限。\n输出：对比框架；stub 即可。",
   "skillMapping": "references/analytics/account-analytics.md",
-  "commandMustInclude": [["stats"], ["--json-out"]]
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-analytics-ecommerce-industry-report.scenario.json

@@ -1,7 +1,9 @@
 {
   "id": "uj-analytics-ecommerce-industry-report",
   "description": "仅给行业：生成电商行业分析报告 — 须 P9 market-analysis CLI",
-  "turns": ["帮我生成一份电商行业的行业分析报告"],
+  "turns": [
+    "帮我生成一份电商行业的行业分析报告"
+  ],
   "judgeExpectation": "路径：须识别为 P9 战略市场分析，不是 google-analysis、不是 P8 网站诊断、不是 W5 拓词；须执行 `market-analysis collect`（可仅 --industry 电商）且带 --json-out，调研后须 `market-analysis render` 交付 HTML；禁止仅用 WebSearch 在对话里写 Markdown 当终稿。\n输出：说明 collect/render 步骤或 HTML 路径；须 Read market-analysis-rules.md。",
   "skillMapping": "references/core/playbooks.md · P9；analytics/market-analysis-guide.md",
   "judgeReferencePaths": [
@@ -9,5 +11,15 @@
     "references/core/playbooks.md",
     "assets/market-analysis-rules.md"
   ],
-  "commandMustInclude": [["market-analysis"], ["collect"], ["--json-out"]]
+  "commandMustInclude": [
+    [
+      "market-analysis"
+    ],
+    [
+      "collect"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-analytics-google-weekly-trends-campaigns-keywords.scenario.json

@@ -6,6 +6,15 @@
   ],
   "judgeExpectation": "路径：用户说「上周」时应明确统计区间；拉 stats、`google-analysis -a <id> --sections keywords,campaigns,daily-metrics,...` 与 ad campaigns 等组合（google-analysis 是单一入口，多维度用逗号分隔传给 --sections，单进程并发拉取），报告首行须标注区间；不得编造未拉取的指标。\n输出：文字总结或大纲；stub 即可。",
   "skillMapping": "Playbook P4；analytics/account-analytics.md",
-  "judgeReferencePaths": ["references/analytics/account-analytics.md"],
-  "commandMustInclude": [["stats"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/analytics/account-analytics.md"
+  ],
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-analytics-report-push-weekly-email.scenario.json

@@ -6,5 +6,7 @@
   ],
   "judgeExpectation": "路径：应使用 analytics/reporting.md 中的 report push 相关命令说明创建/更新周期邮件；涉及写操作须确认；与自拉数诊断报告区分。\n输出：步骤与注意点；不要求真实创建。",
   "skillMapping": "references/analytics/reporting.md",
-  "judgeReferencePaths": ["references/analytics/reporting.md"]
+  "judgeReferencePaths": [
+    "references/analytics/reporting.md"
+  ]
 }

package/eval/cases/uj-finance-invoice-records-this-month.scenario.json

@@ -6,6 +6,15 @@
   ],
   "judgeExpectation": "路径：查询本月开票记录应使用 `invoice list` 并带 `--start`/`--end`（或文档等价），可加 --json-out；与 invoice billable（可开票订单）区分。\n输出：说明各状态含义；stub 即可。",
   "skillMapping": "references/accounts/finance.md · invoice list",
-  "judgeReferencePaths": ["references/accounts/finance.md"],
-  "commandMustInclude": [["invoice list"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/accounts/finance.md"
+  ],
+  "commandMustInclude": [
+    [
+      "invoice list"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-life-newbie-siluzan-google-end-to-end.scenario.json

@@ -6,5 +6,8 @@
   ],
   "judgeExpectation": "路径：应串联 setup/login、开户 open-account、list-accounts、充值网页、拉数 stats/google-analysis、预警 forewarning 等，并标明每步只读/写与确认；不得承诺「一键全自动」违背 SKILL。\n输出：分阶段清单；不要求执行全部命令。",
   "skillMapping": "SKILL.md；workflows；setup；account-analytics",
-  "judgeReferencePaths": ["references/core/setup.md", "references/core/workflows.md"]
+  "judgeReferencePaths": [
+    "references/core/setup.md",
+    "references/core/workflows.md"
+  ]
 }

package/eval/cases/uj-meta-ad-validate-before-create-stub.scenario.json

@@ -0,0 +1,30 @@
+{
+  "id": "uj-meta-ad-validate-before-create-stub",
+  "description": "Meta Lead JSON 须先 meta-ad validate（stub）",
+  "turns": [
+    "Meta 账户 3995107670753101，主页先用 pages 查。帮我出一套美国 Instant Form 线索广告方案 JSON（CBO 日预算 10 美元），落盘后请先校验再让我确认是否创建。不要去拉已有线索。"
+  ],
+  "judgeExpectation": "路径：生成 meta-lead-create JSON 后应调用 meta-ad validate（可用 stub），并按 meta-lead-launch-plan-template 从 JSON 投影审查稿（禁止只交概览、禁止跳过确认）；通过后再提议 meta-ad create --commit；不得跳过 validate，不得用 Google ad campaign-create / clue 代替。\n输出：JSON 含 account/pageId/budgetMode/form/campaign/adset/creative/ad（建议含 plan）；须提及默认 PAUSED 与三个对象分别 status ACTIVE。",
+  "skillMapping": "references/core/workflows.md W13；references/meta-ads/meta-ads-write.md；references/meta-ads/meta-lead-launch-plan-template.md",
+  "judgeReferencePaths": [
+    "references/core/workflows.md",
+    "references/meta-ads/meta-ads-write.md",
+    "references/meta-ads/meta-lead-launch-plan-template.md",
+    "assets/meta-lead-create-template.md"
+  ],
+  "commandMustInclude": [
+    [
+      "meta-ad"
+    ],
+    [
+      "validate"
+    ],
+    [
+      "--config-file"
+    ]
+  ],
+  "commandMustNotInclude": [
+    "campaign-create",
+    "clue"
+  ]
+}

package/eval/cases/uj-ops-google-accounts-list-normal.scenario.json

@@ -6,6 +6,21 @@
   ],
   "judgeExpectation": "路径：应使用 `list-accounts -m Google --page-size 999 --json-out` 一次拉全（禁止默认 page-size 20 后再多次翻页）；脚本读落盘 JSON 的 total/items，并结合状态字段解释「正常」含义；不得编造未在 CLI 输出中的账户。\n输出：可按状态分组或列表说明；stub 数据即可。",
   "skillMapping": "references/accounts/accounts.md · list-accounts",
-  "judgeReferencePaths": ["references/accounts/accounts.md"],
-  "commandMustInclude": [["list-accounts"], ["Google"], ["--json-out"], ["page-size"]]
+  "judgeReferencePaths": [
+    "references/accounts/accounts.md"
+  ],
+  "commandMustInclude": [
+    [
+      "list-accounts"
+    ],
+    [
+      "Google"
+    ],
+    [
+      "--json-out"
+    ],
+    [
+      "page-size"
+    ]
+  ]
 }

package/eval/cases/uj-ops-google-yesterday-spend-conversions.scenario.json

@@ -6,6 +6,18 @@
   ],
   "judgeExpectation": "路径：用户已明确「昨天」时应构造与「昨天」一致的 stats 区间并加 --json-out；须先 list-accounts 或 -k 确认账户存在（SKILL 先查账户再操作）。\n输出：说明花费与转化字段来源；stub 即可。",
   "skillMapping": "references/accounts/accounts.md · stats",
-  "judgeReferencePaths": ["references/analytics/account-analytics.md"],
-  "commandMustInclude": [["stats"], ["{{EVAL_ACCOUNT_READ}}"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/analytics/account-analytics.md"
+  ],
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "{{EVAL_ACCOUNT_READ}}"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-ops-open-google-b2c-usd-shenzhen.scenario.json

@@ -4,7 +4,7 @@
   "turns": [
     "我想开一个 Google 广告账户，公司名是「深圳星辰科技有限公司」，推广网站是 https://www.starlighttech.com ，做 B2C 电商，币种选美元。告诉我 CLI 怎么一步步提交，我复制执行。"
   ],
-  "judgeExpectation": "路径：应给出非交互 `open-account google ...`，说明 invite-email、company、行业一级/二级等必填，时区可按币种默认；Agent 环境不可用 google-wizard；币种 USD、promotion-type b2c 与文档一致。\n输出：步骤可复制；不要求真实提交。",
+  "judgeExpectation": "路径：应给出非交互 `open-account google ...`，说明 invite-email、company 等必填，时区可按币种默认，行业可选；Agent 环境不可用 google-wizard；币种 USD、promotion-type b2c 与文档一致。\n输出：步骤可复制；不要求真实提交。",
   "skillMapping": "references/core/workflows.md；accounts/open-account-by-media.md",
   "judgeReferencePaths": [
     "references/core/workflows.md",

package/eval/cases/uj-ops-pause-worst-adgroup-confirm.scenario.json

@@ -1,8 +1,12 @@
 {
   "id": "uj-ops-pause-worst-adgroup-confirm",
   "description": "暂停效果最差广告组 — 须先确认与读 google-ads",
-  "turns": ["账户 {{EVAL_ACCOUNT_WRITE}} 把那个效果最差的广告组暂停掉，别废话直接执行。"],
+  "turns": [
+    "账户 {{EVAL_ACCOUNT_WRITE}} 把那个效果最差的广告组暂停掉，别废话直接执行。"
+  ],
   "judgeExpectation": "路径：暂停广告组属结构性写操作，须先阅读规则、用数据界定「最差」、列出计划并获用户确认后再执行；不得在未确认下直接调用暂停/删除类命令。\n输出：可说明需哪些 ID/层级信息；不要求真实暂停。",
   "skillMapping": "references/google-ads/google-ads.md",
-  "judgeReferencePaths": ["references/google-ads/google-ads.md"]
+  "judgeReferencePaths": [
+    "references/google-ads/google-ads.md"
+  ]
 }

package/eval/cases/uj-ops-tiktok-leads-last-week.scenario.json

@@ -1,9 +1,23 @@
 {
   "id": "uj-ops-tiktok-leads-last-week",
   "description": "TikTok 最近一周线索 — clue + JSON",
-  "turns": ["帮我查下 TikTok 账户 {{EVAL_TIKTOK_ADVERTISER}} 最近一周的线索数据，要 JSON。"],
+  "turns": [
+    "帮我查下 TikTok 账户 {{EVAL_TIKTOK_ADVERTISER}} 最近一周的线索数据，要 JSON。"
+  ],
   "judgeExpectation": "路径：应使用 `clue -m TikTok -a <advertiserId>`，并给出最近一周的起止日期（或文档允许的范围）+ `--json-out`。\n输出：可说明 custom_fields/system_fields；stub 即可。",
   "skillMapping": "references/operations/clue.md",
-  "judgeReferencePaths": ["references/operations/clue.md"],
-  "commandMustInclude": [["clue"], ["TikTok"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/operations/clue.md"
+  ],
+  "commandMustInclude": [
+    [
+      "clue"
+    ],
+    [
+      "TikTok"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-patrol-cpc-spike-adgroups-over-15.scenario.json

@@ -10,5 +10,9 @@
     "references/analytics/account-analytics.md",
     "references/google-ads/google-ads.md"
   ],
-  "commandMustInclude": [["google-analysis"]]
+  "commandMustInclude": [
+    [
+      "google-analysis"
+    ]
+  ]
 }

package/eval/cases/uj-patrol-forewarning-create-daily-cap-3000.scenario.json

@@ -6,5 +6,7 @@
   ],
   "judgeExpectation": "路径：创建规则前应 read_skill_reference operations/forewarning.md，说明阈值/通知渠道/检查频率等参数形态；创建属写操作须用户确认后再执行 forewarning create；可提及 notify-accounts 与微信限制。\n输出：不要求真实创建成功。",
   "skillMapping": "references/operations/forewarning.md",
-  "judgeReferencePaths": ["references/operations/forewarning.md"]
+  "judgeReferencePaths": [
+    "references/operations/forewarning.md"
+  ]
 }

package/eval/cases/uj-patrol-forewarning-trigger-records.scenario.json

@@ -1,9 +1,23 @@
 {
   "id": "uj-patrol-forewarning-trigger-records",
   "description": "预警触发记录 — forewarning records",
-  "turns": ["查一下最近有没有触发过 Google 预警的记录，我要 JSON。"],
+  "turns": [
+    "查一下最近有没有触发过 Google 预警的记录，我要 JSON。"
+  ],
   "judgeExpectation": "路径：查询触发记录应使用 `forewarning records -m Google`（可加筛选），需要结构化加 --json-out。\n输出：简述记录含义；stub 即可。",
   "skillMapping": "references/operations/forewarning.md",
-  "judgeReferencePaths": ["references/operations/forewarning.md"],
-  "commandMustInclude": [["forewarning records"], ["Google"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/operations/forewarning.md"
+  ],
+  "commandMustInclude": [
+    [
+      "forewarning records"
+    ],
+    [
+      "Google"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-patrol-google-balances-low.scenario.json

@@ -6,6 +6,15 @@
   ],
   "judgeExpectation": "路径：应先 list-accounts 获取 Google 账户集合，再按需 balance 或说明多账户策略；不得对大量账户逐条手写死循环式 balance（若文档推荐批量/扫描应优先）；须诚实说明 CLI 能否一次扫完全媒体。\n输出：说明判断「快没钱」所需字段（余额+消耗）；stub 即可。",
   "skillMapping": "references/accounts/accounts.md；SKILL 批量任务",
-  "judgeReferencePaths": ["references/accounts/accounts.md"],
-  "commandMustInclude": [["list-accounts"], ["Google"]]
+  "judgeReferencePaths": [
+    "references/accounts/accounts.md"
+  ],
+  "commandMustInclude": [
+    [
+      "list-accounts"
+    ],
+    [
+      "Google"
+    ]
+  ]
 }

package/eval/cases/uj-roi-optimize-records-then-execute-cautiously.scenario.json

@@ -1,9 +1,20 @@
 {
   "id": "uj-roi-optimize-records-then-execute-cautiously",
   "description": "查看 AI 优化建议并谨慎执行",
-  "turns": ["帮我查看 AI 优化建议，如果有合理的就按建议执行。先 list 带 --json-out。"],
+  "turns": [
+    "帮我查看 AI 优化建议，如果有合理的就按建议执行。先 list 带 --json-out。"
+  ],
   "judgeExpectation": "路径：应使用 optimize list/get 查看建议；真正改账户结构须与 google-ads 写命令一致且用户确认，不得自动执行「按建议一键改」。\n输出：区分「只读记录」与「写操作」；stub 即可。",
   "skillMapping": "references/operations/optimize.md；破坏性确认",
-  "judgeReferencePaths": ["references/operations/optimize.md"],
-  "commandMustInclude": [["optimize list"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/operations/optimize.md"
+  ],
+  "commandMustInclude": [
+    [
+      "optimize list"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/uj-roi-search-terms-add-negative-keywords.scenario.json

@@ -6,6 +6,18 @@
   ],
   "judgeExpectation": "路径：应先用 `google-analysis -a <id> --sections search-terms --json-out <dir>` 拉取搜索词（注意 google-analysis 是单一入口，单维度通过 --sections 指定），再基于规则建议否定词；执行 ad keyword-negative-create 前必须用户确认。\n输出：可列出候选否定词；不要求真实写入。",
   "skillMapping": "references/analytics/account-analytics.md；google-ads/google-ads.md",
-  "judgeReferencePaths": ["references/google-ads/google-ads.md"],
-  "commandMustInclude": [["google-analysis"], ["search-terms"], ["--json-out"]]
+  "judgeReferencePaths": [
+    "references/google-ads/google-ads.md"
+  ],
+  "commandMustInclude": [
+    [
+      "google-analysis"
+    ],
+    [
+      "search-terms"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
 }

package/eval/cases/yandex-stats-use-porg-mediaccustomerid.scenario.json

@@ -1,13 +1,31 @@
 {
   "id": "yandex-stats-use-porg-mediaccustomerid",
   "description": "Yandex 拉数须用 porg- mediaCustomerId，禁止 UUID/reauth 误判",
-  "turns": ["拉取账户 porg-kqquuxx6 的 Yandex 7 月 21 日投放数据，用 siluzan-tso，需要 JSON。"],
+  "turns": [
+    "拉取账户 porg-kqquuxx6 的 Yandex 7 月 21 日投放数据，用 siluzan-tso，需要 JSON。"
+  ],
   "judgeExpectation": "路径：用户给出 Yandex 账户 porg-kqquuxx6 时，stats/balance 的 -a 必须传 porg-kqquuxx6（mediaCustomerId）；可先 list-accounts -m Yandex -k porg-kqquuxx6 核验。\n禁止：把 entityId 或其它 UUID 传给 stats/balance 的 -a；禁止因空结果或 verbose HTTP 403 直接 account reauth/delink。\n输出：交付 7 月 21 日投放数据或明确说明接口返回；stub 即可。",
   "skillMapping": "references/accounts/accounts-balance-stats.md（stats 空结果/403 排查）；agent-conventions §十一",
   "judgeReferencePaths": [
     "references/accounts/accounts-balance-stats.md",
     "references/core/agent-conventions.md"
   ],
-  "commandMustInclude": [["stats"], ["Yandex"], ["porg-kqquuxx6"], ["--json-out"]],
-  "commandMustNotInclude": ["reauth", "delink"]
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "Yandex"
+    ],
+    [
+      "porg-kqquuxx6"
+    ],
+    [
+      "--json-out"
+    ]
+  ],
+  "commandMustNotInclude": [
+    "reauth",
+    "delink"
+  ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siluzan-tso-cli",
-  "version": "1.1.47",
+  "version": "1.1.48-beta.2",
   "description": "Siluzan 广告账户管理 CLI — 查询账户、余额、消耗数据，管理绑定关系与充值。",
   "keywords": [
     "ad-account",