dsh-vision-router 3.1.5 → 3.2.1

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.
Files changed (47) hide show
  1. package/README.md +6 -6
  2. package/README.zh.md +6 -6
  3. package/THIRD_PARTY_NOTICES.md +107 -0
  4. package/assets/licenses/apache-2.0.txt +202 -0
  5. package/assets/licenses/moxcms-BSD-3-Clause.txt +26 -0
  6. package/assets/licenses/roots-BSD-2-Clause.txt +24 -0
  7. package/assets/licenses/unicode-ident-Unicode-3.0.txt +39 -0
  8. package/assets/licenses/vtracer-MIT.txt +25 -0
  9. package/assets/licenses/zlib-rs-Zlib.txt +19 -0
  10. package/cordis.patch.yml +8 -15
  11. package/docs/architecture/dsh-support-window-3.1-historical.md +98 -0
  12. package/docs/architecture/dsh-support-window.md +30 -83
  13. package/docs/architecture/dvr32-host-retirement.md +194 -0
  14. package/docs/ci-archive/README.md +3 -0
  15. package/docs/ci-archive/minimum-host-settings-persistence.legacy.js +118 -0
  16. package/docs/compatibility/dsh-0.2.2-rc2-audit.md +40 -0
  17. package/docs/compliance/vtracer-alpha4-provenance.md +47 -0
  18. package/docs/compliance/vtracer-alpha4-reconstructed-Cargo.lock +567 -0
  19. package/docs/compliance/vtracer-alpha4-rust-inventory.json +421 -0
  20. package/docs/compliance/vtracer-alpha4-rust-license-texts.md +13018 -0
  21. package/docs/progressive-tools-cache.md +4 -0
  22. package/docs/releases/v3.2.0-rc.0.md +16 -0
  23. package/docs/releases/v3.2.0.md +38 -0
  24. package/docs/releases/v3.2.1.md +21 -0
  25. package/docs/remote-settings.md +83 -8
  26. package/index.js +55 -57
  27. package/lib/client.js +13 -13
  28. package/lib/core-primitives.js +69 -187
  29. package/lib/doctor-cli-p0.js +14 -1
  30. package/lib/doctor-cli.js +70 -2
  31. package/lib/doctor-runtime.js +8 -3
  32. package/lib/doctor.js +57 -1
  33. package/lib/dsh-support-window.js +80 -31
  34. package/lib/grounding-box-recovery.js +76 -0
  35. package/lib/grounding-coordinate-runtime.js +10 -0
  36. package/lib/remote-settings-bridge.js +93 -57
  37. package/lib/remote-settings-risk-client-boundary.js +2 -2
  38. package/lib/runtime-i18n.js +4 -4
  39. package/lib/settings-client-017-compat.js +4 -2
  40. package/lib/settings-ia-client-prelude.js +26 -10
  41. package/lib/trace-vtracer-worker.js +163 -0
  42. package/lib/web/dsh-settings-017-root-transport.js +52 -6
  43. package/lib/web-capability-boundary.js +6 -0
  44. package/package.json +21 -26
  45. package/presets/README.md +0 -9
  46. package/presets/web-connection-ready/index.mjs +0 -48
  47. package/presets/web-connection-ready/package.json +0 -6
