dsh-custom-mode 1.13.0 → 2.0.1

package/README.i18n.yaml

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

package/README.md

@@ -56,7 +56,7 @@ One command installs everything — the settings-page plugin, and the preset it
 activation:
 
 ```sh
-dsh plugin --profile web add dsh-custom-mode@1.13.0   # pin the version to get this one for sure
+dsh plugin --profile web add dsh-custom-mode@2.0.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
@@ -396,17 +396,22 @@ 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.13.0
+dsh plugin --profile web add dsh-custom-mode@2.0.1
 # then restart the DSH process that serves the web profile
 ```
 
-**Do not install by bare name if you want this release.** pnpm applies a release cooldown (`minimumReleaseAge`,
-24 hours by default) and a bare `dsh plugin add dsh-custom-mode` resolves to *the newest version older than 24
-hours*. Measured on a clean machine while 1.9.0 was latest: the bare command installed **1.0.1**. Pinning the
-version bypasses the cooldown, which is why the command above carries `@`.
+**Do not install by bare name, and do not use `@latest`.** pnpm applies a release cooldown
+(`minimumReleaseAge`, 24 hours by default). A bare `dsh plugin add dsh-custom-mode` resolves to *the newest
+version older than 24 hours*. Measured: while npm `latest` was 1.12.2 and six minutes old, `@latest` installed
+1.11.6. Pin the exact version.
 
-**How to know what you are running**: the settings page shows the installed version at the bottom (Plugin version).
-Compare it with `npm view dsh-custom-mode version`.
+Each exact pin appends a `minimumReleaseAgeExclude` line in the profile's `pnpm-workspace.yaml`. pnpm 11.7.0
+honours only the first line that matches the package name ([pnpm#12463](https://github.com/pnpm/pnpm/issues/12463)).
+Keep one line, `dsh-custom-mode`, not a list of versions. This plugin does not edit that file. If install fails
+with `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION`, merge the list to that one line and run the install again:
+`node_modules` may already show the new version while `package.json` still names the old one.
+
+**How to know the upgrade worked**: restart dsh, then read the version at the bottom of this settings page.
 
 **What an update does not touch**: `$DSH_HOME/.agent-presets/<your assistants>/` — `prompt.md`, `preset.yml` and
 your row switches are yours. Seeding only fills in *missing* files, so a prompt you wrote is never overwritten.

package/README.zh.md

@@ -49,7 +49,7 @@ base mode / plugin switches / multi-assistant / multi-persona。
 一条命令装完——设置页插件，以及它在首次激活时自动播种的 preset：
 
 ```sh
-dsh plugin --profile web add dsh-custom-mode@1.13.0   # 钉版本才能确定拿到这一版
+dsh plugin --profile web add dsh-custom-mode@2.0.1   # 钉版本才能确定拿到这一版
 # 不带版本号会受 pnpm 的发布冷却期影响（`minimumReleaseAge`，默认一天）：发布后数小时内按名安装
 # 可能**静默装到旧版** —— 实测 1.3.0 发布 38 分钟后按名安装装到了 1.0.3。用 profile 里的
 # `npm ls dsh-custom-mode` 核对实际装到的版本，或像上面那样钉版本。
@@ -68,7 +68,7 @@ dsh `0.1.6-alpha.2` 起有插件管理页：**侧边栏 → 插件 → 添加插
 
 | 输入 | 填什么 | 说明 |
 | --- | --- | --- |
-| **包名** | `dsh-custom-mode` | 受 pnpm 发布冷却期影响，可能装到旧版。要这一版请钉 `@1.13.0` |
+| **包名** | `dsh-custom-mode` | 受 pnpm 发布冷却期影响，可能装到旧版。要这一版请钉 `@2.0.1` |
 | **GitHub 仓库地址** | `https://github.com/BOWLUNA/dsh-custom-mode` | 指向**仓库根**即可 |
 | **本地插件目录** | `<你 clone 的路径>` | 就是仓库根 —— 仓库根**本身**就是发布包 |
 
@@ -300,15 +300,16 @@ MIT
 
 ```sh
 # 钉版本的写法：要哪版就是哪版
-dsh plugin --profile web add dsh-custom-mode@1.13.0
+dsh plugin --profile web add dsh-custom-mode@2.0.1
 # 然后重启为该 profile 提供服务的 DSH 进程
 ```
 
-**想要这一版就别用不带版本号的安装。** pnpm 有发布冷却期（`minimumReleaseAge`，默认 24 小时），
-`dsh plugin add dsh-custom-mode` 会解析成**"超过 24 小时的最新版"**。实测：在 1.9.0 已是 latest 的干净机器上，
-不带版本号的命令装到的是 **1.0.1**。钉版本可以绕过冷却期，所以上面的命令带 `@`。
+**不要按裸名安装，也不要用 `@latest`。** pnpm 有发布冷却期（`minimumReleaseAge`，默认 24 小时）。
+`dsh plugin add dsh-custom-mode` 会解析成**超过 24 小时的最新版**。实测：npm 上 `latest` 已是发布 6 分钟的 1.12.2 时，`@latest` 装成了 1.11.6。请钉精确版本。
 
-**怎么知道自己在跑哪一版**：设置页底部显示已安装版本（「插件版本」），与 `npm view dsh-custom-mode version` 对照即可。
+每次钉精确版本，pnpm 都会在 profile 的 `pnpm-workspace.yaml` 里追加一条 `minimumReleaseAgeExclude`。pnpm 11.7.0 只认第一条命中包名的记录（[pnpm#12463](https://github.com/pnpm/pnpm/issues/12463)）。这个包只留一条 `dsh-custom-mode`，不要留一串版本号。本插件不改这个文件。若安装报 `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION`，把列表收成那一条再装一次：`node_modules` 里可能已经是新版本，而 `package.json` 仍写着旧版本。
+
+**怎样算升级成功**：重启 dsh，再看本设置页底部的版本号。
 
 **更新不会碰的东西**：`$DSH_HOME/.agent-presets/<你的助手>/` —— `prompt.md`、`preset.yml` 与你逐行拨过的开关都属于你。
 播种只补**缺失**的文件，你写过的提示词永远不会被覆盖。