dsh-auth-remote 0.1.9 → 0.1.10

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 (49) hide show
  1. package/CHANGELOG.md +11 -0
  2. package/CHANGELOG.zh-CN.md +11 -0
  3. package/README.md +17 -11
  4. package/README.zh-CN.md +17 -11
  5. package/cordis.patch.yml +2 -1
  6. package/dist/cli.js +91 -46
  7. package/dist/cli.js.map +2 -2
  8. package/dist/client.js +2880 -581
  9. package/dist/client.js.map +4 -4
  10. package/dist/index.js +133 -36
  11. package/dist/index.js.map +3 -3
  12. package/dist/login.css +2 -8
  13. package/dist/login.css.map +2 -2
  14. package/dist/login.js +80 -42
  15. package/dist/login.js.map +2 -2
  16. package/dist/types/adapters/dsh/account-callback.d.ts +3 -0
  17. package/dist/types/adapters/dsh/account-callback.d.ts.map +1 -1
  18. package/dist/types/adapters/dsh/hmr-context.d.ts +10 -0
  19. package/dist/types/adapters/dsh/hmr-context.d.ts.map +1 -0
  20. package/dist/types/auth/service.d.ts +2 -0
  21. package/dist/types/auth/service.d.ts.map +1 -1
  22. package/dist/types/auth/sessions.d.ts +2 -0
  23. package/dist/types/auth/sessions.d.ts.map +1 -1
  24. package/dist/types/config.d.ts +9 -3
  25. package/dist/types/config.d.ts.map +1 -1
  26. package/dist/types/http/account-login.d.ts +5 -3
  27. package/dist/types/http/account-login.d.ts.map +1 -1
  28. package/dist/types/index.d.ts +2 -2
  29. package/dist/types/index.d.ts.map +1 -1
  30. package/dist/types/shared/account-login.d.ts +2 -1
  31. package/dist/types/shared/account-login.d.ts.map +1 -1
  32. package/dist/types/shared/auth-contract.d.ts +2 -0
  33. package/dist/types/shared/auth-contract.d.ts.map +1 -1
  34. package/dist/types/shared/i18n.d.ts +78 -40
  35. package/dist/types/shared/i18n.d.ts.map +1 -1
  36. package/dist/types/shared/locales/en.d.ts +39 -20
  37. package/dist/types/shared/locales/en.d.ts.map +1 -1
  38. package/dist/types/shared/locales/zh.d.ts +39 -20
  39. package/dist/types/shared/locales/zh.d.ts.map +1 -1
  40. package/docs/deployment.md +22 -19
  41. package/docs/deployment.zh-CN.md +22 -19
  42. package/docs/development.md +20 -8
  43. package/docs/development.zh-CN.md +20 -8
  44. package/docs/legacy-compatibility.md +86 -64
  45. package/docs/legacy-compatibility.zh-CN.md +86 -64
  46. package/docs/releasing.md +5 -5
  47. package/docs/releasing.zh-CN.md +5 -5
  48. package/examples/web-profile-auth-remote.patch.yml +4 -2
  49. package/package.json +18 -14
@@ -2,7 +2,7 @@
2
2
 
3
3
  [English](development.md)
4
4
 
5
- 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.1-alpha.3`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
5
+ 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.1-alpha.5`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
6
6
 
7
7
  兼容声明或适配变更前,先阅读 [Legacy 兼容维护清单](legacy-compatibility.zh-CN.md)。共同复核运行时准入、测试目标、CI 和用户声明;适用版本退出支持集合时同次清理专属运行时代码及测试。旧插件配置按自身迁移策略退役,保留共享安全逻辑,并用完整版本号与精确版本证据同步更新中英文清单及两个维度的矩阵。
8
8
 
@@ -16,7 +16,7 @@ pnpm pack:local
16
16
  pnpm smoke
17
17
  ```
18
18
 
19
- `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.1.9.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
19
+ `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.1.10.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
20
20
 
21
21
  ## 使用隔离开发 profile
22
22
 
@@ -31,16 +31,16 @@ pnpm dev:start
31
31
  直接查看状态时显式使用同一隔离 home:
32
32
 
33
33
  ```sh
