@xmoon76/dsh-pi-tui 0.4.9 → 0.5.0

package/README.en.md

@@ -19,7 +19,7 @@ Stable releases are recommended for ordinary users. Install DSH first, then add
 the TUI to the `pi-tui` profile:
 
 ```sh
-npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@latest
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty @deepseek-ai/dsh@latest
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
@@ -30,7 +30,7 @@ Preview installation uses the DSH `alpha` channel and the TUI `next` channel.
 The DSH native install scripts must be explicitly allowed:
 
 ```sh
-npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@alpha
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty @deepseek-ai/dsh@alpha
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
 dsh --profile pi-tui
 ```
@@ -54,16 +54,19 @@ next compatibility range, and fallback paths.
 
 | TUI package line | Official DSH tags for the pairing | Notes |
 |---|---|---|
-| `0.4.9` (stable / `@latest`) | `dsh-v0.1.7-rc.2` | Current stable line; 0.1.7-rc.2 minimum |
+| `0.5.0` (stable / `@latest`) | `dsh-v0.1.7-rc.2`, `dsh-v0.2.0-rc.1` | Current stable line; 0.1.7-rc.2 minimum, exact validation target 0.2.0-rc.1 |
+| `0.4.9` (stable, previous) | `dsh-v0.1.7-rc.2` | Previous stable; the compatible TUI for a 0.1.7-rc.2 runtime |
 | `0.4.8` (stable, previous) | `dsh-v0.1.7-rc.1` | Previous stable; the compatible TUI for a 0.1.7-rc.1 runtime |
 | `0.4.6` (stable, previous) | `dsh-v0.1.5-rc.1`, `dsh-v0.1.5-rc.2` | Previous stable; the compatible TUI for a 0.1.5 runtime |
 | `0.4.7-alpha.2` (next, previous) | `dsh-v0.1.6-alpha.2` | Previous next line; the compatible TUI for a 0.1.6-alpha.2 runtime |
 
-Do not mix the stable and `@next` prerelease lines. The `0.4.9` line unifies its
+Do not mix the stable and `@next` prerelease lines. The `0.5.0` line unifies its
 whole DSH peer floor at `>=0.1.7-rc.2` (the rc.2 preset registry peers
 `dsh-agent` exactly, so a wider legacy floor no longer satisfies a standalone
-tarball install); older runtimes fail at the normal incompatible-runtime
-boundary, so install the paired TUI line from the table above. The startup notice
+tarball install), while its exact validation and recommended upgrade target is
+the published `0.2.0-rc.1` family; older runtimes fail at the normal
+incompatible-runtime boundary, so install the paired TUI line from the table
+above. The startup notice
 is best-effort rather than a Loader startup-order guarantee. See the [full
 historical compatibility matrix](docs/dsh-compatibility.md) for official-tag
 pairings and fallback commands, and see the [latest `next`
@@ -595,8 +598,9 @@ This section contains DSH compatibility and CI validation details only; ordinary
 ### npm mode (current `next`)
 
 The current compatibility-train line is npm mode: it targets the published
-`dsh-v0.1.7-rc.2` family declared by this checkout's `package.json` and
-resolved by its lockfile. The isolated npm driver installs that exact
+`dsh-v0.2.0-rc.1` family declared by this checkout's `package.json` and
+resolved by its lockfile (the runtime peer floor stays `>=0.1.7-rc.2`). The
+isolated npm driver installs that exact
 family from the public registry and exercises the TUI build/test/package path:
 
 ```sh

package/README.md

@@ -18,7 +18,7 @@
 稳定版是普通用户的推荐渠道。请先安装 DSH，再将 TUI 添加到 `pi-tui` profile：
 
 ```sh
-npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@latest
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty @deepseek-ai/dsh@latest
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
 dsh --profile pi-tui
 ```
@@ -29,7 +29,7 @@ dsh --profile pi-tui
 时需要显式允许其原生安装脚本：
 
 ```sh
-npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty,@google/genai,protobufjs,fs-ext @deepseek-ai/dsh@alpha
+npm install -g --allow-scripts=@deepseek-ai/dsh-subprocess-local,koffi,node-pty @deepseek-ai/dsh@alpha
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
 dsh --profile pi-tui
 ```
@@ -52,14 +52,16 @@ pnpm compat:dsh:npm
 
 | TUI 包版本 | 对应的官方 DSH tags | 说明 |
 |---|---|---|
-| `0.4.9`（stable / `@latest`） | `dsh-v0.1.7-rc.2` | 当前稳定版；最低 0.1.7-rc.2 |
+| `0.5.0`（stable / `@latest`） | `dsh-v0.1.7-rc.2`、`dsh-v0.2.0-rc.1` | 当前稳定版；最低 0.1.7-rc.2，精确验证目标 0.2.0-rc.1 |
+| `0.4.9`（stable，历史） | `dsh-v0.1.7-rc.2` | 上一稳定版；0.1.7-rc.2 runtime 的兼容 TUI |
 | `0.4.8`（stable，历史） | `dsh-v0.1.7-rc.1` | 上一稳定版；0.1.7-rc.1 runtime 的兼容 TUI |
 | `0.4.6`（stable，历史） | `dsh-v0.1.5-rc.1`、`dsh-v0.1.5-rc.2` | 上一稳定版；0.1.5 runtime 的兼容 TUI |
 | `0.4.7-alpha.2`（next，历史） | `dsh-v0.1.6-alpha.2` | 上一条 next 线；0.1.6-alpha.2 runtime 的兼容 TUI |
 