@@ -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.
@@ -0,0 +1,118 @@
1
+ import test from 'node:test'
2
+ import assert from 'node:assert/strict'
3
+ import path from 'node:path'
4
+ import { createRequire } from 'node:module'
5
+ import { pathToFileURL } from 'node:url'
6
+ import { Config } from '../entry.js'
7
+ import { mutateLocalRemoteSettingsPermission } from '../lib/local-remote-settings-permission.js'
8
+
9
+ function minimumHostSettingsRoot() {
10
+ const root = process.env.DSH_MINIMUM_SETTINGS_ROOT
11
+ assert.equal(
12
+ typeof root,
13
+ 'string',
14
+ 'DSH_MINIMUM_SETTINGS_ROOT must point at the isolated minimum-supported Host @deepseek-ai/dsh-settings package',
15
+ )
16
+ assert.notEqual(root.trim(), '', 'DSH_MINIMUM_SETTINGS_ROOT must not be blank')
17
+ return path.resolve(root)
18
+ }
19
+
20
+ test('minimum supported Host SettingsProvider persists allowRemoteSettings in the raw user section', async () => {
21
+ const settingsRoot = minimumHostSettingsRoot()
22
+ const settingsModule = await import(pathToFileURL(path.join(settingsRoot, 'lib/index.js')).href)
23
+ const peerRequire = createRequire(path.join(settingsRoot, 'package.json'))
24
+ const cordisEntry = peerRequire.resolve('@deepseek-ai/cordis')
25
+ const { Context } = await import(pathToFileURL(cordisEntry).href)
26
+
27
+ class MemorySettings extends settingsModule.SettingsProvider {
28
+ constructor(ctx) {
29
+ super(ctx)
30
+ this.doc = {}
31
+ }
32
+ get writable() { return true }
33
+ load() { return Promise.resolve(structuredClone(this.doc)) }
34
+ persist(ns, section) {
35
+ this.doc[ns] = structuredClone(section)
36
+ return Promise.resolve()
37
+ }
38
+ }
39
+
40
+ const ctx = new Context()
41
+ const fiber = ctx.plugin(MemorySettings)
42
+ await fiber
43
+ const provider = ctx.get('settings')
44
+ provider.register('vision-router', Config)
45
+
46
+ const before = provider.describe({ redactSecrets: true }).find((entry) => entry.ns === 'vision-router')
47
+ assert.ok(before)
48
+ assert.equal(before.user, undefined)
49
+ assert.equal(before.value.allowRemoteSettings, false)
50
+
51
+ const result = await mutateLocalRemoteSettingsPermission(provider, {
52
+ operation: 'set',
53
+ value: true,
54
+ expectedRevision: before.revision,
55
+ })
56
+ assert.equal(result.ok, true)
57
+
58
+ const after = provider.describe({ redactSecrets: true }).find((entry) => entry.ns === 'vision-router')
59
+ assert.ok(after)
60
+ assert.equal(after.user.allowRemoteSettings, true)
61
+ assert.equal(after.value.allowRemoteSettings, true)
62
+ assert.equal(provider.doc['vision-router'].allowRemoteSettings, true)
63
+ assert.ok(after.revision > before.revision)
64
+
65
+ await fiber.dispose()
66
+ })
67
+
68
+ test('minimum supported Host SettingsProvider preserves prototype routing fields without product authority', async () => {
69
+ const settingsRoot = minimumHostSettingsRoot()
70
+ const settingsModule = await import(pathToFileURL(path.join(settingsRoot, 'lib/index.js')).href)
71
+ const peerRequire = createRequire(path.join(settingsRoot, 'package.json'))
72
+ const cordisEntry = peerRequire.resolve('@deepseek-ai/cordis')
73
+ const { Context } = await import(pathToFileURL(cordisEntry).href)
74
+
75
+ class MemorySettings extends settingsModule.SettingsProvider {
76
+ constructor(ctx) {
77
+ super(ctx)
78
+ this.doc = {
79
+ 'vision-router': {
80
+ capabilityRoutingShadow: true,
81
+ capabilityRoutingStrategy: 'privacy',
82
+ },
83
+ }
84
+ }
85
+ get writable() { return true }
86
+ load() { return Promise.resolve(structuredClone(this.doc)) }
87
+ persist(ns, section) {
88
+ this.doc[ns] = structuredClone(section)
89
+ return Promise.resolve()
90
+ }
91
+ }
92
+
93
+ const ctx = new Context()
94
+ const fiber = ctx.plugin(MemorySettings)
95
+ await fiber
96
+ const provider = ctx.get('settings')
97
+ provider.register('vision-router', Config)
98
+
99
+ const before = provider.describe({ redactSecrets: true }).find((entry) => entry.ns === 'vision-router')
100
+ assert.ok(before)
101
+ const fields = before.schema.refs[String(before.schema.uid)].dict
102
+ assert.equal(Object.hasOwn(fields, 'capabilityRoutingShadow'), false)
103
+ assert.equal(Object.hasOwn(fields, 'capabilityRoutingStrategy'), false)
104
+ assert.equal(before.user.capabilityRoutingShadow, true)
105
+ assert.equal(before.user.capabilityRoutingStrategy, 'privacy')
106
+ assert.equal(before.value.routingMode, 'ordered')
107
+ assert.equal(before.value.routingPreference, 'balanced')
108
+
109
+ await provider.mutate('vision-router', [
110
+ { op: 'set', path: ['routingMode'], value: 'auto' },
111
+ ], before.revision)
112
+ assert.equal(provider.doc['vision-router'].capabilityRoutingShadow, true)
113
+ assert.equal(provider.doc['vision-router'].capabilityRoutingStrategy, 'privacy')
114
+ assert.equal(provider.get('vision-router').routingMode, 'auto')
115
+ assert.equal(provider.get('vision-router').routingPreference, 'balanced')
116
+
117
+ await fiber.dispose()
118
+ })
@@ -0,0 +1,40 @@
1
+ # DSH 0.2.2-rc.2 exact-source compatibility audit
2
+
3
+ ## Immutable basis
4
+
5
+ - Host: `deepseek-ai/deepseek-harness@ddac96760b6edf8fa0fe17cbdcf0b512f4c12b2c` (`dsh-v0.2.2-rc.2`, published 2026-11-11 11:33:06 UTC).
6
+ - DVR baseline: `300ec9828d7769fabd0ae423a4b3331f6b79d462` (`3.2.0`).
7
+ - Prior RC1 Host: `66491b05e3f05ad35bcdd4f6cd7ed26041d9e3db` (`dsh-v0.2.2-rc.1`).
8
+ - This audit is an acceptance candidate, **not** a compatibility certification or release.
9
+
10
+ ## RC2 surface deltas and DVR risks
11
+
12
+ 1. Session gained atomic batch `append([...])`. Its public `session/event(session,event)` contract remains per-event after the entire batch commits. DVR's feed-based vision index, surface repair and model-selection ownership depend on observing each event exactly once; test upstream batch acceptance/observer behavior on the exact release, then test DVR actual Host lifecycles.
13
+ 2. Agent model selection still occurs before `tools.resolve` and `agent/pre-step`. Keep DVR's early inbox-based model selection and verify real image->text route recovery. Never reinstate model changes at `agent/request`.
14
+ 3. Host changes include plugin startup failure handling, tool-error categories, dynamic MCP and LLM retry settings. Verify plugin mount/disposal, tool error propagation, Settings revisioned save/readback and native/Desktop route behavior instead of treating this release note as proof of parity.
15
+ 4. Web/desktop overlay and Settings compatibility shims remain subject to the exact-source contract, authenticated browser lifecycle, cold image/tool activation, mixed attachments and multi-plugin ordering. Do not delete overlays without an upstream-specific red/green proof.
16
+
17
+ ## Exit gates
18
+
19
+ - RC2 pin and workflow static tests; `pnpm build`, `pnpm build:check` and standard DVR tests.
20
+ - RC2 upstream Session append `append.spec.ts` (including atomic rollback, reentry and post-commit observer timing).
21
+ - Three-OS exact Host source and peer/proxy contracts on Node 24.9; no shared untrusted build caches.
22
+ - Real Chromium: cold Vision ON/OFF, mixed paste, Settings/save/reload, bundle recompose, Desktop Host wiring.
23
+ - Real macOS/Windows Desktop model route and reverse-text flow, Windows default tool-only path, multi-plugin ordering on Node 24.9/24.21.
24
+ - Follow-up triage for any failure using first failing product assertion versus infrastructure/bootstrap failure. Until all gates pass, keep the PR draft; no merge, tag or publish.
25
+
26
+ ## Actual acceptance evidence
27
+
28
+ - The previous fully reviewed PR head `fa58884352a5dbc9b0a67d6672262b5e787d98d4` completed [61 checks (59 success, 2 skipped, zero failure)](https://github.com/ysr666/dsh-vision-router/pull/830/checks) and the exact [RC2 Host Gate (six jobs successful)](https://github.com/ysr666/dsh-vision-router/actions/runs/43123077322). This is **historical SHA-specific evidence**, never a waiver for a changed head.
29
+ - On actual RC2 `SessionStore`, the DVR observer/index repaired 272 guards committed in **one** atomic append, with **16** precise overflow reads, **0** whole-log reads, exactly-once surface repair, isolated attachment indices and no dirty state after a failed batch. The upstream Session 14-test batch suite also passed.
30
+ - The current-PR candidate `.tgz` was built and inspected with `verify-packed-public-api.mjs`, then actually installed through the official RC2 CLI Host, with 3 successful bundle recompositions. A source-directory install alone is not the evidence.
31
+ - Real RC2 macOS Desktop, Windows Desktop (Node 24.9 and 24.21), browser cold Vision toggling, Settings save/reload, mixed attachment handling and multi-plugin ordering passed at that SHA.
32
+ - This validates **the PR checkout after later commits**. The published immutable `v3.2.0@676c6d7a` is **not** the audited main baseline `300ec982`: main includes Settings patches #823/#828 and VTracer migration #829 after the tag. A new **advisory-only** step runs the actual published `dsh-vision-router@3.2.0` from npm with an isolated RC2 Host and probes the local Settings transport. Its outcome must be examined separately; it cannot retroactively repair npm 3.2.0 and must not be counted as candidate certification.
33
+ - Issue [#826](https://github.com/ysr666/dsh-vision-router/issues/826) concerns the **Dataelem third-party Desktop generation installer**, not the official DeepSeek Harness Desktop or CLI installer. Its upstream bug [dataelement/dsh-desktop#563](https://github.com/dataelement/dsh-desktop/issues/563) and proposed fix [#565](https://github.com/dataelement/dsh-desktop/pull/565) remain open as of 2026-11-12. We have not tested the reporter's actual installed third-party Desktop; no success claim or issue closure is authorized.
34
+
35
+ ## Status
36
+
37
+ **RC2 current-checkout capability evidence: green at the prior tested head.** Any later commit must pass the full exact RC2 Host Gate again. The immutable npm 3.2.0 historical diagnostic and third-party generation installation are distinct evidence boundaries.
38
+
39
+ **No merge, release, or issue-state changes** follow automatically from this audit. A clean current-head CI matrix and an explicit owner decision remain required.
40
+