dsh-auth-remote 0.2.0 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (69) hide show
  1. package/CHANGELOG.md +21 -0
  2. package/CHANGELOG.zh-CN.md +21 -0
  3. package/CONTRIBUTING.md +2 -0
  4. package/CONTRIBUTING.zh-CN.md +2 -0
  5. package/README.md +33 -47
  6. package/README.zh-CN.md +33 -47
  7. package/dist/cli.js +63 -530
  8. package/dist/cli.js.map +4 -4
  9. package/dist/client.js +917 -135
  10. package/dist/client.js.map +3 -3
  11. package/dist/index.js +124 -67
  12. package/dist/index.js.map +4 -4
  13. package/dist/login.css +0 -21
  14. package/dist/login.css.map +2 -2
  15. package/dist/login.js +892 -155
  16. package/dist/login.js.map +3 -3
  17. package/dist/types/adapters/dsh/browser-capability.d.ts.map +1 -1
  18. package/dist/types/adapters/dsh/compatibility.d.ts +1 -1
  19. package/dist/types/adapters/dsh/compatibility.d.ts.map +1 -1
  20. package/dist/types/adapters/dsh/liveshare.d.ts +4 -0
  21. package/dist/types/adapters/dsh/liveshare.d.ts.map +1 -0
  22. package/dist/types/adapters/dsh/runtime-capabilities.d.ts +6 -11
  23. package/dist/types/adapters/dsh/runtime-capabilities.d.ts.map +1 -1
  24. package/dist/types/adapters/dsh/webserver.d.ts +8 -4
  25. package/dist/types/adapters/dsh/webserver.d.ts.map +1 -1
  26. package/dist/types/cli/ipc-client.d.ts.map +1 -1
  27. package/dist/types/cli/messages.d.ts +56 -0
  28. package/dist/types/cli/messages.d.ts.map +1 -0
  29. package/dist/types/cli/profile.d.ts.map +1 -1
  30. package/dist/types/cli/prompt.d.ts.map +1 -1
  31. package/dist/types/config.d.ts +2 -2
  32. package/dist/types/config.d.ts.map +1 -1
  33. package/dist/types/http/account-login.d.ts.map +1 -1
  34. package/dist/types/index.d.ts.map +1 -1
  35. package/dist/types/shared/dsh-support.d.ts.map +1 -1
  36. package/dist/types/shared/i18n.d.ts +878 -105
  37. package/dist/types/shared/i18n.d.ts.map +1 -1
  38. package/dist/types/shared/locales/de.d.ts +145 -0
  39. package/dist/types/shared/locales/de.d.ts.map +1 -0
  40. package/dist/types/shared/locales/en.d.ts +0 -49
  41. package/dist/types/shared/locales/en.d.ts.map +1 -1
  42. package/dist/types/shared/locales/es.d.ts +145 -0
  43. package/dist/types/shared/locales/es.d.ts.map +1 -0
  44. package/dist/types/shared/locales/fr.d.ts +145 -0
  45. package/dist/types/shared/locales/fr.d.ts.map +1 -0
  46. package/dist/types/shared/locales/ja.d.ts +145 -0
  47. package/dist/types/shared/locales/ja.d.ts.map +1 -0
  48. package/dist/types/shared/locales/pt.d.ts +145 -0
  49. package/dist/types/shared/locales/pt.d.ts.map +1 -0
  50. package/dist/types/shared/locales/ru.d.ts +145 -0
  51. package/dist/types/shared/locales/ru.d.ts.map +1 -0
  52. package/dist/types/shared/locales/zh.d.ts +0 -49
  53. package/dist/types/shared/locales/zh.d.ts.map +1 -1
  54. package/docs/deployment.md +30 -22
  55. package/docs/deployment.zh-CN.md +30 -22
  56. package/docs/development.md +70 -56
  57. package/docs/development.zh-CN.md +70 -56
  58. package/docs/legacy-compatibility.md +149 -80
  59. package/docs/legacy-compatibility.zh-CN.md +149 -80
  60. package/docs/releasing.md +15 -9
  61. package/docs/releasing.zh-CN.md +15 -9
  62. package/docs/reverse-proxy.md +2 -2
  63. package/docs/reverse-proxy.zh-CN.md +2 -2
  64. package/docs/support-history.md +67 -60
  65. package/docs/support-history.zh-CN.md +67 -60
  66. package/examples/web-profile-auth-remote.patch.yml +1 -1
  67. package/package.json +19 -22
  68. package/dist/types/cli/language.d.ts +0 -14
  69. package/dist/types/cli/language.d.ts.map +0 -1
@@ -2,64 +2,70 @@
2
2
 
3
3
  [简体中文](legacy-compatibility.zh-CN.md)
4
4
 
