dsh-plugin-bridge 0.3.2 → 0.3.4

package/README.md

@@ -9,7 +9,7 @@
 [![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.2-alpha.5](https://img.shields.io/badge/dsh-rc.6%20%E2%86%92%200.1.2--alpha.5-4c8dff)](https://github.com/deepseek-ai/deepseek-harness)
+[![dsh 0.1.5-alpha.1](https://img.shields.io/badge/dsh-0.1.5--alpha.1-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)
 
@@ -35,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.3.2
+dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.4
 ```
 
 Then type in the official WebUI:
@@ -118,6 +118,10 @@ The five sections are Goal, Current state, Key decisions and conventions, Key fi
 | 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 / alpha.3 / alpha.5 | Yes | Yes | Official DSH npm hosts: typed controllers 13/13 and PTC auto-open; the alpha.5 gate installed the branch tarball, retained alpha.3 titles, edited ordered lists, fell back from unresolved image to text, and removed cleanly |
+| 0.1.2-rc.1 → 0.1.3-alpha.2 | Yes (Bridge 0.3.3+) | Yes (Bridge 0.3.3+) | Real npm-host upgrade, preserved v2 history/title, exact edited payload, PTC paused goal, image fallback and clean removal; see [acceptance report](reports/dsh-0.1.3-alpha.2-compat-2026-09-08.md) |
+| 0.1.5-alpha.1 | Yes (Bridge 0.3.4+) | Yes (Bridge 0.3.4+) | Official npm host with session format V3: tarball install, served native-card bundle, doctor 13/13 and preset listing on a V3 session; SDK type diff and V3 fold fixtures. Model-backed preview, migration and image fallback were not re-run; see [smoke report](reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md) |
+
+Use Bridge 0.3.4 or later for DSH 0.1.5-alpha.1: DSH published no 0.1.4, and a caret prerelease range such as `^0.1.3-alpha.2` never matches the next prerelease minor, so 0.3.4 adds `^0.1.5-alpha.1` and builds against that SDK with byte-identical `lib/` output. Session format V3 records the system prompt as a `system/message` surface node; Bridge folds only user, assistant and tool events, so prompt text never enters a handoff. Use Bridge 0.3.3 or later for DSH 0.1.3-alpha.2; Bridge 0.3.2 does not include those compatibility changes. The typed adapter reads the default 240-message history window with one fresh `inspect` call instead of four; it does not cache running state. `doctor` checks method availability, not end-to-end compatibility.
 
 CI covers Node.js 22 and 24. Run `/bridge --doctor` after every Harness upgrade; it names missing required gateway methods instead of failing vaguely.
 
@@ -148,7 +152,7 @@ npm ci
 npm run verify
 ```
 
-`verify` builds and type-checks both plugin halves, runs 170 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 176 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)
 

package/README.zh.md

@@ -9,7 +9,7 @@
 [![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.2-alpha.5](https://img.shields.io/badge/dsh-rc.6%20%E2%86%92%200.1.2--alpha.5-4c8dff)](https://github.com/deepseek-ai/deepseek-harness)
+[![dsh 0.1.5-alpha.1](https://img.shields.io/badge/dsh-0.1.5--alpha.1-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)
 
@@ -35,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.3.2
+dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.4
 ```
 
 然后在官方 WebUI 输入：
@@ -118,6 +118,10 @@ token 百分比会随 preset、回复长度和缓存状态大幅波动；worker
 | 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 / alpha.3 / alpha.5 | 支持 | 支持 | 官方 DSH npm 宿主：typed controllers 13/13 与 PTC 自动跳转；alpha.5 门禁安装分支 tarball，保留 alpha.3 标题，编号列表可编辑，未解析图片降级为文本，卸载干净 |
+| 0.1.2-rc.1 → 0.1.3-alpha.2 | 支持（Bridge 0.3.3+） | 支持（Bridge 0.3.3+） | 官方 npm 宿主真实升级、v2 历史与标题保留、编辑内容逐字交接、PTC goal 暂停、图片回退及卸载；见[验收记录](reports/dsh-0.1.3-alpha.2-compat-2026-09-08.md) |
+| 0.1.5-alpha.1 | 支持（Bridge 0.3.4+） | 支持（Bridge 0.3.4+） | 官方 npm 宿主（会话格式 V3）：tarball 安装、原生卡片 bundle 已下发、V3 会话上 doctor 13/13 与预设列表；SDK 类型 diff 与 V3 折叠 fixture。未重跑需要模型的预览、迁移与图片回退；见[smoke 记录](reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md) |
+
+DSH 0.1.5-alpha.1 请使用 Bridge 0.3.4 或更高版本：DSH 没有发布 0.1.4，而 `^0.1.3-alpha.2` 这类 caret 预发布范围不会匹配下一个预发布 minor，所以 0.3.4 追加 `^0.1.5-alpha.1` 并基于该 SDK 构建，`lib/` 产物逐字节相同。会话格式 V3 把系统提示词记成 `system/message` surface node；Bridge 只折叠用户、助手和工具事件，提示词文本不会进入交接。DSH 0.1.3-alpha.2 请使用 Bridge 0.3.3 或更高版本；Bridge 0.3.2 不包含那些兼容改动。typed adapter 只调用一次 `inspect`，就能读取默认 240 条消息的历史窗口，原来需要四次；不会缓存运行状态。`doctor` 检查方法是否存在，不能代替完整迁移验收。
 
 CI 覆盖 Node.js 22/24。每次升级 Harness 后先跑 `/bridge --doctor`；缺哪个必要网关方法会被直接点名。
 
@@ -148,7 +152,7 @@ npm ci
 npm run verify
 ```
 
-`verify` 会构建并类型检查插件两端、运行 170 项测试、核对 `lib/` 与数据集，再把真实 npm tarball 打包、安装并导入。测试不消耗模型 token。`prepublishOnly` 使用同一个 gate；GitHub Release 还会先检查 tag 与 `package.json` 版本一致，再走可信 npm 发布。
+`verify` 会构建并类型检查插件两端、运行 176 项测试、核对 `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)
 

package/docs/design.md

@@ -81,4 +81,6 @@ Bridge's preview, safety, and migration engine depends on the typed `BridgeHost`
 
 `/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.
 
+Hosts that already materialize a full snapshot may optionally implement `sessions.historyWindow`. `foldedHistory` requests its complete message budget once through this method; other adapters keep the existing paged `history` path. The typed DSH adapter takes one fresh `inspect` snapshot per window, returns only the bounded tail, and retains no snapshot between calls. Worker polling continues through fresh `history` reads. This reduces repeated Bridge-side reads and allocations; it does not promise bounded disk I/O inside the host. Method probes check availability only; v2 log replay and actual migration are covered by the [installed-host acceptance](../reports/dsh-0.1.3-alpha.2-compat-2026-09-08.md). DSH 0.1.5 session format V3 adds `system/message` surface nodes and positional replacements; the fold and the message budget ignore both, and the [0.1.5-alpha.1 smoke](../reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md) records the installed-host probe without a model-backed migration.
+
 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 完成真实视觉迁移，并用官方 npm `0.1.2-alpha.2` 完成 typed-controller 安装、编辑、迁移与卸载验收），并有一个可跑的 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 安装、编辑、迁移与卸载验收，官方 npm `0.1.5-alpha.1` 完成安装、doctor 13/13 与预设列表 smoke），并有一个可跑的 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.3.2
+dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.4
 ```
 
 发生了什么（不用手动干预）：
@@ -141,7 +141,7 @@ dsh-bridge migrate --to code --summary-file <path>
 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 的原图迁移已实测；官方 npm `0.1.2-alpha.2` 的 typed-controller 13/13、三态编辑、PTC 自动跳转、暂停目标与干净卸载也已实测。
+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 自动跳转、暂停目标与干净卸载也已实测；官方 npm `0.1.5-alpha.1`（会话格式 V3）已实测安装、doctor 13/13 与预设列表，需要模型的迁移验收尚未重跑。
 
 **Q：图片迁移需要怎么选模型？**
 A：图片已有助手分析时，Bridge 逐字搬这段视觉证据，不需要再次烧视觉 token。图片还没被分析时，源会话应选 `deepseek-v4-flash-vision-exp` 等视觉路由；Bridge 会在 kickoff 前把源 provider/model/reasoning effort 复制到目标，再搬原图。文本模型仍不能识图，Bridge 也不会暗中启动本地视觉模型。

package/lib/dsh-alpha-host.d.ts

@@ -58,7 +58,7 @@ type ContextLike = AlphaServices & {
 };
 /** Probe the real alpha services instead of the adapter's always-present closures. */
 export declare function probeDshAlphaHost(input: ContextLike): BridgeHostProbe[];
-/** Create the semantic BridgeHost over DSH v0.1.2 typed Host controllers. */
+/** Create the semantic BridgeHost over DSH typed Host controllers. */
 export declare function createDshAlphaHost(input: ContextLike, signal?: AbortSignal): BridgeHost;
 /** Prefer the stable rc.2 path when present; otherwise use alpha controllers. */
 export declare function resolveDshHost(input: ContextLike, signal?: AbortSignal): BridgeHost;

package/lib/dsh-alpha-host.js

@@ -1,10 +1,10 @@
 /**
- * DSH v0.1.2 alpha typed-controller adapter.
+ * DSH v0.1.2/v0.1.3 typed-controller adapter.
  *
  * The alpha removed the legacy ApiProxy service.  Keep that product change at
  * this boundary: migration code continues to consume BridgeHost, while this
- * adapter talks to the Host controllers structurally so the package can still
- * be built against the current rc.2 SDK.
+ * adapter talks to the Host controllers structurally while the browser half
+ * builds against the current client SDK.
  */
 import { randomUUID } from 'node:crypto';
 import { createApiProxyHost, probeApiProxy } from './api-rpc.js';
@@ -117,11 +117,23 @@ function currentModel(row) {
     };
 }
 function paginateHistory(events, beforeSeq, maxMessages) {
-    const visible = beforeSeq === undefined ? [...events] : events.filter(event => (event.seq ?? -1) < beforeSeq);
+    // Snapshot events are ordered. Locate the cursor without copying/scanning
+    // the entire prefix on every page; only allocate the returned window.
+    let end = events.length;
+    if (beforeSeq !== undefined) {
+        let low = 0;
+        while (low < end) {
+            const middle = Math.floor((low + end) / 2);
+            if ((events[middle]?.seq ?? -1) < beforeSeq)
+                low = middle + 1;
+            else
+                end = middle;
+        }
+    }
     let count = 0;
     let cut = 0;
-    for (let index = visible.length - 1; index >= 0; index -= 1) {
-        const type = visible[index]?.type;
+    for (let index = end - 1; index >= 0; index -= 1) {
+        const type = events[index]?.type;
         if (type !== 'user/message' && type !== 'assistant/message')
             continue;
         count += 1;
@@ -131,7 +143,7 @@ function paginateHistory(events, beforeSeq, maxMessages) {
         }
     }
     return {
-        events: visible.slice(cut).map(event => ({ event })),
+        events: events.slice(cut, end).map(event => ({ event })),
         hasMore: cut > 0,
     };
 }
@@ -151,13 +163,13 @@ export function probeDshAlphaHost(input) {
         available: typeof ALPHA_METHODS[method]?.(services) === 'function',
     }));
 }
-/** Create the semantic BridgeHost over DSH v0.1.2 typed Host controllers. */
+/** Create the semantic BridgeHost over DSH typed Host controllers. */
 export function createDshAlphaHost(input, signal) {
     const services = servicesOf(input);
     const controller = services.sessionController;
     const abort = signal ?? new AbortController().signal;
     const host = {
-        descriptor: Object.freeze({ id: 'dsh-typed-controllers', version: '0.1.2-alpha', transport: 'in-process' }),
+        descriptor: Object.freeze({ id: 'dsh-typed-controllers', transport: 'in-process' }),
         sessions: Object.freeze({
             list: async (request = {}) => {
                 const list = required('session.list', controller?.list);
@@ -173,6 +185,11 @@ export function createDshAlphaHost(input, signal) {
                 const value = await invoke('session.history', () => inspect.call(controller, request.sessionId, abort));
                 return paginateHistory(value.events, request.beforeSeq, request.maxMessages ?? 60);
             },
+            historyWindow: async (request) => {
+                const inspect = required('session.history', controller?.inspect);
+                const value = await invoke('session.history', () => inspect.call(controller, request.sessionId, abort));
+                return paginateHistory(value.events, undefined, request.maxMessages);
+            },
             models: async ({ sessionId }) => {
                 const list = required('session.list', controller?.list);
                 const catalog = required('session.models', controller?.modelCatalog);

package/lib/host.d.ts

@@ -85,6 +85,20 @@ export interface BridgeHost {
             }[];
             hasMore?: boolean;
         }>;
+        /** Optional single-read window for hosts that already materialize a complete
+         * snapshot. Each invocation reads fresh state; readers must not cache it
+         * across commands or worker polls. The budget counts user/assistant message events. */
+        historyWindow?(input: {
+            sessionId: string;
+            maxMessages: number;
+        }, options?: {
+            timeoutMs?: number;
+        }): Promise<{
+            events?: {
+                event: SessionEvent;
+            }[];
+            hasMore?: boolean;
+        }>;
         models(input: {
             sessionId: string;
         }): Promise<SessionModels>;

package/lib/migrate.js

@@ -151,6 +151,12 @@ export async function foldedHistory(input, sessionId, options = {}) {
     const host = asBridgeHost(input);
     const pageMessages = options.pageMessages ?? HISTORY_PAGE_MESSAGES;
     const maxPages = options.maxPages ?? HISTORY_MAX_PAGES;
+    if (maxPages <= 0)
+        return [];
+    if (host.sessions.historyWindow) {
+        const window = await host.sessions.historyWindow({ sessionId, maxMessages: pageMessages * maxPages }, { timeoutMs: 60_000 });
+        return foldSessionEvents((window.events ?? []).map(entry => entry.event));
+    }
     let events = [];
     let beforeSeq;
     for (let page = 0; page < maxPages; page += 1) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-bridge",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "Previewable cross-preset session migration for DeepSeek Harness with bounded, fixed-schema handoffs",
   "type": "module",
   "main": "lib/index.js",
@@ -14,6 +14,8 @@
     "reports/native-workbench-2026-08-25.md",
     "reports/native-workbench-2026-08-25.raw.json",
     "reports/dsh-0.1.2-alpha.2-compat-2026-08-31.md",
+    "reports/dsh-0.1.3-alpha.2-compat-2026-09-08.md",
+    "reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md",
     "cordis.patch.yml",
     "README.md",
     "README.zh.md"
@@ -60,11 +62,11 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-api-remotes": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1",
-    "@deepseek-ai/dsh-client-ui-chat": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1",
-    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1",
-    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1",
+    "@deepseek-ai/dsh-api-remotes": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1 || ^0.1.3-alpha.2 || ^0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-chat": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1 || ^0.1.3-alpha.2 || ^0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1 || ^0.1.3-alpha.2 || ^0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1 || ^0.1.3-alpha.2 || ^0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.7 || ^0.1.1-rc.1 || ^0.1.2-alpha.1 || ^0.1.3-alpha.2 || ^0.1.5-alpha.1",
     "react": "^18.2.0"
   },
   "peerDependenciesMeta": {
@@ -81,14 +83,14 @@
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "4.0.2",
-    "@deepseek-ai/dsh-api-remotes": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-api-session-controller": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-client-ui-chat": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-client-ui-session": "^0.1.2-alpha.2",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-api-remotes": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-api-session-controller": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-chat": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-primitives": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-renderer": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-session": "0.1.5-alpha.1",
+    "@deepseek-ai/dsh-client-ui-slots": "0.1.5-alpha.1",
     "@types/node": "^26.2.0",
     "@types/react": "~18.3.1",
     "react": "^18.3.1",

package/reports/dsh-0.1.3-alpha.2-compat-2026-09-08.md

@@ -0,0 +1,65 @@
+# DSH 0.1.3-alpha.2 compatibility and history-window acceptance
+
+Date: 2026-09-08 (Asia/Shanghai). **Bridge 0.3.3 release acceptance**. The runtime tests used the implementation candidate based on `d2b9be2`, before its package version was bumped from 0.3.2 to 0.3.3. These results do not apply to the unchanged registry 0.3.2 package.
+
+## Environments and artifact
+
+- Official npm DSH `0.1.2-rc.1`: 214 DSH packages at that version; Node 24.19.0.
+- Official npm DSH `0.1.3-alpha.2`: 223 DSH packages at that version; Node 22.23.1.
+- Candidate built from this branch and installed with the official `dsh plugin --profile web add <tarball>` command. The same isolated profile was then opened by alpha.2.
+- `pnpm peers check` reported no peer dependency issues after upgrade.
+- The profile, workspace, credentials copy, browser and host test driver were isolated. Only synthetic Session content was submitted to the configured DeepSeek endpoint. Test drivers and browser recordings are not part of the plugin package.
+- Alpha.2's `fs-ext` was built during installation under Node 22. Attempting to launch that installation under Node 24 produced `ERR_DLOPEN_FAILED`; using the matching Node 22 runtime resolved the environment error. This run does not claim an installed alpha.2/Node 24 test.
+
+## Upgrade and real migration
+
+| Check | Result |
+|---|---|
+| Old-host installed command | Doctor 13/13; actual preview and migration via `commands.execute` succeeded |
+| Old-host facts | Project BRIDGE-A13-7813, PostgreSQL, port 7813, planned-but-not-created `src/migration.ts`, and MongoDB prohibition preserved |
+| Old-host target | PTC, paused goal, zero autonomous goal rounds |
+| Same-profile upgrade | Original title retained; source header becomes format v2 |
+| Old log artifacts | All four pre-upgrade JSONL/Zstandard artifacts remain byte-identical by SHA-256 |
+| Source content | Folded user and assistant text exactly matches the pre-upgrade snapshot; no test file was created |
+| Alpha.2 command | Doctor 13/13; preview requested through the installed WebUI |
+| Native editing | Text/Markdown round trip preserves numbered-list continuation; edited Next step reaches target exactly |
+| Default confirmation | Exactly one new target; automatically opened in PTC, goal paused, zero goal rounds |
+| Target response | Restates the critical facts and waits; does not execute tools or create files |
+| Restart | Edited objective and paused state remain intact; old log hashes still match |
+
+The reviewed native payload had SHA-256 `cba24d3dc1dd707de9f7cfb1b111ac95311838f166216825115c11c86e987f5e` and included long synthetic text to exercise scrolling. Both the submitted content and target goal retained those exact bytes.
+
+## UI and image fallback
+
+- At 1280, 768 and 375 pixels, the document had no horizontal overflow; the preview had its own scrollable body and scrolling it did not move the confirmation controls.
+- A separate 375-pixel check scrolled the confirmation button into view and verified that its center hit the actual button, rather than the fixed composer. Native confirmation then succeeded at the desktop viewport.
+- No page errors were observed during the connected preview/edit/confirm runs. No pixel-baseline comparison or full accessibility audit was performed.
+- A real image was admitted through the official vision route, then cancelled before any assistant message; the source contained one durable image and zero assistant analyses. Its selected model was changed to text-only `deepseek-v4-flash` before migration.
+- Target prompt admission rejected the image with `session/attachment-invalid` and `Model "deepseek-v4-flash" does not support image input`. Bridge returned a visible warning and completed a text-only kickoff containing the unresolved-image warning. The target had zero image blocks and a paused goal.
+- Raw-image delivery to a vision-capable target was not repeated in this run.
+
+## History cost comparison
+
+The fixture contains 6,000 synthetic user-message events, created through the old host's Session API and upgraded to v2. The default returned window remains 240 messages. The installed alpha.2 `SessionController.inspect` was instrumented to count reads; results below compare the original `main` implementation against the candidate using the same real controller. The session had no attached Agent during the cold-session query comparison. Five sequential samples were taken per implementation, original first; host/OS caches may affect timing. Heap delta is before/after allocation during a read, **not peak RSS or retained memory**.
+
+| Metric | Original 0.3.2 | Candidate |
+|---|---:|---:|
+| Full `inspect` calls per source window | 4 | 1 |
+| Returned message count | 240 | 240 |
+| Median read + fold time | 12.93 ms | 6.70 ms |
+| Median observed heap delta | 5,579,552 B | 5,165,760 B |
+| Folded content equality | Identical | Identical |
+
+Original times (ms): 58.612, 12.926, 12.533, 12.958, 11.980. Candidate: 7.643, 6.689, 6.703, 7.015, 6.665. The initial original sample also pays first-read setup. An earlier attached-session comparison showed little wall-clock change (about 4–5 ms in both paths). The reliable improvement is avoiding repeated full reads; this is not an end-to-end model latency or universal speedup claim.
+
+The adapter retains no running-state or cross-request history cache. Regression tests additionally cover new events after a window read, current worker turn completion, errors/cancellation, and equality with the paged path across tool and compaction records.
+
+## Removal and verification
+
+- Official `dsh plugin --profile web remove dsh-plugin-bridge`, followed by a host restart, removed the dependency, bundle registration and profile package link.
+- The old Session remained readable through the generic command renderer. The browser had zero Bridge cards, zero Bridge style elements, zero Bridge resource requests, and zero observed page errors.
+- Executing `/bridge --doctor` returned no command execution; an independently registered companion command still succeeded.
+- Host restart successfully reopened the same persisted sessions, exercising normal session-lock release. Crash recovery and multi-process lock contention were not separately tested.
+- `npm ci` followed by `npm run verify` passed under Node 22.23.1: 174 tests, build/typecheck, generated artifact checks, datasets and package import smoke. The Node 24.19.0 test run also passed all 174 tests.
+- Summary model calls, UI fixtures and inspection endpoints were restricted to the isolated acceptance environment. No user Session database was edited or deleted.
+- After acceptance, the temporary credential copy, both installed runtimes, synthetic profile, browser process and three test-created summary directories were removed. Sanitized measurement results, check logs and screenshots were retained outside the repository.

package/reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md

@@ -0,0 +1,49 @@
+# DSH 0.1.5-alpha.1 compatibility smoke
+
+Date: 2026-09-09 (Asia/Shanghai). **Bridge 0.3.4 release smoke**. The runtime checks used the candidate built from the `compat/dsh-0.1.5-alpha.1` branch on top of `f2d0fba`, before its package version was bumped from 0.3.3 to 0.3.4. These results do not apply to the registry 0.3.3 package, whose peer ranges stop at `^0.1.3-alpha.2`.
+
+This is a smaller gate than the [0.1.3-alpha.2 acceptance](dsh-0.1.3-alpha.2-compat-2026-09-08.md): it proves install, load, host probing and the command path on the new host, and it audits the SDK contract by type diff. It does not repeat the model-backed preview, edit, migration or image-fallback runs; see [Not covered](#not-covered).
+
+## Upstream change
+
+DSH went from `dsh-v0.1.3-alpha.2` (2026-09-07) to `dsh-v0.1.5-alpha.1` (2026-09-08, 563 commits); no 0.1.4 was published to npm. Relevant items from the release notes and from diffing the published `.d.ts` files of every package Bridge pins (`dsh-api-remotes`, `dsh-api-session-controller`, `dsh-client-ui-chat/-conversation/-primitives/-renderer/-session/-slots`) plus the Host packages it calls structurally (`dsh-goal`, `dsh-session`, `dsh-session-persistence`, `dsh-commands`, `dsh-agent`, `dsh-agent-presets`, `dsh-workspace`, `dsh-api-workspace-controller`):
+
+| Change | Effect on Bridge |
+|---|---|
+| Session format V3: `SESSION_FORMAT_VERSION = 3`, new `system/message` surface event, `SurfaceOp.replace` fields renamed to `startSeq`/`endSeq`, `user/message` payload unchanged (`UserMessage` with `content`) | None at runtime. The fold handles user, assistant, chunk, tool and turn events only; `system/message` and replacement copies are skipped, and the message budget counts user/assistant events only. New fixtures lock this in. |
+| `ctx.agent` removed; `AgentSetup` receives the Agent explicitly; `Inbox` is now type-only | None. Bridge never read `ctx.agent` or `Inbox`; goals already receive the Agent from `sessionController.resolveAgent`. |
+| `GoalService.pause/resume/clear(agent, ref)`, `remoteExportCreate(agent, request)`, new `goal/activation-changed` event, model may no longer resume a user-paused goal | Signatures unchanged. The paused migration target now also shows a resume control in the official UI. |
+| `SessionController.list/create/inspect/modelCatalog/selectModel/prompt/cancel/rename/attachment/resolveAgent` and `SessionInspection { events }` | Unchanged; `session/attachment-invalid` with `MODEL_DOES_NOT_SUPPORT_IMAGES` still exists. |
+| Client: Details panel removed (`DetailsSlotProps`, `SelectionTarget`, `conversation.details.tool` gone); `openFile` gains `options`; `MarkdownText` gains optional `pathImages`; `conversation.chat.commandview` and `CommandRowProps` unchanged; `commands.execute(sessionId, line, attachments)` unchanged | None. Bridge does not use the removed types. |
+| `fs-ext` no longer compiles natively on macOS/Linux | Install no longer depends on a matching Node ABI. |
+| Semver: `^0.1.3-alpha.2` does not satisfy `0.1.5-alpha.1` | The only required change: add `|| ^0.1.5-alpha.1` to the five optional peers and pin devDependencies to `0.1.5-alpha.1`. |
+
+## Build against the 0.1.5-alpha.1 SDK
+
+- devDependencies pinned to `0.1.5-alpha.1`; `npm install` changed only the `@deepseek-ai/*` entries in the lockfile.
+- `tsc` typecheck of both halves passed; `tsdown` client build passed.
+- The generated `lib/` (server build and browser bundle) is byte-identical to the 0.3.3 build, so the SDK bump changes no shipped code.
+- Node 22.23.1 test run: 176/176 after updating the load test's pin and adding two V3 fixtures (fold ignores `system/message` and replacement nodes; the typed adapter's single-read window and the paged path agree on a V3 snapshot and never count system nodes toward the budget).
+
+## Installed host smoke
+
+Environment: official npm `@deepseek-ai/dsh@0.1.5-alpha.1` installed into a scratch prefix (541 packages, Node 22.23.1, pnpm 11.22.0), isolated `DSH_HOME`, no credentials configured, no user profile or session touched.
+
+| Check | Result |
+|---|---|
+| `dsh plugin --profile web add <packed tarball>` | Profile initialized; Bridge joined `dsh.profile.bundles` after `@deepseek-ai/dsh-base` and `@deepseek-ai/dsh-web-app`; no peer warnings |
+| `dsh web --no-open` boot | Served; the combined `/plugins/??…` module table includes `dsh-plugin-bridge/client.js`, and the served text contains the native-card style id and the `conversation.chat.commandview` registration |
+| Slash-command menu | `/bridge` listed with its description |
+| `/bridge --doctor` on a fresh session | `dsh-typed-controllers · 13/13 个方法可用`, mode `standard`, targets `ptc · minimal · cordis` |
+| `/bridge` (no arguments) | Usage plus `可迁入：ptc · minimal · cordis`, `当前：standard` |
+| Session storage | The created session was written as `session.v3.jsonl.zstd` |
+
+Both command results were read from the `POST /api/commands/execute` responses. The WebUI's `ws://…/api/remote.mux` stream could not be held by the automation browser used for this run, so the rendered card was not inspected visually; the card bundle itself is unchanged from 0.3.3, where it was verified on 0.1.3-alpha.2.
+
+## Not covered
+
+- No model request was made: the summary worker, native Text/Markdown editing, confirmation, target restatement, paused goal and image-to-text fallback were not re-run on 0.1.5-alpha.1. The 0.1.3-alpha.2 report remains the latest full migration evidence.
+- No in-place upgrade of an existing v2 profile to V3 was exercised; DSH states it rewrites supported histories into new V3 log files while preserving the originals, and Bridge reads history only through `inspect`, but this run did not measure it.
+- No removal/restart cycle was repeated on this host.
+
+The isolated install, profile and scratch workspace were left outside the repository and can be deleted; nothing from them is part of the package.