dsh-auth-remote 0.3.4 → 0.3.6
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 +2 -2
- package/CONTRIBUTING.zh-CN.md +2 -2
- package/README.md +19 -18
- package/README.zh-CN.md +19 -18
- package/dist/client.js +106 -16
- package/dist/client.js.map +3 -3
- package/dist/index.js +17 -20
- package/dist/index.js.map +2 -2
- package/dist/types/shared/dsh-support.d.ts +3 -0
- package/dist/types/shared/dsh-support.d.ts.map +1 -1
- package/docs/deployment.md +8 -6
- package/docs/deployment.zh-CN.md +8 -6
- package/docs/development.md +57 -50
- package/docs/development.zh-CN.md +57 -50
- package/docs/legacy-compatibility.md +140 -100
- package/docs/legacy-compatibility.zh-CN.md +132 -92
- package/docs/releasing.md +27 -14
- package/docs/releasing.zh-CN.md +27 -14
- package/docs/reverse-proxy.md +1 -1
- package/docs/reverse-proxy.zh-CN.md +1 -1
- package/docs/support-history.md +69 -65
- package/docs/support-history.zh-CN.md +52 -48
- package/docs/support-policy.md +24 -20
- package/docs/support-policy.zh-CN.md +25 -19
- package/package.json +17 -18
|
@@ -2,73 +2,78 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](legacy-compatibility.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
Last reviewed: 2026-11-
|
|
5
|
+
Last reviewed: 2026-11-13. 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
|
-
Plugin `0.3.
|
|
11
|
+
Plugin `0.3.6` is a local candidate declaring eight exact DSH releases: `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`, `0.2.2-rc.2`. The minimum supported host is `0.2.1-rc.1`; development defaults to recommended upstream RC prerelease `0.2.2-rc.2`. Technical admission remains `>=0.2.1-alpha.3`, including prereleases, without a new upper bound. Candidate declarations establish neither final same-archive acceptance nor publication.
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
`0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` retire from maintenance in plugin `0.3.6`, last supported plugin `0.3.5`. Their legacySince=2026-10-28, windowDays=14 and eligibleRetirement=2026-11-11 remain unchanged. retiredOn=2026-11-13 is the preparation date; registry publication time is recorded separately. They remain technically admissible with a warning and do not enter the technical refusal set. Published `0.3.5` retains its ten historical declarations and behavior, with its original archive available. The `0.3.4` upstream-failure retirement of `0.2.2-alpha.2` and six `0.3.1` technical retirements remain unchanged.
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
Exclusive HOST/PROTOCOL, PUBLIC option/text, THEME radius/thumb and TEST direct-navigation paths remain retired; shared checks remain. ACCOUNT/HMR still intersect support. RESOURCE/LIVESHARE retain historical applicability on `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`, intersecting current support at `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`. SETTINGS-ICON retains those three supported hosts; ACCOUNT-SLOT applies to exact `0.2.2-rc.2`. No existing production adaptation becomes an empty intersection through these three retirements. Final same-archive evidence is separate and inherits no prototype or historical archive success.
|
|
16
16
|
|
|
17
17
|
## Scope and review rules
|
|
18
18
|
|
|
19
|
-
The current
|
|
19
|
+
The current eight exact declarations are listed above. DSH `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1` and `0.2.2-rc.2` 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`.
|
|
20
20
|
|
|
21
21
|
- Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
|
|
22
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.
|
|
23
|
-
- `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.6` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
|
|
24
24
|
- Missing exact-version evidence requires preserving implementation and recording the gap. Passing the same test on different releases does not prove identical implementation.
|
|
25
|
-
- Support or shared host-adapter changes require all
|
|
25
|
+
- Support or shared host-adapter changes require all eight 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.
|
|
26
26
|
|
|
27
27
|
## Feature → version matrix
|
|
28
28
|
|
|
29
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.
|
|
30
30
|
|
|
31
|
-
| Entry
|
|
32
|
-
|
|
|
33
|
-
| [DSH-HOST-001](#dsh-host-001), old IPv4 schema/TLS rejection
|
|
34
|
-
| [DSH-PROTOCOL-001](#dsh-protocol-001), HTTP/loopback bridge
|
|
35
|
-
| [DSH-PUBLIC-001](#dsh-public-001), missing CLI option
|
|
36
|
-
| [DSH-PUBLIC-001](#dsh-public-001), text projection
|
|
37
|
-
| [DSH-THEME-001](#dsh-theme-001), radius fallback
|
|
38
|
-
| [DSH-THEME-001](#dsh-theme-001), switch-thumb fallback
|
|
39
|
-
| [DSH-THEME-001](#dsh-theme-001), focus-color migration
|
|
40
|
-
| [DSH-TEST-001](#dsh-test-001), direct Settings navigation
|
|
41
|
-
| [DSH-
|
|
42
|
-
| [DSH-
|
|
43
|
-
| [DSH-
|
|
44
|
-
| [DSH-
|
|
45
|
-
| [DSH-
|
|
46
|
-
| [
|
|
47
|
-
| [
|
|
48
|
-
| [
|
|
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`, `0.2.2-rc.2` | 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-TEST-001](#dsh-test-001), current Search/Fetch form branches | `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`, `0.2.2-rc.2` | Retain the switch branch and exact `0.2.2-rc.2` provider/billing branch while supported intersections remain; preserve settings/credential gates |
|
|
42
|
+
| [DSH-TEST-001](#dsh-test-001), maintenance-retirement boundary acceptance | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` | Independent three-scenario CLI/HTTP acceptance for plugin `0.3.6` only; no positive-support or technical-refusal claim; no Chromium; CI requires this only for validated `0.3.6` full, otherwise expects a skip |
|
|
43
|
+
| [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`, `0.2.2-rc.2` | Retained; no server-side old-version branch after global admission; exported helper still checks optional/invalid/older version inputs |
|
|
44
|
+
| [DSH-ACCOUNT-SLOT-001](#dsh-account-slot-001) | `0.2.2-rc.2` | Private component decoration preserving native account children; exact mechanism evidence obtained, declared in candidate `0.3.6`, final same-archive acceptance pending |
|
|
45
|
+
| [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`, `0.2.2-rc.2` | Retained for supported exact hosts; only retired matrix targets removed |
|
|
46
|
+
| [DSH-RESOURCE-001](#dsh-resource-001) | `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2` | 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`, `0.2.2-rc.2`, retain implementation/security tests |
|
|
47
|
+
| [DSH-LIVESHARE-001](#dsh-liveshare-001) | `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2` | Public peer/baseline and business Origin boundaries retained. Historical local Relay reports certify only their original archive/exact hosts; current viewer/Origin acceptance is separate. Current support intersection `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`; retain implementation/shared security tests Current coverage: native viewer and Connection business-Origin/HMR probe; Owner/Relay product cases removed in `0.3.6`. |
|
|
48
|
+
| [DSH-SETTINGS-ICON-001](#dsh-settings-icon-001) | `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2` | Native optional icon slot; exact default policy in the entry |
|
|
49
|
+
| [PLUGIN-CONFIG-001](#plugin-config-001) | Plugin `0.1.5` allowedOrigins input, independent of DSH versions | Retained under its own contract |
|
|
50
|
+
| [PLUGIN-LOCALE-001](#plugin-locale-001) | Plugin `0.3.2`; independent of DSH versions | New memory contract; old key ignored/retained/not migrated |
|
|
51
|
+
| [PLUGIN-CLI-001](#plugin-cli-001) | Plugin `0.3.2`; independent of DSH versions | Fixed English; earlier --lang ended by plugin policy |
|
|
49
52
|
|
|
50
53
|
## Version → feature matrix
|
|
51
54
|
|
|
52
55
|
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.
|
|
53
56
|
|
|
54
|
-
| Exact DSH version | Current state
|
|
55
|
-
| ----------------- |
|
|
56
|
-
| `0.1.7-rc.1` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
57
|
-
| `0.1.7-rc.2` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
58
|
-
| `0.2.0-rc.1` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
59
|
-
| `0.2.0-rc.2` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
60
|
-
| `0.2.1-alpha.1` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
61
|
-
| `0.2.1-alpha.2` | Retired in `0.3.1`; last plugin `0.2.0`
|
|
62
|
-
| `0.2.1-alpha.3` |
|
|
63
|
-
| `0.2.1-alpha.4` |
|
|
64
|
-
| `0.2.1-alpha.5` |
|
|
65
|
-
| `0.2.1-rc.1` | Supported
|
|
66
|
-
| `0.2.1-rc.2` | Supported
|
|
67
|
-
| `0.2.1-rc.3` | Supported
|
|
68
|
-
| `0.2.1-rc.4` | Supported
|
|
69
|
-
| `0.2.1-rc.5` | Supported
|
|
70
|
-
| `0.2.2-alpha.2` | Retired in `0.3.4` (2026-11-05); last historical support `0.3.3`
|
|
71
|
-
| `0.2.2-alpha.3` | Supported
|
|
57
|
+
| Exact DSH version | Current state | Historical adaptations / retained shared checks |
|
|
58
|
+
| ----------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
59
|
+
| `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 |
|
|
60
|
+
| `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 |
|
|
61
|
+
| `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 |
|
|
62
|
+
| `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 |
|
|
63
|
+
| `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 |
|
|
64
|
+
| `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 |
|
|
65
|
+
| `0.2.1-alpha.3` | Maintenance retired in `0.3.6`; last supported `0.3.5` | Historical DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-SETTINGS-ICON-001 host-default policy; native capability facts remain, without current onboarding/Settings/host-release positive browser coverage. DSH-TEST-001: only plugin `0.3.6` full three-scenario CLI/HTTP maintenance-boundary checks, not restored support. |
|
|
66
|
+
| `0.2.1-alpha.4` | Maintenance retired in `0.3.6`; last supported `0.3.5` | Historical DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-SETTINGS-ICON-001 host-default policy; native capability facts remain, without current onboarding/Settings/host-release positive browser coverage. DSH-TEST-001: only plugin `0.3.6` full three-scenario CLI/HTTP maintenance-boundary checks, not restored support. |
|
|
67
|
+
| `0.2.1-alpha.5` | Maintenance retired in `0.3.6`; last supported `0.3.5` | Historical DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-SETTINGS-ICON-001 host-default policy; native capability facts remain, without current onboarding/Settings/host-release positive browser coverage. DSH-TEST-001: only plugin `0.3.6` full three-scenario CLI/HTTP maintenance-boundary checks, not restored support. |
|
|
68
|
+
| `0.2.1-rc.1` | Supported; minimum supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings retained; actual host-release prompt observed as the previous host in the `0.2.1-rc.2` round trip; DSH-SETTINGS-ICON-001: host default |
|
|
69
|
+
| `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; DSH-TEST-001: Search/Fetch switch |
|
|
70
|
+
| `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; DSH-TEST-001: Search/Fetch switch |
|
|
71
|
+
| `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; DSH-TEST-001: Search/Fetch switch |
|
|
72
|
+
| `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; DSH-TEST-001: Search/Fetch switch |
|
|
73
|
+
| `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 |
|
|
74
|
+
| `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; DSH-TEST-001: Search/Fetch switch; LIVESHARE coverage retains viewer and business-Origin/HMR only; product-flow reports are historical. |
|
|
75
|
+
| `0.2.2-rc.1` | 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; DSH-TEST-001: Search/Fetch switch; LIVESHARE coverage retains viewer and business-Origin/HMR only; product-flow reports are historical. |
|
|
76
|
+
| `0.2.2-rc.2` | Supported candidate; development default and recommended RC prerelease | DSH-THEME-001, DSH-ACCOUNT-001, DSH-ACCOUNT-SLOT-001, DSH-HMR-001, DSH-RESOURCE-001, DSH-LIVESHARE-001, DSH-SETTINGS-ICON-001; shared native/security checks retained; final same-archive evidence separate; DSH-TEST-001: provider/billing menus; LIVESHARE coverage retains viewer and business-Origin/HMR only; product-flow reports are historical. |
|
|
72
77
|
|
|
73
78
|
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.
|
|
74
79
|
|
|
@@ -87,7 +92,7 @@ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Exclusive adapt
|
|
|
87
92
|
| Field | Maintenance basis |
|
|
88
93
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
89
94
|
| 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 |
|
|
90
|
-
| 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
|
|
95
|
+
| 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`, `0.2.2-rc.2` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
|
|
91
96
|
| 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 |
|
|
92
97
|
| 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 |
|
|
93
98
|
| 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 |
|
|
@@ -101,7 +106,7 @@ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`.
|
|
|
101
106
|
| Field | Maintenance basis |
|
|
102
107
|
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
103
108
|
| 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 |
|
|
104
|
-
| 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
|
|
109
|
+
| 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`, `0.2.2-rc.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 |
|
|
105
110
|
| 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 |
|
|
106
111
|
| 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 |
|
|
107
112
|
| 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 |
|
|
@@ -114,14 +119,14 @@ Outer Cookie Secure follows the public origin; native Cookie Secure follows the
|
|
|
114
119
|
|
|
115
120
|
Public URL projection and model prompt location differences. Type: `dsh-runtime`. Exclusive adaptation retired in plugin `0.3.1`; shared native validation remains.
|
|
116
121
|
|
|
117
|
-
| Field | Maintenance basis
|
|
118
|
-
| ---------------------------------- |
|
|
119
|
-
| 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
|
|
120
|
-
| 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
|
|
121
|
-
| 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
|
|
122
|
-
| 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
|
|
123
|
-
| 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
|
|
124
|
-
| 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`
|
|
122
|
+
| Field | Maintenance basis |
|
|
123
|
+
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
124
|
+
| 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 |
|
|
125
|
+
| 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 |
|
|
126
|
+
| 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`, `0.2.2-rc.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 |
|
|
127
|
+
| 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 |
|
|
128
|
+
| 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 |
|
|
129
|
+
| 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`, `0.2.2-rc.2`. A new projection location does not change how another supported release must be observed |
|
|
125
130
|
|
|
126
131
|
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.
|
|
127
132
|
|
|
@@ -132,10 +137,10 @@ CSS fallback for missing theme tokens. Type: `dsh-runtime`. Retired in plugin `0
|
|
|
132
137
|
| Field | Maintenance basis |
|
|
133
138
|
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
134
139
|
| 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 |
|
|
135
|
-
| 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` 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`
|
|
140
|
+
| 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`, `0.2.2-rc.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
141
|
| 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 |
|
|
137
142
|
| 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. |
|
|
138
|
-
| Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all
|
|
143
|
+
| Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all eight 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 |
|
|
139
144
|
|
|
140
145
|
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.
|
|
141
146
|
|
|
@@ -145,13 +150,13 @@ Exact focus evidence correction (2026-10-28): all seven native focus.css rules r
|
|
|
145
150
|
|
|
146
151
|
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.
|
|
147
152
|
|
|
148
|
-
| Field | Maintenance basis
|
|
149
|
-
| ------------------------ |
|
|
150
|
-
| 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
|
|
151
|
-
| 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` use account menu → Settings and native account onboarding. The manual sign-in overlay adds no alternate Settings entry; generic asynchronous retries remain.
|
|
152
|
-
| 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
|
|
153
|
-
| 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`
|
|
154
|
-
| 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
|
|
153
|
+
| Field | Maintenance basis |
|
|
154
|
+
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
155
|
+
| 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 |
|
|
156
|
+
| 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`, `0.2.2-rc.2` use account menu → Settings and native account onboarding. The manual sign-in overlay adds no alternate Settings entry; generic asynchronous retries remain. |
|
|
157
|
+
| 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`, `0.2.2-rc.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 |
|
|
158
|
+
| 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` |
|
|
159
|
+
| 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 |
|
|
155
160
|
|
|
156
161
|
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.
|
|
157
162
|
|
|
@@ -161,37 +166,54 @@ On 2026-10-16, `tests/browser/host-release.spec.ts` retained a `0.2.1-alpha.4` p
|
|
|
161
166
|
|
|
162
167
|
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.
|
|
163
168
|
|
|
169
|
+
On exact `0.2.2-rc.2`, `tests/browser/web-search-settings.spec.ts` uses real independent provider and `searchBilling`/`fetchBilling` menus; `native Search and Fetch billing preserves settings and credential boundaries` is mandatory. It covers auto/account/api-key, clearing default overrides, refusal retention, restart, and actual credential replacement/removal without echo. Native model configuration directs endpoints locally without setting API-specific overrides that lock billing. The switch branch remains for `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`; `0.2.1-rc.1` still has no real case in that feature file. `tests/browser/rc-navigation.spec.ts` retains three native More menus, model controls and revocation. Both branch intersections remain nonempty, so retire neither implementation nor shared security checks. These checks do not close the notice/reload gaps above; stage and final archive evidence remain separate.
|
|
170
|
+
|
|
171
|
+
The one-release plugin `0.3.6` boundary acceptance uses `scripts/verify-maintenance-retired.mjs` and `tests/retirement/maintenance-retirement.test.ts` only for exact `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`. The consumer first validates supported `0.2.2-rc.2` and the complete eight-host archive, then explicitly rejects declaration of the selected retired host. Explicit binary/archive selection does not change DSH_TEST_VERSION. Three scenarios per host check real install/init, retirement warning before readiness, authenticated configuration/source HMR with warning deduplication and revocation, and no TCP/HTTP/readiness/WebSocket listener after Loader or runtime refusal. The Loader fault changes only the temporary plugin Host peer on `0.2.1-alpha.3`, or its engines.dsh on `0.2.1-alpha.4`, `0.2.1-alpha.5`; upstream identity and dependency graphs remain intact. Real HMR observation and package-file/copy checks are reused, without launching Chromium. Source HMR uses an independently byte-verified copy of the installed candidate in the profile’s public native watch root because node_modules is excluded; the initial installed entry and configuration HMR are tested before switching to that copy. This does not restore positive support or change the six-host technical refusal consumer; final-archive results remain separate. `tests/unit/verify-maintenance-retired.test.ts` covers identity/TAP/installed-byte refusal, real uncooperative preparation cancellation and unsafe parent directories; shared detached-process shutdown in `scripts/runtime.mjs` remains bounded.
|
|
172
|
+
|
|
173
|
+
The generic unpackaged evidence protocol is in `scripts/packed-artifact.mjs`: every local/PR/master/tag producer records HEAD, the full diff, untracked inputs, file modes/digests and archive SHA. Within an acceptance context, every actual runtime preparation in `scripts/runtime.mjs` records the real CLI, lock, DSH→WebApp→SDK manifests and complete-tree copy check, including Host round trips, private account runtimes and smoke. Original consumer JSON/TAP schemas remain; adjacent sidecars bind raw reports/logs/all runtimes to the producer digest. The index requires each suite’s runtime roles, including a distinct smoke runtime, the exact previous host for each round trip, and both private account runtimes on `0.2.2-rc.2`. Missing reports or required runtimes, wrong hashes, mixed producers and partial suites are refused; one producer’s success cannot certify another. Ordinary/full still run complete positive coverage on all eight hosts. Only a validated plugin `0.3.6` with full plan requires the three maintenance-retirement targets above; an actual simulated `0.3.7` full-plan archive outputs false. Independent `0.2.1-alpha.2` technical refusal remains in full. CI uploads raw artifacts and the index outside npm; this is neither an inventory generator nor an inventory-specific gate.
|
|
174
|
+
|
|
164
175
|
## DSH-ACCOUNT-001
|
|
165
176
|
|
|
166
177
|
Manual official-account callback handoff. Type: `dsh-runtime`. Active; an independently removable temporary adaptation.
|
|
167
178
|
|
|
168
|
-
| Field | Maintenance basis
|
|
169
|
-
| ------------------------------------- |
|
|
170
|
-
| 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
|
|
171
|
-
| 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.
|
|
172
|
-
| 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
|
|
173
|
-
| Reason and upstream |
|
|
174
|
-
| 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/`.
|
|
175
|
-
| Tests | `tests/integration/account-login.test.ts` uses the real `0.2.2-
|
|
176
|
-
| 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.
|
|
177
|
-
| 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` 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
|
-
| 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
|
|
179
|
+
| Field | Maintenance basis |
|
|
180
|
+
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
181
|
+
| 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`, `0.2.2-rc.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 |
|
|
182
|
+
| 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. |
|
|
183
|
+
| 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 |
|
|
184
|
+
| Reason and upstream | Installed account-provider `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 |
|
|
185
|
+
| 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/`. Hosts without children use public slot entries/subscribe/priority APIs; child-owning entries follow DSH-ACCOUNT-SLOT-001; 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. |
|
|
186
|
+
| Tests | `tests/integration/account-login.test.ts` uses the real merged `0.2.2-rc.2` account 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. |
|
|
187
|
+
| 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. |
|
|
188
|
+
| 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`, `0.2.2-rc.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 |
|
|
189
|
+
| 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 |
|
|
179
190
|
|
|
180
191
|
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.
|
|
181
192
|
|
|
182
193
|
2026-10-28 candidate administrator boundary: index injection grants ownsHost/manual only for an owner peer; an absent peer retains the old contract, which does not imply old hosts lack a remoteAccess baseline. The client reads public `__DSH_REMOTE_ACCESS__` before styles, dictionaries, monitoring, slots or account adaptation; explicit non-owner or present-invalid baselines return immediately. `tests/unit/client-capability.test.ts` and `tests/browser/liveshare.spec.ts` cover the native viewer carrier/index and the complete entry without administrator effects.
|
|
183
194
|
|
|
195
|
+
## DSH-ACCOUNT-SLOT-001
|
|
196
|
+
|
|
197
|
+
Native account child ownership decoration. Type: `dsh-runtime`. Exact applicability: DSH `0.2.2-rc.2`; this is not an officially supported extension interface.
|
|
198
|
+
|
|
199
|
+
- Upstream evidence: tag `dsh-v0.2.2-rc.2` (`ddac96760b6edf8fa0fe17cbdcf0b512f4c12b2c`); exact ui-settings-account declares notifications children on its launcher, ui-renderer binds renderSlot to the original StoredEntry, and duplicated children declarations are rejected.
|
|
200
|
+
- Implementation: `src/client/account/native-entry.ts`, `src/client/account/index.tsx`. Replace only writable component; retain the original entry/children/inject/options/registrant/disposer. An owned provideRoot contribution redraws installation/removal; conditional restoration protects later writers. Inactive wrappers delegate to native without initiating plugin authorization; pending preference reads recheck lifetime. Hosts without children retain public shadow registration.
|
|
201
|
+
- Tests: `tests/unit/account-entry.test.ts` checks shape, rollback, reinstallation, conditional restoration and release. `tests/browser/account-login.spec.ts` requires `native account entry decoration preserves child ownership across client reloads` and `native account notifications remain local across language and lifecycle changes` on exact `0.2.2-rc.2`. `tests/fixtures/account-entry-observer.js` observes real entries, bindings, root contributions and module lifetimes. The regressions cover client bundle HMR during authorization, inactive retained wrappers, replacement before pending preference reads settle, and local notification content/events across eight UI languages. Actual local wire locales are `zh_CN` and `en_US`; these are not eight independently localized service responses. Real notification services and cross-product notification localization mapping remain unverified. Stage probes and browser reports bind their own candidate digest. Final eight-version acceptance remains separate; prototype success does not establish it.
|
|
202
|
+
- Migration/retirement: initial evidence covers only `0.2.2-rc.2`. Retain while applicability intersects support. Remove private implementation and exclusive tests only after a public replacement is verified on each applicable supported exact host, or the applicable set entirely leaves support. Preserve shared authentication, security and native child ownership checks. `DSH-ACCOUNT-001` continues to own the loopback callback contract.
|
|
203
|
+
|
|
184
204
|
## DSH-HMR-001
|
|
185
205
|
|
|
186
206
|
Long-lived listener transaction-context isolation after native hot reload. Type: `dsh-runtime`. Active.
|
|
187
207
|
|
|
188
|
-
| Field | Maintenance basis
|
|
189
|
-
| ----------------------------------- |
|
|
190
|
-
| 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
|
|
191
|
-
| 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.
|
|
192
|
-
| 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.
|
|
193
|
-
| 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.
|
|
194
|
-
| 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.
|
|
208
|
+
| Field | Maintenance basis |
|
|
209
|
+
| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
210
|
+
| 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`, `0.2.2-rc.2` |
|
|
211
|
+
| 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. |
|
|
212
|
+
| 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. |
|
|
213
|
+
| 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. Historical module-replacement regression also targeted `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. |
|
|
214
|
+
| 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. |
|
|
215
|
+
|
|
216
|
+
Current positive configuration/module-HMR cases register on `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`, `0.2.2-rc.2`; final same-archive results are separate. The three retired Alphas have no continuing positive browser coverage; only plugin `0.3.6` maintenance-retirement checks exercise real config/source HMR, warning deduplication and session boundaries.
|
|
195
217
|
|
|
196
218
|
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.
|
|
197
219
|
|
|
@@ -201,7 +223,7 @@ Native HTTP resource admission. Type: `dsh-runtime`. Introduced in plugin `0.3.2
|
|
|
201
223
|
|
|
202
224
|
| Field | Maintenance basis |
|
|
203
225
|
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
204
|
-
| Exact adapted versions | `0.2.2-alpha.2`, `0.2.2-alpha.3`; current support intersection is `0.2.2-alpha.3`, 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.
|
|
226
|
+
| Exact adapted versions | `0.2.2-alpha.2`, `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`; current support intersection is `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`, 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. |
|
|
205
227
|
| 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. |
|
|
206
228
|
| 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. |
|
|
207
229
|
| 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. |
|
|
@@ -212,39 +234,41 @@ Native HTTP resource admission. Type: `dsh-runtime`. Introduced in plugin `0.3.2
|
|
|
212
234
|
|
|
213
235
|
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.
|
|
214
236
|
|
|
237
|
+
The stream integration test on exact development dependency `0.2.2-rc.2` reads the native private `server` member only to attach a passive Node `request` observer for two test resource paths. Within a bounded five seconds, `tests/integration/http-gate.test.ts` waits for a nonempty real response queue, writableNeedDrain, and 200ms without production, then retains the original 50ms strict counter equality. This replaces the fixed 100ms TCP-fill assumption without wrapping write or changing routing/admission. Complete bytes, at most one HEAD prefetch, client disconnect, revocation and cancel/abort/close checks remain. This private member is test observation rather than a product API; final same-archive evidence is separate.
|
|
238
|
+
|
|
215
239
|
## DSH-LIVESHARE-001
|
|
216
240
|
|
|
217
241
|
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`.
|
|
218
242
|
|
|
219
|
-
| Field | Maintenance basis
|
|
220
|
-
| ------------------------------- |
|
|
221
|
-
| Native public boundary | Native WebServer index injection passes the real `peer`; only principal kind owner receives plugin administrator capabilities. The public `__DSH_REMOTE_ACCESS__` baseline controls the earliest client exit. Old absent-peer events retain their contract; old hosts can already carry a remoteAccess baseline. No private RemoteAccess state, URL or isLoopback inference is used for owner identity.
|
|
222
|
-
| 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.
|
|
223
|
-
| 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.
|
|
224
|
-
| Tests and limits | `tests/unit/client-capability.test.ts`, `tests/browser/liveshare.spec.ts`, `tests/fixtures/liveshare-viewer.mjs` and `liveshare-client-observer.js`
|
|
225
|
-
| Migration and retirement | Retain
|
|
243
|
+
| Field | Maintenance basis |
|
|
244
|
+
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
245
|
+
| Native public boundary | Native WebServer index injection passes the real `peer`; only principal kind owner receives plugin administrator capabilities. The public `__DSH_REMOTE_ACCESS__` baseline controls the earliest client exit. Old absent-peer events retain their contract; old hosts can already carry a remoteAccess baseline. No private RemoteAccess state, URL or isLoopback inference is used for owner identity. |
|
|
246
|
+
| 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. |
|
|
247
|
+
| 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. |
|
|
248
|
+
| Tests and limits | `tests/unit/client-capability.test.ts`, `tests/browser/liveshare.spec.ts`, `tests/fixtures/liveshare-viewer.mjs` and `liveshare-client-observer.js` retain real native viewer carrier/index and full-client isolation. `tests/integration/liveshare-origin.test.ts` retains three tests for exact paths, success/error/cancellation restoration, missing trusted context and fiber disposal/reload. On exact `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`, `tests/browser/native-transport.spec.ts` requires native connection business Origin follows admission and survives configuration reload. The thin `tests/fixtures/business-origin-observer.mjs` registers the two exact Owner POST paths through real `connection.fetch.register`; actual HTTP, HTTPS and HTTPS→HTTP proxy requests pass native admission, the public waterfall and native Request conversion. A passive listener records the bridge write and one Origin restoration pair before/after real configuration HMR. The probe reads private native `webServer.server` only to observe real Node requests and header writes; this test dependency is not a product API. Anonymous/revoked, bad/missing/duplicate Origin and cross-site requests remain denied before the Fetch handler. No sharing Host or Relay is loaded. The two Owner/Relay product-flow cases and their exclusive relay/session fixtures were removed by the `0.3.6` scope decision; historical reports remain bound to their original archives and exact hosts. No current Owner authorization, worker/create/list/stop, Relay or product-lifetime acceptance is claimed. |
|
|
249
|
+
| Migration and retirement | Retain for the exact current support intersection `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2` while these boundaries are required. 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
250
|
|
|
227
|
-
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.
|
|
251
|
+
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. This historical review required local-protocol regression and viewer isolation. The current scope retains native viewer and shared Origin checks; never enable sharing automatically or claim production Relay/OAuth, real visitor model calls or file writes.
|
|
228
252
|
|
|
229
253
|
## DSH-SETTINGS-ICON-001
|
|
230
254
|
|
|
231
255
|
Optional native Security & sign-in navigation icon. Type: `dsh-runtime`. Introduced in plugin `0.3.4`; retained while its supported applicability intersection is nonempty.
|
|
232
256
|
|
|
233
|
-
| Field | Maintenance basis
|
|
234
|
-
| ---------------------------- |
|
|
235
|
-
| Native-icon applicability | Exact DSH `0.2.2-alpha.3`
|
|
236
|
-
| 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
|
|
237
|
-
| 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.
|
|
238
|
-
| Tests and exact evidence | `tests/browser/settings-icon.spec.ts` registers on all
|
|
239
|
-
| Retirement | Keep while supported exact `0.2.2-alpha.3` 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.
|
|
257
|
+
| Field | Maintenance basis |
|
|
258
|
+
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
259
|
+
| Native-icon applicability | Exact DSH `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2` declare `settings.section.icon`, matched by the `settings.section` id `security`. |
|
|
260
|
+
| 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 twelve exact primitives packages export `IconShieldOutlineMedium`. |
|
|
261
|
+
| 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. |
|
|
262
|
+
| Tests and exact evidence | `tests/browser/settings-icon.spec.ts` registers on all eight 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. |
|
|
263
|
+
| Retirement | Keep while supported exact `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2` 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. |
|
|
240
264
|
|
|
241
265
|
## PLUGIN-CONFIG-001
|
|
242
266
|
|
|
243
|
-
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.
|
|
267
|
+
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.6`, independent of the DSH version set.
|
|
244
268
|
|
|
245
269
|
| Field | Maintenance basis |
|
|
246
270
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
247
|
-
| 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` and `0.3.
|
|
271
|
+
| 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`, `0.3.5` and `0.3.6` retain it |
|
|
248
272
|
| 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 |
|
|
249
273
|
| 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 |
|
|
250
274
|
| 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 |
|
|
@@ -267,9 +291,9 @@ Fixed-English CLI. Type: `plugin-contract`; plugin `0.3.2` explicitly ends its e
|
|
|
267
291
|
|
|
268
292
|
## Shared security boundaries
|
|
269
293
|
|
|
270
|
-
Remote profiles must independently disable native `webserver`. `tests/browser/startup-compatibility.spec.ts`
|
|
294
|
+
Remote profiles must independently disable native `webserver`. On all eight supported hosts, `tests/browser/startup-compatibility.spec.ts` uses the plugin’s engines fault for Loader skip and separately its admission-range fault for post-import refusal. The three retired Alphas instead use `scripts/verify-maintenance-retired.mjs` only for plugin `0.3.6` full: `0.2.1-alpha.3` uses a Host peer fault; `0.2.1-alpha.4` and `0.2.1-alpha.5` use engines faults, changing only private plugin copies. `scripts/verify-retired.mjs` independently checks unmodified-candidate installation rollback and whole-bundle peer skip on historical technically refused hosts; full retains exact `0.2.1-alpha.2`. Every path requires no TCP/HTTP/readiness/WebSocket listener and preserves upstream identity/auditing.
|
|
271
295
|
|
|
272
|
-
`src/shared/dsh-support.ts`
|
|
296
|
+
`src/shared/dsh-support.ts` reads eight current exact declarations: `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`, `0.2.2-rc.2`. Three Alphas have separate maintenance-retirement lifecycle records: effectivePlugin=0.3.6, lastSupportedPlugin=0.3.5, original legacySince=2026-10-28/windowDays=14/eligibleRetirement=2026-11-11 and preparation date retiredOn=2026-11-13. Six technical retirements retain last support `0.2.0`; `0.2.2-alpha.2` retains its `0.3.4`/2026-11-05 exception and last support `0.3.3`. Dates are not npm timestamps or timed refusal. Process/HMR warning deduplication and necessary API/identity/security checks remain.
|
|
273
297
|
|
|
274
298
|
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.
|
|
275
299
|
|
|
@@ -312,3 +336,19 @@ The `0.3.4` release withdraws only exact DSH `0.2.2-alpha.2` after native-only r
|
|
|
312
336
|
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.
|
|
313
337
|
|
|
314
338
|
`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.
|
|
339
|
+
|
|
340
|
+
## 2026-11-06 RC admission review
|
|
341
|
+
|
|
342
|
+
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.
|
|
343
|
+
|
|
344
|
+
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.
|
|
345
|
+
|
|
346
|
+
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.
|
|
347
|
+
|
|
348
|
+
2026-11-13 provider migration stage: development dependencies pin exact `0.2.2-rc.2` and remove the merged deepseek-account-platform development dependency. Account integration uses the actual deepseek-account service with platformOrigin/harnessOrigin/inferenceOrigin explicitly local. Notification list/content/events use valid local samples; unexpected requests fail. live-config observes the merged account package on exact `0.2.2-rc.2` and the exact platform package on existing targets, without ignoring resolution failures. Declarations and the default runtime switch together in the next stage; old exact-host facts remain unchanged.
|
|
349
|
+
|
|
350
|
+
## 2026-11-13 RC and maintenance-retirement intersection review
|
|
351
|
+
|
|
352
|
+
Exact `0.2.2-rc.2` tag `ddac96760b6edf8fa0fe17cbdcf0b512f4c12b2c` and installed packages retain the WebServer resource boundary, HMR executing/runExclusive, native focus fallback, settings-general icon declaration and account notification children. Real merged-provider integration verifies PKCE/loopback behavior. Development and the actual rc.2 chain use Cordis `4.1.0`, Schemastery `3.19.0`, Loader/Include `1.1.0`. Supported exact `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 their old SDK/effectiveConfig/config observation.
|
|
353
|
+
|
|
354
|
+
Each original 13 entries was reviewed against the eight-host set; DSH-ACCOUNT-SLOT-001 brings the total to 14 stable IDs. Previously retired exclusive paths remain retired. ACCOUNT/HMR, RESOURCE/LIVESHARE and SETTINGS-ICON retain nonempty intersections, so all production adaptations and shared security checks remain. PLUGIN-CONFIG/LOCALE/CLI retain independent policies. Only obsolete exclusive positive tests and host-switch targets are removed. Technical refusal still selects the original six hosts; the three maintenance-retired Alphas remain admitted with a warning after technical checks. Unknown-host, real authorization/Relay, non-loopback IPv6 and notice/reload mapping gaps remain. Final eight-host and three-host maintenance acceptance is recorded separately; stage results do not replace it.
|