dsh-plugin-bridge 0.3.3 → 0.3.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -4
- package/README.zh.md +5 -4
- package/docs/design.md +1 -1
- package/docs/guide.zh.md +3 -3
- package/package.json +15 -14
- package/reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md +49 -0
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
[](https://github.com/Totoro-qaq/dsh-plugin-bridge/actions/workflows/ci.yml)
|
|
10
10
|
[](LICENSE)
|
|
11
11
|
[](package.json)
|
|
12
|
-
[](https://github.com/deepseek-ai/deepseek-harness)
|
|
13
13
|
[](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)
|
|
14
14
|
[](https://dshfind.com/en/plugins/Totoro-qaq/dsh-plugin-bridge?ref=badge)
|
|
15
15
|
|
|
@@ -35,7 +35,7 @@ dsh plugin --profile web add dsh-plugin-bridge
|
|
|
35
35
|
Pinned GitHub fallback:
|
|
36
36
|
|
|
37
37
|
```bash
|
|
38
|
-
dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.
|
|
38
|
+
dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.4
|
|
39
39
|
```
|
|
40
40
|
|
|
41
41
|
Then type in the official WebUI:
|
|
@@ -119,8 +119,9 @@ The five sections are Goal, Current state, Key decisions and conventions, Key fi
|
|
|
119
119
|
| 0.1.1-rc.2 | Yes | Yes | Installed official WebUI: doctor 13/13, edit/confirm/auto-open, three-run repeat gate |
|
|
120
120
|
| 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 |
|
|
121
121
|
| 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) |
|
|
122
|
+
| 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) |
|
|
122
123
|
|
|
123
|
-
Use Bridge 0.3.3 or later for DSH 0.1.3-alpha.2; Bridge 0.3.2 does not include
|
|
124
|
+
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.
|
|
124
125
|
|
|
125
126
|
CI covers Node.js 22 and 24. Run `/bridge --doctor` after every Harness upgrade; it names missing required gateway methods instead of failing vaguely.
|
|
126
127
|
|
|
@@ -151,7 +152,7 @@ npm ci
|
|
|
151
152
|
npm run verify
|
|
152
153
|
```
|
|
153
154
|
|
|
154
|
-
`verify` builds and type-checks both plugin halves, runs
|
|
155
|
+
`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.
|
|
155
156
|
|
|
156
157
|
Community listings: [Awesome DSH Plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin) · [Awesome DeepSeek Harness](https://github.com/Dominic789654/awesome-deepseek-harness)
|
|
157
158
|
|
package/README.zh.md
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
[](https://github.com/Totoro-qaq/dsh-plugin-bridge/actions/workflows/ci.yml)
|
|
10
10
|
[](LICENSE)
|
|
11
11
|
[](package.json)
|
|
12
|
-
[](https://github.com/deepseek-ai/deepseek-harness)
|
|
13
13
|
[](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)
|
|
14
14
|
[](https://dshfind.com/zh/plugins/Totoro-qaq/dsh-plugin-bridge?ref=badge)
|
|
15
15
|
|
|
@@ -35,7 +35,7 @@ dsh plugin --profile web add dsh-plugin-bridge
|
|
|
35
35
|
GitHub 固定版本备用路径：
|
|
36
36
|
|
|
37
37
|
```bash
|
|
38
|
-
dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.
|
|
38
|
+
dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.4
|
|
39
39
|
```
|
|
40
40
|
|
|
41
41
|
然后在官方 WebUI 输入：
|
|
@@ -119,8 +119,9 @@ token 百分比会随 preset、回复长度和缓存状态大幅波动；worker
|
|
|
119
119
|
| 0.1.1-rc.2 | 支持 | 支持 | 官方 WebUI 实装：doctor 13/13、编辑/确认/自动跳转、三次重复门禁 |
|
|
120
120
|
| 0.1.2-alpha.2 / alpha.3 / alpha.5 | 支持 | 支持 | 官方 DSH npm 宿主：typed controllers 13/13 与 PTC 自动跳转；alpha.5 门禁安装分支 tarball，保留 alpha.3 标题，编号列表可编辑，未解析图片降级为文本，卸载干净 |
|
|
121
121
|
| 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) |
|
|
122
|
+
| 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) |
|
|
122
123
|
|
|
123
|
-
DSH 0.1.3-alpha.2 请使用 Bridge 0.3.3 或更高版本；Bridge 0.3.2
|
|
124
|
+
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` 检查方法是否存在，不能代替完整迁移验收。
|
|
124
125
|
|
|
125
126
|
CI 覆盖 Node.js 22/24。每次升级 Harness 后先跑 `/bridge --doctor`；缺哪个必要网关方法会被直接点名。
|
|
126
127
|
|
|
@@ -151,7 +152,7 @@ npm ci
|
|
|
151
152
|
npm run verify
|
|
152
153
|
```
|
|
153
154
|
|
|
154
|
-
`verify` 会构建并类型检查插件两端、运行
|
|
155
|
+
`verify` 会构建并类型检查插件两端、运行 176 项测试、核对 `lib/` 与数据集，再把真实 npm tarball 打包、安装并导入。测试不消耗模型 token。`prepublishOnly` 使用同一个 gate；GitHub Release 还会先检查 tag 与 `package.json` 版本一致，再走可信 npm 发布。
|
|
155
156
|
|
|
156
157
|
社区收录：[Awesome DSH Plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin) · [Awesome DeepSeek Harness](https://github.com/Dominic789654/awesome-deepseek-harness)
|
|
157
158
|
|
package/docs/design.md
CHANGED
|
@@ -81,6 +81,6 @@ Bridge's preview, safety, and migration engine depends on the typed `BridgeHost`
|
|
|
81
81
|
|
|
82
82
|
`/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.
|
|
83
83
|
|
|
84
|
-
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).
|
|
84
|
+
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.
|
|
85
85
|
|
|
86
86
|
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
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
|
|
5
5
|
## 1. 安装
|
|
6
6
|
|
|
7
|
-
前置：已安装 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
|
|
7
|
+
前置：已安装 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` 即会自动初始化）。
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
10
|
dsh plugin --profile web add dsh-plugin-bridge
|
|
@@ -13,7 +13,7 @@ dsh plugin --profile web add dsh-plugin-bridge
|
|
|
13
13
|
需要固定 GitHub tag 或 npm 暂时不可用时：
|
|
14
14
|
|
|
15
15
|
```bash
|
|
16
|
-
dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.
|
|
16
|
+
dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.3.4
|
|
17
17
|
```
|
|
18
18
|
|
|
19
19
|
发生了什么（不用手动干预）：
|
|
@@ -141,7 +141,7 @@ dsh-bridge migrate --to code --summary-file <path>
|
|
|
141
141
|
A：确认重启过 `dsh web`（插件在启动时挂载），并且用的是 `web` profile。命令注册依赖 `commands` 服务；执行时优先用 rc.2 的 `apiProxy`，alpha 则使用 typed Session / Workspace / Preset / Goal controllers。必要能力不完整时 `/bridge --doctor` 会逐项报告，不会假装可用。
|
|
142
142
|
|
|
143
143
|
**Q：升级了 dsh 之后还能用吗？**
|
|
144
|
-
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
|
|
144
|
+
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 与预设列表，需要模型的迁移验收尚未重跑。
|
|
145
145
|
|
|
146
146
|
**Q：图片迁移需要怎么选模型？**
|
|
147
147
|
A：图片已有助手分析时，Bridge 逐字搬这段视觉证据，不需要再次烧视觉 token。图片还没被分析时，源会话应选 `deepseek-v4-flash-vision-exp` 等视觉路由；Bridge 会在 kickoff 前把源 provider/model/reasoning effort 复制到目标，再搬原图。文本模型仍不能识图，Bridge 也不会暗中启动本地视觉模型。
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-plugin-bridge",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.4",
|
|
4
4
|
"description": "Previewable cross-preset session migration for DeepSeek Harness with bounded, fixed-schema handoffs",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "lib/index.js",
|
|
@@ -15,6 +15,7 @@
|
|
|
15
15
|
"reports/native-workbench-2026-08-25.raw.json",
|
|
16
16
|
"reports/dsh-0.1.2-alpha.2-compat-2026-08-31.md",
|
|
17
17
|
"reports/dsh-0.1.3-alpha.2-compat-2026-09-08.md",
|
|
18
|
+
"reports/dsh-0.1.5-alpha.1-compat-2026-09-09.md",
|
|
18
19
|
"cordis.patch.yml",
|
|
19
20
|
"README.md",
|
|
20
21
|
"README.zh.md"
|
|
@@ -61,11 +62,11 @@
|
|
|
61
62
|
},
|
|
62
63
|
"peerDependencies": {
|
|
63
64
|
"@deepseek-ai/cordis": "^4.0.1",
|
|
64
|
-
"@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",
|
|
65
|
-
"@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",
|
|
66
|
-
"@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",
|
|
67
|
-
"@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",
|
|
68
|
-
"@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",
|
|
65
|
+
"@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",
|
|
66
|
+
"@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",
|
|
67
|
+
"@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",
|
|
68
|
+
"@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",
|
|
69
|
+
"@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",
|
|
69
70
|
"react": "^18.2.0"
|
|
70
71
|
},
|
|
71
72
|
"peerDependenciesMeta": {
|
|
@@ -82,14 +83,14 @@
|
|
|
82
83
|
},
|
|
83
84
|
"devDependencies": {
|
|
84
85
|
"@deepseek-ai/cordis": "4.0.2",
|
|
85
|
-
"@deepseek-ai/dsh-api-remotes": "0.1.
|
|
86
|
-
"@deepseek-ai/dsh-api-session-controller": "0.1.
|
|
87
|
-
"@deepseek-ai/dsh-client-ui-chat": "0.1.
|
|
88
|
-
"@deepseek-ai/dsh-client-ui-conversation": "0.1.
|
|
89
|
-
"@deepseek-ai/dsh-client-ui-primitives": "0.1.
|
|
90
|
-
"@deepseek-ai/dsh-client-ui-renderer": "0.1.
|
|
91
|
-
"@deepseek-ai/dsh-client-ui-session": "0.1.
|
|
92
|
-
"@deepseek-ai/dsh-client-ui-slots": "0.1.
|
|
86
|
+
"@deepseek-ai/dsh-api-remotes": "0.1.5-alpha.1",
|
|
87
|
+
"@deepseek-ai/dsh-api-session-controller": "0.1.5-alpha.1",
|
|
88
|
+
"@deepseek-ai/dsh-client-ui-chat": "0.1.5-alpha.1",
|
|
89
|
+
"@deepseek-ai/dsh-client-ui-conversation": "0.1.5-alpha.1",
|
|
90
|
+
"@deepseek-ai/dsh-client-ui-primitives": "0.1.5-alpha.1",
|
|
91
|
+
"@deepseek-ai/dsh-client-ui-renderer": "0.1.5-alpha.1",
|
|
92
|
+
"@deepseek-ai/dsh-client-ui-session": "0.1.5-alpha.1",
|
|
93
|
+
"@deepseek-ai/dsh-client-ui-slots": "0.1.5-alpha.1",
|
|
93
94
|
"@types/node": "^26.2.0",
|
|
94
95
|
"@types/react": "~18.3.1",
|
|
95
96
|
"react": "^18.3.1",
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# DSH 0.1.5-alpha.1 compatibility smoke
|
|
2
|
+
|
|
3
|
+
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`.
|
|
4
|
+
|
|
5
|
+
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).
|
|
6
|
+
|
|
7
|
+
## Upstream change
|
|
8
|
+
|
|
9
|
+
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`):
|
|
10
|
+
|
|
11
|
+
| Change | Effect on Bridge |
|
|
12
|
+
|---|---|
|
|
13
|
+
| 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. |
|
|
14
|
+
| `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`. |
|
|
15
|
+
| `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. |
|
|
16
|
+
| `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. |
|
|
17
|
+
| 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. |
|
|
18
|
+
| `fs-ext` no longer compiles natively on macOS/Linux | Install no longer depends on a matching Node ABI. |
|
|
19
|
+
| 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`. |
|
|
20
|
+
|
|
21
|
+
## Build against the 0.1.5-alpha.1 SDK
|
|
22
|
+
|
|
23
|
+
- devDependencies pinned to `0.1.5-alpha.1`; `npm install` changed only the `@deepseek-ai/*` entries in the lockfile.
|
|
24
|
+
- `tsc` typecheck of both halves passed; `tsdown` client build passed.
|
|
25
|
+
- 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.
|
|
26
|
+
- 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).
|
|
27
|
+
|
|
28
|
+
## Installed host smoke
|
|
29
|
+
|
|
30
|
+
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.
|
|
31
|
+
|
|
32
|
+
| Check | Result |
|
|
33
|
+
|---|---|
|
|
34
|
+
| `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 |
|
|
35
|
+
| `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 |
|
|
36
|
+
| Slash-command menu | `/bridge` listed with its description |
|
|
37
|
+
| `/bridge --doctor` on a fresh session | `dsh-typed-controllers · 13/13 个方法可用`, mode `standard`, targets `ptc · minimal · cordis` |
|
|
38
|
+
| `/bridge` (no arguments) | Usage plus `可迁入：ptc · minimal · cordis`, `当前：standard` |
|
|
39
|
+
| Session storage | The created session was written as `session.v3.jsonl.zstd` |
|
|
40
|
+
|
|
41
|
+
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.
|
|
42
|
+
|
|
43
|
+
## Not covered
|
|
44
|
+
|
|
45
|
+
- 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.
|
|
46
|
+
- 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.
|
|
47
|
+
- No removal/restart cycle was repeated on this host.
|
|
48
|
+
|
|
49
|
+
The isolated install, profile and scratch workspace were left outside the repository and can be deleted; nothing from them is part of the package.
|