cc-viewer 1.8.0 → 1.8.1

package/dist/index.html

@@ -21,7 +21,7 @@
     // 整体显示大小已弃用 CSS zoom：Electron 改用 webFrame.setZoomFactor（首屏抢占见
     // electron/tab-content-preload.js），纯浏览器交由用户用浏览器自带快捷键缩放，故此处不再设 zoom。
   </script>
-  <script type="module" crossorigin src="./assets/index-C3BRHDVF.js"></script>
+  <script type="module" crossorigin src="./assets/index-CH_N7vvX.js"></script>
   <link rel="modulepreload" crossorigin href="./assets/vendor-antd-CSjy2pdD.js">
   <link rel="modulepreload" crossorigin href="./assets/vendor-codemirror-Clv6kvI5.js">
   <link rel="modulepreload" crossorigin href="./assets/vendor-mdxeditor-CtujsSUV.js">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-viewer",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "Claude Code logging, visualization, and management toolkit — launch a web viewer alongside Claude Code with full request/response tracing, proxy, and mobile support",
   "license": "MIT",
   "main": "server.js",

package/server/lib/builtin-model-prompts.js

@@ -0,0 +1,198 @@
+// 内置模型提示词层：让 packages/app/server/system-prompt-templates/presets/ 的 6 个预设
+// 成为「默认生效」的模型 system prompt——spawn 时模型匹配且用户无对应文件（workspace >
+// global 两级用户文件优先）时自动注入；用户可通过墓碑文件禁用某个内置条目。
+//
+// 数据源复用 system-prompt-presets.js 的 listSystemPromptPresets()（manifest 读取 +
+// renderPresetTemplate 边界剥离都已在里面，且注释承诺不触发 createSystemPromptVariables/
+// git 子进程）。本模块函数对非法入参会 throw（setBuiltinDisabled/materializeBuiltinPrompt），
+// spawn 注入链路的安全由调用点整层 try-catch 保证（system-prompt-files.js 失败回落
+// sentinel，注入链路永不 throw）。
+//
+// Built-in model prompt layer: the shipped presets act as default-effective model
+// system prompts. User files (workspace > global) always win; a per-scope tombstone
+// file disables individual built-in entries.
+import { createHash } from 'node:crypto';
+import { existsSync, mkdirSync, readdirSync, readFileSync, rmSync, statSync, writeFileSync } from 'node:fs';
+import { tmpdir } from 'node:os';
+import { join } from 'node:path';
+import { expandModelIdVariants, normalizeModelName } from './model-system-prompts.js';
+import { listSystemPromptPresets } from './system-prompt-presets.js';
+import { renameSyncWithRetry } from './file-api.js';
+import { reportSwallowed } from '@ccv/core/error-report';
+
+// 墓碑文件名：放在对应 scope 的 modelPromptDir 里，内容是规范大写名的 JSON 数组。
+// parseModelPromptFileName 对非 *_SYSTEM.md 文件名返回 null，天然不干扰条目列表。
+// Tombstone file inside a scope's model-prompt dir: a JSON array of canonical names.
+export const BUILTIN_DISABLED_FILE = '.builtin-disabled.json';
+
+// 物化目录：preset 文本（边界已剥离、${...} 保持字面量，spawn 渲染管线再替换变量）
+// 写成内容寻址的临时文件，供 --system-prompt-file 注入（文件对形式是快照钉扎的前提）。
+// 惰性读取 env 覆盖（测试用）：node --test 多进程并行时共享目录会被彼此的 GC 竞态误删。
+// Materialized temp dir for boundary-stripped preset texts (content-addressed).
+const materializeDir = () => process.env.CCV_BUILTIN_PROMPT_MATERIALIZE_DIR || join(tmpdir(), 'cc-viewer-builtin-prompts');
+
+/**
+ * 列出全部内置模型条目。name = manifest match 的大写规范化（与用户条目同名体系，
+ * 用户同名文件天然形成覆盖）；text = renderPresetTemplate 输出（无边界标记）。
+ * List all built-in model entries derived from the preset manifest.
+ *
+ * @returns {Array<{ id: string, title: string, name: string, mode: 'override'|'append', matchLower: string, text: string }>}
+ */
+export function listBuiltinModelPrompts() {
+  let presets;
+  try {
+    presets = listSystemPromptPresets();
+  } catch {
+    return []; // manifest 损坏等：内置层整体缺席，调用方回落 sentinel
+  }
+  const out = [];
+  for (const p of presets) {
+    const name = normalizeModelName(typeof p?.match === 'string' ? p.match : '');
+    if (!name || typeof p.text !== 'string' || p.text.trim().length === 0) continue;
+    out.push({
+      id: p.id,
+      title: p.title || p.id,
+      name,
+      mode: p.defaultMode === 'override' ? 'override' : 'append',
+      matchLower: p.match.toLowerCase(),
+      text: p.text,
+    });
+  }
+  return out;
+}
+
+/**
+ * 按 modelId 匹配内置条目：别名展开（expandModelIdVariants，先 lowercase）后任一变体
+ * 包含 preset 的 match 即命中；多命中取 match 最长者、等长字典序（对齐 matchModelPrompt
+ * 的消歧规则）。
+ * Match a model id against built-in entries (alias-expanded substring, longest wins).
+ *
+ * @param {string|null} modelId
+ * @returns {{ id: string, name: string, mode: 'override'|'append', text: string } | null}
+ */
+export function matchBuiltinModelPrompt(modelId) {
+  const variants = expandModelIdVariants(modelId);
+  if (!variants.length) return null;
+  const hits = listBuiltinModelPrompts().filter((e) => variants.some((v) => v.includes(e.matchLower)));
+  if (!hits.length) return null;
+  hits.sort((a, b) => b.matchLower.length - a.matchLower.length || a.name.localeCompare(b.name));
+  const e = hits[0];
+  return { id: e.id, name: e.name, mode: e.mode, text: e.text };
+}
+
+/**
+ * 读某 scope 目录的墓碑名单。目录/文件缺失 → []（良性静默）；文件存在但 JSON 损坏或
+ * 形状非法 → console.warn + reportSwallowed 后仍宽容返回 []（fail-open 是刻意的：
+ * 墓碑是辅助状态，宁可恢复注入也不因损坏阻断功能——但用户显式 opt-out 被静默逆转
+ * 必须有诊断痕迹，三方审查一致要求）。
+ * Read a scope dir's tombstone list. Missing dir/file → []; corrupt file → warn +
+ * reportSwallowed, still [] (deliberate fail-open, but never silently).
+ *
+ * @param {string|null|undefined} modelPromptDir
+ * @returns {string[]} 规范大写名数组（已排序）
+ */
+export function readBuiltinDisabled(modelPromptDir) {
+  if (!modelPromptDir) return [];
+  const target = join(modelPromptDir, BUILTIN_DISABLED_FILE);
+  if (!existsSync(target)) return [];
+  try {
+    const raw = readFileSync(target, 'utf-8');
+    const parsed = JSON.parse(raw);
+    if (!Array.isArray(parsed)) throw new Error('tombstone file is not a JSON array');
+    const names = parsed.map((n) => normalizeModelName(typeof n === 'string' ? n : '')).filter(Boolean);
+    return [...new Set(names)].sort();
+  } catch (err) {
+    console.warn(`[CC Viewer] built-in prompt tombstone ${target} unreadable (${err.message}); treating as no disables`);
+    reportSwallowed('builtin-model-prompts.readDisabled', err);
+    return [];
+  }
+}
+
+/**
+ * 写墓碑：disabled=true 把 name 加入名单，false 移出。tmp+rename 原子写，数组去重排序。
+ * Add/remove a name in a scope dir's tombstone list (atomic tmp+rename write).
+ *
+ * @param {string} modelPromptDir 目标 scope 的 modelPromptDir（自动 mkdir -p）
+ * @param {string} name 条目名（经 normalizeModelName 规范化，非法 throw）
+ * @param {boolean} disabled
+ * @returns {{ name: string, disabled: boolean, list: string[] }}
+ */
+export function setBuiltinDisabled(modelPromptDir, name, disabled) {
+  if (!modelPromptDir) throw new Error('no target directory');
+  const canonical = normalizeModelName(name);
+  if (!canonical) throw new Error('invalid model prompt name');
+  const list = readBuiltinDisabled(modelPromptDir);
+  const next = disabled ? [...new Set([...list, canonical])].sort() : list.filter((n) => n !== canonical);
+  mkdirSync(modelPromptDir, { recursive: true });
+  const target = join(modelPromptDir, BUILTIN_DISABLED_FILE);
+  const tmp = `${target}.${process.pid}.tmp`;
+  writeFileSync(tmp, `${JSON.stringify(next, null, 2)}\n`, 'utf-8');
+  renameSyncWithRetry(tmp, target); // Windows 杀软/索引瞬时 EPERM 重试（与仓库写路径一致）
+  return { name: canonical, disabled: !!disabled, list: next };
+}
+
+/**
+ * 多 scope 合成判断：任一目录的墓碑名单含 name 即视为禁用（workspace 墓碑禁本工作区、
+ * global 墓碑全局禁用；对单次启动而言两者都是「该禁」）。
+ * Combine tombstones across scopes: disabled when ANY dir's list contains the name.
+ *
+ * @param {string} name 规范大写名
+ * @param {...(string|null|undefined)} modelPromptDirs
+ * @returns {boolean}
+ */
+export function isBuiltinDisabled(name, ...modelPromptDirs) {
+  const canonical = normalizeModelName(name);
+  if (!canonical) return false;
+  return modelPromptDirs.some((dir) => readBuiltinDisabled(dir).includes(canonical));
+}
+
+/**
+ * 把内置条目文本物化为内容寻址的临时文件（不存在才写，避并发截断；顺手清同 id
+ * 旧 hash 文件）。返回文件路径。
+ * Materialize a built-in entry's text into a content-addressed temp file.
+ *
+ * @param {string} id preset id（文件名安全字符校验）
+ * @param {string} text renderPresetTemplate 输出（边界已剥离、${...} 字面量保留）
+ * @returns {string} 物化文件绝对路径
+ */
+export function materializeBuiltinPrompt(id, text) {
+  if (typeof id !== 'string' || !/^[A-Za-z0-9._-]+$/.test(id)) throw new Error('invalid preset id');
+  if (typeof text !== 'string' || text.trim().length === 0) throw new Error('empty preset text');
+  const hash = createHash('sha256').update(text).digest('hex').slice(0, 8);
+  const fileName = `${id}-${hash}.md`;
+  const dir = materializeDir();
+  mkdirSync(dir, { recursive: true, mode: 0o700 }); // 仅属主可读写：Linux 多用户 /tmp 下防跨用户预植
+  const target = join(dir, fileName);
+  // write-if-absent 必须回读校验内容 hash：可预测路径 + 预置恶意文件（hash 可算，
+  // preset 文本随包公开）会把注入内容掉包——不一致则覆盖。写入用 tmp+rename 原子落盘，
+  // 进程在写中途崩溃留下截断文件时 write-if-absent 永不愈合。
+  const writeAtomic = () => {
+    const tmp = `${target}.${process.pid}.tmp`;
+    writeFileSync(tmp, text, 'utf-8');
+    renameSyncWithRetry(tmp, target);
+  };
+  if (!existsSync(target)) {
+    writeAtomic();
+  } else {
+    try {
+      const existing = readFileSync(target, 'utf-8');
+      if (createHash('sha256').update(existing).digest('hex').slice(0, 8) !== hash) writeAtomic();
+    } catch {
+      writeAtomic(); // 读失败（截断/权限）→ 覆盖重写
+    }
+  }
+  // best-effort GC：同 id 的旧 hash 文件（版本升级后残留）。精确匹配 8 位 hex hash 防
+  // id 前缀误删（如未来 kimi-k3-turbo）；只清 mtime 足够旧的文件，避免跨版本并发
+  // （新旧实例同跑）时删掉旧实例正要读的文件。失败无碍。
+  try {
+    const idRe = new RegExp(`^${id.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')}-[0-9a-f]{8}\\.md$`);
+    for (const f of readdirSync(dir)) {
+      if (!idRe.test(f) || f === fileName) continue;
+      const p = join(dir, f);
+      try {
+        if (Date.now() - statSync(p).mtimeMs > 10 * 60_000) rmSync(p, { force: true });
+      } catch { /* ignore */ }
+    }
+  } catch { /* ignore */ }
+  return target;
+}

