dsh-custom-mode 1.11.6 → 1.12.0

package/README.i18n.yaml

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

package/README.md

@@ -27,15 +27,13 @@ modes ("assistants") can live side by side, each with its own prompt.
 Also searched for as: custom mode · custom prompt · system-prompt editor · multi-mode / several assistants ·
 multi-agent · roleplay (RP) / chat personas.
 
-**Two dsh lines are supported: the newest line and the previous stable** — both checked on every push,
-neither merely claimed. npm's `latest` and `next` have both pointed at `0.2.0-rc.2` since 2026-09-29, so
-"latest stable" and "latest preview" are one release now; the second leg stays because most installs in
-the field are still on `0.1.7-rc.2`:
+**Unit tests cover three lines. The render gate runs only on `0.2.0-rc.2`.** npm's `latest` and `next` have both pointed at `0.2.0-rc.2` since 2026-09-29:
 
 | dsh | role | status |
 | --- | --- | --- |
 | `0.2.0-rc.2` | **newest line** — npm's `latest` *and* `next`, and the line the official desktop app ships (it is version-locked to dsh) | ✅ CI (ubuntu node 20/24 + **windows**) + a real instance: install, composition and the seeded preset verified on this line (the full render gate runs here) |
-| `0.1.7-rc.2` | previous stable — still inside the declared range, and what most existing installs run | ✅ CI + a real instance: verified rendered on this line since 1.9.15 |
+| `0.2.1-alpha.1` | preview line — npm `alpha`. Covered by unit tests; the render gate does not run here | ✅ CI |
+| `0.1.7-rc.2` | previous stable — still inside the declared range, and what most existing installs run | ✅ CI. On this line the page falls back where the shell does not provide atoms; the render gate does not run here |
 
 Older builds (`0.1.5-rc.3`, `0.1.6-alpha.*`) use the same mechanisms and remain inside the declared peer
 range, but they no longer get a CI leg of their own.
@@ -59,7 +57,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.6   # pin the version to get this one for sure
+dsh plugin --profile web add dsh-custom-mode@1.12.0   # 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
@@ -118,7 +116,7 @@ Electron shell**, so this plugin's page renders there unchanged. One install pat
   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.6` → `+ dsh-custom-mode 1.11.1`).
+  to operate on that profile (an older note claimed a pin installed a different version; that note is withdrawn).
   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
@@ -315,13 +313,19 @@ What this plugin supports is declared in `engines.dsh` and the `@deepseek-ai/dsh
 `package.json`, and `tools/verify-version-consistency.mjs` (run in CI) asserts that the DSH
 version CI installs and tests falls inside those ranges.
 