5
- Last reviewed: 2026-10-19. 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.
5
+ Last reviewed: 2026-10-29. 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
- Maintenance dates and current normal/legacy 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) queries distinguish declarations, reports, verified candidates and availability. The capability matrices below do not themselves announce retirement.
7
+ Current candidate maintenance dates and commitments are in [README](../README.md#dsh-compatibility). The unchanged [support policy](support-policy.md) retains the previous release record. Historical [DSH → plugin](support-history.md#by-dsh) and [plugin → DSH](support-history.md#by-plugin) distinguish declarations, reports, candidates and distribution.
8
+
9
+ ## Current migration candidate
10
+
11
+ Plugin `0.3.2` is unpublished. It declares DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2`; technical admission is `>=0.2.1-alpha.3` including prereleases without an upper bound, and the default/manual recommendation is `0.2.2-alpha.2`. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` are legacy from 2026-10-28 with a 14-day window and eligibility from 2026-11-11 (Asia/Shanghai); dates do not end support. Published `0.3.1` retains its seven declarations and retired DSH `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`, last supported by plugin `0.2.0`. Current commitments are in README; support-policy retains the previous release record.
12
+
13
+ Exact historical evidence remains below. Exclusive HOST/PROTOCOL old paths, PUBLIC option/text paths, THEME radius/thumb fallbacks and TEST direct navigation retired in `0.3.1`; this work does not retire them again. Native focus rules and shared security checks cover the eight current exact targets. ACCOUNT, HMR, general onboarding retries and PLUGIN-CONFIG remain; `0.3.2` adds RESOURCE and LIVESHARE boundaries. Exact new published packages/APIs were inspected; final same-archive reports are recorded separately without inheriting an old archive's success.
8
14
 
9
15
  ## Scope and review rules
10
16
 
11
- Plugin `0.2.0` (npm `0.1.10` history is unchanged) declares exact support for DSH `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` and `0.2.1-rc.2`. Development and tests default to `0.2.1-rc.2`. Runtime admission uses `>=0.1.7-rc.1`, including prereleases; admission is not verification and still requires package identity and API checks. Versions absent from these matrices do not inherit their verification claims. Manual-account admission uses `>=0.2.1-alpha.3` including prereleases, required native capabilities and the live `manualAccountLogin` preference; forward admission is not exact-version verification.
17
+ The current eight exact declarations are listed above. DSH `0.2.2-alpha.2` itself requires Node `>=24.9.0`; the plugin engine stays `>=24` with no added minor-version gate. Forward admission with prereleases still requires identity/API checks; unknown versions inherit no verification. The account adapter also requires capabilities and live `manualAccountLogin`.
12
18
 
13
19
  - Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
14
20
  - `dsh-runtime`: retain an adaptation while its applicable versions intersect the supported set. When the intersection becomes empty, remove exclusive implementation and tests and update both languages, matrices, entries and guides in the same change. Keep shared security checks.
15
- - `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.2.0` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
21
+ - `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.3.2` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
16
22
  - Missing exact-version evidence requires preserving implementation and recording the gap. Passing the same test on different releases does not prove identical implementation.
17
- - Support-range or shared host adaptation changes require CLI, browser and installation smoke coverage of the same final artifact across all declared versions. Full `DSH-ACCOUNT-001` feature regression targets `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-rc.2`; `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` need startup, Settings and disabled-adapter checks for that feature change. CLI/smoke always includes all eleven; full/release browser plans do too. Ordinary low-risk browser selection follows the fixed plan in the development guide.
23
+ - 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.
18
24
 
19
25
  ## Feature → version matrix
20
26
 
21
- “Native” means the exact installed DSH package provides the capability. “Plugin validation/fallback/enabled” identifies an adaptation retained here. “Rejected”, “absent” and “not provided” distinguish rejected configuration, a missing native option and a missing native feature. “Unverified” does not authorize code removal. Public HTTPS through an HTTP reverse proxy is separate from a native DSH HTTPS listener.
22
-
23
- | Feature and maintenance ID | `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` |
24
- | -------------------------------------------------------------------------------- | ---------------------------- | ---------------------------- | ---------------------------- | ---------------------------- | --------------------------------- | ---------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
25
- | Concrete IPv4 listener validation · [DSH-HOST-001](#dsh-host-001) | Plugin validation | Plugin validation | Plugin validation | Plugin validation | Plugin validation | Native validation | Native validation | Native validation | Native validation | Native validation | Native validation |
26
- | Native IPv6 listener · [DSH-HOST-001](#dsh-host-001) | Rejected | Rejected | Rejected | Rejected | Rejected | Native | Native | Native | Native | Native | Native |
27
- | Native HTTPS listener · [DSH-PROTOCOL-001](#dsh-protocol-001) | Rejected | Rejected | Rejected | Rejected | Rejected | Native | Native | Native | Native | Native | Native |
28
- | Server-side Connection bridge · [DSH-PROTOCOL-001](#dsh-protocol-001) | HTTP / `127.0.0.1` | HTTP / `127.0.0.1` | HTTP / `127.0.0.1` | HTTP / `127.0.0.1` | HTTP / `127.0.0.1` | Actual protocol and bind authority | Actual protocol and bind authority | Actual protocol and bind authority | Actual protocol and bind authority | Actual protocol and bind authority | Actual protocol and bind authority |
29
- | Plugin's single `publicUrl` entry · [DSH-PUBLIC-001](#dsh-public-001) | Supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported | Supported |
30
- | Native `--public-url` option · [DSH-PUBLIC-001](#dsh-public-001) | Absent | Absent | Absent | Absent | Native | Native | Native | Native | Native | Native | Native |
31
- | Model-facing Web address · [DSH-PUBLIC-001](#dsh-public-001) | Native loopback text section | Native loopback text section | Native loopback text section | Native loopback text section | Final public root in text section | Final public root in text section | Final public root in runtime context | Final public root in runtime context | Final public root in runtime context | Final public root in runtime context | Final public root in runtime context |
32
- | `DSH_WEB_URL` · [DSH-PUBLIC-001](#dsh-public-001) | Native loopback address | Native loopback address | Native loopback address | Native loopback address | Final public root | Final public root | Final public root | Final public root | Final public root | Final public root | Final public root |
33
- | Radius and focus theme tokens · [DSH-THEME-001](#dsh-theme-001) | Plugin fallback | Native | Native | Native | Native | Native | Native | Native | Native | Native | Native |
34
- | Toggle switch thumb token · [DSH-THEME-001](#dsh-theme-001) | Plugin fallback | Plugin fallback | Native | Native | Native | Native | Native | Native | Native | Native | Native |
35
- | Listener transaction context after HMR · [DSH-HMR-001](#dsh-hmr-001) | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation | Plugin isolation |
36
- | Settings entry · [DSH-TEST-001](#dsh-test-001) | Sidebar Settings | Sidebar Settings | Sidebar Settings | Sidebar Settings | Sidebar Settings | Sidebar Settings | Account menu → Settings | Account menu → Settings | Account menu → Settings | Account menu → Settings | Account menu → Settings |
37
- | Exact first-run notice/reload triggers · [DSH-TEST-001](#dsh-test-001) | Unverified; keep helper | Unverified; keep helper | Unverified; keep helper | Unverified; keep helper | Unverified; keep helper | Unverified; keep helper | Account onboarding adapted; notice/reload triggers unverified | Account onboarding and host-release prompt verified; other triggers unverified | Account onboarding and host-release prompt verified; other triggers unverified | Account onboarding and host-release regression target; other triggers unverified | Account onboarding and host-release regression target; other triggers unverified |
38
- | Native official-account provider · [DSH-ACCOUNT-001](#dsh-account-001) | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only | Present; loopback HTTP only |
39
- | Plain-Web official-account entry · [DSH-ACCOUNT-001](#dsh-account-001) | Disabled; Desktop only | Disabled; Desktop only | Disabled; Desktop only | Disabled; Desktop only | Disabled; Desktop only | Disabled; Desktop only | Enabled | Enabled | Enabled | Enabled | Enabled |
40
- | Native `startSignIn` first argument · [DSH-ACCOUNT-001](#dsh-account-001) | Locale string | Client metadata object | Client metadata object | Client metadata object | Client metadata object | Client metadata object | Client metadata object | Client metadata object | Client metadata object | Client metadata object | Client metadata object |
41
- | Plugin manual account callback · [DSH-ACCOUNT-001](#dsh-account-001) | Disabled | Disabled | Disabled | Disabled | Disabled | Disabled | Plugin enabled; native API-key choice retained; waits for preference | Plugin enabled; native API-key choice retained; waits for preference | Plugin enabled; native API-key choice retained; waits for preference | Plugin enabled; native API-key choice retained; waits for preference | Plugin enabled; native API-key choice retained; waits for preference |
42
- | Plugin `0.1.5` configuration migration · [PLUGIN-CONFIG-001](#plugin-config-001) | Retained | Retained | Retained | Retained | Retained | Retained | Retained | Retained | Retained | Retained | Retained |
27
+ These rows identify adaptations or migrations and their exact applicable hosts. Historical native facts remain in each stable entry; retirement removes exclusive implementation, not shared security checks.
28
+
29
+ | Entry | Exact applicable DSH versions | Candidate disposition |
30
+ | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
31
+ | [DSH-HOST-001](#dsh-host-001), old IPv4 schema/TLS rejection | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` | No support intersection; exclusive implementation/tests removed in `0.3.1`; native Config and concrete binding retained |
32
+ | [DSH-PROTOCOL-001](#dsh-protocol-001), HTTP/loopback bridge | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` | No support intersection; fallback removed; actual protocol, normalized authority and Secure separation retained |
33
+ | [DSH-PUBLIC-001](#dsh-public-001), missing CLI option | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2` | No support intersection; missing-option and loopback projection paths removed |
34
+ | [DSH-PUBLIC-001](#dsh-public-001), text projection | `0.2.1-alpha.1`, `0.2.1-alpha.2` | No support intersection; text selection removed; context and environment checked, sections still observed for leaks/duplicates |
35
+ | [DSH-THEME-001](#dsh-theme-001), radius fallback | `0.1.7-rc.1` | No support intersection; old radius fallbacks removed; native themes/visual checks retained |
36
+ | [DSH-THEME-001](#dsh-theme-001), switch-thumb fallback | `0.1.7-rc.1`, `0.1.7-rc.2` | No support intersection; fallbacks removed in `0.3.1`; native tokens and visual/focus checks retained |
37
+ | [DSH-THEME-001](#dsh-theme-001), focus-color migration | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` | Migrated using exact native rules and minimum/default UI evidence; visible keyboard focus retained |
38
+ | [DSH-TEST-001](#dsh-test-001), direct Settings navigation | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2` | No support intersection; direct entry removed in `0.3.1`; account-menu navigation and generic asynchronous retries retained |
39
+ | [DSH-ACCOUNT-001](#dsh-account-001), manual loopback callback | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` | Retained; no server-side old-version branch after global admission; exported helper still checks optional/invalid/older version inputs |
40
+ | [DSH-HMR-001](#dsh-hmr-001), listener context isolation | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` | Retained for supported exact hosts; only retired matrix targets removed |
41
+ | [DSH-RESOURCE-001](#dsh-resource-001) | `0.2.2-alpha.2` | Retain instance-private HTTP resource gate; native in-process peer reads unchanged |
42
+ | [DSH-LIVESHARE-001](#dsh-liveshare-001) | `0.2.2-alpha.2` | Public peer/baseline isolation and connection/request business Origin restoration; local native HTTPS/proxy Relay protocol round trips verified |
43
+ | [PLUGIN-CONFIG-001](#plugin-config-001) | Plugin `0.1.5` allowedOrigins input, independent of DSH versions | Retained under its own contract |
44
+ | [PLUGIN-LOCALE-001](#plugin-locale-001) | Plugin `0.3.2`; independent of DSH versions | New memory contract; old key ignored/retained/not migrated |
45
+ | [PLUGIN-CLI-001](#plugin-cli-001) | Plugin `0.3.2`; independent of DSH versions | Fixed English; earlier --lang ended by plugin policy |
43
46
 
44
47
  ## Version → feature matrix
45
48
 
46
- Each row identifies the exact release's branches and relevant entries. The native `startSignIn` first argument is a locale string on `0.1.7-rc.1` and a client metadata object on `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` and `0.2.1-rc.2`. Before removing support, find its row and inspect each entry's complete applicable set. Removing one row does not necessarily retire an entire entry.
47
-
48
- | Exact DSH version | Listener and bridge differences | Native public address, model prompt and environment | Theme and Settings entry | Official account and manual callback | Entries to review on removal or migration |
49
- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
50
- | `0.1.7-rc.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1`; isolate listener transaction context after native HMR | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Radius/focus and switch thumb need fallback; sidebar Settings; notice/reload triggers unverified | Native account service present; plain-Web entry disabled; manual callback disabled | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-THEME-001, DSH-TEST-001, DSH-HMR-001 |
51
- | `0.1.7-rc.2` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1`; isolate listener transaction context after native HMR | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Native radius/focus; switch thumb fallback; sidebar Settings; notice/reload triggers unverified | Native account service present; plain-Web entry disabled; manual callback disabled | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-THEME-001, DSH-TEST-001, DSH-HMR-001 |
52
- | `0.2.0-rc.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1`; isolate listener transaction context after native HMR | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Native radius/focus and switch thumb; sidebar Settings; notice/reload triggers unverified | Native account service present; plain-Web entry disabled; manual callback disabled | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
53
- | `0.2.0-rc.2` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1`; isolate listener transaction context after native HMR | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Native radius/focus and switch thumb; sidebar Settings; notice/reload triggers unverified | Native account service present; plain-Web entry disabled; manual callback disabled | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
54
- | `0.2.1-alpha.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1`; isolate listener transaction context after native HMR | Native `--public-url`; model text and `DSH_WEB_URL` use the plugin's final public root | Native radius/focus and switch thumb; sidebar Settings; notice/reload triggers unverified | Native account service present; plain-Web entry disabled; manual callback disabled | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
55
- | `0.2.1-alpha.2` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority; isolate listener transaction context after native HMR | Native `--public-url`; model text and `DSH_WEB_URL` use the plugin's final public root | Native radius/focus and switch thumb; sidebar Settings; notice/reload triggers unverified | Native account service present; plain-Web entry disabled; manual callback disabled | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
56
- | `0.2.1-alpha.3` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority; port type permits an unbound value, requiring validation after listening; isolate listener transaction context after native HMR | Native `--public-url`; model address in `app:web-surface` runtime context; `DSH_WEB_URL` uses final public root | Native radius/focus and switch thumb; account menu → Settings; account onboarding adapted, notice/reload triggers unverified | Native loopback HTTP origins only; instruction dialog and manual callback enabled; API-key choice retained; waits for preference | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-ACCOUNT-001, DSH-HMR-001 |
57
- | `0.2.1-alpha.4` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority; port type permits an unbound value, requiring validation after listening; isolate listener transaction context after native HMR | Native `--public-url`; model address in `app:web-surface` runtime context; `DSH_WEB_URL` uses final public root | Native radius/focus and switch thumb; account menu → Settings; account onboarding and host-release prompt verified; other triggers unverified | Native loopback HTTP origins only; instruction dialog and manual callback enabled; API-key choice retained; waits for preference | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-ACCOUNT-001, DSH-HMR-001 |
58
- | `0.2.1-alpha.5` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority; port type permits an unbound value, requiring validation after listening; isolate listener transaction context after native HMR | Native `--public-url`; model address in `app:web-surface` runtime context; `DSH_WEB_URL` uses final public root | Native radius/focus and switch thumb; account menu → Settings; account onboarding and host-release prompt verified; other triggers unverified | Native loopback HTTP origins only; instruction dialog and manual callback enabled; API-key choice retained; waits for preference | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-ACCOUNT-001, DSH-HMR-001 |
59
- | `0.2.1-rc.1` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority; port type permits an unbound value, requiring validation after listening; isolate listener transaction context after native HMR | Native `--public-url`; model address in `app:web-surface` runtime context; `DSH_WEB_URL` uses final public root | Native radius/focus and switch thumb; account menu → Settings; account onboarding and host-release regression target; other triggers unverified | Native loopback HTTP origins only; instruction dialog and manual callback enabled; API-key choice retained; waits for preference | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-ACCOUNT-001, DSH-HMR-001 |
60
- | `0.2.1-rc.2` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority; port type permits an unbound value, requiring validation after listening; isolate listener transaction context after native HMR | Native `--public-url`; model address in `app:web-surface` runtime context; `DSH_WEB_URL` uses final public root | Native radius/focus and switch thumb; account menu → Settings; account onboarding and host-release regression target; other triggers unverified | Native loopback HTTP origins only; instruction dialog and manual callback enabled; API-key choice retained; waits for preference | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-ACCOUNT-001, DSH-HMR-001 |
61
-
62
- `PLUGIN-CONFIG-001` and shared security boundaries apply to every row and cannot be retired by dropping a DSH release. Unlisted future releases need separate regression evidence before being called verified; the forward admission rule for `DSH-ACCOUNT-001` does not establish that evidence.
49
+ Historical rows stay searchable; a retired row is not a current positive target. All supported rows use native concrete IPv4/IPv6, HTTP/HTTPS, context projection, native radius/thumb tokens and focus rules and account-menu Settings. Exact published code/API evidence is recorded below; final same-archive runtime evidence is separate.
50
+
51
+ | Exact DSH version | Candidate state | Historical adaptations / retained shared checks |
52
+ | ----------------- | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
53
+ | `0.1.7-rc.1` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-THEME-001, DSH-TEST-001, DSH-HMR-001; historical locale-string startSignIn argument |
54
+ | `0.1.7-rc.2` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-THEME-001, DSH-TEST-001, DSH-HMR-001; metadata-object startSignIn argument |
55
+ | `0.2.0-rc.1` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
56
+ | `0.2.0-rc.2` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001 |
57
+ | `0.2.1-alpha.1` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001; native public URL text |
58
+ | `0.2.1-alpha.2` | Retired in `0.3.1`; last plugin `0.2.0` | DSH-PUBLIC-001, DSH-TEST-001, DSH-HMR-001; native transport and public URL text |
59
+ | `0.2.1-alpha.3` | Legacy; minimum supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation, context/env and general onboarding regressions retained; missing native release metadata |
60
+ | `0.2.1-alpha.4` | Legacy | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings and real host-release prompt regression retained |
61
+ | `0.2.1-alpha.5` | Legacy | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings and real host-release prompt regression retained |
62
+ | `0.2.1-rc.1` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings and real host-release prompt regression retained |
63
+ | `0.2.1-rc.2` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings, host-release and Search/Fetch regression retained |
64
+ | `0.2.1-rc.3` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings; real UI/Search/Fetch/host-release regression registered; final evidence separate |
65
+ | `0.2.1-rc.4` | Supported | DSH-THEME-001, DSH-ACCOUNT-001, DSH-HMR-001; native validation/context/env/theme/Settings; real UI/Search/Fetch/host-release regression registered; final evidence separate |
66
+ | `0.2.2-alpha.2` | `0.3.2` unpublished candidate declaration; default/manual recommendation | DSH-RESOURCE-001, DSH-LIVESHARE-001, DSH-ACCOUNT-001, DSH-HMR-001, DSH-THEME-001; shared native validation/context/theme/Settings checks retained; final same-archive reports separate |
67
+
68
+ 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.
63
69
 
64
70
  ## Capability migration and retirement workflow
65
71
 
@@ -71,66 +77,76 @@ Each row identifies the exact release's branches and relevant entries. The nativ
71
77
 
72
78
  ## DSH-HOST-001
73
79
 
74
- Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Active.
80
+ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Exclusive adaptation retired in plugin `0.3.1`; shared native validation remains.
75
81
 
76
82
  | Field | Maintenance basis |
77
83
  | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
78
84
  | 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 |
79
- | 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` and `0.2.1-rc.2` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
85
+ | Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
80
86
  | 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 |
81
87
  | 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 |
82
88
  | 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 |
83
89
 
90
+ 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.
91
+
84
92
  ## DSH-PROTOCOL-001
85
93
 
86
- Native protocol and Connection bind-authority differences. Type: `dsh-runtime`. Active.
94
+ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`. Exclusive adaptation retired in plugin `0.3.1`; shared native validation remains.
87
95
 
88
96
  | Field | Maintenance basis |
89
97
  | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
90
98
  | 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 |
91
- | Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-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 |
99
+ | Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2` use the actual protocol and normalized bind authority. IPv6 zones must not enter portable public URLs; mapped IPv6 must match Connection's WHATWG comparison |
92
100
  | 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 |
93
101
  | 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 |
94
102
  | 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 |
95
103
 
96
104
  Outer Cookie Secure follows the public origin; native Cookie Secure follows the listener protocol. This is shared security behavior, independent of a version fallback's retirement.
97
105
 
106
+ 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.
107
+
98
108
  ## DSH-PUBLIC-001
99
109
 
100
- Public URL projection and model prompt location differences. Type: `dsh-runtime`. Active.
110
+ Public URL projection and model prompt location differences. Type: `dsh-runtime`. Exclusive adaptation retired in plugin `0.3.1`; shared native validation remains.
101
111
 
102
112
  | Field | Maintenance basis |
103
113
  | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
104
114
  | 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 |
105
115
  | 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 |
106
- | Native context projection versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-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 |
116
+ | Native context projection versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2` publish the model address through `webApp.getAdvertisedUrl()` and harness-dev-context's `app:web-surface`, in `assembly.contexts`; `DSH_WEB_URL` still uses the final public root |
107
117
  | 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 |
108
118
  | 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 |
109
- | 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` and `0.2.1-rc.2`. A new projection location does not change how another supported release must be observed |
119
+ | Migration and retirement | Remove missing-option branches and CLI rejection tests when their applicable set leaves support. Keep text-location assertions while `0.2.1-alpha.1` or `0.2.1-alpha.2` remains supported and context assertions for `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2`. A new projection location does not change how another supported release must be observed |
120
+
121
+ 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.
110
122
 
111
123
  ## DSH-THEME-001
112
124
 
113
- CSS fallback for missing theme tokens. Type: `dsh-runtime`. Active.
125
+ CSS fallback for missing theme tokens. Type: `dsh-runtime`. Retired in plugin `0.3.1`; native tokens and shared visual checks remain.
114
126
 
115
127
  | Field | Maintenance basis |
116
128
  | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
117
- | Fallback version | `0.1.7-rc.1` lacks `--dsw-radius-md`, `--dsw-radius-lg` and `--dsw-focus-ring-color`; `0.1.7-rc.1` and `0.1.7-rc.2` lack `--dsw-alias-switch-thumb` |
118
- | Native capability versions | `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` and `0.2.1-rc.2` provide the radius/focus tokens. `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` and `0.2.1-rc.2` also provide the switch thumb token |
119
- | Implementation and upstream | `var()` fallbacks in `src/client/settings/style.css` and `src/client/account/style.css`; CSS token definitions embedded in exact `@deepseek-ai/dsh-client-ui-theme/lib` packages. The button switch uses the native track/thumb shape; its missing thumb token falls back to the existing foreground token. Account and security task dialogs share surface, radius, focus and control styling |
129
+ | Fallback version | Historical `0.3.1` migration: Old radius-md/lg apply to `0.1.7-rc.1`, switch-thumb to `0.1.7-rc.1`, `0.1.7-rc.2`; duplicate focus-color fallback migrates using native rules on all seven |
130
+ | Native capability versions | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` each provide radius/thumb definitions and the same native focus rules; focus-ring-color is an optional override, not a guaranteed keyboard-mode root token. Historical radius is confirmed from `0.1.7-rc.2`, thumb from `0.2.0-rc.1` |
131
+ | 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 |
120
132
  | 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. |
121
- | Migration and retirement | Remove radius/focus fallbacks only after `0.1.7-rc.1` leaves support and remaining exact-version evidence is complete. Retain the switch-thumb fallback while either `0.1.7-rc.1` or `0.1.7-rc.2` remains supported. Keep live themes, layout, visible focus and shared visual verification |
133
+ | Migration and retirement | Remove exclusive radius/thumb fallbacks once their old applicable sets leave support. Focus color on all eight has migrated to native rules without directly reading an undefined override. Keep live themes, layout, visible focus, switch appearance and shared visual tests |
134
+
135
+ 2026-10-28 cleanup: the exact old radius, switch-thumb and direct Settings sets in the matrix have no support intersection; exclusive implementations are removed. The duplicate focus-color fallback migrates using seven-version native rules without assuming a normal-mode focus-ring-color. Generic onboarding/reopen/persistence retries and shared visual assertions remain.
136
+
137
+ Exact focus evidence correction (2026-10-28): all seven native focus.css rules resolve `var(--dsw-focus-ring-color, var(--dsw-alias-state-business-primary))` on :focus-visible. focus-ring-color is an optional pointer-mode override, not a default root token. Declaration text does not prove a value in normal keyboard mode. The plugin now sets only solid outline shape with native `--dsw-focus-ring-width`, delegating color to the host global rule. This removes the duplicate plugin fallback while retaining visible keyboard focus; cleanup does not mean directly referencing an undefined override.
122
138
 
123
139
  ## DSH-TEST-001
124
140
 
125
- Settings navigation and first-run test adaptations. Type: `dsh-runtime`. Active; exact notice/reload trigger applicability remains incomplete.
141
+ 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.
126
142
 
127
- | Field | Maintenance basis |
128
- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
129
- | 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 |
130
- | Account-menu version | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-rc.2` use account menu → Settings and official-account onboarding. The manual dialog lives outside sidebar/onboarding entries so rebuilding an entry does not cancel pending authorization |
131
- | 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` and `0.2.1-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 |
132
- | 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` |
133
- | 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 |
143
+ | Field | Maintenance basis |
144
+ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
145
+ | Direct Settings versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` and `0.2.1-alpha.2` use sidebar Settings and API-key onboarding |
146
+ | Account-menu version | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` use account menu → Settings and native account onboarding. The manual sign-in overlay adds no alternate Settings entry; generic asynchronous retries remain. |
147
+ | Evidence gap | For `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2`, the per-trigger mapping of delayed notice, replacement during acknowledgement, first API-key save and page reload is incomplete. Shared helper success does not establish every trigger independently on each release |
148
+ | Implementation and tests | `openDshSettings`, `completeApiKeyPrompt`, `clickThroughDshPrompts` and reopen in `tests/helpers/runtime.ts`; `tests/browser/dsh-bootstrap.spec.ts`, `tests/browser/dsh-gate.spec.ts`, `tests/browser/account-login.spec.ts` |
149
+ | Migration and retirement | First establish exact applicability of each interaction through real UI evidence, then remove exclusive branches by support-set intersection. General async retries, persistence waits and browser fallbacks are not automatically exclusive to any DSH release |
134
150
 
135
151
  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.
136
152
 
@@ -138,50 +154,99 @@ On `0.2.1-alpha.3`, the 2026-10-15 CI run and a local reproduction with `DEEPSEE
138
154
 
139
155
  On 2026-10-16, `tests/browser/host-release.spec.ts` retained a `0.2.1-alpha.4` page while switching the actual Host to `0.2.1-alpha.3` in the same isolated profile and port. The native service-version prompt appeared; `0.2.1-alpha.3` publishes no release metadata, so the destination correctly reads unknown. Native reload rechecked authentication and preserved the original session and profile switch; restoring `0.2.1-alpha.4` passed again. The test prepares the exact older runtime itself and changes no upstream source, version or graph metadata. This exact case does not close the other notice/first-save trigger gaps.
140
156
 
157
+ 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.
158
+
141
159
  ## DSH-ACCOUNT-001
142
160
 
143
161
  Manual official-account callback handoff. Type: `dsh-runtime`. Active; an independently removable temporary adaptation.
144
162
 
145
163
  | Field | Maintenance basis |
146
164
  | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
147
- | 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` and `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-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 |
165
+ | Native capability versus plugin scope | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1` and `0.2.1-alpha.2` already ship account providers/APIs, but ui-settings-account `apply` returns immediately without `dshDesktop`. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2` enable that UI for plain Web. The plugin admits the adapter from `0.2.1-alpha.3` subject to capability and configuration checks; a disabled plugin adapter does not mean native account capability is absent |
148
166
  | 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. |
149
- | Explicitly disabled 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`; missing native capabilities also return unavailable. A false preference returns `account_disabled` for new starts and preserves already admitted attempts. |
167
+ | 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 |
150
168
  | Reason and upstream | Account-platform `protocol.ts/loginOrigin` in every exact installed release listed above accepts only loopback HTTP with an explicit port; ui-settings-account defaults to the browser origin. A public browser cannot automatically callback to the DSH machine, and the outer gate rejects cross-site navigation |
151
169
  | Implementation | `src/shared/account-login.ts`, `src/http/account-login.ts`, `src/adapters/dsh/account-callback.ts`, `src/adapters/dsh/browser-capability.ts`, `src/client/account/`. Public slot entries/subscribe/priority APIs replace the sign-in action; independent `shell.overlay` renders instructions, input and buttons. Native `useApiKey` continues credential onboarding without calling `complete`; the account menu reopens the editor through `openOnboarding`. Inactive authorization offers this choice; active authorization retains cancellation. The server binds the initiating session and retains the native temporary callback handler, dispatched internally only from authenticated POST with a real in-memory Node response. It never fetches the pasted URL, reads private provider state or replaces native PKCE/credential storage. Dynamic configuration preserves the Loader reference. Callback capture blocks direct manual callbacks only while a manual attempt owns the handler; otherwise it delegates to the native handler through the existing outer gate. No preference change cancels an attempt or unloads the provider. The compact dialog shows two initial steps and hides completed instructions during authorization; API-key choice, failed-navigation guidance and expiry feedback remain available. Direct callback ownership is checked against the public provider view, so native cancellation followed by a new native authorization restores its callback even before a plugin state poll. Rejected cancellation retains ownership until the public view proves a terminal or different attempt, and permits cancellation cleanup to retry. `src/index.ts` attempts every shutdown resource in order before reporting cleanup errors, retaining the state lock until request and connection cleanup has been attempted. Configuration retries use the native mirror ensure API before its first accepted document and the explicitly injected remote.settings transport for a held namespace. Menu sign-in waits for an unknown preference to settle, then chooses manual or native routing from the latest accepted value. |
152
- | Tests | `tests/integration/account-login.test.ts` uses the real `0.2.1-rc.2` provider from pinned development dependencies and local Platform stand-in for PKCE, redirect URI, state, session, duplicate submission, cancellation, revocation, expiry and retries. Public cancellation fault injection verifies that a live manual callback remains blocked; shutdown failure regression checks listener and admin socket closure and reacquisition of the same profile lock. `tests/browser/account-login.spec.ts` covers credential-free onboarding with `DEEPSEEK_API_KEY` unset, native API-key save and menu reopening, instructions before authorization, pasted failed-navigation callbacks, blocked popups and responsive bilingual 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. |
170
+ | Tests | `tests/integration/account-login.test.ts` uses the real `0.2.2-alpha.2` provider from pinned development dependencies and local Platform stand-in for PKCE, redirect URI, state, session, duplicate submission, cancellation, revocation, expiry and retries. Public cancellation fault injection verifies that a live manual callback remains blocked; shutdown failure regression checks listener and admin socket closure and reacquisition of the same profile lock. `tests/browser/account-login.spec.ts` covers credential-free onboarding with `DEEPSEEK_API_KEY` unset, native API-key save and menu reopening, instructions before authorization, pasted failed-navigation callbacks, blocked popups and responsive eight-language themes. `tests/unit/client-capability.test.ts` checks SemVer admission and rejects invalid/older versions. `tests/browser/live-config.spec.ts` and `tests/fixtures/live-config-observer.mjs` observe real Loader reference/fiber, listener, profile lock, long connections and restart persistence; final cross-version results belong to the execution record. Additional browser cases cover initial describe failure and full-mirror recovery, retry of a temporarily missing namespace through the injected transport, and delayed true/false preferences without premature native authorization. Plugin dictionaries do not expand old native language catalogs. |
153
171
  | 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. |
154
- | Retirement and preservation | Retain the adaptation while supported `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` or `0.2.1-rc.2` needs loopback. Only when its applicable set leaves support, or each exact native public flow is verified usable, remove exclusive callback/UI/flag code and tests. Keep session ownership, state/PKCE, one-time use, revocation and prohibition on URL forwarding wherever shared by another flow |
172
+ | Retirement and preservation | `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` still need loopback, so retain the adapter. Remove exclusive code only when the applicable set leaves support or each supported exact native public flow is verified. Keep shared state/PKCE, session ownership, one-time use, revocation and no URL forwarding |
155
173
  | 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 |
156
174
 
175
+ 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.
176
+
177
+ 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.
178
+
157
179
  ## DSH-HMR-001
158
180
 
159
181
  Long-lived listener transaction-context isolation after native hot reload. Type: `dsh-runtime`. Active.
160
182
 
161
- | Field | Maintenance basis |
162
- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
163
- | 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` |
164
- | 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. |
165
- | 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. |
166
- | Tests and evidence | `tests/browser/account-login.spec.ts`, `tests/fixtures/hmr-config-probe.mjs`. On `0.2.1-alpha.3`, changing installed code and letting native profile watching replace it reproduced and fixed the reported settings/rejected “HMR transactions cannot be nested”. Real configuration-HMR/queue regressions passed for `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3` and `0.2.1-alpha.4`: listener generation increased, independent saves waited for an existing transaction, genuine nesting remained rejected and the original session stayed valid. Installed-code replacement followed by re-enabling also passed on `0.2.1-alpha.3` and `0.2.1-alpha.4`. The 2026-10-16 targeted run passed 10/10. Future releases do not inherit these exact-version conclusions. Current module-replacement regression also targets `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-rc.2`; exact commands, counts and final-artifact results are recorded separately. |
167
- | 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. |
183
+ | Field | Maintenance basis |
184
+ | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
185
+ | Adapted versions | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` and `0.2.2-alpha.2` |
186
+ | Native behavior and static evidence | Individually inspected exact `@deepseek-ai/dsh-hmr/lib/index.js` on 2026-10-16: `runExclusive` implementations for `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3` and `0.2.1-alpha.4` reject nesting through a private `executing: AsyncLocalStorage` boolean marker. Native `watchConfig` itself creates long-lived watchers with `executing.exit`. HTTP/HTTPS listeners created inside a reload transaction pass the stale marker to later independent requests. Exact `0.2.1-alpha.5` JavaScript and types were rechecked on 2026-10-19 and are byte-identical to `0.2.1-alpha.4`; no public listener-isolation API was added. Exact published `0.2.2-alpha.2` still uses private `executing: AsyncLocalStorage` with a true marker and runExclusive nesting rejection, with no public listener-isolation API; method names do not prove future semantics. |
187
+ | Implementation boundary | `src/adapters/dsh/hmr-context.ts`, `src/index.ts`: only during native listener initialization, call `exit` after checking `runExclusive`, native AsyncLocalStorage identity and a current true marker. This explicitly depends on a private field shape; there is no equivalent public API. An absent shape or marker retains native initialization. Do not replace the HMR queue or exit transactions in Settings saves/request dispatch; genuine nested calls remain rejected. |
188
+ | Tests and evidence | `tests/browser/account-login.spec.ts`, `tests/fixtures/hmr-config-probe.mjs`. On `0.2.1-alpha.3`, changing installed code and letting native profile watching replace it reproduced and fixed the reported settings/rejected “HMR transactions cannot be nested”. Real configuration-HMR/queue regressions passed for `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.1-alpha.3` and `0.2.1-alpha.4`: listener generation increased, independent saves waited for an existing transaction, genuine nesting remained rejected and the original session stayed valid. Installed-code replacement followed by re-enabling also passed on `0.2.1-alpha.3` and `0.2.1-alpha.4`. The 2026-10-16 targeted run passed 10/10. Future releases do not inherit these exact-version conclusions. Current module-replacement regression also targets `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3` and `0.2.1-rc.4`; exact commands, counts and final-artifact results are recorded separately. On `0.2.2-alpha.2`, `tests/fixtures/hmr-lifecycle-probe.mjs` and the browser fault case observe import failure retaining the same instance; failure after genuine initialization disposes old/failed instances and native rollback creates a new fiber using the old implementation. Subsequent successful replacement, first Settings write, real mux closure, lock release/reacquisition and persisted authentication are covered. Final same-archive reports are separate. |
189
+ | Migration and retirement | Prefer a public upstream isolation API after exact-version evidence and migration. Remove exclusive implementation/tests only when native isolation is fixed on every remaining supported adapted release, or when the adapted and supported sets no longer intersect. Update both languages and matrix directions together. Keep authentication, origin checks, the native queue, genuine nesting rejection and regression coverage. |
190
+
191
+ ## DSH-RESOURCE-001
192
+
193
+ Native HTTP resource admission. Type: `dsh-runtime`. Added in unpublished plugin `0.3.2`.
194
+
195
+ | Field | Maintenance basis |
196
+ | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
197
+ | Exact adapted versions | `0.2.2-alpha.2`; intersects the eight-target candidate set, so retain. `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4` retain handler registration admission. |
198
+ | Native shape and order | Exact published `@deepseek-ai/dsh-host-webserver@0.2.2-alpha.2`, `lib/index.js` lines 427–440, 456–471, 599–628; source tag `dsh-v0.2.2-alpha.2` (`f3803c96974ad4a94195fb97e5c637e9c2a3afe3`). Named and fallback resources dispatch before handlers. Private `serveResource(req, res, target, resource)` converts Node headers to Fetch Headers and owns the native response bridge. The constructor installs the wrapper before listener initialization or resource registration. Method existence alone does not establish future semantics. |
199
+ | Implementation | `src/adapters/dsh/webserver.ts`: capture the native function on one instance and preserve `this`; run the gate before conversion, rebuild target from the admitted `req.url` after root-token removal, then delegate. Do not modify the prototype, copy routing/stream code, wrap a resource as a handler, fabricate owner identity or gate `readResource(request, peer)`. Handler and upgrade gates remain. |
200
+ | 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. |
201
+ | Tests | `tests/integration/dsh-adapter.test.ts`: native named/fallback mixed registration, one HTTP gate, unchanged prototype, in-process exact/longest-prefix/fallback, peer identity, handler shadowing, HEAD, disposal and errors. `tests/integration/http-gate.test.ts`: real raw headers, cookies/origin/session/readiness, PWA limits, token target, methods/ETag/Set-Cookie, delayed Response revocation, native bytes/backpressure/cancellation and errors. Candidate full-archive results are recorded separately. `tests/browser/native-transport.spec.ts` compares genuine native asset/fallback bytes and ETag GET/HEAD/304, denying anonymous/revoked correct-tag requests; bundle/map/chunk retain immutable 200 and index has no immutable/max-age policy, without imposing nonexistent ETag/304 behavior. |
202
+ | Migration and retirement | Prefer a future public pre-resource HTTP admission API only after exact-version evidence establishes the same raw-request and lifecycle boundary. Migrate releases individually; retain the private path while any supported applicable release still requires it. Remove exclusive implementation/tests only after that intersection is empty or every remaining adapted release has migrated. Keep shared auth, raw-header, origin, readiness, revocation and stream checks. |
203
+
204
+ 2026-10-28 candidate intersection review: DSH-HOST-001, DSH-PROTOCOL-001, the retired paths in DSH-PUBLIC-001/DSH-THEME-001/DSH-TEST-001 remain retired with unchanged exact historical sets; no adaptation is retired again. DSH-ACCOUNT-001 and DSH-HMR-001 remain required on `0.2.2-alpha.2` as confirmed by its exact published loopback/AsyncLocalStorage code, as well as `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`. PLUGIN-CONFIG-001 remains under its own policy. No historical evidence gaps are closed by this admission.
205
+
206
+ ## DSH-LIVESHARE-001
207
+
208
+ Public peer admission and owner-login business Origin. Type: `dsh-runtime`. Added in unpublished plugin `0.3.2` for exact DSH `0.2.2-alpha.2`.
209
+
210
+ | Field | Maintenance basis |
211
+ | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
212
+ | 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. |
213
+ | 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. |
214
+ | 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. |
215
+ | Tests and limits | `tests/unit/client-capability.test.ts`, `tests/browser/liveshare.spec.ts`, `tests/fixtures/liveshare-viewer.mjs` and `liveshare-client-observer.js` establish real native viewer carrier/index and full-client isolation. `tests/integration/liveshare-origin.test.ts` checks public waterfall header restoration, strict selection and fiber disposal/reload with real Node request objects; `tests/helpers/liveshare-relay.ts` and `tests/fixtures/liveshare-session.mjs` provide the local protocol/probe without replacing Host services. Local Relay protocol runs cover native HTTPS and HTTPS→HTTP ingress, actual Start/Redeem state/PKCE/cancel/retry, the native worker, create/list/stop, real viewer index/assets/carrier and accepted native viewer channel operations. Anonymous/revoked/bad/missing/duplicate-Origin and cross-site requests remain rejected by the outer gate; logout does not stop a share. The fixture replaces only Relay consent/identity/transport and uses the real plain-Node Host to serialize the shipped carrier. No real Relay/OAuth/product experience, real visitor model operation or file writing is established. |
216
+ | Migration and retirement | Retain while supported `0.2.2-alpha.2` requires these boundaries. Prefer a native public business-Origin contract after exact evidence and migration; retire exclusive implementation/tests only when every supported applicable host has migrated or the support intersection is empty. Keep shared admission, owner/viewer identity and lifecycle tests. |
168
217
 
169
218
  ## PLUGIN-CONFIG-001
170
219
 
171
- Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.2.0`, independent of the DSH version set.
220
+ Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.3.2`, independent of the DSH version set.
172
221
 
173
222
  | Field | Maintenance basis |
174
223
  | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
175
- | 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 plugin `0.2.0` retains it |
224
+ | Configuration contract | A single-item or empty top-level `allowedOrigins` array from plugin `0.1.5`; plugin `0.1.6` introduced in-memory migration and plugins `0.3.1` and `0.3.2` retain it |
176
225
  | 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 |
177
226
  | 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 |
178
227
  | 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 |
179
228
 
229
+ ## PLUGIN-LOCALE-001
230
+
231
+ Browser language memory migration. Type: `plugin-contract`, decided by plugin `0.3.2` independently of DSH retirement.
232
+
233
+ - Contract: `dsh-auth-remote-lang` → single `navigator.language` → en; en/zh/ja/es/fr/de/ru/pt (Brazilian Portuguese), with case-insensitive valid language/region matching. The standalone page has no selector and selects once. Ignore, retain and do not migrate old `dsh-auth-remote.locale`; signing out keeps the new key. Register dictionaries without expanding the native catalog.
234
+ - Implementation/tests: `src/shared/i18n.ts`, `src/client/login/index.ts`, `src/client/settings/locale-memory.ts`; `tests/unit/i18n.test.ts`, `tests/unit/locale-memory.test.ts`, `tests/browser/login.spec.ts`. Only owners subscribe to native ConfigForm, then immediately read it. Process preference only for ready + defined accepted value. Save strings verbatim; explicit absence removes the new key. Loading, failed reads/saves/storage and optimistic values do not overwrite accepted memory.
235
+ - Migration/retirement: a future key, selection-order or saving-contract change needs an explicit plugin migration and synchronized guides/tests. Reducing DSH support cannot end this contract.
236
+
237
+ ## PLUGIN-CLI-001
238
+
239
+ Fixed-English CLI. Type: `plugin-contract`; plugin `0.3.2` explicitly ends its earlier language option independently of DSH retirement.
240
+
241
+ - Contract: remove `--lang`, rather than changing zh to en. Every form is invalid before profile/prompt/data access; environment languages do not select text. JSON, exit codes, confirmation, secret input and administration protocol remain.
242
+ - Implementation/tests: `src/cli/messages.ts`, `src/cli/index.ts`, `tests/cli/admin-cli.test.ts`; CLI does not use browser dictionaries. `scripts/verify-retired.mjs` retains historical `--lang zh` and Chinese prompts for published `0.2.0`; current behavior does not rewrite that old package.
243
+ - Migration/retirement: users remove the old argument from scripts. Future CLI contract changes follow plugin policy, not the host support set.
244
+
180
245
  ## Shared security boundaries
181
246
 
182
- Protected remote deployments must independently disable native `webserver` in the profile patch. A skipped auth bundle cannot apply its own disable. `tests/browser/startup-compatibility.spec.ts` exercises actual bundle skipping and plugin-side runtime rejection on `0.2.1-rc.1` and `0.2.1-rc.2` using damaged isolated plugin copies, retaining Loader auditing and upstream packages. TCP, HTTP, readiness and WebSocket upgrade probes must all be refused; these fixtures establish rejection behavior only.
247
+ Remote profiles must independently disable native `webserver`. `tests/browser/startup-compatibility.spec.ts` covers Loader skip/plugin runtime rejection on eight hosts: a peer fault on minimum `0.2.1-alpha.3`, engines faults on the other seven. `scripts/verify-retired.mjs` uses separate old profiles for unmodified-candidate installation rollback and whole-package native peer skip, repeatedly requiring no TCP/HTTP/readiness/WebSocket listener while preserving upstream identity/auditing.
183
248
 
184
- Plugin `0.2.0` classifies maintenance in `src/shared/dsh-support.ts` from exact manifest declarations and explicit records. Six declared releases remain legacy, with no real retirement records or calendar-driven admission change. Startup warns once per exact version/state in a process, including configuration and module HMR; authentication, required APIs and package identity still decide whether service can run. Unit/integration coverage and the real legacy/normal HMR diagnostic checks in `tests/browser/account-login.spec.ts` verify this separation. See the [support policy](support-policy.md) for dates and retirement decisions.
249
+ `src/shared/dsh-support.ts` explicitly records three legacy Alphas, four normal RCs, normally supported `0.2.2-alpha.2` and six retired hosts in candidate `0.3.2`, with last plugin `0.2.0`. `retiredOn: 2026-10-28` is preparation date, not actual npm publication, and never drives shutdown. Process-wide/HMR deduplication, required APIs, host identity and shared security checks remain; README records current dates.
185
250
 
186
251
  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.
187
252
 
@@ -199,4 +264,8 @@ Historical 2026-10-16 admission evidence: exact tag `dsh-v0.2.1-alpha.4` (`86a40
199
264
 
200
265
  Historical 2026-10-19 alpha admission evidence: exact tag `dsh-v0.2.1-alpha.5` (`1517a4dbca0a2789ff1d41ba439600f8547d23fa`) and exact published packages establish the capabilities listed for the added release. Critical WebServer, Connection, Settings, Slots and HMR JavaScript and types are byte-identical to `0.2.1-alpha.4`. At that historical baseline, the plugin's development dependencies were pinned to Cordis `4.0.5-alpha.2` and Schemastery `3.18.5-alpha.2`. Exact host-runtime dependency compositions are recorded and verified separately. The `0.2.1-alpha.5` model-label Slot does not participate in authentication. New account notification titles, optional JSON metadata and stacked cards remain handled by the preserved native account menu, without a plugin copy of that implementation. All seven dsh-runtime entries still intersect the nine-release support set and are retained; PLUGIN-CONFIG-001 remains independent. `host-release.spec.ts` retains the real `0.2.1-alpha.4` → `0.2.1-alpha.3` → `0.2.1-alpha.4` case and adds `0.2.1-alpha.5` → `0.2.1-alpha.4` → `0.2.1-alpha.5` with known destination identity and reload checks. Existing notice/reload trigger gaps remain open. Same-final-artifact nine-release CLI, full browser, smoke and hash results are recorded separately; historical candidates and targeted runs do not establish those results.
201
266
 
202
- 2026-10-19 RC candidate admission: verified exact tags `dsh-v0.2.1-rc.1` (`1600d8a1e140dcde43a1a0941940a0480712c011`), `dsh-v0.2.1-rc.2` (`687f282e8625c6b8d11ff58211a90524be2e4317`) and npm package identities/integrities. Inspected `lib` JavaScript/types/CSS in nine host modules are identical to `0.2.1-alpha.5`: WebServer, Connection, Settings, Slots, account, account-platform, authorization, WebApp and HMR. Development pins Cordis `4.0.5` and Schemastery `3.18.5`; actual host compositions are recorded through installed dependency chains. Each of the seven dsh-runtime entries still intersects the eleven-release target set and is retained; PLUGIN-CONFIG-001 remains independent. No release actually retires here; the six legacy dates are in the [support policy](support-policy.md). Full real RC regressions, four host-switch mappings and final eleven-release same-archive evidence belong to separate execution records. Static identity is not runtime success; plugin `0.2.0` does not alter npm `0.1.10` historical support.
267
+ Historical 2026-10-19 RC candidate admission: verified exact tags `dsh-v0.2.1-rc.1` (`1600d8a1e140dcde43a1a0941940a0480712c011`), `dsh-v0.2.1-rc.2` (`687f282e8625c6b8d11ff58211a90524be2e4317`) and npm package identities/integrities. Inspected `lib` JavaScript/types/CSS in nine host modules are identical to `0.2.1-alpha.5`: WebServer, Connection, Settings, Slots, account, account-platform, authorization, WebApp and HMR. Development pins Cordis `4.0.5` and Schemastery `3.18.5`; actual host compositions are recorded through installed dependency chains. Each of the seven dsh-runtime entries still intersects the eleven-release target set and is retained; PLUGIN-CONFIG-001 remains independent. No release actually retires here; the six legacy dates are in the [support policy](support-policy.md). Full real RC regressions, four host-switch mappings and final eleven-release same-archive evidence belong to separate execution records. Static identity is not runtime success; plugin `0.2.0` does not alter npm `0.1.10` historical support.
268
+
269
+ Exact 2026-10-28 admission: `0.2.1-rc.3` tag `1f81c047fc48fa190a683e469daa699857e9afe8`, `0.2.1-rc.4` tag `504a01a9578abc2c6f1fb896b1dc322c9fe24f66` and archive identity/integrity were checked; nine critical lib trees match `0.2.1-rc.2`. Native focus.css is byte-identical on `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`. New RCs retain account loopback restrictions and private HMR executing/runExclusive shape; no native public authorization or public isolation replacement is established, so ACCOUNT/HMR remain. Search/Fetch, navigation and switching specialized runs passed; final same-archive evidence is separate.
270
+
271
+ The 2026-10-29 `0.3.2` intersection review changes no prior exclusive-path retirement. Exact new `0.2.2-alpha.2` source is tag `dsh-v0.2.2-alpha.2` (`f3803c96974ad4a94195fb97e5c637e9c2a3afe3`), using actual Cordis `4.0.6-alpha.1` / Schemastery `3.18.6-alpha.1`; older SDK facts remain unchanged. Real WebServer Config/protocol, WebApp `getAdvertisedUrl()`, harness-dev-context and native account metadata/loopback restrictions were inspected individually. Shared THEME evidence is inline `:focus-visible` at line 1473 of exact `@deepseek-ai/dsh-client-ui-theme@0.2.2-alpha.2/lib/client.js`, retaining `--dsw-focus-ring-color` fallback to `--dsw-alias-state-business-primary` and a transparent pointer override; file SHA-256 is `3f3b79545546d9cebee52d198aa49512c7a9d1db783d9f907db8f207a153e015`. This does not establish byte equality of entire theme packages. Current eight-host matrices and native cases define verification targets; final same-archive reports are recorded separately. Historical gaps remain, and local protocol stand-ins do not establish real-service experience.