siluzan-tso-cli 1.1.20-beta.2 → 1.1.20-beta.21

package/eval/cases/optimize-list-by-account.scenario.json

@@ -1,9 +1,17 @@
 {
   "id": "optimize-list-by-account",
   "description": "AI 优化记录 — optimize list",
-  "turns": ["查 Google 账户 {{EVAL_ACCOUNT_READ}} 在丝路赞里的 AI 优化记录列表，给我 JSON。"],
+  "turns": [
+    "查 Google 账户 {{EVAL_ACCOUNT_READ}} 在丝路赞里的 AI 优化记录列表，给我 JSON。"
+  ],
   "judgeExpectation": "路径：查某账户优化批次列表应使用 `siluzan-tso optimize list -a <mediaCustomerId>`，需要分析时加 `--json`；脱管账户场景文档另有 `--match-media-customer-id`，本场景用简单 -a 即可。\n输出：不要求记录内容真实。",
   "skillMapping": "references/optimize.md",
-  "judgeReferencePaths": ["references/optimize.md"],
-  "commandMustInclude": [["optimize list"]]
+  "judgeReferencePaths": [
+    "references/optimize.md"
+  ],
+  "commandMustInclude": [
+    [
+      "optimize list"
+    ]
+  ]
 }

package/eval/cases/p1-single-account-profile.scenario.json

@@ -6,5 +6,15 @@
   ],
   "judgeExpectation": "路径：应先确认账户（list-accounts 或等效），再拉 stats 与 ad campaigns（或带日期的 campaigns），需要结构化数据时应使用 --json。\n输出：应对该区间做文字/表格总结；若材料中有货币/区间信息，应表述清楚；不要求具体消耗数字正确。",
   "skillMapping": "Playbook P1 · 单账户投放画像",
-  "commandMustInclude": [["list-accounts"], ["stats"], ["ad campaigns"]]
+  "commandMustInclude": [
+    [
+      "list-accounts"
+    ],
+    [
+      "stats"
+    ],
+    [
+      "ad campaigns"
+    ]
+  ]
 }

package/eval/cases/p2-balance-scan-bulk.scenario.json

@@ -6,6 +6,13 @@
   ],
   "judgeExpectation": "路径：多账户续航/余额筛查应使用 balance-scan（或文档允许的批量命令），不应大量逐账户单独 balance 拖慢任务。\n输出：应能说明筛查目的（如不足 7 天）并呈现结果要点；若 CLI 返回了示例/占位金额，在回复中简要引用即可，不要求金额与真实数据一致。",
   "skillMapping": "Playbook P2 · 批量余额 / 硬规范「批量任务」",
-  "commandMustInclude": [["balance-scan"]],
-  "commandMustNotInclude": ["for ", "while "]
+  "commandMustInclude": [
+    [
+      "balance-scan"
+    ]
+  ],
+  "commandMustNotInclude": [
+    "for ",
+    "while "
+  ]
 }

package/eval/cases/p3-accounts-digest.scenario.json

@@ -6,7 +6,11 @@
   ],
   "judgeExpectation": "路径：多账户汇总消耗应优先 accounts-digest，而非对每个账户重复 stats。\n输出：应有汇总表或对比说明；不要求 ROAS/消耗数值与真实数据一致。",
   "skillMapping": "Playbook P3 · accounts-digest",
-  "commandMustInclude": [["accounts-digest"]],
+  "commandMustInclude": [
+    [
+      "accounts-digest"
+    ]
+  ],
   "maxOccurrences": [
     {
       "pattern": "stats --",

package/eval/cases/p4-period-report-window.scenario.json

@@ -6,5 +6,12 @@
   ],
   "judgeExpectation": "路径：在已给起止日期下应拉取 stats 与 ad campaigns（或等价）以支撑周期分析。\n输出：应有区间感知的文字总结；不要求指标数值准确。",
   "skillMapping": "Playbook P4 · 周期报告",
-  "commandMustInclude": [["stats"], ["ad campaigns"]]
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "ad campaigns"
+    ]
+  ]
 }

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