34
- DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.1-alpha.3/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
34
+ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.1-alpha.5/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
35
35
  ```
36
36
 
37
37
  开发 home 可能含测试账号数据,须保持私有,不要提交或复制到部署 profile。
38
38
 
39
39
  ## 测试边界
40
40
 
41
- `pnpm test:unit` 覆盖认证状态机、TOTP、备用码、来源策略、翻译、存储持久性和锁恢复。`pnpm test:integration` 使用真实 HTTP/WebSocket socket 验证原生就绪、Cookie、来源判定与撤销。`pnpm test:cli` 构建真实压缩包,并用隔离 profile/Unix socket 验证交互与非交互命令。`pnpm test:browser` 用临时 profile 启动所选的 DSH 版本,验证登录、安全页、原生设置、工作区、上传/预览、SSE、WebSocket 和 HTTPS 转发链。
41
+ `pnpm test:unit` 覆盖认证状态机、TOTP、备用码、来源策略、翻译、存储持久性和锁恢复。`pnpm test:integration` 使用真实 HTTP/WebSocket socket 验证原生就绪、Cookie、来源判定与撤销。`pnpm test:cli` 构建真实压缩包,并用隔离 profile/Unix socket 验证交互与非交互命令。`pnpm test:browser` 用临时 profile 启动所选的 DSH 版本,验证登录、安全与登录页、原生设置、工作区、上传/预览、SSE、WebSocket 和 HTTPS 转发链。
42
42
 
43
- 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.1-alpha.3`)时可替换 DSH 二进制。
43
+ 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.1-alpha.5`)时可替换 DSH 二进制。
44
44
 
45
45
  DSH 测试运行时位于 `.cache/test-runtime/<version>`,与源码依赖分别固定。宿主服务和 React 不打入客户端 bundle。[部署指南](deployment.zh-CN.md)说明 profile 与备份规则。
46
46
 
@@ -48,7 +48,7 @@ DSH 测试运行时位于 `.cache/test-runtime/<version>`,与源码依赖分
48
48
 
49
49
  ## 跨版本验证
50
50
 
51
- 默认测试 DSH `0.2.1-alpha.3`;`DSH_TEST_VERSION` 可选择 `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`,测试运行时分别位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`。`DSH_TEST_BIN` 必须报告所选的精确版本。CI 对七版分别运行 CLI、安装冒烟和浏览器测试。开发类型和集成测试使用锁定的 DSH `0.2.1-alpha.3` 包。源码检出目录的测试指南(`tests/README.zh-CN.md`)说明真实 Loader/模型地址核对,以及原生 IPv6/TLS 正向或不支持能力的断言;原生测试传输不可用时失败,不跳过。
51
+ 默认测试 DSH `0.2.1-alpha.5`;`DSH_TEST_VERSION` 可选择 `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`,测试运行时分别位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`。`DSH_TEST_BIN` 必须报告所选的精确版本。CI 对九版分别运行 CLI、安装冒烟和浏览器测试。开发类型和集成测试使用锁定的 DSH `0.2.1-alpha.5` 包。源码检出目录的测试指南(`tests/README.zh-CN.md`)说明真实 Loader/模型地址核对,以及原生 IPv6/TLS 正向或不支持能力的断言;原生测试传输不可用时失败,不跳过。
52
52
 
53
53
  ```sh
54
54
  DSH_TEST_VERSION=0.1.7-rc.1 pnpm test:cli
@@ -63,14 +63,26 @@ DSH_TEST_VERSION=0.2.1-alpha.1 pnpm test:cli
63
63
  DSH_TEST_VERSION=0.2.1-alpha.1 pnpm test:browser
64
64
  DSH_TEST_VERSION=0.2.1-alpha.2 pnpm test:cli
65
65
  DSH_TEST_VERSION=0.2.1-alpha.2 pnpm test:browser
