dsh-custom-mode 1.11.0 → 1.11.1

package/README.i18n.yaml

@@ -1,5 +1,5 @@
 # 双语配对一致性记录：两侧在「上次确认一致」时的 git blob 哈希。
 # 两份文档权威相同——改完任意一侧，请把另一侧也改掉，然后重新记录：
 #   node tools/verify-translation-pairing.mjs --write
-README.md: 4e45a434fa7cfd4a939cda95c8d79d81395df7fe
-README.zh.md: 22d9b905b579dab2c35faa095e71ffb211ab46f2
+README.md: 4009df09f4f352850312dbeefb0f4f8729ba1e45
+README.zh.md: dc907b21aa6d277d5ad0f91b2c7acd40d3fd3e42

package/README.md

@@ -59,7 +59,7 @@ One command installs everything — the settings-page plugin, and the preset it
 activation:
 
 ```sh
-dsh plugin --profile web add dsh-custom-mode@1.11.0   # pin the version to get this one for sure
+dsh plugin --profile web add dsh-custom-mode@1.11.1   # pin the version to get this one for sure
 # A bare `add dsh-custom-mode` is subject to pnpm's release cooldown (`minimumReleaseAge`, 1 day by
 # default): for hours after a release it can silently install an OLDER version — measured: a bare
 # install 38 minutes after 1.3.0 shipped landed on 1.0.3. Check what you got with `npm ls
@@ -107,7 +107,8 @@ Electron shell**, so this plugin's page renders there unchanged. One install pat
 
 - **Install from inside the app**: sidebar → **Plugins** → add plugin → search `dsh-custom-mode`.
   The app runs the shared plugin manager with its own bundled pnpm.
-- **Do not try to use the CLI for it — dsh itself refuses** (measured on 0.1.7-rc.2):
+- **Do not try to use a standalone CLI for it — dsh itself refuses** (measured on 0.1.7-rc.2, and again on
+  0.2.0-rc.2):
   ```
   $ dsh plugin --profile desktop add .
   error: profile "desktop" is managed exclusively by the Electron application
@@ -116,8 +117,17 @@ Electron shell**, so this plugin's page renders there unchanged. One install pat
   and startup recovery renames `cordis.patch.yml`. `install.sh` therefore **refuses** `--profile desktop`
   too and points you at the app, so the two agree instead of one silently working around the other.
   (A lab simulation of the profile shape can override it with `DSH_ALLOW_DESKTOP_PROFILE=1`.)
+  **The app's own bundled CLI is the exception** — `<install>\resources\runtime\cli\bin\dsh.cmd` is allowed
+  to operate on that profile (measured on 1.11.1: `add dsh-custom-mode@1.11.1` → `+ dsh-custom-mode 1.11.1`).
+  It is a launcher, not a dsh feature: it starts Electron with `ELECTRON_RUN_AS_NODE=1` and runs the
+  desktop-host CLI, so it is the app talking to its own profile rather than something driving from outside.
 - **Nothing else to do on the preset side**: `$DSH_HOME/.agent-presets/` is product data shared by the
   desktop app and the CLI, and the preset is seeded by the plugin on first activation.
+- **If the mode does not show up in the picker, open Settings → Custom mode and read the warning.** A preset
+  whose rows cannot start on that machine is marked *broken* by the platform and dropped from every picker;
+  the settings page names the rows and offers **Fix for this line**. On the desktop line that can take one
+  click and then a **restart of the app** — the picker re-reads the registry only at boot (measured on
+  1.11.1, see `docs/MEASUREMENTS.md` section 34).
 - If a third-party bundle ever keeps the app from starting, the native recovery dialog offers
   **Disable third-party plugins**; installed packages and the plugin's own data stay on disk.
 
@@ -420,7 +430,7 @@ installing again — your data is not touched:
 
 ```sh
 # the pinned form: what you ask for is what you get
