dsh-auth-remote 0.3.3 → 0.3.4

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.
@@ -1 +1 @@
1
- {"version":3,"file":"dsh-support.d.ts","sourceRoot":"","sources":["../../../src/shared/dsh-support.ts"],"names":[],"mappings":"AAAA,kFAAkF;AAClF,MAAM,WAAW,eAAe;IAC9B,KAAK,EAAE,QAAQ,CAAA;IACf,OAAO,EAAE,MAAM,CAAA;IACf,WAAW,EAAE,MAAM,CAAA;IACnB,UAAU,EAAE,MAAM,CAAA;IAClB,kBAAkB,EAAE,MAAM,CAAA;IAC1B,eAAe,EAAE,MAAM,CAAA;CACxB;AAED,MAAM,WAAW,gBAAgB;IAC/B,KAAK,EAAE,SAAS,CAAA;IAChB,OAAO,EAAE,MAAM,CAAA;IACf,SAAS,EAAE,MAAM,CAAA;IACjB,eAAe,EAAE,MAAM,CAAA;IACvB,mBAAmB,EAAE,MAAM,CAAA;IAC3B,eAAe,EAAE,MAAM,CAAA;CACxB;AAED,MAAM,MAAM,kBAAkB,GAAG,eAAe,GAAG,gBAAgB,CAAA;AACnE,MAAM,MAAM,UAAU,GAClB;IAAE,KAAK,EAAE,WAAW,GAAG,YAAY,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GACtD;IAAE,KAAK,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,eAAe,CAAA;CAAE,GAC7D;IAAE,KAAK,EAAE,SAAS,CAAC;IAAC,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,gBAAgB,CAAA;CAAE,CAAA;AAanE,eAAO,MAAM,mBAAmB,EAAE,SAAS,eAAe,EAIzD,CAAA;AAGD,eAAO,MAAM,oBAAoB,EAAE,SAAS,gBAAgB,EAczD,CAAA;AAGH,sFAAsF;AACtF,wBAAgB,kBAAkB,CAChC,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,WAAW,CAAC,MAAM,CAAC,EAC7B,OAAO,GAAE,SAAS,kBAAkB,EAAc,GACjD,UAAU,CAWZ;AAED,wBAAgB,iBAAiB,CAAC,OAAO,EAAE,UAAU,GAAG,MAAM,GAAG,SAAS,CAYzE;AAID,2FAA2F;AAC3F,wBAAgB,cAAc,CAC5B,OAAO,EAAE,UAAU,EACnB,KAAK,GAAE,CAAC,OAAO,EAAE,MAAM,KAAK,IAAmB,GAC9C,OAAO,CAUT"}
1
+ {"version":3,"file":"dsh-support.d.ts","sourceRoot":"","sources":["../../../src/shared/dsh-support.ts"],"names":[],"mappings":"AAAA,kFAAkF;AAClF,MAAM,WAAW,eAAe;IAC9B,KAAK,EAAE,QAAQ,CAAA;IACf,OAAO,EAAE,MAAM,CAAA;IACf,WAAW,EAAE,MAAM,CAAA;IACnB,UAAU,EAAE,MAAM,CAAA;IAClB,kBAAkB,EAAE,MAAM,CAAA;IAC1B,eAAe,EAAE,MAAM,CAAA;CACxB;AAED,MAAM,WAAW,gBAAgB;IAC/B,KAAK,EAAE,SAAS,CAAA;IAChB,OAAO,EAAE,MAAM,CAAA;IACf,SAAS,EAAE,MAAM,CAAA;IACjB,eAAe,EAAE,MAAM,CAAA;IACvB,mBAAmB,EAAE,MAAM,CAAA;IAC3B,eAAe,EAAE,MAAM,CAAA;CACxB;AAED,MAAM,MAAM,kBAAkB,GAAG,eAAe,GAAG,gBAAgB,CAAA;AACnE,MAAM,MAAM,UAAU,GAClB;IAAE,KAAK,EAAE,WAAW,GAAG,YAAY,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GACtD;IAAE,KAAK,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,eAAe,CAAA;CAAE,GAC7D;IAAE,KAAK,EAAE,SAAS,CAAC;IAAC,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,gBAAgB,CAAA;CAAE,CAAA;AAanE,eAAO,MAAM,mBAAmB,EAAE,SAAS,eAAe,EAIzD,CAAA;AAGD,eAAO,MAAM,oBAAoB,EAAE,SAAS,gBAAgB,EAmB3D,CAAA;AAGD,sFAAsF;AACtF,wBAAgB,kBAAkB,CAChC,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,WAAW,CAAC,MAAM,CAAC,EAC7B,OAAO,GAAE,SAAS,kBAAkB,EAAc,GACjD,UAAU,CAWZ;AAED,wBAAgB,iBAAiB,CAAC,OAAO,EAAE,UAAU,GAAG,MAAM,GAAG,SAAS,CAYzE;AAID,2FAA2F;AAC3F,wBAAgB,cAAc,CAC5B,OAAO,EAAE,UAAU,EACnB,KAAK,GAAE,CAAC,OAAO,EAAE,MAAM,KAAK,IAAmB,GAC9C,OAAO,CAUT"}
@@ -2,17 +2,17 @@
2
2
 
3
3
  [简体中文](deployment.zh-CN.md)
4
4
 
