dsh-auth-remote 0.1.8 → 0.1.9

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 (44) hide show
  1. package/CHANGELOG.md +8 -1
  2. package/CHANGELOG.zh-CN.md +8 -1
  3. package/CONTRIBUTING.md +1 -1
  4. package/CONTRIBUTING.zh-CN.md +1 -1
  5. package/README.md +28 -12
  6. package/README.zh-CN.md +28 -12
  7. package/dist/cli.js +50 -0
  8. package/dist/cli.js.map +2 -2
  9. package/dist/client.js +457 -1
  10. package/dist/client.js.map +4 -4
  11. package/dist/index.js +356 -23
  12. package/dist/index.js.map +3 -3
  13. package/dist/login.js +50 -0
  14. package/dist/login.js.map +2 -2
  15. package/dist/types/adapters/dsh/account-callback.d.ts +12 -0
  16. package/dist/types/adapters/dsh/account-callback.d.ts.map +1 -0
  17. package/dist/types/adapters/dsh/browser-capability.d.ts +1 -1
  18. package/dist/types/adapters/dsh/browser-capability.d.ts.map +1 -1
  19. package/dist/types/adapters/dsh/webserver.d.ts +3 -0
  20. package/dist/types/adapters/dsh/webserver.d.ts.map +1 -1
  21. package/dist/types/http/account-login.d.ts +43 -0
  22. package/dist/types/http/account-login.d.ts.map +1 -0
  23. package/dist/types/http/routes.d.ts +16 -1
  24. package/dist/types/http/routes.d.ts.map +1 -1
  25. package/dist/types/index.d.ts.map +1 -1
  26. package/dist/types/shared/account-login.d.ts +21 -0
  27. package/dist/types/shared/account-login.d.ts.map +1 -0
  28. package/dist/types/shared/i18n.d.ts +50 -0
  29. package/dist/types/shared/i18n.d.ts.map +1 -1
  30. package/dist/types/shared/locales/en.d.ts +25 -0
  31. package/dist/types/shared/locales/en.d.ts.map +1 -1
  32. package/dist/types/shared/locales/zh.d.ts +25 -0
  33. package/dist/types/shared/locales/zh.d.ts.map +1 -1
  34. package/docs/deployment.md +19 -15
  35. package/docs/deployment.zh-CN.md +19 -15
  36. package/docs/development.md +16 -6
  37. package/docs/development.zh-CN.md +16 -6
  38. package/docs/legacy-compatibility.md +170 -117
  39. package/docs/legacy-compatibility.zh-CN.md +170 -0
  40. package/docs/releasing.md +6 -6
  41. package/docs/releasing.zh-CN.md +6 -6
  42. package/docs/reverse-proxy.md +2 -2
  43. package/docs/reverse-proxy.zh-CN.md +2 -2
  44. package/package.json +25 -11
@@ -2,9 +2,9 @@
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.2`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
5
+ 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.1-alpha.3`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
6
6
 
7
- 兼容声明或适配变更前,先阅读 [Legacy 兼容维护清单](legacy-compatibility.md)。共同复核运行时准入、测试目标、CI 和用户声明;适用版本退出支持集合时同次清理专属运行时代码及测试。旧插件配置按自身迁移策略退役,保留共享安全逻辑并用精确版本证据更新清单。
7
+ 兼容声明或适配变更前,先阅读 [Legacy 兼容维护清单](legacy-compatibility.zh-CN.md)。共同复核运行时准入、测试目标、CI 和用户声明;适用版本退出支持集合时同次清理专属运行时代码及测试。旧插件配置按自身迁移策略退役,保留共享安全逻辑,并用完整版本号与精确版本证据同步更新中英文清单及两个维度的矩阵。
8
8
 
9
9
  ## 准备和检查源码检出
10
10
 
@@ -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.8.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
19
+ `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.1.9.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
20
20
 
21
21
  ## 使用隔离开发 profile
22
22
 
@@ -31,7 +31,7 @@ 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.2/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.3/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
35
35
  ```
36
36
 
37
37
  开发 home 可能含测试账号数据,须保持私有,不要提交或复制到部署 profile。
@@ -40,13 +40,15 @@ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.1-alpha.2/node_modules/.bin
40
40
 
41
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.2`)时可替换 DSH 二进制。
43
+ 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.1-alpha.3`)时可替换 DSH 二进制。
44
44
 