-**Two lines are supported: the newest line (`0.2.0-rc.2`, which npm's `latest` and `next` both point at
-since 2026-09-29, and the line the desktop app ships) and the previous stable (`0.1.7-rc.2` — still inside
+**Three lines are supported: the newest stable line (`0.2.0-rc.2`, which npm's `latest` and `next` both
+point at since 2026-09-29, and the line the desktop app ships), the newest preview line
+(`0.2.1-alpha.1`, which npm's `alpha` points at) and the previous stable (`0.1.7-rc.2` — still inside
 the declared range, and what most existing installs run)** — declared as
-`>=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0 || >=0.2.0-0 <0.3.0-0` (the extra clauses exist because
-semver only matches a pre-release inside a range that names its own `major.minor.patch`), and CI installs both
+`>=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0 || >=0.2.0-0 <0.3.0-0 || >=0.2.1-alpha.1 <0.3.0-0` (the extra clauses exist because
+semver only matches a pre-release inside a range that names its own `major.minor.patch`), and CI installs all three
 and runs the whole suite against each — the rendered gate runs on the **newest** line, because that is
 where the shell's own UI changes land first.
+**The newest preview line needs its own leg because the stable line's clause does *not* cover it**:
+`>=0.2.0-0 <0.3.0-0` reads like it covers all of `0.2.x`, but the pre-release gate only opens when some
+comparator in the set names the same `major.minor.patch`, and that comparator's tuple is `0.2.0` — so
+`0.2.1-alpha.1` is refused. A range that *looks* wide is therefore neither coverage of the preview line
+nor evidence that it was ever run.
 **The official desktop app (DeepSeek Harness Desktop) is covered too**: it is version-locked to dsh and now
 ships `0.2.0-rc.2`, i.e. the same combination this matrix pins. Install it from inside the app (sidebar →
 Plugins); the CLI is refused for that profile by dsh itself. On `0.2.0-rc.2` measured (2026-09-30, clean
@@ -400,7 +404,7 @@ MIT
 | | |
 | --- | --- |
 | Model | DeepSeek V4.1 Flash (`deepseek-v4-flash`, provider `deepseek-official`) |
-| Runtime | DeepSeek Harness **0.2.0-rc.2** (newest line) / **0.1.7-rc.2** (previous stable) — the two supported lines; the token figures below are from an earlier `0.1.6-alpha.2` session |
+| Runtime | Unit tests: `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.1.7-rc.2`. The render gate runs only on `0.2.0-rc.2`. The token figures below are from an earlier `0.1.6-alpha.2` session |
 | Uncached input | 224,058 tok |
 | Cache reads | 125,638,016 tok |
 | Output | 425,539 tok |
@@ -430,7 +434,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.6
+dsh plugin --profile web add dsh-custom-mode@1.12.0
 # then restart the DSH process that serves the web profile
 ```
 

package/README.zh.md

@@ -22,12 +22,13 @@ base mode / plugin switches / multi-assistant / multi-persona。
 常见的叫法：自定义模式 · 自定义提示词 · 系统提示词编辑 · 多助手／多模式 · 多个 Agent 模式 ·
 角色扮演／聊天人格（RP）。
 
-**支持两条线：最新线（npm 的 `latest` 与 `next` 自 2026-09-29 起都指向 `0.2.0-rc.2`）与上一个正式版** —— 两条都是每次 push 真跑，不是声明：
+**单元测试覆盖三条线，渲染闸门只跑 `0.2.0-rc.2`。** npm 的 `latest` 与 `next` 自 2026-09-29 起都指向 `0.2.0-rc.2`：
 
 | dsh | 定位 | 状态 |
 | --- | --- | --- |
 | `0.2.0-rc.2` | **最新线** —— npm 的 `latest` 与 `next` 都指向它，官方桌面端也在这一条线上（与 dsh 同版本号） | ✅ CI（ubuntu node 20/24 + **windows**）+ 真机：这条线上安装、组合树与播种都验过（整道渲染闸门跑在这里）|
-| `0.1.7-rc.2` | 上一个正式版 —— 仍在声明范围内，现役安装大多在它上面 | ✅ CI + 真机：自 1.9.15 起就在这条线上验过渲染 |
+| `0.2.1-alpha.1` | 预览线 —— npm 的 `alpha` 指向它。单元测试覆盖；渲染闸门不在这条线上 | ✅ CI |
+| `0.1.7-rc.2` | 上一个正式版 —— 仍在声明范围内，现役安装大多在它上面 | ✅ CI。设置页在这条线上会退回壳没提供的控件；渲染闸门不在这里 |
 
 更早的线（`0.1.5-rc.3`、`0.1.6-alpha.*`）共用同一套机制，peer 范围仍然接纳，但不再单独占 CI 腿。
 
@@ -48,7 +49,7 @@ base mode / plugin switches / multi-assistant / multi-persona。
 一条命令装完——设置页插件，以及它在首次激活时自动播种的 preset：
 
 ```sh
-dsh plugin --profile web add dsh-custom-mode@1.11.6   # 钉版本才能确定拿到这一版
+dsh plugin --profile web add dsh-custom-mode@1.12.0   # 钉版本才能确定拿到这一版
 # 不带版本号会受 pnpm 的发布冷却期影响（`minimumReleaseAge`，默认一天）：发布后数小时内按名安装
 # 可能**静默装到旧版** —— 实测 1.3.0 发布 38 分钟后按名安装装到了 1.0.3。用 profile 里的
 # `npm ls dsh-custom-mode` 核对实际装到的版本，或像上面那样钉版本。
@@ -67,7 +68,7 @@ dsh `0.1.6-alpha.2` 起有插件管理页：**侧边栏 → 插件 → 添加插
 
 | 输入 | 填什么 | 说明 |
 | --- | --- | --- |
-| **包名** | `dsh-custom-mode` | 最省事 |
+| **包名** | `dsh-custom-mode` | 受 pnpm 发布冷却期影响，可能装到旧版。要这一版请钉 `@1.12.0` |
 | **GitHub 仓库地址** | `https://github.com/BOWLUNA/dsh-custom-mode` | 指向**仓库根**即可 |
 | **本地插件目录** | `<你 clone 的路径>` | 就是仓库根 —— 仓库根**本身**就是发布包 |
 
@@ -98,7 +99,7 @@ dsh `0.1.6-alpha.2` 起有插件管理页：**侧边栏 → 插件 → 添加插
   `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.6` → `+ dsh-custom-mode 1.11.1`）。它是启动器而不是 dsh 的
+  （1.11.1 实测时，命令写的版本和装上的版本对不上，这次记录作废）。它是启动器而不是 dsh 的
   新功能 —— 它用 `ELECTRON_RUN_AS_NODE=1` 起 Electron 去跑 desktop-host 的 CLI，所以那是**应用在跟自己的
   profile 说话**，不是从外面驱动它。
 - **预设那一侧不用做任何事**：`$DSH_HOME/.agent-presets/` 是桌面端与 CLI 共享的产品数据，
@@ -222,12 +223,16 @@ dsh 的系统提示词通常来自 preset 的 YAML，而官方 `@deepseek-ai/dsh
 
 ## 版本
 
-**支持两条线：最新线（`0.2.0-rc.2`，npm 的 `latest` 与 `next` 自 2026-09-29 起都指向它，也是桌面端
-所在的那条线）与上一个正式版（`0.1.7-rc.2`，仍在声明范围内，现役安装大多在它上面）** —— 声明为
-`>=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0 || >=0.2.0-0 <0.3.0-0`（多出来的两段是因为
-semver 只允许范围里**点名了** `major.minor.patch` 的预发布版本被匹配到），CI 会两条线各装一次并各跑一遍
+**支持三条线：最新正式线（`0.2.0-rc.2`，npm 的 `latest` 与 `next` 自 2026-09-29 起都指向它，也是桌面端
+所在的那条线）、最新预览线（`0.2.1-alpha.1`，npm 的 `alpha` 指向它）与上一个正式版（`0.1.7-rc.2`，
+仍在声明范围内，现役安装大多在它上面）** —— 声明为
+`>=0.1.5-rc.2 <0.2.0-0 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0 || >=0.2.0-0 <0.3.0-0 || >=0.2.1-alpha.1 <0.3.0-0`（多出来的三段是因为
+semver 只允许范围里**点名了** `major.minor.patch` 的预发布版本被匹配到），CI 会三条线各装一次并各跑一遍
 完整测试 —— 其中**渲染闸门跑在最新线**上，因为壳自己的 UI 改动最先落在那里。
-这里的策略是"只跟两个最新的"：更早的线（`0.1.5-rc.3`、`0.1.6-alpha.*`）仍在 peer 范围内，但不单独占 CI 腿。
+这里的策略是"只跟最新的几条"：更早的线（`0.1.5-rc.3`、`0.1.6-alpha.*`）仍在 peer 范围内，但不单独占 CI 腿。
+★ 最新**预览**线必须单独占一条腿，因为它**不会**被正式线的范围顺带覆盖：`>=0.2.0-0 <0.3.0-0` 读起来
+覆盖整个 `0.2.x`，但预发布门只在**某个比较符点名了同 `major.minor.patch`** 时才放行，而那个比较符的
+元组是 `0.2.0` ⇒ `0.2.1-alpha.1` 被拒。所以"声明看着宽"既不等于"预览线被覆盖"，更不等于"跑过"。
 **官方桌面端（DeepSeek Harness Desktop）也在覆盖范围内**：它与 dsh 同版本号，当前即为 `0.2.0-rc.2`，
 正是这条矩阵钉住的组合；在应用内（侧栏 → Plugins）安装即可，CLI 那条路 dsh 自己会拒。
 `0.2.0-rc.2` 实测（2026-09-30，干净的一次性 `DSH_HOME`）：`dsh plugin --profile web add dsh-custom-mode`
@@ -301,7 +306,7 @@ MIT
 | | |
 | --- | --- |
 | 模型 | DeepSeek V4.1 Flash（`deepseek-v4-flash`，provider `deepseek-official`） |
-| 运行时 | DeepSeek Harness **0.2.0-rc.2**（最新线）/ **0.1.7-rc.2**（上一个正式版）—— 支持的就是这两条线；下面的用量数字来自更早的 `0.1.6-alpha.2` 那一轮 |
+| 运行时 | 单元测试：`0.2.0-rc.2`、`0.2.1-alpha.1`、`0.1.7-rc.2`。渲染闸门只跑 `0.2.0-rc.2`。下面的用量数字来自更早的 `0.1.6-alpha.2` 那一轮 |
 | 未缓存输入 | 224,058 tok |
 | 缓存读取 | 125,638,016 tok |
 | 输出 | 425,539 tok |
@@ -330,7 +335,7 @@ MIT
 
 ```sh
 # 钉版本的写法：要哪版就是哪版
-dsh plugin --profile web add dsh-custom-mode@1.11.6
+dsh plugin --profile web add dsh-custom-mode@1.12.0
 # 然后重启为该 profile 提供服务的 DSH 进程
 ```
 

package/atomic.mjs

@@ -14,7 +14,8 @@
  *    random temporary name does not help with *that* collision, only with temp-vs-temp ones.
  */
 import { randomBytes } from 'node:crypto'
-import { existsSync, renameSync, rmSync, statSync, writeFileSync } from 'node:fs'
+import { existsSync, readdirSync, renameSync, rmSync, statSync, writeFileSync } from 'node:fs'
+import { join } from 'node:path'
 
 /** Synchronous backoff: these write paths are synchronous, so waiting is simpler than async plumbing. */
 function sleepSync(ms) {
@@ -195,6 +196,35 @@ export function writeAtomicPair(entries) {
  * @param {string} text - content to write.
  * @returns {void}
  */
+/**
+ * 掉电落在「旧文件已改名为 .bak、新文件还没装上」时，把唯一的备份移回原名。
+ *
+ * 多于一份备份时不动：无法判断哪一份是最后的好内容。
+ *
+ * @param {string} directory - one assistant directory.
+ * @returns {void}
+ */
+export function restoreBackups(directory) {
+  const names = ['prompt.md', 'agent.cordis.yml', 'preset.yml']
+  let entries
+  try {
+    entries = readdirSync(directory)
+  } catch {
+    return
+  }
+  for (const name of names) {
+    const file = join(directory, name)
+    if (existsSync(file)) continue
+    const backups = entries.filter((entry) => entry.startsWith(name + '.bak-'))
+    if (backups.length !== 1) continue
+    try {
+      renameSync(join(directory, backups[0]), file)
+    } catch {
+      /* 恢复失败就留着备份，下一次读取再试 */
+    }
+  }
+}
+
 export function writeAtomic(file, text) {
   const temporary = `${file}.tmp-${String(process.pid)}-${randomBytes(4).toString('hex')}`
   try {