-dsh plugin --profile web add dsh-custom-mode@1.11.0
+dsh plugin --profile web add dsh-custom-mode@1.11.1
 # then restart the DSH process that serves the web profile
 ```
 

package/README.zh.md

@@ -48,7 +48,7 @@ base mode / plugin switches / multi-assistant / multi-persona。
 一条命令装完——设置页插件，以及它在首次激活时自动播种的 preset：
 
 ```sh
-dsh plugin --profile web add dsh-custom-mode@1.11.0   # 钉版本才能确定拿到这一版
+dsh plugin --profile web add dsh-custom-mode@1.11.1   # 钉版本才能确定拿到这一版
 # 不带版本号会受 pnpm 的发布冷却期影响（`minimumReleaseAge`，默认一天）：发布后数小时内按名安装
 # 可能**静默装到旧版** —— 实测 1.3.0 发布 38 分钟后按名安装装到了 1.0.3。用 profile 里的
 # `npm ls dsh-custom-mode` 核对实际装到的版本，或像上面那样钉版本。
@@ -89,7 +89,7 @@ dsh `0.1.6-alpha.2` 起有插件管理页：**侧边栏 → 插件 → 添加插
 安装只有一条路，就是上面那条：
 
 - **在应用里装**：侧栏 → **插件** → 添加插件 → 搜 `dsh-custom-mode`。应用自带 pnpm，走的是同一套插件管理器。
-- **不要试着用 CLI 装 —— dsh 自己就会拒绝**（0.1.7-rc.2 实测）：
+- **不要试着用独立的 CLI 装 —— dsh 自己就会拒绝**（0.1.7-rc.2 实测，0.2.0-rc.2 复测同样）：
   ```
   $ dsh plugin --profile desktop add .
   error: profile "desktop" is managed exclusively by the Electron application
@@ -97,8 +97,15 @@ dsh `0.1.6-alpha.2` 起有插件管理页：**侧边栏 → 插件 → 添加插
   桌面端独占 `$DSH_HOME/profiles/desktop`：那里的包操作持有 profile 事务锁，启动恢复还会重命名
   `cordis.patch.yml`。所以 `install.sh` 也**拒绝** `--profile desktop` 并指向应用内安装 —— 两边一致，
   而不是某一方偷偷绕过去。（只想在本机模拟 profile 形状时可设 `DSH_ALLOW_DESKTOP_PROFILE=1`。）
+  **应用自带的捆绑 CLI 是例外**：`<安装目录>\resources\runtime\cli\bin\dsh.cmd` 可以操作那个 profile
+  （1.11.1 实测：`add dsh-custom-mode@1.11.1` → `+ dsh-custom-mode 1.11.1`）。它是启动器而不是 dsh 的
+  新功能 —— 它用 `ELECTRON_RUN_AS_NODE=1` 起 Electron 去跑 desktop-host 的 CLI，所以那是**应用在跟自己的
+  profile 说话**，不是从外面驱动它。
 - **预设那一侧不用做任何事**：`$DSH_HOME/.agent-presets/` 是桌面端与 CLI 共享的产品数据，
   预设由插件首次激活时落盘。
+- **模式没出现在选择器里，就去「设置 → 自定义模式」读那条告警。** 行的启动条件在本机不满足时，平台会把整个
+  预设判为 broken 并**从所有选择器里丢掉**；设置页会点名那几行，并给出**「按本线修复」**。在桌面端那条线上，
+  这通常是一次点击 + **重启应用** —— 选择器只在应用启动时重读注册表（1.11.1 实测，见 `docs/MEASUREMENTS.md` §34）。
 - 万一某个第三方 bundle 让应用起不来：原生恢复对话框提供**「禁用第三方插件」**，已安装的包与插件数据都留在磁盘上。
 
 **兼容性是声明出来的，不是猜的。** dsh 会拿每个插件的 `peerDependencies["@deepseek-ai/dsh"]` 与运行时
@@ -323,7 +330,7 @@ MIT
 
 ```sh
 # 钉版本的写法：要哪版就是哪版
