@xmoon76/dsh-pi-tui 0.4.9 → 0.5.1

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,22 @@ 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.1` (stable / `@latest`) | `dsh-v0.2.0-rc.2` | Current stable line; both the minimum and the exact validation target are the 0.2.0-rc.2 family |
+| `0.5.0` (stable, previous) | `dsh-v0.1.7-rc.2`, `dsh-v0.2.0-rc.1` | Previous stable; 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
-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
+Do not mix the stable and `@next` prerelease lines. `0.5.1` lifts the whole DSH
+peer floor to `>=0.2.0-rc.2`: the Question lifecycle
+consumes contracts published only in rc.2 (the `userQuestions.attachWait`/
+`answer` Remotes and the `userQuestions` Session projection), so mixing in the
+rc.1 family would be a false compatibility statement. The previous stable `0.5.0`
+line keeps its `>=0.1.7-rc.2` floor (exact validation target 0.2.0-rc.1);
+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`
@@ -250,18 +256,50 @@ The editor supports two Shell modes:
 ! git status
 ```
 
-Runs a local command and submits its output into the current Session.
+Runs the command in the Host environment and submits its output into the current Session.
 
 ```text
 !! git status
 ```
 
-Runs the command locally only. Its output is not added to model context.
+Runs the command in the Host environment as well; its output stays out of model context (card display only).
 
 `!` / `!!` are editor modes rather than plain text prefixes. The prompt and completion behavior switch together with the active mode.
 
 Shell cards show a bounded output preview by default. `Ctrl+O` expands the retained output — except in fullscreen Focus, where Ctrl+O owns the Thought roots and the shell cards keep their folded state.
 
+### Git commit attribution (optional)
+
+When enabled, dsh-pi-tui instructs the Agent to add the official attribution trailers when it creates Git commits:
+
+```text
+Co-Authored-By: @xmoon76/dsh-pi-tui <dsh-pi-tui@xmoon.org>
+```
+
+It is **off by default**. Three modes are supported:
+
+```text
+off            no attribution guidance (default)
+product        the official Co-Authored-By trailer
+product-model  official trailer + Assisted-By: <provider>/<model>
+```
+
+This is **Agent guidance (a prompt policy), not repository-level enforcement**:
+dsh-pi-tui installs no Git hooks, rewrites no `git commit` command, and probes
+no repository. The `provider`/`model` in `product-model` come straight from
+DSH's official model selection (a model switch takes effect on the next
+request).
+
+Boundaries:
+
+- `!` / `!!` user shell commands and commits from your own terminal are completely untouched;
+- no `prepare-commit-msg` hook is installed and existing hooks are never modified;
+- **not effective under the `minimal` preset**: its persona is a complete system prompt
+  (`complete: true`) that replaces every other section — the same existing behavior for the
+  other TUI guidance (progress updates, response style, focus);
+- no GitHub credentials or API are required; the Author/Committer identity is never modified;
+- a model may in theory ignore or mis-transcribe the instruction — this is the accepted tradeoff: low-intrusion guidance instead of a full Git lifecycle subsystem.
+
 ### File references and images
 
 Typing `@` opens workspace file search and completion:
@@ -302,6 +340,29 @@ The `Icon style` option in `/settings` switches the TUI's structural icons:
 symbols), or `Minimal` (decorative icons hidden; only status/interaction
 markers remain). Switching applies immediately and persists.
 
+The `Terminal progress` row in `/settings` selects the native terminal status
+reporting in four modes: `9;4+7501` (default — both the OSC 9;4 progress bar and
+the OSC 7501 semantic state), `9;4` (progress-bar compatibility only), `7501`
+(semantic state only: working, waiting for approval/answer, done, error) and
+`Off` (clear and stop reporting). Switching applies immediately; done and error
+are reported only once a real run's last turn result is proven, while a
+cancelled or interrupted run returns to idle. A persisted `On` reads as the
+dual-protocol default.
+
+Terminal compatibility: a terminal that does not know OSC 7501 simply ignores
+it — Ghostty's GUI currently shows the OSC 9;4 progress bar and not the 7501
+semantic state, which is expected and not a reporting failure. Inside tmux and
+other terminal multiplexers an unknown OSC may not be forwarded to the outer
+terminal (this feature deliberately implements no tmux DCS passthrough and does
+not change multiplexer settings); use an outer terminal that supports it when
+the state must survive a multiplexer. The OSC 7501 semantic state describes the
+current Main Agent only.
+
+This project's own Remote composition (experimental, our Host) reports the same
+state: the Host side is served by this extension's private Host status stream and
+shares ONE interval classifier with Direct. **A third-party DSH Host without this
+extension's Host plugin is not supported** (it has no equivalent event source).
+
 Slash Commands registered by other plugins through `ctx.commands` are discovered automatically.
 
 ### Footer customization
@@ -349,7 +410,7 @@ For the full `/footer` workflow, Custom Text / Command items, YAML reference, se
 | `Tab`         | Autocomplete slash commands and file paths          |
 | `@`           | File completion                                     |
 | `!`           | Enter Shell mode                                    |
-| `!!`          | Enter local-only Shell mode                         |
+| `!!`          | Enter Session-excluded Shell mode                   |
 
 Use `/help` inside the TUI for the current command and keybinding list. The table above shows the defaults; after customization, `/help` and `/keybindings` show the effective keys.
 
@@ -595,8 +656,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.2` family declared by this checkout's `package.json` and
+resolved by its lockfile (the runtime peer floor is also `>=0.2.0-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,19 @@ 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.1`（stable / `@latest`） | `dsh-v0.2.0-rc.2` | 当前稳定版；最低与精确验证目标均为 0.2.0-rc.2 family |
+| `0.5.0`（stable，历史） | `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 统一为
-`>=0.1.7-rc.2`（rc.2 的 preset registry 精确 peer `dsh-agent`，更宽的旧
-floor 已无法满足独立 tarball 安装）；旧 runtime 会在正常的不兼容边界以非零状态失败，
+不要把稳定线与 `@next` 预发布线混装。`0.5.1` 把整个 DSH peer
+floor 提升到 `>=0.2.0-rc.2`：Question 生命周期消费 rc.2 才发布的公开契约
+（`userQuestions.attachWait`/`answer` Remote 与 `userQuestions` Session
+projection），rc.1 family 不提供这些契约，混装属于虚假的兼容声明。上一稳定版
+`0.5.0` 保持 `>=0.1.7-rc.2` floor 不变（精确验证目标 0.2.0-rc.1）；旧
+runtime 会在正常的不兼容边界以非零状态失败，
 请按上表安装配对的 TUI 线。完整的历史兼容矩阵和 fallback 命令见
 [兼容性文档](docs/dsh-compatibility.md)；要查看 `@next` 的最新集成状态，请看
 [next 分支 README](https://github.com/XMoon/dsh-pi-tui/blob/next/README.md)。
@@ -216,18 +221,49 @@ Footer `↓` 打开的 Quick Tasks 是轻量浏览视图，只提供方向键导
 ! git status
 ```
 
-执行本地命令，并把输出提交到当前 Session。
+在宿主（Host）环境执行命令，并把输出提交到当前 Session。
 
 ```text
 !! git status
 ```
 
-只在本地执行，输出不会进入模型上下文。
+同样在宿主环境执行，但输出不进入模型上下文（仅卡片展示）。
 
 `!` / `!!` 是独立的编辑器模式，而不是普通文本前缀。进入 Shell 模式后 Prompt 和补全行为会同步切换。
 
 Shell 卡片默认只显示有限的输出预览，`Ctrl+O` 可以展开完整保留内容——全屏 Focus 除外:那里 `Ctrl+O` 负责 Thought root 的整体开关,Shell 卡片保持折叠。
 
+### Git 提交署名（可选）
+
+开启后，dsh-pi-tui 会指示 Agent 在创建 Git 提交时加上官方项目署名：
+
+```text
+Co-Authored-By: @xmoon76/dsh-pi-tui <dsh-pi-tui@xmoon.org>
+```
+
+默认 **关闭**。支持三种模式：
+
+```text
+off            不添加署名指引（默认）
+product        官方 Co-Authored-By 署名
+product-model  官方署名 + Assisted-By: <provider>/<model>
+```
+
+这是 **Agent 指引（prompt policy），不是仓库级强制**：dsh-pi-tui 不会安装 Git
+钩子、不改写任何 `git commit` 命令、也不探测仓库。`product-model` 的
+`provider`/`model` 由 DSH 官方模型选择直接注入（切换模型后下一次请求生效）。
+
+边界说明：
+
+- `!` / `!!` 用户 Shell 和你自己终端里的手动提交完全不受影响；
+- 不安装任何 `prepare-commit-msg` 钩子，不修改已有钩子；
+- **使用 `minimal` preset 时不生效**：该 preset 的 persona 是完整 system prompt
+  （`complete: true`），会替换掉其它全部 section；既有的 TUI 指引（Progress updates、
+  Response style、Focus）在该 preset 下同样是这种既有行为；
+- 不需要 GitHub 凭证/API；不修改 Author/Committer 身份；
+- 模型理论上可能忽略或写错指引——这是有意的取舍：用低侵入的指引替代一整套
+  Git 生命周期子系统。
+
 ### 文件引用与图片
 
 输入 `@` 可以搜索和补全工作区文件：
@@ -267,6 +303,23 @@ TUI 使用 DSH 提供的模型和设置服务。
 彩色)、`Symbols`(紧凑的单格终端符号)、`Minimal`(隐藏装饰性图标,只
 保留状态/交互标记);切换立即生效并持久化。
 
