dsh-vision-router 3.1.5 → 3.2.0

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 CHANGED
@@ -22,7 +22,7 @@
22
22
  > **Data leaves your machine by default.** When a cloud vision model is used, Vision Router sends the image (or a derived crop), the vision prompt and related request metadata to that provider. A fresh install has an anonymous OVHcloud vision fallback enabled, so "free" and "no key" do **not** mean offline. Do not use the cloud chain for confidential, regulated or classified material. See [Data flow and strict local-only use](#data-flow-and-strict-local-only-use).
23
23
 
24
24
  > [!WARNING]
25
- > **v3.1.5 stability patch:** Bound canceled visual streams and empty-result caching (#798–#799), preserve fallback time across multiple backends (#800), classify and bound repeated HTTP 5xx failures including silent OCR/grounding transports (#804, #805, #810), fix picker-selected visual model dispatch (#801), correct misleading progressive Vision activation messages across deferred Host Fibers (#809), and add read-only Host-core dependency warnings (#802/#797). **The original #791 550/503 and #792 Windows screenshot remain unverified field incidents.** No settings, permission, privacy or Node/DSH support-floor change. See [v3.1.5 notes](docs/releases/v3.1.5.md). Confirm publication at [GitHub Releases](https://github.com/ysr666/dsh-vision-router/releases/latest) or npm.
25
+ > **v3.2.0 stable release:** Requires DSH >=0.2.1-rc.5 <0.3.0-0 and Node.js >=24.9.0; DSH 0.1.x / 0.2.0 and Node 22 are no longer supported by this version. The DSH Host owns Connection authorization and trustedHosts; DVR retains only the minimal third-party RPC startup-order patch. **Existing profiles are not upgraded automatically.** Run the read-only `doctor --upgrade-preflight` first, then separately verify legacy Session data, custom profile overlays and a rollback path. Older installations may stay on v3.1.5. See [v3.2.0 release notes](docs/releases/v3.2.0.md).
26
26
 
27
27
  ## Start here
28
28
 
@@ -422,8 +422,8 @@ ollama pull qwen2.5vl
422
422
  ## Requirements
423
423
 
424
424
  - DeepSeek Harness Web profile. Normal installs can use `npx @deepseek-ai/dsh ...`; source checkouts use `pnpm dsh ...`. A bare `dsh ...` command only works when the CLI is already on your shell `PATH`.
425
- - **DSH Host support policy:** DVR 3.0.x supports DSH 0.1.x continuously from `0.1.5-rc.1` (current stable evidence: `0.1.5-rc.3`) and supports the 0.2.x train from verified `0.2.0-rc.2`. Exact `0.2.0-rc.2` is also the ordinary 3.0 development Host. Pre-0.1.5 Hosts are unsupported, and DVR no longer publishes the older jagged 0.1.x exception list. Runtime behavior remains capability-based. See [DSH Host support window](docs/architecture/dsh-support-window.md).
426
- - Node ≥ 22 (host side).
425
+ - **DSH Host policy (unreleased DVR 3.2 candidate):** Minimum DSH 0.2.1-rc.5; currently recommended DSH 0.2.2-rc.1. DSH 0.1.x, 0.2.0 and earlier 0.2.1 prereleases are retired. DSH owns native Connection authentication, routing and trustedHosts. Older sessions, attachments and Settings data remain readable. See [new Host support window](docs/architecture/dsh-support-window.md) and [retirement plan](docs/architecture/dvr32-host-retirement.md).
426
+ - Node.js >=24.9.0 (Host side; Node 22 is retired).
427
427
  - No API key for the default free chain; a credential reference (`apiKeyEnv`) only for paid `httpProviders`.
428
428
  - Chrome / Chromium / Edge is needed only for `vision_html_screenshot`; every other tool works without a browser.
429
429
  - Desktop capture is opt-in. Windows and macOS use OS-provided capture facilities; Linux needs ImageMagick `import` or `scrot` and a capturable desktop session (Wayland support depends on the environment).
package/README.zh.md CHANGED
@@ -22,7 +22,7 @@
22
22
  > **默认配置会让数据出网。** 使用云端视觉模型时,Vision Router 会将图片(或由它裁剪出的局部)、识图提示词及相关请求元数据发送给对应供应商。新安装默认开启 OVHcloud 匿名视觉兜底,因此“免费”和“免 Key”不等于离线。涉密、涉案、内部或其他受限材料请勿使用云端链路。详见[数据流向与严格纯本地配置](#数据流向与严格纯本地配置)。
23
23
 
24
24
  > [!WARNING]
25
- > **v3.1.5 稳定性补丁:** 修复视觉流停止卡住与空结果缓存(#798–#799)、多模型回退预算耗尽(#800)、连续 HTTP 5xx 与无响应 OCR/定位回退无法及时结束(#804、#805、#810)、视觉复合模型分发错误(#801)、渐进式视觉工具已挂载却错误提示不可用(#809);doctor 增加 Host 核心依赖只读风险提示(#802/#797)。**#791 原用户 550/503 来源和 #792 Windows 启动截图根因仍未确认。** 不更改设置、权限、隐私策略或 Node/DSH 支持下限。详见 [v3.1.5 更新说明](docs/releases/v3.1.5.md),是否正式发布以 [GitHub Releases](https://github.com/ysr666/dsh-vision-router/releases/latest) 或 npm 为准。
25
+ > **v3.2.0 正式版:** 最低要求 DSH >=0.2.1-rc.5 <0.3.0-0、Node.js >=24.9.0;本版本不再支持 DSH 0.1.x / 0.2.0 和 Node 22。Connection 鉴权及 trustedHosts 由 DSH 负责,插件只保留第三方 RPC 所需的最小启动顺序补丁。**不会自动迁移已有 Profile。** 升级前请先运行只读 `doctor --upgrade-preflight`,再单独验收旧会话数据、自定义配置和回滚方案;旧环境可继续使用 v3.1.5。详见 [v3.2.0 发布说明](docs/releases/v3.2.0.md)。
26
26
 
27
27
  ## 先用起来
28
28
 
@@ -421,8 +421,8 @@ ollama pull qwen2.5vl
421
421
  ## 环境要求
422
422
 
423
423
  - DeepSeek Harness 的 Web profile。普通安装可用 `npx @deepseek-ai/dsh ...`;从源码仓库运行时用 `pnpm dsh ...`。只有 CLI 已经进入系统 `PATH` 时才能直接写 `dsh ...`。
424
- - **DSH Host 支持策略:** DVR 3.0.x 从 `0.1.5-rc.1` 起连续支持 DSH 0.1.x(当前稳定证据为 `0.1.5-rc.3`),并从已验证的 `0.2.0-rc.2` 起支持 0.2.x;精确 `0.2.0-rc.2` 同时作为 3.0 默认开发 Host。低于 0.1.5 的 Host 不再支持,也不再维护旧的 0.1.x 锯齿式例外列表。运行时仍按能力判断,而不是按版本字符串分支。详见 [DSH Host 支持窗口](docs/architecture/dsh-support-window.md)。
425
- - Node ≥ 22(宿主侧)。
424
+ - **DSH Host 支持策略(尚未发布的 DVR 3.2 候选):** 最低 DSH 0.2.1-rc.5,当前建议 0.2.2-rc.1;DSH 0.1.x、0.2.0 和更早的 0.2.1 预发布版本退役。连接鉴权、路由与 trustedHosts 由 DSH 官方 Connection 管理,DVR 仅保留 webServer 注入顺序补丁;旧版会话、图片附件和设置的持久化数据继续兼容。详见 [新版支持策略](docs/architecture/dsh-support-window.md) 与 [退役实施方案](docs/architecture/dvr32-host-retirement.md)。
425
+ - Node.js >=24.9.0(宿主侧;不再支持 Node 22)。
426
426
  - 默认免费链路无需 API Key;付费 `httpProviders` 只需一个凭据引用(`apiKeyEnv`)。
427
427
  - 只有 `vision_html_screenshot` 需要 Chrome / Chromium / Edge;其余工具无浏览器也能用。
428
428
  - 桌面截屏必须显式开启。Windows/macOS 使用系统截屏能力;Linux 需安装 ImageMagick `import` 或 `scrot`,且必须处于可截取的桌面会话(Wayland 支持取决于环境)。
package/cordis.patch.yml CHANGED
@@ -19,29 +19,22 @@
19
19
  name: '@deepseek-ai/dsh-client-modules'
20
20
  inject: [webServer]
21
21
 
22
- # DSH 0.1.x / 0.2.0-rc.2 Connection 的 Host owner 必须注入 webServer
23
- # (issue #478),但 0.2.1-alpha.2 已移除 webRuntime、改为 webStartup。
24
- # 不要静态引用任一代独有的 webRuntime:它会使新 Host 必需服务永远待定。
25
- #
26
- # 本层统一让 Connection 在 webServer、webStartup 及 DVR 私有 ready gate
27
- # 均就绪后启动;ready gate 在旧 Host 等官方 webRuntime(含 bind-derived
28
- # LAN authorities),在新 Host 直接读取官方 webStartup.trustedHosts。
29
- # trustedHosts 只转交 Host 授权列表,不自行扩大、合并或猜测网络信任;
30
- # Cookie、/api 和 RPC 仍归官方 Connection 所有。Host 新增配置项时,
31
- # exact-source contract 必须拒绝未经审查的整段 config 覆盖。
22
+ # The supported DSH Web Connection owns trustedHosts and authorization, but its
23
+ # generic connection.rpc.handle() registers a WebServer route from its provider
24
+ # Fiber. In 0.2.1-rc.5 / 0.2.2-rc.1 that Fiber does not explicitly inject
25
+ # webServer, so foreign plugins' RPC endpoints can fall through to the static
26
+ # GET/HEAD resource handler (HTTP 405). Retain ONLY the official webServer
27
+ # activation dependency; never replace the native Connection config/trust list.
28
+ # Verified by real Windows multi-plugin RPC red/green, #807.
32
29
  - id: connection
33
30
  name: '@deepseek-ai/dsh-client-connection'
34
- inject: [webStartup, webServer, visionRouterWebConnectionReady]
35
- config:
36
- trustedHosts: !!js ctx.visionRouterWebConnectionReady.trustedHosts
31
+ inject: [webStartup, webServer]
37
32
 
38
33
  # 挂载插件行。默认保持完整视觉工具表常驻(issue #81):虽然渐进挂载可以
39
34
  # 少发一小段工具 schema,但图片轮首次扩展工具列表会改变请求前缀,可能让
40
35
  # 长会话的 provider KV/prefix cache 整体失效。高级用户仍可在 profile /
41
36
  # composition 补丁中显式把 progressiveTools 改回 true(启动期配置)。
42
37
  - insert:
43
- - id: vision-router-web-connection-ready
44
- name: './presets/web-connection-ready/index.mjs'
45
38
  - id: vision-router
46
39
  name: dsh-vision-router
47
40
  config:
@@ -0,0 +1,98 @@
1
+ # DVR 3.1 historical support window (not applicable to DVR 3.2)
2
+
3
+ # DSH Host support window
4
+
5
+ Status: normative for the current DVR 3.x compatibility program.
6
+
7
+ ## Public support policy
8
+
9
+ The public support policy contains only released Host semantics. Preview/canary versions are intentionally excluded from this table.
10
+
11
+ | DVR train | Minimum Supported Host | Current Stable Host | Ordinary development Host |
12
+ |---|---|---|---|
13
+ | `2.2.x` | `0.1.0-rc.8` | `0.1.5-rc.3` | historical 2.2 development baseline |
14
+ | `2.3.x` | **DSH `0.1.5` train** | `0.1.5-rc.3` | historical 2.3 baseline |
15
+ | `3.0.x` | **DSH `0.1.5` train** | `0.1.5-rc.3` | **exact `0.2.0-rc.2`** |
16
+
17
+ DVR `2.2.x` keeps `0.1.0-rc.8` as its historical public floor.
18
+
19
+ DVR `2.3.0` deliberately resets the public minimum to the **DSH `0.1.5` train**. The earliest admitted release in that train is `0.1.5-rc.1`; current stable evidence is `0.1.5-rc.3`. DVR 2.3 no longer publishes a jagged list of `0.1.0` / `0.1.1` / `0.1.3` / `0.1.7` exceptions.
20
+
21
+ Ordinary DVR 2.3 development is pinned to **exact DSH `0.2.0-rc.2`** so `pnpm install && pnpm test` exercises the latest fully verified Host/Desktop generation rather than an obsolete compatibility floor. This exact development pin is evidence policy, not a reason to turn runtime behavior into version-string checks.
22
+
23
+ Runtime branching remains capability-based rather than version-string-driven.
24
+
25
+ ### DSH 0.2.x forward admission
26
+
27
+ DVR 2.2.x peer-admits the DSH `0.2.x` train from the verified rc.1 boundary (`>=0.2.0-rc.1 <0.3.0-0`) without raising its historical `0.1.0-rc.8` minimum Host floor.
28
+
29
+ DVR 2.3 uses exact `0.2.0-rc.2` as its ordinary development Host while keeping the public minimum at the `0.1.5` train. Peer admission is intentionally train-shaped: `>=0.1.5-rc.1 <0.2.0-0` for the continuous supported 0.1.x line from 0.1.5, plus `>=0.2.0-rc.2 <0.3.0-0` for the 0.2.x train from the verified rc.2 boundary. Initial forward admission was backed by public pre-0.2.0 master `21638c56315ae6a2b552d6091945d3144c9af32e`. Exact release evidence has now advanced to immutable `dsh-v0.2.0-rc.2` commit `639ed015397290b3745d163aafe02ffee4aa3f84`, published on 2026-09-29. Required gates cover three-OS source contracts, real Host + Chromium, Settings mount/save/reload/readback, mixed attachments, bundle recomposition, Windows Node 22/24 Desktop authentication, the Node 24 multi-plugin isolation adversary, and Host-owned Sharp resolution.
30
+
31
+ The final immutable upstream `0.2.0` stable tag and signed official Desktop installer remain release-time revalidation targets. The verified `0.2.0-rc.2` boundary is already part of DVR 2.3's peer-admitted supported 0.2.x train; it does not raise the public minimum above the DSH 0.1.5 train.
32
+
33
+ ## Verification evidence and drift canaries
34
+
35
+ Exact evidence answers which admitted Host points have current CI proof; moving canaries answer whether upstream has drifted beyond those points. Evidence inside an already declared train does not by itself change the minimum support floor, while peer-admission boundaries remain explicit support policy.
36
+
37
+ | Evidence role | DSH source | Meaning |
38
+ |---|---|---|
39
+ | Exact stable evidence | `0.1.5-rc.3` | Required Host/wire and real Host + Chromium coverage for the current stable release. |
40
+ | Exact supported 0.2.x boundary | `0.2.0-rc.2` (`next/rc`) | Required Host/wire/lifecycle/browser/Desktop evidence for the peer-admitted 0.2.x train; it does not raise the 0.1.5 minimum floor. |
41
+ | Stable drift canary | npm dist-tag `latest` | Scheduled, dynamically resolved surveillance. A failure starts compatibility investigation; it does not rewrite support policy. |
42
+ | Next/rc drift canary | npm dist-tag `next` | Scheduled, dynamically resolved surveillance for the rc channel. A failure does not rewrite support policy. |
43
+ | Alpha/pre-release drift canary | npm dist-tag `alpha` | Scheduled, dynamically resolved surveillance for the alpha channel. A failure does not rewrite support policy. |
44
+
45
+ Exact evidence points may advance inside an already admitted train when CI proof advances. The public minimum and any peer-admission boundary change remain explicit support-policy changes.
46
+
47
+ Historical release notes under `docs/releases/` are release-time snapshots and are not rewritten when later evidence advances.
48
+
49
+ Peer-dependency admission is itself part of the compatibility contract. DVR 2.3 deliberately admits the 0.2.x train from verified `0.2.0-rc.2`; moving npm `next`/`alpha` canaries outside that declared boundary remain surveillance only.
50
+
51
+ ## Floor transitions across DVR 2.x
52
+
53
+ DVR 2.0.x was released with DSH `0.1.0-rc.6` as its minimum Host. DVR 2.1.0 raised the public minimum to DSH `0.1.0-rc.8`; DVR 2.2.x inherited that rc.8 floor. DVR 2.3.0 raises the floor again to the DSH `0.1.5` train.
54
+
55
+ ```text
56
+ DVR 2.0.x minimum: DSH 0.1.0-rc.6
57
+ DVR 2.1.x minimum: DSH 0.1.0-rc.8
58
+ DVR 2.2.x minimum: DSH 0.1.0-rc.8
59
+ DVR 2.3.x minimum: DSH 0.1.5 train (earliest admitted release: 0.1.5-rc.1)
60
+ DVR 3.0.x minimum: DSH 0.1.5 train (unchanged from 2.3.x; earliest admitted release: 0.1.5-rc.1)
61
+ ```
62
+
63
+ Users on DSH trains older than `0.1.5` must upgrade DSH before upgrading to DVR 2.3.x or 3.0.x.
64
+
65
+ The 2.3 floor increase authorizes a fresh deletion audit for Host-version compatibility whose only purpose was keeping pre-`0.1.5` Hosts running. It does **not** authorize deleting compatibility for durable data merely because the Host that originally produced that data is no longer supported. Session logs, replay envelopes, persisted settings and other long-lived inputs require separate reachability evidence on supported Hosts.
66
+
67
+ ## Support-policy change protocol
68
+
69
+ A public Host support-floor change is valid only when all of the following are true:
70
+
71
+ 1. the floor change is announced in a DVR minor or major release, never only in a patch release;
72
+ 2. README / support documentation and release notes state the old and new floors;
73
+ 3. Doctor reports the effective public support policy and gives a capability-based upgrade result for Hosts below the active floor;
74
+ 4. required CI proves the public floor, current stable Host, and every declared forward-admission boundary, while moving canaries remain separately labelled surveillance;
75
+ 5. compatibility seams are removed only after the new minimum Host proves the replacement capability;
76
+ 6. removal PRs keep restart, settings, native-image coexistence, tool execution, Node 22/24 and supported-platform regressions green.
77
+
78
+ Advancing exact evidence inside an already declared train or moving a canary target does **not** by itself change the minimum support floor. Changing the peer-admitted train boundary is a support-policy change and must be explicit.
79
+
80
+ ## Capability-first rule
81
+
82
+ Version labels describe support policy and CI evidence; runtime branching still uses capabilities.
83
+
84
+ DVR must not turn these tables into widespread version-string conditionals. Runtime compatibility continues to feature-detect the concrete Host seam it needs. If a capability cannot be proven safely, the compatibility path fails open or reports an explicit unsupported/unknown state according to that seam's contract.
85
+
86
+ The same rule binds the contract gate. `scripts/dsh-host-contract-smoke.mjs` derives the settings
87
+ seam from the Host it is pointed at (`EXPECT_SETTINGS_MODE=auto`): the `0.1.5` train exposes
88
+ `SettingsProvider.register()`, while the `0.1.7` release and every `0.2.x` Host since — `0.2.0-rc.2`
89
+ through the `0.2.1` alpha line — replace it with `SettingsForms.describe()` plus ConfigEditor
90
+ `configuration()`/`edit()`. A gate that pins one shape reports an unsupported Host for a Host DVR
91
+ supports, so the floating canaries derive the seam, the pinned legs keep naming theirs explicitly,
92
+ and a Host with neither reviewed seam fails the gate by name instead of passing silently.
93
+
94
+ ## Compatibility-retirement rule
95
+
96
+ The 2.3.x `0.1.5` train floor makes any compatibility path used only by pre-`0.1.5` Hosts eligible for a fresh deletion audit, but does not automatically authorize deletion. Durable session formats, replay envelopes, adapter wire shapes, and other historical inputs may outlive the Host version that originally produced them.
97
+
98
+ See [DSH 0.2.0-rc.2 compatibility audit](dsh-020-rc2-adaptation.md) for the upstream seam review and validation plan.
@@ -1,96 +1,43 @@
1
- # DSH Host support window
1
+ # DVR 3.2 DSH Host support window
2
2
 
3
- Status: normative for the current DVR 3.x compatibility program.
3
+ **Status: 3.2.0-rc.0 development branch; NOT released.** The previous DVR 3.1.x support policy remains available in [historical support window](dsh-support-window-3.1-historical.md).
4
4
 
5
- ## Public support policy
5
+ | Policy | DVR 3.2 candidate |
6
+ |---|---|
7
+ | Minimum DSH Host | 0.2.1-rc.5 |
8
+ | Current recommended Host | 0.2.2-rc.1 (an RC, not a stable release) |
9
+ | DSH range | >=0.2.1-rc.5 <0.3.0-0 |
10
+ | Minimum Node.js | 24.9.0 |
11
+ | Retired | DSH 0.1.x, 0.2.0, 0.2.1-rc.4 or earlier; Node 22 |
6
12
 
7
- The public support policy contains only released Host semantics. Preview/canary versions are intentionally excluded from this table.
13
+ The prior DVR 3.1.4 release retains its historic support contract. The new support floor is a breaking compatibility-policy change, never a silent patch update.
8
14
 
9
- | DVR train | Minimum Supported Host | Current Stable Host | Ordinary development Host |
10
- |---|---|---|---|
11
- | `2.2.x` | `0.1.0-rc.8` | `0.1.5-rc.3` | historical 2.2 development baseline |
12
- | `2.3.x` | **DSH `0.1.5` train** | `0.1.5-rc.3` | historical 2.3 baseline |
13
- | `3.0.x` | **DSH `0.1.5` train** | `0.1.5-rc.3` | **exact `0.2.0-rc.2`** |
15
+ The published `engines.dsh` train allows later 0.2.x releases, including
16
+ prereleases, as a compatibility *admission policy*; it cannot guarantee their
17
+ runtime behavior. Doctor now distinguishes exact-release approval
18
+ (0.2.1-rc.5 and 0.2.2-rc.1 on Node 24) from merely being in that range:
19
+ future/unpinned 0.2.x Hosts and Node 25+ are marked `unknown`, not `ok`,
20
+ until separately validated. This does not rewrite the Host admission range
21
+ or block a user whose separately reviewed deployment works.
14
22
 
15
- DVR `2.2.x` keeps `0.1.0-rc.8` as its historical public floor.
23
+ ## Core Host ownership
16
24
 
17
- DVR `2.3.0` deliberately resets the public minimum to the **DSH `0.1.5` train**. The earliest admitted release in that train is `0.1.5-rc.1`; current stable evidence is `0.1.5-rc.3`. DVR 2.3 no longer publishes a jagged list of `0.1.0` / `0.1.1` / `0.1.3` / `0.1.7` exceptions.
25
+ Both DSH 0.2.1-rc.5 and DSH 0.2.2-rc.1 own webStartup trustedHosts and all Connection authorization. DVR 3.2 retires the cross-generation Connection config override and private readiness provider. However, a real Windows six-order foreign-plugin test caught HTTP 405 from generic connection.rpc.handle() when the Connection provider Fiber omitted a webServer injection. Thus DVR retains one **minimal ordering-only patch**: Connection inject: [webStartup, webServer], with **no config/trustedHosts override**. DSH still exclusively owns cookies, /api, WebSocket, trust authority and all other Connection config. Never extend, guess or bypass the official trust list.
18
26
 
19
- Ordinary DVR 2.3 development is pinned to **exact DSH `0.2.0-rc.2`** so `pnpm install && pnpm test` exercises the latest fully verified Host/Desktop generation rather than an obsolete compatibility floor. This exact development pin is evidence policy, not a reason to turn runtime behavior into version-string checks.
27
+ Keep the independent modules/webServer activation dependency and DVR disabled:false recompose guard until each replacement is independently proven; their root causes are not fixed merely by raising the Host floor.
20
28
 
21
- Runtime branching remains capability-based rather than version-string-driven.
29
+ DSH 0.2.1-rc.5+ uses `engines.dsh` as its sole native plugin-admission authority. **DSH 0.2.0-rc.2 still ignores engines.dsh** and only inspects DSH peers, so DVR retains exactly one optional `@deepseek-ai/dsh-llm-deepseek` peer with the same minimum as a defensive *old-Host rejection guard*. DVR retires the redundant anonymous-user-id and storage-domain peers, which can produce strict pnpm conflicts; no actual Host runtime service or type-only import is removed. The `sharp` optional peer remains.
22
30
 
23
- ### DSH 0.2.x forward admission
31
+ ## Acceptance and safety
24
32
 
25
- DVR 2.2.x peer-admits the DSH `0.2.x` train from the verified rc.1 boundary (`>=0.2.0-rc.1 <0.3.0-0`) without raising its historical `0.1.0-rc.8` minimum Host floor.
33
+ The initial unmodified Windows DSH 0.2.2-rc.1 Electron experiment on DVR 3.1.3 verified native Connection after disabling the bundle, preserving token 303, unauthenticated 401 and core-probe 200. One transient /connect timeout was observed. The initial zero-Connection-overrides design was later found to return HTTP 405 for third-party RPC endpoints
34
+ despite passing DVR's own Vision end-to-end tests. On Windows 0.2.2-rc.1, reproducing with identical
35
+ multi-plugin fixtures proved HTTP 405 before the minimal ordering patch and HTTP 200 after it for
36
+ all six plugin load orders. These observations are not proof of all cross-platform requirements.
37
+ The minimal patch must preserve the exact Host-owned trustedHosts config in both supported versions.
26
38
 
27
- DVR 2.3 uses exact `0.2.0-rc.2` as its ordinary development Host while keeping the public minimum at the `0.1.5` train. Peer admission is intentionally train-shaped: `>=0.1.5-rc.1 <0.2.0-0` for the continuous supported 0.1.x line from 0.1.5, plus `>=0.2.0-rc.2 <0.3.0-0` for the 0.2.x train from the verified rc.2 boundary. Initial forward admission was backed by public pre-0.2.0 master `21638c56315ae6a2b552d6091945d3144c9af32e`. Exact release evidence has now advanced to immutable `dsh-v0.2.0-rc.2` commit `639ed015397290b3745d163aafe02ffee4aa3f84`, published on 2026-09-29. Required gates cover three-OS source contracts, real Host + Chromium, Settings mount/save/reload/readback, mixed attachments, bundle recomposition, Windows Node 22/24 Desktop authentication, the Node 24 multi-plugin isolation adversary, and Host-owned Sharp resolution.
39
+ The new release requires both exact Host boundaries, Node 24.9 and newer 24 LTS, three OSes, cold/reenable/restart, authenticated and unauthenticated transport, trusted/untrusted LAN checks, real image-tool E2E, Settings persistence and historical-data readback.
28
40
 
29
- The final immutable upstream `0.2.0` stable tag and signed official Desktop installer remain release-time revalidation targets. The verified `0.2.0-rc.2` boundary is already part of DVR 2.3's peer-admitted supported 0.2.x train; it does not raise the public minimum above the DSH 0.1.5 train.
41
+ Old profile-owned Connection overrides may still exist after package upgrade because profile patches take precedence; Doctor should identify them without rewriting user files. Historical session formats, replay envelopes, attachment pixels and settings migrations remain supported independently of which Host produced them.
30
42
 
31
- ## Verification evidence and drift canaries
32
-
33
- Exact evidence answers which admitted Host points have current CI proof; moving canaries answer whether upstream has drifted beyond those points. Evidence inside an already declared train does not by itself change the minimum support floor, while peer-admission boundaries remain explicit support policy.
34
-
35
- | Evidence role | DSH source | Meaning |
36
- |---|---|---|
37
- | Exact stable evidence | `0.1.5-rc.3` | Required Host/wire and real Host + Chromium coverage for the current stable release. |
38
- | Exact supported 0.2.x boundary | `0.2.0-rc.2` (`next/rc`) | Required Host/wire/lifecycle/browser/Desktop evidence for the peer-admitted 0.2.x train; it does not raise the 0.1.5 minimum floor. |
39
- | Stable drift canary | npm dist-tag `latest` | Scheduled, dynamically resolved surveillance. A failure starts compatibility investigation; it does not rewrite support policy. |
40
- | Next/rc drift canary | npm dist-tag `next` | Scheduled, dynamically resolved surveillance for the rc channel. A failure does not rewrite support policy. |
41
- | Alpha/pre-release drift canary | npm dist-tag `alpha` | Scheduled, dynamically resolved surveillance for the alpha channel. A failure does not rewrite support policy. |
42
-
43
- Exact evidence points may advance inside an already admitted train when CI proof advances. The public minimum and any peer-admission boundary change remain explicit support-policy changes.
44
-
45
- Historical release notes under `docs/releases/` are release-time snapshots and are not rewritten when later evidence advances.
46
-
47
- Peer-dependency admission is itself part of the compatibility contract. DVR 2.3 deliberately admits the 0.2.x train from verified `0.2.0-rc.2`; moving npm `next`/`alpha` canaries outside that declared boundary remain surveillance only.
48
-
49
- ## Floor transitions across DVR 2.x
50
-
51
- DVR 2.0.x was released with DSH `0.1.0-rc.6` as its minimum Host. DVR 2.1.0 raised the public minimum to DSH `0.1.0-rc.8`; DVR 2.2.x inherited that rc.8 floor. DVR 2.3.0 raises the floor again to the DSH `0.1.5` train.
52
-
53
- ```text
54
- DVR 2.0.x minimum: DSH 0.1.0-rc.6
55
- DVR 2.1.x minimum: DSH 0.1.0-rc.8
56
- DVR 2.2.x minimum: DSH 0.1.0-rc.8
57
- DVR 2.3.x minimum: DSH 0.1.5 train (earliest admitted release: 0.1.5-rc.1)
58
- DVR 3.0.x minimum: DSH 0.1.5 train (unchanged from 2.3.x; earliest admitted release: 0.1.5-rc.1)
59
- ```
60
-
61
- Users on DSH trains older than `0.1.5` must upgrade DSH before upgrading to DVR 2.3.x or 3.0.x.
62
-
63
- The 2.3 floor increase authorizes a fresh deletion audit for Host-version compatibility whose only purpose was keeping pre-`0.1.5` Hosts running. It does **not** authorize deleting compatibility for durable data merely because the Host that originally produced that data is no longer supported. Session logs, replay envelopes, persisted settings and other long-lived inputs require separate reachability evidence on supported Hosts.
64
-
65
- ## Support-policy change protocol
66
-
67
- A public Host support-floor change is valid only when all of the following are true:
68
-
69
- 1. the floor change is announced in a DVR minor or major release, never only in a patch release;
70
- 2. README / support documentation and release notes state the old and new floors;
71
- 3. Doctor reports the effective public support policy and gives a capability-based upgrade result for Hosts below the active floor;
72
- 4. required CI proves the public floor, current stable Host, and every declared forward-admission boundary, while moving canaries remain separately labelled surveillance;
73
- 5. compatibility seams are removed only after the new minimum Host proves the replacement capability;
74
- 6. removal PRs keep restart, settings, native-image coexistence, tool execution, Node 22/24 and supported-platform regressions green.
75
-
76
- Advancing exact evidence inside an already declared train or moving a canary target does **not** by itself change the minimum support floor. Changing the peer-admitted train boundary is a support-policy change and must be explicit.
77
-
78
- ## Capability-first rule
79
-
80
- Version labels describe support policy and CI evidence; runtime branching still uses capabilities.
81
-
82
- DVR must not turn these tables into widespread version-string conditionals. Runtime compatibility continues to feature-detect the concrete Host seam it needs. If a capability cannot be proven safely, the compatibility path fails open or reports an explicit unsupported/unknown state according to that seam's contract.
83
-
84
- The same rule binds the contract gate. `scripts/dsh-host-contract-smoke.mjs` derives the settings
85
- seam from the Host it is pointed at (`EXPECT_SETTINGS_MODE=auto`): the `0.1.5` train exposes
86
- `SettingsProvider.register()`, while the `0.1.7` release and every `0.2.x` Host since — `0.2.0-rc.2`
87
- through the `0.2.1` alpha line — replace it with `SettingsForms.describe()` plus ConfigEditor
88
- `configuration()`/`edit()`. A gate that pins one shape reports an unsupported Host for a Host DVR
89
- supports, so the floating canaries derive the seam, the pinned legs keep naming theirs explicitly,
90
- and a Host with neither reviewed seam fails the gate by name instead of passing silently.
91
-
92
- ## Compatibility-retirement rule
93
-
94
- The 2.3.x `0.1.5` train floor makes any compatibility path used only by pre-`0.1.5` Hosts eligible for a fresh deletion audit, but does not automatically authorize deletion. Durable session formats, replay envelopes, adapter wire shapes, and other historical inputs may outlive the Host version that originally produced them.
95
-
96
- See [DSH 0.2.0-rc.2 compatibility audit](dsh-020-rc2-adaptation.md) for the upstream seam review and validation plan.
43
+ [Retirement execution and rollback](dvr32-host-retirement.md).
@@ -0,0 +1,194 @@
1
+ # DVR 3.2 Host retirement and rollback
2
+
3
+ **Branch:** feat/dvr32-retire-legacy-host. **Not merged, not released.** Scope: DSH >=0.2.1-rc.5 <0.3.0-0; Node >=24.9.0.
4
+
5
+ 1. Retire the private web-connection-ready plugin and all Connection config/trustedHosts overrides. Retain precisely one Connection inject: [webStartup, webServer] patch because the native Connection provider's generic foreign RPC registrations otherwise return HTTP 405 in Windows multi-plugin tests. Do not change official Host authentication or add trusted authorities.
6
+ 2. Preserve modules/webServer ordering, the DVR disabled:false recompose guard and old user-data migrators until separately proven obsolete.
7
+ 3. Keep engines.dsh as the **supported** Host compatibility authority. Retire the conflicting anonymous-user-id and storage-domain optional peers, but retain **one optional dsh-llm-deepseek peer** to reject older DSH 0.2.0 Hosts that ignore engines.dsh. Update engines.node, development fixtures, Doctor and release notes together.
8
+ 4. Negative admission must reject DSH 0.1.x, DSH 0.2.0, DSH 0.2.1-rc.4, Node 22 and Node 24.8.
9
+ 5. Require real DSH 0.2.1-rc.5 and 0.2.2-rc.1 installs: cold start, three enable-disable-reenable cycles, reconnection, 303/401/200, authenticated/unauthenticated API, WebSocket, trusted/untrusted LAN, actual Vision image turn and Settings/restart readback.
10
+ 6. Windows, macOS and Linux exact-source gates plus build, typecheck, reproducible pack and migration tests must be green.
11
+ 7. Retired Host workflows become historical/manual checks, not mandatory 3.2 release gates. Preserve old 3.1.4 packages and the historical support document.
12
+
13
+ **Rollback:** Revert the isolated 3.2 branch. Never auto-rewrite the user's profile patches, delete sessions, or release a partial change. Review manual profile-owned Connection overlays separately before user migration.
14
+
15
+ ## CI security pre-release hardening
16
+
17
+ The 3.2 DSH rc5 fixture introduced an unsafe transitive zod@4.4.3 (GHSA-mrhx-c7xc-m3w5). The workspace forces zod@4.6.7 across development fixtures, including DSH's transitive packages; the release manifest also consumes the patched runtime version. Recheck the entire lockfile and GitHub dependency review before publishing.
18
+
19
+ The floating DSH Alpha surveillance lane checks out an upstream commit chosen from a separately reviewed pin and runs on schedule or dispatch. It must never restore or save a shared Actions build cache that a later trusted branch could consume. All three Alpha Host job families now build in disposable job state; this costs CI time intentionally. Do not put the cache back merely to optimize the Alpha lane.
20
+
21
+ The weekly/dispatch Alpha settings workflow uses a literal reviewed immutable
22
+ SHA in all three upstream checkouts, and checks the config pin against that SHA
23
+ before fetching any upstream code. A config-only pin refresh bot cannot change
24
+ workflow execution authority; the human reviewer must explicitly update all
25
+ three static refs to the newly approved commit. A stale pin fails closed.
26
+
27
+ ## Windows multi-plugin 405 counterexample (2026-11-08)
28
+
29
+ Original zero-Connection-overlay release candidate passed normal DVR image-tool E2E but **failed** the independent third-party RPC/HTTP waterfall six-order test. With official DSH 0.2.2-rc.1, POST /fixture-rpc/ping fell through to the resource handler (405), because generic connection.rpc.handle registers its route using the Connection provider Fiber's webServer capability, which the DSH native Connection row did not inject. A minimal Connection overlay declaring inject: [webStartup, webServer] preserves the official config.trustedHosts unchanged and returned 200 for all six plugin orderings. This is a non-retired activation boundary, not authorization ownership. Security regression tests reject any extra Connection keys, a missing webServer, or revived private readiness service. Both supported exact-source DSH gates must assert the composed Connection retains the official config in structured form.
30
+
31
+ ## Retired DSH alpha.4 browser forensic
32
+
33
+ The previous continuous PR browser smoke explicitly checked out DSH 0.1.2-alpha.4,
34
+ which predates the DVR 3.2 minimum by several years and still requires the
35
+ legacy webRuntime Connection dependency. Keeping it as a PR release gate would
36
+ force the private readiness bridge back into production, negating this retirement.
37
+ The original #387 forensic workflow is retained as workflow_dispatch only,
38
+ using the last green historical DVR fbe230ca04c2... and the original
39
+ pre-#388 comparison c7c92d25f7c5..., so investigators can still reproduce the
40
+ old bug without pretending that DVR 3.2 supports the retired Host.
41
+ The **same alpha-browser-cold-toggle-smoke.mjs** remains an active PR/main gate
42
+ against supported pinned DSH 0.2.1-rc.5 in dsh-021-rc5-validation.yml;
43
+ that live cold toggle, Settings lifecycle, and renderer tests must not be removed.
44
+
45
+ ## Upgrade preflight and safe rollback for existing profiles
46
+
47
+ This is a **prerelease** compatibility change, not an automatic 3.1.x patch.
48
+ The 3.1.4 line remains available. **Do not update a working DSH profile merely
49
+ to validate this PR.** Validate first in a disposable profile / development
50
+ installation; do not test by rewriting someone else's live config.
51
+
52
+ 1. Verify Node.js >=24.9.0 and the actual DSH executable's version is within
53
+ `>=0.2.1-rc.5 <0.3.0-0`. Check the **running Desktop's bundled Host**
54
+ separately from a shell's unrelated `dsh` command. An Oh-DSH profile has
55
+ its own home and must not be confused with the official ~/.dsh home.
56
+ 2. Back up the **complete selected profile directory**, including
57
+ `package.json`, `pnpm-lock.yaml`, and `cordis.patch.yml`, and record the
58
+ previous DSH and DVR package versions. Keep independent session, attachment,
59
+ and settings data intact; do not auto-delete or auto-migrate those stores.
60
+ 3. From the **3.2 source checkout**, run the **read-only** preflight:
61
+ `node lib/doctor-cli-p0.js doctor --profile desktop --upgrade-preflight --no-runtime`
62
+ (or substitute `web` for the actual profile). Never use `--fix` or `repair`
63
+ as a preflight, and do not paste raw private reports into public issues.
64
+ The explicit `--upgrade-preflight` mode returns **nonzero** for known
65
+ profile-owned Connection overrides, retired ready-bridge references, stale
66
+ workspace version-pinned release-age exclusions, floating GitHub DVR
67
+ package refs (default branch, main/master or other non-immutable branches),
68
+ or an unsupported Node version. Ordinary `doctor` still treats historical
69
+ patch warnings as advisories. A zero exit means only that these known **local profile**
70
+ hazards were not detected: it never proves the actual Desktop Host version,
71
+ runtime image-tool functionality, browser trust, or session migration.
72
+ Report `upgradePreflight.fullReleaseApproval` is always false.
73
+ In particular, a `github:ysr666/dsh-vision-router` or `#main` dependency
74
+ may update as soon as `main` advances, bypassing npm `next` altogether.
75
+ A locked `pnpm-lock.yaml` records today's commit but is not a permanent
76
+ safeguard against future lock regeneration. Explicit version tags are
77
+ more stable than branches but can still be force-moved; only a full commit
78
+ SHA is immutable. These version-specific refs are exempt from this
79
+ floating-source warning. Freeze refs only in a **backed-up isolated profile copy**
80
+ first; do not silently rewrite active development profiles.
81
+ 4. If Doctor finds a **profile-owned** `id: connection` row or any
82
+ `visionRouterWebConnectionReady` / `vision-router-web-connection-ready`
83
+ reference, review the user's exact custom overlay **after backup** before
84
+ enabling 3.2. Profile patches apply after bundled patches: a historic
85
+ `webRuntime` injection or old Connection `config` can override the newly
86
+ verified Host settings and break startup. **Never delete arbitrary profile
87
+ rows, credentials, trusted hosts, or another plugin's configuration.**
88
+ 5. The 3.2 **bundle-owned** Connection row is intentional and should not be
89
+ removed: its only override is `inject: [webStartup, webServer]`, preserving
90
+ the official Host's `config.trustedHosts` and auth semantics. Doctor's
91
+ **profile-owned** override warnings refer to *separate, later user patches*,
92
+ not to this bundled compatibility ordering shim.
93
+ 6. On a disposable upgraded profile, verify cold start, Settings save/reload,
94
+ browser auth, actual vision result, third-party plugin RPC, and disabling
95
+ the **entire** DVR bundle without losing the Host's `/`, `/connect`, or
96
+ `/api` routes. Restore the backed-up profile together with the previously
97
+ installed compatible DSH/DVR pair if recovery is required. Never claim
98
+ session or image preservation from a fresh-profile-only test.
99
+
100
+ ### Historical DSH session format is a separate upstream upgrade gate
101
+
102
+ An installer-compatible Host does **not** prove historical Session migration.
103
+ The released DSH v0 format writer once produced `permission/preset` with an
104
+ additional `origin` key, which current v0-to-v1 readers may reject. Older
105
+ Hosts also reject certain released `subagent/descriptor` version-2 events.
106
+ See upstream [discussion #9421](https://github.com/deepseek-ai/deepseek-harness/discussions/9421)
107
+ and [#9343](https://github.com/deepseek-ai/deepseek-harness/discussions/9343).
108
+ These are **DSH persistence-reader responsibilities**, not DVR vision routing.
109
+
110
+ Before retiring a user's old Host, validate **their data** using an isolated
111
+ backup and the target Host's actual Session-persistence `open(id, 'read')`
112
+ API. For legacy v0 stores, favor 0.2.2-rc.1 over 0.2.1-rc.5 where version-2
113
+ subagent descriptors exist; even 0.2.2-rc.1 cannot read all original
114
+ `permission/preset.origin` sources unmodified. A narrow offline
115
+ normalization of known released variants can be evaluated **only on a copy**,
116
+ with original byte-identical backups and read-only API verification. Do not
117
+ strip arbitrary event fields, migrate all user logs in-place, or infer
118
+ successful history migration from the plugin's profile preflight status.
119
+ No historical-log repair or automatic migration is implemented in DVR 3.2.
120
+
121
+ No code in this PR edits existing user profiles, session logs, image attachments,
122
+ or saved settings as part of retirement. The remaining upstream stale-Fiber HMR
123
+ issue and the separate #792 source-text screenshot investigation stay tracked
124
+ independently; this document does not claim that either upstream defect is fixed.
125
+
126
+
127
+ ## DSH 3.2 legacy admission and peer-graph retirement: two-sided A/B
128
+
129
+ Supported DSH 0.2.1-rc.5+ uses `engines.dsh` as its sole native
130
+ plugin-admission authority, but **official DSH 0.2.0-rc.2 only inspects
131
+ `@deepseek-ai/dsh-*` peers**, ignoring `engines.dsh` entirely. Testing
132
+ that official old evaluator against an otherwise identical 3.2 manifest
133
+ proved the crucial negative control:
134
+ - **Zero DSH peer declarations**: old DSH 0.2.0-rc.2 **incorrectly admits**
135
+ DVR 3.2. This is unsafe, even though 3.2 announces that it retired 0.2.0.
136
+ - One optional `@deepseek-ai/dsh-llm-deepseek` peer with the exact canonical
137
+ `>=0.2.1-rc.5 <0.3.0-0` requirement: old DSH 0.2.0-rc.2 **rejects**
138
+ DVR 3.2. Modern rc5/rc1 evaluators still use `engines.dsh` first.
139
+
140
+ Therefore DVR 3.2 **retains exactly one** optional DSH LLM peer solely to
141
+ protect legacy Hosts that have not yet learned `engines.dsh`. It retires the
142
+ other two old optional DSH peers (`anonymous-user-id` and `storage-domain`)
143
+ because they add pnpm dependency-graph conflicts without protecting the
144
+ minimum supported Host any further. The `sharp` optional peer is unaffected.
145
+
146
+ Disposable Node 24.21 / pnpm 11.20 strict-install A/B using the actual
147
+ 3.2 prerelease tarball and published Host provider components:
148
+ - With DSH llm-deepseek rc1 alone, the original three-peer candidate **failed**
149
+ `ERR_PNPM_PEER_DEP_ISSUES` because anonymous-user-id had two constraints
150
+ but was not explicitly installed.
151
+ - Installing anonymous-user-id explicitly made that original candidate pass,
152
+ confirming the cause was the peer graph, not RC version admission.
153
+ - Retaining only the **single legacy LLM guard** and `sharp` passed
154
+ `strictPeerDependencies=true` with DSH llm-deepseek **both rc5 and rc1**,
155
+ without an explicit anonymous-user-id install.
156
+ - A package with zero legacy peers also installed, but failed the older-Host
157
+ safety requirement above, and was intentionally discarded.
158
+
159
+ DSH Host modules must still not be imported statically at runtime by
160
+ DVR's activation entries; the source, generated-tree and
161
+ child-process negative-control tests continue blocking all three
162
+ Host-provided module names (even the two no longer in peerDependencies).
163
+ The source-only storage-domain import is type-only.
164
+
165
+ No real user profile or npm release was changed during these tests.
166
+
167
+ ## Release-channel safety when retiring old Host generations
168
+
169
+ Retirement is a new minor prerelease, **not a default npm upgrade**.
170
+ The protected release workflow must verify on Node >=24.9 (exact Node 24.21
171
+ in the release verification job). Before creating an immutable Git tag,
172
+ `scripts/release-channel.mjs` classifies only canonical stable, `rc.N`,
173
+ and `alpha.N` versions; unknown preview classes fail closed.
174
+
175
+ - `3.2.0-rc.0` publishes to npm `next` and is marked GitHub prerelease,
176
+ never GitHub Latest; `3.2.0-alpha.N` would use npm `alpha`.
177
+ - Only a reviewed stable version such as `3.2.0` may update npm `latest`
178
+ and GitHub Latest. The existing DVR 3.1.4 package stays installable.
179
+ - This release-channel gate is independent from the installation,
180
+ profile-upgrade and real image-tool acceptance gates. Success here
181
+ does not authorize publishing, re-tagging an immutable npm version,
182
+ or rewriting any user profile.
183
+
184
+ ## Transient Electron transport failures in Desktop CI
185
+
186
+ Exact-source Desktop E2E can fail *before* renderer assertions when GitHub
187
+ returns HTTP 502/503/504 for the **official pnpm-locked Electron binary**.
188
+ The CI-only `scripts/ci-electron-download-retry.mjs` recovers solely from
189
+ Electron's missing-binary error: it invokes the same package's own
190
+ `install.js` with at most three bounded attempts and short backoff.
191
+ It never chooses an alternate mirror, version or unchecked artifact and
192
+ never retries screenshot assertions, DSH Host errors or other non-download
193
+ failures. Exhausted retries still fail the CI job. The default CodeQL
194
+ scanning task has an independent download lifecycle and is not bypassed.
@@ -0,0 +1,3 @@
1
+ # DVR 3.1 historical Host tests
2
+
3
+ These tests exercised the old DSH 0.1.5 SettingsProvider Host and were retired as active release gates with the DVR 3.2 minimum of DSH 0.2.1-rc.5. They are retained as historical evidence, not as a runnable 3.2 test suite. Durable migration and Settings persistence remain covered by 3.2 runtime and Host tests.