5
- This guide covers plugin `0.3.3` with recommended DSH `0.2.2-alpha.2` and the default `~/.dsh` data directory. See [README](../README.md#dsh-compatibility) for the nine supported DSH releases, the [support policy](support-policy.md) for maintenance details, and [development](development.md) for source builds.
5
+ This guide covers `0.3.4` and its DSH `0.2.2-alpha.3` development default and recommended host. Use the default `~/.dsh` data directory only for your intended account, never for verification. See [README](../README.md#dsh-compatibility) for nine exact declarations, the [support policy](support-policy.md) for maintenance and [development](development.md) for source builds. Published `0.3.3` keeps its nine declarations. Confirm `0.3.4` availability from the completed release workflow and npm registry.
6
6
 
7
- Upstream DSH `0.2.2-alpha.2` itself requires Node `>=24.9.0`; the plugin still declares Node `>=24` and adds no minor-version gate.
7
+ Production acceptance is bounded to Linux with `/proc`, Node.js 24 and Playwright Chromium. DSH `0.2.2-alpha.3` requires Node `>=24.9.0`; the plugin engine stays `>=24`. The Alpha host is not an upstream stable release. Native IPv4/IPv6 HTTP/HTTPS and the existing Node forwarding topologies are covered by the prescribed local tests. A real non-loopback IPv6 interface, other platforms/browsers, real Nginx/Traefik, official-account authorization and production Relay/OAuth are unverified; local protocol stand-ins do not establish real-service behavior.
8
8
 
9
9
  ## Minimal installation
10
10
 
11
- Use the same default `web` profile for installation and the running service:
11
+ After the independent-profile rehearsal and backup below, use the same intended `web` profile for installation and the running service. After successful publication, install the npm version; for an offline installation, substitute the absolute path to your verified release archive:
12
12
 
13
13
  ```sh
14
14
  dsh --version
15
- dsh plugin --profile web add dsh-auth-remote@0.3.3
15
+ dsh plugin --profile web add dsh-auth-remote@0.3.4
16
16
  dsh plugin --profile web list
17
17
  dsh web --no-open --port 13090
18
18
  ```
@@ -126,7 +126,7 @@ Standard `/api` routes work with `preserveOriginPaths: []`; there is no need to
126
126
 
127
127
  ## Start and verify the public entry
128
128
 
129
- 1. Verify Linux, Node.js 24+ (at least `24.9.0` for recommended DSH `0.2.2-alpha.2`), the exact compatible DSH version, and the intended profile/package. Keep test and development data separate.
129
+ 1. Verify Linux, Node.js 24+ (at least `24.9.0` for default DSH `0.2.2-alpha.3`), the exact compatible DSH version, and the intended profile/package. Keep test and development data separate.
130
130
  2. Merge one complete profile configuration and configure a private reachable proxy upstream if needed; see the [proxy guide](reverse-proxy.md).
131
131
  3. Start DSH. For the HTTP upstream example, inspect `curl -fsS -H 'Host: dsh.example.com' http://127.0.0.1:13090/auth-remote/ready` and require the expected plugin/protocol and `ready: true`.
132
132
  4. Confirm anonymous HTML redirect and API denial, then initialize locally, sign in, bind TOTP and save backup codes. Exercise official settings, workspace, preview, uploads, SSE/WebSocket and revocation through the selected entry.
@@ -135,9 +135,13 @@ Startup prints the actual protocol/address/port and one distinct public root, de
135
135
 
136
136
  ## Backup, recovery and changes
137
137
 
138
- Before upgrading to `0.3.3`, stop DSH and back up the authentication directory, profile patch and package/lock files. Keep access private and retain independent `webserver disabled: true`. Confirm that DSH is a listed target (recommended `0.2.2-alpha.2`), install the plugin, and verify readiness, anonymous denial, login and revocation. To roll back, stop the service and restore matching host/plugin package, lock and patch backups. This release does not change the authentication data format; still check schema when restoring and never overwrite live state.
138
+ Before upgrading, record the exact old DSH version, plugin archive and digest, profile configuration and package/lock files. Stop the old process, confirm that it released the profile lock, and back up the complete target profile, authentication state, DSH data and configuration with private permissions. Keep the original backup intact. Copy it into an independent private `DSH_HOME` to rehearse the selected exact host and verified `0.3.4` release archive; do not reuse a production profile for verification.
139
139
 
140
- When upgrading from a plugin earlier than `0.3.2`, account for the behavior changes introduced in `0.3.2` and retained in `0.3.3`: CLI text is fixed English, so remove `--lang` from scripts; JSON fields are unchanged. The standalone login page has no language selector and uses `dsh-auth-remote-lang` memory, then `navigator.language`, then English. Old `dsh-auth-remote.locale` is ignored, retained and not migrated. Entering DSH remembers only native accepted preferences; signing out keeps them. The plugin's eight languages do not expand DSH's native language catalog.
140
+ Only then change the stopped production installation. Keep its public entry private and retain the independent `webserver disabled: true` row until readiness, anonymous rejection, login and session revocation checks pass. Do not overwrite live state. This version changes no plugin storage format.
141
+
142
+ For rollback, stop the new process and restore the matching old exact host, plugin archive, configuration and corresponding complete data backup. Host-switch tests establish only their covered configuration/session contracts; they do not promise that an old host can read arbitrary new production data. Use the matching backup for production data rollback.
143
+
144
+ When upgrading from a plugin earlier than `0.3.2`, account for the behavior changes introduced in `0.3.2` and retained in `0.3.4`: CLI text is fixed English, so remove `--lang` from scripts; JSON fields are unchanged. The standalone login page has no language selector and uses `dsh-auth-remote-lang` memory, then `navigator.language`, then English. Old `dsh-auth-remote.locale` is ignored, retained and not migrated. Entering DSH remembers only native accepted preferences; signing out keeps them. The plugin's eight languages do not expand DSH's native language catalog.
141
145
 
142
146
  Stop DSH and verify it released the profile lock before copying `~/.dsh/profiles/web/auth-remote/auth-state.json`. Keep the copy in a private directory (0700) with file mode 0600. It contains password hashes, the TOTP secret, backup-code hashes and sessions. Do not copy an in-progress temporary file, overwrite live locked state or commit it. Back up the corresponding profile patch and package/lock files.
143
147
 
@@ -2,17 +2,17 @@
2
2
 
3
3
  [English](deployment.md)
4
4
 
5
- 本指南面向插件 `0.3.3` 与推荐 DSH `0.2.2-alpha.2`,使用默认 `~/.dsh` 数据目录。九个支持版本见 [README](../README.zh-CN.md#dsh-兼容性),维护细节见[支持规范](support-policy.zh-CN.md)。源码构建见[开发指南](development.zh-CN.md)。
5
+ 本指南面向 `0.3.4` 及其开发默认和推荐宿主 DSH `0.2.2-alpha.3`。默认 `~/.dsh` 只用于预期账号,不用于验证。九版精确声明见 [README](../README.zh-CN.md#dsh-兼容性),维护见[支持规范](support-policy.zh-CN.md),源码构建见[开发指南](development.zh-CN.md)。已发布 `0.3.3` 保留九版声明;`0.3.4` 的可用性由发布工作流完成状态和 npm registry 确认。
6
6
 
7
- 上游 DSH `0.2.2-alpha.2` 自身要求 Node `>=24.9.0`;插件仍声明 Node `>=24`,不增加小版本拦截。
7
+ 生产验收边界为带 `/proc` 的 Linux、Node.js 24 和 Playwright Chromium。DSH `0.2.2-alpha.3` 要求 Node `>=24.9.0`;插件引擎仍为 `>=24`。Alpha 宿主不是上游稳定版。规定的本地测试覆盖原生 IPv4/IPv6 HTTP/HTTPS 与既有 Node 转发拓扑;真实非回环 IPv6 网卡、其他平台/浏览器、真实 Nginx/Traefik、官方账号授权及生产 Relay/OAuth 未验证,本地协议替身不证明真实服务行为。
8
8
 
9
9
  ## 最小化安装
10
10
 
11
- 安装和运行服务使用同一默认 `web` profile:
11
+ 完成下方独立 profile 演练和备份后,安装与运行使用同一预期 `web` profile;发布工作流成功后安装 npm 版本;离线安装时改用已验证发布归档的绝对路径:
12
12
 
13
13
  ```sh
14
14
  dsh --version
15
- dsh plugin --profile web add dsh-auth-remote@0.3.3
15
+ dsh plugin --profile web add dsh-auth-remote@0.3.4
16
16
  dsh plugin --profile web list
17
17
  dsh web --no-open --port 13090
18
18
  ```
@@ -126,7 +126,7 @@ dsh web --no-open --tls-cert ./tls/dsh.crt --tls-key ./tls/dsh.key
126
126
 
127
127
  ## 启动并验证公开入口
128
128
 
129
- 1. 核对 Linux、Node.js 24+(推荐 DSH `0.2.2-alpha.2` 至少需要 `24.9.0`)、精确兼容 DSH 版本及目标 profile/包;测试开发数据独立。
129
+ 1. 核对 Linux、Node.js 24+(默认 DSH `0.2.2-alpha.3` 至少需要 `24.9.0`)、精确兼容 DSH 版本及目标 profile/包;测试开发数据独立。
130
130
  2. 合并一个完整 profile 配置,需要代理时建立私有可达上游,参见[代理指南](reverse-proxy.zh-CN.md)。
131
131
  3. 启动 DSH。HTTP 上游示例检查 `curl -fsS -H 'Host: dsh.example.com' http://127.0.0.1:13090/auth-remote/ready`,要求预期插件/协议和 `ready: true`。
132
132
  4. 核对匿名 HTML 跳转和 API 拒绝,再本地初始化、登录、绑定 TOTP、保存备用码。经所选入口测试官方设置、工作区、预览、上传、SSE/WebSocket 和撤销。
@@ -135,9 +135,13 @@ dsh web --no-open --tls-cert ./tls/dsh.crt --tls-key ./tls/dsh.key
135
135
 
136
136
  ## 备份、恢复与变更
137
137
 
138
- 升级到 `0.3.3` 前,停止 DSH 并备份认证目录、profile patch、package/lock;保持入口私有和独立 `webserver disabled: true`。确认宿主属于所列支持版本(推荐 `0.2.2-alpha.2`),安装插件并核对 ready、匿名拒绝、登录及撤销。回退时停服并恢复匹配的宿主/插件包、锁和 patch 备份。此次发布不改变认证数据格式;恢复时仍核对 schema,禁止覆盖运行中的状态。
138
+ 升级前记录原精确 DSH 版本、插件归档及摘要、profile 配置和 package/lock 文件。停止旧进程并确认 profile 锁释放,以私有权限备份完整目标 profile、认证状态、DSH 数据和配置,保留原始备份。先将备份复制到独立私有 `DSH_HOME`,演练所选精确宿主与已验证的 `0.3.4` 发布归档;验证不得复用生产 profile。
139
139
 
140
- 从早于 `0.3.2` 的插件升级时,须考虑 `0.3.2` 已引入、`0.3.3` 保留的行为:CLI 固定英语,删除脚本中的 `--lang` 参数;JSON 字段不变。独立登录页不提供语言选择器,按 `dsh-auth-remote-lang` 缓存、`navigator.language`、英文选择语言。旧 `dsh-auth-remote.locale` 不读取、不清理、不迁移;进入 DSH 后仅同步原生已接纳的偏好,退出保留。插件八语不会扩充 DSH 的原生语言目录。
140
+ 演练通过后再修改已停服的生产安装。在 readiness、匿名拒绝、登录与会话撤销检查通过前,保持公开入口私有,并保留独立 `webserver disabled: true`。不得覆盖运行中的状态;本版本不修改插件存储格式。
141
+
142
+ 回滚时先停止新进程,再恢复匹配的原精确宿主、插件归档、配置及对应完整数据备份。宿主切换测试只证明所覆盖的配置/会话契约,不承诺旧宿主可直接读取任意新生产数据;生产数据回滚必须使用对应备份。
143
+
144
+ 从早于 `0.3.2` 的插件升级时,须考虑 `0.3.2` 已引入、`0.3.4` 保留的行为:CLI 固定英语,删除脚本中的 `--lang` 参数;JSON 字段不变。独立登录页不提供语言选择器,按 `dsh-auth-remote-lang` 缓存、`navigator.language`、英文选择语言。旧 `dsh-auth-remote.locale` 不读取、不清理、不迁移;进入 DSH 后仅同步原生已接纳的偏好,退出保留。插件八语不会扩充 DSH 的原生语言目录。
141
145
 
142
146
  停止 DSH 并确认释放 profile 锁,再复制 `~/.dsh/profiles/web/auth-remote/auth-state.json`。副本目录权限 0700、文件权限 0600;它含密码哈希、TOTP 密钥、备用码哈希和会话。不要复制写入中的临时文件、覆盖运行中持锁状态或提交 Git;同时备份对应 profile patch 和包/锁文件。
143
147
 
@@ -2,9 +2,9 @@
2
2
 
3
3
  [简体中文](development.zh-CN.md)
4
4
 
5
- This guide describes nine exact verification targets for planned plugin release `0.3.3`, defaulting to DSH `0.2.2-alpha.2`. Final same-archive evidence belongs to unpackaged test reports; declarations and reports are distinct.
5
+ This guide describes nine exact verification targets for `0.3.4`, defaulting to DSH `0.2.2-alpha.3`. Final same-archive evidence belongs to unpackaged test reports; declarations and reports are distinct.
6
6
 
7
- Development and the full test suite use Linux (`/proc` is required for the profile lock), Node.js 24+, pnpm 12.5.1, and DSH `0.2.2-alpha.2`. DSH `0.2.2-alpha.2` itself requires Node.js `>=24.9.0`; the plugin engine stays `>=24`. Browser tests use Playwright-managed Chromium and a Node HTTP/HTTPS forwarder.
7
+ Development and the full test suite use Linux (`/proc` is required for the profile lock), Node.js 24+, pnpm 12.5.1, and DSH `0.2.2-alpha.3`. DSH `0.2.2-alpha.3` requires Node.js `>=24.9.0`; the plugin engine stays `>=24`. Browser tests use Playwright-managed Chromium and a Node HTTP/HTTPS forwarder.
8
8
 
9
9
  ## Set up and check a checkout
10
10
 
@@ -16,7 +16,7 @@ pnpm pack:local
16
16
  pnpm smoke
17
17
  ```
18
18
 
19
- `pnpm check` runs type checking, formatting, build, package/deployment/document checks, then unit, integration, CLI, and browser tests. `pnpm pack:local` writes `artifacts/dsh-auth-remote-0.3.3.tgz` after static checks; it does not publish. `pnpm smoke` installs that archive into an isolated DSH home, starts the pinned DSH runtime briefly, checks readiness, anonymous redirection/denial and an online CLI status, then stops it.
19
+ `pnpm check` runs type checking, formatting, build, package/deployment/document checks, then unit, integration, CLI, and browser tests. `pnpm pack:local` writes `artifacts/dsh-auth-remote-0.3.4.tgz` after static checks; it does not publish. `pnpm smoke` installs that archive into an isolated DSH home, starts the pinned DSH runtime briefly, checks readiness, anonymous redirection/denial and an online CLI status, then stops it.
20
20
 
21
21
  ## Use the isolated development profile
22
22
 
@@ -31,7 +31,7 @@ The scripts manage only `.dev/runtime-<version>` and `.dev/dsh-home` under this
31
31
  For direct inspection, use the same isolated home explicitly:
32
32
 
33
33
  ```sh
34
- DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.2-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.2-alpha.3/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
35
35
  ```
36
36
 
37
37
  The development home contains test account data. Keep it private and do not commit or copy it into a deployment profile.
@@ -40,7 +40,7 @@ The development home contains test account data. Keep it private and do not comm
40
40
 
41
41
  `pnpm test:unit` covers the auth state machine, TOTP, backup codes, origin policy, translations, storage durability and lock recovery. `pnpm test:integration` exercises real HTTP/WebSocket sockets, native readiness, cookies, origin decisions and revocation. `pnpm test:cli` builds the real archive and tests interactive and noninteractive commands against isolated profiles and Unix sockets. `pnpm test:browser` boots the selected DSH version with temporary profiles and verifies the login and Security & sign-in UI, native settings, workspace, upload/preview, SSE, WebSocket and an HTTPS forwarding chain.
42
42
 
43
- Browser network traffic uses a Node HTTP/HTTPS forwarder. The dedicated self-signed certificate and key under `tests/fixtures/tls/` are test fixtures only; they are never packaged or deployment credentials. Chat uses a local model stub. No real third-party authorization or paid model request is exercised. The default browser is Playwright Chromium; `DSH_TEST_BROWSER` can select a local browser executable, and `DSH_TEST_BIN` can select another binary only if it reports the exact selected version (default `0.2.2-alpha.2`).
43
+ Browser network traffic uses a Node HTTP/HTTPS forwarder. The dedicated self-signed certificate and key under `tests/fixtures/tls/` are test fixtures only; they are never packaged or deployment credentials. Chat uses a local model stub. No real third-party authorization or paid model request is exercised. The default browser is Playwright Chromium; `DSH_TEST_BROWSER` can select a local browser executable, and `DSH_TEST_BIN` can select another binary only if it reports the exact selected version (default `0.2.2-alpha.3`).
44
44
 
45
45
  Shared Host environments are allowlisted without real model credentials/endpoints; browser launch removes ambient proxy variables. Before first key entry, `localModelEndpoint` points native llm-deepseek baseURL at a local HTTP stub, without preseeded keys or disabled onboarding. UI cases require zero model calls; proxy chat allows only local chat and native session-title POSTs. Counts are checked at fixture close and unexpected requests fail.
46
46
 
@@ -54,7 +54,7 @@ Current support is in [README](../README.md#dsh-compatibility) and the [support
54
54
 
55
55
  ## Cross-version verification
56
56
 
57
- The default target is DSH `0.2.2-alpha.2`; `DSH_TEST_VERSION` accepts only `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`. Test runtimes live under `.cache/test-runtime/<version>` and development runtimes under `.dev/runtime-<version>`. `DSH_TEST_BIN` must report that exact version. CI keeps nine-version CLI/installation smoke; full runs nine complete browser targets and ordinary uses the selection below. Development types and integration use locked `0.2.2-alpha.2` packages. All nine targets check the real Loader, model runtime context/`DSH_WEB_URL`, and positive IPv4/IPv6 HTTP/HTTPS security boundaries. Missing native transport support fails instead of skipping.
57
+ The default target is DSH `0.2.2-alpha.3`; `DSH_TEST_VERSION` accepts only `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3`. Test runtimes live under `.cache/test-runtime/<version>` and development runtimes under `.dev/runtime-<version>`. `DSH_TEST_BIN` must report that exact version. CI keeps nine-version CLI/installation smoke; full runs nine complete browser targets and ordinary uses the selection below. Development types and integration use locked `0.2.2-alpha.3` packages. All nine targets check the real Loader, model runtime context/`DSH_WEB_URL`, and positive IPv4/IPv6 HTTP/HTTPS security boundaries. Missing native transport support fails instead of skipping.
58
58
 
59
59
  ```sh
60
60
  DSH_TEST_VERSION=0.2.1-alpha.3 pnpm test:cli
@@ -73,17 +73,17 @@ DSH_TEST_VERSION=0.2.1-rc.4 pnpm test:cli
73
73
  DSH_TEST_VERSION=0.2.1-rc.4 pnpm test:browser
74
74
  DSH_TEST_VERSION=0.2.1-rc.5 pnpm test:cli
75
75
  DSH_TEST_VERSION=0.2.1-rc.5 pnpm test:browser
76
- DSH_TEST_VERSION=0.2.2-alpha.2 pnpm test:cli
77
- DSH_TEST_VERSION=0.2.2-alpha.2 pnpm test:browser
76
+ DSH_TEST_VERSION=0.2.2-alpha.3 pnpm test:cli
77
+ DSH_TEST_VERSION=0.2.2-alpha.3 pnpm test:browser
78
78
  ```
79
79
 
80
80
  Browser tests save light/dark, desktop/narrow-screen screenshots under `.cache/ui-review/<version>` for visual review. Security CSS is installed and removed with the plugin, scopes its selectors to the plugin page, and reads the host's live `--dsw-*` tokens. The standalone login uses a subset of DSH 0.2.0-rc.1 theme tokens and the system color scheme without reading host preferences before authentication.
81
81
 
82
- Official-account tests use a local Platform stand-in with the actual DSH `0.2.2-alpha.2` account provider. They check the original redirect URI and PKCE verifier during exchange, rejected state/URL/session combinations, duplicate submissions, cancellation, expiry and retries. Browser coverage checks the instruction-first menu and onboarding dialog, failed loopback navigation followed by paste/confirm, blocked popups, live locale and responsive light/dark layout. These tests do not establish a real official-account authorization session.
82
+ Official-account tests use a local Platform stand-in with the actual DSH `0.2.2-alpha.3` account provider. They check the original redirect URI and PKCE verifier during exchange, rejected state/URL/session combinations, duplicate submissions, cancellation, expiry and retries. Browser coverage checks the instruction-first menu and onboarding dialog, failed loopback navigation followed by paste/confirm, blocked popups, live locale and responsive light/dark layout. These tests do not establish a real official-account authorization session.
83
83
 
84
84
  Core account tests load the exact provider from locked development dependencies, so they do not require a pre-existing CLI runtime cache. Browser tests still exercise the provider installed into each isolated DSH profile.
85
85
 
86
- The temporary account adapter retains capability and live-configuration checks; complete manual-feature regression targets `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2`. After global minimum admission the server no longer branches for older hosts; the separately exported helper still checks omitted, invalid and older inputs. Forward admission is not verification. Support or shared host-adapter changes require the same final tgz across all nine CLI, complete browser and smoke runs with `--suite cli --suite browser --suite smoke` per release. Never call rebuilding/repacking wrappers in the consumer loop. The runner restores archive dist, checks SHA-256 per suite and isolates smoke from development profiles. See `DSH-ACCOUNT-001` for public-callback evidence and migration/retirement conditions.
86
+ The temporary account adapter retains capability and live-configuration checks; complete manual-feature regression targets `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3`. After global minimum admission the server no longer branches for older hosts; the separately exported helper still checks omitted, invalid and older inputs. Forward admission is not verification. Support or shared host-adapter changes require the same final tgz across all nine CLI, complete browser and smoke runs with `--suite cli --suite browser --suite smoke` per release. Never call rebuilding/repacking wrappers in the consumer loop. The runner restores archive dist, checks SHA-256 per suite and isolates smoke from development profiles. See `DSH-ACCOUNT-001` for public-callback evidence and migration/retirement conditions.
87
87
 
88
88
  `live-config.spec.ts` observes the real Loader reference/fiber, auth/store identity, lock, listener and SSE/WebSocket continuity, checks the loaded dependency chain and restarts to verify the profile override. It does not fabricate services. Dialog regression covers cancellation/errors, focus/keyboard, optional/enforced TOTP, one-time code copying and redirect holds after revocation. Task documents, test credentials, profiles, screenshots and generated directories must remain outside the npm archive.
89
89
 
@@ -91,19 +91,19 @@ The temporary account adapter retains capability and live-configuration checks;
91
91
 
92
92
  The account preference binding recovers an initial failed read through the native describe mirror’s `ensure()` API. Recovery of an already held namespace uses the explicitly injected `remote.settings` transport and folds the accepted namespace back into that mirror. A sign-in click while the preference is loading waits for the shared read, then uses the latest accepted true/false value; loading does not select the native flow. Browser regression covers initial failure, a temporarily missing namespace and delayed reads for both routing choices.
93
93
 
94
- Native Search/Fetch settings regression on `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5` and `0.2.2-alpha.2` covers real settings/credentials selection, failed saves, refresh/restart persistence and anonymous/revoked-session refusal. Endpoints are local and request counts must stay zero. On `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5` and `0.2.2-alpha.2`, `rc-navigation.spec.ts` checks global/session/right-sidebar More menus, native settings/model selection and refusal after revocation. Market/Creator entries are inspected without installation or external authorization. Public sessions/sessionProjections APIs create a real session empty completed turn to expose native menus; no chat is sent and no snapshot is replaced. Official dynamic `/models` internal semantics are outside the verification claim.
94
+ Native Search/Fetch settings regression on `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3` covers real settings/credentials selection, failed saves, refresh/restart persistence and anonymous/revoked-session refusal. Endpoints are local and request counts must stay zero. On `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3`, `rc-navigation.spec.ts` checks global/session/right-sidebar More menus, native settings/model selection and refusal after revocation. Market/Creator entries are inspected without installation or external authorization. Public sessions/sessionProjections APIs create a real session empty completed turn to expose native menus; no chat is sent and no snapshot is replaced. Official dynamic `/models` internal semantics are outside the verification claim.
95
95
 
96
96
  Startup diagnostics use installed exact declarations and explicit lifecycle records, warning once per process/version/state even across configuration/module HMR. The three Alpha releases are legacy from 2026-10-28 with a 14-day window and earliest eligibility 2026-11-11 (Asia/Shanghai); dates never stop service. The six retired versions record last plugin `0.2.0`, retirement release `0.3.1` and preparation date `retiredOn: 2026-10-28`, which is not an actual npm publication timestamp. Mock-clock tests preserve classification after eligibility; real legacy HMR checks process-wide deduplication. API, package identity and security failures still refuse service.
97
97
 
98
- `browser/host-release.spec.ts` fixes eight real round trips: `0.2.1-alpha.4` ↔ `0.2.1-alpha.3`, `0.2.1-alpha.5` ↔ `0.2.1-alpha.4`, `0.2.1-rc.1` ↔ `0.2.1-alpha.5`, `0.2.1-rc.2` ↔ `0.2.1-rc.1`, `0.2.1-rc.3` ↔ `0.2.1-rc.2`, `0.2.1-rc.4` ↔ `0.2.1-rc.3`, `0.2.1-rc.5` ↔ `0.2.1-rc.4`, and `0.2.2-alpha.2` ↔ `0.2.1-rc.4`. Each keeps the page in one temporary profile/port, checks the native release prompt, reloads to verify authentication, the original session and persisted settings, then restores the starting release. Only `0.2.1-alpha.3` lacks release metadata and reads unknown; every other destination must show its actual full version. No upstream source, version or dependency-graph metadata is changed.
98
+ `browser/host-release.spec.ts` fixes eight real round trips: `0.2.1-alpha.4` ↔ `0.2.1-alpha.3`, `0.2.1-alpha.5` ↔ `0.2.1-alpha.4`, `0.2.1-rc.1` ↔ `0.2.1-alpha.5`, `0.2.1-rc.2` ↔ `0.2.1-rc.1`, `0.2.1-rc.3` ↔ `0.2.1-rc.2`, `0.2.1-rc.4` ↔ `0.2.1-rc.3`, `0.2.1-rc.5` ↔ `0.2.1-rc.4`, `0.2.2-alpha.3` ↔ `0.2.1-rc.5`. Each keeps the page in one temporary profile/port, checks the native release prompt, reloads to verify authentication, the original session and persisted settings, then restores the starting release. Only `0.2.1-alpha.3` lacks release metadata and reads unknown; every other destination must show its actual full version. No upstream source, version or dependency-graph metadata is changed.
99
99
 
100
100
  ## Consume a fixed archive
101
101
 
102
102
  `pnpm verify:packed` consumes an existing tgz without building or packing. Record its SHA-256 first, then pass the archive, that digest, an exact declared DSH release and one or more suites:
103
103
 
104
104
  ```sh
105
- sha256sum artifacts/dsh-auth-remote-0.3.3.tgz
106
- pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.3.tgz --sha256 <recorded-sha256> --dsh-version 0.2.2-alpha.2 --suite cli --suite browser --suite smoke
105
+ sha256sum artifacts/dsh-auth-remote-0.3.4.tgz
106
+ pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.4.tgz --sha256 <recorded-sha256> --dsh-version 0.2.2-alpha.3 --suite cli --suite browser --suite smoke
107
107
  ```
108
108
 
109
109
  The consumer validates the package name/version and selected release declaration, stages those exact bytes at the fixed artifact path and restores only the archive's dist. CLI execution and installation comparisons therefore use that dist. It rejects unsafe tar entries, a changed digest, unknown selections, zero actual tests and skipped/cancelled/todo tests. Node's passing placeholder for a test file with no matching cases does not count as a real test. `--test-name-pattern` optionally filters one `cli` or `browser` suite; its report is explicitly partial and includes the files, pattern and actual commands. Fixed specialized suites cannot override their filter/count requirements; every required file must register tests.
@@ -115,7 +115,7 @@ The consumer validates the package name/version and selected release declaration
115
115
  | `smoke` | Install and briefly boot the archive in a new marked home |
116
116
  | `theme` | The exact login/security theme and narrow-screen case (one real test) |
117
117
  | `account` | startup-compatibility, account-login and live-config on `0.2.1-alpha.3` |
118
- | `host-release` | One real round trip on `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` |
118
+ | `host-release` | One real round trip on `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.3` |
119
119
  | `rc-bootstrap` | host-release and dsh-bootstrap on `0.2.1-rc.1` (two real tests) |
120
120
 
121
121
  Consumption is serial within a checkout, enforced by a consumer lock. Each suite checks the input archive, fixed consumer archive and restored dist again. JSON reports and test logs remain under `.cache/verify-packed/`. Smoke creates its marked temporary root directly under `.cache/v-*` to keep the management socket within Linux's pathname limit in the default GitHub checkout. It uses its own runtime/home and `--port 0`; it reads only that child process's announced actual loopback address and checks online CLI status in the same profile. Existing `.dev/dsh-home` and services on 13090 are independent. Only the newly created verification root is removed. `DSH_VERIFY_ROOT` is internal and rejects unmarked, symlinked or external paths; ordinary development commands retain their existing profile and port.
@@ -125,7 +125,7 @@ Consumption is serial within a checkout, enforced by a consumer lock. Each suite
125
125
  `verify-retired.mjs` does not extend `DSH_TEST_VERSION` or the positive matrix. It checks the same candidate/SHA256SUMS and published `0.2.0` integrity, then uses two private old profiles for real CLI rejection/complete rollback and native peer skip of a whole incompatible package. The latter preserves actual old peer resolution, repeatedly confirms no TCP/HTTP/readiness/WebSocket listener, and cleans up processes. The six-host one-time acceptance belongs to the `0.3.1` migration history. Current full/release plans run only `0.2.1-alpha.2`, and ordinary runs none.
126
126
 
127
127
  ```sh
128
- node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.3.tgz --sha256 <recorded-sha256> --retired-dsh-version 0.2.1-alpha.2
128
+ node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.4.tgz --sha256 <recorded-sha256> --retired-dsh-version 0.2.1-alpha.2
129
129
  ```
130
130
 
131
131
  The six independent negative targets are `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`. Reports stay separate from positive evidence under `.cache/verify-retired/`.
@@ -146,14 +146,22 @@ Manual dispatch, unknown events, every release and the Monday 00:00 UTC schedule
146
146
  | `0.2.1-rc.3` | `browser` |
147
147
  | `0.2.1-rc.4` | `browser` |
148
148
  | `0.2.1-rc.5` | `browser` |
149
- | `0.2.2-alpha.2` | `browser` |
149
+ | `0.2.2-alpha.3` | `browser` |
150
150
 
151
151
  The shared workflow validates the exact matrix. Full requires validate, cli-smoke, browser and retired-rejection to succeed; ordinary accepts only the predetermined retired-rejection skip and requires the other three successes. Unknown plans, missing results, failures, cancellations and other skips fail. `CI Verify` also requires plan/producer success; releases use full and inherit the negative gate. Keep fixed-port tests serial per checkout; local parallel jobs require independent source/dist/artifacts/runtime/profile trees, writable node_modules copies and network namespaces. Copy-mode installation avoids shared HMR inode changes.
152
152
 
153
- On exact DSH `0.2.2-alpha.2`, `native-transport.spec.ts` compares genuine native asset/fallback bytes and ETags for GET/HEAD/304, rejects anonymous/revoked correct-tag requests, and retains immutable 200 semantics for real bundle/map/chunk artifacts and nonimmutable index behavior. Four real `/api/remote.mux` cases cover native HTTPS/proxy, default/none compression, whole-frame threshold/RSV1, successful ready frames and actual expiry/revocation. The installed native Gateway/ws owns transport and compression.
153
+ On exact DSH `0.2.2-alpha.3`, `native-transport.spec.ts` compares genuine native asset/fallback bytes and ETags for GET/HEAD/304, rejects anonymous/revoked correct-tag requests, and retains immutable 200 semantics for real bundle/map/chunk artifacts and nonimmutable index behavior. Four real `/api/remote.mux` cases cover native HTTPS/proxy, default/none compression, whole-frame threshold/RSV1, successful ready frames and actual expiry/revocation. The installed native Gateway/ws owns transport and compression.
154
154
 
155
155
  The new-host `account-login.spec.ts` source-HMR fault case preserves the initial instance on import failure, then throws after genuine replacement initialization to prove old/failed resource cleanup and native automatic rollback. It checks real provider fibers, listeners, state-lock nonces, mux closure, persisted authentication, the first restored Settings save and final lock reacquisition. The copied entry uses one canonical file URL and explicit native watch roots; public log export observes warnings without replacing HMR.
156
156
 
157
157
  Browser language tests cover all eight plugin dictionaries, login fallback/memory, native accepted preference vs optimistic edits, delayed/unavailable/failed reads and saves, storage failures and sign-out/revocation persistence. DSH's native language catalog is unchanged. CLI tests require fixed English across environment languages and reject every `--lang` form before profile access; the published `0.2.0` retired fixture keeps its historical Chinese contract.
158
158
 
159
- `liveshare.spec.ts` registers only on exact `0.2.2-alpha.2`: real native Host/Owner PKCE/share worker/viewer carriers and stop operations use a local Relay identity/transport stand-in. Viewer clients remain inert for administrator features. Tests do not establish real Relay/OAuth, visitor models or file writes. Partial filtered reports and file placeholders never certify the final nine-host archive.
159
+ `liveshare.spec.ts` registers on exact `0.2.2-alpha.3`: real native Host/Owner PKCE/share worker/viewer carriers and stop operations use a local Relay identity/transport stand-in. Viewer clients remain inert for administrator features. Tests do not establish real Relay/OAuth, visitor models or file writes. Partial filtered reports and file placeholders never certify the final nine-host archive.
160
+
161
+ Version `0.3.4` is prepared for release; actual availability is established by the release workflow and npm registry. Published `0.3.3` retains nine declarations; the new exact `0.2.2-alpha.3` claim is not retroactive. Release acceptance requires one final archive on Linux/Node.js 24 (at least `24.9.0` for the new default)/Chromium. Other Node majors cannot substitute for this acceptance; real proxy products, external authorization, a non-loopback IPv6 interface and other platforms/browsers remain unverified.
162
+
163
+ Direct development dependencies use DSH `0.2.2-alpha.3`, Cordis `4.0.6-alpha.2` and Schemastery `3.18.6-alpha.2`; the actual new host chain uses Loader `1.0.7-alpha.2` and Include `1.0.11-alpha.2`. These are distribution package versions. Keep `autoInstallPeers: false` and only verified, installer-required exact release-age exceptions. Configuration observation reads canonical `entry.fiber.ctx.fiber.effectiveConfig`, falling back to `config` only when the old host has no accessor; inactive fibers, absent values and non-`.get()` references fail. Production retains the constructor's native Volatile reference.
164
+
165
+ `settings-icon.spec.ts` registers on all nine hosts: `0.2.2-alpha.3` checks the native shield, size/currentColor/selection, light/dark narrow layouts, contribution release/default restoration, genuine declaration withdrawal/recreation without duplicates and disposal; the other eight check the default icon. Observation/release controls live only in fixtures, and native Loader resolves the modules. Viewers install no administrator effects. Complete browser verification checks mandatory mux/resource/HMR/icon TAP names as well as nonempty files; name-filtered runs are partial. Language cases assert the actual visited sets rather than relying on their titles.
166
+
167
+ LiveShare is an officially published, experimental optional plugin, disabled by default (`listedByDefault: false`); this plugin never enables it automatically. Necessary compatibility applies to exact `0.2.2-alpha.3`. Local protocol stand-ins do not establish production Relay/OAuth, real visitor model operations or file writing. Private-interface dependencies and unknown-host limits remain in the inventory.
@@ -2,9 +2,9 @@
2
2
 
3
3
  [English](development.md)
4
4
 
5
- 本指南描述计划发布 `0.3.3` 的九版精确验证目标,默认 DSH `0.2.2-alpha.2`。最终同包运行证据保存在包外测试报告中;声明与实测报告分开表达。
5
+ 本指南描述版本 `0.3.4` 的九版精确验证目标,默认 DSH `0.2.2-alpha.3`。最终同包运行证据保存在包外测试报告中;声明与实测报告分开表达。
6
6
 
7
- 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.2-alpha.2`。DSH `0.2.2-alpha.2` 自身要求 Node.js `>=24.9.0`;插件引擎仍为 `>=24`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
7
+ 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.2-alpha.3`。DSH `0.2.2-alpha.3` 自身要求 Node.js `>=24.9.0`;插件引擎仍为 `>=24`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
8
8
 
9
9
  兼容声明或适配变更前,先阅读 [Legacy 兼容维护清单](legacy-compatibility.zh-CN.md)。共同复核运行时准入、测试目标、CI 和用户声明;适用版本退出支持集合时同次清理专属运行时代码及测试。旧插件配置按自身迁移策略退役,保留共享安全逻辑,并用完整版本号与精确版本证据同步更新中英文清单及两个维度的矩阵。
10
10
 
@@ -18,7 +18,7 @@ pnpm pack:local
18
18
  pnpm smoke
19
19
  ```
20
20
 
21
- `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.3.3.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
21
+ `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.3.4.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
22
22
 
23
23
  ## 使用隔离开发 profile
24
24
 
@@ -33,7 +33,7 @@ pnpm dev:start
33
33
  直接查看状态时显式使用同一隔离 home:
34
34
 
35
35
  ```sh
36
- DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.2-alpha.2/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
36
+ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.2-alpha.3/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
37
37
  ```
38
38
 
39
39
  开发 home 可能含测试账号数据,须保持私有,不要提交或复制到部署 profile。
@@ -42,7 +42,7 @@ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.2-alpha.2/node_modules/.bin
42
42
 
43
43
  `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 转发链。
44
44
 
45
- 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.2-alpha.2`)时可替换 DSH 二进制。
45
+ 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.2-alpha.3`)时可替换 DSH 二进制。
46
46
 
47
47
  共享 Host 环境由 allowlist 构造,清除真实模型凭据/endpoint;浏览器清除 ambient 代理变量。`localModelEndpoint` 在首次输入 Key 前把原生 llm-deepseek baseURL 指向本地 HTTP 替身,不预存 Key、不关闭引导。UI 专项要求零模型调用;代理聊天只接纳本地 chat 和原生 session-title 两次 POST。计数在 fixture 关闭时检查,异常请求使测试失败。
48
48
 
@@ -54,7 +54,7 @@ DSH 测试运行时位于 `.cache/test-runtime/<version>`,与源码依赖分
54
54
 
55
55
  ## 跨版本验证
56
56
 
57
- 默认测试 DSH `0.2.2-alpha.2`;`DSH_TEST_VERSION` 仅可选择 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.2`。测试运行时位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`;`DSH_TEST_BIN` 必须报告所选精确版本。CI 保留九版 CLI/安装 smoke,全量运行九版完整 browser,普通使用下文固定选择。开发类型与集成测试使用锁定的 `0.2.2-alpha.2` 包。九版均验证真实 Loader、模型 runtime context/`DSH_WEB_URL` 和 IPv4/IPv6 HTTP/HTTPS 正向安全边界;测试传输不可用时失败,不跳过。
57
+ 默认测试 DSH `0.2.2-alpha.3`;`DSH_TEST_VERSION` 仅可选择 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.3`。测试运行时位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`;`DSH_TEST_BIN` 必须报告所选精确版本。CI 保留九版 CLI/安装 smoke,全量运行九版完整 browser,普通使用下文固定选择。开发类型与集成测试使用锁定的 `0.2.2-alpha.3` 包。九版均验证真实 Loader、模型 runtime context/`DSH_WEB_URL` 和 IPv4/IPv6 HTTP/HTTPS 正向安全边界;测试传输不可用时失败,不跳过。
58
58
 
59
59
  ```sh
60
60
  DSH_TEST_VERSION=0.2.1-alpha.3 pnpm test:cli
@@ -73,17 +73,17 @@ DSH_TEST_VERSION=0.2.1-rc.4 pnpm test:cli
73
73
  DSH_TEST_VERSION=0.2.1-rc.4 pnpm test:browser
74
74
  DSH_TEST_VERSION=0.2.1-rc.5 pnpm test:cli
75
75
  DSH_TEST_VERSION=0.2.1-rc.5 pnpm test:browser
76
- DSH_TEST_VERSION=0.2.2-alpha.2 pnpm test:cli
77
- DSH_TEST_VERSION=0.2.2-alpha.2 pnpm test:browser
76
+ DSH_TEST_VERSION=0.2.2-alpha.3 pnpm test:cli
77
+ DSH_TEST_VERSION=0.2.2-alpha.3 pnpm test:browser
78
78
  ```
79
79
 
80
80
  浏览器测试把浅色/深色、桌面/窄屏截图保存在 `.cache/ui-review/<version>`,供人工检查。安全页的 CSS 在插件生效时注入、销毁时移除,所有选择器只作用于插件页面,并直接引用宿主 `--dsw-*` 主题变量。独立登录页使用 dsh 0.2.0-rc.1 的主题变量子集并跟随系统配色,不读取登录前不可用的宿主设置。
81
81
 
82
- 官方账号专项测试使用本地平台替身与真实 DSH `0.2.2-alpha.2` 账号提供者,验证兑换保留原始 redirect URI 和 PKCE verifier,以及错误 state/URL/会话、重复提交、取消、过期和重试。浏览器覆盖账号菜单与引导中的先说明弹窗、回环导航失败后粘贴确认、弹窗拦截、动态语言与浅深色响应式布局。这些测试不会建立真实官方账号授权。
82
+ 官方账号专项测试使用本地平台替身与真实 DSH `0.2.2-alpha.3` 账号提供者,验证兑换保留原始 redirect URI 和 PKCE verifier,以及错误 state/URL/会话、重复提交、取消、过期和重试。浏览器覆盖账号菜单与引导中的先说明弹窗、回环导航失败后粘贴确认、弹窗拦截、动态语言与浅深色响应式布局。这些测试不会建立真实官方账号授权。
83
83
 
84
84
  账号核心测试从锁定的开发依赖加载精确版本提供者,无需预先存在 CLI 运行时缓存;浏览器测试仍使用隔离 DSH profile 中实际安装的提供者。
85
85
 
86
- 此临时账号适配保留必要能力与动态配置检查;完整手动功能回归覆盖 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.2`。全局下限准入后的服务端不再分流旧宿主,独立导出 helper 仍检查缺省、无效和旧版本参数。未来准入不构成已验证声明。支持范围或共享宿主适配变更须用同一最终 tgz 完整运行九版 CLI、browser 与 smoke,逐版执行 `--suite cli --suite browser --suite smoke`;禁止在消费循环调用重建/重打包包装命令。运行器恢复归档 dist、逐 suite 校验 SHA-256,并隔离 smoke 与开发 profile。公网回调、迁移及退役条件见 `DSH-ACCOUNT-001`。
86
+ 此临时账号适配保留必要能力与动态配置检查;完整手动功能回归覆盖 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.3`。全局下限准入后的服务端不再分流旧宿主,独立导出 helper 仍检查缺省、无效和旧版本参数。未来准入不构成已验证声明。支持范围或共享宿主适配变更须用同一最终 tgz 完整运行九版 CLI、browser 与 smoke,逐版执行 `--suite cli --suite browser --suite smoke`;禁止在消费循环调用重建/重打包包装命令。运行器恢复归档 dist、逐 suite 校验 SHA-256,并隔离 smoke 与开发 profile。公网回调、迁移及退役条件见 `DSH-ACCOUNT-001`。
87
87
 
88
88
  `live-config.spec.ts` 仅观察真实 Loader 的配置引用/fiber、认证/存储实例、锁、监听器及 SSE/WebSocket 连续性,核对实际依赖链并重启验证 profile override;不伪造服务。安全弹窗回归覆盖取消/错误、焦点/键盘、默认及强制 TOTP、一次性备用码复制与会话撤销后跳转保持。任务文档、测试凭证、profile、截图及生成目录不得进入 npm 包。
89
89
 
@@ -91,19 +91,19 @@ DSH_TEST_VERSION=0.2.2-alpha.2 pnpm test:browser
91
91
 
92
92
  账号配置绑定通过原生 describe 镜像的 `ensure()` API 恢复首次读取失败;已有镜像中的命名空间恢复使用明确注入的 `remote.settings` 传输,并将已接纳值回填到同一镜像。偏好加载期间点击登录会等待共享读取,再按最新接纳的 true/false 值选择入口;加载中不等同于关闭。浏览器回归覆盖首次读取失败、命名空间暂缺,以及两种路由选择的延迟读取。
93
93
 
94
- `0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.2` 的原生 Search/Fetch 设置回归覆盖真实设置/凭据域的选择、保存失败和刷新/重启持久化,以及匿名/撤销会话拒绝。全部地址为本地测试地址,请求计数必须为零。`rc-navigation.spec.ts` 在 `0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.2` 验证全局、会话、右侧栏 More 菜单、原生设置/模型选择及撤销后拒绝;只检查插件市场/Creator 入口可见,不执行安装或外部授权。通过公开 sessions/sessionProjections 构造真实会话的空完成 turn 以展示原生菜单,不发送聊天,不替换快照。官方动态 `/models` 内部语义不在承诺内。
94
+ `0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.3` 的原生 Search/Fetch 设置回归覆盖真实设置/凭据域的选择、保存失败和刷新/重启持久化,以及匿名/撤销会话拒绝。全部地址为本地测试地址,请求计数必须为零。`rc-navigation.spec.ts` 在 `0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.3` 验证全局、会话、右侧栏 More 菜单、原生设置/模型选择及撤销后拒绝;只检查插件市场/Creator 入口可见,不执行安装或外部授权。通过公开 sessions/sessionProjections 构造真实会话的空完成 turn 以展示原生菜单,不发送聊天,不替换快照。官方动态 `/models` 内部语义不在承诺内。
95
95
 
96
96
  启动维护诊断读取已安装插件的精确声明与显式生命周期记录,同一进程每个精确版本/状态只提示一次,配置/模块 HMR 不重置。三个 Alpha 的 legacy 起算 2026-10-28、14 日窗口、最早资格 2026-11-11(Asia/Shanghai),日期不会停服。六个退役版本记录最后插件 `0.2.0`、退役版本 `0.3.1` 和准备日期 `retiredOn: 2026-10-28`,该日期不是 npm 实际发布时间。单元以模拟时钟确认到期不改变分类;真实 legacy HMR 用例观察同进程去重。必要 API、包身份和安全失败仍拒绝服务。
97
97
 
98
- `browser/host-release.spec.ts` 固定八组真实宿主往返切换:`0.2.1-alpha.4` ↔ `0.2.1-alpha.3`、`0.2.1-alpha.5` ↔ `0.2.1-alpha.4`、`0.2.1-rc.1` ↔ `0.2.1-alpha.5`、`0.2.1-rc.2` ↔ `0.2.1-rc.1`、`0.2.1-rc.3` ↔ `0.2.1-rc.2`、`0.2.1-rc.4` ↔ `0.2.1-rc.3`、`0.2.1-rc.5` ↔ `0.2.1-rc.4`、`0.2.2-alpha.2` ↔ `0.2.1-rc.4`。同一临时 profile/端口保留页面,检查原生版本提示,刷新后核对认证、原会话和持久设置,再恢复起始版本。只有 `0.2.1-alpha.3` 无 release 元数据并显示未解析;其余目的宿主必须显示真实完整版本。不修改上游源码、版本或依赖图元数据。
98
+ `browser/host-release.spec.ts` 固定八组真实宿主往返切换:`0.2.1-alpha.4` ↔ `0.2.1-alpha.3`、`0.2.1-alpha.5` ↔ `0.2.1-alpha.4`、`0.2.1-rc.1` ↔ `0.2.1-alpha.5`、`0.2.1-rc.2` ↔ `0.2.1-rc.1`、`0.2.1-rc.3` ↔ `0.2.1-rc.2`、`0.2.1-rc.4` ↔ `0.2.1-rc.3`、`0.2.1-rc.5` ↔ `0.2.1-rc.4`、`0.2.2-alpha.3` ↔ `0.2.1-rc.5`。同一临时 profile/端口保留页面,检查原生版本提示,刷新后核对认证、原会话和持久设置,再恢复起始版本。只有 `0.2.1-alpha.3` 无 release 元数据并显示未解析;其余目的宿主必须显示真实完整版本。不修改上游源码、版本或依赖图元数据。
99
99
 
100
100
  ## 消费固定归档
101
101
 
102
102
  `pnpm verify:packed` 消费已有 tgz,不构建或打包。先记录 SHA-256,再传入归档、该摘要、精确声明的 DSH 版本及一个或多个 suite:
103
103
 
104
104
  ```sh
105
- sha256sum artifacts/dsh-auth-remote-0.3.3.tgz
106
- pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.3.tgz --sha256 <recorded-sha256> --dsh-version 0.2.2-alpha.2 --suite cli --suite browser --suite smoke
105
+ sha256sum artifacts/dsh-auth-remote-0.3.4.tgz
106
+ pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.4.tgz --sha256 <recorded-sha256> --dsh-version 0.2.2-alpha.3 --suite cli --suite browser --suite smoke
107
107
  ```
108
108
 
109
109
  运行器验证包名/版本及所选宿主声明,将相同字节放到固定制品路径,仅恢复归档中的 dist,因此 CLI 执行与安装比较都使用这份 dist。不安全 tar 条目、摘要变化、未知选择、零真实用例及 skipped/cancelled/todo 用例均失败。Node 对无匹配用例文件产生的通过占位项不计作真实测试。`--test-name-pattern` 可筛选单个 `cli` 或 `browser` suite,报告明确标记为局部,并包含文件、筛选表达式与实际命令。固定专项不能覆盖其筛选/数量要求,每个必需文件均须注册测试。
@@ -115,7 +115,7 @@ pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.3.tgz --sha256 <recor
115
115
  | `smoke` | 在新建且带标记的 home 中安装并短暂启动归档 |
116
116
  | `theme` | 精确登录/安全主题与窄屏用例(1 个真实测试) |
117
117
  | `account` | `0.2.1-alpha.3` 的 startup-compatibility、account-login 与 live-config |
118
- | `host-release` | `0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.2` 的真实往返切换(1 个真实测试) |
118
+ | `host-release` | `0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.3` 的真实往返切换(1 个真实测试) |
119
119
  | `rc-bootstrap` | `0.2.1-rc.1` 的 host-release 与 dsh-bootstrap(2 个真实测试) |
120
120
 
121
121
  同一 checkout 的消费以锁保证串行。每个 suite 结束均重新校验输入归档、固定消费归档及恢复的 dist。JSON 报告和测试日志保留在 `.cache/verify-packed/`。smoke 直接在 `.cache/v-*` 新建带内部标记的短目录,确保默认 GitHub 检出路径下的管理 socket 不超过 Linux 路径上限;使用独立 runtime/home,以 `--port 0` 启动,仅读取该子进程公布的实际回环地址,并在相同 profile 检查在线 CLI 状态。既有 `.dev/dsh-home` 和 13090 上的服务保持独立,只清理本次新建的验证根目录。`DSH_VERIFY_ROOT` 是内部入口,拒绝无标记、符号链接及外部路径;普通开发命令保留原有 profile 和端口。
@@ -125,7 +125,7 @@ pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.3.tgz --sha256 <recor
125
125
  `verify-retired.mjs` 不扩展 `DSH_TEST_VERSION` 或正向矩阵。它核验同一候选/SHA256SUMS 及已发布 `0.2.0` 的完整性,在两个私有旧 profile 验证真实 CLI 安装拒绝/完整回滚,以及完整不兼容包的原生 peer skip。后一路保留真实旧 peer 解析、连续确认无 TCP/HTTP/readiness/WebSocket 监听并清理进程。六版一次性验收属于 `0.3.1` 迁移历史;当前 full/发布仅运行 `0.2.1-alpha.2`,ordinary 不运行。
126
126
 
127
127
  ```sh
128
- node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.3.tgz --sha256 <recorded-sha256> --retired-dsh-version 0.2.1-alpha.2
128
+ node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.4.tgz --sha256 <recorded-sha256> --retired-dsh-version 0.2.1-alpha.2
129
129
  ```
130
130
 
131
131
  六个独立负向目标:`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/verify-retired/`。
@@ -146,14 +146,22 @@ node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.3.tgz --
146
146
  | `0.2.1-rc.3` | `browser` |
147
147
  | `0.2.1-rc.4` | `browser` |
148
148
  | `0.2.1-rc.5` | `browser` |
149
- | `0.2.2-alpha.2` | `browser` |
149
+ | `0.2.2-alpha.3` | `browser` |
150
150
 
151
151
  共享工作流先验证精确矩阵。full 聚合要求 validate、cli-smoke、browser、retired-rejection 全部成功;ordinary 仅接受 retired-rejection 的预定 skipped,其余必须成功。未知 plan、缺失结果、失败/取消或其他 skip 均拒绝。`CI Verify` 还要求 plan/producer 成功,发布固定 full 并继承负向门禁。单 checkout 固定端口测试串行;本地并发需独立源码/dist/制品/runtime/profile、可写 node_modules 副本及网络命名空间,复制安装避免共享 HMR inode 变化。
152
152
 
153
- 精确 DSH `0.2.2-alpha.2` 的 `native-transport.spec.ts` 比较真实原生 asset/fallback 文件与 ETag,覆盖 GET/HEAD/304、匿名/撤销携正确 ETag 仍拒绝;真实 bundle/map/chunk 保留 immutable 200,index 不采用 immutable 缓存。四个真实 `/api/remote.mux` 用例覆盖原生 HTTPS/代理、默认/none 压缩、whole-frame 阈值/RSV1、成功 ready 帧和真实到期/撤销;传输和压缩仍由原生 Gateway/ws 实现。
153
+ 精确 DSH `0.2.2-alpha.3` 的 `native-transport.spec.ts` 比较真实原生 asset/fallback 文件与 ETag,覆盖 GET/HEAD/304、匿名/撤销携正确 ETag 仍拒绝;真实 bundle/map/chunk 保留 immutable 200,index 不采用 immutable 缓存。四个真实 `/api/remote.mux` 用例覆盖原生 HTTPS/代理、默认/none 压缩、whole-frame 阈值/RSV1、成功 ready 帧和真实到期/撤销;传输和压缩仍由原生 Gateway/ws 实现。
154
154
 
155
155
  新版 `account-login.spec.ts` 的 source HMR 故障用例在导入失败时保留原实例,再于真实替换实例完成初始化后抛错,验证旧/失败资源清理和原生自动回滚。检查真实 provider fiber、监听器、状态锁 nonce、mux 关闭、认证持久性、恢复后的首次 Settings 保存和最终锁再获取。副本入口使用统一 file URL 与显式原生监听 root;公开日志 exporter 只观测 warn,不替换 HMR。
156
156
 
157
157
  浏览器语言测试覆盖插件八语、登录回退/记忆、原生已接纳偏好与乐观选择、延迟/不可用/失败读取和保存、存储失败,以及退出/撤销后保留;不改变 DSH 原生语言目录。CLI 在不同环境语言下须固定英语,各种 `--lang` 在 profile 访问前拒绝;退役夹具对已发布 `0.2.0` 保留历史中文合同。
158
158
 
159
- `liveshare.spec.ts` 仅在精确 `0.2.2-alpha.2` 注册:真实原生 Host/Owner PKCE/分享 worker/查看页载体和停止操作配本地 Relay 身份/传输替身;viewer 不挂载管理员功能。不宣称真实 Relay/OAuth、访客模型或文件写入已验证。局部筛选报告和文件 placeholder 不认证最终九版归档。
159
+ `liveshare.spec.ts` 在精确 `0.2.2-alpha.3` 注册:真实原生 Host/Owner PKCE/分享 worker/查看页载体和停止操作配本地 Relay 身份/传输替身;viewer 不挂载管理员功能。不宣称真实 Relay/OAuth、访客模型或文件写入已验证。局部筛选报告和文件 placeholder 不认证最终九版归档。
160
+
161
+ 版本 `0.3.4` 的发布可用性由发布工作流和 npm registry 确认;已发布 `0.3.3` 保留九版声明,新增精确 `0.2.2-alpha.3` 不追溯给旧包。发布以同一最终归档的全量验收为前提;Linux/Node.js 24(新默认至少 `24.9.0`)/Chromium 为本次边界,其他 Node 大版本不能替代验收,真实代理产品/外部授权/非回环 IPv6 网卡/其他平台浏览器仍未验证。
162
+
163
+ 直接开发依赖为 DSH `0.2.2-alpha.3`、Cordis `4.0.6-alpha.2`、Schemastery `3.18.6-alpha.2`;实际新宿主链使用 Loader `1.0.7-alpha.2` 和 Include `1.0.11-alpha.2`。这些是分发包版本。保留 `autoInstallPeers: false`,发布时间例外只列经核验且安装器要求的精确版本。配置观测读取 canonical `entry.fiber.ctx.fiber` 的 `effectiveConfig`,只有不存在访问器的旧宿主才回退 `config`;未激活、缺值或非 `.get()` 引用报错。生产构造参数继续保留原生 Volatile。
164
+
165
+ `settings-icon.spec.ts` 在九版均注册:`0.2.2-alpha.3` 验证原生盾牌/size/currentColor/选中态、明暗窄屏、贡献释放默认恢复、真实声明撤下重建去重及卸载;其他八版验证默认图标。观测和释放入口仅在 fixture,模块仍由宿主 Loader 解析;viewer 不安装管理员效果。完整 browser 除整文件非空外,还核对必需 mux/资源/HMR/图标 TAP 名称;名称筛选明确为 partial。八语用例断言实际访问集合,不以标题代替执行。
166
+
167
+ LiveShare 是官方已发布、默认关闭的实验性可选插件(`listedByDefault: false`),本插件不自动启用。必要兼容只在精确 `0.2.2-alpha.3` 维护;本地协议替身不证明生产 Relay/OAuth、真实访客模型或文件写入。私有接口依赖与未知宿主限制见兼容库存。