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

package/eval/cases/pmax-brand-edit-routing.scenario.json

@@ -0,0 +1,12 @@
+{
+  "id": "pmax-brand-edit-routing",
+  "description": "PMax 改商家名：先 pmax-get，BG 生效时用 pmax-brand-assets-edit",
+  "turns": [
+    "Google 账户 {{EVAL_ACCOUNT_READ}} 的 PMax 活动 campaignId=23856329277，只改商家名为「New Brand Co」，Logo 不动。\n按 SKILL 用 siluzan-tso 执行；需要结构化数据时加 --json-out ./snap-pmax。"
+  ],
+  "judgeExpectation": "路径：应先 `ad pmax-get`（带 --json-out）确认 `_brandGuidelinesActive` 或 brandAssets；BG 生效时改商家名/Logo 须 `ad pmax-brand-assets-edit --patch-file`，不得 `pmax-assets-update` 链接 BUSINESS_NAME/LOGO，不得 `ad campaign-edit`。\n输出：说明改的是 Campaign 级 brandAssets；stub 即可。",
+  "skillMapping": "references/google-ads/pmax-api.md § Brand Guidelines",
+  "judgeReferencePaths": ["references/google-ads/pmax-api.md"],
+  "commandMustInclude": [["pmax-get"], ["pmax-brand-assets-edit"]],
+  "commandMustNotInclude": ["pmax-assets-update", "campaign-edit", "ad campaign-edit"]
+}

package/eval/cases/pmax-edit-not-campaign-edit.scenario.json

@@ -0,0 +1,15 @@
+{
+  "id": "pmax-edit-not-campaign-edit",
+  "description": "改 PMax 日预算须 pmax-edit（勿 campaign-edit）",
+  "turns": [
+    "把 Google 账户 {{EVAL_ACCOUNT_READ}} 的 PMax 活动 23856329277 日预算从 50 调到 80 元。\n按 SKILL 用 siluzan-tso 执行，--json-out ./snap-pmax。"
+  ],
+  "judgeExpectation": "路径：改 PMax 日预算应先 `pmax-get` 取 budgetId，再 `ad pmax-edit`（budget + budgetId 成对）；**不得** `ad campaign-edit`（会 400）。\n输出：说明 PMax 与 Search 系列 API 隔离；stub 即可。",
+  "skillMapping": "references/google-ads/pmax-api.md §4.3",
+  "judgeReferencePaths": [
+    "references/google-ads/pmax-api.md",
+    "references/google-ads/google-ads.md"
+  ],
+  "commandMustInclude": [["pmax-get"], ["pmax-edit"]],
+  "commandMustNotInclude": ["campaign-edit", "ad campaign-edit"]
+}

package/eval/cases/pmax-enable-brand-guidelines.scenario.json

@@ -0,0 +1,15 @@
+{
+  "id": "pmax-enable-brand-guidelines",
+  "description": "存量 PMax 启用 Brand Guidelines",
+  "turns": [
+    "账户 {{EVAL_ACCOUNT_WRITE}} 的 PMax 活动 23856329277 是旧活动，还没开 Brand Guidelines，现在要启用并带上商家名和 Logo（config 已准备好）。\n请用 siluzan-tso 执行，--json-out ./snap-pmax。"
+  ],
+  "judgeExpectation": "路径：存量活动 `_brandGuidelinesActive=false` 时启用 BG 应 `pmax-get` 确认后 `ad pmax-brand-guidelines-enable --config-file`；启用后不可关闭；后续改品牌走 `pmax-brand-assets-edit`。\n输出：说明 enable 与 edit 分工；stub 即可。",
+  "skillMapping": "references/google-ads/pmax-api.md §4.3.1",
+  "judgeReferencePaths": [
+    "references/google-ads/pmax-api.md",
+    "assets/pmax-brand-guidelines-enable-template.md"
+  ],
+  "commandMustInclude": [["pmax-get"], ["pmax-brand-guidelines-enable"]],
+  "commandMustNotInclude": ["campaign-edit", "ad campaign-edit"]
+}

package/eval/cases/pmax-no-assets-update-brand-fields.scenario.json

@@ -0,0 +1,12 @@
+{
+  "id": "pmax-no-assets-update-brand-fields",
+  "description": "BG 生效时禁止用 pmax-assets-update 改 BUSINESS_NAME/LOGO",
+  "turns": [
+    "PMax 活动 23856329277（账户 {{EVAL_ACCOUNT_READ}}）要换 Logo 图片，新 Logo 已准备好 patch JSON。\nBrand Guidelines 已开启。请用 siluzan-tso 正确命令执行，--json-out ./snap-pmax。"
+  ],
+  "judgeExpectation": "路径：用户要在 PMax 上换 Logo 时，若 BG 已生效，应 `pmax-get` 后走 `pmax-brand-assets-edit`，**不得** `pmax-assets-update` 对 AssetGroup PUT LOGO/BUSINESS_NAME（CLI 预检与网关均会 400）。\n输出：说明 Campaign 级品牌与 AssetGroup 素材分离；stub 即可。",
+  "skillMapping": "references/google-ads/pmax-api.md § Brand Guidelines",
+  "judgeReferencePaths": ["references/google-ads/pmax-api.md"],
+  "commandMustInclude": [["pmax-get"], ["pmax-brand-assets-edit"]],
+  "commandMustNotInclude": ["pmax-assets-update"]
+}

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