+`/settings` 中的 `Terminal progress` 控制原生终端状态上报,共四档:
+`9;4+7501`(默认,同时上报 OSC 9;4 进度条与 OSC 7501 语义状态)、
+`9;4`(只保留进度条兼容协议)、`7501`(只上报语义状态:运行中 / 等待审批 /
+等待回答 / 完成 / 出错)、`Off`(清除并停止上报)。切换立即生效;完成与出错
+只在一次真实运行的最后一个 turn 结果被证实后上报,中断或取消会回到空闲。
+旧的 `On` 配置读作默认双协议。
+
+终端兼容性说明:不认识 OSC 7501 的终端会直接忽略它——目前 Ghostty 的 GUI
+只显示 OSC 9;4 进度条、不显示 7501 语义状态,这是预期行为,不代表上报失败。
+在 tmux 等终端复用器里,未知 OSC 可能不会被转发到外层终端(本功能有意不实现
+tmux 的 DCS passthrough,也不修改复用器设置);需要跨复用器保留状态时请直接
+使用支持它的外层终端。此外,OSC 7501 的语义状态只作用于当前 Main Agent。
+
+本项目的 Remote(实验性、自有 Host 组合)同样上报这套状态:Host 侧由本扩展自带的
+私有状态流提供,并与 Direct 共用同一份区间判定。**未安装本项目 Host 扩展的第三方
+DSH Host 不支持**这套上报(它没有对应的事件源)。
+
 其他插件注册到 `ctx.commands` 的 Slash Command 也会被自动发现。
 
 ### Footer 自定义
