@xmoon76/dsh-pi-tui 0.4.0 → 0.4.1

package/README.en.md

@@ -9,24 +9,96 @@ A Pi-style terminal frontend for [DeepSeek Harness](https://github.com/deepseek-
 
 `dsh-pi-tui` is installed as an independent dsh bundle inside a profile. It provides terminal interaction for streaming conversations, tool calls, session management, subagents, history search, shell commands, approvals, and settings. Models, tools, Sessions, permissions, Skills, Plan, Goal, and Subagent runtime behavior are still provided by DeepSeek Harness.
 
+![dsh-pi-tui](docs/dsh-pi-tui.png)
+
+## Install into a DSH profile
+
+### Stable / latest
+
+Stable releases are recommended for ordinary users. Install DSH first, then add
+the TUI to the `pi-tui` profile:
+
+```sh
+npm install -g @deepseek-ai/dsh@0.1.2-rc.1
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
+dsh --profile pi-tui
+```
+
+### Preview / next
+
+Preview releases contain unreleased changes. Use this channel only when you need
+to try or validate a prerelease:
+
 ```sh
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
 dsh --profile pi-tui
 ```
 
-![dsh-pi-tui](docs/dsh-pi-tui.png)
+### Requirements
 
-## DSH compatibility and source validation
+* DeepSeek Harness
+* Node.js `^22.19.0 || >=24`
 
-The published package declares the lower-bound-only DSH peer contract `>=0.1.2-rc.1`. Source validation does not change that contract or vendor DSH into this repository.
+### DSH/TUI version pairing (important)
 
-When the target DSH version is not yet available from npm, validate against the official checkout pinned by commit SHA:
+| TUI package line | Matching DSH line | Notes |
+|---|---|---|
+| `0.4.1` (`@latest`) | `>=0.1.2-rc.1` | Current stable; validated against the rc.1 family |
+| `0.4.x-alpha` (`@next`) | `>=0.1.2-rc.1` | Subsequent prerelease; each release validates its concrete DSH family |
+| `0.4.0-alpha.2` (published) | `>=0.1.2-alpha.4` | Previous 0.4 prerelease; its releases validated the alpha.4/alpha.5 family |
+| `0.4.0-alpha.1` (published) | `>=0.1.2-alpha.2` | Earlier 0.4 prerelease; accepts the alpha.2/alpha.3 runtime |
+| `0.3.x` (`@0.3`) | `0.1.1-rc.2` | Legacy runtime line |
+
+Do not mix the lines: DSH 0.1.1 is outside the 0.4 peer window and the
+normal incompatible-runtime boundary will fail. The startup row prints upgrade
+and rollback guidance when concurrent Loader ordering allows it, but that
+friendly notice is best-effort rather than a startup-order guarantee. If you
+keep DSH 0.1.1, use the 0.3 TUI line; if you keep the alpha.2/alpha.3
+baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`; if you keep the
+alpha.4/alpha.5 baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`. The stable
+installation path is documented above under “Install into a DSH profile”; if
+you need to keep the legacy DSH runtime, use this compatibility recovery path:
 
 ```sh
-pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
+npm install -g @deepseek-ai/dsh@0.1.1-rc.2
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
+dsh --profile pi-tui
 ```
 
-CI follows the tracked `test/compat/dsh-mode.json` policy for pushes to `next` and pull requests targeting `next`; `main` and every tag use npm Mode. Both `next` lanes use `test/compat/dsh-source.json` for the current validated DSH target; Source Mode validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary, while npm Mode runs the frozen registry lane. The published `pi2dsh` ecosystem check is explicitly marked skipped for an unpublished source family. See [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md) for the full workflow.
+The current 0.4 line declares `>=0.1.2-rc.1`; each release validates
+its concrete DSH family. `npm install -g` is only for installing DSH itself; to
+install dsh-pi-tui into a DSH profile, you must use the `dsh plugin` command.
+
+New agent sessions use the official roster's selected preset id. A custom DSH
+preset literally named `code` is valid and remains `code` when it exists in the
+current roster. Old persisted `code` defaults/session values fall back to `ptc`
+only after the roster proves that no custom `code` preset exists.
+
+### Profile management
+
+Update the installed TUI:
+
+```sh
+dsh plugin --profile pi-tui -- update @xmoon76/dsh-pi-tui
+```
+
+List installed plugins:
+
+```sh
+dsh plugin --profile pi-tui -- list
+```
+
+Remove the plugin:
+
+```sh
+dsh plugin --profile pi-tui -- remove @xmoon76/dsh-pi-tui
+```
+
+Resume an existing Session:
+
+```sh
+dsh --profile pi-tui --session <session-id>
+```
 
 ## Features
 
@@ -94,7 +166,8 @@ Regular `↑` / `↓` history recall is still available for recent input.
 
 ### Subagents and background tasks
 
-`/tasks` opens the task browser for the current Session.
+`/tasks` opens the full Task Center for all background work in the current
+Session; the Footer's `↓` opens the lightweight Quick Tasks view for running work.
 
 Subagents are shown using their complete lineage, including nested descendants:
 
@@ -113,6 +186,12 @@ The browser distinguishes:
 * nested descendants
 * background Jobs
 
+The two views share the same runtime state: `A` toggles Active / All scope,
+`Tab` changes type filters, `/` enters search, `S` stops the selected task after
+confirmation, and `N` / `Shift+N` moves between running tasks. In Quick Tasks,
+`T` or the bottom “View all” row opens the full Task Center, and `Esc` returns
+one layer at a time.
+
 Completed one-shot Subagents remain available for persisted Transcript inspection.
 
 A direct `continuable` Child can be opened in an interactive viewer and sent follow-up messages directly (through DSH's official `subagents.prompt()` human channel — queued in order as the Child's own next turn, with user provenance). The Child has its own Transcript, Draft, and runtime state, without modifying the main Session input.
@@ -219,8 +298,8 @@ For the full `/footer` workflow, Custom Text / Command items, YAML reference, se
 | `Shift+Enter` | Insert newline                                      |
 | `Esc`         | Cancel current interaction / interrupt running work |
 | `Esc Esc`     | Open Rewind while idle                              |
-| `Ctrl+C`      | Interrupt / clear current input                     |
-| `Ctrl+D`      | Quit the TUI (like `/exit`)                         |
+| `Ctrl+C`      | Keyboard exit confirmation; clears the draft first |
+| `Ctrl+D`      | Keyboard exit confirmation when empty; forward-delete with draft text |
 | `Ctrl+S`      | Steer queued messages and the draft into the running turn |
 | `Ctrl+T`      | Toggle the todo panel                               |
 | `Ctrl+R`      | Search input history                                |
@@ -308,102 +387,6 @@ dsh-pi-tui:
   works; only `false` removes every trigger of an action.
 
 
-## Installation
-
-### Requirements
-
-* DeepSeek Harness
-* Node.js `^22.19.0 || >=24`
-
-### DSH/TUI version pairing (important)
-
-| TUI package line | Matching DSH line | Notes |
-|---|---|---|
-| `0.4.0` (`@latest`) | `>=0.1.2-rc.1` | Current stable; validated against the rc.1 family |
-| `0.4.x-alpha` (`@next`) | `>=0.1.2-rc.1` | Subsequent prerelease; each release validates its concrete DSH family |
-| `0.4.0-alpha.2` (published) | `>=0.1.2-alpha.4` | Previous 0.4 prerelease; its releases validated the alpha.4/alpha.5 family |
-| `0.4.0-alpha.1` (published) | `>=0.1.2-alpha.2` | Earlier 0.4 prerelease; accepts the alpha.2/alpha.3 runtime |
-| `0.3.x` (`@0.3`) | `0.1.1-rc.2` | Legacy runtime line |
-
-Do not mix the lines: DSH 0.1.1 is outside the 0.4 peer window and the
-normal incompatible-runtime boundary will fail. The startup row prints upgrade
-and rollback guidance when concurrent Loader ordering allows it, but that
-friendly notice is best-effort rather than a startup-order guarantee. If you
-keep DSH 0.1.1, use the 0.3 TUI line; if you keep the alpha.2/alpha.3
-baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`; if you keep the
-alpha.4/alpha.5 baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`. For the
-current 0.4 stable release, install the matching DSH first and then add the
-TUI to a profile:
-
-```sh
-npm install -g @deepseek-ai/dsh@0.1.2-rc.1
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
-dsh --profile pi-tui
-```
-
-If you need to keep the legacy DSH runtime:
-
-```sh
-npm install -g @deepseek-ai/dsh@0.1.1-rc.2
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
-dsh --profile pi-tui
-```
-
-The current 0.4 line declares `>=0.1.2-rc.1`; each release validates
-its concrete DSH family. Running only `npm install -g @xmoon76/dsh-pi-tui` does
-not install the plugin into a DSH profile; the `dsh plugin` command is still
-required.
-
-New agent sessions use the official roster's selected preset id. A custom DSH
-preset literally named `code` is valid and remains `code` when it exists in the
-current roster. Old persisted `code` defaults/session values fall back to `ptc`
-only after the roster proves that no custom `code` preset exists.
-
-### npm
-
-Using a dedicated `pi-tui` profile is recommended. Use the TUI channel that
-matches your DSH line: `@latest` for stable releases, `@next` for prereleases:
-
-```sh
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
-dsh --profile pi-tui
-```
-
-Resume an existing Session:
-
-```sh
-dsh --profile pi-tui --session <session-id>
-```
-
-### Source Mode (validation only)
-
-Source Mode is the validation-only distribution selected by the tracked policy for `next` CI and available for local compatibility checks. It reads the full commit pin in `test/compat/dsh-source.json`, builds the official DSH tarball family, installs it through temporary pnpm overrides, and removes the temporary state afterward. Do not write DSH source paths, `file:` dependencies, or workspace symlinks into a published package.
-
-```sh
-pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
-pnpm compat:dsh:npm
-```
-
-The published package already contains the Pi TUI fork required at runtime. No separate internal TUI package needs to be installed.
-
-### Update
-
-```sh
-dsh plugin --profile pi-tui -- update @xmoon76/dsh-pi-tui
-```
-
-List installed plugins:
-
-```sh
-dsh plugin --profile pi-tui -- list
-```
-
-Remove:
-
-```sh
-dsh plugin --profile pi-tui -- remove @xmoon76/dsh-pi-tui
-```
-
 ## Running from source
 
 ```sh
@@ -566,6 +549,25 @@ dsh plugin --profile pi-tui-dev -- add @xmoon76/dsh-pi-tui@link:$PWD
 dsh --profile pi-tui-dev
 ```
 
+## DSH compatibility and validation
+
+This section contains Source Mode and CI validation details only; ordinary users do not need Source Mode to install the TUI.
+
+### Source Mode (validation only)
+
+Source Mode is the validation-only distribution selected by the tracked policy for `next` CI and available for local compatibility checks. It reads the full commit pin in `test/compat/dsh-source.json`, builds the official DSH tarball family, installs it through temporary pnpm overrides, and removes the temporary state afterward. Do not write DSH source paths, `file:` dependencies, or workspace symlinks into a published package.
+
+```sh
+pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
+pnpm compat:dsh:npm
+```
+
+The published package already contains the Pi TUI fork required at runtime. No separate internal TUI package needs to be installed.
+
+### CI validation policy
+
+CI follows the tracked `test/compat/dsh-mode.json` policy for pushes to `next` and pull requests targeting `next`; `main` and every tag use npm Mode. Both `next` lanes use `test/compat/dsh-source.json` for the current validated DSH target; Source Mode validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary, while npm Mode runs the frozen registry lane. The published `pi2dsh` ecosystem check is explicitly marked skipped for an unpublished source family. See [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md) for the full workflow.
+
 ## Repository layout
 
 The repository root is the npm package published as `@xmoon76/dsh-pi-tui`.

package/README.md

@@ -9,24 +9,92 @@
 
 `dsh-pi-tui` 作为独立的 dsh bundle 安装到 profile 中，提供流式对话、工具调用、会话管理、Subagent、历史搜索、Shell、审批与设置等终端交互。模型、工具、Session、权限、Skills、Plan、Goal、Subagent 等运行时能力仍由 DeepSeek Harness 提供。
 
+![dsh-pi-tui](docs/dsh-pi-tui.png)
+
+## 安装到 DSH Profile
+
+### Stable / latest
+
+稳定版是普通用户的推荐渠道。请先安装 DSH，再将 TUI 添加到 `pi-tui` profile：
+
+```sh
+npm install -g @deepseek-ai/dsh@0.1.2-rc.1
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
+dsh --profile pi-tui
+```
+
+### Preview / next
+
+预览版包含未发布的变更，仅在需要体验或验证预发布版本时使用：
+
 ```sh
 dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
 dsh --profile pi-tui
 ```
 
-![dsh-pi-tui](docs/dsh-pi-tui.png)
+### 环境要求
 
-## DSH 兼容性与源码验证
+* DeepSeek Harness
+* Node.js `^22.19.0 || >=24`
 
-发布包通过 `package.json` peer contract 使用 DSH `>=0.1.2-rc.1`；源码验证不会修改这个发布契约，也不会把 DSH vendor 进本仓库。
+### DSH 与 TUI 版本对应（重要）
 
-当目标 DSH 版本尚未发布到 npm 时，可以用固定 commit 的官方源码包做本地验证：
+| TUI 包版本 | 对应 DSH 版本 | 说明 |
+|---|---|---|
+| `0.4.1`（`@latest`） | `>=0.1.2-rc.1` | 当前稳定版；按 0.1.2-rc.1 family 验证 |
+| `0.4.x-alpha`（`@next`） | `>=0.1.2-rc.1` | 后续预发布线；按每个发布版本的具体 DSH family 验证 |
+| `0.4.0-alpha.2`（已发布） | `>=0.1.2-alpha.4` | 上一条 0.4 预发布线；其发布版本按 alpha.4/alpha.5 family 验证 |
+| `0.4.0-alpha.1`（已发布） | `>=0.1.2-alpha.2` | 更早的 0.4 预发布线；接受 alpha.2/alpha.3 运行时 |
+| `0.3.x`（`@0.3`） | `0.1.1-rc.2` | 旧运行时兼容线 |
+
+不要把两条线混装：DSH 0.1.1 不在 0.4 的 peer 支持范围内，运行时会在
+正常的不兼容边界以非零状态失败。启动行会在 Loader 并发挂载顺序允许时打印
+升级和回退提示，但该友好提示是 best-effort，不是启动顺序保证；保留 DSH
+0.1.1 时请使用 0.3，保留 alpha.2/alpha.3 时请使用
+`@xmoon76/dsh-pi-tui@0.4.0-alpha.1`，保留 alpha.4/alpha.5 时请使用
+`@xmoon76/dsh-pi-tui@0.4.0-alpha.2`。稳定版的安装方式已在上方“安装到 DSH
+Profile”中给出；如果需要保留旧 DSH，请使用下面的兼容恢复路径：
 
 ```sh
-pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
+npm install -g @deepseek-ai/dsh@0.1.1-rc.2
+dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
+dsh --profile pi-tui
 ```
 
-CI 对 push 到 `next` 以及目标为 `next` 的 PR 遵循跟踪的 `test/compat/dsh-mode.json` 策略；`main` 和所有 tag 使用 npm Mode。`next` 的两种 lane 都从 `test/compat/dsh-source.json` 读取当前 validated DSH target；Source Mode 会验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界，npm Mode 则运行冻结的 registry lane。对于尚未发布的 source family，已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
+`0.4` 当前线的声明支持范围是 `>=0.1.2-rc.1`；每个发布版本都会验证
+具体的 DSH family。`npm install -g` 仅用于安装 DSH 本身；要将 dsh-pi-tui
+安装进 DSH profile，必须使用 `dsh plugin` 命令。
+
+新的 Agent preset 使用当前 roster 中选定的 id。DSH 允许合法的自定义
+`code` preset；只要当前 roster 存在它，显式输入和持久化状态都会保留 `code`。
+旧数据中省略请求的 `code` default/session 值只有在确认 roster 不含 `code` 后
+才会回退到 `ptc`。
+
+### Profile management
+
+更新已安装的 TUI：
+
+```sh
+dsh plugin --profile pi-tui -- update @xmoon76/dsh-pi-tui
+```
+
+查看已安装插件：
+
+```sh
+dsh plugin --profile pi-tui -- list
+```
+
+卸载：
+
+```sh
+dsh plugin --profile pi-tui -- remove @xmoon76/dsh-pi-tui
+```
+
+恢复已有 Session：
+
+```sh
+dsh --profile pi-tui --session <session-id>
+```
 
 ## 功能
 
@@ -218,8 +286,8 @@ TUI 使用 DSH 提供的模型和设置服务。
 | `Shift+Enter` | 换行                     |
 | `Esc`         | 取消当前交互 / 中断运行          |
 | `Esc Esc`     | 空闲时打开 Rewind           |
-| `Ctrl+C`      | 中断 / 清空当前输入            |
-| `Ctrl+D`      | 退出 TUI(等同 `/exit`)    |
+| `Ctrl+C`      | 键盘退出确认;首次清空草稿       |
+| `Ctrl+D`      | 空草稿时键盘退出确认;有内容时向前删除 |
 | `Ctrl+S`      | Steer:把队列消息和草稿一起发送到正在运行的回合 |
 | `Ctrl+T`      | 切换 Todo 面板              |
 | `Ctrl+R`      | 搜索输入历史                 |
@@ -297,99 +365,6 @@ dsh-pi-tui:
   移除某 action 的全部触发。
 
 
-## 安装
-
-### 环境要求
-
-* DeepSeek Harness
-* Node.js `^22.19.0 || >=24`
-
-### DSH 与 TUI 版本对应（重要）
-
-| TUI 包版本 | 对应 DSH 版本 | 说明 |
-|---|---|---|
-| `0.4.0`（`@latest`） | `>=0.1.2-rc.1` | 当前稳定版；按 0.1.2-rc.1 family 验证 |
-| `0.4.x-alpha`（`@next`） | `>=0.1.2-rc.1` | 后续预发布线；按每个发布版本的具体 DSH family 验证 |
-| `0.4.0-alpha.2`（已发布） | `>=0.1.2-alpha.4` | 上一条 0.4 预发布线；其发布版本按 alpha.4/alpha.5 family 验证 |
-| `0.4.0-alpha.1`（已发布） | `>=0.1.2-alpha.2` | 更早的 0.4 预发布线；接受 alpha.2/alpha.3 运行时 |
-| `0.3.x`（`@0.3`） | `0.1.1-rc.2` | 旧运行时兼容线 |
-
-不要把两条线混装：DSH 0.1.1 不在 0.4 的 peer 支持范围内，运行时会在
-正常的不兼容边界以非零状态失败。启动行会在 Loader 并发挂载顺序允许时打印
-升级和回退提示，但该友好提示是 best-effort，不是启动顺序保证；保留 DSH
-0.1.1 时请使用 0.3，保留 alpha.2/alpha.3 时请使用
-`@xmoon76/dsh-pi-tui@0.4.0-alpha.1`，保留 alpha.4/alpha.5 时请使用
-`@xmoon76/dsh-pi-tui@0.4.0-alpha.2`。当前 0.4 稳定版的推荐安装顺序如下
-（先装 DSH，再把 TUI 装入 profile）：
-
-```sh
-npm install -g @deepseek-ai/dsh@0.1.2-rc.1
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
-dsh --profile pi-tui
-```
-
-如果需要保留旧 DSH：
-
-```sh
-npm install -g @deepseek-ai/dsh@0.1.1-rc.2
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
-dsh --profile pi-tui
-```
-
-`0.4` 当前线的声明支持范围是 `>=0.1.2-rc.1`；每个发布版本都会验证
-具体的 DSH family。仅执行 `npm install -g @xmoon76/dsh-pi-tui` 不会把插件安装进
-DSH profile，实际使用仍应执行上面的 `dsh plugin` 命令。
-
-新的 Agent preset 使用当前 roster 中选定的 id。DSH 允许合法的自定义
-`code` preset；只要当前 roster 存在它，显式输入和持久化状态都会保留 `code`。
-旧数据中省略请求的 `code` default/session 值只有在确认 roster 不含 `code` 后
-才会回退到 `ptc`。
-
-### npm
-
-推荐使用单独的 `pi-tui` profile。使用与 DSH 版本匹配的
-TUI channel（稳定版用 `@latest`，预发布版用 `@next`）：
-
-```sh
-dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
-dsh --profile pi-tui
-```
-
-恢复已有 Session：
-
-```sh
-dsh --profile pi-tui --session <session-id>
-```
-
-### Source Mode（仅验证）
-
-Source Mode 是 `next` CI 按跟踪策略选用的、并可用于本地兼容性检查的验证专用 distribution。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
-
-```sh
-pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
-pnpm compat:dsh:npm
-```
-
-安装包已经包含运行所需的 Pi TUI fork，不需要额外安装内部的 TUI package。
-
-### 更新
-
-```sh
-dsh plugin --profile pi-tui -- update @xmoon76/dsh-pi-tui
-```
-
-查看已安装插件：
-
-```sh
-dsh plugin --profile pi-tui -- list
-```
-
-卸载：
-
-```sh
-dsh plugin --profile pi-tui -- remove @xmoon76/dsh-pi-tui
-```
-
 ## 从源码运行
 
 ```sh
@@ -552,6 +527,25 @@ dsh plugin --profile pi-tui-dev -- add @xmoon76/dsh-pi-tui@link:$PWD
 dsh --profile pi-tui-dev
 ```
 
+## DSH 兼容性与验证
+
+以下内容仅介绍 Source Mode 和 CI 验证细节；普通用户无需使用 Source Mode 安装 TUI。
+
+### Source Mode（仅验证）
+
+Source Mode 是 `next` CI 按跟踪策略选用的、并可用于本地兼容性检查的验证专用 distribution。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
+
+```sh
+pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
+pnpm compat:dsh:npm
+```
+
+安装包已经包含运行所需的 Pi TUI fork，不需要额外安装内部的 TUI package。
+
+### CI 验证策略
+
+CI 对 push 到 `next` 以及目标为 `next` 的 PR 遵循跟踪的 `test/compat/dsh-mode.json` 策略；`main` 和所有 tag 使用 npm Mode。`next` 的两种 lane 都从 `test/compat/dsh-source.json` 读取当前 validated DSH target；Source Mode 会验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界，npm Mode 则运行冻结的 registry lane。对于尚未发布的 source family，已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
+
 ## 项目结构
 
 仓库根目录是发布到 npm 的 `@xmoon76/dsh-pi-tui` bundle。

package/dist/builtins.mjs

@@ -1,4 +1,4 @@
-import { H as PI_TUI_EXTENSIONS_SERVICE, L as dshVersion } from "./src-zkySYmLZ.mjs";
+import { H as PI_TUI_EXTENSIONS_SERVICE, L as dshVersion } from "./src-CeGK2mHo.mjs";
 import { TUI_STARTUP_SERVICE } from "./startup.mjs";
 import { readFileSync } from "node:fs";
 import { join } from "node:path";

package/dist/extensions.mjs

@@ -1,3 +1,3 @@
-import { B as inject, H as PI_TUI_EXTENSIONS_SERVICE, U as API_VERSION, V as name, W as describeKey, z as apply } from "./src-zkySYmLZ.mjs";
+import { B as inject, H as PI_TUI_EXTENSIONS_SERVICE, U as API_VERSION, V as name, W as describeKey, z as apply } from "./src-CeGK2mHo.mjs";
 import "./startup.mjs";
 export { API_VERSION, PI_TUI_EXTENSIONS_SERVICE, apply, describeKey, inject, name };

package/dist/index.mjs

@@ -1,3 +1,3 @@
-import { A as shouldConsumeAdvertisedMiss, C as normalizeSkillInvocation, D as resumeCommand, E as resolveInitialCatalog, F as teardownViewerForSessionSwap, I as viewerActionCapability, M as subagentJobTranscriptId, N as subagentJobViewHint, O as runningProfile, P as subagentNoticeIsFailure, R as forkSeed, S as name, T as recordedPreset, _ as interruptAgent, a as SessionLockRefusedError, b as isUserQueueInput, c as commandRejectsImages, d as contextRefreshKind, f as createViewerOpenToken, g as inject, h as foldQueueRows, i as SESSIONLESS_COMMANDS, j as shouldSteerOnEnter, k as settleCompactionSurface, l as compactingFromLog, m as foldCompactionEvent, n as HOST_COMMAND_CATALOG, o as apply, p as dangerCommand, r as LOCAL_COMMANDS, s as busyAfterTurnBoundary, t as Config, u as composeAgent, v as isPlainExitPrompt, w as recomposeBlank, x as matchPendingSubagentCall, y as isSubagentSettlementNotice } from "./src-zkySYmLZ.mjs";
+import { A as shouldConsumeAdvertisedMiss, C as normalizeSkillInvocation, D as resumeCommand, E as resolveInitialCatalog, F as teardownViewerForSessionSwap, I as viewerActionCapability, M as subagentJobTranscriptId, N as subagentJobViewHint, O as runningProfile, P as subagentNoticeIsFailure, R as forkSeed, S as name, T as recordedPreset, _ as interruptAgent, a as SessionLockRefusedError, b as isUserQueueInput, c as commandRejectsImages, d as contextRefreshKind, f as createViewerOpenToken, g as inject, h as foldQueueRows, i as SESSIONLESS_COMMANDS, j as shouldSteerOnEnter, k as settleCompactionSurface, l as compactingFromLog, m as foldCompactionEvent, n as HOST_COMMAND_CATALOG, o as apply, p as dangerCommand, r as LOCAL_COMMANDS, s as busyAfterTurnBoundary, t as Config, u as composeAgent, v as isPlainExitPrompt, w as recomposeBlank, x as matchPendingSubagentCall, y as isSubagentSettlementNotice } from "./src-CeGK2mHo.mjs";
 import "./startup.mjs";
 export { Config, HOST_COMMAND_CATALOG, LOCAL_COMMANDS, SESSIONLESS_COMMANDS, SessionLockRefusedError, apply, busyAfterTurnBoundary, commandRejectsImages, compactingFromLog, composeAgent, contextRefreshKind, createViewerOpenToken, dangerCommand, foldCompactionEvent, foldQueueRows, forkSeed, inject, interruptAgent, isPlainExitPrompt, isSubagentSettlementNotice, isUserQueueInput, matchPendingSubagentCall, name, normalizeSkillInvocation, recomposeBlank, recordedPreset, resolveInitialCatalog, resumeCommand, runningProfile, settleCompactionSurface, shouldConsumeAdvertisedMiss, shouldSteerOnEnter, subagentJobTranscriptId, subagentJobViewHint, subagentNoticeIsFailure, teardownViewerForSessionSwap, viewerActionCapability };