-不要把稳定线与 `@next` 预发布线混装。`0.4.9` 的整个 DSH peer floor 统一为
+不要把稳定线与 `@next` 预发布线混装。`0.5.0` 的整个 DSH peer floor 统一为
 `>=0.1.7-rc.2`（rc.2 的 preset registry 精确 peer `dsh-agent`，更宽的旧
-floor 已无法满足独立 tarball 安装）；旧 runtime 会在正常的不兼容边界以非零状态失败，
+floor 已无法满足独立 tarball 安装），精确验证与推荐升级目标是已发布的
+`0.2.0-rc.1` family；旧 runtime 会在正常的不兼容边界以非零状态失败，
 请按上表安装配对的 TUI 线。完整的历史兼容矩阵和 fallback 命令见
 [兼容性文档](docs/dsh-compatibility.md)；要查看 `@next` 的最新集成状态，请看
 [next 分支 README](https://github.com/XMoon/dsh-pi-tui/blob/next/README.md)。
@@ -549,7 +551,8 @@ dsh --profile pi-tui-dev
 ### npm 模式（当前 `next`）
 
 当前兼容列车线是 npm 模式：以本 checkout 的 `package.json` 声明、
-lockfile 解析的已发布 `dsh-v0.1.7-rc.2` family 为兼容目标。隔离的 npm
+lockfile 解析的已发布 `dsh-v0.2.0-rc.1` family 为精确验证目标（运行时
+peer floor 保持 `>=0.1.7-rc.2`）。隔离的 npm
 驱动从公共 registry 安装该精确 family，并跑完整 build/test/package 路径：
 
 ```sh

package/dist/builtins.mjs

@@ -1,5 +1,6 @@
-import { L as dshVersion, V as PI_TUI_EXTENSIONS_SERVICE } from "./src-BAwPimrH.mjs";
-import { n as TUI_STARTUP_SERVICE } from "./startup-xTIOW90U.mjs";
+import { n as TUI_STARTUP_SERVICE } from "./startup-DM-xxzcX.mjs";
+import { i as PI_TUI_EXTENSIONS_SERVICE } from "./extensions-Dg1qhjUi.mjs";
+import { n as dshVersion } from "./dsh-version-V0exEv9O.mjs";
 import { readFileSync } from "node:fs";
 import { join } from "node:path";
 //#region src/builtins.ts

package/dist/dsh-version-V0exEv9O.mjs

@@ -0,0 +1,76 @@
+import { readFileSync, realpathSync } from "node:fs";
+import { dirname, join } from "node:path";
+//#region src/dsh-version.ts
+/**
+* The installed dsh (DeepSeek Harness CLI) version, resolved from the
+* launcher's real path: `process.argv[1]` is the `dsh` bin, whose realpath
+* walks up to the `@deepseek-ai/dsh/package.json` that owns it. The header
+* and the welcome card show the harness the TUI runs on, not this bundle's
+* own patch level. Undefined when the launcher path is unreadable.
+*
+* The module also owns the bundle's OWN version reads (`bundleVersion`) and
+* the combined welcome-card display line (`versionDisplay`).
+* @module @xmoon76/dsh-pi-tui/dsh-version
+*/
+/** @returns the installed dsh version string, or undefined. */
+function dshVersion() {
+	const bin = process.argv[1];
+	if (bin === void 0) return void 0;
+	try {
+		let dir = dirname(realpathSync(bin));
+		for (let depth = 0; depth < 8; depth += 1) {
+			try {
+				const pkg = JSON.parse(readFileSync(join(dir, "package.json"), "utf8"));
+				if (pkg.name === "@deepseek-ai/dsh" && typeof pkg.version === "string") return pkg.version;
+			} catch {}
+			const parent = dirname(dir);
+			if (parent === dir) return void 0;
+			dir = parent;
+		}
+	} catch {}
+}
+/**
+* The bundle's own version, read from package.json at runtime so the welcome
+* card never drifts from the shipped version. The DISPLAYED version prefers
+* the installed dsh version (`dshVersion` — shared with the header badge
+* via src/dsh-version.ts), falling back to this one.
+* @returns the version string, or a fallback when the file is unreadable.
+*/
+function packageVersion() {
+	try {
+		const pkg = JSON.parse(readFileSync(join(import.meta.dirname, "..", "package.json"), "utf8"));
+		return dshVersion() ?? pkg.version ?? "0.0.0";
+	} catch {
+		return dshVersion() ?? "0.0.0";
+	}
+}
+/**
+* The welcome card's version line: the installed dsh version plus the
+* bundle's own version (header-badge parity — `dsh-0.1.7-rc.2 ·
+* tui-v0.4.9`). Without a resolvable dsh launcher it degrades to
+* the bundle version alone.
+* @returns the combined version string.
+*/
+function versionDisplay() {
+	const dsh = dshVersion();
+	return dsh === void 0 ? `tui-v${bundleVersion()}` : `dsh-${dsh} · tui-v${bundleVersion()}`;
+}
+/**
+* The BUNDLE's OWN version (`@xmoon76/dsh-pi-tui`'s package.json),
+* INDEPENDENT of the installed dsh version. The status snapshot's
+* host.tuiVersion and the footer's `version(format=tui)` item must report
+* the TUI's own patch level — the welcome-card helper above deliberately
+* prefers the dsh version for display, so reusing it made `tui` show the
+* harness version (and `both` show the dsh version twice) inside a real
+* dsh installation (the review's P2).
+* @returns the bundle version string, or a fallback when the file is unreadable.
+*/
+function bundleVersion() {
+	try {
+		return JSON.parse(readFileSync(join(import.meta.dirname, "..", "package.json"), "utf8")).version ?? "0.0.0";
+	} catch {
+		return "0.0.0";
+	}
+}
+//#endregion
+export { versionDisplay as i, dshVersion as n, packageVersion as r, bundleVersion as t };