@@ -0,0 +1,24 @@
+{
+  "id": "rag-before-keyword-expand",
+  "description": "拓词编排 — RAG 补产品语境后再 keyword",
+  "turns": [
+    "客户做工业胶粘剂出口，官网 https://example.com/adhesive ，帮我拓一批 Google 搜索词。先从知识库找产品型号和行业术语，再用 keyword 拉市场侧搜索量，命令用 --json-out 落盘。"
+  ],
+  "judgeExpectation": "路径：应先 `rag list`/`rag query` 拉客户产品/英文类目等背景，再 `keyword -k \"...\"`（可加 `--url`/`--json-out`）；不得跳过知识库直接只跑 keyword。\n输出：说明两步分工（市场参考词 vs 企业事实）；stub 即可。",
+  "skillMapping": "references/rag.md · references/keyword-planner-workflows.md",
+  "judgeReferencePaths": [
+    "references/rag.md",
+    "references/keyword-planner-workflows.md"
+  ],
+  "commandMustInclude": [
+    [
+      "rag"
+    ],
+    [
+      "keyword"
+    ],
+    [
+      "--json-out"
+    ]
+  ]
+}

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

@@ -0,0 +1,23 @@
+{
+  "id": "rag-list-then-query",
+  "description": "知识库 — 先 list 选库再 query 检索（TSO 业务辅助）",
+  "turns": [
+    "拓 Google 词前要先查知识库：请依次执行 siluzan-tso rag list --rag-only --json，再 siluzan-tso rag query -q \"产品卖点 应用场景\" --partition wiki --json，两条命令都要跑。"
+  ],
+  "judgeExpectation": "路径：应先 `siluzan-tso rag list --rag-only`（可加 `--json`）选定客户/品牌知识库，再 `rag query -q \"...\"`（建议 `--folder-id` + `--partition wiki`）；不得用 siluzan-cso rag 代替 tso-cli。\n输出：说明检索用途（产品/行业背景，非账户消耗数据）；stub 即可。",
+  "skillMapping": "references/rag.md",
+  "judgeReferencePaths": [
+    "references/rag.md"
+  ],
+  "commandMustInclude": [
+    [
+      "rag list"
+    ],
+    [
+      "rag query"
+    ],
+    [
+      "--json"
+    ]
+  ]
+}

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

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

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

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

package/eval/cases/reporting-vs-account-analytics-routing.scenario.json

@@ -6,5 +6,8 @@
   ],
   "judgeExpectation": "路径：用户问「Siluzan/丝路赞 上的优化报告、列表、推送」时应对照 reporting.md（report list/create 等）；若用户要自己拉数写 HTML/PDF 诊断，应对照 account-analytics.md，不应把两类混为一谈。\n输出：说清适用场景；不要求执行真实 report create。",
   "skillMapping": "SKILL「报告的生成」；reporting.md vs account-analytics.md",
-  "judgeReferencePaths": ["references/reporting.md", "references/account-analytics.md"]
+  "judgeReferencePaths": [
+    "references/reporting.md",
+    "references/account-analytics.md"
+  ]
 }

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/setup.md · 首次登录与凭据",
-  "judgeReferencePaths": ["references/setup.md"]
+  "judgeReferencePaths": [
+    "references/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/setup.md",
-  "judgeReferencePaths": ["references/setup.md"],
+  "judgeReferencePaths": [
+    "references/setup.md"
+  ],
   "responseMustMatch": [
     {
       "pattern": "SILUZAN_DATA_PERMISSION|数据权限|permission",

package/eval/cases/skill-optimize-vs-google-ads-distinction.scenario.json

@@ -6,5 +6,8 @@
   ],
   "judgeExpectation": "路径：应说明 `optimize` 为平台侧优化记录/查询；Google 广告结构、关键词与系列级优化以 `google-ads.md` 为准；二者独立，不应混为同一流程。\n输出：可点名两篇文档；不要求执行 CLI。",
   "skillMapping": "SKILL.md；references/optimize.md vs google-ads.md",
-  "judgeReferencePaths": ["references/optimize.md", "references/google-ads.md"]
+  "judgeReferencePaths": [
+    "references/optimize.md",
+    "references/google-ads.md"
+  ]
 }

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.md · BC 绑定",
-  "judgeReferencePaths": ["references/accounts.md"]
+  "judgeReferencePaths": [
+    "references/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"]]
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "--json"
+    ]
+  ]
 }

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

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

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

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

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