66
+ DSH_TEST_VERSION=0.2.1-alpha.3 pnpm test:cli
67
+ DSH_TEST_VERSION=0.2.1-alpha.3 pnpm test:browser
68
+ DSH_TEST_VERSION=0.2.1-alpha.4 pnpm test:cli
69
+ DSH_TEST_VERSION=0.2.1-alpha.4 pnpm test:browser
66
70
  pnpm test:cli
67
71
  pnpm test:browser
68
72
  ```
69
73
 
70
74
  浏览器测试把浅色/深色、桌面/窄屏截图保存在 `.cache/ui-review/<version>`,供人工检查。安全页的 CSS 在插件生效时注入、销毁时移除,所有选择器只作用于插件页面,并直接引用宿主 `--dsw-*` 主题变量。独立登录页使用 dsh 0.2.0-rc.1 的主题变量子集并跟随系统配色,不读取登录前不可用的宿主设置。
71
75
 
72
- 官方账号专项测试使用本地平台替身与真实 DSH `0.2.1-alpha.3` 账号提供者,验证兑换保留原始 redirect URI 和 PKCE verifier,以及错误 state/URL/会话、重复提交、取消、过期和重试。浏览器覆盖账号菜单与引导中的先说明弹窗、回环导航失败后粘贴确认、弹窗拦截、动态语言与浅深色响应式布局。这些测试不会建立真实官方账号授权。
76
+ 官方账号专项测试使用本地平台替身与真实 DSH `0.2.1-alpha.5` 账号提供者,验证兑换保留原始 redirect URI 和 PKCE verifier,以及错误 state/URL/会话、重复提交、取消、过期和重试。浏览器覆盖账号菜单与引导中的先说明弹窗、回环导航失败后粘贴确认、弹窗拦截、动态语言与浅深色响应式布局。这些测试不会建立真实官方账号授权。
73
77
 
74
78
  账号核心测试从锁定的开发依赖加载精确版本提供者,无需预先存在 CLI 运行时缓存;浏览器测试仍使用隔离 DSH profile 中实际安装的提供者。
75
79
 
76
- 此临时适配仅在精确 `0.2.1-alpha.3` 启用,完整功能回归只针对该版本;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` 只需验证启动、设置入口与功能未启用,无需因该专项重跑七版完整矩阵。支持范围或共享宿主适配变更仍须完整矩阵,CI 目标不变。后续版本默认使用原生流程;公网回调证据、迁移及退役条件见兼容维护清单的 `DSH-ACCOUNT-001`。
80
+ 此临时适配按 `>=0.2.1-alpha.3`(包含预发布)加必要能力与动态配置准入;完整手动功能回归覆盖 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`。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` 验证基础认证、完整安全与登录交互、动态配置持久化及手动能力不可用反馈。未来准入不构成已验证声明。支持范围或共享宿主适配变更须以同一最终 tgz 完整运行九版 CLI、浏览器及 smoke;循环内直接运行测试文件和 smoke:packed,不能调用会重新打包的 test:cli/test:browser/smoke,并在每版后校验 SHA-256。公网回调证据、迁移及退役条件见兼容维护清单的 `DSH-ACCOUNT-001`。
81
+
82
+ `live-config.spec.ts` 仅观察真实 Loader 的配置引用/fiber、认证/存储实例、锁、监听器及 SSE/WebSocket 连续性,核对实际依赖链并重启验证 profile override;不伪造服务。安全弹窗回归覆盖取消/错误、焦点/键盘、默认及强制 TOTP、一次性备用码复制与会话撤销后跳转保持。任务文档、测试凭证、profile、截图及生成目录不得进入 npm 包。
83
+
84
+ `account-login.spec.ts` 还在每个声明版本验证真实原生配置 HMR:修改普通字段 `sessionHours` 重建监听器,之后独立 Settings 写入必须等待已有原生事务,而真正嵌套仍被拒绝。在 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5` 额外修改隔离安装的插件代码,验证原生模块替换后可以重新开启手动登录。测试专用事务探针调用真实 HMR,不替代服务且不进入 npm 包。监听器上下文的最小适配见 `DSH-HMR-001`。
85
+
86
+ 账号配置绑定通过原生 describe 镜像的 `ensure()` API 恢复首次读取失败;已有镜像中的命名空间恢复使用明确注入的 `remote.settings` 传输,并将已接纳值回填到同一镜像。偏好加载期间点击登录会等待共享读取,再按最新接纳的 true/false 值选择入口;加载中不等同于关闭。浏览器回归覆盖首次读取失败、命名空间暂缺,以及两种路由选择的延迟读取。
87
+
88
+ `browser/host-release.spec.ts` 在 `0.2.1-alpha.4`、`0.2.1-alpha.5` 运行:前者准备真实 `0.2.1-alpha.3`,后者准备真实 `0.2.1-alpha.4`。每项均在同一临时 profile/端口切换宿主,保留页面并检查原生版本刷新提示;刷新后核对认证、原会话与已保存配置,再恢复起始版本。`0.2.1-alpha.3` 目的宿主没有 release 元数据,显示未解析;`0.2.1-alpha.4` 目的宿主须显示真实版本。不伪造上游源码、版本或依赖图元数据。
@@ -2,56 +2,60 @@
2
2
 
3
3
  [简体中文](legacy-compatibility.zh-CN.md)
4
4
 
5
- Last reviewed: 2026-10-15. 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-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
6
 
7
7
  ## Scope and review rules
8
8
 
9
- Plugin `0.1.9` declares 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` and `0.2.1-alpha.3`. Development and tests default to `0.2.1-alpha.3`. 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 or automatic manual-account activation.
9
+ Plugin `0.1.10` declares 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` and `0.2.1-alpha.5`. Development and tests default to `0.2.1-alpha.5`. 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
10
 
11
11
  - Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
12
12
  - `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.1.9` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
13
+ - `plugin-contract`: retire under the plugin's configuration migration policy, independently of DSH support. Plugin `0.1.10` still accepts the `allowedOrigins` input introduced by plugin `0.1.5`.
14
14
  - 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 only `0.2.1-alpha.3`; `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. The complete CI version matrix stays unchanged.
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 `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5`; `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. Both CLI/smoke and browser CI matrices include these nine exact releases.
16
16
 
17
17
  ## Feature → version matrix
18
18
 
19
19
  “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
20
 
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
- | Settings entry · [DSH-TEST-001](#dsh-test-001) | Sidebar Settings | Sidebar Settings | Sidebar Settings | Sidebar Settings | Sidebar Settings | Sidebar Settings | Account menu → Settings |
33
- | 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 |
34
- | 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 |
35
- | 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 |
36
- | 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 |
37
- | Plugin manual account callback · [DSH-ACCOUNT-001](#dsh-account-001) | Disabled | Disabled | Disabled | Disabled | Disabled | Disabled | Plugin enabled; native API-key choice retained |
38
- | Plugin `0.1.5` configuration migration · [PLUGIN-CONFIG-001](#plugin-config-001) | Retained | Retained | Retained | Retained | Retained | Retained | Retained |
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` | `0.2.1-alpha.4` | `0.2.1-alpha.5` |
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 | Native validation | Native validation |
24
+ | Native IPv6 listener · [DSH-HOST-001](#dsh-host-001) | Rejected | Rejected | Rejected | Rejected | Rejected | Native | Native | Native | Native |
25
+ | Native HTTPS listener · [DSH-PROTOCOL-001](#dsh-protocol-001) | Rejected | Rejected | Rejected | Rejected | Rejected | Native | Native | 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 | 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 | Supported | Supported |
28
+ | Native `--public-url` option · [DSH-PUBLIC-001](#dsh-public-001) | Absent | Absent | Absent | Absent | Native | Native | 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 | Final public root in runtime context | 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 | 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 | Native | Native |
32
+ | Toggle switch thumb token · [DSH-THEME-001](#dsh-theme-001) | Plugin fallback | Plugin fallback | Native | Native | Native | Native | Native | Native | Native |
33
+ | 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 |
34
+ | 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 |
35
+ | 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 |
36
+ | 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 |
37
+ | 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 |
38
+ | 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 |
39
+ | 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 |
40
+ | Plugin `0.1.5` configuration migration · [PLUGIN-CONFIG-001](#plugin-config-001) | Retained | Retained | Retained | Retained | Retained | Retained | Retained | Retained | Retained |
39
41
 
40
42
  ## Version → feature matrix
41
43
 
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` and `0.2.1-alpha.3`. Before removing support, find its row and inspect each entry's complete applicable set. Removing one row does not necessarily retire an entire entry.
44
+ 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` and `0.2.1-alpha.5`. 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
45
 
44
- | 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 |
45
- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
46
- | `0.1.7-rc.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1` | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Three tokens 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 |
47
- | `0.1.7-rc.2` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1` | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Three native tokens; 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 |
48
- | `0.2.0-rc.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1` | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Three native tokens; 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 |
49
- | `0.2.0-rc.2` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1` | No `--public-url`; plugin public entry works; model text and `DSH_WEB_URL` retain native loopback | Three native tokens; 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 |
50
- | `0.2.1-alpha.1` | Plugin validates concrete IPv4; HTTP only; Connection uses HTTP / `127.0.0.1` | Native `--public-url`; model text and `DSH_WEB_URL` use the plugin's final public root | Three native tokens; 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 |
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 | Three native tokens; 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 |
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 | Three native tokens; 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 | DSH-HOST-001, DSH-PROTOCOL-001, DSH-PUBLIC-001, DSH-TEST-001, DSH-ACCOUNT-001 |
46
+ | 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 |
47
+ | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
48
+ | `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 |
49
+ | `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 |
50
+ | `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 |
51
+ | `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 |
52
+ | `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 |
53
+ | `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 |
54
+ | `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 |
55
+ | `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 |
56
+ | `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 |
53
57
 
54
- `PLUGIN-CONFIG-001` and shared security boundaries apply to every row and cannot be retired by dropping a DSH release. Unlisted future releases require separate review; `DSH-ACCOUNT-001` defaults to disabled for every release not explicitly enabled.
58
+ `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
59
 
56
60
  ## Capability migration and retirement workflow
57
61
 
@@ -68,7 +72,7 @@ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Active.
68
72
  | Field | Maintenance basis |
69
73
  | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
70
74
  | 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` and `0.2.1-alpha.3` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
75
+ | Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5` use native Config/address APIs for concrete IPv4/IPv6; wildcard listeners remain forbidden |
72
76
  | 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
77
  | 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
78
  | 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 +84,7 @@ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`.
80
84
  | Field | Maintenance basis |
81
85
  | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
82
86
  | 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` and `0.2.1-alpha.3` use the actual protocol and normalized bind authority. IPv6 zones must not enter portable public URLs; mapped IPv6 must match Connection's WHATWG comparison |
87
+ | Native capability versions | `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5` 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
88
  | 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
89
  | 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
90
  | 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,62 +99,76 @@ Public URL projection and model prompt location differences. Type: `dsh-runtime`
95
99
  | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
96
100
  | 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
101
  | 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 version | `0.2.1-alpha.3` publishes 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 |
102
+ | Native context projection versions | `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5` 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
103
  | 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
104
  | 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 |
105
+ | 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` and `0.2.1-alpha.5`. A new projection location does not change how another supported release must be observed |
102
106
 
103
107
  ## DSH-THEME-001
104
108
 
105
109
  CSS fallback for missing theme tokens. Type: `dsh-runtime`. Active.
106
110
 
107
- | Field | Maintenance basis |
108
- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
109
- | Fallback version | Only `0.1.7-rc.1` lacks `--dsw-radius-md`, `--dsw-radius-lg` and `--dsw-focus-ring-color` |
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 these tokens |
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 account dialog is enabled only on `0.2.1-alpha.3` and directly consumes its native typography, radius and elevation tokens; its styling changes do not remove Security fallbacks for `0.1.7-rc.1` |
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 | After `0.1.7-rc.1` leaves support and token evidence is complete for the remaining exact versions, remove only fallbacks and documentation retained for that missing-token release. Keep live themes, layout, visible focus and shared visual verification |
111
+ | Field | Maintenance basis |
112
+ | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
113
+ | 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` |
114
+ | 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` and `0.2.1-alpha.5` 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` and `0.2.1-alpha.5` also provide the switch thumb token |
115
+ | 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 |
116
+ | 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 across all eight tabled versions. 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. |
117
+ | 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
118
 
115
119
  ## DSH-TEST-001
116
120
 
117
121
  Settings navigation and first-run test adaptations. Type: `dsh-runtime`. Active; exact notice/reload trigger applicability remains incomplete.
118
122
 
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` uses account menu → Settings and official-account onboarding. The manual dialog lives outside sidebar/onboarding entries so rebuilding an entry does not cancel pending authorization |
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` and `0.2.1-alpha.3`, 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 |
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 |
123
+ | Field | Maintenance basis |
124
+ | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
125
+ | 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 |
126
+ | Account-menu version | `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5` 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 |
127
+ | 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` and `0.2.1-alpha.5`, 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 |
128
+ | 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` |
129
+ | 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
130
 
127
131
  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
132
 
129
133
  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
134
 
135
+ 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.
136
+
131
137
  ## DSH-ACCOUNT-001
132
138
 
133
139
  Manual official-account callback handoff. Type: `dsh-runtime`. Active; an independently removable temporary adaptation.
134
140
 
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` enables that UI for plain Web. This plugin adapts only `0.2.1-alpha.3`; a disabled plugin adapter does not mean native account capability is absent |
138
- | Only enabled version | Exact `0.2.1-alpha.3`, jointly gated by `supportsManualAccountLogin` and the server-injected browser flag. Do not replace this with an unbounded version comparison |
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`, `0.2.1-alpha.2` and all unreviewed future releases. Their native callbacks/account slots stay untouched; manual-authorization endpoints report unavailable |
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-alpha.3` provider and local Platform stand-in for PKCE, redirect URI, state, session, duplicate submission, cancellation, revocation, expiry and retries. `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 exact activation and disabled future versions |
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. A new release defaults to native behavior; any manual adaptation requires evidence and explicit inclusion in the enabled set |
144
- | Retirement and preservation | Retain the branch while supported `0.2.1-alpha.3` still needs loopback. When it leaves support, or its 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 |
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 |
141
+ | Field | Maintenance basis |
142
+ | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
143
+ | 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` 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 |
144
+ | 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. |
145
+ | 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. |
146
+ | 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 |
147
+ | 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. |
148
+ | Tests | `tests/integration/account-login.test.ts` uses the real `0.2.1-alpha.5` 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. |
149
+ | 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. |
150
+ | Retirement and preservation | Retain the adaptation while supported `0.2.1-alpha.3`, `0.2.1-alpha.4` or `0.2.1-alpha.5` 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 |
151
+ | 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 |
152
+
153
+ ## DSH-HMR-001
154
+
155
+ Long-lived listener transaction-context isolation after native hot reload. Type: `dsh-runtime`. Active.
156
+
157
+ | Field | Maintenance basis |
158
+ | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
159
+ | 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` |
160
+ | Native behavior and static evidence | Individually inspected exact `@deepseek-ai/dsh-hmr/lib/index.js` on 2026-10-16: all eight `runExclusive` implementations 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. |
161
+ | 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. |
162
+ | 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”. All eight real configuration-HMR/queue regressions passed: 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`; exact commands, counts and final-artifact results are recorded separately. |
163
+ | 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
164
 
147
165
  ## PLUGIN-CONFIG-001
148
166
 
149
- Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.1.9`, independent of the DSH version set.
167
+ Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.1.10`, independent of the DSH version set.
150
168
 
151
169
  | Field | Maintenance basis |
152
170
  | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
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.1.9` retains it |
171
+ | 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.1.10` retains it |
154
172
  | 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
173
  | 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
174
  | 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 |
@@ -168,3 +186,7 @@ Resolve evidence through the installed DSH → WebApp → actual dependency chai
168
186
  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
187
 
170
188
  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.
189
+
190
+ 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.
191
+
192
+ 2026-10-19 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`. The plugin's development dependencies remain 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.