-dsh plugin --profile web add dsh-custom-mode@1.11.0
+dsh plugin --profile web add dsh-custom-mode@1.11.1
 # 然后重启为该 profile 提供服务的 DSH 进程
 ```
 

package/client.js

@@ -142,8 +142,8 @@ try {
         "api.selfCheckFailed": "生成结果自检失败，已放弃写入：{detail}",
         "api.internalError": "宿主内部错误：{detail}",
         "api.bodyTooLarge": "请求体过大（上限 {max} 字节）",
-        "api.repairNotNeeded": "这个助手在本机没有无法解析的行，无需修复。",
-        "api.repaired": "已按本机这条 dsh 线关闭 {count} 个无法解析的行（{ids}）。现在这个模式能重新出现在选择器里。",
+        "api.repairNotNeeded": "这个助手在本机没有起不来的行，无需修复。",
+        "api.repaired": "已按本机这条 dsh 线关闭 {count} 个起不来的行（{ids}）。现在这个模式能重新出现在选择器里。",
         "api.badAssistantId": "助手标识不合法：{id}（只能用 a-z、0-9 与连字符）",
         "api.seedFailed": "复制模式模板失败：{detail}",
         "api.metaWriteFailed": "写入 preset.yml 失败：{detail}",
@@ -157,6 +157,7 @@ try {
         "api.baseCompositionUnavailable": "本机取不到基础模式「{mode}」的出厂组成，无法改动插件开关或基础模式（系统提示词可以单独保存）。",
         "warn.approvalGateMissing": "审批闸门未启用：本机这个 DSH 版本没有 tools/pre-execute 事件，会话内改写系统提示词不会弹审批。见「详情」。",
         "warn.unresolvableRows": "有行在本机这条 DSH 线上无法解析：平台会把整个模式判为 broken，并从新会话的选择器里**静默丢弃**。点右侧的「按本线修复」即可（只关掉那几行，其它选择不动）。",
+        "warn.presetBroken": "平台把这个模式判为 broken，它会**从新会话的选择器里消失** —— 而上面的「无法解析」检查解释不了为什么（多半是某一行依赖的服务/引擎没起来）。点右侧的「按本线修复」把那几行关掉即可。宿主给的原因见「详情」。",
         "warn.exclusiveRowsActive": "两条互斥的壳同时开着（它们注册同名工具）：平台会把整个模式判为 broken，并从新会话的选择器里**静默丢弃**。把其中一条关掉即可 —— 在设置页保存一次也会自动避让。",
         "warn.baseCompositionUnavailable": "取不到本机这条 DSH 线的出厂组成：基础模式与插件开关暂时不能改（系统提示词不受影响，照常可保存）。已尝试的途径写在宿主日志里。",
         "warn.approvalGateMissing.label": "审批闸门未启用",
@@ -360,8 +361,8 @@ try {
         "api.selfCheckFailed": "The generated composition failed its self-check, so nothing was written: {detail}",
         "api.internalError": "Unexpected host error: {detail}",
         "api.bodyTooLarge": "Request body too large (limit {max} bytes)",
-        "api.repairNotNeeded": "Nothing to repair — no row of this assistant is unresolvable on this machine.",
-        "api.repaired": "Disabled {count} row(s) this dsh line cannot resolve ({ids}). The mode can appear in the pickers again.",
+        "api.repairNotNeeded": "Nothing to repair — every row of this assistant can start on this machine.",
+        "api.repaired": "Disabled {count} row(s) this dsh line cannot start ({ids}). The mode can appear in the pickers again.",
         "api.badAssistantId": "Invalid assistant id: {id} (a-z, 0-9 and hyphens only)",
         "api.seedFailed": "Copying the mode template failed: {detail}",
         "api.metaWriteFailed": "Writing preset.yml failed: {detail}",
@@ -378,6 +379,7 @@ try {
         "warn.noDescription": "No description: the new-session mode picker will show it as \"no description yet\".",
         "warn.approvalGateMissing": "The approval gate is off: this DSH build has no tools/pre-execute event, so in-session prompt rewrites do not ask for approval. See the details.",
         "warn.unresolvableRows": "Some rows cannot be resolved on this DSH line: the platform marks the whole mode broken and silently drops it from the new-session picker. Click Fix for this line — it only turns those rows off and leaves your other choices alone.",
+        "warn.presetBroken": "The platform marks this mode broken, so it **disappears from the new-session picker** — and the \"unresolvable\" check above cannot explain why (usually a row whose service or engine never started). Click Fix for this line to turn those rows off. The host's own reason is in Details.",
         "warn.exclusiveRowsActive": "Both shells are on, and they register the same tool names: the platform marks the whole mode broken and silently drops it from the new-session picker. Turn one of them off — saving from the settings page also resolves it automatically.",
         "warn.approvalGateMissing.label": "Approval gate is off",
         "warn.approvalGateMissing.hint": "This DSH build has no tools/pre-execute event, so in-session prompt rewrites do NOT ask for approval. The settings page is unaffected; upgrade DSH or turn the custom_prompt tool row off to restore the gate.",
@@ -2031,8 +2033,13 @@ try {
                     "div",
                     { key: code, className: "cpfe-warn-row" },
                     react.createElement("p", { className: "cpfe-warn" }, "⚠ " + t("warn." + code)),
-                    // 本线无法解析的行可以一键修（只关掉那几行；用户创建它的那个版本可能早于播种改为派生的版本）。
-                    code === "unresolvableRows"
+                    // 本线起不来的行可以一键修（只关掉那几行；用户创建它的那个版本可能早于播种改为派生的版本）。
+                    //
+                    // ★ 两个 code 都要给按钮：`presetBroken` 说的是"平台判它 broken，而『无法解析』解释不了"
+                    //   —— 那正是**修复按钮唯一还帮得上的时候**。原先只认 `unresolvableRows`，于是
+                    //   第一轮修复之后 `unresolvable` 变空、按钮消失，而告警文案还在叫用户"点右侧的
+                    //   按本线修复"。实测（2026-10-01，桌面端）就是卡在这一步：能看见病，没有药。
+                    code === "unresolvableRows" || code === "presetBroken"
                       ? react.createElement(
                           A.Button,
                           { disabled: busy, onClick: repairRowsNow },

package/index.mjs

@@ -290,6 +290,32 @@ export function configWarnings(text, prompt, meta) {
   return warnings
 }
 
+/**
+ * 从宿主给的那条 `broken` 里抠出**行 id**。
+ *
+ * 平台把"这个预设为什么起不来"写成一行行 `<rowId> (<module>): <reason>`，例如
+ *
+ *     workflow-worker-thread (@deepseek-ai/dsh-workflow-worker-thread): never started
+ *     tool-workflow (@deepseek-ai/dsh-tool-workflow): waiting for workflowEngine
+ *
+ * 这是**唯一**能知道"是哪一行害的"的来源：`unresolvableRows()` 只答"模块装没装"，答不了
+ * "上游服务等不到"。实测（2026-10-01，官方桌面端 0.2.0-rc.2）：关掉那个装不上的引擎行之后
+ * `unresolvable` 变空、页面**全绿**，而预设**仍然 broken**（依赖引擎的两个工具在等它）——
+ * 于是用户再也走不到可用状态，模式一直不出现。见 docs/MEASUREMENTS.md §34。
+ *
+ * @param {unknown} message - the roster row's `broken` string.
+ * @returns {string[]} row ids, de-duplicated, in the order they appear.
+ */
+export function brokenRowIds(message) {
+  if (typeof message !== 'string') return []
+  const ids = []
+  for (const line of message.split('\n')) {
+    const match = /^\s*([A-Za-z0-9][A-Za-z0-9_-]*)\s+\(/.exec(line)
+    if (match !== null) ids.push(match[1])
+  }
+  return [...new Set(ids)]
+}
+
 export function readState(rows, id, options = {}) {
   const directory = assistantDir(rows, id)
   if (directory === undefined) return unknownAssistant(id)
@@ -326,6 +352,15 @@ export function readState(rows, id, options = {}) {
     if (!isBaseCompositionUnavailable(error)) throw error
     baseUnavailable = { code: error.code, params: { mode, detail: describe(error) } }
   }
+  // 宿主给的那条 broken（若这条线上有）。**必须在 return 之前算**：warnings 要用它。
+  const selfRow = Array.isArray(rows) ? rows.find((item) => item !== null && typeof item === 'object' && item.id === id) : undefined
+  const hostBroken = typeof selfRow?.broken === 'string' ? selfRow.broken.trim() : ''
+  const unresolvable = unresolvableRows(text)
+  const knownUnresolvable = new Set(unresolvable.map((row) => row.id))
+  const hostBrokenIds = brokenRowIds(hostBroken)
+  // 宿主说坏了，而我们**解释不了**（不是"模块装不上"）—— 那就要单独点名，否则页面全绿、
+  // 模式却在选择器里不出现。抠不出行 id 时（宿主换了措辞）也照样点名：宁可笼统，不可沉默。
+  const unexplainedBroken = hostBroken !== '' && (hostBrokenIds.length === 0 || hostBrokenIds.some((rowId) => knownUnresolvable.has(rowId) === false))
   return {
     ok: true,
     id,
@@ -349,7 +384,10 @@ export function readState(rows, id, options = {}) {
     history: listHistory(directory),
     // 本插件版本 + 本机装的那条 dsh 线上无法解析的行（页面据此显示版本与"按本线修复"）。
     version: PLUGIN_VERSION,
-    unresolvable: unresolvableRows(text),
+    unresolvable,
+    // 宿主自己给的「这个预设为什么起不来」原文。它比 `unresolvable` 宽：除了"模块装不上"，
+    // 还包括"上游服务等不到"这类**装配期**失败。页面据此点名，而不是在坏着的时候显示全绿。
+    broken: hostBroken === '' ? null : hostBroken,
     // 「配置了却不生效」的告警码（文案在页面侧按语言渲染）。
     warnings: [
       ...configWarnings(text, prompt.ok === true ? prompt.text : '', meta),
@@ -357,7 +395,11 @@ export function readState(rows, id, options = {}) {
       // 诚实地把它变成页面上的告警，而不是只留在 console.error 里。
       ...(existsSync(join(directory, 'approval-gate-missing')) ? ['approvalGateMissing'] : []),
       // 本线无法解析的启用行 = 平台会把整个预设判为 broken 并从选择器里丢掉（曾经的 P0）。
-      ...(unresolvableRows(text).length > 0 ? ['unresolvableRows'] : []),
+      ...(unresolvable.length > 0 ? ['unresolvableRows'] : []),
+      // ★ 宿主报了 broken，而**我们自己的检查解释不了**（不是"模块装不上"，而是"服务等不到"之类）。
+      //   不点名的话，页面上 `unresolvable` 空、告警空 —— 一切看起来正常，而模式**根本没出现在
+      //   选择器里**。这正是本仓记录过两次的那种"静默失败"，只是换了个触发面。
+      ...(unexplainedBroken ? ['presetBroken'] : []),
       // 出厂组成取不到：提示词能改，基础模式与插件开关不能。
       ...(baseUnavailable === null ? [] : ['baseCompositionUnavailable']),
     ],
@@ -762,9 +804,30 @@ export function repairComposition(rows, input) {
   const file = compositionFile(directory)
   if (!existsSync(file)) return { ok: false, code: 'compositionMissing', params: { path: file }, error: '找不到组成文件：' + file }
   const text = readFileSync(file, 'utf8')
-  const bad = unresolvableRows(text)
+  // 两类"这一行在本机起不来"，必须**都**关掉：
+  //  ① 模块装不上 —— 我们自己在 node_modules 里查得出来（`unresolvableRows`）；
+  //  ② 装配期失败（"服务等不到"之类）—— 只有宿主知道，写在它给的 `broken` 里。
+  // 只修 ① 会留下一个**页面全绿、预设却仍然 broken**的状态（桌面端实测，见 brokenRowIds 的注释）：
+  // `unresolvable` 变空 ⇒ 告警消失 ⇒ 用户以为修好了，而模式始终没出现在选择器里。
+  const selfRow = Array.isArray(rows) ? rows.find((item) => item !== null && typeof item === 'object' && item.id === id) : undefined
+  // 只关**这份文本里真的有**的行：宿主报的可能是别处的行，而 `disableRowsInPlace` 对不存在的 id
+  // 是无操作 —— 计数会因此说谎（说关了 3 个其实只关了 1 个）。
+  const present = new Set()
+  const collectIds = (list) => {
+    for (const row of list) {
+      present.add(row.id)
+      if (Array.isArray(row.children)) collectIds(row.children)
+    }
+  }
+  try {
+    collectIds(collectRows(text))
+  } catch {
+    /* 文本解析不了就只按 unresolvableRows 走（它自己会兜底） */
+  }
+  const wanted = [...new Set([...unresolvableRows(text).map((row) => row.id), ...brokenRowIds(selfRow?.broken)])]
+  const bad = wanted.map((rowId) => ({ id: rowId })).filter((row) => present.has(row.id))
   if (bad.length === 0) {
-    return { ok: true, id, code: 'repairNotNeeded', note: '这个助手在本机没有无法解析的行，无需修复。' }
+    return { ok: true, id, code: 'repairNotNeeded', note: '这个助手在本机没有起不来的行，无需修复。' }
   }
   // **就地**关闭那几行，不重渲染：重渲染会顺手丢掉 base 之外的自有行，而用户的数据不该被这样动。
   const rendered = disableRowsInPlace(text, bad.map((row) => row.id))
@@ -782,7 +845,7 @@ export function repairComposition(rows, input) {
     // 草稿，否则下一次保存会按草稿重渲染，把刚才的修复原样撤销（issue #8 实测：
     // 修复写进了磁盘，但草稿里那几行仍是启用的，于是保存后 ghost 行又回来了）。
     params: { count: bad.length, ids, repairedIds: bad.map((row) => row.id) },
-    note: '已按本机这条 dsh 线关闭 ' + String(bad.length) + ' 个无法解析的行（' + ids + '）。现在这个模式能重新出现在选择器里。',
+    note: '已按本机这条 dsh 线关闭 ' + String(bad.length) + ' 个起不来的行（' + ids + '）。现在这个模式能重新出现在选择器里。',
   }
 }
 

package/locales.mjs

@@ -102,8 +102,8 @@ export const zh = {
   'api.selfCheckFailed': '生成结果自检失败，已放弃写入：{detail}',
   'api.internalError': '宿主内部错误：{detail}',
   'api.bodyTooLarge': '请求体过大（上限 {max} 字节）',
-  'api.repairNotNeeded': '这个助手在本机没有无法解析的行，无需修复。',
-  'api.repaired': '已按本机这条 dsh 线关闭 {count} 个无法解析的行（{ids}）。现在这个模式能重新出现在选择器里。',
+  'api.repairNotNeeded': '这个助手在本机没有起不来的行，无需修复。',
+  'api.repaired': '已按本机这条 dsh 线关闭 {count} 个起不来的行（{ids}）。现在这个模式能重新出现在选择器里。',
   'api.badAssistantId': '助手标识不合法：{id}（只能用 a-z、0-9 与连字符）',
   'api.seedFailed': '复制模式模板失败：{detail}',
   'api.metaWriteFailed': '写入 preset.yml 失败：{detail}',
@@ -117,6 +117,7 @@ export const zh = {
   'api.baseCompositionUnavailable': '本机取不到基础模式「{mode}」的出厂组成，无法改动插件开关或基础模式（系统提示词可以单独保存）。',
   'warn.approvalGateMissing': '审批闸门未启用：本机这个 DSH 版本没有 tools/pre-execute 事件，会话内改写系统提示词不会弹审批。见「详情」。',
   'warn.unresolvableRows': '有行在本机这条 DSH 线上无法解析：平台会把整个模式判为 broken，并从新会话的选择器里**静默丢弃**。点右侧的「按本线修复」即可（只关掉那几行，其它选择不动）。',
+  'warn.presetBroken': '平台把这个模式判为 broken，它会**从新会话的选择器里消失** —— 而上面的「无法解析」检查解释不了为什么（多半是某一行依赖的服务/引擎没起来）。点右侧的「按本线修复」把那几行关掉即可。宿主给的原因见「详情」。',
   'warn.exclusiveRowsActive': '两条互斥的壳同时开着（它们注册同名工具）：平台会把整个模式判为 broken，并从新会话的选择器里**静默丢弃**。把其中一条关掉即可 —— 在设置页保存一次也会自动避让。',
   'warn.baseCompositionUnavailable': '取不到本机这条 DSH 线的出厂组成：基础模式与插件开关暂时不能改（系统提示词不受影响，照常可保存）。已尝试的途径写在宿主日志里。',
   'warn.approvalGateMissing.label': '审批闸门未启用',
@@ -338,8 +339,8 @@ export const en = {
   'api.selfCheckFailed': 'The generated composition failed its self-check, so nothing was written: {detail}',
   'api.internalError': 'Unexpected host error: {detail}',
   'api.bodyTooLarge': 'Request body too large (limit {max} bytes)',
-  'api.repairNotNeeded': 'Nothing to repair — no row of this assistant is unresolvable on this machine.',
-  'api.repaired': 'Disabled {count} row(s) this dsh line cannot resolve ({ids}). The mode can appear in the pickers again.',
+  'api.repairNotNeeded': 'Nothing to repair — every row of this assistant can start on this machine.',
+  'api.repaired': 'Disabled {count} row(s) this dsh line cannot start ({ids}). The mode can appear in the pickers again.',
   'api.badAssistantId': 'Invalid assistant id: {id} (a-z, 0-9 and hyphens only)',
   'api.seedFailed': 'Copying the mode template failed: {detail}',
   'api.metaWriteFailed': 'Writing preset.yml failed: {detail}',
@@ -356,6 +357,7 @@ export const en = {
   'warn.noDescription': 'No description: the new-session mode picker will show it as "no description yet".',
   'warn.approvalGateMissing': 'The approval gate is off: this DSH build has no tools/pre-execute event, so in-session prompt rewrites do not ask for approval. See the details.',
   'warn.unresolvableRows': 'Some rows cannot be resolved on this DSH line: the platform marks the whole mode broken and silently drops it from the new-session picker. Click Fix for this line — it only turns those rows off and leaves your other choices alone.',
+  'warn.presetBroken': 'The platform marks this mode broken, so it **disappears from the new-session picker** — and the "unresolvable" check above cannot explain why (usually a row whose service or engine never started). Click Fix for this line to turn those rows off. The host\'s own reason is in Details.',
   'warn.exclusiveRowsActive': 'Both shells are on, and they register the same tool names: the platform marks the whole mode broken and silently drops it from the new-session picker. Turn one of them off — saving from the settings page also resolves it automatically.',
   'warn.approvalGateMissing.label': 'Approval gate is off',
   'warn.approvalGateMissing.hint': 'This DSH build has no tools/pre-execute event, so in-session prompt rewrites do NOT ask for approval. The settings page is unaffected; upgrade DSH or turn the custom_prompt tool row off to restore the gate.',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-custom-mode",
-  "version": "1.11.0",
+  "version": "1.11.1",
   "description": "Custom modes and custom prompts for DeepSeek Harness (dsh): edit a mode's system prompt on the settings page (it takes effect on the next model step), pick its base mode, switch plugin rows one by one, and keep several assistants side by side — coding, chat or roleplay (RP) personas (multi-mode / multi-agent).",
   "license": "MIT",
   "type": "module",