@@ -0,0 +1,20 @@
+{
+  "id": "uj-ad-campaign-validate-before-create-stub",
+  "description": "方案 JSON 须先 campaign-validate（stub）",
+  "turns": [
+    "账户 6326027735，客户名从 list-accounts 取。为 B2B payment API 做一条美国搜索系列方案 JSON，含 1 个广告组、核心词与长尾词分层，落盘后请先校验再让我确认是否创建。"
+  ],
+  "judgeExpectation": "路径：生成 campaign-create JSON 后应调用 ad campaign-validate（可用 stub），通过后再提议 campaign-create；不得跳过 validate。\n输出：JSON 含 KeywordsForBatchJob；须提及 validate 门禁（硬约束，非 taxonomy 数量强制）。",
+  "skillMapping": "references/google-ads-campaign-plan.md",
+  "judgeReferencePaths": [
+    "references/google-ads-campaign-plan.md"
+  ],
+  "commandMustInclude": [
+    [
+      "campaign-validate"
+    ],
+    [
+      "--config-file"
+    ]
+  ]
+}

package/eval/cases/uj-ad-keywords-camping-tent-outdoor-plan.scenario.json

@@ -4,6 +4,6 @@
   "turns": [
     "针对关键词「camping tent, outdoor gear, hiking equipment」生成一个完整的 Google 广告投放方案，包括系列与广告组结构。"
   ],
-  "judgeExpectation": "路径：应引用关键词策略/匹配方式/否定词等规则文档思路，给出分层与预算分配，用户确认前不执行写命令。\n输出：结构化方案；不要求真实 CLI。",
+  "judgeExpectation": "路径：应引用关键词策略/匹配方式/否定词等规则文档思路，给出分层与预算分配，用户确认前不执行写命令。\n输出：campaign-create JSON + Markdown 说明；含 KeywordsForBatchJob；说明 validate 步骤；不要求真实 create。",
   "skillMapping": "references/google-ads-rules/google-ads-keyword-strategy.md"
 }

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

@@ -4,7 +4,9 @@
   "turns": [
     "我卖户外露营装备，主要面向美国和欧洲市场，网站是 https://www.campgear.com ，每天预算 3000 美金，帮我规划一套 Google 搜索广告方案。先出方案别直接开户投钱。"
   ],
-  "judgeExpectation": "路径：应先阅读 google-ads.md 规则流程，再输出可确认的投放方案（地域/语言/预算/系列结构），不得跳过合规与确认直接执行 campaign-create。\n输出：方案级 Markdown 即可；不要求执行 CLI。",
-  "skillMapping": "references/google-ads.md；google-ads-rules",
-  "judgeReferencePaths": ["references/google-ads.md"]
+  "judgeExpectation": "路径：应先阅读 google-ads.md 规则流程，再输出可确认的投放方案（地域/语言/预算/系列结构），不得跳过合规与确认直接执行 campaign-create。\n输出：须含可执行的 campaign-create JSON（唯一数据源）+ 从 JSON 推导的 Markdown 说明；关键词在 KeywordsForBatchJob；方案阶段应说明须 ad campaign-validate 通过后再 create。",
+  "skillMapping": "references/google-ads-campaign-plan.md；google-ads-rules",
+  "judgeReferencePaths": [
+    "references/google-ads-campaign-plan.md"
+  ]
 }

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/account-analytics.md；report-templates",
-  "judgeReferencePaths": ["references/account-analytics.md"],
+  "judgeReferencePaths": [
+    "references/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/account-analytics.md",
-  "commandMustInclude": [["stats"], ["--json"]]
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "--json"
+    ]
+  ]
 }

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；account-analytics.md",
-  "judgeReferencePaths": ["references/account-analytics.md"],
-  "commandMustInclude": [["stats"], ["--json"]]
+  "judgeReferencePaths": [
+    "references/account-analytics.md"
+  ],
+  "commandMustInclude": [
+    [
+      "stats"
+    ],
+    [
+      "--json"
+    ]
+  ]
 }

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

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

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

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

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/setup.md", "references/workflows.md"]
+  "judgeReferencePaths": [
+    "references/setup.md",
+    "references/workflows.md"
+  ]
 }

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

