dsh-auth-remote 0.3.3 → 0.3.5
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/CHANGELOG.md +16 -0
- package/CHANGELOG.zh-CN.md +16 -0
- package/CONTRIBUTING.md +1 -1
- package/CONTRIBUTING.zh-CN.md +1 -1
- package/README.md +23 -16
- package/README.zh-CN.md +23 -16
- package/dist/client.js +8 -0
- package/dist/client.js.map +2 -2
- package/dist/index.js +22 -17
- package/dist/index.js.map +2 -2
- package/dist/types/shared/dsh-support.d.ts.map +1 -1
- package/docs/deployment.md +11 -7
- package/docs/deployment.zh-CN.md +11 -7
- package/docs/development.md +40 -29
- package/docs/development.zh-CN.md +40 -29
- package/docs/legacy-compatibility.md +115 -70
- package/docs/legacy-compatibility.zh-CN.md +115 -70
- package/docs/releasing.md +13 -11
- package/docs/releasing.zh-CN.md +13 -11
- package/docs/reverse-proxy.md +2 -0
- package/docs/reverse-proxy.zh-CN.md +2 -0
- package/docs/support-history.md +69 -63
- package/docs/support-history.zh-CN.md +69 -63
- package/docs/support-policy.md +29 -15
- package/docs/support-policy.zh-CN.md +29 -15
- package/package.json +18 -15
|
@@ -2,69 +2,74 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](legacy-compatibility.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
Last reviewed: 2026-
|
|
5
|
+
Last reviewed: 2026-11-06. This inventory and its Chinese counterpart maintain the same stable IDs, version facts, implementation locations, tests and retirement conditions. Update both languages together. The matrices are lookup views; the entries define maintenance decisions. Use complete DSH version numbers instead of release-order descriptions or abbreviated version names.
|
|
6
6
|
|
|
7
7
|
Current maintenance dates and commitments are in the [support policy](support-policy.md). Historical [DSH → plugin](support-history.md#by-dsh) and [plugin → DSH](support-history.md#by-plugin) distinguish declarations, reports, planned releases and distribution.
|
|
8
8
|
|
|
9
9
|
## Current release scope
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Plugin `0.3.5` is prepared for release and declares DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3`, `0.2.2-rc.1`. Admission remains `>=0.2.1-alpha.3` with prereleases and no upper bound. The development default and recommended host are `0.2.2-rc.1` (upstream RC prerelease); publication requires final same-archive acceptance. Published `0.3.4` retains its nine declarations including `0.2.2-alpha.3`, without `0.2.2-rc.1`; `0.3.5` availability is confirmed by the release workflow and npm registry. The legacy announcement for `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` stays 2026-10-28, 14 days, eligible from 2026-11-11 (Asia/Shanghai); dates never end support. Historical retirements and last plugin `0.2.0` remain below.
|
|
12
12
|
|
|
13
|
-
Exclusive HOST/PROTOCOL
|
|
13
|
+
Exclusive HOST/PROTOCOL, PUBLIC option/text, THEME radius/thumb and TEST direct-navigation paths remain retired from `0.3.1`; shared native/security checks remain. ACCOUNT/HMR and generic onboarding retries retain nonempty supported intersections. RESOURCE/LIVESHARE apply to exact `0.2.2-alpha.2`, `0.2.2-alpha.3` and `0.2.2-rc.1`. DSH-SETTINGS-ICON-001 adds native navigation for `0.2.2-alpha.3` and `0.2.2-rc.1`; all other exact defaults are listed below. Final same-archive reports stay outside npm and never inherit an old archive's success.
|
|
14
|
+
|
|
15
|
+
The applicability columns retain historical exact hosts, including retired `0.2.2-alpha.2`; current support is the ten-version set above. Its 2026-11-05 retirement is an explicit zero-day upstream-failure exception in `0.3.4`, last historical plugin `0.3.3`. See the [support policy](support-policy.md#upstream-failure-exception). RESOURCE/LIVESHARE now intersect support at `0.2.2-alpha.3` and `0.2.2-rc.1`; their private boundaries remain necessary.
|
|
14
16
|
|
|
15
17
|
## Scope and review rules
|
|
16
18
|
|
|
17
|
-
The current
|
|
19
|
+
The current ten exact declarations are listed above. DSH `0.2.2-alpha.2`, `0.2.2-alpha.3` and `0.2.2-rc.1` require Node `>=24.9.0`; the plugin engine stays `>=24` with no added minor-version gate. Forward admission with prereleases still requires identity/API checks; unknown versions inherit no verification. The account adapter also requires capabilities and live `manualAccountLogin`.
|
|
18
20
|
|
|
19
21
|
- Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
|
|
20
22
|
- `dsh-runtime`: retain an adaptation while its applicable versions intersect the supported set. When the intersection becomes empty, remove exclusive implementation and tests and update both languages, matrices, entries and guides in the same change. Keep shared security checks.
|
|
21
|
-
- `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.3.
|
|
23
|
+
- `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.3.5` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
|
|
22
24
|
- Missing exact-version evidence requires preserving implementation and recording the gap. Passing the same test on different releases does not prove identical implementation.
|
|
23
|
-
- Support or shared host-adapter changes require all
|
|
25
|
+
- Support or shared host-adapter changes require all ten CLI, complete browser and smoke targets on one final archive, retaining full account coverage. Ordinary selection follows development. Current full/releases independently verify adjacent retired `0.2.1-alpha.2`; the six-host one-time negative acceptance belongs to the `0.3.1` migration history and is not repeated here.
|
|
24
26
|
|
|
25
27
|
## Feature → version matrix
|
|
26
28
|
|
|
27
29
|
These rows identify adaptations or migrations and their exact applicable hosts. Historical native facts remain in each stable entry; retirement removes exclusive implementation, not shared security checks.
|
|
28
30
|
|
|
29
|
-
| Entry | Exact applicable DSH versions
|
|
30
|
-
| ------------------------------------------------------------- |
|
|
31
|
-
| [DSH-HOST-001](#dsh-host-001), old IPv4 schema/TLS rejection | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`
|
|
32
|
-
| [DSH-PROTOCOL-001](#dsh-protocol-001), HTTP/loopback bridge | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`
|
|
33
|
-
| [DSH-PUBLIC-001](#dsh-public-001), missing CLI option | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`
|
|
34
|
-
| [DSH-PUBLIC-001](#dsh-public-001), text projection | `0.2.1-alpha.1`, `0.2.1-alpha.2`
|
|
35
|
-
| [DSH-THEME-001](#dsh-theme-001), radius fallback | `0.1.7-rc.1`
|
|
36
|
-
| [DSH-THEME-001](#dsh-theme-001), switch-thumb fallback | `0.1.7-rc.1`, `0.1.7-rc.2`
|
|
37
|
-
| [DSH-THEME-001](#dsh-theme-001), focus-color migration | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` | Migrated using exact native rules and minimum/default UI evidence; visible keyboard focus retained
|
|
38
|
-
| [DSH-TEST-001](#dsh-test-001), direct Settings navigation | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`
|
|
39
|
-
| [DSH-ACCOUNT-001](#dsh-account-001), manual loopback callback | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` | Retained; no server-side old-version branch after global admission; exported helper still checks optional/invalid/older version inputs
|
|
40
|
-
| [DSH-HMR-001](#dsh-hmr-001), listener context isolation | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` | Retained for supported exact hosts; only retired matrix targets removed
|
|
41
|
-
| [DSH-RESOURCE-001](#dsh-resource-001) | `0.2.2-alpha.2` | Retain instance-private HTTP resource gate; native in-process peer reads unchanged |
|
|
42
|
-
| [DSH-LIVESHARE-001](#dsh-liveshare-001) | `0.2.2-alpha.2` | Public peer/baseline isolation and connection/request business Origin restoration; local native HTTPS/proxy Relay protocol round trips verified |
|
|
43
|
-
| [
|
|
44
|
-
| [PLUGIN-
|
|
45
|
-
| [PLUGIN-
|
|
31
|
+
| Entry | Exact applicable DSH versions | Current disposition |
|
|
32
|
+
| ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
33
|
+
| [DSH-HOST-001](#dsh-host-001), old IPv4 schema/TLS rejection | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` | No support intersection; exclusive implementation/tests removed in `0.3.1`; native Config and concrete binding retained |
|
|
34
|
+
| [DSH-PROTOCOL-001](#dsh-protocol-001), HTTP/loopback bridge | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` | No support intersection; fallback removed; actual protocol, normalized authority and Secure separation retained |
|
|
35
|
+
| [DSH-PUBLIC-001](#dsh-public-001), missing CLI option | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2` | No support intersection; missing-option and loopback projection paths removed |
|
|
36
|
+
| [DSH-PUBLIC-001](#dsh-public-001), text projection | `0.2.1-alpha.1`, `0.2.1-alpha.2` | No support intersection; text selection removed; context and environment checked, sections still observed for leaks/duplicates |
|
|
37
|
+
| [DSH-THEME-001](#dsh-theme-001), radius fallback | `0.1.7-rc.1` | No support intersection; old radius fallbacks removed; native themes/visual checks retained |
|
|
38
|
+
| [DSH-THEME-001](#dsh-theme-001), switch-thumb fallback | `0.1.7-rc.1`, `0.1.7-rc.2` | No support intersection; fallbacks removed in `0.3.1`; native tokens and visual/focus checks retained |
|
|
39
|
+
| [DSH-THEME-001](#dsh-theme-001), focus-color migration | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` | Migrated using exact native rules and minimum/default UI evidence; visible keyboard focus retained |
|
|
40
|
+
| [DSH-TEST-001](#dsh-test-001), direct Settings navigation | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2` | No support intersection; direct entry removed in `0.3.1`; account-menu navigation and generic asynchronous retries retained |
|
|
41
|
+
| [DSH-ACCOUNT-001](#dsh-account-001), manual loopback callback | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` | Retained; no server-side old-version branch after global admission; exported helper still checks optional/invalid/older version inputs |
|
|
42
|
+
| [DSH-HMR-001](#dsh-hmr-001), listener context isolation | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` | Retained for supported exact hosts; only retired matrix targets removed |
|
|
43
|
+
| [DSH-RESOURCE-001](#dsh-resource-001) | `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` | Retain instance-private HTTP resource gate; native in-process peer reads unchanged; current support intersection `0.2.2-alpha.3`, `0.2.2-rc.1`, retain implementation/security tests |
|
|
44
|
+
| [DSH-LIVESHARE-001](#dsh-liveshare-001) | `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` | Public peer/baseline isolation and connection/request business Origin restoration; local native HTTPS/proxy Relay protocol round trips verified; current support intersection `0.2.2-alpha.3`, `0.2.2-rc.1`, retain implementation/security tests |
|
|
45
|
+
| [DSH-SETTINGS-ICON-001](#dsh-settings-icon-001) | `0.2.2-alpha.3`, `0.2.2-rc.1` | Native optional icon slot; exact default policy in the entry |
|
|
46
|
+
| [PLUGIN-CONFIG-001](#plugin-config-001) | Plugin `0.1.5` allowedOrigins input, independent of DSH versions | Retained under its own contract |
|
|
47
|
+
| [PLUGIN-LOCALE-001](#plugin-locale-001) | Plugin `0.3.2`; independent of DSH versions | New memory contract; old key ignored/retained/not migrated |
|
|
48
|
+
| [PLUGIN-CLI-001](#plugin-cli-001) | Plugin `0.3.2`; independent of DSH versions | Fixed English; earlier --lang ended by plugin policy |
|
|
46
49
|
|
|
47
50
|
## Version → feature matrix
|
|
48
51
|
|
|
49
52
|
Historical rows stay searchable; a retired row is not a current positive target. All supported rows use native concrete IPv4/IPv6, HTTP/HTTPS, context projection, native radius/thumb tokens and focus rules and account-menu Settings. Exact published code/API evidence is recorded below; final same-archive runtime evidence is separate.
|
|
50
53
|
|
|
51
|
-
| Exact DSH version | Current state
|
|
52
|
-
| ----------------- |
|
|
53
|
-
| `0.1.7-rc.1` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
54
|
-
| `0.1.7-rc.2` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
55
|
-
| `0.2.0-rc.1` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
56
|
-
| `0.2.0-rc.2` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
57
|
-
| `0.2.1-alpha.1` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
58
|
-
| `0.2.1-alpha.2` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
59
|
-
| `0.2.1-alpha.3` | Legacy; minimum supported
|
|
60
|
-
| `0.2.1-alpha.4` | Legacy
|
|
61
|
-
| `0.2.1-alpha.5` | Legacy
|
|
62
|
-
| `0.2.1-rc.1` | Supported
|
|
63
|
-
| `0.2.1-rc.2` | Supported
|
|
64
|
-
| `0.2.1-rc.3` | Supported
|
|
65
|
-
| `0.2.1-rc.4` | Supported
|
|
66
|
-
| `0.2.1-rc.5` | Supported
|
|
67
|
-
| `0.2.2-alpha.2` |
|
|
54
|
+
| Exact DSH version | Current state | Historical adaptations / retained shared checks |
|
|
55
|
+
| ----------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
56
|
+
| `0.1.7-rc.1` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-THEME-001, DSH-TEST-001, DSH-HMR-001; historical locale-string startSignIn argument |
|
|
57
|
+
| `0.1.7-rc.2` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-THEME-001, DSH-TEST-001, DSH-HMR-001; metadata-object startSignIn argument |
|
|
58
|
+
| `0.2.0-rc.1` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
|
|
59
|
+
| `0.2.0-rc.2` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
|
|
60
|
+
| `0.2.1-alpha.1` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001; native public URL text |
|
|
61
|
+
| `0.2.1-alpha.2` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001; native transport and public URL text |
|
|
62
|
+
| `0.2.1-alpha.3` | Legacy; minimum supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation, context/env and general onboarding regressions retained; missing native release metadata; DSH-SETTINGS-ICON-001: host default |
|
|
63
|
+
| `0.2.1-alpha.4` | Legacy | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings and real host-release prompt regression retained; DSH-SETTINGS-ICON-001: host default |
|
|
64
|
+
| `0.2.1-alpha.5` | Legacy | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings and real host-release prompt regression retained; DSH-SETTINGS-ICON-001: host default |
|
|
65
|
+
| `0.2.1-rc.1` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings and real host-release prompt regression retained; DSH-SETTINGS-ICON-001: host default |
|
|
66
|
+
| `0.2.1-rc.2` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings, host-release and Search/Fetch regression retained; DSH-SETTINGS-ICON-001: host default |
|
|
67
|
+
| `0.2.1-rc.3` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings; real UI/Search/Fetch/host-release regression registered; final evidence separate; DSH-SETTINGS-ICON-001: host default |
|
|
68
|
+
| `0.2.1-rc.4` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings; real UI/Search/Fetch/host-release regression registered; final evidence separate; DSH-SETTINGS-ICON-001: host default |
|
|
69
|
+
| `0.2.1-rc.5` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings; real UI/Search/Fetch/host-release regression registered; final evidence separate; DSH-SETTINGS-ICON-001: host default |
|
|
70
|
+
| `0.2.2-alpha.2` | Retired in `0.3.4` (2026-11-05); last historical support `0.3.3` | DSH-RESOURCE-001, DSH-LIVESHARE-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-THEME-001; shared native validation/context/theme/Settings checks retained; final same-archive reports separate; DSH-SETTINGS-ICON-001: host default |
|
|
71
|
+
| `0.2.2-alpha.3` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-RESOURCE-001, DSH-LIVESHARE-001, DSH-SETTINGS-ICON-001 native shield; shared native/security checks retained |
|
|
72
|
+
| `0.2.2-rc.1` | Supported; development default and recommended RC prerelease host | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-RESOURCE-001, DSH-LIVESHARE-001, DSH-SETTINGS-ICON-001 native shield; shared native/security checks retained |
|
|
68
73
|
|
|
69
74
|
PLUGIN-CONFIG-001, PLUGIN-LOCALE-001, PLUGIN-CLI-001 and shared authentication checks are independent of runtime retirements and apply across the current plugin's hosts. Forward admission does not establish exact verification.
|
|
70
75
|
|
|
@@ -83,7 +88,7 @@ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Exclusive adapt
|
|
|
83
88
|
| Field | Maintenance basis |
|
|
84
89
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
85
90
|
| Adapted versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2` and `0.2.1-alpha.1` expose only `127.0.0.1` and `0.0.0.0` in native schema. The plugin validates concrete IPv4 itself and rejects wildcards, IPv6 and TLS |
|
|
86
|
-
| Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
91
|
+
| Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
|
|
87
92
|
| Implementation and upstream | `src/config.ts`, `src/adapters/dsh/runtime-capabilities.ts`, `src/adapters/dsh/webserver.ts`; Config/listener in exact `@deepseek-ai/dsh-host-webserver/lib/index.js`. Unified `resolveStartupConfig` replaced the transitional resolver |
|
|
88
93
|
| Tests and evidence | `tests/unit/config.test.ts`, `tests/integration/dsh-adapter.test.ts`, `tests/integration/native-transport.test.ts`, `tests/browser/native-transport.spec.ts`. The 2026-10-10 `0.2.1-alpha.2` checks covered IPv4, IPv6, mapped/scoped loopback and non-loopback IPv4. No bindable non-loopback IPv6 interface was available; only schema/policy was inspected for that case |
|
|
89
94
|
| Migration and retirement | Remove exclusive IPv4/schema branches and rejection tests only when all adapted versions leave support, or each has evidence of native support and a completed migration. Keep wildcard rejection, port validation, package identity and shared gate checks |
|
|
@@ -97,7 +102,7 @@ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`.
|
|
|
97
102
|
| Field | Maintenance basis |
|
|
98
103
|
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
99
104
|
| Fallback versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2` and `0.2.1-alpha.1` have no native TLS/protocol API, and Connection cannot recognize a concrete non-loopback bind. Keep the server-side HTTP / `127.0.0.1` bridge while the real listener and plugin public URL use concrete IPv4 |
|
|
100
|
-
| Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
105
|
+
| Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` use the actual protocol and normalized bind authority. IPv6 zones must not enter portable public URLs; mapped IPv6 must match Connection's WHATWG comparison |
|
|
101
106
|
| Implementation and upstream | `listenerProtocol`/`listenerTransport` in `runtime-capabilities.ts`, `src/adapters/dsh/{readiness,browser-auth,startup-urls}.ts`, `src/http/gate.ts`, `src/index.ts`, [cordis.patch.yml](../cordis.patch.yml). `connectionTrustedHosts` combines final nativeAuthority, public authorities needed by preserved paths and explicit CLI trust without expanding outer origin admission |
|
|
102
107
|
| Tests and evidence | `tests/integration/native-transport.test.ts`, `tests/browser/native-transport.spec.ts`, `tests/browser/proxy-chain.spec.ts`. On 2026-10-10, actual `0.1.7-rc.1` and `0.2.1-alpha.1` non-loopback packages demonstrated the need for the loopback bridge; `0.2.1-alpha.2` verified HTTPS/IPv6 MFA, Host settings, CLI revocation and mapped IPv6 HTTP/HTTPS |
|
|
103
108
|
| Migration and retirement | Migrate each fallback version only after native protocol/authority evidence. Remove its exclusive fallback when that complete applicable set no longer intersects support. Keep positive HTTP, both proxy directions, Cookie Secure, stream revocation and shared authentication checks |
|
|
@@ -110,14 +115,14 @@ Outer Cookie Secure follows the public origin; native Cookie Secure follows the
|
|
|
110
115
|
|
|
111
116
|
Public URL projection and model prompt location differences. Type: `dsh-runtime`. Exclusive adaptation retired in plugin `0.3.1`; shared native validation remains.
|
|
112
117
|
|
|
113
|
-
| Field | Maintenance basis
|
|
114
|
-
| ---------------------------------- |
|
|
115
|
-
| Versions without the native option | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1` and `0.2.0-rc.2` have no `--public-url`. Preserve native model Web text and `DSH_WEB_URL`: fixed `127.0.0.1` plus actual port without a trailing slash. The plugin's own single public entry remains configurable; do not describe it as a native CLI capability
|
|
116
|
-
| Native text projection versions | `0.2.1-alpha.1` and `0.2.1-alpha.2` consume `webServer.publicUrl` natively; model system-prompt Web text and `DSH_WEB_URL` use the plugin's final public root
|
|
117
|
-
| Native context projection versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
118
|
-
| Implementation and upstream | [cordis.patch.yml](../cordis.patch.yml), `src/adapters/dsh/startup-urls.ts`; exact WebApp `lib/startup.js`, `lib/index.js` and `harness-dev-context`. Connection must depend on webStartup/webServer instead of waiting for removed webRuntime
|
|
119
|
-
| Tests and evidence | `tests/browser/deployment-profile.spec.ts`, `tests/browser/startup-compatibility.spec.ts`, `tests/fixtures/startup-observer.mjs`; real `systemPrompt.assemble` and `shellEnv.collect` verify text versus context location, environment output and absence of tokens per exact version. Installed packages inspected on 2026-10-09 established the missing-option set and `0.2.1-alpha.1` boundary; 2026-10-15 review established the `0.2.1-alpha.3` context change
|
|
120
|
-
| Migration and retirement | Remove missing-option branches and CLI rejection tests when their applicable set leaves support. Keep text-location assertions while `0.2.1-alpha.1` or `0.2.1-alpha.2` remains supported and context assertions for `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
118
|
+
| Field | Maintenance basis |
|
|
119
|
+
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
120
|
+
| Versions without the native option | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1` and `0.2.0-rc.2` have no `--public-url`. Preserve native model Web text and `DSH_WEB_URL`: fixed `127.0.0.1` plus actual port without a trailing slash. The plugin's own single public entry remains configurable; do not describe it as a native CLI capability |
|
|
121
|
+
| Native text projection versions | `0.2.1-alpha.1` and `0.2.1-alpha.2` consume `webServer.publicUrl` natively; model system-prompt Web text and `DSH_WEB_URL` use the plugin's final public root |
|
|
122
|
+
| Native context projection versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` publish the model address through `webApp.getAdvertisedUrl()` and harness-dev-context's `app:web-surface`, in `assembly.contexts`; `DSH_WEB_URL` still uses the final public root |
|
|
123
|
+
| Implementation and upstream | [cordis.patch.yml](../cordis.patch.yml), `src/adapters/dsh/startup-urls.ts`; exact WebApp `lib/startup.js`, `lib/index.js` and `harness-dev-context`. Connection must depend on webStartup/webServer instead of waiting for removed webRuntime |
|
|
124
|
+
| Tests and evidence | `tests/browser/deployment-profile.spec.ts`, `tests/browser/startup-compatibility.spec.ts`, `tests/fixtures/startup-observer.mjs`; real `systemPrompt.assemble` and `shellEnv.collect` verify text versus context location, environment output and absence of tokens per exact version. Installed packages inspected on 2026-10-09 established the missing-option set and `0.2.1-alpha.1` boundary; 2026-10-15 review established the `0.2.1-alpha.3` context change |
|
|
125
|
+
| Migration and retirement | Remove missing-option branches and CLI rejection tests when their applicable set leaves support. Keep text-location assertions while `0.2.1-alpha.1` or `0.2.1-alpha.2` remains supported and context assertions for `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`. A new projection location does not change how another supported release must be observed |
|
|
121
126
|
|
|
122
127
|
2026-10-28 retirement evidence: the exact applicable legacy set above has no intersection with supported `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`. Exact installed Config/protocol/address APIs and matching new RC published lib trees were verified. Removed capability booleans, old schema/protocol/authority and public-option/text selection code and exclusive tests. Shared port/API/schema/identity/HTTP/TLS/IPv6/proxy/Secure/origin/revocation tests remain in the referenced files.
|
|
123
128
|
|
|
@@ -128,10 +133,10 @@ CSS fallback for missing theme tokens. Type: `dsh-runtime`. Retired in plugin `0
|
|
|
128
133
|
| Field | Maintenance basis |
|
|
129
134
|
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
130
135
|
| Fallback version | Historical `0.3.1` migration: Old radius-md/lg apply to `0.1.7-rc.1`, switch-thumb to `0.1.7-rc.1`, `0.1.7-rc.2`; duplicate focus-color fallback migrates using native rules on all seven |
|
|
131
|
-
| Native capability versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` each provide radius/thumb definitions and the same native focus rules; focus-ring-color is an optional override, not a guaranteed keyboard-mode root token. Historical radius is confirmed from `0.1.7-rc.2`, thumb from `0.2.0-rc.1`
|
|
136
|
+
| Native capability versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` each provide radius/thumb definitions and the same native focus rules; focus-ring-color is an optional override, not a guaranteed keyboard-mode root token. Historical radius is confirmed from `0.1.7-rc.2`, thumb from `0.2.0-rc.1` |
|
|
132
137
|
| Implementation and upstream | `src/client/settings/style.css` and `src/client/account/style.css` read native radius/thumb, set solid outline, `--dsw-focus-ring-width` and offset, and delegate color to host :focus-visible rules; standalone login keeps its own styles |
|
|
133
138
|
| Tests and evidence | `tests/browser/dsh-bootstrap.spec.ts`, `tests/browser/login.spec.ts`, `tests/browser/account-login.spec.ts` and manual screenshots under `.cache/ui-review/<version>`. Exact installed theme definitions on 2026-10-16 established the switch-thumb split for `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3` and `0.2.1-alpha.4`. Inspected `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` on 2026-10-09; `0.2.1-alpha.2` on 2026-10-10; `0.2.1-alpha.3` on 2026-10-15. Exact `0.2.1-alpha.5` theme definitions inspected on 2026-10-19 provide the same radius, focus and switch-thumb tokens. |
|
|
134
|
-
| Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all
|
|
139
|
+
| Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all ten supported targets has migrated to native rules without directly reading an undefined override. Keep live themes, layout, visible focus, switch appearance and shared visual tests |
|
|
135
140
|
|
|
136
141
|
2026-10-28 cleanup: the exact old radius, switch-thumb and direct Settings sets in the matrix have no support intersection; exclusive implementations are removed. The duplicate focus-color fallback migrates using seven-version native rules without assuming a normal-mode focus-ring-color. Generic onboarding/reopen/persistence retries and shared visual assertions remain.
|
|
137
142
|
|
|
@@ -141,13 +146,13 @@ Exact focus evidence correction (2026-10-28): all seven native focus.css rules r
|
|
|
141
146
|
|
|
142
147
|
Settings navigation and first-run test adaptations. Type: `dsh-runtime`. Direct entry retired in plugin `0.3.1`; general first-run retries retained, with exact notice/reload trigger applicability still incomplete.
|
|
143
148
|
|
|
144
|
-
| Field | Maintenance basis
|
|
145
|
-
| ------------------------ |
|
|
146
|
-
| Direct Settings versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` and `0.2.1-alpha.2` use sidebar Settings and API-key onboarding
|
|
147
|
-
| Account-menu version | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` use account menu → Settings and native account onboarding. The manual sign-in overlay adds no alternate Settings entry; generic asynchronous retries remain.
|
|
148
|
-
| Evidence gap | For `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
149
|
-
| Implementation and tests | `openDshSettings`, `completeApiKeyPrompt`, `clickThroughDshPrompts` and reopen in `tests/helpers/runtime.ts`; `tests/browser/dsh-bootstrap.spec.ts`, `tests/browser/dsh-gate.spec.ts`, `tests/browser/account-login.spec.ts`
|
|
150
|
-
| Migration and retirement | First establish exact applicability of each interaction through real UI evidence, then remove exclusive branches by support-set intersection. General async retries, persistence waits and browser fallbacks are not automatically exclusive to any DSH release
|
|
149
|
+
| Field | Maintenance basis |
|
|
150
|
+
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
151
|
+
| Direct Settings versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` and `0.2.1-alpha.2` use sidebar Settings and API-key onboarding |
|
|
152
|
+
| Account-menu version | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` use account menu → Settings and native account onboarding. The manual sign-in overlay adds no alternate Settings entry; generic asynchronous retries remain. |
|
|
153
|
+
| Evidence gap | For `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`, the per-trigger mapping of delayed notice, replacement during acknowledgement, first API-key save and page reload is incomplete. Shared helper success does not establish every trigger independently on each release |
|
|
154
|
+
| Implementation and tests | `openDshSettings`, `completeApiKeyPrompt`, `clickThroughDshPrompts` and reopen in `tests/helpers/runtime.ts`; `tests/browser/dsh-bootstrap.spec.ts`, `tests/browser/dsh-gate.spec.ts`, `tests/browser/account-login.spec.ts` |
|
|
155
|
+
| Migration and retirement | First establish exact applicability of each interaction through real UI evidence, then remove exclusive branches by support-set intersection. General async retries, persistence waits and browser fallbacks are not automatically exclusive to any DSH release |
|
|
151
156
|
|
|
152
157
|
Parallel `0.2.1-alpha.3` verification also exposed a fixture issue: shared pnpm hardlink ctime changes when another isolated profile installs the same package, triggering native HMR and client plugin disposal. Test installations now copy files, and the account fixture verifies that its client file has no shared hardlink. This is not evidence of a first-run onboarding reload and does not close the notice/reload applicability gap above.
|
|
153
158
|
|
|
@@ -163,14 +168,14 @@ Manual official-account callback handoff. Type: `dsh-runtime`. Active; an indepe
|
|
|
163
168
|
|
|
164
169
|
| Field | Maintenance basis |
|
|
165
170
|
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
166
|
-
| Native capability versus plugin scope | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` and `0.2.1-alpha.2` already ship account providers/APIs, but ui-settings-account `apply` returns immediately without `dshDesktop`. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
171
|
+
| Native capability versus plugin scope | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` and `0.2.1-alpha.2` already ship account providers/APIs, but ui-settings-account `apply` returns immediately without `dshDesktop`. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` enable that UI for plain Web. The plugin admits the adapter from `0.2.1-alpha.3` subject to capability and configuration checks; a disabled plugin adapter does not mean native account capability is absent |
|
|
167
172
|
| Admission rule | `>=0.2.1-alpha.3` with SemVer prereleases included, required provider/slot APIs and `manualAccountLogin: true`. The preference defaults to true and is a Loader-owned volatile reference; a profile override controls new authorizations without remounting authentication. |
|
|
168
173
|
| Historical disabled branch | The old six-version server branch is removed after global admission, with no old positive targets. The exported helper still rejects omitted/invalid/older inputs. Missing APIs remain unavailable; live false rejects new starts and preserves admitted attempts |
|
|
169
174
|
| Reason and upstream | Account-platform `protocol.ts/loginOrigin` in every exact installed release listed above accepts only loopback HTTP with an explicit port; ui-settings-account defaults to the browser origin. A public browser cannot automatically callback to the DSH machine, and the outer gate rejects cross-site navigation |
|
|
170
175
|
| Implementation | `src/shared/account-login.ts`, `src/http/account-login.ts`, `src/adapters/dsh/account-callback.ts`, `src/adapters/dsh/browser-capability.ts`, `src/client/account/`. Public slot entries/subscribe/priority APIs replace the sign-in action; independent `shell.overlay` renders instructions, input and buttons. Native `useApiKey` continues credential onboarding without calling `complete`; the account menu reopens the editor through `openOnboarding`. Inactive authorization offers this choice; active authorization retains cancellation. The server binds the initiating session and retains the native temporary callback handler, dispatched internally only from authenticated POST with a real in-memory Node response. It never fetches the pasted URL, reads private provider state or replaces native PKCE/credential storage. Dynamic configuration preserves the Loader reference. Callback capture blocks direct manual callbacks only while a manual attempt owns the handler; otherwise it delegates to the native handler through the existing outer gate. No preference change cancels an attempt or unloads the provider. The compact dialog shows two initial steps and hides completed instructions during authorization; API-key choice, failed-navigation guidance and expiry feedback remain available. Direct callback ownership is checked against the public provider view, so native cancellation followed by a new native authorization restores its callback even before a plugin state poll. Rejected cancellation retains ownership until the public view proves a terminal or different attempt, and permits cancellation cleanup to retry. `src/index.ts` attempts every shutdown resource in order before reporting cleanup errors, retaining the state lock until request and connection cleanup has been attempted. Configuration retries use the native mirror ensure API before its first accepted document and the explicitly injected remote.settings transport for a held namespace. Menu sign-in waits for an unknown preference to settle, then chooses manual or native routing from the latest accepted value. |
|
|
171
|
-
| Tests | `tests/integration/account-login.test.ts` uses the real `0.2.2-
|
|
176
|
+
| Tests | `tests/integration/account-login.test.ts` uses the real `0.2.2-rc.1` provider from pinned development dependencies and local Platform stand-in for PKCE, redirect URI, state, session, duplicate submission, cancellation, revocation, expiry and retries. Public cancellation fault injection verifies that a live manual callback remains blocked; shutdown failure regression checks listener and admin socket closure and reacquisition of the same profile lock. `tests/browser/account-login.spec.ts` covers credential-free onboarding with `DEEPSEEK_API_KEY` unset, native API-key save and menu reopening, instructions before authorization, pasted failed-navigation callbacks, blocked popups and responsive eight-language themes. `tests/unit/client-capability.test.ts` checks SemVer admission and rejects invalid/older versions. `tests/browser/live-config.spec.ts` and `tests/fixtures/live-config-observer.mjs` observe real Loader reference/fiber, listener, profile lock, long connections and restart persistence; final cross-version results belong to the execution record. Additional browser cases cover initial describe failure and full-mirror recovery, retry of a temporarily missing namespace through the injected transport, and delayed true/false preferences without premature native authorization. Plugin dictionaries do not expand old native language catalogs. |
|
|
172
177
|
| Public-callback migration | Platform must accept the public `redirect_uri`, and origin policy, callback, exchange, UI and session boundaries must be verified on the exact target DSH release. Platform acceptance alone does not remove DSH's `loginOrigin` restriction. Forward-admitted versions still need exact regression before being called verified; native public-flow migration requires exact evidence. |
|
|
173
|
-
| Retirement and preservation | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` still need loopback, so retain the adapter. Remove exclusive code only when the applicable set leaves support or each supported exact native public flow is verified. Keep shared state/PKCE, session ownership, one-time use, revocation and no URL forwarding
|
|
178
|
+
| Retirement and preservation | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` still need loopback, so retain the adapter. Remove exclusive code only when the applicable set leaves support or each supported exact native public flow is verified. Keep shared state/PKCE, session ownership, one-time use, revocation and no URL forwarding |
|
|
174
179
|
| Evidence limits | On 2026-10-15, full exchange passed with the actual provider and local Platform stand-in. Official `auth_init` accepted a loopback control, which was cancelled, and rejected three `example.com` public forms at schema validation. A full real official-account authorization was not verified; a domain allowlist has not been ruled out |
|
|
175
180
|
|
|
176
181
|
2026-10-28: all seven admitted exact hosts use the metadata-object native call. The post-admission server no longer disables its provider or bridge for old versions; capability checks and dynamic preference semantics remain. The separately exported index-injection helper still rejects omitted, invalid and older version inputs without granting the manual flag. `tests/unit/client-capability.test.ts` checks both boundaries.
|
|
@@ -183,19 +188,21 @@ Long-lived listener transaction-context isolation after native hot reload. Type:
|
|
|
183
188
|
|
|
184
189
|
| Field | Maintenance basis |
|
|
185
190
|
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
186
|
-
| Adapted versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`
|
|
191
|
+
| Adapted versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` |
|
|
187
192
|
| Native behavior and static evidence | Individually inspected exact `@deepseek-ai/dsh-hmr/lib/index.js` on 2026-10-16: `runExclusive` implementations for `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3` and `0.2.1-alpha.4` reject nesting through a private `executing: AsyncLocalStorage` boolean marker. Native `watchConfig` itself creates long-lived watchers with `executing.exit`. HTTP/HTTPS listeners created inside a reload transaction pass the stale marker to later independent requests. Exact `0.2.1-alpha.5` JavaScript and types were rechecked on 2026-10-19 and are byte-identical to `0.2.1-alpha.4`; no public listener-isolation API was added. Exact published `0.2.2-alpha.2` still uses private `executing: AsyncLocalStorage` with a true marker and runExclusive nesting rejection, with no public listener-isolation API; method names do not prove future semantics. |
|
|
188
193
|
| Implementation boundary | `src/adapters/dsh/hmr-context.ts`, `src/index.ts`: only during native listener initialization, call `exit` after checking `runExclusive`, native AsyncLocalStorage identity and a current true marker. This explicitly depends on a private field shape; there is no equivalent public API. An absent shape or marker retains native initialization. Do not replace the HMR queue or exit transactions in Settings saves/request dispatch; genuine nested calls remain rejected. |
|
|
189
194
|
| Tests and evidence | `tests/browser/account-login.spec.ts`, `tests/fixtures/hmr-config-probe.mjs`. On `0.2.1-alpha.3`, changing installed code and letting native profile watching replace it reproduced and fixed the reported settings/rejected “HMR transactions cannot be nested”. Real configuration-HMR/queue regressions passed for `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3` and `0.2.1-alpha.4`: listener generation increased, independent saves waited for an existing transaction, genuine nesting remained rejected and the original session stayed valid. Installed-code replacement followed by re-enabling also passed on `0.2.1-alpha.3` and `0.2.1-alpha.4`. The 2026-10-16 targeted run passed 10/10. Future releases do not inherit these exact-version conclusions. Current module-replacement regression also targets `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3` and `0.2.1-rc.4`, `0.2.1-rc.5`; exact commands, counts and final-artifact results are recorded separately. On `0.2.2-alpha.2`, `tests/fixtures/hmr-lifecycle-probe.mjs` and the browser fault case observe import failure retaining the same instance; failure after genuine initialization disposes old/failed instances and native rollback creates a new fiber using the old implementation. Subsequent successful replacement, first Settings write, real mux closure, lock release/reacquisition and persisted authentication are covered. Final same-archive reports are separate. |
|
|
190
195
|
| Migration and retirement | Prefer a public upstream isolation API after exact-version evidence and migration. Remove exclusive implementation/tests only when native isolation is fixed on every remaining supported adapted release, or when the adapted and supported sets no longer intersect. Update both languages and matrix directions together. Keep authentication, origin checks, the native queue, genuine nesting rejection and regression coverage. |
|
|
191
196
|
|
|
197
|
+
2026-11-03 exact review: DSH `0.2.2-alpha.3` HMR retains `executing: AsyncLocalStorage` and `runExclusive` nesting rejection; its whole lib tree is not identical to `0.2.2-alpha.2`. Loader now retains a registry wrapper; canonical identity is `entry.fiber.ctx.fiber`. Cordis `4.0.6-alpha.2` keeps raw input in `config` and the runtime object in `effectiveConfig`. `tests/fixtures/live-config-observer.mjs` requires ACTIVE and a `.get()` reference, falls back to old `config` only when the accessor is absent, and compares the same fiber/reference/auth/store/listener/lock. Production `src/config.ts`/`src/index.ts` retain the constructor's Volatile. Both `0.2.2-alpha.2` and `0.2.2-alpha.3` register the genuine HMR failure/cleanup/rollback case; final artifact evidence remains separate.
|
|
198
|
+
|
|
192
199
|
## DSH-RESOURCE-001
|
|
193
200
|
|
|
194
201
|
Native HTTP resource admission. Type: `dsh-runtime`. Introduced in plugin `0.3.2`.
|
|
195
202
|
|
|
196
203
|
| Field | Maintenance basis |
|
|
197
204
|
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
198
|
-
| Exact adapted versions | `0.2.2-alpha.2`;
|
|
205
|
+
| Exact adapted versions | `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`; current support intersection is `0.2.2-alpha.3`, `0.2.2-rc.1`, so retain. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5` retain handler registration admission. |
|
|
199
206
|
| Native shape and order | Exact published `@deepseek-ai/dsh-host-webserver@0.2.2-alpha.2`, `lib/index.js` lines 427–440, 456–471, 599–628; source tag `dsh-v0.2.2-alpha.2` (`f3803c96974ad4a94195fb97e5c637e9c2a3afe3`). Named and fallback resources dispatch before handlers. Private `serveResource(req, res, target, resource)` converts Node headers to Fetch Headers and owns the native response bridge. The constructor installs the wrapper before listener initialization or resource registration. Method existence alone does not establish future semantics. |
|
|
200
207
|
| Implementation | `src/adapters/dsh/webserver.ts`: capture the native function on one instance and preserve `this`; run the gate before conversion, rebuild target from the admitted `req.url` after root-token removal, then delegate. Do not modify the prototype, copy routing/stream code, wrap a resource as a handler, fabricate owner identity or gate `readResource(request, peer)`. Handler and upgrade gates remain. |
|
|
201
208
|
| Failure and lifecycle | Missing `serveResource` when resource reading exists, an un-installable private wrapper, or resource registration without an installed boundary fails activation/registration with a concrete API error. DenyGate and readiness remain fail closed. `AuthConnections` tracks the original Node response, including pending Response and backpressure; native abort/body cancellation remains responsible for IO. No version upper bound or unknown-version rejection is added. |
|
|
@@ -204,6 +211,8 @@ Native HTTP resource admission. Type: `dsh-runtime`. Introduced in plugin `0.3.2
|
|
|
204
211
|
|
|
205
212
|
2026-10-28 candidate intersection review: DSH-HOST-001, DSH-PROTOCOL-001, the retired paths in DSH-PUBLIC-001/DSH-THEME-001/DSH-TEST-001 remain retired with unchanged exact historical sets; no adaptation is retired again. DSH-ACCOUNT-001 and DSH-HMR-001 remain required on `0.2.2-alpha.2` as confirmed by its exact published loopback/AsyncLocalStorage code, as well as `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`. PLUGIN-CONFIG-001 remains under its own policy. No historical evidence gaps are closed by this admission.
|
|
206
213
|
|
|
214
|
+
2026-11-03 extension: exact `@deepseek-ai/dsh-host-webserver@0.2.2-alpha.3` has the same complete lib tree as `@deepseek-ai/dsh-host-webserver@0.2.2-alpha.2`, including the named/fallback dispatch and private `serveResource` boundary above. New source identity is tag `dsh-v0.2.2-alpha.3`, commit `05b1cae8db6e674c5685101494d4eec24652424a`. The supported applicability intersection is exactly `0.2.2-alpha.2`, `0.2.2-alpha.3`; retain the instance-private gate and shared security tests. Both exact hosts register resource caching and four ingress/compression mux cases, without treating static equality as final runtime acceptance.
|
|
215
|
+
|
|
207
216
|
## DSH-LIVESHARE-001
|
|
208
217
|
|
|
209
218
|
Public peer admission and owner-login business Origin. Type: `dsh-runtime`. Introduced in plugin `0.3.2` for exact DSH `0.2.2-alpha.2`.
|
|
@@ -214,15 +223,29 @@ Public peer admission and owner-login business Origin. Type: `dsh-runtime`. Intr
|
|
|
214
223
|
| Origin ordering | Exact published Connection admits internal Host/Cookie before the public `connection/request` waterfall. `src/adapters/dsh/liveshare.ts`, installed once per server fiber in `src/index.ts`, restores only the validated outer Origin from `requireRequestContext` while awaiting next for POST `/api/liveshare.ownerLoginStart` and POST `/api/liveshare.ownerLoginRedeem`. Finally restores the previous header on success, rejection or cancellation. Missing Origin is left missing; missing trusted context rejects. Similar paths, subpaths, other methods, Cancel and ownerCredential are untouched. |
|
|
215
224
|
| Retained security and lifecycle | Outer raw-header/origin/session gate, native admit, native Cookie authority, readiness, trustedHosts and preserveOriginPaths remain. Do not use an owner peer instead of HTTP authentication or bind share lifetime to a plugin session. Activation never enables LiveShare or changes production Relay configuration. |
|
|
216
225
|
| Tests and limits | `tests/unit/client-capability.test.ts`, `tests/browser/liveshare.spec.ts`, `tests/fixtures/liveshare-viewer.mjs` and `liveshare-client-observer.js` establish real native viewer carrier/index and full-client isolation. `tests/integration/liveshare-origin.test.ts` checks public waterfall header restoration, strict selection and fiber disposal/reload with real Node request objects; `tests/helpers/liveshare-relay.ts` and `tests/fixtures/liveshare-session.mjs` provide the local protocol/probe without replacing Host services. Local Relay protocol runs cover native HTTPS and HTTPS→HTTP ingress, actual Start/Redeem state/PKCE/cancel/retry, the native worker, create/list/stop, real viewer index/assets/carrier and accepted native viewer channel operations. Anonymous/revoked/bad/missing/duplicate-Origin and cross-site requests remain rejected by the outer gate; logout does not stop a share. The fixture replaces only Relay consent/identity/transport and uses the real plain-Node Host to serialize the shipped carrier. No real Relay/OAuth/product experience, real visitor model operation or file writing is established. |
|
|
217
|
-
| Migration and retirement | Retain while supported `0.2.2-alpha.2` requires these boundaries. Prefer a native public business-Origin contract after exact evidence and migration; retire exclusive implementation/tests only when every supported applicable host has migrated or the support intersection is empty. Keep shared admission, owner/viewer identity and lifecycle tests.
|
|
226
|
+
| Migration and retirement | Retain while supported `0.2.2-alpha.2` or `0.2.2-alpha.3`, `0.2.2-rc.1` requires these boundaries. Prefer a native public business-Origin contract after exact evidence and migration; retire exclusive implementation/tests only when every supported applicable host has migrated or the support intersection is empty. Keep shared admission, owner/viewer identity and lifecycle tests. |
|
|
227
|
+
|
|
228
|
+
2026-11-03 extension: exact Connection, account, account-platform, authorization and LiveShare protocol lib trees are byte-identical between `0.2.2-alpha.2` and `0.2.2-alpha.3`; both still require the boundaries above. The `0.2.2-alpha.3` LiveShare implementation itself changed, so no whole-package identity is claimed. Its published experimental bundle is in `OPTIONAL_BUNDLES`, has `listedByDefault: false`, and the factory Web profile does not enable it. Keep the necessary local-protocol regression and viewer isolation; never enable it automatically or claim production Relay/OAuth, real visitor model calls or file writes.
|
|
229
|
+
|
|
230
|
+
## DSH-SETTINGS-ICON-001
|
|
231
|
+
|
|
232
|
+
Optional native Security & sign-in navigation icon. Type: `dsh-runtime`. Introduced in plugin `0.3.4`; retained while its supported applicability intersection is nonempty.
|
|
233
|
+
|
|
234
|
+
| Field | Maintenance basis |
|
|
235
|
+
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
236
|
+
| Native-icon applicability | Exact DSH `0.2.2-alpha.3`, `0.2.2-rc.1` declare `settings.section.icon`, matched by the `settings.section` id `security`. |
|
|
237
|
+
| Default-icon policy | Exact DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` have no declaration and retain the host default. All eleven exact primitives packages export `IconShieldOutlineMedium`. |
|
|
238
|
+
| Implementation and lifecycle | `src/client/index.ts`, `package.json` client module dependencies, `scripts/build.mjs`/`check-package.mjs`. Register only after the administrator guard, using native `slots.inject`/`register` and `IconShieldOutlineMedium` with the slot's size. `currentColor`, selected state, labels and decorative accessibility containers belong to the host. Missing declarations wait without a contribution; declaration withdrawal disposes it, recreation registers once, and client unload removes it. DSH modules/React remain external; no service, DOM or icon replacement is introduced. |
|
|
239
|
+
| Tests and exact evidence | `tests/browser/settings-icon.spec.ts` registers on all ten targets; `tests/fixtures/settings-icon-observer.js` retains real native factories/facades/disposers only in tests. It checks native module/element identity, light/dark desktop/narrow selected/idle states, contribution-only release restoring the default with the section retained, genuine settings-general disposal/recreation twice, deduplication, client unload and viewer early exit. `tests/browser/liveshare.spec.ts` additionally checks real viewer carriers. Exact tag/commit above, Settings contract and ui-renderer declaration-epoch lifecycle establish the API; screenshots and same-archive results remain unpackaged. |
|
|
240
|
+
| Retirement | Keep while supported exact `0.2.2-alpha.3`, `0.2.2-rc.1` needs this contribution. A future native replacement requires exact evidence and migration; an empty support intersection permits removing only exclusive contribution/import/tests and updating both inventories and matrix directions. Preserve the administrator boundary, host ownership and shared visual/security checks. |
|
|
218
241
|
|
|
219
242
|
## PLUGIN-CONFIG-001
|
|
220
243
|
|
|
221
|
-
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.
|
|
244
|
+
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.5`, independent of the DSH version set.
|
|
222
245
|
|
|
223
246
|
| Field | Maintenance basis |
|
|
224
247
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
225
|
-
| Configuration contract | A single-item or empty top-level `allowedOrigins` array from plugin `0.1.5`; plugin `0.1.6` introduced in-memory migration and plugins `0.3.1`, `0.3.2` and `0.3.
|
|
248
|
+
| Configuration contract | A single-item or empty top-level `allowedOrigins` array from plugin `0.1.5`; plugin `0.1.6` introduced in-memory migration and plugins `0.3.1`, `0.3.2`, `0.3.3`, `0.3.4` and `0.3.5` retain it |
|
|
226
249
|
| Behavior and implementation | `src/config.ts`, [cordis.patch.yml](../cordis.patch.yml). Omission differs from explicit empty input; a single entry becomes the sole `publicUrl`, while an empty array derives it from the bound listener. Multiple/duplicate entries and coexistence with the new field fail. Emit one deprecation warning per activation without rewriting the profile; use unified pre-start parsing and post-listen finalization |
|
|
227
250
|
| Tests | `tests/unit/config.test.ts`, `tests/unit/origin-policy.test.ts`, `tests/integration/http-gate.test.ts`, `tests/browser/startup-compatibility.spec.ts`; real Loader checks 0/1 entries, multiple/duplicate entries, null, file/CLI conflicts, warning count and unchanged profile |
|
|
228
251
|
| Migration and retirement | Remove exclusive detection, conversion and tests only after the plugin contract explicitly ends these inputs and provides migration guidance. Dropping any DSH release is insufficient. Keep single-URL validation and origin security regression |
|
|
@@ -245,9 +268,9 @@ Fixed-English CLI. Type: `plugin-contract`; plugin `0.3.2` explicitly ends its e
|
|
|
245
268
|
|
|
246
269
|
## Shared security boundaries
|
|
247
270
|
|
|
248
|
-
Remote profiles must independently disable native `webserver`. `tests/browser/startup-compatibility.spec.ts` covers Loader skip/plugin runtime rejection on
|
|
271
|
+
Remote profiles must independently disable native `webserver`. `tests/browser/startup-compatibility.spec.ts` covers Loader skip/plugin runtime rejection on ten hosts: a peer fault on minimum `0.2.1-alpha.3`, engines faults on the other nine. `scripts/verify-retired.mjs` uses separate old profiles for unmodified-candidate installation rollback and whole-package native peer skip, repeatedly requiring no TCP/HTTP/readiness/WebSocket listener while preserving upstream identity/auditing.
|
|
249
272
|
|
|
250
|
-
`src/shared/dsh-support.ts`
|
|
273
|
+
`src/shared/dsh-support.ts` reads current exact declarations `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3`, `0.2.2-rc.1` with explicit lifecycle records; the six historical retirements retain last plugin `0.2.0`, and `0.2.2-alpha.2` is retired in `0.3.4` on 2026-11-05 with last historical plugin `0.3.3`. Dates record preparation/decisions, not npm publication or timed refusal. Process/HMR warning deduplication and necessary API, identity and security checks remain. See the support policy for the zero-day upstream failure exception.
|
|
251
274
|
|
|
252
275
|
Package identity, API checks after forward admission, concrete binding, original Host/Origin/Fetch Metadata, loopback admission, passwords/TOTP, sessions, stream revocation, storage failure and CLI confirmation apply to all declared releases. HTTPS → HTTP reverse proxy support, Host settings capability `ownsHost` and server-side native browser authentication exchange must not be removed merely because an adaptation retires.
|
|
253
276
|
|
|
@@ -275,4 +298,26 @@ The 2026-10-30 `0.3.3` review adds exact DSH `0.2.1-rc.5`, tag `dsh-v0.2.1-rc.5`
|
|
|
275
298
|
|
|
276
299
|
Per-entry support-intersection review for `0.3.3`: DSH-HOST-001, DSH-PROTOCOL-001 and the retired DSH-PUBLIC-001/DSH-THEME-001/DSH-TEST-001 paths keep their exact historical applicability and retirement evidence. The native validation, context/theme and account-menu checks include `0.2.1-rc.5`; general asynchronous retries and the notice/reload evidence gap remain. DSH-ACCOUNT-001 still requires the loopback handoff on `0.2.1-rc.5`, and DSH-HMR-001 still requires the same executing/runExclusive isolation; both retain nonempty supported intersections. DSH-RESOURCE-001 and DSH-LIVESHARE-001 retain only `0.2.2-alpha.2` applicability. PLUGIN-CONFIG-001, PLUGIN-LOCALE-001 and PLUGIN-CLI-001 retain their independent contracts. No implementation or test is retired in this support addition.
|
|
277
300
|
|
|
278
|
-
The new exact regression target uses `tests/browser/account-login.spec.ts`, `live-config.spec.ts`, `startup-compatibility.spec.ts`, `web-search-settings.spec.ts` and `rc-navigation.spec.ts`, plus `host-release.spec.ts` for `0.2.1-rc.5` ↔ `0.2.1-rc.4`.
|
|
301
|
+
The new exact regression target uses `tests/browser/account-login.spec.ts`, `live-config.spec.ts`, `startup-compatibility.spec.ts`, `web-search-settings.spec.ts` and `rc-navigation.spec.ts`, plus `host-release.spec.ts` for `0.2.1-rc.5` ↔ `0.2.1-rc.4`. That historical `0.3.3` verification contract required nine exact CLI, complete-browser and smoke targets; it does not certify the current `0.3.4` archive or infer a surviving old-archive result.
|
|
302
|
+
|
|
303
|
+
2026-11-03 `0.3.4` admission review: exact DSH tag `dsh-v0.2.2-alpha.3` is `05b1cae8db6e674c5685101494d4eec24652424a`; published package identities/integrities and an isolated installed dependency chain were checked. WebApp, WebServer, Connection and account packages resolve to `0.2.2-alpha.3`, Cordis to `4.0.6-alpha.2`, Schemastery to `3.18.6-alpha.2`, Loader to `1.0.7-alpha.2`, Include to `1.0.11-alpha.2`. Earlier exact host compositions are not rewritten. Native `@deepseek-ai/dsh-client-ui-theme@0.2.2-alpha.3/lib/client.js` line 1473 retains the native focus fallback and transparent pointer override; SHA-256 is `78d79a77112e2a83cfa1a9015c06f4b980efb9e1b071bc0b2ba46525748c3592`. This is not equality of whole theme packages.
|
|
304
|
+
|
|
305
|
+
Per-entry review retains the historical empty intersections and retirement evidence for HOST/PROTOCOL and exclusive PUBLIC/THEME/TEST paths; shared native validation, context, focus and account-menu checks add exact `0.2.2-alpha.3`. The unresolved notice/reload trigger mapping remains a gap. ACCOUNT and HMR retain nonempty intersections and their loopback/transaction adaptations. RESOURCE/LIVESHARE now intersect exact `0.2.2-alpha.2`, `0.2.2-alpha.3`; SETTINGS-ICON intersects exact `0.2.2-alpha.3` and keeps the nine explicitly listed defaults. PLUGIN-CONFIG-001, PLUGIN-LOCALE-001 and PLUGIN-CLI-001 retain independent migration policies. No adaptation or shared security check is retired. Both matrices and entries were reviewed manually and with a local agent; no inventory generator or special CI gate is introduced. At the 2026-11-03 review, `0.3.4` was a local candidate: final ten-host CLI/browser/smoke and independent `0.2.1-alpha.2` refusal reports bind their own source/archive identity outside npm; local protocol stand-ins and unknown hosts inherit no broader claims.
|
|
306
|
+
|
|
307
|
+
2026-11-04 release preparation: current version descriptions now follow the formal publication workflow. The ten exact declarations, all thirteen inventory entries, applicable version intersections, legacy dates and independent plugin contracts remain unchanged. Actual availability is established by the release workflow and registry; earlier local-candidate reports do not certify the new release artifact. The tagged workflow must verify its newly produced archive on all ten hosts before publication.
|
|
308
|
+
|
|
309
|
+
## 2026-11-05 retirement review
|
|
310
|
+
|
|
311
|
+
The `0.3.4` release withdraws only exact DSH `0.2.2-alpha.2` after native-only reproduction of the incompatible `internal/update` callback in shipped `@deepseek-ai/dsh-app-boot@0.2.2-alpha.2` with Cordis `4.0.6-alpha.2`. Fresh resolution fails with `next is not a function`; the original Cordis `4.0.6-alpha.1` composition succeeds. The CI run `41807651546` / browser job `126499190719` is separate from the previously passing dependency composition. The earlier CI SDK versions are reconstructed from release-age cutoffs, not recovered old lockfiles. Plugin `0.3.3` and migration host `0.2.2-alpha.3` registry archives/integrities were rechecked on 2026-11-05. Historical plugin availability does not repair the native dependency mismatch.
|
|
312
|
+
|
|
313
|
+
Per-entry intersection review: DSH-HOST-001, DSH-PROTOCOL-001 and the exclusive DSH-PUBLIC-001/DSH-THEME-001/DSH-TEST-001 paths keep their established empty intersections and retirement evidence. Shared context, native theme/focus and account-menu checks remain across the current nine exact declarations. DSH-ACCOUNT-001 and DSH-HMR-001 retain that same nonempty supported intersection. DSH-RESOURCE-001 and DSH-LIVESHARE-001 retain exact supported `0.2.2-alpha.3`; DSH-SETTINGS-ICON-001 still retains exact `0.2.2-alpha.3`. PLUGIN-CONFIG-001, PLUGIN-LOCALE-001 and PLUGIN-CLI-001 remain independent. No exclusive production adaptation becomes removable; generic onboarding retries and their evidence gap remain.
|
|
314
|
+
|
|
315
|
+
`package.json`, `scripts/runtime.mjs`, `scripts/packed-artifact.mjs` and `scripts/verify-packed.mjs` remove the retired positive target. Browser registrations retain all remaining applicable cases; `tests/browser/host-release.spec.ts` now exercises `0.2.2-alpha.3` ↔ `0.2.1-rc.5`, avoiding the retired runtime. `src/shared/dsh-support.ts` and `tests/unit/dsh-support.test.ts` record/classify the retirement and warning. Technical admission and its security tests still include `0.2.2-alpha.2`; it is not added to the native peer-refusal set. Independent retired `0.2.1-alpha.2` refusal remains. New final-archive nine-host CLI/browser/smoke evidence is required; no old archive result transfers.
|
|
316
|
+
|
|
317
|
+
## 2026-11-06 RC admission review
|
|
318
|
+
|
|
319
|
+
Plugin `0.3.5` adds exact DSH `0.2.2-rc.1` while retaining all nine existing targets; this upstream RC prerelease is the development default and recommendation. Exact tag `dsh-v0.2.2-rc.1` is commit `66491b05e3f05ad35bcdd4f6cd7ed26041d9e3db`, compared with `dsh-v0.2.2-alpha.3` (`05b1cae8db6e674c5685101494d4eec24652424a`). The complete source diff changes only own versions in 387 manifests. Identity/integrity checks cover 24 exact npm package pairs and 48 archives: 954 lib files match across both releases, with regular-file differences only in manifests. Static identity does not establish final runtime success. The actual RC chain resolves WebApp, WebServer, Connection and account/account-platform to `0.2.2-rc.1`, Cordis to `4.1.0`, Schemastery to `3.19.0` and Loader/Include to `1.1.0`; earlier exact SDK facts remain unchanged.
|
|
320
|
+
|
|
321
|
+
Per-entry intersection decisions: DSH-HOST-001, DSH-PROTOCOL-001 and the exclusive historical DSH-PUBLIC-001/DSH-THEME-001/DSH-TEST-001 paths retain empty supported intersections and their retirement evidence. Shared native Config/protocol, context, theme/focus and account-menu validation adds `0.2.2-rc.1`. Generic onboarding retries and the notice/reload trigger-mapping gap remain. DSH-ACCOUNT-001 still needs loopback handoff on the RC; DSH-HMR-001 still needs executing/runExclusive transaction isolation. DSH-RESOURCE-001 and DSH-LIVESHARE-001 apply historically to exact `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`, intersecting current support at `0.2.2-alpha.3`, `0.2.2-rc.1`. DSH-SETTINGS-ICON-001 uses the native shield on `0.2.2-alpha.3`, `0.2.2-rc.1`; the eight supported defaults and historical `0.2.2-alpha.2` default remain. No exclusive production implementation becomes removable through this addition. PLUGIN-CONFIG-001, PLUGIN-LOCALE-001 and PLUGIN-CLI-001 retain independent contracts.
|
|
322
|
+
|
|
323
|
+
Code/test references remain in each entry. Exact RC branches extend `tests/browser/{native-transport,account-login,login,liveshare,settings-icon,web-search-settings,rc-navigation}.spec.ts`; `host-release.spec.ts` adds `0.2.2-rc.1` ↔ `0.2.2-alpha.3` while retaining `0.2.2-alpha.3` ↔ `0.2.1-rc.5`. The fixed-archive consumer requires full resource/mux/HMR/language/icon and both Owner LiveShare TAP names on both hosts and refuses zero Search/Fetch/navigation registration. Configuration observation still reads canonical fiber effectiveConfig; production Volatile is unchanged. Final ten-host same-archive CLI/browser/smoke, independent `0.2.1-alpha.2` refusal, source/archive identity and screenshots remain outside npm. Partial or historical success does not certify the final candidate. Real authorization, production Relay, non-loopback IPv6 and existing trigger-mapping gaps are not closed by an RC label.
|