@@ -313,8 +366,8 @@ TUI 使用 DSH 提供的模型和设置服务。
 | `Ctrl+V`      | 粘贴图片                   |
 | `Tab`         | 补全斜杠命令与文件路径           |
 | `@`           | 文件补全                   |
-| `!`           | 进入 Shell 模式            |
-| `!!`          | 进入 Local-only Shell 模式 |
+| `!`           | 进入 Shell 模式（结果进 Session） |
+| `!!`          | 进入 Session 排除的 Shell 模式     |
 
 完整按键和命令以 TUI 中的 `/help` 为准。表中的快捷键是默认值;用户自定义后,以 `/help` 和 `/keybindings` 显示的生效键位为准。
 
@@ -549,7 +602,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.2` family 为精确验证目标（运行时
+peer floor 同为 `>=0.2.0-rc.2`）。隔离的 npm
 驱动从公共 registry 安装该精确 family，并跑完整 build/test/package 路径：
 
 ```sh

package/cordis.patch.yml

@@ -64,6 +64,19 @@
     - id: workspace
       name: '@deepseek-ai/dsh-workspace'
 
+    # The OFFICIAL Host `@`-file reference authority (M3-3A): this row is
+    # the same one the official web bundle mounts. It provides
+    # `ctx.fileReferences` (the discovery service the Session Controller's
+    # `fileReferences/list` Remote already forwards to) AND installs the
+    # official per-agent `context:file-reference` system prompt — the model
+    # guidance that relative `@` paths resolve from the workspace root.
+    # Mounting it aligns the TUI's `@`-mention semantics with the official
+    # client contract: the selected mention text goes to the prompt
+    # LITERALLY (`@src/foo.ts`), and the Host/model resolves it; the TUI's
+    # historical send-time absolute-path rewrite is retired with it.
+    - id: file-reference-local
+      name: '@deepseek-ai/dsh-file-reference-local'
+
     # The authorization seam (`ctx.authorization`): plugin-owned credential-
     # obtaining flows, one attempt per key, transport-neutral notices and
     # prompts. The dsh host does NOT mount it anywhere (the base layer ships