@@ -6,6 +6,18 @@
   ],
   "judgeExpectation": "路径：应使用 `list-accounts -m Google`（建议 --json）获取账户列表，并结合返回中的状态字段解释「正常」含义；不得编造未在 CLI 输出中的账户。\n输出：可按状态分组或列表说明；stub 数据即可。",
   "skillMapping": "references/accounts.md · list-accounts",
-  "judgeReferencePaths": ["references/accounts.md"],
-  "commandMustInclude": [["list-accounts"], ["Google"], ["--json"]]
+  "judgeReferencePaths": [
+    "references/accounts.md"
+  ],
+  "commandMustInclude": [
+    [
+      "list-accounts"
+    ],
+    [
+      "Google"
+    ],
+    [
+      "--json"
+    ]
+  ]
 }

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

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

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

@@ -6,5 +6,8 @@
   ],
   "judgeExpectation": "路径：应给出非交互 `open-account google ...`，说明 invite-email、timezone、company 等必填；Agent 环境不可用 google-wizard；币种 USD、promotion-type b2c 与文档一致。\n输出：步骤可复制；不要求真实提交。",
   "skillMapping": "references/workflows.md；open-account-by-media.md",
-  "judgeReferencePaths": ["references/workflows.md", "references/open-account-by-media.md"]
+  "judgeReferencePaths": [
+    "references/workflows.md",
+    "references/open-account-by-media.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.md",
-  "judgeReferencePaths": ["references/google-ads.md"]
+  "judgeReferencePaths": [
+    "references/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`。\n输出：可说明 custom_fields/system_fields；stub 即可。",
   "skillMapping": "references/clue.md",
-  "judgeReferencePaths": ["references/clue.md"],
-  "commandMustInclude": [["clue"], ["TikTok"], ["--json"]]
+  "judgeReferencePaths": [
+    "references/clue.md"
+  ],
+  "commandMustInclude": [
+    [
+      "clue"
+    ],
+    [
+      "TikTok"
+    ],
+    [
+      "--json"
+    ]
+  ]
 }

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

@@ -6,6 +6,13 @@
   ],
   "judgeExpectation": "路径：应先通过 google-analysis 等拉取广告组级 CPC/花费，再解释异常；暂停广告组前须确认，不得直接执行。\n输出：可列出将使用的子命令；不要求真实暂停。",
   "skillMapping": "references/account-analytics.md；google-ads.md",
-  "judgeReferencePaths": ["references/account-analytics.md", "references/google-ads.md"],
-  "commandMustInclude": [["google-analysis"]]
+  "judgeReferencePaths": [
+    "references/account-analytics.md",
+    "references/google-ads.md"
+  ],
+  "commandMustInclude": [
+    [
+      "google-analysis"
+    ]
+  ]
 }

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

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

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.md；SKILL 批量任务",
-  "judgeReferencePaths": ["references/accounts.md"],
-  "commandMustInclude": [["list-accounts"], ["Google"]]
+  "judgeReferencePaths": [
+    "references/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。"],
+  "turns": [
+    "帮我查看 AI 优化建议，如果有合理的就按建议执行。先 list 带 --json。"
+  ],
   "judgeExpectation": "路径：应使用 optimize list/get 查看建议；真正改账户结构须与 google-ads 写命令一致且用户确认，不得自动执行「按建议一键改」。\n输出：区分「只读记录」与「写操作」；stub 即可。",
   "skillMapping": "references/optimize.md；破坏性确认",
-  "judgeReferencePaths": ["references/optimize.md"],
-  "commandMustInclude": [["optimize list"], ["--json"]]
+  "judgeReferencePaths": [
+    "references/optimize.md"
+  ],
+  "commandMustInclude": [
+    [
+      "optimize list"
+    ],
+    [
+      "--json"
+    ]
+  ]
 }