dsh-plugin-bridge 0.2.11 → 0.3.1

package/README.md

@@ -9,8 +9,9 @@
 [![ci](https://github.com/Totoro-qaq/dsh-plugin-bridge/actions/workflows/ci.yml/badge.svg)](https://github.com/Totoro-qaq/dsh-plugin-bridge/actions/workflows/ci.yml)
 [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)
 [![node ≥22](https://img.shields.io/badge/node-%E2%89%A522-339933)](package.json)
-[![dsh rc.6 → 0.1.1-rc.2](https://img.shields.io/badge/dsh-rc.6%20%E2%86%92%200.1.1--rc.2-4c8dff)](https://github.com/deepseek-ai/deepseek-harness)
+[![dsh rc.6 → 0.1.2-alpha.2](https://img.shields.io/badge/dsh-rc.6%20%E2%86%92%200.1.2--alpha.2-4c8dff)](https://github.com/deepseek-ai/deepseek-harness)
 [![Listed in Awesome DSH Plugin](https://img.shields.io/badge/listed_in-Awesome_DSH_Plugin-2ea44f)](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)
+[![dshfind](https://dshfind.com/api/badge/Totoro-qaq/dsh-plugin-bridge?lang=en)](https://dshfind.com/en/plugins/Totoro-qaq/dsh-plugin-bridge?ref=badge)
 
 English | [中文](README.zh.md)
 
@@ -34,7 +35,7 @@ dsh plugin --profile web add dsh-plugin-bridge
 Pinned GitHub fallback:
 
 ```bash
-dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.2.10
+dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.1
 ```
 
 Then type in the official WebUI:
@@ -47,12 +48,16 @@ Then type in the official WebUI:
 /bridge code --go --continue  restate and start work in the same target request
 ```
 
-The preview is editable. Correct a number or path in the printed summary file, then run:
+On DSH rc.7 and later, the official WebUI renders `/bridge` as a native card. **Text** exposes the fixed five sections as ordinary fields and list rows; **Markdown** preserves full source freedom; **Preview** renders Markdown or a complete JSON tree. Long content scrolls inside the card while the action bar stays reachable. **Confirm migration** opens the created target session.
+
+UIs that implement the official `conversation.chat.commandview` slot receive the same card automatically. Other custom UIs retain the complete server result, summary-file workflow, and target title/session-ID fallback; UI authors can reuse the framework-free `dsh-plugin-bridge/client-contract` export instead of reimplementing the wire. On an older or non-slot client, correct the printed summary file and run:
 
 ```text
 /bridge code --go --file <path>
 ```
 
+Preview edits are temporary until migration is confirmed. Restarting the client or system may discard them; the source session remains untouched, and you can regenerate the preview.
+
 Uninstall with `dsh plugin --profile web remove dsh-plugin-bridge`, then restart `dsh web`.
 
 ## Why Bridge
@@ -78,6 +83,8 @@ The release gate is intentionally small and reproducible; these are regression r
 | Confirm / `--continue` target request shape | **2 · 1** to first useful work |
 | Confirm extra, paired nominal median | **+8.1%** vs `--continue` |
 | Summary worker share of clean acceptance components | **20.74% nominal** |
+| Native WebUI repeat gate (preview / target facts) | **3/3 · 3/3**, five facts each |
+| DSH 0.1.2-alpha.2 npm install / doctor / target | **clean · 13/13 · PTC paused** |
 
 The token percentage varies widely with preset, response length, and cache state. The worker share is composition, not causal overhead versus no Bridge; the stable product claim is one additional confirmation request. Read the [design and evidence boundaries](docs/design.md), [full release report](reports/v0.2.3-e2e-report.md), and [vision report](reports/v0.2.6-rc11-vision-report.md).
 
@@ -105,23 +112,24 @@ The five sections are Goal, Current state, Key decisions and conventions, Key fi
 
 ## Compatibility
 
-| DSH baseline | Text handoff | Raw unresolved image | Verification boundary |
+| DSH baseline | Server handoff | Native card | Verification boundary |
 |---|---:|---:|---|
-| 0.1.0-rc.6 / rc.7 | Yes | Optional gateway unavailable | Narrow RPC contract and text compatibility tests |
-| 0.1.0-rc.8 | Yes | Host-dependent | Real install, restart, command lifecycle, and migration baseline |
-| 0.1.1-rc.2 | Yes | Yes | Official WebUI migration with `deepseek-v4-flash-vision-exp`, 13/13 doctor methods, and 5/5 vision gates |
+| 0.1.0-rc.6 | Yes | No | Narrow RPC contract and text compatibility tests |
+| 0.1.0-rc.7 / rc.8 | Yes | Contract-checked | Client-module/command-slot contract plus server fallback |
+| 0.1.1-rc.2 | Yes | Yes | Installed official WebUI: doctor 13/13, edit/confirm/auto-open, three-run repeat gate |
+| 0.1.2-alpha.2 | Yes | Yes | Official npm install: typed controllers 13/13, split-client build, edit/confirm/PTC auto-open, clean removal |
 
 CI covers Node.js 22 and 24. Run `/bridge --doctor` after every Harness upgrade; it names missing required gateway methods instead of failing vaguely.
 
 Current limits:
 
 - installation needs one WebUI restart;
-- Bridge prints the created title and session ID because stable plugin-driven session navigation is not yet available;
-- preview normally takes 20–60 seconds and is bounded by `previewTimeoutMs`;
+- the native card auto-opens the created target through the official Session runtime; older clients still receive the title and session ID fallback;
+- progress appears immediately while the worker runs; the current fixed three-run sample took 7.4–12.8 seconds of worker time, while `previewTimeoutMs` remains the hard bound;
 - text-only models cannot inspect unresolved images;
-- each release-acceptance cell currently has one run, so the tables are release evidence rather than statistical guarantees.
+- the native-card repeat gate is still only three fixed runs, so it is release evidence rather than a statistical guarantee.
 
-The server command stays the compatibility core. A native migration card is technically possible through official client modules and slots, but is intentionally deferred until that prerelease contract is stable; see the [feasibility note](docs/native-webui-feasibility.md).
+The server command stays the compatibility core. The same package now adds an optional official client half for rendered editing and navigation; if that prerelease client contract fails to load, `/bridge` still returns the complete server result. See the [implementation boundary](docs/native-webui-feasibility.md).
 
 ## Documentation
 
@@ -129,6 +137,8 @@ The server command stays the compatibility core. A native migration card is tech
 - [Chinese install, configuration, rollback, and FAQ](docs/guide.zh.md)
 - [Release acceptance report](reports/v0.2.3-e2e-report.md)
 - [Vision migration report](reports/v0.2.6-rc11-vision-report.md)
+- [Native WebUI repeat acceptance](reports/native-workbench-2026-08-25.md)
+- [DSH 0.1.2-alpha.2 compatibility acceptance](reports/dsh-0.1.2-alpha.2-compat-2026-08-31.md)
 - [Historical compression benchmark](docs/benchmark.md)
 
 ## Development
@@ -138,10 +148,12 @@ npm ci
 npm run verify
 ```
 
-`verify` builds and type-checks the project, runs 125 fake-host tests, checks generated `lib/` and datasets, then packs, installs, and imports the actual npm tarball. Tests spend no model tokens. `prepublishOnly` runs the same gate; GitHub releases also require the tag to match `package.json` before trusted npm publishing.
+`verify` builds and type-checks both plugin halves, runs 167 tests, checks generated `lib/` and datasets, then packs, installs, and imports the actual npm tarball. Tests spend no model tokens. `prepublishOnly` runs the same gate; GitHub releases also require the tag to match `package.json` before trusted npm publishing.
 
 Community listings: [Awesome DSH Plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin) · [Awesome DeepSeek Harness](https://github.com/Dominic789654/awesome-deepseek-harness)
 
+Ecosystem discovery: [dsh-TUI](https://github.com/ccch1mneyyy/dsh-TUI). Bridge remains a standard DSH plugin; TUI/std conformance is tracked separately.
+
 ## License
 
 MIT

package/README.zh.md

@@ -9,8 +9,9 @@
 [![ci](https://github.com/Totoro-qaq/dsh-plugin-bridge/actions/workflows/ci.yml/badge.svg)](https://github.com/Totoro-qaq/dsh-plugin-bridge/actions/workflows/ci.yml)
 [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)
 [![node ≥22](https://img.shields.io/badge/node-%E2%89%A522-339933)](package.json)
-[![dsh rc.6 → 0.1.1-rc.2](https://img.shields.io/badge/dsh-rc.6%20%E2%86%92%200.1.1--rc.2-4c8dff)](https://github.com/deepseek-ai/deepseek-harness)
+[![dsh rc.6 → 0.1.2-alpha.2](https://img.shields.io/badge/dsh-rc.6%20%E2%86%92%200.1.2--alpha.2-4c8dff)](https://github.com/deepseek-ai/deepseek-harness)
 [![收录于 Awesome DSH Plugin](https://img.shields.io/badge/%E5%B7%B2%E6%94%B6%E5%BD%95-Awesome_DSH_Plugin-2ea44f)](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)
+[![dshfind](https://dshfind.com/api/badge/Totoro-qaq/dsh-plugin-bridge?lang=zh)](https://dshfind.com/zh/plugins/Totoro-qaq/dsh-plugin-bridge?ref=badge)
 
 [English](README.md) | 中文
 
@@ -34,7 +35,7 @@ dsh plugin --profile web add dsh-plugin-bridge
 GitHub 固定版本备用路径：
 
 ```bash
-dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.2.10
+dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.1
 ```
 
 然后在官方 WebUI 输入：
@@ -47,12 +48,16 @@ dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.2.10
 /bridge code --go --continue  在同一次目标请求里复述并开始工作
 ```
 
-预览可以编辑。数字或路径不对时，修改输出里打印的摘要文件，再执行：
+DSH rc.7 及以上会在官方 WebUI 原生卡片中渲染 `/bridge`。「文本编辑」把固定五段变成普通文本框和逐条列表；「Markdown」保留完整源码自由；「预览」渲染 Markdown 或完整 JSON 树。长内容只在卡片正文内滚动，操作按钮保持可达；点「确认迁移」后自动打开目标会话。
+
+实现官方 `conversation.chat.commandview` slot 的第三方 UI 会自动得到同一张卡片。其他自定义 UI 仍保留完整服务端结果、摘要文件流程和目标标题/session ID 回退；UI 作者还可以复用无 React 的 `dsh-plugin-bridge/client-contract` 导出，而无需重写协议。旧客户端可修改输出里打印的摘要文件，再执行：
 
 ```text
 /bridge code --go --file <路径>
 ```
 
+预览中的修改在确认迁移前只是临时草稿。重启客户端或系统可能使其丢失；源会话始终不受影响，重新运行预览即可生成新的草稿。
+
 卸载：`dsh plugin --profile web remove dsh-plugin-bridge`，然后重启 `dsh web`。
 
 ## 为什么是 Bridge
@@ -78,6 +83,8 @@ dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.2.10
 | Confirm / `--continue` 到首次有效工作的目标请求数 | **2 · 1** |
 | Confirm 相对 `--continue` 的 nominal 配对中位额外成本 | **+8.1%** |
 | 摘要 worker 在干净验收组件中的 nominal 占比 | **20.74%** |
+| 原生 WebUI 重复门禁（预览 / 目标事实） | **3/3 · 3/3**，每次五项 |
+| DSH 0.1.2-alpha.2 npm 安装 / doctor / 目标 | **干净 · 13/13 · PTC 已暂停** |
 
 token 百分比会随 preset、回复长度和缓存状态大幅波动；worker 占比是组成，不是相对“无 Bridge”的因果开销。稳定结论是默认确认多一个请求。边界和原始证据见[设计与证据说明](docs/design.md)、[完整 release report](reports/v0.2.3-e2e-report.md)和[视觉迁移报告](reports/v0.2.6-rc11-vision-report.md)。
 
@@ -105,23 +112,24 @@ token 百分比会随 preset、回复长度和缓存状态大幅波动；worker
 
 ## 兼容性
 
-| DSH 基线 | 文本交接 | 未解析原图 | 验证边界 |
+| DSH 基线 | 服务端交接 | 原生卡片 | 验证边界 |
 |---|---:|---:|---|
-| 0.1.0-rc.6 / rc.7 | 支持 | 无可选附件网关 | 窄 RPC 契约与文本兼容测试 |
-| 0.1.0-rc.8 | 支持 | 取决于 host | 真实安装、重启、命令生命周期和迁移基线 |
-| 0.1.1-rc.2 | 支持 | 支持 | 官方 WebUI + `deepseek-v4-flash-vision-exp`，doctor 13/13，视觉 gate 5/5 |
+| 0.1.0-rc.6 | 支持 | 不支持 | 窄 RPC 契约与文本兼容测试 |
+| 0.1.0-rc.7 / rc.8 | 支持 | 契约核对 | client module / command slot 契约与服务端回退 |
+| 0.1.1-rc.2 | 支持 | 支持 | 官方 WebUI 实装：doctor 13/13、编辑/确认/自动跳转、三次重复门禁 |
+| 0.1.2-alpha.2 | 支持 | 支持 | 官方 npm 实装：typed controllers 13/13、拆分 client 构建、编辑/确认/PTC 自动跳转、干净卸载 |
 
 CI 覆盖 Node.js 22/24。每次升级 Harness 后先跑 `/bridge --doctor`；缺哪个必要网关方法会被直接点名。
 
 当前边界：
 
 - 安装后需要重启一次 WebUI；
-- 官方尚无稳定的插件跳转目标会话接口，Bridge 会打印新会话标题和 ID；
-- 预览通常 20–60 秒，并受 `previewTimeoutMs` 限制；
+- 原生卡片通过官方 Session runtime 自动打开目标；旧客户端仍回退为标题和 ID；
+- worker 运行时立即显示进度；本次三次固定样本的 worker 用时为 7.4–12.8 秒，`previewTimeoutMs` 仍是硬上限；
 - 纯文本模型无法读取未解析原图；
-- release acceptance 每个 cell 目前只有一次运行，表格是发布证据，不是统计保证。
+- 原生卡片重复门禁也只有三次固定输入，是发布证据，不是统计保证。
 
-服务端命令仍是兼容核心。官方 client module 与 slot 已证明原生迁移卡片可行，但其 prerelease 契约还不稳定，因此暂不把它塞进 v0.2.10；详见[可行性记录](docs/native-webui-feasibility.md)。
+服务端命令仍是兼容核心。同一个包现在附带可选的官方 WebUI client half，负责渲染、编辑和跳转；即使 prerelease 客户端契约加载失败，`/bridge` 的完整服务端结果仍在。详见[实现边界](docs/native-webui-feasibility.md)。
 
 ## 文档
 
@@ -129,6 +137,8 @@ CI 覆盖 Node.js 22/24。每次升级 Harness 后先跑 `/bridge --doctor`；
 - [中文安装、配置、回退与 FAQ](docs/guide.zh.md)
 - [完整 release acceptance](reports/v0.2.3-e2e-report.md)
 - [视觉迁移报告](reports/v0.2.6-rc11-vision-report.md)
+- [原生 WebUI 重复验收](reports/native-workbench-2026-08-25.md)
+- [DSH 0.1.2-alpha.2 兼容性验收](reports/dsh-0.1.2-alpha.2-compat-2026-08-31.md)
 - [历史压缩档位 benchmark](docs/benchmark.md)
 
 ## 开发验证
@@ -138,10 +148,12 @@ npm ci
 npm run verify
 ```
 
-`verify` 会构建、类型检查、运行 125 项 fake-host 测试、核对 `lib/` 与数据集，再把真实 npm tarball 打包、安装并导入。测试不消耗模型 token。`prepublishOnly` 使用同一个 gate；GitHub Release 还会先检查 tag 与 `package.json` 版本一致，再走可信 npm 发布。
+`verify` 会构建并类型检查插件两端、运行 167 项测试、核对 `lib/` 与数据集，再把真实 npm tarball 打包、安装并导入。测试不消耗模型 token。`prepublishOnly` 使用同一个 gate；GitHub Release 还会先检查 tag 与 `package.json` 版本一致，再走可信 npm 发布。
 
 社区收录：[Awesome DSH Plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin) · [Awesome DeepSeek Harness](https://github.com/Dominic789654/awesome-deepseek-harness)
 
+生态发现入口：[dsh-TUI](https://github.com/ccch1mneyyy/dsh-TUI)。Bridge 仍按标准 DSH 插件安装；TUI/std 一致性适配另行跟踪。
+
 ## License
 
 MIT

package/docs/design.md

@@ -75,8 +75,10 @@ Stored tool calls are valid only under the preset composition that produced them
 
 Model and reasoning-effort changes are separate from preset migration and may still happen within one session.
 
-## Upstream coupling
+## Adapter boundary
 
-Bridge deliberately uses a narrow host contract. `/bridge --doctor` checks thirteen required gateway methods and names missing methods after a Harness upgrade. Attachment recovery and `goal.clear` are optional enhancements and do not raise that baseline.
+Bridge's preview, safety, and migration engine depends on the typed `BridgeHost` port, not DSH RPC route names. Product/version-specific mapping is isolated in the in-process `ctx.apiProxy` and HTTP adapters. The legacy `Rpc` function remains accepted through a compatibility wrapper for the 0.2.x line.
 
-The server-side slash command remains the compatibility core. A native WebUI card is feasible but would depend on prerelease client-module and slot contracts; the current decision is documented in [native-webui-feasibility.md](native-webui-feasibility.md).
+`/bridge --doctor` checks thirteen required semantic capabilities and names missing capabilities before mutation. Attachment recovery and goal clearing are optional enhancements and do not raise that baseline. Any future adapter must implement `BridgeHost` and pass the same fail-closed fixtures.
+
+The server-side slash command remains the compatibility core. The package also ships an optional WebUI client half that occupies the official per-command slot, reuses `MarkdownText` / `JsonTree`, offers lossless Text/Markdown editing, submits the reviewed summary back to the same host command, and opens the created target through the official Session runtime. The React-free `dsh-plugin-bridge/client-contract` export lets other UIs reuse the same parser and wire while unknown UIs retain the server/file fallback. No folding, attachment, goal, or fail-closed policy is reimplemented in the browser. The version boundary and fallback are documented in [native-webui-feasibility.md](native-webui-feasibility.md).

package/docs/guide.zh.md

@@ -4,7 +4,7 @@
 
 ## 1. 安装
 
-前置：已安装 dsh（`dsh --version` 能输出版本，本插件已核对 0.1.0-rc.6 / rc.7 / rc.8，并在 0.1.1-rc.2 完成真实视觉迁移），并有一个可跑的 web profile（跑过一次 `dsh web` 即会自动初始化）。
+前置：已安装 dsh（`dsh --version` 能输出版本，本插件已核对 0.1.0-rc.6 / rc.7 / rc.8，在 0.1.1-rc.2 完成真实视觉迁移，并用官方 npm `0.1.2-alpha.2` 完成 typed-controller 安装、编辑、迁移与卸载验收），并有一个可跑的 web profile（跑过一次 `dsh web` 即会自动初始化）。
 
 ```bash
 dsh plugin --profile web add dsh-plugin-bridge
@@ -13,7 +13,7 @@ dsh plugin --profile web add dsh-plugin-bridge
 需要固定 GitHub tag 或 npm 暂时不可用时：
 
 ```bash
-dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.2.10
+dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.1
 ```
 
 发生了什么（不用手动干预）：
@@ -57,7 +57,7 @@ dsh plugin --profile web remove dsh-plugin-bridge   # 重启后生效
 
 `/bridge code` 会：拉取并折叠会话历史 → 按字符预算取材（用户消息全文 + 最近几轮结论 + 最近一次 compaction 底稿）→ 起一个临时的压缩工人生成**固定五段摘要**（目标 / 当前状态 / 关键决策与约定 / 关键文件 / 下一步）→ 工人用完即归档 → 把摘要贴给你。
 
-通常 20–60 秒。**认真扫一眼**：
+卡片会立即显示经过秒数；模型耗时取决于取材与路由。本次 `0.1.1-rc.2` 三次固定输入的 worker 用时为 7.4–12.8 秒，超出 `previewTimeoutMs` 仍会被取消。**认真扫一眼**：
 
 - 目标对不对；
 - 关键约定在不在——尤其是**数字**，漂移里最主要的一类就是端口被补全成 3000/8080；
@@ -66,7 +66,17 @@ dsh plugin --profile web remove dsh-plugin-bridge   # 重启后生效
 
 ### 3.2 要改摘要
 
-预览会把摘要写进一个文件并打印路径。改那个文件，然后：
+rc.7+ 的官方 WebUI 提供三种模式：
+
+- 「预览」：渲染 Markdown；完整 JSON 文档显示为可展开的树；
+- 「文本编辑」：把目标、当前状态、关键决策、关键文件、下一步拆成普通字段，列表逐项增删，不需要输入 Markdown 符号；
+- 「Markdown」：保留完整源码和附录修改能力，适合开发者或自定义结构。
+
+长内容只在卡片正文内滚动，顶部模式切换、复制和确认按钮不会随内容滚走。非标准五段、JSON 或自定义标题不会被猜测性转换：文本模式会提示改用 Markdown，原稿保持不变。切回「预览」核对，再点「确认迁移」，校对稿会逐字成为目标的唯一事实源并自动打开目标会话。
+
+兼容官方 `conversation.chat.commandview` slot 的第三方 UI 会自动加载这张卡片。完全自研 UI 可以导入 `dsh-plugin-bridge/client-contract` 复用纯解析与编辑 contract；没有实现 slot 时仍走下面的服务端/文件回退，不影响迁移。
+
+旧客户端或 CLI 仍可走文件回退：预览会把摘要写进一个文件并打印路径。改那个文件，然后：
 
 ```
 /bridge code --go --file /tmp/dsh-bridge-xxxx/summary-....md
@@ -128,10 +138,10 @@ dsh-bridge migrate --to code --summary-file <path>
 ## 6. 常见问题
 
 **Q：`/bridge` 打了没反应 / 提示未知命令？**
-A：确认重启过 `dsh web`（插件在启动时挂载），并且用的是 `web` profile。命令注册依赖 `commands` 服务、执行依赖 `apiProxy` 服务，两者在官方 web profile 里都在；缺其一插件会挂起等待而不是半挂，日志里能看到。
+A：确认重启过 `dsh web`（插件在启动时挂载），并且用的是 `web` profile。命令注册依赖 `commands` 服务；执行时优先用 rc.2 的 `apiProxy`，alpha 则使用 typed Session / Workspace / Preset / Goal controllers。必要能力不完整时 `/bridge --doctor` 会逐项报告，不会假装可用。
 
 **Q：升级了 dsh 之后还能用吗？**
-A：先打一次 `/bridge --doctor`，它会告诉你这套 host 暴露了十三个网关方法里的哪几个、当前模式是什么、生效配置是什么。全绿就是好的。缺方法它会点名，把那行连同你的 dsh 版本发到 issues 就行。rc.6 / rc.7 / rc.8 已逐条核对；0.1.1-rc.2 的 doctor 13/13、预览、迁移、目标模型继承与原图 kickoff 均实测通过。
+A：先打一次 `/bridge --doctor`，它会告诉你这套 host 暴露了十三项能力里的哪几项、当前模式是什么、生效配置是什么。全绿就是好的。缺能力它会点名，把那行连同你的 dsh 版本发到 issues 就行。rc.6 / rc.7 / rc.8 已逐条核对；0.1.1-rc.2 的原图迁移已实测；官方 npm `0.1.2-alpha.2` 的 typed-controller 13/13、三态编辑、PTC 自动跳转、暂停目标与干净卸载也已实测。
 
 **Q：图片迁移需要怎么选模型？**
 A：图片已有助手分析时，Bridge 逐字搬这段视觉证据，不需要再次烧视觉 token。图片还没被分析时，源会话应选 `deepseek-v4-flash-vision-exp` 等视觉路由；Bridge 会在 kickoff 前把源 provider/model/reasoning effort 复制到目标，再搬原图。文本模型仍不能识图，Bridge 也不会暗中启动本地视觉模型。

package/docs/native-webui-feasibility.md

@@ -1,44 +1,72 @@
-# Native WebUI migration card: feasibility note
+# Native WebUI migration card: implementation boundary
 
-Status: **feasible, intentionally not shipped in v0.2.10**.
+Status: **implemented on main; the server command remains the compatibility fallback**.
 
-## What was verified
+## Verified extension path
 
-The official rc.8 WebUI supports third-party browser modules through a package-level `dsh.client` manifest. Its client runtime exposes a slot registry, and official plugins register occupants such as conversation views, input docks, settings items, and command renderers. This provides a real extension path; DOM patching or a forked WebUI is not required.
+The official rc.7 through `0.1.1-rc.2` WebUI and the split `0.1.2-alpha.2` client packages support third-party browser modules through a package-level `dsh.client` manifest. The renderer exposes a slot registry, and official plugins register occupants such as conversation views, input docks, settings items, and command renderers. Bridge uses that path; it does not patch the DOM or fork the WebUI.
 
-The existing Bridge package is host-side only. It injects `commands` and `apiProxy`, and that slash-command path already works in the official WebUI. A client face could call the same host RPCs and render the same five-section preview without changing migration semantics.
+The host half hard-injects only `commands`: it prefers rc.2's `apiProxy` when present and otherwise maps alpha's typed Session, Workspace, Preset, and Goal controllers into `BridgeHost`. The client half registers the `bridge` key in `conversation.chat.commandview`, parses only the host result, renders Markdown or complete JSON, offers lossless five-section Text/Markdown editing, and sends the reviewed summary back through `/bridge --go --summary64`. `recordInput: false` keeps that encoded payload out of the durable command log.
 
 ## Product shape
 
-A Bridge-native surface should express migration verification rather than copy a generic dashboard:
+The native surface expresses migration verification rather than copying a generic dashboard:
 
-1. choose a target preset;
-2. generate the five-section preview;
-3. show number, path, image, and truncation warnings beside the preview;
-4. require explicit confirmation;
-5. show the created title and session ID, with copy/open actions only when the host exposes stable navigation.
+1. the ordinary `/bridge <preset>` command chooses the target and starts the preview;
+2. the running command row immediately shows elapsed time and states that the source is untouched;
+3. the settled card renders the five-section handoff and its warnings;
+4. the user can switch among rendered Preview, non-developer Text fields, and exact Markdown source;
+5. explicit confirmation invokes the same host command and then opens the created session through `ctx.sessions.open`.
 
-The slash command remains available as the universal fallback.
+The server result always retains the created title and session ID, and the file-edit path remains available to older clients and the CLI.
 
-## Why it is not a P0 dependency
+The package also exports `dsh-plugin-bridge/client-contract`, a React-free card/parser/editor model. A custom UI that implements the official keyed command-view slot receives the packaged card; another UI can map the pure contract to its own components. A UI that implements neither path still receives the complete server text and file fallback. Bridge never patches an unknown UI DOM to simulate compatibility.
 
-- The client packages and slot contracts are still prerelease and version-coupled to the Harness WebUI.
-- Adding a browser face introduces React and multiple DSH client peer dependencies to a package that currently needs only the host contract.
-- A UI must not create a second migration implementation. The host-side preview, safety checks, and fail-closed behavior need to stay authoritative.
-- Current WebUI navigation does not provide Bridge with a stable, documented way to jump to the newly created session, so a card cannot yet promise seamless navigation.
+Custom clients do not need React or any DSH browser package to reuse the wire:
 
-## Recommended implementation boundary
+```ts
+import {
+  buildBridgeMigrationCommand,
+  parseBridgeCard,
+  parseBridgeTextProjection,
+} from 'dsh-plugin-bridge/client-contract'
 
-When the client contract stabilizes, prefer either an optional client entry in this package or a thin `dsh-plugin-bridge-ui` companion. Both should consume Bridge RPC results and never reimplement history folding, summary creation, attachment policy, or goal safety in the browser.
+const card = parseBridgeCard(commandOutcome)
+if (card.phase === 'preview') {
+  const textFields = parseBridgeTextProjection(card.summary) // undefined => keep raw Markdown
+  const confirmLine = buildBridgeMigrationCommand(
+    card.targetPreset,
+    reviewedSummary,
+    card.lang,
+    card.previewId ?? '',
+  )
+  // Dispatch confirmLine through this UI's ordinary slash-command transport.
+}
+```
 
-Prototype acceptance criteria:
+`previewId` binds confirmation to the exact preview that produced the card. Custom UIs should not cache or invent it; an absent ID means the server/client pair is too old for in-card confirmation and should use the printed file workflow.
 
-- loads and disposes through the official client-module lifecycle;
-- works on both wide and narrow official WebUI layouts;
-- exposes the exact same preview file and warnings as `/bridge`;
-- creates no target before confirmation;
-- proves cleanup after plugin removal and restart;
-- keeps `/bridge --doctor` and the host command usable when the client face fails;
-- pins and tests every supported DSH client-package version.
+## Compatibility boundary
 
-Until those criteria can be maintained across releases, the official slash command is the more stable and lower-cost product surface.
+- Client packages and slot contracts remain prerelease and version-coupled. They are optional peers; rc.6 and clients that cannot load the browser half retain the complete server command result.
+- rc.2 guards both the parent `remote` face and `remote.commands`, and its generated command wire requires an explicit image array. Bundle tests pin both details.
+- The browser does not own a second migration engine. History folding, summary generation, attachment policy, target creation, goal pause, and rollback remain host-authoritative.
+- Edited summaries are bounded to 24,000 characters and base64url-encoded for one command invocation. Malformed or oversized payloads fail closed before target creation; emptiness checks do not trim the transmitted Markdown.
+- A WebUI payload is accepted only while the exact preview ID for the matching source session and target preset is pending and unexpired. The preview is consumed before migration; retrying the same completed payload returns the first target result instead of creating another session, even if a newer preview has since been generated.
+- Once a target session exists, an unconfirmed kickoff is returned as that same navigable target with a warning and cached result. Bridge does not restore the preview and create a second target when prompt delivery is ambiguous.
+- The client contract shapes for rc.7, rc.8, `0.1.1-rc.1`, `0.1.1-rc.2`, and `0.1.2-alpha.2` were compared. Both rc.2 and alpha.2 have installed official-WebUI evidence; alpha.2 uses the split `ui-chat`, Session Controller, renderer, and Session UI declarations.
+
+## Acceptance evidence
+
+The 2026-08-25 installed-WebUI gate covered:
+
+- official client-module load and disposal;
+- wide and narrow layout behavior;
+- server `/bridge --doctor` fallback and native rendering;
+- immediate progress, rendered Markdown, editable text, and JSON tree rendering;
+- no target before confirmation;
+- reviewed-payload migration, paused goal, and automatic target navigation.
+
+Three fixed real-model runs preserved five facts in both preview and target, with worker times from 7.4 to 12.8 seconds. See the [native workbench report](../reports/native-workbench-2026-08-25.md). This is release evidence, not a statistical guarantee.
+
+The 2026-08-31 npm-installed alpha.2 gate additionally covered typed-controller doctor 13/13, split-client compilation, localized primitive labels, Text-to-Markdown review, PTC auto-open, paused goal, and clean removal. See the [alpha.2 compatibility report](../reports/dsh-0.1.2-alpha.2-compat-2026-08-31.md).

package/lib/api-rpc.d.ts

@@ -7,9 +7,10 @@
  * 迁移——不需要端口、不需要 `DSH_WEB_URL`、不需要 bash、也不依赖模型愿不愿意
  * 帮忙调用。
  *
- * `migrate.ts` 只认注入进来的 `Rpc`，于是同一套编排在三个地方复用：
- * `/bridge` 命令（这里）、CLI（走 HTTP）、评测 harness。
+ * 本文件把这个产品表面收敛到 `BridgeHost`；迁移核心不再认识 RPC 路由名。
+ * `/bridge` 命令、CLI（走 HTTP）和评测 harness 仍复用同一套编排。
  */
+import { type BridgeHost } from './host.ts';
 import { type Rpc } from './rpc.ts';
 /** 一个 unary 网关方法：`(request, signal) => 信封`。 */
 type UnaryMethod = (request: {
@@ -61,4 +62,6 @@ export declare function probeApiProxy(apiProxy: Partial<ApiProxyLike> | undefine
  * @param signal - 派发方的取消信号（命令处理器拿到的那个）。
  */
 export declare function createApiProxyRpc(apiProxy: ApiProxyLike, signal?: AbortSignal): Rpc;
+/** 当前 DSH 进程内网关的 BridgeHost adapter。 */
+export declare function createApiProxyHost(apiProxy: ApiProxyLike, signal?: AbortSignal): BridgeHost;
 export {};

package/lib/api-rpc.js

@@ -7,9 +7,10 @@
  * 迁移——不需要端口、不需要 `DSH_WEB_URL`、不需要 bash、也不依赖模型愿不愿意
  * 帮忙调用。
  *
- * `migrate.ts` 只认注入进来的 `Rpc`，于是同一套编排在三个地方复用：
- * `/bridge` 命令（这里）、CLI（走 HTTP）、评测 harness。
+ * 本文件把这个产品表面收敛到 `BridgeHost`；迁移核心不再认识 RPC 路由名。
+ * `/bridge` 命令、CLI（走 HTTP）和评测 harness 仍复用同一套编排。
  */
+import { createBridgeHostFromRpc } from './host.js';
 import { RpcError } from './rpc.js';
 /** RPC 方法名 → `ctx.apiProxy` 上的位置。 */
 const ROUTES = {
@@ -74,3 +75,10 @@ export function createApiProxyRpc(apiProxy, signal) {
         return result.value;
     };
 }
+/** 当前 DSH 进程内网关的 BridgeHost adapter。 */
+export function createApiProxyHost(apiProxy, signal) {
+    return createBridgeHostFromRpc(createApiProxyRpc(apiProxy, signal), {
+        id: 'dsh-api-proxy',
+        transport: 'in-process',
+    });
+}

package/lib/cli.js

@@ -19,6 +19,7 @@ import { tmpdir } from 'node:os';
 import { join } from 'node:path';
 import { SOURCE_CHAR_BUDGET, SUMMARY_CHAR_BUDGET, estimateSummaryTokens } from './compression.js';
 import { executeMigration, findSession, listPresets, migratedTitle, previewMigration, resolveWorkerModel, titleOf, } from './migrate.js';
+import { createBridgeHostFromRpc } from './host.js';
 import { RpcError, createRpc, resolveApiBase } from './rpc.js';
 const HELP = `dsh-bridge · 跨 preset 会话迁移
 
@@ -151,6 +152,7 @@ async function main(argv) {
     const quiet = bool(args, 'quiet') || json;
     const api = resolveApiBase(str(args, 'api'));
     const rpc = createRpc({ api, prefix: 'bridge-cli' });
+    const host = createBridgeHostFromRpc(rpc, { id: 'dsh-http-api', transport: 'http' });
     const progress = (message) => {
         if (!quiet)
             process.stderr.write(`… ${message}\n`);
@@ -162,7 +164,7 @@ async function main(argv) {
         case 'doctor': {
             const report = { api, sessionIdFromEnv: process.env.DSH_SESSION_ID ?? null };
             try {
-                const presets = await listPresets(rpc);
+                const presets = await listPresets(host);
                 report.gateway = 'ok';
                 report.presets = presets.map((p) => p.id);
             }
@@ -171,7 +173,7 @@ async function main(argv) {
             }
             const sessionId = str(args, 'session') ?? process.env.DSH_SESSION_ID;
             if (sessionId) {
-                const row = await findSession(rpc, sessionId).catch(() => undefined);
+                const row = await findSession(host, sessionId).catch(() => undefined);
                 report.session = row ? { sessionId: row.sessionId, agentPreset: row.agentPreset, cwd: row.cwd } : 'not-found';
             }
             out(report, () => {
@@ -187,8 +189,8 @@ async function main(argv) {
         }
         case 'presets': {
             const sessionId = str(args, 'session') ?? process.env.DSH_SESSION_ID;
-            const current = sessionId ? (await findSession(rpc, sessionId).catch(() => undefined))?.agentPreset : undefined;
-            const presets = await listPresets(rpc);
+            const current = sessionId ? (await findSession(host, sessionId).catch(() => undefined))?.agentPreset : undefined;
+            const presets = await listPresets(host);
             const rows = presets.map((p) => ({ ...p, current: p.id === current }));
             out({ current, presets: rows }, () => {
                 const lines = rows.map((p) => {
@@ -204,7 +206,7 @@ async function main(argv) {
         case 'preview': {
             const sessionId = resolveSessionId(args);
             const to = str(args, 'to');
-            const result = await previewMigration(rpc, {
+            const result = await previewMigration(host, {
                 sessionId,
                 tier: tierOf(args),
                 provider: str(args, 'provider'),
@@ -276,8 +278,8 @@ async function main(argv) {
             catch (error) {
                 throw new UsageError(`读不到摘要文件 ${file}：${error instanceof Error ? error.message : String(error)}`);
             }
-            const source = await findSession(rpc, sessionId).catch(() => undefined);
-            const result = await executeMigration(rpc, {
+            const source = await findSession(host, sessionId).catch(() => undefined);
+            const result = await executeMigration(host, {
                 sessionId,
                 sourceSession: source,
                 to,
@@ -311,7 +313,7 @@ async function main(argv) {
         case 'run': {
             const sessionId = resolveSessionId(args);
             const to = requireTarget(args);
-            const preview = await previewMigration(rpc, {
+            const preview = await previewMigration(host, {
                 sessionId,
                 tier: tierOf(args),
                 provider: str(args, 'provider'),
@@ -323,7 +325,7 @@ async function main(argv) {
                 ...(num(args, 'worker-timeout') === undefined ? {} : { workerTimeoutMs: num(args, 'worker-timeout') }),
                 onProgress: progress,
             });
-            const result = await executeMigration(rpc, {
+            const result = await executeMigration(host, {
                 sessionId,
                 sourceSession: preview.sourceSession,
                 to,
@@ -342,7 +344,7 @@ async function main(argv) {
         case 'worker-model': {
             // 诊断用：只回答「档位会挑到哪个模型」，不建任何会话。
             const sessionId = resolveSessionId(args);
-            const route = await resolveWorkerModel(rpc, sessionId, tierOf(args), {
+            const route = await resolveWorkerModel(host, sessionId, tierOf(args), {
                 provider: str(args, 'provider'),
                 model: str(args, 'model'),
             });

package/lib/client-contract.d.ts

@@ -0,0 +1,87 @@
+/** Pure wire-to-view helpers shared by the native WebUI card and Node tests. */
+export declare const MAX_EDITED_SUMMARY_CHARS = 24000;
+export type BridgeOutcome = {
+    kind: 'success' | 'error';
+    text?: string;
+} | null;
+export type BridgeCard = {
+    phase: 'running';
+} | {
+    phase: 'preview';
+    lang: 'zh' | 'en';
+    sourcePreset: string;
+    targetPreset: string;
+    previewId?: string;
+    summary: string;
+    summaryFile?: string;
+    stats: string;
+    warnings: string[];
+} | {
+    phase: 'migrated';
+    lang: 'zh' | 'en';
+    targetPreset: string;
+    title: string;
+    sessionId: string;
+    details: string[];
+    warnings: string[];
+} | {
+    phase: 'error';
+    text: string;
+} | {
+    phase: 'message';
+    text: string;
+    lang: 'zh' | 'en';
+};
+export type BridgeTextSectionKey = 'goal' | 'currentState' | 'keyDecisions' | 'keyFiles' | 'nextStep';
+export interface BridgeTextSection {
+    key: BridgeTextSectionKey;
+    label: string;
+    kind: 'text' | 'list';
+    /** Plain-text editor value. List markers are intentionally omitted. */
+    text: string;
+    /** Exact source span replaced when this field is edited. */
+    bodyStart: number;
+    bodyEnd: number;
+    items?: BridgeTextListItem[];
+    listStyle?: 'bullet' | 'plain';
+    textStyle?: 'plain' | 'bullets';
+}
+export interface BridgeTextListItem {
+    text: string;
+    contentStart: number;
+    contentEnd: number;
+    itemStart: number;
+    itemEnd: number;
+    /** Original indentation for wrapped lines, kept when that item is edited. */
+    continuationPrefixes?: string[];
+}
+export interface BridgeTextProjection {
+    lang: 'zh' | 'en';
+    /** The untouched Markdown document used to enter text mode. */
+    markdown: string;
+    lineEnding: '\n' | '\r\n';
+    sections: BridgeTextSection[];
+    /** Known appendices are visible but read-only in plain-text mode. */
+    opaqueSuffix: string;
+}
+/**
+ * Project only Bridge's exact bilingual five-section schema into plain fields.
+ * Unknown structure fails closed; known visual appendices remain opaque Markdown.
+ */
+export declare function parseBridgeTextProjection(markdown: string): BridgeTextProjection | undefined;
+/** Replace one editable body while preserving every byte outside that section. */
+export declare function replaceBridgeTextSection(projection: BridgeTextProjection, key: BridgeTextSectionKey, plainText: string): string;
+/** Replace one list item without rewriting siblings and while retaining wrapped-line indentation. */
+export declare function replaceBridgeTextListItem(projection: BridgeTextProjection, key: BridgeTextSectionKey, index: number, plainText: string): string;
+/** Remove exactly one original list-item span. */
+export declare function removeBridgeTextListItem(projection: BridgeTextProjection, key: BridgeTextSectionKey, index: number): string;
+/** Append one item using the section's existing bullet/plain convention. */
+export declare function appendBridgeTextListItem(projection: BridgeTextProjection, key: BridgeTextSectionKey, plainText: string): string;
+/** Map the official WebUI document language onto Bridge's supported UI copy. */
+export declare function uiLanguageOf(documentLang: string | undefined): 'zh' | 'en';
+/** Convert one durable `/bridge` outcome into the native card's view model. */
+export declare function parseBridgeCard(outcome: BridgeOutcome): BridgeCard;
+/** Return a value only when the complete editor document is valid JSON. */
+export declare function parseJsonDocument(text: string): object | unknown[] | undefined;
+/** Build the hidden-input-safe command used by the native editor confirmation. */
+export declare function buildBridgeMigrationCommand(targetPreset: string, summary: string, lang: 'zh' | 'en', previewId: string): string;