package/server/lib/launch-config.js

@@ -108,6 +108,10 @@ export function suppressManuallyFlaggedPinned(entries, userArgs) {
 // The F2 no-record notice only matters to users who HAVE injection configured right
 // now (sentinel files or a model-prompt dir) — for everyone else a resume silently
 // injecting nothing is exactly the status quo, and the line would be pure noise.
+// Fidelity note (accepted gap): this check does NOT see the built-in preset layer —
+// users whose only injection is a default-effective built-in (no dirs, no sentinels)
+// get no F2 notice on resume either. Deliberate: making built-in hits count would turn
+// the notice into near-constant noise for every built-in user resuming old sessions.
 export function injectionConfigured(spawnDir, logDir = LOG_DIR) {
   try {
     return isNonEmptyFile(join(spawnDir, SYSTEM_PROMPT_FILE))
@@ -152,7 +156,7 @@ function _defaultModelReader(spawnDir, env, opts) {
  *   sysPrompt: {args: string[], loaded: string[], model: string|null, entries: object[], suppressed?: string, pinned?: boolean, noRecord?: boolean, noRecordNotice?: boolean},
  *   resume: object|null,
  *   resolvedModelId: string|null,
- *   diagnostic: null|'no-match'|'no-model',
+ *   diagnostic: null|'no-match'|'no-model'|'builtin-disabled',
  * }}
  */
 export function resolveLaunchSystemPrompt(p) {
@@ -222,6 +226,10 @@ export function resolveLaunchSystemPrompt(p) {
     });
     if (suppressInjection) {
       sysPrompt = { args: [], loaded: [], model: null, entries: [] };
+    } else if (sysPrompt.builtinDisabled) {
+      // The resolved model hit a built-in preset that the user tombstone-disabled —
+      // distinct from 'no-match' (a likely misnamed file): this is an intentional opt-out.
+      out.diagnostic = 'builtin-disabled';
     } else if (resolvedModelId && !sysPrompt.model && !sysPrompt.suppressed
       && (existsSync(join(spawnDir, MODEL_PROMPT_DIR)) || existsSync(join(logDir, MODEL_PROMPT_DIR)))) {
       // A system_prompt dir is configured but the resolved model matched no entry

package/server/lib/model-system-prompts.js

@@ -261,10 +261,26 @@ function modelIdVariants(id) {
   return MODEL_ID_ALIASES[id] || [id];
 }
 
+// 供内置预设匹配复用的导出包装：入参任意大小写，先剥 `[1m]` 类方括号后缀
+// （spawn 渲染管线对 model.name 做同样的剥离；上游 resolver 正常会剥，这里兜底），
+// 再 toLowerCase 展开别名——避免大写 env（如 K3）或带后缀的裸名（k3[1m]）绕过别名表。
+// 单一别名源，勿在别处复制 MODEL_ID_ALIASES。
+// Exported wrapper for the built-in preset matcher: strips a trailing bracket suffix
+// and lowercases before expanding, so uppercase ids (K3) or suffixed shorthands
+// (k3[1m]) cannot bypass the alias table.
+export function expandModelIdVariants(modelId) {
+  if (!modelId || typeof modelId !== 'string') return [];
+  const stripped = modelId.replace(/\s*\[[^\]]*\]$/, '').toLowerCase();
+  return modelIdVariants(stripped);
+}
+
 export function matchModelPrompt(modelId, candidates) {
   if (!modelId || typeof modelId !== 'string') return null;
   if (!Array.isArray(candidates)) return null;
-  const variants = modelIdVariants(modelId.toLowerCase());
+  // 与内置层（builtin-model-prompts.js）同一展开：剥 `[1m]` 类后缀 + lowercase + 别名。
+  // 若用户层不剥后缀而内置层剥（k3[1m] + 用户有 KIMI-K3_SYSTEM.md），用户文件会
+  // 静默 miss、内置反客为主 —— 违反「用户文件永远优先」，两层必须同语义。
+  const variants = expandModelIdVariants(modelId);
   for (const cand of candidates) {
     if (!cand || !cand.dir) continue;
     const hits = listModelPrompts(cand.dir).filter((e) => {

package/server/lib/system-prompt-files.js

@@ -1,7 +1,9 @@
 import { readFileSync, writeFileSync, rmSync } from 'node:fs';
 import { join } from 'node:path';
 import { MODEL_PROMPT_DIR, matchModelPrompt } from './model-system-prompts.js';
+import { isBuiltinDisabled, matchBuiltinModelPrompt, materializeBuiltinPrompt } from './builtin-model-prompts.js';
 import { isNonEmptyFile } from './file-api.js';
+import { reportSwallowed } from '@ccv/core/error-report';
 
 // isNonEmptyFile lives in file-api.js (shared leaf, cycle break:
 // model-system-prompts.js must not import this module). Re-exported here so
@@ -42,22 +44,28 @@ export function hasArg(args, ...names) {
  *
  * 模型定制(opts.modelId 提供时)：先在 <projectDir>/system_prompt/(工作区)与
  * opts.globalModelDir(全局)里做模糊匹配；命中的条目「整体取代」上面两份默认 sentinel
- * ——即便手动 flag 抑制了注入也不再回看默认文件(条目已取而代之)。未命中/无 modelId
- * 则完全走旧逻辑。
+ * ——即便手动 flag 抑制了注入也不再回看默认文件(条目已取而代之)。未命中则进入内置层：
+ * 随包 presets(builtin-model-prompts.js)按同语义再匹配一次，命中且未被墓碑禁用时把
+ * preset 文本物化为临时文件注入；命中被禁用(builtinDisabled)或未命中才回落 sentinel。
  *
  * Decide whether to inject system-prompt file flags based on sentinel files in
  * the launch directory. When opts.modelId is given, model-specific entries in
  * the workspace/global system_prompt folders are matched first; a match fully
- * supersedes the Default sentinels. Pure function: reads fs/env only.
+ * supersedes the Default sentinels. Without a file match, shipped built-in presets
+ * act as the fallback layer (tombstone-disabled ones are skipped). Reads fs/env;
+ * writes materialized built-in temp files; the built-in layer never throws — any
+ * failure falls back to the sentinel logic via reportSwallowed.
  *
  * @param {string} projectDir 启动目录(绝对路径)
  * @param {string[]} [existingArgs] 已有的 claude 参数(用于「手动优先」判断)
  * @param {Object} [env] 环境变量(默认 process.env)
  * @param {{ modelId?: string|null, globalModelDir?: string|null }} [opts]
- * @returns {{ args: string[], loaded: string[], model: string|null, suppressed?: 'env'|'manual-flag' }}
+ * @returns {{ args: string[], loaded: string[], model: string|null, suppressed?: 'env'|'manual-flag',
+ *          builtinDisabled?: string }}
  *          args: 待追加参数；loaded: 实际加载的文件(终端提示)；model: 命中的条目名(未命中为 null)；
  *          suppressed: 注入被有意跳过的原因(env 开关 / 手动同义 flag 抑制了已命中的模型条目)——
  *          调用方(pty-manager)据此不再打「no matching entry」误导性告警。
+ *          builtinDisabled 仅在内置层命中但被墓碑禁用时出现(增量字段，否则不存在)。
  */
 export function buildSystemPromptFileArgs(projectDir, existingArgs = [], env = process.env, opts = {}) {
   const out = { args: [], loaded: [], model: null };
@@ -81,8 +89,37 @@ export function buildSystemPromptFileArgs(projectDir, existingArgs = [], env = p
       }
       return out; // 命中即返回：默认 sentinel 不再参与(含手动 flag 抑制注入的情况)。
     }
+    // 用户文件未命中 → 内置层(随包 presets)：同语义匹配 + 墓碑检查；命中即物化注入并
+    // 提前返回(同样取代 sentinel)。整层 try-catch：任何失败(preset 缺失/tmp 不可写)经
+    // reportSwallowed 回落 sentinel——内置不可用绝不应连默认注入都拖垮。
+    // No file match → built-in fallback layer (shipped presets, tombstone-aware).
+    try {
+      const builtin = matchBuiltinModelPrompt(opts.modelId);
+      if (builtin) {
+        const flagPair = builtin.mode === 'override'
+          ? ['--system-prompt', '--system-prompt-file']
+          : ['--append-system-prompt', '--append-system-prompt-file'];
+        if (hasArg(existingArgs, ...flagPair)) {
+          out.suppressed = 'manual-flag'; // 与文件命中同语义：有意跳过，非「无条目」
+          return out; // 手动抑制也提前返回(不物化、不回看 sentinel)
+        }
+        const workspaceModelDir = join(projectDir, MODEL_PROMPT_DIR);
+        if (isBuiltinDisabled(builtin.name, workspaceModelDir, opts.globalModelDir)) {
+          out.builtinDisabled = builtin.name; // 供 launch-config 区分「被禁用」与「无条目」
+          // 落回 sentinel（不 return）
+        } else {
+          const path = materializeBuiltinPrompt(builtin.id, builtin.text);
+          out.args.push(flagPair[1], path);
+          out.loaded.push(`builtin:${builtin.name}`); // 稳定标签，不打印 tmp 丑路径
+          out.model = builtin.name;
+          return out;
+        }
+      }
+    } catch (err) {
+      reportSwallowed('system-prompt-files.builtin', err);
+    }
     // No matching entry: fall through to the default sentinels. Diagnostics for
-    // this case live in the caller (pty-manager) — this stays a pure function.
+    // this case live in the caller (launch-config/pty-manager).
   }
 
   // 整段替换：CC_SYSTEM.md → --system-prompt-file (用户已传 --system-prompt[-file] 则跳过)

package/server/pty-manager.js

@@ -390,8 +390,9 @@ async function _spawnClaudeImpl(proxyPort, cwd, extraArgs = [], claudePath = nul
   // When the launch dir has a non-empty CC_SYSTEM.md / CC_APPEND_SYSTEM.md, auto-append
   // --system-prompt-file / --append-system-prompt-file (each independent; skipped if the
   // user already passed the synonymous flag). Model customization: fuzzy-match against
-  // <cwd>/system_prompt/ and <LOG_DIR>/system_prompt/ using "the model used on the last
-  // launch"; a matched entry wholly replaces the two default sentinels above.
+  // <cwd>/system_prompt/ and <LOG_DIR>/system_prompt/ using the model id resolved from the
+  // ACTIVE configuration (proxy profile mapping > env > settings.json); a matched entry
+  // (user file first, then built-in presets) wholly replaces the two default sentinels above.
   // Note: currentWorkspacePath is only assigned below, so the cwd param decides the launch
   // dir here. Spawns inside LOG_DIR (IM worker working dir = <LOG_DIR>/IM_<id>/) skip model
   // matching: the IM persona relies on the default sentinel CC_APPEND_SYSTEM.md injection,
@@ -425,7 +426,9 @@ async function _spawnClaudeImpl(proxyPort, cwd, extraArgs = [], claudePath = nul
       suppressInjection: _systemPromptFileRejectedPaths.has(claudePath) || skipOnce,
     });
     sysPrompt = r.sysPrompt;
-    if (r.diagnostic === 'no-match') {
+    if (r.diagnostic === 'builtin-disabled') {
+      console.warn(`[CC Viewer] model-specific prompt: built-in prompt "${r.sysPrompt.builtinDisabled}" for modelId="${r.resolvedModelId}" is disabled via .builtin-disabled.json in the workspace or global ${MODEL_PROMPT_DIR}/ — falling back to defaults`);
+    } else if (r.diagnostic === 'no-match') {
       console.warn(`[CC Viewer] model-specific prompt: modelId="${r.resolvedModelId}" resolved from active config but no matching entry found in workspace or global ${MODEL_PROMPT_DIR}/`);
     } else if (r.diagnostic === 'no-model') {
       console.warn(`[CC Viewer] model-specific prompt: no model id resolved from active config (--settings / env / settings.json / proxy profile) — entries in ${MODEL_PROMPT_DIR}/ skipped for this launch`);

package/server/routes/expert.js

@@ -15,6 +15,11 @@ import {
   MODEL_PROMPT_DIR, normalizeModelName, listModelPrompts,
   writeModelPrompt, deleteModelPrompt, matchModelPrompt,
 } from '../lib/model-system-prompts.js';
+import {
+  matchBuiltinModelPrompt, isBuiltinDisabled,
+  readBuiltinDisabled, setBuiltinDisabled, listBuiltinModelPrompts,
+} from '../lib/builtin-model-prompts.js';
+import { reportSwallowed } from '@ccv/core/error-report';
 import { resolveSpawnModel } from '../lib/spawn-model-resolver.js';
 import { listSystemPromptPresets, groupPresetsByCategory, getSystemPromptVariablesDoc } from '../lib/system-prompt-presets.js';
 import { LOG_DIR } from '../../findcc.js';
@@ -41,12 +46,24 @@ function sendJson(res, code, obj) {
   } catch { /* socket 已关闭：忽略 */ }
 }
 
+// scope → 目标 modelPromptDir 的统一解析（postModelPrompts 普通分支与墓碑分支共用）：
+// global 直取 LOG_DIR；workspace 需活动工作区（缺失返回 {error} 由调用方回 400）。
+async function resolveScopeModelDir(deps, scope) {
+  if (scope === 'global') return { dir: join(LOG_DIR, MODEL_PROMPT_DIR) };
+  const dir = await resolveDir(deps);
+  if (!dir) return { error: 'no_active_workspace' };
+  return { dir: join(dir, MODEL_PROMPT_DIR) };
+}
+
 // Single source for "is a custom system prompt configured to inject" — mirrors the
 // spawn-time injection semantics of buildSystemPromptFileArgs: the env kill switch wins;
 // a matched model entry supersedes the Default sentinels for activation purposes.
 // Fidelity note: spawn-only gates this helper cannot see (insideLogDir skip, manual
 // --system-prompt-file flags, one-shot skip tokens) may rarely make "active" a false
-// positive — acceptable for a UI hint.
+// positive — acceptable for a UI hint. The built-in layer shares the same gates, and
+// can also false-NEGATIVE the other way: when the spawn-time model signal comes from
+// launchSettings (launcher-delivered ANTHROPIC_MODEL), this resolver may see no model
+// while spawn still injects a built-in preset (entry stays hidden). Same acceptance.
 function computeSystemPromptStatus(dir) {
   if (process.env[DISABLE_AUTO_SYSTEM_PROMPT_ENV] === '1') {
     return { active: false, modelId: null, matched: null, defaultActive: false };
@@ -61,8 +78,28 @@ function computeSystemPromptStatus(dir) {
         { dir: join(LOG_DIR, MODEL_PROMPT_DIR), scope: 'global' },
       ])
     : null;
-  const matched = match ? { scope: match.scope, name: match.name, mode: match.mode } : null;
-  return { active: !!matched || defaultActive, modelId, matched, defaultActive };
+  let matched = match ? { scope: match.scope, name: match.name, mode: match.mode } : null;
+  // 内置层镜像 spawn 语义：用户文件未命中时，内置 preset 命中（未禁用）同样构成注入；
+  // 命中被墓碑禁用则报 builtinDisabled（条件字段，仅此时出现，命名与 spawn 返回字段
+  // 对齐）——UI 据此让入口以「已禁用」态保活，点入可重启用，否则 chip 消失后无法找回禁用开关。
+  let builtinDisabledEntry;
+  if (!matched && modelId) {
+    try {
+      const builtin = matchBuiltinModelPrompt(modelId);
+      if (builtin) {
+        if (isBuiltinDisabled(builtin.name, dir ? join(dir, MODEL_PROMPT_DIR) : null, join(LOG_DIR, MODEL_PROMPT_DIR))) {
+          builtinDisabledEntry = { name: builtin.name };
+        } else {
+          matched = { scope: 'builtin', name: builtin.name, mode: builtin.mode };
+        }
+      }
+    } catch (err) {
+      reportSwallowed('expert.systemPromptStatus.builtin', err);
+    }
+  }
+  const out = { active: !!matched || defaultActive, modelId, matched, defaultActive };
+  if (builtinDisabledEntry) out.builtinDisabled = builtinDisabledEntry;
+  return out;
 }
 
 async function getSystemText(req, res, parsedUrl, isLocal, deps) {
@@ -124,12 +161,26 @@ async function getModelPrompts(req, res, parsedUrl, isLocal, deps) {
     const dir = await resolveDir(deps);
     const globalDir = join(LOG_DIR, MODEL_PROMPT_DIR);
     const status = computeSystemPromptStatus(dir);
+    // 内置 preset 条目（默认生效层）：text 为 renderPresetTemplate 输出（边界已剥离），
+    // disabled 双 scope 墓碑标志供弹窗渲染禁用态/重启用。
+    const workspaceModelDir = dir ? join(dir, MODEL_PROMPT_DIR) : null;
+    const disabledWs = readBuiltinDisabled(workspaceModelDir);
+    const disabledG = readBuiltinDisabled(globalDir);
+    const builtin = listBuiltinModelPrompts().map((e) => ({
+      id: e.id,
+      title: e.title,
+      name: e.name,
+      mode: e.mode,
+      text: e.text,
+      disabled: { workspace: disabledWs.includes(e.name), global: disabledG.includes(e.name) },
+    }));
     sendJson(res, 200, {
       workspaceDir: dir || null,
       workspaceActive: !!dir,
       globalDir,
       workspace: dir ? collectModelEntries(join(dir, MODEL_PROMPT_DIR)) : [],
       global: collectModelEntries(globalDir),
+      builtin,
       // 当前生效配置解析出的模型 id 及其命中的条目(未命中为 null)——弹窗据此把默认页签
       // 指向命中条目；matched.name 为规范化大写名，与页签 key 的构成一致。
       modelId: status.modelId,
@@ -162,29 +213,39 @@ function postModelPrompts(req, res, parsedUrl, isLocal, deps) {
   req.on('end', async () => {
     if (truncated) return; // 超限已 destroy，socket 关闭，勿再解析/回包(对齐 postSystemText)
     try {
-      const { scope, name, mode, text } = JSON.parse(body || '{}');
+      const { scope, name, mode, text, action } = JSON.parse(body || '{}');
       if (scope !== 'workspace' && scope !== 'global') {
         sendJson(res, 400, { error: 'bad_scope' });
         return;
       }
       const canonical = normalizeModelName(name);
       if (!canonical) { sendJson(res, 400, { error: 'bad_model_name' }); return; }
-      let targetDir;
-      if (scope === 'global') {
-        targetDir = join(LOG_DIR, MODEL_PROMPT_DIR);
-      } else {
-        const dir = await resolveDir(deps);
-        if (!dir) { sendJson(res, 400, { error: 'no_active_workspace' }); return; }
-        targetDir = join(dir, MODEL_PROMPT_DIR);
+      const target = await resolveScopeModelDir(deps, scope);
+      if (target.error) { sendJson(res, 400, { error: target.error }); return; }
+      // 墓碑操作（禁用/启用内置 preset 条目）。action 存在但非法 → 400 兜底：
+      // 拼错的 action 绝不可 fall-through 到下面的「空 text = 删除用户条目」分支。
+      if (action !== undefined) {
+        if (action !== 'disable-builtin' && action !== 'enable-builtin') {
+          sendJson(res, 400, { error: 'bad_action' });
+          return;
+        }
+        if (!listBuiltinModelPrompts().some((e) => e.name === canonical)) {
+          sendJson(res, 400, { error: 'unknown_builtin' });
+          return;
+        }
+        const disabled = action === 'disable-builtin';
+        setBuiltinDisabled(target.dir, canonical, disabled);
+        sendJson(res, 200, { ok: true, scope, name: canonical, disabled });
+        return;
       }
       const raw = typeof text === 'string' ? text : '';
       if (raw.trim().length === 0) {
         // 空文本 = 删除条目(对齐 system-text 的「存空即禁用」约定；此时 mode 可缺省)。
-        deleteModelPrompt(targetDir, canonical);
+        deleteModelPrompt(target.dir, canonical);
         sendJson(res, 200, { ok: true, name: canonical, scope, cleared: true });
         return;
       }
-      const result = writeModelPrompt(targetDir, canonical, mode === 'override' ? 'override' : 'append', raw);
+      const result = writeModelPrompt(target.dir, canonical, mode === 'override' ? 'override' : 'append', raw);
       sendJson(res, 200, { ok: true, scope, ...result });
     } catch (e) {
       console.error('[CC Viewer] expert model-prompts POST failed:', e.message);

package/ultraAgents/README.md

@@ -48,6 +48,8 @@ in `src/utils/ultraplanTemplates.js`). Preset `content` should therefore be writ
 > `src/utils/ultraplanTemplates.js`'s `ULTRAPLAN_VARIANTS.codeExpert` / `researchExpert`,
 > and is pinned byte-for-byte by `test/ultra-agents-api.test.js` — to change the body, edit that
 > source file and regenerate the JSON in this directory; do not hand-write a second copy here.
+> Other presets (e.g. `test-analysis-expert`) are authored standalone in this directory and have
+> no template source.
 
 ## Validation and Limits
 
@@ -66,6 +68,7 @@ Each file undergoes defensive validation at load time. Invalid files are skipped
 | --- | --- | --- | --- |
 | `code-expert.json` | Code Expert / 代码专家 | Inline localized (all 18 languages) | `ULTRAPLAN_VARIANTS.codeExpert` |
 | `research-expert.json` | Research Expert / 调研专家 | Inline localized (all 18 languages) | `ULTRAPLAN_VARIANTS.researchExpert` |
+| `test-analysis-expert.json` | Test Analysis Expert / 测分专家 | Inline localized (all 18 languages) | standalone (authored here; UI-only Midscene.js YAML test-case generation, generation-only) |
 
 To add a new preset: drop a new `*.json` file in this directory (file name should match `id`),
 and restart/refresh to see it in the modal.

package/ultraAgents/test-analysis-expert.json

@@ -0,0 +1,45 @@
+{
+  "id": "test-analysis-expert",
+  "version": 1,
+  "title": {
+    "zh": "测分专家",
+    "en": "Test Analysis Expert",
+    "zh-TW": "測試分析專家",
+    "ko": "테스트 분석 전문가",
+    "ja": "テスト分析エキスパート",
+    "de": "Testanalyse-Experte",
+    "es": "Experto en análisis de pruebas",
+    "fr": "Expert en analyse de tests",
+    "it": "Esperto di analisi dei test",
+    "da": "Testanalyseekspert",
+    "pl": "Ekspert analizy testów",
+    "ru": "Эксперт по анализу тестирования",
+    "ar": "خبير تحليل الاختبارات",
+    "no": "Testanalyseekspert",
+    "pt-BR": "Especialista em análise de testes",
+    "th": "ผู้เชี่ยวชาญการวิเคราะห์การทดสอบ",
+    "tr": "Test analiz uzmanı",
+    "uk": "Експерт з аналізу тестування"
+  },
+  "description": {
+    "zh": "测试分析专家：多智能体素材分析 + Midscene YAML 用例生成，产出 UI 测试分析报告与自动化用例，只生成不执行。",
+    "en": "Test analysis expert: multi-agent materials analysis and Midscene.js YAML flow generation — produces a UI test-analysis report and automation cases; generation only, no execution.",
+    "zh-TW": "測試分析專家：多智能體素材分析 + Midscene YAML 用例產生，產出 UI 測試分析報告與自動化用例，只產生不執行。",
+    "ko": "테스트 분석 전문가: 멀티 에이전트 자료 분석 + Midscene YAML 케이스 생성 — UI 테스트 분석 보고서와 자동화 케이스를 산출하며, 실행 없이 생성만 합니다.",
+    "ja": "テスト分析エキスパート：マルチエージェント素材分析 + Midscene YAML フロー生成 — UI テスト分析レポートと自動化ケースを生成、実行は行いません。",
+    "de": "Testanalyse-Experte: Multi-Agenten-Materialanalyse und Midscene-YAML-Flow-Generierung – erstellt einen UI-Testanalysebericht und Automatisierungsfälle; nur Generierung, keine Ausführung.",
+    "es": "Experto en análisis de pruebas: análisis de materiales multiagente y generación de flujos YAML de Midscene.js — produce un informe de análisis de pruebas UI y casos de automatización; solo generación, sin ejecución.",
+    "fr": "Expert en analyse de tests : analyse des matériaux multi-agents et génération de flux YAML Midscene.js — produit un rapport d'analyse de tests UI et des cas d'automatisation ; génération uniquement, sans exécution.",
+    "it": "Esperto di analisi dei test: analisi dei materiali multi-agente e generazione di flussi YAML Midscene.js — produce un report di analisi dei test UI e casi di automazione; solo generazione, nessuna esecuzione.",
+    "da": "Testanalyseekspert: multi-agent-materialeanalyse og Midscene.js YAML-flow-generering — producerer en UI-testanalyserapport og automatiseringscases; kun generering, ingen eksekvering.",
+    "pl": "Ekspert analizy testów: wieloagentowa analiza materiałów i generowanie przepływów YAML Midscene.js — tworzy raport analizy testów UI i przypadki automatyzacji; tylko generowanie, bez wykonywania.",
+    "ru": "Эксперт по анализу тестирования: мультиагентный анализ материалов и генерация YAML-потоков Midscene.js — формирует отчёт по анализу UI-тестирования и автоматизированные кейсы; только генерация, без выполнения.",
+    "ar": "خبير تحليل الاختبارات: تحليل المواد متعدد الوكلاء وتوليد تدفقات YAML لـ Midscene.js — يُنتج تقرير تحليل اختبارات واجهة المستخدم وحالات أتمتة؛ توليد فقط دون تنفيذ.",
+    "no": "Testanalyseekspert: multi-agent materialeanalyse og Midscene.js YAML-flytgenerering — produserer en UI-testanalyserapport og automatiseringscaser; kun generering, ingen kjøring.",
+    "pt-BR": "Especialista em análise de testes: análise de materiais multiagente e geração de fluxos YAML do Midscene.js — produz um relatório de análise de testes de UI e casos de automação; apenas geração, sem execução.",
+    "th": "ผู้เชี่ยวชาญการวิเคราะห์การทดสอบ: วิเคราะห์เอกสารแบบหลายเอเจนต์และสร้างโฟลว์ YAML ของ Midscene.js — สร้างรายงานการวิเคราะห์การทดสอบ UI และกรณีทดสอบอัตโนมัติ สร้างอย่างเดียวไม่รัน",
+    "tr": "Test analiz uzmanı: çok aracılı malzeme analizi ve Midscene.js YAML akışı üretimi — UI test analiz raporu ve otomasyon senaryoları üretir; yalnızca üretim, çalıştırma yok.",
+    "uk": "Експерт з аналізу тестування: мультиагентний аналіз матеріалів і генерація YAML-потоків Midscene.js — створює звіт аналізу UI-тестування та кейси автоматизації; лише генерація, без виконання."
+  },
+  "content": "<system-reminder>\n[SCOPED INSTRUCTION] The following instructions apply only to the next 1–3 interactions. Once the task is complete, these instructions should gradually decrease in priority and no longer affect subsequent interactions. You should be adept at utilizing tools such as `AskUserQuestion`, `EnterPlanMode`, and `Agent`, rather than relying solely on plain text processing. Before execution, you must ensure that the `EnterPlanMode`, `ExitPlanMode`, `TaskCreate`, `TaskUpdate`, `TaskStop`, `TaskGet`, `TaskOutput` and `TaskList` tools are loaded.\n\nPre-requisite: Use `AskUserQuestion` to clarify the target UI scope (modules, pages, key flows), the case-text language, and the output directory whenever the request is ambiguous. Skip only if the intent is unambiguous.\n\nYou are a UI test-analysis expert. Your only deliverables are (a) a markdown test-analysis report (including validation notes) and (b) Midscene.js YAML automation flows (github.com/web-infra-dev/midscene). Hard rules:\n- UI layer only: do not produce API-level or unit-level test points or code.\n- Generation only: NEVER execute the YAML flows, a midscene runner, Playwright, or any browser automation; validation is by reading and cross-checking.\n- Case text inside YAML files follows the case-text language clarified at intake (default: the language of the source materials).\n\nLeverage a multi-agent exploration mechanism to formulate an exceptionally detailed test analysis.\n\nInstructions:\n1. Materials intake — the analysis requires these materials; confirm each given path actually exists and never fabricate contents:\n- REQUIRED: (a) system-analysis docs; (b) requirements docs; (c) the code repository of the system under test; (d) environment context (target URLs, accounts, viewport, midscene model configuration).\n- OPTIONAL: existing test assets (style reference + dedup), prototypes/design drafts or page snapshots, defect/risk history.\n- If any REQUIRED material is missing, use `AskUserQuestion` before continuing (offer: user supplies the path / proceed with assumptions recorded in the report / narrow the scope). Missing optional materials are noted in the report and do not block.\n\n2. Use the `Agent` tool to spawn parallel agents that analyze the materials from different angles:\n- Requirements deconstruction: testable behaviors, roles, preconditions, acceptance criteria; flag ambiguities and conflicts; assign each requirement item a stable requirement ID.\n- System-analysis mapping: pages, flows and state models (state x event x action x result); identify stateful lifecycles.\n- Code grounding: map requirement behaviors to concrete pages/routes/components in the repository; extract the exact visible UI copy/labels as assertion material; flag requirement-vs-code mismatches (when UI copy in code conflicts with the specification, the specification wins and the case is marked as a suspected bug); also flag behaviors found in code but absent from the specification (spec-silent), to be handled per the anti-oracle guardrail.\n- Environment completeness: verify the environment context fully specifies a midscene target (url, viewport, model configuration); list gaps; determine the login strategy per flow group: (a) `cookie` (path to a JSON cookie file) in the environment segment when provided, or (b) a first `task` acting as the login setup flow, or (c) login treated as an out-of-scope precondition recorded in the handoff notes.\n- (Only when test assets exist) Asset inventory: style conventions and a dedup list.\nYou may add other roles or deploy additional agents beyond the ones listed above; the maximum number of concurrently dispatched agents is 5.\n\n3. Synthesize the findings from all agents into a test-analysis report (markdown). The report must include:\n- A traceability matrix: requirement ID to test point(s).\n- The test-point list with fixed fields: ID | requirement ID(s) | page/flow | behavior under test | input/precondition (including entry state: login role, seed data) | expected result (grounded in the requirements) | design technique | priority | YAML file (backfilled in step 4).\n- The design technique for each test point, chosen by these decision rules (not definitions):\n  pure input domains to equivalence partitioning + boundary values (template: min-1/min/min+1/max-1/max/max+1);\n  multi-condition business rules to decision tables;\n  lifecycle state machines (orders, sessions, wizards) to state-transition testing;\n  more than 3 parameters that cannot be exhaustively combined to pairwise;\n  tight time or broad scope to risk table, top-N first;\n  default (display/copy/navigation points matching no technique): scenario-based, at least one happy-path case per requirement item, exception paths on demand.\n- Risk ranking (impact x probability) and a list of known non-goals.\nRe-read the report once against the intake materials, then submit it as the plan via `ExitPlanMode`. Once `ExitPlanMode` returns a result:\n- If approved: proceed to generate the YAML flows in this session.\n- If rejected: revise the report based on the feedback provided and call `ExitPlanMode` again.\n- If an error occurs (including receiving a \"Not in Plan Mode\" message): do **not** follow the suggestions provided in the error message; instead, prompt the user for further instructions.\n\n4. Generate the YAML flows (only after approval):\n- One YAML file per page/flow group; at least one `task` per test point; embed the test-point ID in the task name (e.g. `name: TP-012 login-empty-password`). A test point whose technique yields multiple attempts (BVA's six boundary values, decision-table rows, pairwise combinations) may either run several attempt -> assert -> reset cycles inside ONE task - each cycle re-establishing its own entry state via reload/navigation so no step depends on a previous attempt's end state - or split into suffixed tasks (`TP-012-1` ... `TP-012-n`); the convention used must be stated in the report.\n- File skeleton: an environment segment (`page:` is the recommended key, with `url`, `viewportWidth`/`viewportHeight` - default 1440x800 - plus `userAgent`/`cookie` (path to a JSON cookie file)/`output` only when the environment context requires them; `web:` remains supported as a compatibility entry but is discouraged for new files; `browser:` (multi-tab flows) and the optional `agent:` section (testId, reportFileName) are documented keys, acceptable when the environment context requires them; NEVER the deprecated `target:`; never mix `page`/`browser`/`web`/`target`) followed by `tasks:`. Structural rule: every task's steps live under that task's `flow:` key, and a task may only carry `name`/`continueOnError`/`flow`:\n  tasks:\n    - name: TP-012 login-empty-password\n      flow:\n        - aiTap: 'the blue Login button at the top right'\n- Flow granularity: each `-` step is ONE user-visible action in the case-text language; use instant actions (`aiTap`, `aiHover`, `aiInput`+`value`, `aiKeyboardPress`+`keyName`, `aiScroll`) for single-element operations and `ai`/`aiAct` only for multi-step or conditional actions; prompts describe elements visually (appearance + position, e.g. \"the blue Login button at the top right\"), never by DOM/selectors/xpath; YAML string hygiene: wrap every prompt/value/errorMessage string in single quotes - any string containing `: ` (colon+space), `#`, or leading/trailing spaces MUST be quoted or YAML parsing fails; `aiQuery` prompts must state the result format and carry a `name`; every flow ends with at least one `aiAssert` whose prompt states requirement-grounded visible text or state (optionally `errorMessage` carrying the test-point ID); prefer `aiWaitFor` (waits for a condition, default 30000ms, raise `timeout` when needed) for asynchronous UI and use `sleep` only for fixed-duration animation/throttle waits; `aiBoolean` may check a visible state mid-flow; `javascript` only for UI-state preconditions not reachable via `ai*` actions (e.g. seeding login state or localStorage), never for assertions.\n- Every flow is self-contained: it starts from a reachable entry page and never depends on the end state of a previous task or file; record the navigation chain in the test point's precondition.\n- Secrets and accounts are referenced as `${VAR}` placeholders documented in the handoff notes - never hardcode credentials.\n- Create one task per YAML file with `TaskCreate` (subject = relative path) and move it through in_progress to completed with `TaskUpdate` as generation and review fixes land; backfill the report's YAML-file column.\n- **Anti-oracle-compliance guardrail (most important):** expected results come from the requirements/system-analysis docs - NEVER derive an expectation from the implementation's current behavior. Because nothing is ever executed, 'implementation behavior' can only mean what the code-grounding agent read in the repository (UI copy, conditional rendering, validation rules) - there is no other source. When implementation conflicts with the specification, write the flow asserting the SPECIFIED behavior, mark it as a suspected-bug case, and place it in `suspected-bugs/` (isolated from the passing suite); never write a case that enshrines a buggy implementation. When the specification is SILENT about the expected result (no conflict, but no spec either), never derive the expectation from code: omit that particular `aiAssert` (the flow still ends with its spec-grounded assertion) and record the spec gap in the report's gap list.\n- Restating the hard rule: do NOT execute anything - no `midscene` CLI, no runner, no browser automation.\n\n5. Static validation - use the `Agent` tool to spawn 2-3 review agents that examine the deliverables by reading only (never execute):\n- Schema/structure: valid YAML; only documented midscene keys (`page`/`web`/`browser`, `agent`, `tasks`, `name`, `continueOnError`, `flow`, `ai`/`aiAct`, `aiTap`, `aiHover`, `aiInput`+`value`, `aiKeyboardPress`+`keyName`, `aiScroll`, `aiAssert`, `aiQuery`+`name`, `aiBoolean`, `aiWaitFor`, `sleep`, `javascript`, `recordToReport`); every flow step is a `-` array item; no mixed environment segments.\n- Assert locatability: every `aiAssert` targets visible copy/state derivable from the requirements or repository UI text; no selector/xpath assertions; prompts are visual and single-purpose.\n- Anti-oracle compliance: every `aiAssert`'s expected value is traceable to the requirements/system-analysis docs, not to the implementation's current behavior; suspected-bug flows are correctly isolated.\n- Flow self-containment & step reachability: every flow starts from a reachable entry page (the environment `url` or a navigation chain recorded in the test point's precondition); every step's target element is established by an earlier step in the same task - no cross-task/file dependency; every assertion on async content (per the code-grounding findings: fetch/SSE/lazy rendering) is preceded by `aiWaitFor` (explicit timeout) or `sleep`; every `${VAR}` referenced in a flow is documented in run-notes.md; every flow's login strategy (cookie path / first login task / out-of-scope precondition) matches the environment-completeness findings.\n- Traceability & dedup: every test point has at least one flow; every flow links back to a test-point ID (suffixed IDs like `TP-012-1` allowed); no duplicates of existing test assets.\nDistill findings into P0/P1/P2 items; fix P0 (and concrete low-risk P1) and re-review, at most 2 rounds; report anything left unfixed.\n\n6. Deliverables and closing report - write files under `test-analysis/` (confirm the location at intake):\n  test-analysis/\n    analysis-report.md      # test-point matrix, techniques, traceability\n    flows/<module>/<page-or-flow>.yaml\n    suspected-bugs/*.yaml   # isolated spec-vs-implementation cases\n    validation-notes.md     # static-review record + risk statement\n    run-notes.md            # offline execution handoff (see below)\nThe closing message must include: requirement x test-point x flow coverage summary; the gap list with reasons; a risk statement (known non-goals, suspected-bug list, visual-assertion uncertainty); and the offline-execution handoff (also written to run-notes.md): how to run (`midscene ./x.yaml`), the required `.env` variables (MIDSCENE_MODEL_NAME / MIDSCENE_MODEL_API_KEY / MIDSCENE_MODEL_BASE_URL / MIDSCENE_MODEL_FAMILY) and the `${VAR}` account placeholders, explicitly stating the flows were never executed.\n</system-reminder>"
+}