45
45
  DSH 测试运行时位于 `.cache/test-runtime/<version>`,与源码依赖分别固定。宿主服务和 React 不打入客户端 bundle。[部署指南](deployment.zh-CN.md)说明 profile 与备份规则。
46
46
 
47
+ 隔离验证安装使用 pnpm 的文件复制模式,避免不同 profile 共享包文件的硬链接元数据变化触发 DSH 客户端热重载。
48
+
47
49
  ## 跨版本验证
48
50
 
49
- 默认测试 DSH `0.2.1-alpha.2`;`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`,测试运行时分别位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`。`DSH_TEST_BIN` 必须报告所选的精确版本。CI 对六版分别运行 CLI、安装冒烟和浏览器测试。开发类型和集成测试使用锁定的 alpha.2 包。源码检出目录的测试指南(`tests/README.zh-CN.md`)说明真实 Loader/模型地址核对,以及原生 IPv6/TLS 正向或不支持能力的断言;原生测试传输不可用时失败,不跳过。
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 正向或不支持能力的断言;原生测试传输不可用时失败,不跳过。
50
52
 
51
53
  ```sh
52
54
  DSH_TEST_VERSION=0.1.7-rc.1 pnpm test:cli
@@ -59,8 +61,16 @@ DSH_TEST_VERSION=0.2.0-rc.2 pnpm test:cli
59
61
  DSH_TEST_VERSION=0.2.0-rc.2 pnpm test:browser
60
62
  DSH_TEST_VERSION=0.2.1-alpha.1 pnpm test:cli
61
63
  DSH_TEST_VERSION=0.2.1-alpha.1 pnpm test:browser
64
+ DSH_TEST_VERSION=0.2.1-alpha.2 pnpm test:cli
65
+ DSH_TEST_VERSION=0.2.1-alpha.2 pnpm test:browser
62
66
  pnpm test:cli
63
67
  pnpm test:browser
