dsh-update-status 0.1.6 → 0.1.8

package/CHANGELOG.md

@@ -2,6 +2,33 @@
 
 All notable changes to this project are documented here.
 
+## 0.1.8 — 2026-09-25
+
+Verified DeepSeek Harness: `0.1.7-rc.2` (the latest release candidate, and what npm's `next` dist-tag publishes), also `0.1.7-rc.1` and `0.1.7-alpha.2`. Full bilingual release notes: [`docs/releases/v0.1.8.md`](docs/releases/v0.1.8.md).
+
+A version-matrix release with **zero code change**: DSH moved from `0.1.7-rc.1` to `0.1.7-rc.2`, and nothing this plugin binds to changed shape. No migration is needed from `0.1.7`.
+
+- **`0.1.7-rc.2` joins the verified list.** `VERIFIED_DSH_VERSIONS` in `src/shared/types.ts` and `package.json`'s `dsh.compatibility.dshReleases` both gain it, keeping `0.1.7-alpha.2` and `0.1.7-rc.1`; `tests/shared/compatibility.spec.ts` keeps the two lists identical and proves the `dsh.engines.dsh` / `@deepseek-ai/dsh-settings` peer ranges admit every listed release.
+- **The user-visible effect.** `0.1.7-rc.2` is what npm's `next` dist-tag publishes, and the old list stopped at `0.1.7-rc.1`, so following `next` produced a `preview-unverified` advisory (`notice` level, never repaints the chip). The running version and the channel row now read verified, and that advisory is gone. Generated upgrade commands and installation guidance are untouched.
+- **rc.1 → rc.2 interface audit, all 7 bound packages.** `dsh-settings`, `dsh-client-ui-settings`, `dsh-client-ui-settings-general`, `dsh-client-ui-sidebar`, `dsh-client-ui-layout`, `dsh-client-connection` and `dsh-api-remotes` were diffed across the two releases. Every difference is additive shortcut plumbing: `settingsOpen` / `settingsShortcut` on the settings slot context, `shortcuts` on the sidebar shell context, `useShortcuts` on `SidebarRoot` / `HeaderLeadingControls`, `panelInfo` on the layout service, a `shortcuts.layout` locale namespace, a `shortcut.open` label, and a `dsh-schedule/remote` type re-export. Nothing this plugin uses was removed or reshaped: the `ctx.configForms` form face, `remote.settings`' `settings.describe` / `settings.mutate`, the `/api/dsh-update-status.*` Connection RPC routes and the four slots (`sidebar.brand.name`, `sidebar.footer.action`, `shell.overlay`, `settings.section`) are all unchanged.
+- **Live load check on rc.2.** With a disposable `DSH_HOME`, this repository was installed into a web profile with `link:` and `dsh --profile web --dump-config` composed the `dsh-update-status` entry with no compatibility refusal — rc.2's profile-load gate accepts the bundle.
+- **Tests: 98 passing** (unchanged — this release adds no behaviour to lock). The audit and the live load check are the new evidence; the panel/chip end-to-end interaction was **not** re-run on rc.2, and the `0.1.6` live adaptation conclusion still stands.
+- **Unchanged**: the Host half, the client half, the RPC channel, the status read, the sidebar chip, the detail panel, the LAN (non-loopback) fallback and the profile-patch preference model.
+
+## 0.1.7 — 2026-09-24
+
+Verified DeepSeek Harness: `0.1.7-rc.1` (the latest release candidate) and `0.1.7-alpha.2`. Full bilingual release notes: [`docs/releases/v0.1.7.md`](docs/releases/v0.1.7.md).
+
+`0.1.6` made the plugin work on the DSH `0.1.7` line; `0.1.7` makes it speak the page's language. Contributed by [@ivkiwi](https://github.com/ivkiwi) as PR #7, rebased onto `0.1.6` and landed with the original authorship preserved (commit `362d83e`). No migration is needed from `0.1.6`.
+
+- **Runtime warnings are language-neutral now (the user-visible fix).** The Host used to compose the warning sentences itself, in Chinese (`无法检查 npm registry：…`, `npm registry 未发布 alpha 通道。`, …), and the Client displayed that string verbatim — so an English UI showed Chinese warnings. `UpdateStatus` now carries `warnings: UpdateWarning[]` with four codes (`registry-unavailable`, `channel-unavailable`, `version-incomparable`, `preview-unverified`) and their interpolation data, and the Client renders them from its own `en` / `zh` dictionary. The English `warning` string is **kept as a mixed-version fallback**, so a new client against an older Host — or an older client against a new Host — still shows a useful English sentence.
+- **The `warningKind` contract is unchanged.** All `preview-unverified` → `notice` (advisory, never repaints the chip); anything else → `failure`. The `0.1.5` rule that keeps "DSH upgraded ahead of the plugin" from painting the chip red still holds.
+- **The Client validates the structured payload at the boundary.** A new `warningOf` guard checks each code and its interpolation types, so a malformed payload is dropped rather than rendered as `[object Object]`.
+- **Non-command installation guidance is localized too**, while **real upgrade commands (`npm install -g …` / `pnpm add -g …`) pass through untouched** — a command can never be corrupted by translation.
+- **Dev toolchain bumped** (development dependencies only, not in the published artifact): tsdown `0.22.14` → `0.23.0`, vitest `4.1.11` → `5.0.1`.
+- **Tests: 98 passing** (up from 94). Four new `tests/client/i18n.spec.ts` specs cover English and Chinese rendering of structured warnings, the structured-preferred/legacy-fallback path, and installation guidance that localizes without altering real commands.
+- **Unchanged**: the `0.1.6` adaptation (volatile `Config` form, `ctx.configForms` channel, profile-patch storage), the status read, the RPC channel, the sidebar chip, the detail panel and the LAN fallback.
+
 ## 0.1.6 — 2026-09-23
 
 Verified DeepSeek Harness: `0.1.7-rc.1` (the latest release candidate) and `0.1.7-alpha.2`. Full bilingual release notes: [`docs/releases/v0.1.6.md`](docs/releases/v0.1.6.md).

package/README.md

@@ -53,7 +53,7 @@ Requirements:
 
 - DeepSeek Harness with the Web profile
 - Node.js 20 or newer
-- Verified DSH releases: `0.1.7-rc.1` (latest RC) and `0.1.7-alpha.2`
+- Verified DSH releases: `0.1.7-rc.2` (latest RC), `0.1.7-rc.1` and `0.1.7-alpha.2`
 
 With an installed `dsh` command:
 
@@ -148,36 +148,40 @@ If you want DSH's stock policy instead (a non-loopback page never persists setti
 
 ## Compatibility
 
-Current release: plugin **`0.1.6`** is verified against DeepSeek Harness **`0.1.7-rc.1`** (the latest release candidate) and **`0.1.7-alpha.2`**.
+Current release: plugin **`0.1.8`** is verified against DeepSeek Harness **`0.1.7-rc.2`** (the latest release candidate), **`0.1.7-rc.1`** and **`0.1.7-alpha.2`**.
 
 ### Which plugin version goes with which DeepSeek Harness version
 
 | Plugin | Verified DeepSeek Harness | On npm | What that version is |
 | --- | --- | --- | --- |
-| **`0.1.6`** | `0.1.7-rc.1`, `0.1.7-alpha.2` | not published | Adapts to DSH 0.1.7: the preferences ARE the plugin entry's volatile `Config` (a form namespace is the Loader entry id), the official client channel is `ctx.configForms`, and `@deepseek-ai/schemastery` is a peer |
-| `0.1.5` | `0.1.6-alpha.2`, `0.1.6-alpha.1`, `0.1.5-rc.1` | `latest` | One dot carries every state (green up to date, grey checking, amber breathing update), neutral grey chip surface in both themes, and advisory notices no longer repaint the chip |
+| **`0.1.8`** | `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | `latest` | Version-matrix release: adds the running `0.1.7-rc.2` to the verified list after auditing the rc.1 → rc.2 interface delta; zero code change |
+| `0.1.7` | `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Runtime warnings become language-neutral codes rendered by the client, so the English UI is fully English; dev toolchain bumped |
+| `0.1.6` | `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Adapts to DSH 0.1.7: the preferences ARE the plugin entry's volatile `Config` (a form namespace is the Loader entry id), the official client channel is `ctx.configForms`, and `@deepseek-ai/schemastery` is a peer |
+| `0.1.5` | `0.1.6-alpha.2`, `0.1.6-alpha.1`, `0.1.5-rc.1` | published | One dot carries every state (green up to date, grey checking, amber breathing update), neutral grey chip surface in both themes, and advisory notices no longer repaint the chip |
 | `0.1.4` | `0.1.6-alpha.1`, `0.1.5-rc.1` | published | Fixes the unselectable "channel you are running"; preference writes locked by tests |
 | `0.1.3` | `0.1.6-alpha.1`, `0.1.5-rc.1` | published | Carries the `0.1.2` LAN (non-loopback) fix, re-verified on 0.1.6 and locked by tests |
 | `0.1.2` | `0.1.5-rc.1` | **never published** | Removed the `connection.isLoopback` gate, so LAN pages work |
 | `0.1.1` | `0.1.5-rc.1` | published | The previous npm `latest`; the plugin is inert on LAN/non-loopback pages |
 | `0.1.0` | `0.1.2-rc.1` | published | First release |
 
-- **`0.1.6` supports the DSH `0.1.7` line only.** DSH `0.1.7` removed the runtime `ctx.settings.register(...)` API and the `ctx.settingsScope` client service this plugin was built on, so `0.1.6` is the only release whose preferences work there. On an older DSH — including `0.1.6-alpha.2` — stay on plugin **`0.1.5`**.
+- **`0.1.6` through `0.1.8` support the DSH `0.1.7` line only.** DSH `0.1.7` removed the runtime `ctx.settings.register(...)` API and the `ctx.settingsScope` client service this plugin was built on, so those are the only releases whose preferences work there. On an older DSH — including `0.1.6-alpha.2` — stay on plugin **`0.1.5`**.
 - **Verified DeepSeek Harness** is the exact DSH release that plugin build was tested against. The list has one source of truth in two places — `VERIFIED_DSH_VERSIONS` in [`src/shared/types.ts`](src/shared/types.ts) and `dsh.compatibility.dshReleases` in [`package.json`](package.json) — and a test keeps them identical. A release that is not on the list is not declared compatible: verify it manually first, and if it turns out incompatible, disable or uninstall the plugin rather than patching DSH core. A release that is merely *not listed yet* is reported as **unverified**: that is an advisory in the panel only, and it never repaints the chip — an operator who upgrades DSH ahead of this plugin keeps a normal chip.
 - **On npm** is what `dsh plugin --profile web add dsh-update-status@latest` actually installs. A version that exists in this repository but not on npm is a development state, not a release.
 - Match them explicitly when it matters:
 
   ```sh
-  dsh plugin --profile web add dsh-update-status@0.1.6   # DSH 0.1.7-rc.1 or 0.1.7-alpha.2 (not on npm yet)
+  dsh plugin --profile web add dsh-update-status@0.1.8   # DSH 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
+  dsh plugin --profile web add dsh-update-status@0.1.7   # DSH 0.1.7-rc.1 or 0.1.7-alpha.2
+  dsh plugin --profile web add dsh-update-status@0.1.6   # DSH 0.1.7-rc.1 or 0.1.7-alpha.2
   dsh plugin --profile web add dsh-update-status@0.1.5   # DSH 0.1.6-alpha.2, 0.1.6-alpha.1 or 0.1.5-rc.1
   dsh plugin --profile web add dsh-update-status@0.1.4   # DSH 0.1.6-alpha.1 or 0.1.5-rc.1
   dsh plugin --profile web add dsh-update-status@0.1.0   # DSH 0.1.2-rc.1 only
   ```
 
 - Two declarations make the `0.1.7` line load at all, and a test keeps them honest:
-  - `dsh.engines.dsh` and `peerDependencies['@deepseek-ai/dsh-settings']` both declare `>=0.1.7-alpha.2 <0.2.0`, which admits both verified releases. The lower bound names the alpha on purpose — under node-semver's default prerelease rule a range like `>=0.1.6-0 <0.2.0` does **not** admit `0.1.7-alpha.2`. DSH `0.1.7-rc.1` also refuses an incompatible bundle at profile load, so a range that excluded the running release would silently drop the plugin.
+  - `dsh.engines.dsh` and `peerDependencies['@deepseek-ai/dsh-settings']` both declare `>=0.1.7-alpha.2 <0.2.0`, which admits all three verified releases. The lower bound names the alpha on purpose — under node-semver's default prerelease rule a range like `>=0.1.6-0 <0.2.0` does **not** admit `0.1.7-alpha.2`. DSH `0.1.7-rc.2` also refuses an incompatible bundle at profile load, so a range that excluded the running release would silently drop the plugin.
   - `@deepseek-ai/schemastery` is a **peer**, not a plain dependency: DSH 0.1.7 resolves only a linked plugin's peer dependencies from the running installation, so a `link:` install of this directory would otherwise fail to import the Host half.
-- Per-release notes — what changed, who is affected, what to do — are hand-written in Chinese and English and become the GitHub Release body: [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md) (covers the never-published `0.1.2`).
+- Per-release notes — what changed, who is affected, what to do — are hand-written in Chinese and English and become the GitHub Release body: [`v0.1.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.8.md) · [`v0.1.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.7.md) · [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md) (covers the never-published `0.1.2`).
 
 ## Configuration
 

package/README.zh.md

@@ -53,7 +53,7 @@
 
 - 带 Web profile 的 DeepSeek Harness
 - Node.js 20 或更新版本
-- 已验证的 DSH 版本：`0.1.7-rc.1`（最新 RC）与 `0.1.7-alpha.2`
+- 已验证的 DSH 版本：`0.1.7-rc.2`（最新 RC）、`0.1.7-rc.1` 与 `0.1.7-alpha.2`
 
 已经安装 `dsh` 命令：
 
@@ -148,36 +148,40 @@ DSH 对来源不是 loopback（`localhost` / `127.0.0.1`）的页面会关闭 Ho
 
 ## 兼容性
 
-当前发布：插件 **`0.1.6`** 已针对 DeepSeek Harness **`0.1.7-rc.1`**（最新候选版本）与 **`0.1.7-alpha.2`** 验证。
+当前发布：插件 **`0.1.8`** 已针对 DeepSeek Harness **`0.1.7-rc.2`**（最新候选版本）、**`0.1.7-rc.1`** 与 **`0.1.7-alpha.2`** 验证。
 
 ### 插件版本与 DeepSeek Harness 版本的对应关系
 
 | 插件版本 | 已验证的 DeepSeek Harness | npm 发布状态 | 该版本是什么 |
 | --- | --- | --- | --- |
-| **`0.1.6`** | `0.1.7-rc.1`、`0.1.7-alpha.2` | 未发布 | 适配 DSH 0.1.7：偏好设置就是插件条目的 volatile `Config`（设置表单命名空间 = loader 条目 id），官方客户端通道改为 `ctx.configForms`，`@deepseek-ai/schemastery` 改为 peer |
-| `0.1.5` | `0.1.6-alpha.2`、`0.1.6-alpha.1`、`0.1.5-rc.1` | `latest` | 一颗圆点承载全部状态（绿=已是最新、灰=检查中、橙=有新版本）、两套主题都用中性灰底框、提示性告警不再重绘芯片 |
+| **`0.1.8`** | `0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | `latest` | 版本矩阵发布：核对 rc.1 → rc.2 接口差异后，把正在运行的 `0.1.7-rc.2` 加入已验证清单；代码零改动 |
+| `0.1.7` | `0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 运行期告警改为语言中立的代码、由客户端按界面语言渲染，英文界面不再混入中文；dev 工具链升级 |
+| `0.1.6` | `0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 适配 DSH 0.1.7：偏好设置就是插件条目的 volatile `Config`（设置表单命名空间 = loader 条目 id），官方客户端通道改为 `ctx.configForms`，`@deepseek-ai/schemastery` 改为 peer |
+| `0.1.5` | `0.1.6-alpha.2`、`0.1.6-alpha.1`、`0.1.5-rc.1` | 已发布 | 一颗圆点承载全部状态（绿=已是最新、灰=检查中、橙=有新版本）、两套主题都用中性灰底框、提示性告警不再重绘芯片 |
 | `0.1.4` | `0.1.6-alpha.1`、`0.1.5-rc.1` | 已发布 | 修复「正在运行的通道不可选」；偏好写入路径补齐回归测试 |
 | `0.1.3` | `0.1.6-alpha.1`、`0.1.5-rc.1` | 已发布 | 含 `0.1.2` 的局域网（非回环）修复，并在 0.1.6 上复验、补上回归测试 |
 | `0.1.2` | `0.1.5-rc.1` | **未发布** | 移除 `connection.isLoopback` 门控，局域网页面可用 |
 | `0.1.1` | `0.1.5-rc.1` | 已发布 | 此前 npm 上的 `latest`；局域网/非回环页面下插件整体不可用 |
 | `0.1.0` | `0.1.2-rc.1` | 已发布 | 首个版本 |
 
-- **`0.1.6` 只支持 DSH `0.1.7` 线。** DSH `0.1.7` 移除了本插件赖以工作的运行时 `ctx.settings.register(...)` API 与 `ctx.settingsScope` 客户端服务，因此该版本线上只有 `0.1.6` 的偏好设置能工作；仍在更早的 DSH（含 `0.1.6-alpha.2`）上时，请继续使用插件 **`0.1.5`**。
+- **`0.1.6` 至 `0.1.8` 只支持 DSH `0.1.7` 线。** DSH `0.1.7` 移除了本插件赖以工作的运行时 `ctx.settings.register(...)` API 与 `ctx.settingsScope` 客户端服务，因此该版本线上只有它们的偏好设置能工作；仍在更早的 DSH（含 `0.1.6-alpha.2`）上时，请继续使用插件 **`0.1.5`**。
 - **已验证的 DeepSeek Harness** 是该插件构建实际测试过的确切 DSH 版本。这份清单只有两个存放处——[`src/shared/types.ts`](src/shared/types.ts) 的 `VERIFIED_DSH_VERSIONS` 与 [`package.json`](package.json) 的 `dsh.compatibility.dshReleases`——并有测试保证两者一致。未列出的 DSH 版本不会被宣称为兼容：请先人工验证；确认不兼容时请禁用或卸载插件，不要修改 DSH 核心。若只是**尚未列入**，插件会标为「尚未验证兼容」：这是**只出现在面板里**的提示，绝不会重绘芯片——DSH 升级快于插件时，芯片依然保持正常外观。
 - **npm 发布状态** 是 `dsh plugin --profile web add dsh-update-status@latest` 实际会装到的版本。只存在于本仓库、尚未发布到 npm 的版本属于开发状态，不是发布版本。
 - 需要精确对应时显式指定版本：
 
   ```sh
-  dsh plugin --profile web add dsh-update-status@0.1.6   # DSH 0.1.7-rc.1 或 0.1.7-alpha.2（尚未发布到 npm）
+  dsh plugin --profile web add dsh-update-status@0.1.8   # DSH 0.1.7-rc.2、0.1.7-rc.1 或 0.1.7-alpha.2
+  dsh plugin --profile web add dsh-update-status@0.1.7   # DSH 0.1.7-rc.1 或 0.1.7-alpha.2
+  dsh plugin --profile web add dsh-update-status@0.1.6   # DSH 0.1.7-rc.1 或 0.1.7-alpha.2
   dsh plugin --profile web add dsh-update-status@0.1.5   # DSH 0.1.6-alpha.2、0.1.6-alpha.1 或 0.1.5-rc.1
   dsh plugin --profile web add dsh-update-status@0.1.4   # DSH 0.1.6-alpha.1 或 0.1.5-rc.1
   dsh plugin --profile web add dsh-update-status@0.1.0   # 仅 DSH 0.1.2-rc.1
   ```
 
 - 有两处声明让 `0.1.7` 线能正常加载，并由测试守住：
-  - `dsh.engines.dsh` 与 `peerDependencies['@deepseek-ai/dsh-settings']` 都声明 `>=0.1.7-alpha.2 <0.2.0`，两个已验证版本都在范围内。下界特意写成这个 alpha：按 node-semver 默认的预发布规则，`>=0.1.6-0 <0.2.0` 这样的范围**并不接纳** `0.1.7-alpha.2`。另外 DSH `0.1.7-rc.1` 会在 profile 加载时拒绝不兼容的 bundle，范围若排除正在运行的版本，插件会被静默丢弃。
+  - `dsh.engines.dsh` 与 `peerDependencies['@deepseek-ai/dsh-settings']` 都声明 `>=0.1.7-alpha.2 <0.2.0`，三个已验证版本都在范围内。下界特意写成这个 alpha：按 node-semver 默认的预发布规则，`>=0.1.6-0 <0.2.0` 这样的范围**并不接纳** `0.1.7-alpha.2`。另外 DSH `0.1.7-rc.2` 会在 profile 加载时拒绝不兼容的 bundle，范围若排除正在运行的版本，插件会被静默丢弃。
   - `@deepseek-ai/schemastery` 是 **peer**，不是普通依赖：DSH 0.1.7 只从运行安装解析 link 插件的 peer 依赖，否则 `link:` 安装会连 Host 半边都 import 失败。
-- 每个版本的中英文详细说明（改了什么、影响谁、需要做什么）手写后直接作为 GitHub Release 正文：[`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md)（含从未发布的 `0.1.2`）。
+- 每个版本的中英文详细说明（改了什么、影响谁、需要做什么）手写后直接作为 GitHub Release 正文：[`v0.1.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.8.md) · [`v0.1.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.7.md) · [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md)（含从未发布的 `0.1.2`）。
 
 ## 配置
 

package/lib/client.js

@@ -261,6 +261,30 @@ window.__ModuleLoader__.load({
 				zh: "检查提示",
 				en: "Check notice"
 			},
+			"warning.registryUnavailable": {
+				zh: "无法检查 npm registry：{detail}",
+				en: "Unable to check the npm registry: {detail}"
+			},
+			"warning.channelUnavailable": {
+				zh: "npm registry 未发布 {channel} 通道。",
+				en: "The npm registry does not publish a {channel} channel."
+			},
+			"warning.versionIncomparable": {
+				zh: "无法按 SemVer 比较当前版本 {currentVersion} 与 {channel} 通道版本 {selectedVersion}。",
+				en: "Unable to compare the current version {currentVersion} with {channel} channel version {selectedVersion} using SemVer."
+			},
+			"warning.previewUnverified": {
+				zh: "{channel} 是预览通道，版本 {version} 尚未验证与本插件兼容。",
+				en: "{channel} is a preview channel; version {version} has not been verified as compatible with this plugin."
+			},
+			"guidance.sourceCheckout": {
+				zh: "请更新 DSH 源码 checkout、安装依赖并重新构建；本插件无法从 GUI 原地替换。",
+				en: "Update the DSH source checkout, install its dependencies, and rebuild it; this plugin cannot replace it in place from the GUI."
+			},
+			"guidance.unknownInstall": {
+				zh: "升级前请先确认 DSH 的安装方式；本插件无法代为执行升级。",
+				en: "Confirm how DSH was installed before upgrading; this plugin cannot perform the upgrade for you."
+			},
 			"panel.static": {
 				zh: "此连接只显示静态版本；请在运行 DSH 的本机打开侧栏查看完整更新信息。",
 				en: "This connection shows only the static version. Open the sidebar on the computer running DSH for full update details."
@@ -341,10 +365,35 @@ window.__ModuleLoader__.load({
 				return "en";
 			}
 		}
-		function t(key) {
+		function t(key, params = {}, language = languageOf()) {
 			const entry = DICTIONARY[key];
 			if (entry === void 0) return key;
-			return entry[languageOf()] ?? entry.en;
+			return (entry[language] ?? entry.en).replace(/\{([A-Za-z]+)\}/g, (match, name) => params[name] ?? match);
+		}
+		function warningText(warning, language = languageOf()) {
+			switch (warning.code) {
+				case "registry-unavailable": return t("warning.registryUnavailable", { detail: warning.detail }, language);
+				case "channel-unavailable": return t("warning.channelUnavailable", { channel: warning.channel }, language);
+				case "version-incomparable": return t("warning.versionIncomparable", {
+					currentVersion: warning.currentVersion,
+					channel: warning.channel,
+					selectedVersion: warning.selectedVersion
+				}, language);
+				case "preview-unverified": return t("warning.previewUnverified", {
+					channel: warning.channel,
+					version: warning.version
+				}, language);
+			}
+		}
+		/** Prefer structured warnings, but keep the Host string for mixed-version clients. */
+		function localizedWarning(status, language = languageOf()) {
+			const warnings = status.warnings ?? [];
+			return warnings.length === 0 ? status.warning : warnings.map((item) => warningText(item, language)).join(" ");
+		}
+		function localizedUpgradeGuidance(status, language = languageOf()) {
+			if (status.installKind === "source-checkout") return t("guidance.sourceCheckout", {}, language);
+			if (status.installKind === "unknown") return t("guidance.unknownInstall", {}, language);
+			return status.upgradeCommand;
 		}
 		//#endregion
 		//#region src/client/react.ts
@@ -533,10 +582,13 @@ window.__ModuleLoader__.load({
 				kind: "update",
 				text: t("panel.available")
 			};
-			if (status?.warning !== null && status?.warning !== void 0) return {
-				kind: "warning",
-				text: status.warning
-			};
+			if (status !== null) {
+				const warning = localizedWarning(status);
+				if (warning !== null) return {
+					kind: "warning",
+					text: warning
+				};
+			}
 			return {
 				kind: "ok",
 				text: t("panel.currentState")
@@ -588,9 +640,10 @@ window.__ModuleLoader__.load({
 			}, [panel.open, ui.panel]);
 			if (!visible) return null;
 			const status = snapshot.status;
+			const warning = status === null ? null : localizedWarning(status);
 			const summary = statusSummary(status, snapshot.loading, snapshot.error);
 			const switchingChannel = status !== null && status.channel !== preferences.channel;
-			const command = switchingChannel ? t("panel.switchingChannel") : status?.upgradeCommand ?? "—";
+			const command = switchingChannel ? t("panel.switchingChannel") : status === null ? "—" : localizedUpgradeGuidance(status);
 			const copy = async () => {
 				setCopyMessage(null);
 				try {
@@ -736,12 +789,12 @@ window.__ModuleLoader__.load({
 								}, release.channel);
 							})]
 						}),
-						status?.warning !== null && status?.warning !== void 0 && /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("p", {
+						warning !== null && /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("p", {
 							className: "dus-warning",
 							children: [
 								t("panel.error"),
 								": ",
-								status.warning
+								warning
 							]
 						}),
 						snapshot.error !== null && /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("p", {
@@ -953,6 +1006,29 @@ window.__ModuleLoader__.load({
 		function stringOrNull(value) {
 			return typeof value === "string" ? value : null;
 		}
+		function warningOf(value) {
+			if (value === null || typeof value !== "object" || Array.isArray(value)) return void 0;
+			const record = value;
+			if (record.code === "registry-unavailable" && typeof record.detail === "string") return {
+				code: record.code,
+				detail: record.detail
+			};
+			if (record.code === "channel-unavailable" && isReleaseChannel(record.channel)) return {
+				code: record.code,
+				channel: record.channel
+			};
+			if (record.code === "version-incomparable" && typeof record.currentVersion === "string" && isReleaseChannel(record.channel) && typeof record.selectedVersion === "string") return {
+				code: record.code,
+				currentVersion: record.currentVersion,
+				channel: record.channel,
+				selectedVersion: record.selectedVersion
+			};
+			if (record.code === "preview-unverified" && isReleaseChannel(record.channel) && typeof record.version === "string") return {
+				code: record.code,
+				channel: record.channel,
+				version: record.version
+			};
+		}
 		/** Reject malformed RPC output before it reaches a slot component. */
 		function updateStatusOf(value) {
 			if (value === null || typeof value !== "object" || Array.isArray(value)) return void 0;
@@ -965,6 +1041,15 @@ window.__ModuleLoader__.load({
 			const warningKind = record.warningKind === "failure" || record.warningKind === "notice" ? record.warningKind : void 0;
 			const publishedAt = record.publishedAt === null ? null : stringOrNull(record.publishedAt);
 			if (record.latestVersion !== null && latestVersion === null || record.checkedAt !== null && checkedAt === null || record.warning !== null && warning === null || record.publishedAt !== null && publishedAt === null) return void 0;
+			const warnings = [];
+			if (record.warnings !== void 0) {
+				if (!Array.isArray(record.warnings)) return void 0;
+				for (const raw of record.warnings) {
+					const parsed = warningOf(raw);
+					if (parsed === void 0) return void 0;
+					warnings.push(parsed);
+				}
+			}
 			const channels = [];
 			for (const raw of record.channels) {
 				if (raw === null || typeof raw !== "object" || Array.isArray(raw)) return void 0;
@@ -987,6 +1072,7 @@ window.__ModuleLoader__.load({
 				checkedAt,
 				warning,
 				warningKind,
+				warnings,
 				installKind: record.installKind,
 				upgradeCommand: record.upgradeCommand,
 				releaseUrl: record.releaseUrl,