dsh-auth-remote 0.3.2 → 0.3.3
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 +7 -1
- package/CHANGELOG.zh-CN.md +7 -1
- package/CONTRIBUTING.md +1 -1
- package/CONTRIBUTING.zh-CN.md +1 -1
- package/README.md +49 -52
- package/README.zh-CN.md +49 -52
- package/docs/deployment.md +23 -29
- package/docs/deployment.zh-CN.md +23 -29
- package/docs/development.md +27 -24
- package/docs/development.zh-CN.md +27 -24
- package/docs/legacy-compatibility.md +78 -71
- package/docs/legacy-compatibility.zh-CN.md +78 -71
- package/docs/releasing.md +10 -10
- package/docs/releasing.zh-CN.md +10 -10
- package/docs/support-history.md +49 -47
- package/docs/support-history.zh-CN.md +49 -47
- package/docs/support-policy.md +25 -7
- package/docs/support-policy.zh-CN.md +25 -7
- package/package.json +2 -1
|
@@ -2,68 +2,69 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](legacy-compatibility.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
Last reviewed: 2026-10-
|
|
5
|
+
Last reviewed: 2026-10-30. 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
|
-
Current
|
|
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
|
-
## Current
|
|
9
|
+
## Current release scope
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Planned plugin release `0.3.3` 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.2`. Technical admission is `>=0.2.1-alpha.3` including prereleases without an upper bound; the default/manual recommendation remains `0.2.2-alpha.2`. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` are legacy from 2026-10-28 with a 14-day window and eligibility from 2026-11-11 (Asia/Shanghai); dates do not end support. Published `0.3.2` retains its eight declarations. The six DSH retirements in `0.3.1`, their last supporting plugin `0.2.0` and all original evidence remain in the historical rows below.
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Exclusive HOST/PROTOCOL old paths, PUBLIC option/text paths, THEME radius/thumb fallbacks and TEST direct navigation retired in `0.3.1`; this work does not retire them again. Native focus rules and shared security checks cover the nine current exact targets. ACCOUNT, HMR, general onboarding retries and PLUGIN-CONFIG remain. RESOURCE and LIVESHARE, introduced in `0.3.2`, still apply only to exact DSH `0.2.2-alpha.2`. The new `0.2.1-rc.5` package/API evidence is below; final same-archive test reports remain outside the npm archive and do not inherit an old archive's success.
|
|
14
14
|
|
|
15
15
|
## Scope and review rules
|
|
16
16
|
|
|
17
|
-
The current
|
|
17
|
+
The current nine exact declarations are listed above. DSH `0.2.2-alpha.2` itself requires 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
18
|
|
|
19
19
|
- Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
|
|
20
20
|
- `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.
|
|
21
|
+
- `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.3.3` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
|
|
22
22
|
- 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
|
|
23
|
+
- Support or shared host-adapter changes require all nine 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
24
|
|
|
25
25
|
## Feature → version matrix
|
|
26
26
|
|
|
27
27
|
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
28
|
|
|
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.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.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.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`
|
|
42
|
-
| [DSH-LIVESHARE-001](#dsh-liveshare-001) | `0.2.2-alpha.2`
|
|
43
|
-
| [PLUGIN-CONFIG-001](#plugin-config-001) | Plugin `0.1.5` allowedOrigins input, independent of DSH versions
|
|
44
|
-
| [PLUGIN-LOCALE-001](#plugin-locale-001) | Plugin `0.3.2`; independent of DSH versions
|
|
45
|
-
| [PLUGIN-CLI-001](#plugin-cli-001) | Plugin `0.3.2`; independent of DSH versions
|
|
29
|
+
| Entry | Exact applicable DSH versions | Current disposition |
|
|
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` | No support intersection; exclusive implementation/tests removed in `0.3.1`; native Config and concrete binding retained |
|
|
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` | No support intersection; fallback removed; actual protocol, normalized authority and Secure separation retained |
|
|
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` | No support intersection; missing-option and loopback projection paths removed |
|
|
34
|
+
| [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 |
|
|
35
|
+
| [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 |
|
|
36
|
+
| [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 |
|
|
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` | No support intersection; direct entry removed in `0.3.1`; account-menu navigation and generic asynchronous retries retained |
|
|
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
|
+
| [PLUGIN-CONFIG-001](#plugin-config-001) | Plugin `0.1.5` allowedOrigins input, independent of DSH versions | Retained under its own contract |
|
|
44
|
+
| [PLUGIN-LOCALE-001](#plugin-locale-001) | Plugin `0.3.2`; independent of DSH versions | New memory contract; old key ignored/retained/not migrated |
|
|
45
|
+
| [PLUGIN-CLI-001](#plugin-cli-001) | Plugin `0.3.2`; independent of DSH versions | Fixed English; earlier --lang ended by plugin policy |
|
|
46
46
|
|
|
47
47
|
## Version → feature matrix
|
|
48
48
|
|
|
49
49
|
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
50
|
|
|
51
|
-
| Exact DSH version |
|
|
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.
|
|
51
|
+
| Exact DSH version | Current state | Historical adaptations / retained shared checks |
|
|
52
|
+
| ----------------- | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
53
|
+
| `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 |
|
|
54
|
+
| `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 |
|
|
55
|
+
| `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 |
|
|
56
|
+
| `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 |
|
|
57
|
+
| `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 |
|
|
58
|
+
| `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 |
|
|
59
|
+
| `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 |
|
|
60
|
+
| `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 |
|
|
61
|
+
| `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 |
|
|
62
|
+
| `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 |
|
|
63
|
+
| `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 |
|
|
64
|
+
| `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 |
|
|
65
|
+
| `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 |
|
|
66
|
+
| `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 |
|
|
67
|
+
| `0.2.2-alpha.2` | Supported; default/manual recommendation | 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 |
|
|
67
68
|
|
|
68
69
|
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.
|
|
69
70
|
|
|
@@ -82,7 +83,7 @@ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Exclusive adapt
|
|
|
82
83
|
| Field | Maintenance basis |
|
|
83
84
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
84
85
|
| 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 |
|
|
85
|
-
| 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` and `0.2.2-alpha.2` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden
|
|
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` and `0.2.2-alpha.2` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
|
|
86
87
|
| 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 |
|
|
87
88
|
| 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 |
|
|
88
89
|
| 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 |
|
|
@@ -96,7 +97,7 @@ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`.
|
|
|
96
97
|
| Field | Maintenance basis |
|
|
97
98
|
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
98
99
|
| 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 |
|
|
99
|
-
| 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` and `0.2.2-alpha.2` use the actual protocol and normalized bind authority. IPv6 zones must not enter portable public URLs; mapped IPv6 must match Connection's WHATWG comparison
|
|
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` and `0.2.2-alpha.2` use the actual protocol and normalized bind authority. IPv6 zones must not enter portable public URLs; mapped IPv6 must match Connection's WHATWG comparison |
|
|
100
101
|
| 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 |
|
|
101
102
|
| 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 |
|
|
102
103
|
| 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 |
|
|
@@ -113,10 +114,10 @@ Public URL projection and model prompt location differences. Type: `dsh-runtime`
|
|
|
113
114
|
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
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 |
|
|
115
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 |
|
|
116
|
-
| 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` and `0.2.2-alpha.2` 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
|
|
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` and `0.2.2-alpha.2` 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 |
|
|
117
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 |
|
|
118
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 |
|
|
119
|
-
| 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` and `0.2.2-alpha.2`. A new projection location does not change how another supported release must be observed
|
|
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` and `0.2.2-alpha.2`. A new projection location does not change how another supported release must be observed |
|
|
120
121
|
|
|
121
122
|
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.
|
|
122
123
|
|
|
@@ -127,10 +128,10 @@ CSS fallback for missing theme tokens. Type: `dsh-runtime`. Retired in plugin `0
|
|
|
127
128
|
| Field | Maintenance basis |
|
|
128
129
|
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
129
130
|
| 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 |
|
|
130
|
-
| 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.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`
|
|
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` |
|
|
131
132
|
| 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 |
|
|
132
133
|
| 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. |
|
|
133
|
-
| Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all
|
|
134
|
+
| Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all nine has migrated to native rules without directly reading an undefined override. Keep live themes, layout, visible focus, switch appearance and shared visual tests |
|
|
134
135
|
|
|
135
136
|
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.
|
|
136
137
|
|
|
@@ -140,13 +141,13 @@ Exact focus evidence correction (2026-10-28): all seven native focus.css rules r
|
|
|
140
141
|
|
|
141
142
|
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.
|
|
142
143
|
|
|
143
|
-
| Field | Maintenance basis
|
|
144
|
-
| ------------------------ |
|
|
145
|
-
| 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
|
|
146
|
-
| 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.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. |
|
|
147
|
-
| 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` and `0.2.2-alpha.2`, 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 |
|
|
148
|
-
| 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`
|
|
149
|
-
| 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
|
|
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` and `0.2.2-alpha.2`, 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 |
|
|
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 |
|
|
150
151
|
|
|
151
152
|
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.
|
|
152
153
|
|
|
@@ -162,14 +163,14 @@ Manual official-account callback handoff. Type: `dsh-runtime`. Active; an indepe
|
|
|
162
163
|
|
|
163
164
|
| Field | Maintenance basis |
|
|
164
165
|
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
165
|
-
| 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` and `0.2.2-alpha.2` 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
|
|
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` and `0.2.2-alpha.2` 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 |
|
|
166
167
|
| 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. |
|
|
167
168
|
| 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 |
|
|
168
169
|
| 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 |
|
|
169
170
|
| 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. |
|
|
170
171
|
| Tests | `tests/integration/account-login.test.ts` uses the real `0.2.2-alpha.2` 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. |
|
|
171
172
|
| 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. |
|
|
172
|
-
| 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.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
|
|
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 |
|
|
173
174
|
| 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 |
|
|
174
175
|
|
|
175
176
|
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.
|
|
@@ -180,21 +181,21 @@ Manual official-account callback handoff. Type: `dsh-runtime`. Active; an indepe
|
|
|
180
181
|
|
|
181
182
|
Long-lived listener transaction-context isolation after native hot reload. Type: `dsh-runtime`. Active.
|
|
182
183
|
|
|
183
|
-
| Field | Maintenance basis
|
|
184
|
-
| ----------------------------------- |
|
|
185
|
-
| 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` and `0.2.2-alpha.2` |
|
|
186
|
-
| 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.
|
|
187
|
-
| 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.
|
|
188
|
-
| 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`; 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. |
|
|
189
|
-
| 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.
|
|
184
|
+
| Field | Maintenance basis |
|
|
185
|
+
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
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` and `0.2.2-alpha.2` |
|
|
187
|
+
| 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
|
+
| 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
|
+
| 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
|
+
| 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. |
|
|
190
191
|
|
|
191
192
|
## DSH-RESOURCE-001
|
|
192
193
|
|
|
193
|
-
Native HTTP resource admission. Type: `dsh-runtime`.
|
|
194
|
+
Native HTTP resource admission. Type: `dsh-runtime`. Introduced in plugin `0.3.2`.
|
|
194
195
|
|
|
195
196
|
| Field | Maintenance basis |
|
|
196
197
|
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
197
|
-
| Exact adapted versions | `0.2.2-alpha.2`; intersects the
|
|
198
|
+
| Exact adapted versions | `0.2.2-alpha.2`; intersects the nine-target release set, 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. |
|
|
198
199
|
| 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. |
|
|
199
200
|
| 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. |
|
|
200
201
|
| 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. |
|
|
@@ -205,7 +206,7 @@ Native HTTP resource admission. Type: `dsh-runtime`. Added in unpublished plugin
|
|
|
205
206
|
|
|
206
207
|
## DSH-LIVESHARE-001
|
|
207
208
|
|
|
208
|
-
Public peer admission and owner-login business Origin. Type: `dsh-runtime`.
|
|
209
|
+
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`.
|
|
209
210
|
|
|
210
211
|
| Field | Maintenance basis |
|
|
211
212
|
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
@@ -217,11 +218,11 @@ Public peer admission and owner-login business Origin. Type: `dsh-runtime`. Adde
|
|
|
217
218
|
|
|
218
219
|
## PLUGIN-CONFIG-001
|
|
219
220
|
|
|
220
|
-
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.
|
|
221
|
+
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.3`, independent of the DSH version set.
|
|
221
222
|
|
|
222
223
|
| Field | Maintenance basis |
|
|
223
224
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
224
|
-
| 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` and `0.3.
|
|
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.3` retain it |
|
|
225
226
|
| 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 |
|
|
226
227
|
| 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 |
|
|
227
228
|
| 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 |
|
|
@@ -244,9 +245,9 @@ Fixed-English CLI. Type: `plugin-contract`; plugin `0.3.2` explicitly ends its e
|
|
|
244
245
|
|
|
245
246
|
## Shared security boundaries
|
|
246
247
|
|
|
247
|
-
Remote profiles must independently disable native `webserver`. `tests/browser/startup-compatibility.spec.ts` covers Loader skip/plugin runtime rejection on
|
|
248
|
+
Remote profiles must independently disable native `webserver`. `tests/browser/startup-compatibility.spec.ts` covers Loader skip/plugin runtime rejection on nine hosts: a peer fault on minimum `0.2.1-alpha.3`, engines faults on the other eight. `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.
|
|
248
249
|
|
|
249
|
-
`src/shared/dsh-support.ts` explicitly records three legacy Alphas,
|
|
250
|
+
`src/shared/dsh-support.ts` explicitly records three legacy Alphas, five normal RCs, normally supported `0.2.2-alpha.2` and six retired hosts in planned release `0.3.3`, with last plugin `0.2.0`. `retiredOn: 2026-10-28` is preparation date, not actual npm publication, and never drives shutdown. Process-wide/HMR deduplication, required APIs, host identity and shared security checks remain; the support policy records current dates.
|
|
250
251
|
|
|
251
252
|
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.
|
|
252
253
|
|
|
@@ -268,4 +269,10 @@ Historical 2026-10-19 RC candidate admission: verified exact tags `dsh-v0.2.1-rc
|
|
|
268
269
|
|
|
269
270
|
Exact 2026-10-28 admission: `0.2.1-rc.3` tag `1f81c047fc48fa190a683e469daa699857e9afe8`, `0.2.1-rc.4` tag `504a01a9578abc2c6f1fb896b1dc322c9fe24f66` and archive identity/integrity were checked; nine critical lib trees match `0.2.1-rc.2`. Native focus.css is byte-identical on `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`. New RCs retain account loopback restrictions and private HMR executing/runExclusive shape; no native public authorization or public isolation replacement is established, so ACCOUNT/HMR remain. Search/Fetch, navigation and switching specialized runs passed; final same-archive evidence is separate.
|
|
270
271
|
|
|
271
|
-
The 2026-10-29 `0.3.2` intersection review changes no prior exclusive-path retirement. Exact new `0.2.2-alpha.2` source is tag `dsh-v0.2.2-alpha.2` (`f3803c96974ad4a94195fb97e5c637e9c2a3afe3`), using actual Cordis `4.0.6-alpha.1` / Schemastery `3.18.6-alpha.1`; older SDK facts remain unchanged. Real WebServer Config/protocol, WebApp `getAdvertisedUrl()`, harness-dev-context and native account metadata/loopback restrictions were inspected individually. Shared THEME evidence is inline `:focus-visible` at line 1473 of exact `@deepseek-ai/dsh-client-ui-theme@0.2.2-alpha.2/lib/client.js`, retaining `--dsw-focus-ring-color` fallback to `--dsw-alias-state-business-primary` and a transparent pointer override; file SHA-256 is `3f3b79545546d9cebee52d198aa49512c7a9d1db783d9f907db8f207a153e015`. This does not establish byte equality of entire theme packages.
|
|
272
|
+
The 2026-10-29 `0.3.2` intersection review changes no prior exclusive-path retirement. Exact new `0.2.2-alpha.2` source is tag `dsh-v0.2.2-alpha.2` (`f3803c96974ad4a94195fb97e5c637e9c2a3afe3`), using actual Cordis `4.0.6-alpha.1` / Schemastery `3.18.6-alpha.1`; older SDK facts remain unchanged. Real WebServer Config/protocol, WebApp `getAdvertisedUrl()`, harness-dev-context and native account metadata/loopback restrictions were inspected individually. Shared THEME evidence is inline `:focus-visible` at line 1473 of exact `@deepseek-ai/dsh-client-ui-theme@0.2.2-alpha.2/lib/client.js`, retaining `--dsw-focus-ring-color` fallback to `--dsw-alias-state-business-primary` and a transparent pointer override; file SHA-256 is `3f3b79545546d9cebee52d198aa49512c7a9d1db783d9f907db8f207a153e015`. This does not establish byte equality of entire theme packages. That release’s eight-host matrices and native cases defined verification targets; final same-archive reports are recorded separately. Historical gaps remain, and local protocol stand-ins do not establish real-service experience.
|
|
273
|
+
|
|
274
|
+
The 2026-10-30 `0.3.3` review adds exact DSH `0.2.1-rc.5`, tag `dsh-v0.2.1-rc.5` (`b830ec950faba0a46dda564be3e2d854afed94f1`). Compared with `dsh-v0.2.1-rc.4` (`504a01a9578abc2c6f1fb896b1dc322c9fe24f66`), 349 manifests change only their own version; the other 19 changed files concern reasoning display, its Body Slot, tests and documentation. The plugin uses neither `conversation.chat.reasoning.body` nor `conversation.chat.reasoning.content`. Exact npm archives for both releases were downloaded and package names/versions checked. The entire `lib` trees of WebServer, Connection, Settings, Slots, account, account-platform, authorization, WebApp, HMR and theme are byte-identical between these two releases, including JavaScript, declarations and CSS. The isolated DSH → WebApp dependency chain resolves WebApp, WebServer and Connection to `0.2.1-rc.5`, Cordis to `4.0.5` and Schemastery to `3.18.5`. This establishes unchanged adapter contracts, not runtime verification of the new plugin archive.
|
|
275
|
+
|
|
276
|
+
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
|
+
|
|
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`. Release verification requires nine exact CLI, complete-browser and smoke targets consuming the same final `0.3.3` archive.
|