package/dist/builtins.mjs

@@ -1,20 +1,16 @@
-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 { readFileSync } from "node:fs";
-import { join } from "node:path";
+import { a as PI_TUI_EXTENSIONS_SERVICE, gt as __exportAll } from "./extensions-1WYBUQ8I.mjs";
+import { n as TUI_STARTUP_SERVICE } from "./startup-CmTYVTGC.mjs";
+import { n as dshVersion, t as bundleVersion } from "./version-a-eF-QER.mjs";
 //#region src/builtins.ts
+var builtins_exports = /* @__PURE__ */ __exportAll({
+	apply: () => apply,
+	inject: () => inject,
+	name: () => name
+});
 /** Stable Cordis plugin name for the builtins row. */
 const name = "pi-tui-builtins";
 /** The builtins mount only when the TUI startup flags were parsed. */
 const inject = [TUI_STARTUP_SERVICE, PI_TUI_EXTENSIONS_SERVICE];
-/** The `@xmoon76/dsh-pi-tui` package version (dist/extensions.mjs → ../package.json). */
-function packageVersion() {
-	try {
-		return JSON.parse(readFileSync(join(import.meta.dirname, "..", "package.json"), "utf8")).version ?? "0.0.0";
-	} catch {
-		return "0.0.0";
-	}
-}
 /**
 * Register the first-party chrome contributions. The turn/step footer
 * segment subscribes to the surface state and re-bakes via handle.replace
@@ -33,7 +29,7 @@ function apply(ctx) {
 		order: 1e3,
 		description: "The dsh and bundle versions (first-party builtin)."
 	}, {
-		text: installedDsh === void 0 ? `tui-v${packageVersion()}` : `dsh-${installedDsh} · tui-v${packageVersion()}`,
+		text: installedDsh === void 0 ? `tui-v${bundleVersion()}` : `dsh-${installedDsh} · tui-v${bundleVersion()}`,
 		tone: "info"
 	});
 	const todoDock = service.register("input.dock.item", {
@@ -42,7 +38,7 @@ function apply(ctx) {
 		description: "The todo summary line (first-party builtin)."
 	}, { label: [] });
 	const renderTodoDock = (state) => {
-		const summary = state.activity.todoSummary;
+		const summary = state.session.displaySubject === void 0 ? state.activity.todoSummary : state.session.displaySubject.todoSummary;
 		if (summary === void 0 || summary === "") {
 			todoDock.replace({ label: [] });
 			return;
@@ -61,4 +57,4 @@ function apply(ctx) {
 	});
 }
 //#endregion
-export { apply, inject, name };
+export { apply, inject, name, builtins_exports as t };

package/dist/extension/advanced.d.mts

@@ -1,4 +1,4 @@
-import { D as PiTuiApiInfo, E as NormalizedKey, _ as ExtensionTier, h as EditorSnapshot, ot as TuiOverlayOptions, v as ExtensionView } from "../public-types-YbB5Rhku.mjs";
+import { D as PiTuiApiInfo, E as NormalizedKey, _ as ExtensionTier, h as EditorSnapshot, ot as TuiOverlayOptions, v as ExtensionView } from "../public-types-BEjj7FEb.mjs";
 
 //#region src/extension/advanced-types.d.ts
 /** API level of the advanced tier. Bumped only on advanced breaking changes. */

package/dist/extension/unstable.d.mts

@@ -1,4 +1,4 @@
-import { D as PiTuiApiInfo, _ as ExtensionTier, ot as TuiOverlayOptions } from "../public-types-YbB5Rhku.mjs";
+import { D as PiTuiApiInfo, _ as ExtensionTier, ot as TuiOverlayOptions } from "../public-types-BEjj7FEb.mjs";
 
 //#region src/extension/unstable-types.d.ts
 /** API level of the unstable tier. Bumped only on unstable breaking changes. */