@@ -10,15 +10,5 @@
     "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,18 +6,6 @@
   ],
   "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,15 +6,6 @@
   ],
   "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,15 +6,6 @@
   ],
   "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,7 +6,5 @@
   ],
   "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,9 +6,7 @@
   ],
   "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,12 +1,8 @@
 {
   "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,12 +6,5 @@
   ],
   "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,7 +6,5 @@
   ],
   "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,9 +6,7 @@
   ],
   "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,15 +6,6 @@
   ],
   "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,7 +6,5 @@
   ],
   "judgeExpectation": "路径：应先阅读 google-ads/google-ads.md 规则流程，再输出可确认的投放方案（地域/语言/预算/系列结构），不得跳过合规与确认直接执行 campaign-create。\n输出：须含可执行的 campaign-create JSON（唯一数据源）+ 从 JSON 推导的 Markdown 说明；关键词写在 KeywordsForBatchJob；方案阶段应说明须 ad campaign-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-analytics-30d-pdf-campaign-device-geo.scenario.json

@@ -6,24 +6,12 @@
   ],
   "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,12 +6,5 @@
   ],
   "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-google-weekly-trends-campaigns-keywords.scenario.json

@@ -6,15 +6,6 @@
   ],
   "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,7 +6,5 @@
   ],
   "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,15 +6,6 @@
   ],
   "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,8 +6,5 @@
   ],
   "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-ops-google-accounts-list-normal.scenario.json

@@ -6,21 +6,6 @@
   ],
   "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,18 +6,6 @@
   ],
   "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-pause-worst-adgroup-confirm.scenario.json

@@ -1,12 +1,8 @@
 {
   "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,23 +1,9 @@
 {
   "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,9 +10,5 @@
     "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,7 +6,5 @@
   ],
   "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,23 +1,9 @@
 {
   "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,15 +6,6 @@
   ],
   "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,20 +1,9 @@
 {
   "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,18 +6,6 @@
   ],
   "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/stub-fixtures/facebook-analysis.json

@@ -9,11 +9,31 @@
   "concurrency": 5,
   "elapsedMs": 4200,
   "results": [
-    { "section": "overview", "ok": true, "elapsedMs": 800, "file": "overview-3995107670753101.json" },
+    {
+      "section": "overview",
+      "ok": true,
+      "elapsedMs": 800,
+      "file": "overview-3995107670753101.json"
+    },
     { "section": "ad-sets", "ok": true, "elapsedMs": 650, "file": "ad-sets-3995107670753101.json" },
-    { "section": "platform", "ok": true, "elapsedMs": 500, "file": "platform-3995107670753101.json" },
+    {
+      "section": "platform",
+      "ok": true,
+      "elapsedMs": 500,
+      "file": "platform-3995107670753101.json"
+    },
     { "section": "country", "ok": true, "elapsedMs": 480, "file": "country-3995107670753101.json" },
-    { "section": "audience", "ok": true, "elapsedMs": 520, "file": "audience-3995107670753101.json" },
-    { "section": "creative", "ok": true, "elapsedMs": 1250, "file": "creative-3995107670753101.json" }
+    {
+      "section": "audience",
+      "ok": true,
+      "elapsedMs": 520,
+      "file": "audience-3995107670753101.json"
+    },
+    {
+      "section": "creative",
+      "ok": true,
+      "elapsedMs": 1250,
+      "file": "creative-3995107670753101.json"
+    }
   ]
 }

package/eval/stub-fixtures/meta-overview.json

@@ -3,7 +3,10 @@
   "schemaVersion": 1,
   "absoluteSnapshotDir": "/tmp/siluzan-eval/snap-meta",
   "manifestFile": "report-manifest-3995107670753101.json",
-  "writtenFiles": ["meta-overview-3995107670753101.json", "meta-overview-3995107670753101.outline.txt"],
+  "writtenFiles": [
+    "meta-overview-3995107670753101.json",
+    "meta-overview-3995107670753101.outline.txt"
+  ],
   "section": "meta-overview",
   "outlineFile": "meta-overview-3995107670753101.outline.txt",
   "agentHint": "禁止 Read 业务 *.json；先 outline schema，再用脚本读 JSON。"

package/eval/stub-fixtures/pmax-asset-group-create-ok.json

@@ -0,0 +1,12 @@
+{
+  "kind": "siluzan-tso-cli-json-snapshot",
+  "schemaVersion": 1,
+  "section": "ad-pmax-asset-group-create-stub",
+  "outlineFile": "ad-pmax-asset-group-create-stub.outline.txt",
+  "payloadPreview": {
+    "id": "98765432199",
+    "name": "AG-Second",
+    "_brandGuidelinesActive": true,
+    "_warnings": ["活动 Brand Guidelines 已生效：businessName/Logo 已被 CLI 忽略"]
+  }
+}