dsh-auth-remote 0.1.9 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +32 -0
- package/CHANGELOG.zh-CN.md +32 -0
- package/CONTRIBUTING.md +3 -1
- package/CONTRIBUTING.zh-CN.md +3 -1
- package/README.md +49 -23
- package/README.zh-CN.md +37 -11
- package/cordis.patch.yml +4 -3
- package/dist/cli.js +91 -46
- package/dist/cli.js.map +2 -2
- package/dist/client.js +2880 -581
- package/dist/client.js.map +4 -4
- package/dist/index.js +201 -36
- package/dist/index.js.map +4 -4
- package/dist/login.css +2 -8
- package/dist/login.css.map +2 -2
- package/dist/login.js +80 -42
- package/dist/login.js.map +2 -2
- package/dist/types/adapters/dsh/account-callback.d.ts +3 -0
- package/dist/types/adapters/dsh/account-callback.d.ts.map +1 -1
- package/dist/types/adapters/dsh/hmr-context.d.ts +10 -0
- package/dist/types/adapters/dsh/hmr-context.d.ts.map +1 -0
- package/dist/types/auth/service.d.ts +2 -0
- package/dist/types/auth/service.d.ts.map +1 -1
- package/dist/types/auth/sessions.d.ts +2 -0
- package/dist/types/auth/sessions.d.ts.map +1 -1
- package/dist/types/config.d.ts +9 -3
- package/dist/types/config.d.ts.map +1 -1
- package/dist/types/http/account-login.d.ts +5 -3
- package/dist/types/http/account-login.d.ts.map +1 -1
- package/dist/types/index.d.ts +2 -2
- package/dist/types/index.d.ts.map +1 -1
- package/dist/types/shared/account-login.d.ts +2 -1
- package/dist/types/shared/account-login.d.ts.map +1 -1
- package/dist/types/shared/auth-contract.d.ts +2 -0
- package/dist/types/shared/auth-contract.d.ts.map +1 -1
- package/dist/types/shared/dsh-support.d.ts +38 -0
- package/dist/types/shared/dsh-support.d.ts.map +1 -0
- package/dist/types/shared/i18n.d.ts +78 -40
- package/dist/types/shared/i18n.d.ts.map +1 -1
- package/dist/types/shared/locales/en.d.ts +39 -20
- package/dist/types/shared/locales/en.d.ts.map +1 -1
- package/dist/types/shared/locales/zh.d.ts +39 -20
- package/dist/types/shared/locales/zh.d.ts.map +1 -1
- package/docs/deployment.md +26 -21
- package/docs/deployment.zh-CN.md +26 -21
- package/docs/development.md +74 -8
- package/docs/development.zh-CN.md +74 -8
- package/docs/legacy-compatibility.md +96 -64
- package/docs/legacy-compatibility.zh-CN.md +96 -64
- package/docs/releasing.md +40 -10
- package/docs/releasing.zh-CN.md +40 -10
- package/docs/support-history.md +97 -0
- package/docs/support-history.zh-CN.md +97 -0
- package/docs/support-policy.md +87 -0
- package/docs/support-policy.zh-CN.md +87 -0
- package/examples/web-profile-auth-remote.patch.yml +6 -3
- package/package.json +28 -17
|
@@ -2,56 +2,64 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](legacy-compatibility.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
Last reviewed: 2026-10-
|
|
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.
|
|
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.
|
|
6
8
|
|
|
7
9
|
## Scope and review rules
|
|
8
10
|
|
|
9
|
-
Plugin `0.1.
|
|
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.
|
|
10
12
|
|
|
11
13
|
- Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
|
|
12
14
|
- `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.
|
|
13
|
-
- `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.
|
|
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`.
|
|
14
16
|
- Missing exact-version evidence requires preserving implementation and recording the gap. Passing the same test on different releases does not prove identical implementation.
|
|
15
|
-
- 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
|
|
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.
|
|
16
18
|
|
|
17
19
|
## Feature → version matrix
|
|
18
20
|
|
|
19
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.
|
|
20
22
|
|
|
21
|
-
| 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`
|
|
22
|
-
| -------------------------------------------------------------------------------- | ---------------------------- | ---------------------------- | ---------------------------- | ---------------------------- | --------------------------------- | ---------------------------------- |
|
|
23
|
-
| Concrete IPv4 listener validation · [DSH-HOST-001](#dsh-host-001) | Plugin validation | Plugin validation | Plugin validation | Plugin validation | Plugin validation | Native validation | Native validation
|
|
24
|
-
| Native IPv6 listener · [DSH-HOST-001](#dsh-host-001) | Rejected | Rejected | Rejected | Rejected | Rejected | Native | Native
|
|
25
|
-
| Native HTTPS listener · [DSH-PROTOCOL-001](#dsh-protocol-001) | Rejected | Rejected | Rejected | Rejected | Rejected | Native | Native
|
|
26
|
-
| 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
|
|
27
|
-
| Plugin's single `publicUrl` entry · [DSH-PUBLIC-001](#dsh-public-001) | Supported | Supported | Supported | Supported | Supported | Supported | Supported
|
|
28
|
-
| Native `--public-url` option · [DSH-PUBLIC-001](#dsh-public-001) | Absent | Absent | Absent | Absent | Native | Native | Native
|
|
29
|
-
| 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
|
|
30
|
-
| `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
|
|
31
|
-
| Radius and focus theme tokens · [DSH-THEME-001](#dsh-theme-001) | Plugin fallback | Native | Native | Native | Native | Native | Native
|
|
32
|
-
|
|
|
33
|
-
|
|
|
34
|
-
|
|
|
35
|
-
|
|
|
36
|
-
| Native
|
|
37
|
-
|
|
|
38
|
-
|
|
|
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 |
|
|
39
43
|
|
|
40
44
|
## Version → feature matrix
|
|
41
45
|
|
|
42
|
-
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`
|
|
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.
|
|
43
47
|
|
|
44
|
-
| Exact DSH version | Listener and bridge differences
|
|
45
|
-
| ----------------- |
|
|
46
|
-
| `0.1.7-rc.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1
|
|
47
|
-
| `0.1.7-rc.2` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1
|
|
48
|
-
| `0.2.0-rc.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1
|
|
49
|
-
| `0.2.0-rc.2` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1
|
|
50
|
-
| `0.2.1-alpha.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1
|
|
51
|
-
| `0.2.1-alpha.2` | Native concrete IPv4/IPv6 and HTTP/HTTPS; Connection uses actual protocol and bind authority | Native `--public-url`; model text and `DSH_WEB_URL` use the plugin's final public root |
|
|
52
|
-
| `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 | Native `--public-url`; model address in `app:web-surface` runtime context; `DSH_WEB_URL` uses final public root |
|
|
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 |
|
|
53
61
|
|
|
54
|
-
`PLUGIN-CONFIG-001` and shared security boundaries apply to every row and cannot be retired by dropping a DSH release. Unlisted future releases
|
|
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.
|
|
55
63
|
|
|
56
64
|
## Capability migration and retirement workflow
|
|
57
65
|
|
|
@@ -68,7 +76,7 @@ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Active.
|
|
|
68
76
|
| Field | Maintenance basis |
|
|
69
77
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
70
78
|
| 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 |
|
|
71
|
-
| Native capability versions | `0.2.1-alpha.2`
|
|
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 |
|
|
72
80
|
| 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 |
|
|
73
81
|
| 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 |
|
|
74
82
|
| 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 |
|
|
@@ -80,7 +88,7 @@ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`.
|
|
|
80
88
|
| Field | Maintenance basis |
|
|
81
89
|
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
82
90
|
| 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 |
|
|
83
|
-
| Native capability versions | `0.2.1-alpha.2`
|
|
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 |
|
|
84
92
|
| 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 |
|
|
85
93
|
| 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 |
|
|
86
94
|
| 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,68 +103,86 @@ Public URL projection and model prompt location differences. Type: `dsh-runtime`
|
|
|
95
103
|
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
96
104
|
| 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 |
|
|
97
105
|
| 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 |
|
|
98
|
-
| Native context projection
|
|
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 |
|
|
99
107
|
| 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 |
|
|
100
108
|
| 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 |
|
|
101
|
-
| 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`. A new projection location does not change how another supported release must be observed
|
|
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 |
|
|
102
110
|
|
|
103
111
|
## DSH-THEME-001
|
|
104
112
|
|
|
105
113
|
CSS fallback for missing theme tokens. Type: `dsh-runtime`. Active.
|
|
106
114
|
|
|
107
|
-
| Field | Maintenance basis
|
|
108
|
-
| --------------------------- |
|
|
109
|
-
| Fallback version |
|
|
110
|
-
| 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` and `0.2.1-alpha.3` provide
|
|
111
|
-
| Implementation and upstream | `var()` fallbacks in `src/client/settings/style.css`; CSS token definitions in exact `@deepseek-ai/dsh-client-ui-theme/lib` packages. The
|
|
112
|
-
| Tests and evidence | `tests/browser/dsh-bootstrap.spec.ts` and manual screenshots under `.cache/ui-review/<version>`. 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
|
|
113
|
-
| Migration and retirement |
|
|
115
|
+
| Field | Maintenance basis |
|
|
116
|
+
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
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 |
|
|
120
|
+
| 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 |
|
|
114
122
|
|
|
115
123
|
## DSH-TEST-001
|
|
116
124
|
|
|
117
125
|
Settings navigation and first-run test adaptations. Type: `dsh-runtime`. Active; exact notice/reload trigger applicability remains incomplete.
|
|
118
126
|
|
|
119
|
-
| Field | Maintenance basis
|
|
120
|
-
| ------------------------ |
|
|
121
|
-
| 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
|
|
122
|
-
| Account-menu version | `0.2.1-alpha.3`
|
|
123
|
-
| 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`
|
|
124
|
-
| 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`
|
|
125
|
-
| 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
|
|
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 |
|
|
126
134
|
|
|
127
135
|
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.
|
|
128
136
|
|
|
129
137
|
On `0.2.1-alpha.3`, the 2026-10-15 CI run and a local reproduction with `DEEPSEEK_API_KEY` unset confirmed that explicit page reload reopens account onboarding when no model credential was configured. Native `SettingsRoot` keeps completed onboarding steps in component state. `tests/browser/login.spec.ts` clears the inherited key in the DSH runtime environment and rechecks prompts when opening plugin settings after reload, while retaining the settings-persistence assertions. `completeApiKeyPrompt` selects the native API-key alternative on `0.2.1-alpha.3` before entering the shared credential editor, so fixture setup actually configures a provider. This exact case does not establish every delayed-notice or automatic-reload trigger listed above.
|
|
130
138
|
|
|
139
|
+
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
|
+
|
|
131
141
|
## DSH-ACCOUNT-001
|
|
132
142
|
|
|
133
143
|
Manual official-account callback handoff. Type: `dsh-runtime`. Active; an independently removable temporary adaptation.
|
|
134
144
|
|
|
135
|
-
| Field | Maintenance basis
|
|
136
|
-
| ------------------------------------- |
|
|
137
|
-
| 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`
|
|
138
|
-
|
|
|
139
|
-
| 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
|
|
140
|
-
| 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
|
|
141
|
-
| 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 |
|
|
142
|
-
| Tests | `tests/integration/account-login.test.ts` uses the real `0.2.1-
|
|
143
|
-
| 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.
|
|
144
|
-
| Retirement and preservation | Retain the
|
|
145
|
-
| 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
|
|
145
|
+
| Field | Maintenance basis |
|
|
146
|
+
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
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 |
|
|
148
|
+
| 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. |
|
|
150
|
+
| 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
|
+
| 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. |
|
|
153
|
+
| 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 |
|
|
155
|
+
| 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
|
+
|
|
157
|
+
## DSH-HMR-001
|
|
158
|
+
|
|
159
|
+
Long-lived listener transaction-context isolation after native hot reload. Type: `dsh-runtime`. Active.
|
|
160
|
+
|
|
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. |
|
|
146
168
|
|
|
147
169
|
## PLUGIN-CONFIG-001
|
|
148
170
|
|
|
149
|
-
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.
|
|
171
|
+
Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.2.0`, independent of the DSH version set.
|
|
150
172
|
|
|
151
173
|
| Field | Maintenance basis |
|
|
152
174
|
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
153
|
-
| 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.
|
|
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 |
|
|
154
176
|
| 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 |
|
|
155
177
|
| 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 |
|
|
156
178
|
| 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 |
|
|
157
179
|
|
|
158
180
|
## Shared security boundaries
|
|
159
181
|
|
|
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.
|
|
183
|
+
|
|
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.
|
|
185
|
+
|
|
160
186
|
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.
|
|
161
187
|
|
|
162
188
|
The production entry validates the bound port after official listener initialization; failure must release the listener, admin socket and storage lock. Connection loss or uncertain storage withdraws readiness and closes business carriers. Never satisfy compatibility checks by fabricating services, disabling Loader startup audits or bypassing the native listener.
|
|
@@ -168,3 +194,9 @@ Resolve evidence through the installed DSH → WebApp → actual dependency chai
|
|
|
168
194
|
Records from 2026-10-09 through 2026-10-10 establish schema, public URL and protocol boundaries and plugin configuration migration 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` and `0.2.1-alpha.2`. The 2026-10-15 review adds `0.2.1-alpha.3` runtime-context, account-menu, port-type and account-callback evidence. The DSH `0.2.1-alpha.3` development composition uses Cordis `4.0.5-alpha.2` and Schemastery `3.18.5-alpha.2`; these are dependency package versions, not shorthand DSH versions. The same review traced each declared release through its base provider, WebApp account-controller and ui-settings-account to establish existing native providers, the plain-Web UI activation boundary and the `startSignIn` argument difference.
|
|
169
195
|
|
|
170
196
|
Open items: exact notice/reload trigger mapping per release, real non-loopback IPv6 interface verification, full real official-account authorization, official public `redirect_uri` acceptance and native DSH adaptation. Gaps limit the relevant claims; they do not justify guessing capabilities or removing implementation early.
|
|
197
|
+
|
|
198
|
+
Historical 2026-10-16 admission evidence: exact tag `dsh-v0.2.1-alpha.4` (`86a402200d95fecef4529d969836f1fe13c6cb0d`) and installed packages establish the listed `0.2.1-alpha.4` capabilities. Its development composition still uses Cordis `4.0.5-alpha.2` and Schemastery `3.18.5-alpha.2`. Each of the six dsh-runtime entries still intersects the new eight-release support set and is retained; PLUGIN-CONFIG-001 remains independent. These are admission facts; same-final-artifact eight-release results belong to the execution record and are not presumed before running.
|
|
199
|
+
|
|
200
|
+
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
|
+
|
|
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.
|