64
68
  ```
65
69
 
66
70
  浏览器测试把浅色/深色、桌面/窄屏截图保存在 `.cache/ui-review/<version>`,供人工检查。安全页的 CSS 在插件生效时注入、销毁时移除,所有选择器只作用于插件页面,并直接引用宿主 `--dsw-*` 主题变量。独立登录页使用 dsh 0.2.0-rc.1 的主题变量子集并跟随系统配色,不读取登录前不可用的宿主设置。
71
+
72
+ 官方账号专项测试使用本地平台替身与真实 DSH `0.2.1-alpha.3` 账号提供者,验证兑换保留原始 redirect URI 和 PKCE verifier,以及错误 state/URL/会话、重复提交、取消、过期和重试。浏览器覆盖账号菜单与引导中的先说明弹窗、回环导航失败后粘贴确认、弹窗拦截、动态语言与浅深色响应式布局。这些测试不会建立真实官方账号授权。
73
+
74
+ 账号核心测试从锁定的开发依赖加载精确版本提供者,无需预先存在 CLI 运行时缓存;浏览器测试仍使用隔离 DSH profile 中实际安装的提供者。
75
+
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`。
@@ -1,117 +1,170 @@
1
- # Legacy 兼容维护清单
2
-
3
- 本清单是人工及本地 AI 修改兼容声明前的唯一维护入口,最后复核日期为 2026-10-10。用户配置指南仍使用中英文版本;不复制英文状态清单,不增加脚本或 CI 门禁。
4
-
5
- ## 复核与退役规则
6
-
7
- 修改 `package.json` 的 peers 或 `dsh.compatibility`、运行时准入范围、测试支持列表、CI 矩阵或用户兼容声明前,逐条读取本清单并检查新支持集合。
8
-
9
- - `dsh-runtime`:适用版本与新支持集合仍有交集则保留;交集为空时,在修改声明的同一次变更删除专属实现、专属测试并更新清单和指南,不延后清理。共同安全校验和共享测试不属于删除范围。
10
- - `plugin-contract`:按插件自身的迁移政策退役;DSH 支持范围收缩不触发退役。旧 `allowedOrigins` 单项和空数组兼容在 0.1.6 保留,只有未来明确结束旧配置支持时才能删除。
11
- - 证据不足时保留实现,登记缺口和待复核版本,不编造退役阈值。未来版本的准入不等于经过兼容验证。
12
-
13
- 当前声明和测试目标为 `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`;默认运行时为 alpha.2。声明和针对性验证不单独证明开发完成,交付须有同一最终产物的六版 CLI/browser/smoke 矩阵与审计确认。本清单维护长期适用范围和退役条件,具体交付证据由执行记录保存。
14
-
15
- 本次证据沿安装目录中的 DSH 包 → WebApp 包 → 实际依赖包解析,核对 manifest 精确版本;从测试目录直接解析子包可能误用仓库或祖先目录的其他版本。下列上游位置均指对应精确版本的安装包,不使用浮动主分支。
16
-
17
- ## DSH-HOST-001:旧监听 host/schema 适配
18
-
19
- | 字段 | 内容 |
20
- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
21
- | 类型 / 生效状态 | `dsh-runtime` / 现存生效 |
22
- | 适用 DSH | 前五版保留具体 IPv4/schema 适配;alpha.2 原生具体 IP 分支已接入 |
23
- | 原因 | 五版 WebServer.Config 仅列 `127.0.0.1` 和 `0.0.0.0`;插件允许具体 IPv4,拒绝通配和非 IPv4,构造函数直接传递监听值 |
24
- | 代码 / 上游证据 | `src/config.ts`、`src/adapters/dsh/webserver.ts`;对应包 `@deepseek-ai/dsh-host-webserver/lib/index.js` 的 Config 和 server.listen |
25
- | 实现位置 | `src/adapters/dsh/runtime-capabilities.ts` 的旧具体 IPv4 分支及现代原生 Config 校验;生产入口在构造时使用统一 `resolveStartupConfig`,已删除过渡 resolver;GuardedWebServer 接收统一 NativeListenerConfig |
26
- | 关联测试 | `tests/integration/dsh-adapter.test.ts`、`tests/integration/http-gate.test.ts`;`tests/unit/config.test.ts` 六版能力输入表;六个精确安装包 schema/能力已分别核对 |
27
- | 客观退役条件 | 所有需要旧 schema 适配的 DSH 均退出支持集合,且精确包证据确认剩余版本具有原生具体 IP 校验 |
28
- | 删除 / 调整范围 | 仅旧 IPv4/schema 分支与专属拒绝测试;保留通配拒绝、端口检查、身份/API 校验及共同门禁测试 |
29
- | 最后复核依据 | 2026-10-10,前五版精确 schema 证据保留;alpha.2 真实 IPv4、IPv6、mapped/scoped loopback 和非回环 IPv4 监听通过;无可绑定的非回环 IPv6 接口,仅核对原生 schema 与策略,不据此扩大实测声明 |
30
-
31
- ## DSH-PROTOCOL-001:旧原生 HTTP 协议假设
32
-
33
- | 字段 | 内容 |
34
- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
35
- | 类型 / 生效状态 | `dsh-runtime` / 旧版 HTTP 和回环 authority 回退保留;现代原生协议/地址桥接已接入 |
36
- | 适用 DSH | 前五版没有 TLS/原生绑定 authority 识别;alpha.2 使用原生 protocol 和地址归一化 |
37
- | 原因 | 前五版 startup 没有 TLS 配置且 Connection 不认识具体非回环 bind,继续使用服务端 HTTP/127.0.0.1 桥接;监听和公开 URL 仍为实际具体 IPv4。现代分支支持 IPv6/HTTPS |
38
- | 代码 / 上游证据 | `src/adapters/dsh/readiness.ts`、`src/adapters/dsh/browser-auth.ts`、`src/adapters/dsh/startup-urls.ts`、`src/http/gate.ts`、`src/index.ts`、[cordis.patch.yml](../cordis.patch.yml);对应 WebApp `lib/startup.js` |
39
- | 实现位置 | `listenerProtocol`、`listenerTransport` 集中旧 HTTP/回环回退;现代回环使用原生 normalizeBindAddress/isLoopbackHost,非回环保留 Connection 绑定 authority 的 WHATWG IPv6 形式并去掉 zone;定稿 nativeAuthority/nativeOrigin 供 readiness 和 gate 共用;0.1.7 将同一 nativeAuthority 自动登记到 Connection.trustedHosts,保留路径所需公开 authority 与显式 CLI 信任合并去重;browser-auth 校验 token URL 协议和 Cookie Secure。外层 Cookie 按公开来源,原生 Cookie 按监听协议 |
40
- | 关联测试 | `tests/integration/native-transport.test.ts`、`tests/browser/native-transport.spec.ts`、`tests/unit/config.test.ts`、既有 dsh-adapter / proxy-chain;包括旧非回环实际包、旧能力拒绝、两种协议方向代理和流撤销 |
41
- | 客观退役条件 | 所有不提供原生监听协议能力的 DSH 均退出支持集合 |
42
- | 删除 / 调整范围 | 仅能力适配器内旧 HTTP/回环回退与专属能力测试;保留 HTTP 正向、双向代理、Cookie 和撤销安全回归 |
43
- | 最后复核依据 | 2026-10-10,rc.1 / alpha.1 真实包非回环绑定曾在统一改写真实 host 后无法激活;恢复旧回环桥接后可认证访问原生设置 API。alpha.2 真实 HTTPS/IPv6 MFA、Host 设置和 CLI 撤销通过;整分支审查发现非回环 mapped IPv6 经 WebServer 归一化后与 Connection 的绑定比较不一致,新增 HTTP/HTTPS、preserveOriginPaths 空数组的实际监听回归。完整六版产物证据由 CLI/browser/smoke 矩阵核对 |
44
-
45
- ## DSH-PUBLIC-001:旧宿主公开地址投影边界
46
-
47
- | 字段 | 内容 |
48
- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
49
- | 类型 / 生效状态 | `dsh-runtime` / 上游能力差异现存;能力解析及插件投影已实现,三个能力组真实包验证通过 |
50
- | 适用 DSH | 前四版无原生 publicUrl;alpha.1 支持,alpha.2 精确包已核实支持 |
51
- | 原因 | 前四版没有 `--public-url`,提示和 `DSH_WEB_URL` 保持原生固定 `127.0.0.1` + 实际端口(无末尾斜杠)的行为;不能为旧宿主补造原生 CLI 参数 |
52
- | 代码 / 上游证据 | [cordis.patch.yml](../cordis.patch.yml)、`src/adapters/dsh/startup-urls.ts`;对应 WebApp `lib/startup.js` 和 `lib/index.js` |
53
- | 实现位置 | bundle 在 webStartup/webServer 可用后读取 `webServer.publicUrl` 只读属性,alpha.1/2 原生消费最终入口,旧版保留原生提示行为 |
54
- | 关联测试 | `tests/browser/deployment-profile.spec.ts` 和 `startup-compatibility.spec.ts`;profile 根目录只读 startup-observer 调用原生 systemPrompt.assemble 和 shellEnv.collect,核对 Web 提示与 DSH_WEB_URL,同一最终地址且无 token;三个能力组真实包验证 |
55
- | 客观退役条件 | 所有缺少原生 publicUrl 的 DSH 均退出支持集合 |
56
- | 删除 / 调整范围 | 仅旧版能力分支、原生提示差异和不支持 CLI 参数的专属测试;保留插件唯一入口、来源准入与启动输出测试 |
57
- | 最后复核依据 | 2026-10-09,四版精确 startup 无 publicUrl,alpha.1 有该字段;不得伪造旧版支持 |
58
-
59
- ## DSH-THEME-001:旧主题 token fallback
60
-
61
- | 字段 | 内容 |
62
- | --------------- | -------------------------------------------------------------------------------------------------------------------------- |
63
- | 类型 / 生效状态 | `dsh-runtime` / 现存生效 |
64
- | 适用 DSH | `0.1.7-rc.1` 缺少 radius-md、radius-lg、focus-ring-color;其他五个已声明版本已提供 |
65
- | 原因 | Security 样式需在最旧支持版本保持圆角和键盘焦点可见性 |
66
- | 代码 / 上游证据 | `src/client/settings/style.css`;精确 `@deepseek-ai/dsh-client-ui-theme/lib` 中 CSS token 定义 |
67
- | 实现位置 | `var(--dsw-radius-md, ...)`、`var(--dsw-radius-lg, 16px)`、focus-ring 的 business-primary fallback |
68
- | 关联测试 | `tests/browser/dsh-bootstrap.spec.ts` 的主题与布局;各版本截图人工复核 |
69
- | 客观退役条件 | `0.1.7-rc.1` 退出支持集合,并确认其余支持版本都有上述 token |
70
- | 删除 / 调整范围 | 仅上述 var 的 fallback 参数和专属旧主题说明;保留宿主动态主题、布局与共享视觉回归 |
71
- | 最后复核依据 | 2026-10-09,五版精确 theme 包 CSS 搜索:rc.1 缺少,rc.2 起均存在;alpha.2 精确 theme 包三个 lib JS 文件的 token 定义均存在 |
72
-
73
- ## DSH-TEST-001:旧宿主 onboarding 交互
74
-
75
- | 字段 | 内容 |
76
- | --------------- | -------------------------------------------------------------------------------------------------------------- |
77
- | 类型 / 生效状态 | `dsh-runtime` / 现存生效,精确适用范围有证据缺口 |
78
- | 适用 DSH | 六版共享测试 helper;具体 notice 名称、首次保存重载与设置页关闭行为的版本范围待真实 UI 复核 |
79
- | 原因 | 宿主启动 notice/API Key 提示可能延迟出现;首次保存可能重载页面并关闭设置 |
80
- | 代码 / 上游证据 | `tests/helpers/runtime.ts` 的注释和实际交互;不能只由源码字符串推定 UI 生命周期 |
81
- | 实现位置 | `completeApiKeyPrompt`、`clickThroughDshPrompts` 中 notice 名称与 reopen 处理 |
82
- | 关联测试 | `tests/browser/dsh-bootstrap.spec.ts`、`tests/browser/dsh-gate.spec.ts` |
83
- | 客观退役条件 | 真实 UI 复核得到精确适用版本后,交集为空才能删除专属交互;证据缺口未补齐时不得退役 |
84
- | 删除 / 调整范围 | 仅经证明确属旧宿主的 notice/reload 分支;通用异步 UI 重试、主题持久化等待和浏览器 fallback 不自动归类为 legacy |
85
- | 最后复核依据 | 2026-10-10,六版完整浏览器矩阵均使用共享 helper 并通过;各项 notice/reload 适配的精确适用范围仍须独立 UI 复核 |
86
-
87
- ## PLUGIN-CONFIG-001:旧 allowedOrigins 配置迁移
88
-
89
- | 字段 | 内容 |
90
- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
91
- | 类型 / 生效状态 | `plugin-contract` / 旧数组配置现存;0.1.6 内存迁移及监听后单入口定稿已生效 |
92
- | 适用契约 | 0.1.5 的顶层 `allowedOrigins`;与 DSH 版本集合无关 |
93
- | 原因 | 0.1.6 迁移到唯一顶层 `publicUrl`,保留旧单项和空数组输入,不改写 profile |
94
- | 代码 / 上游证据 | `src/config.ts`、[cordis.patch.yml](../cordis.patch.yml);插件自身配置契约 |
95
- | 实现位置 | schema 用 undefined union 取消 Schemastery 数组默认值;bundle 无旧数组默认;`resolveStartupConfig` 检查显式互斥并内存转换,`finalizeAuthConfig` 用实际 port 生成唯一策略,旧 resolver 已删除 |
96
- | 关联测试 | `tests/unit/origin-policy.test.ts`、`tests/integration/http-gate.test.ts`;`tests/unit/config.test.ts` 配置解析;startup-compatibility 真实 Loader 验证旧 0/1 项、重复/不同多项、显式 null、新旧 file/CLI 冲突、一次警告和 profile 不改写 |
97
- | 客观退役条件 | 未来产品契约明确结束旧插件配置支持,并提供迁移说明;DSH 版本收缩不触发 |
98
- | 删除 / 调整范围 | 仅旧输入检测、0/1 项转换、弃用提示和专属迁移测试;保留唯一 URL 验证、来源策略和安全回归 |
99
- | 最后复核依据 | 2026-10-09,0.1.5 当前源码;计划保留 0/1 项,多项及任一显式新旧共存报错,每次激活仅一次提示 |
100
-
101
- ## 共享安全边界
102
-
103
- 包身份、未来准入后的 API 检查、具体绑定、原始 Host/Origin/Fetch Metadata、回环准入、密码/TOTP、会话、流撤销、存储故障和 CLI 确认是共享安全逻辑,不随某个 runtime 分支退役。反向代理 HTTPS→HTTP、客户端通用浏览器 fallback 也不是可自动删除的旧 DSH 专属功能。
104
-
105
- 后续实施须将“待实现”更新成实际位置与测试。组合修复已将 Connection 改为依赖 webStartup/webServer,删除 web-runtime 的过时 trustedHosts 转发;`tests/browser/startup-compatibility.spec.ts` 在 alpha.2 原补丁复现 required Connection 等待 webRuntime 的审计失败。不得通过伪造服务、关闭启动审计或放开原生 listener 完成。alpha.1/2 的 startup-compatibility 与 dsh-gate 各 4/4 通过;类型、单元 38/38、集成 29/29 通过。仍不代表新配置、TLS/IPv6 或最终六版矩阵已完成。
106
-
107
- 2026-10-09 任务 3 复核:DSH 开发依赖均升级 alpha.2,Cordis/Schemastery 范围不变。新增 public-url / runtime-capabilities 及配置解析测试,六版真实安装锚点的 WebServer 版本和能力校验均通过。任务 3 曾保留 resolver 过渡路径,任务 4 已删除;当前生产入口仅使用统一启动前解析与监听后定稿,不并行维护两套来源规则。
108
-
109
- 2026-10-10 任务 4 复核:DenyGate 下原生监听后定稿,ready 与 AuthGate 共用唯一来源策略;启动输出使用实际端口并去重。Connection 正常丢失时撤回 ready,桥接预检失败由官方 fiber 释放 listener/admin/存储锁。多来源传输回归拆成独立单入口,保留 HTTP/HTTPS、默认端口、IP、回环、Cookie、头和升级拒绝断言。真实 Loader 旧字段每次激活一次弃用提示且不改写文件;安装包仅在隔离目录测试。
110
-
111
- 任务 4 补证:三个能力组 startup/deployment 各 9/9 通过,alpha.2 dsh-gate 3/3;类型、52 项单元、34 项集成与包验证通过。四个旧 WebApp 的 `localWebUrl` 都使用固定 LOOPBACK_HOST,不能把其模型侧地址误写成插件真实 bind IP。文件、CLI 及旧迁移的插件入口仍按实际生效值;未改写旧版原生注册。显式 null 的 host/port/TLS 不再被当作缺省,证书整组 CLI 覆盖仍优先。
112
-
113
- 2026-10-10 任务 5 复核:旧 HTTP/回环桥接集中在 runtime-capabilities;现代桥接使用原生协议和归一化 authority,zone 不进入便携公开 URL。静态检查、55 项单元、45 项集成通过;alpha.2 原生传输和既有代理浏览器 9/9,rc.1/alpha.1 旧能力拒绝与具体非回环 IPv4 真实包各 4/4,无跳过。TLS 材料错误、Connection 丢失和存储通知故障关闭入口;外层和原生 Cookie 协议独立验证。上述证据来自 0.1.5 开发包;开发包证据不能替代最终 0.1.6 全六版验证。
114
-
115
- 2026-10-10 任务 6 复核:默认测试/开发运行时为 alpha.2,两个既有 CI 矩阵覆盖六版;release 沿用共同默认。原生 systemPrompt Web section 与 DSH_WEB_URL 的最终地址相同且无 token。rc.1/alpha.1/alpha.2 的真实 startup/deployment/native-transport/admin CLI 分别 29/29、29/29、33/33,无跳过;旧多项、重复项、null 及新旧冲突均经过 Loader。静态、55 项单元、45 项集成通过。alpha.2 的最终 0.1.6 六版全量交付另需最终产物证据;onboarding 精确适用范围缺口继续保留。
116
-
117
- 2026-10-10,0.1.7 桥接信任修复复核:`connectionTrustedHosts` 始终返回监听后定稿的 nativeAuthority,保留路径所需公开 authority 与显式 CLI trusted hosts 合并去重。前五版继续登记 HTTP/127.0.0.1 桥接,alpha.2 登记归一化实际监听 authority,不由原始 CLI 参数拼接,亦不扩大外层公开来源。新增实际安装包回环/非回环 CLI host 覆盖与 port 0 回归,六个精确版本各 2/2 通过;验证下游声明列表、CLI 信任保留与去重、匿名拒绝,以及额外可信主机和错误 Origin 仍被外层拒绝。alpha.2 的 0.1.6 安装包已先复现下游 403;完整发布验证另由 CI 执行。支持集合未改变,旧适配继续保留。
1
+ # Legacy compatibility inventory
2
+
3
+ [简体中文](legacy-compatibility.zh-CN.md)
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.
6
+
7
+ ## Scope and review rules
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.
10
+
11
+ - Review both matrices and every affected entry before changing peers, `dsh.compatibility`, runtime admission, test targets, CI or user compatibility claims.
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`.
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.
16
+
17
+ ## Feature → version matrix
18
+
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
+
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 |
39
+
40
+ ## Version → feature matrix
41
+
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.
43
+
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 |
53
+
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.
55
+
56
+ ## Capability migration and retirement workflow
57
+
58
+ 1. When adding or removing DSH support, update both matrices in both languages with complete version numbers, entry IDs and evidence status.
59
+ 2. When a capability changes, use the feature matrix to identify every affected release, then inspect its entries, installed package APIs, implementation and tests. Releases with the same usable API and exact-version verification may move to a shared implementation. Preserve a branch wherever capability or evidence is missing; release order is not migration evidence.
60
+ 3. Record the decision per entry: exact versions retained, exact versions migrated, exclusive code/tests removed and remaining evidence gaps. Do not remove the whole entry while its applicable and supported sets intersect.
61
+ 4. Public OAuth callbacks depend on both DeepSeek Platform and DSH. Platform acceptance of a public `redirect_uri` still requires verification of DSH origin policy, callback handling and UI. Retire the adaptation only under `DSH-ACCOUNT-001` conditions.
62
+ 5. Review both tables and their entries manually. Do not introduce an inventory-specific generator or CI gate; continue using the existing bilingual-link and packaging checks.
63
+
64
+ ## DSH-HOST-001
65
+
66
+ Concrete IP listener and schema adaptation. Type: `dsh-runtime`. Active.
67
+
68
+ | Field | Maintenance basis |
69
+ | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
70
+ | 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 |
72
+ | 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
+ | 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
+ | 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 |
75
+
76
+ ## DSH-PROTOCOL-001
77
+
78
+ Native protocol and Connection bind-authority differences. Type: `dsh-runtime`. Active.
79
+
80
+ | Field | Maintenance basis |
81
+ | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
82
+ | 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 |
84
+ | 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
+ | 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
+ | 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 |
87
+
88
+ Outer Cookie Secure follows the public origin; native Cookie Secure follows the listener protocol. This is shared security behavior, independent of a version fallback's retirement.
89
+
90
+ ## DSH-PUBLIC-001
91
+
92
+ Public URL projection and model prompt location differences. Type: `dsh-runtime`. Active.
93
+
94
+ | Field | Maintenance basis |
95
+ | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
96
+ | 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
+ | 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 |
99
+ | 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
+ | 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 |
102
+
103
+ ## DSH-THEME-001
104
+
105
+ CSS fallback for missing theme tokens. Type: `dsh-runtime`. Active.
106
+
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 |
114
+
115
+ ## DSH-TEST-001
116
+
117
+ Settings navigation and first-run test adaptations. Type: `dsh-runtime`. Active; exact notice/reload trigger applicability remains incomplete.
118
+
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 |
126
+
127
+ 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
+
129
+ 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
+
131
+ ## DSH-ACCOUNT-001
132
+
133
+ Manual official-account callback handoff. Type: `dsh-runtime`. Active; an independently removable temporary adaptation.
134
+
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 |
146
+
147
+ ## PLUGIN-CONFIG-001
148
+
149
+ Migration of plugin `0.1.5` configuration input. Type: `plugin-contract`. Retained in plugin `0.1.9`, independent of the DSH version set.
150
+
151
+ | Field | Maintenance basis |
152
+ | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
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 |
154
+ | 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
+ | 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
+ | 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
+
158
+ ## Shared security boundaries
159
+
160
+ 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
+
162
+ 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.
163
+
164
+ ## Evidence locations and open items
165
+
166
+ Resolve evidence through the installed DSH → WebApp → actual dependency chain and verify every manifest's complete version. Resolving a child package directly from the test directory can accidentally use source dependencies. Use exact installed packages or matching tags rather than a floating branch. Keep artifact hashes, commands, counts and run results in separate execution records; historical development-package success is not final-artifact verification.
167
+
168
+ 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
+
170
+ 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.