dsh-auth-remote 0.3.5 → 0.3.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +9 -0
- package/CHANGELOG.zh-CN.md +9 -0
- package/CONTRIBUTING.md +2 -2
- package/CONTRIBUTING.zh-CN.md +2 -2
- package/README.md +19 -19
- package/README.zh-CN.md +19 -19
- package/dist/client.js +106 -16
- package/dist/client.js.map +3 -3
- package/dist/index.js +17 -20
- package/dist/index.js.map +2 -2
- package/dist/types/shared/dsh-support.d.ts +3 -0
- package/dist/types/shared/dsh-support.d.ts.map +1 -1
- package/docs/deployment.md +8 -6
- package/docs/deployment.zh-CN.md +8 -6
- package/docs/development.md +55 -51
- package/docs/development.zh-CN.md +55 -51
- package/docs/legacy-compatibility.md +132 -101
- package/docs/legacy-compatibility.zh-CN.md +124 -93
- package/docs/releasing.md +27 -14
- package/docs/releasing.zh-CN.md +27 -14
- package/docs/support-history.md +68 -66
- package/docs/support-history.zh-CN.md +50 -48
- package/docs/support-policy.md +23 -20
- package/docs/support-policy.zh-CN.md +24 -19
- package/package.json +14 -16
|
@@ -14,6 +14,9 @@ export interface RetiredDshRecord {
|
|
|
14
14
|
effectivePlugin: string;
|
|
15
15
|
lastSupportedPlugin: string;
|
|
16
16
|
migrationTarget: string;
|
|
17
|
+
legacySince?: string;
|
|
18
|
+
windowDays?: number;
|
|
19
|
+
eligibleRetirement?: string;
|
|
17
20
|
}
|
|
18
21
|
export type DshLifecycleRecord = LegacyDshRecord | RetiredDshRecord;
|
|
19
22
|
export type DshSupport = {
|
|
@@ -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;
|
|
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;IACvB,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB,UAAU,CAAC,EAAE,MAAM,CAAA;IACnB,kBAAkB,CAAC,EAAE,MAAM,CAAA;CAC5B;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;AAEnE,eAAO,MAAM,mBAAmB,EAAE,SAAS,eAAe,EAAO,CAAA;AAGjE,eAAO,MAAM,oBAAoB,EAAE,SAAS,gBAAgB,EA8B3D,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"}
|
package/docs/deployment.md
CHANGED
|
@@ -2,9 +2,9 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](deployment.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
This guide covers `0.3.
|
|
5
|
+
This guide covers candidate `0.3.6` and recommended RC prerelease host DSH `0.2.2-rc.2`. The candidate is unpublished; use npm installation commands only after publication, and a verified candidate archive in an independent profile beforehand. See [README](../README.md#dsh-compatibility) for eight declarations, the [support policy](support-policy.md) for maintenance and [development](development.md) for source builds. Published `0.3.5` retains its original ten declarations and archive as the last supporting plugin for the three retired Alphas. Use the default `~/.dsh` only for your intended account, never verification.
|
|
6
6
|
|
|
7
|
-
Production acceptance is bounded to Linux with `/proc`, Node.js 24 and Playwright Chromium. DSH `0.2.2-rc.
|
|
7
|
+
Production acceptance is bounded to Linux with `/proc`, Node.js 24 and Playwright Chromium. DSH `0.2.2-rc.2` requires Node `>=24.9.0`; the plugin engine stays `>=24`. The RC prerelease 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
|
|
|
@@ -12,7 +12,7 @@ After the independent-profile rehearsal and backup below, use the same intended
|
|
|
12
12
|
|
|
13
13
|
```sh
|
|
14
14
|
dsh --version
|
|
15
|
-
dsh plugin --profile web add dsh-auth-remote@0.3.
|
|
15
|
+
dsh plugin --profile web add dsh-auth-remote@0.3.6
|
|
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
|
|
129
|
+
1. Verify Linux, Node.js 24 (at least `24.9.0` for default DSH `0.2.2-rc.2`), 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,13 +135,15 @@ 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, 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.
|
|
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.6` candidate or published archive; do not reuse a production profile for verification.
|
|
139
139
|
|
|
140
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
141
|
|
|
142
|
+
For `0.2.1-alpha.3`, `0.2.1-alpha.4` or `0.2.1-alpha.5`, retain the available last-supporting `0.3.5` archive and its checksum before migration. `0.3.6` withdraws maintenance after the original 2026-10-28/14-day/2026-11-11 window; `retiredOn: 2026-11-13` is a preparation date, not the registry timestamp. The technical floor stays `>=0.2.1-alpha.3`; a warning is not an assurance that an old host is compatible. Rehearse migration to `0.2.2-rc.2` with the verified new archive and complete backup before changing the live service.
|
|
143
|
+
|
|
142
144
|
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
145
|
|
|
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.
|
|
146
|
+
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.6`: 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.
|
|
145
147
|
|
|
146
148
|
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.
|
|
147
149
|
|
package/docs/deployment.zh-CN.md
CHANGED
|
@@ -2,9 +2,9 @@
|
|
|
2
2
|
|
|
3
3
|
[English](deployment.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
本指南面向候选 `0.3.6` 及推荐 RC 预发布宿主 DSH `0.2.2-rc.2`。候选尚未发布;npm 安装命令仅在发布后使用,此前只能在独立 profile 消费已验证候选归档。八版声明见 [README](../README.zh-CN.md#dsh-兼容性),维护见[支持规范](support-policy.zh-CN.md),源码构建见[开发指南](development.zh-CN.md)。已发布 `0.3.5` 保留原十版声明和归档,是三个退役 Alpha 的最后支持插件。默认 `~/.dsh` 只用于预期账号,不用于验证。
|
|
6
6
|
|
|
7
|
-
生产验收边界为带 `/proc` 的 Linux、Node.js 24 和 Playwright Chromium。DSH `0.2.2-rc.
|
|
7
|
+
生产验收边界为带 `/proc` 的 Linux、Node.js 24 和 Playwright Chromium。DSH `0.2.2-rc.2` 要求 Node `>=24.9.0`;插件引擎仍为 `>=24`。RC 预发布宿主不是上游稳定版。规定的本地测试覆盖原生 IPv4/IPv6 HTTP/HTTPS 与既有 Node 转发拓扑;真实非回环 IPv6 网卡、其他平台/浏览器、真实 Nginx/Traefik、官方账号授权及生产 Relay/OAuth 未验证,本地协议替身不证明真实服务行为。
|
|
8
8
|
|
|
9
9
|
## 最小化安装
|
|
10
10
|
|
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
|
|
13
13
|
```sh
|
|
14
14
|
dsh --version
|
|
15
|
-
dsh plugin --profile web add dsh-auth-remote@0.3.
|
|
15
|
+
dsh plugin --profile web add dsh-auth-remote@0.3.6
|
|
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
|
|
129
|
+
1. 核对 Linux、Node.js 24(默认 DSH `0.2.2-rc.2` 至少需要 `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,13 +135,15 @@ dsh web --no-open --tls-cert ./tls/dsh.crt --tls-key ./tls/dsh.key
|
|
|
135
135
|
|
|
136
136
|
## 备份、恢复与变更
|
|
137
137
|
|
|
138
|
-
升级前记录原精确 DSH 版本、插件归档及摘要、profile 配置和 package/lock 文件。停止旧进程并确认 profile 锁释放,以私有权限备份完整目标 profile、认证状态、DSH 数据和配置,保留原始备份。先将备份复制到独立私有 `DSH_HOME`,演练所选精确宿主与已验证的 `0.3.
|
|
138
|
+
升级前记录原精确 DSH 版本、插件归档及摘要、profile 配置和 package/lock 文件。停止旧进程并确认 profile 锁释放,以私有权限备份完整目标 profile、认证状态、DSH 数据和配置,保留原始备份。先将备份复制到独立私有 `DSH_HOME`,演练所选精确宿主与已验证的 `0.3.6` 候选或发布归档;验证不得复用生产 profile。
|
|
139
139
|
|
|
140
140
|
演练通过后再修改已停服的生产安装。在 readiness、匿名拒绝、登录与会话撤销检查通过前,保持公开入口私有,并保留独立 `webserver disabled: true`。不得覆盖运行中的状态;本版本不修改插件存储格式。
|
|
141
141
|
|
|
142
|
+
从 `0.2.1-alpha.3`、`0.2.1-alpha.4` 或 `0.2.1-alpha.5` 迁移前,保留可获取的最后支持插件 `0.3.5` 归档及摘要。`0.3.6` 在原2026-10-28起算/14日/2026-11-11资格窗口后撤回维护;`retiredOn: 2026-11-13` 是准备日期,不是 registry 时间。技术下限仍为 `>=0.2.1-alpha.3`,告警运行不等于旧宿主兼容保证。先用已验证新归档及完整备份,在独立 profile 演练 `0.2.2-rc.2`,再变更在线服务。
|
|
143
|
+
|
|
142
144
|
回滚时先停止新进程,再恢复匹配的原精确宿主、插件归档、配置及对应完整数据备份。宿主切换测试只证明所覆盖的配置/会话契约,不承诺旧宿主可直接读取任意新生产数据;生产数据回滚必须使用对应备份。
|
|
143
145
|
|
|
144
|
-
从早于 `0.3.2` 的插件升级时,须考虑 `0.3.2` 已引入、`0.3.
|
|
146
|
+
从早于 `0.3.2` 的插件升级时,须考虑 `0.3.2` 已引入、`0.3.6` 保留的行为:CLI 固定英语,删除脚本中的 `--lang` 参数;JSON 字段不变。独立登录页不提供语言选择器,按 `dsh-auth-remote-lang` 缓存、`navigator.language`、英文选择语言。旧 `dsh-auth-remote.locale` 不读取、不清理、不迁移;进入 DSH 后仅同步原生已接纳的偏好,退出保留。插件八语不会扩充 DSH 的原生语言目录。
|
|
145
147
|
|
|
146
148
|
停止 DSH 并确认释放 profile 锁,再复制 `~/.dsh/profiles/web/auth-remote/auth-state.json`。副本目录权限 0700、文件权限 0600;它含密码哈希、TOTP 密钥、备用码哈希和会话。不要复制写入中的临时文件、覆盖运行中持锁状态或提交 Git;同时备份对应 profile patch 和包/锁文件。
|
|
147
149
|
|
package/docs/development.md
CHANGED
|
@@ -2,9 +2,9 @@
|
|
|
2
2
|
|
|
3
3
|
[简体中文](development.zh-CN.md)
|
|
4
4
|
|
|
5
|
-
This guide describes
|
|
5
|
+
This guide describes candidate `0.3.6` and eight exact targets, defaulting to recommended RC prerelease `0.2.2-rc.2`. The candidate is unpublished; final same-archive, Actions and distribution evidence are separate, and historical or specialized results do not certify a revised final candidate.
|
|
6
6
|
|
|
7
|
-
Development and the full test suite use Linux (`/proc` is required for the profile lock), Node.js 24
|
|
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-rc.2`. DSH `0.2.2-rc.2` 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.
|
|
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.6.tgz` after static checks; it does not publish. `pnpm smoke` first runs `pack:local` again to prepare a new candidate, then installs it into an isolated DSH home, briefly starts the pinned runtime, checks readiness, anonymous redirection/denial and online CLI status, then stops it. It does not consume a previously frozen digest; use `verify:packed --suite smoke` for that.
|
|
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-rc.
|
|
34
|
+
DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.2-rc.2/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-rc.
|
|
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-rc.2`).
|
|
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,15 +54,9 @@ Current support is in [README](../README.md#dsh-compatibility) and the [support
|
|
|
54
54
|
|
|
55
55
|
## Cross-version verification
|
|
56
56
|
|
|
57
|
-
The default
|
|
57
|
+
The default is DSH `0.2.2-rc.2`; `DSH_TEST_VERSION` accepts only `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`, `0.2.2-rc.1`, `0.2.2-rc.2`. The retired Alphas are not positive selections. Test runtimes live under `.cache/test-runtime/<version>` and development runtimes under `.dev/runtime-<version>`; `DSH_TEST_BIN` must report the exact selection. Ordinary/full both run complete eight-host CLI/browser/smoke coverage. Types and integration use locked `0.2.2-rc.2` development packages. All eight check the real Loader, model runtime context/`DSH_WEB_URL` and IPv4/IPv6 HTTP/HTTPS security boundaries; missing transport fails instead of skipping.
|
|
58
58
|
|
|
59
59
|
```sh
|
|
60
|
-
DSH_TEST_VERSION=0.2.1-alpha.3 pnpm test:cli
|
|
61
|
-
DSH_TEST_VERSION=0.2.1-alpha.3 pnpm test:browser
|
|
62
|
-
DSH_TEST_VERSION=0.2.1-alpha.4 pnpm test:cli
|
|
63
|
-
DSH_TEST_VERSION=0.2.1-alpha.4 pnpm test:browser
|
|
64
|
-
DSH_TEST_VERSION=0.2.1-alpha.5 pnpm test:cli
|
|
65
|
-
DSH_TEST_VERSION=0.2.1-alpha.5 pnpm test:browser
|
|
66
60
|
DSH_TEST_VERSION=0.2.1-rc.1 pnpm test:cli
|
|
67
61
|
DSH_TEST_VERSION=0.2.1-rc.1 pnpm test:browser
|
|
68
62
|
DSH_TEST_VERSION=0.2.1-rc.2 pnpm test:cli
|
|
@@ -77,48 +71,51 @@ DSH_TEST_VERSION=0.2.2-alpha.3 pnpm test:cli
|
|
|
77
71
|
DSH_TEST_VERSION=0.2.2-rc.1 pnpm test:cli
|
|
78
72
|
DSH_TEST_VERSION=0.2.2-alpha.3 pnpm test:browser
|
|
79
73
|
DSH_TEST_VERSION=0.2.2-rc.1 pnpm test:browser
|
|
74
|
+
DSH_TEST_VERSION=0.2.2-rc.2 pnpm test:cli
|
|
75
|
+
DSH_TEST_VERSION=0.2.2-rc.2 pnpm test:browser
|
|
80
76
|
```
|
|
81
77
|
|
|
82
78
|
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.
|
|
83
79
|
|
|
84
|
-
Official-account tests use a local Platform stand-in with the actual DSH `0.2.2-rc.
|
|
80
|
+
Official-account tests use a local Platform stand-in with the actual merged DSH `0.2.2-rc.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.
|
|
85
81
|
|
|
86
82
|
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.
|
|
87
83
|
|
|
88
|
-
The
|
|
84
|
+
The account adapter retains capability/live-configuration checks and full manual-sign-in coverage on all eight hosts; admitted unknown versions inherit no verification. On `0.2.2-rc.2`, private in-place component decoration preserves entry/children/inject/options and native disposal. Its own provideRoot contribution redraws installation/removal; inactive wrappers delegate, and restoration only overwrites its own component. Older entries without children retain public registration. Two independent private runtimes exercise client/native-source HMR, child ownership, notifications, later-writer protection, pending describe and in-flight cancellation. PKCE/notifications use only local Platform/notification stand-ins. Eight-language visit sets are asserted, but cross-product notification localization mapping is not fully verified. See `DSH-ACCOUNT-001` and `DSH-ACCOUNT-SLOT-001`.
|
|
89
85
|
|
|
90
86
|
`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.
|
|
91
87
|
|
|
92
|
-
`account-login.spec.ts`
|
|
88
|
+
`account-login.spec.ts` uses ordinary `sessionHours` changes for genuine configuration HMR on all eight hosts, checking listener replacement, queued independent Settings writes and rejected genuine nesting. Replacing isolated plugin code must allow manual sign-in again. The probe calls real HMR, replaces no service and is unpackaged; see `DSH-HMR-001`. On all eight, `startup-compatibility.spec.ts` damages only the plugin copy’s `engines.dsh` for Loader refusal without import, then separately injects the plugin admission range for post-import refusal. Both exit naturally nonzero without TCP/HTTP/readiness/WebSocket listeners. Profiles independently disable native webserver; upstream packages and Loader auditing are unchanged.
|
|
93
89
|
|
|
94
90
|
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.
|
|
95
91
|
|
|
96
|
-
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`, `0.2.2-rc.1` 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`, `0.2.2-rc.1`, `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.
|
|
92
|
+
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`, `0.2.2-rc.1` 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`, `0.2.2-rc.1`, `0.2.2-rc.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.
|
|
97
93
|
|
|
98
|
-
|
|
94
|
+
On `0.2.2-rc.2`, Search/Fetch independently cover auto/account/api-key billing, refused saves, refresh/restart persistence, test credential save/replace/remove and no secret echo; anonymous/revoked calls return 401. Endpoints are local, with zero model, Search/Fetch or outside requests.
|
|
99
95
|
|
|
100
|
-
|
|
96
|
+
Startup diagnostics read installed declarations and explicit lifecycle records, warning once per process/version/state across configuration/module HMR. The three Alphas retire from maintenance in candidate `0.3.6` after their original 2026-10-28/14-day/2026-11-11 window, with last support `0.3.5`; retiredOn=2026-11-13 is a preparation date. Alpha-only positive legacy-module-HMR branches are removed; generic warning/date unit contracts remain, and real warning/source-HMR checks move to this release’s maintenance-retirement suite. The six technical retirements retain release `0.3.1`/last `0.2.0` history. Dates never stop service; necessary API/identity/security failures still refuse it.
|
|
97
|
+
|
|
98
|
+
`browser/host-release.spec.ts` fixes seven real round trips: `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`, `0.2.2-rc.1` ↔ `0.2.2-alpha.3`, `0.2.2-rc.2` ↔ `0.2.2-rc.1`. Each retains the page in one temporary profile/port, checks the actual full release prompt, reloads to verify authentication/the original session/settings, then restores the starting host. Minimum `0.2.1-rc.1` registers no round trip. No upstream source, version or dependency graph is changed.
|
|
101
99
|
|
|
102
100
|
## Consume a fixed archive
|
|
103
101
|
|
|
104
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:
|
|
105
103
|
|
|
106
104
|
```sh
|
|
107
|
-
sha256sum artifacts/dsh-auth-remote-0.3.
|
|
108
|
-
pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.
|
|
105
|
+
sha256sum artifacts/dsh-auth-remote-0.3.6.tgz
|
|
106
|
+
pnpm verify:packed --archive artifacts/dsh-auth-remote-0.3.6.tgz --sha256 <recorded-sha256> --dsh-version 0.2.2-rc.2 --suite cli --suite browser --suite smoke
|
|
109
107
|
```
|
|
110
108
|
|
|
111
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.
|
|
112
110
|
|
|
113
|
-
| Suite | Selection
|
|
114
|
-
| -------------- |
|
|
115
|
-
| `cli` | All CLI test files
|
|
116
|
-
| `browser` | All browser test files
|
|
117
|
-
| `smoke` | Install and briefly boot the archive in a new marked home
|
|
118
|
-
| `theme` | The exact login/security theme and narrow-screen case (one real test)
|
|
119
|
-
| `account` | startup-compatibility, account-login and live-config on `0.2.1-
|
|
120
|
-
| `host-release` | One real round trip on `0.2.1-
|
|
121
|
-
| `rc-bootstrap` | host-release and dsh-bootstrap on `0.2.1-rc.1` (two real tests) |
|
|
111
|
+
| Suite | Selection |
|
|
112
|
+
| -------------- | -------------------------------------------------------------------------------------------------------------------------- |
|
|
113
|
+
| `cli` | All CLI test files |
|
|
114
|
+
| `browser` | All browser test files |
|
|
115
|
+
| `smoke` | Install and briefly boot the archive in a new marked home |
|
|
116
|
+
| `theme` | The exact login/security theme and narrow-screen case (one real test) |
|
|
117
|
+
| `account` | startup-compatibility, account-login and live-config on `0.2.1-rc.1` |
|
|
118
|
+
| `host-release` | One real round trip 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`, `0.2.2-rc.1`, `0.2.2-rc.2` |
|
|
122
119
|
|
|
123
120
|
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.
|
|
124
121
|
|
|
@@ -127,44 +124,51 @@ Consumption is serial within a checkout, enforced by a consumer lock. Each suite
|
|
|
127
124
|
`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.
|
|
128
125
|
|
|
129
126
|
```sh
|
|
130
|
-
node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.
|
|
127
|
+
node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.6.tgz --sha256 <recorded-sha256> --retired-dsh-version 0.2.1-alpha.2
|
|
131
128
|
```
|
|
132
129
|
|
|
133
130
|
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/`.
|
|
134
131
|
|
|
132
|
+
## This release’s maintenance-retirement checks
|
|
133
|
+
|
|
134
|
+
Only plugin `0.3.6` full/releases run the three exact targets against the same archive. They do not extend DSH_TEST_VERSION, start Chromium or restore full support:
|
|
135
|
+
|
|
136
|
+
```sh
|
|
137
|
+
node scripts/verify-maintenance-retired.mjs --archive artifacts/dsh-auth-remote-0.3.6.tgz --sha256 <recorded-sha256> --dsh-version 0.2.1-alpha.3
|
|
138
|
+
node scripts/verify-maintenance-retired.mjs --archive artifacts/dsh-auth-remote-0.3.6.tgz --sha256 <recorded-sha256> --dsh-version 0.2.1-alpha.4
|
|
139
|
+
node scripts/verify-maintenance-retired.mjs --archive artifacts/dsh-auth-remote-0.3.6.tgz --sha256 <recorded-sha256> --dsh-version 0.2.1-alpha.5
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
Each host has three scenarios: actual install/init, exact warning before ready, anonymous denial/login, continuous session and one warning through genuine config/source HMR, then revocation; Loader refusal without listeners (`0.2.1-alpha.3` uses a Host peer fault, the other two engines); and post-import plugin admission refusal with no TCP/HTTP/readiness/WebSocket listener. Only temporary plugin copies change. Profiles independently disable native webserver; upstream identity/dependency graphs and candidate bytes remain unchanged. Old native watchers exclude node_modules, so after checking actual installed bytes, the candidate’s own files are copied into a profile watch root with public HMR root/file-URL configuration for real source replacement. Reports live in `.cache/verify-maintenance-retired/`; TAP must contain exactly three real named cases and all processes must stop. Other plugin versions explicitly refuse this suite.
|
|
143
|
+
|
|
144
|
+
## Producer and unpackaged acceptance index
|
|
145
|
+
|
|
146
|
+
After core checks, run `node scripts/pack.mjs` once, then `node scripts/packed-artifact.mjs record` to write adjacent `SHA256SUMS` and unique `producer.json`, binding HEAD/full diff/untracked bytes and modes, archive and Node/pnpm identity. Even identical tgz bytes receive distinct producer identity. Consumer report schemas remain; `report-*-evidence.json` links the raw report/logs and every `report-*-runtimes/` receipt. Actual preparation within the acceptance context records CLI/lock/DSH→WebApp→eight SDK packages and complete-tree nlink=1 checks, including smoke, previous-host and private-account runtimes.
|
|
147
|
+
|
|
148
|
+
Using each printed report path, copy this producer’s original JSON, adjacent sidecar, receipt directory and every sidecar-listed raw log into a new ignored unpackaged directory, retaining basenames. Smoke has three actual log suffixes: dev-prepare.mjs, dev-install.mjs, smoke.mjs; do not copy an absent synthetic smoke log. Do not mix historical producers or partial results. After consumption, use `packed-artifact.mjs index ARCHIVE SHA256 REPORT_ROOT OUTPUT`; see the [release guide](releasing.md) for the command. The index checks all eight CLI/complete-browser/smoke targets, full technical refusal and the three maintenance targets only for `0.3.6` full, plus raw hashes and required runtime roles. Missing/mismatched/mixed/partial evidence fails and replaces a stale passed index with failed status. Empty-file placeholders never count as real cases.
|
|
149
|
+
|
|
135
150
|
## Ordinary and full CI plans
|
|
136
151
|
|
|
137
152
|
`scripts/ci-plan.mjs` selects ordinary verification only when every changed path is one of `CHANGELOG.md`, `CHANGELOG.zh-CN.md`, `CONTRIBUTING.md`, `CONTRIBUTING.zh-CN.md`, `LICENSE` or `tests/unit/i18n.test.ts`. Any other path selects full verification, including source, shared tests/helpers, package/lock/build scripts, workflows, README, support policies and compatibility inventories. Renames/copies, unknown statuses, empty or incomplete differences and an unexpected/dirty checkout also select full. PR comparison uses the actual event base/head and verifies merge parents; push comparison uses before/after. Missing commit evidence falls back to full.
|
|
138
153
|
|
|
139
|
-
Manual dispatch, unknown events,
|
|
140
|
-
|
|
141
|
-
| Exact DSH release | Ordinary browser selection |
|
|
142
|
-
| ----------------- | -------------------------- |
|
|
143
|
-
| `0.2.1-alpha.3` | `browser` |
|
|
144
|
-
| `0.2.1-alpha.4` | `host-release` |
|
|
145
|
-
| `0.2.1-alpha.5` | `host-release` |
|
|
146
|
-
| `0.2.1-rc.1` | `rc-bootstrap` |
|
|
147
|
-
| `0.2.1-rc.2` | `browser` |
|
|
148
|
-
| `0.2.1-rc.3` | `browser` |
|
|
149
|
-
| `0.2.1-rc.4` | `browser` |
|
|
150
|
-
| `0.2.1-rc.5` | `browser` |
|
|
151
|
-
| `0.2.2-alpha.3` | `browser` |
|
|
152
|
-
| `0.2.2-rc.1` | `browser` |
|
|
154
|
+
Manual dispatch, unknown events, releases and the Monday 00:00 UTC schedule use full. Ordinary/full both run complete eight-host CLI/browser/smoke; the low-risk whitelist only selects extra retirement work, not a smaller browser matrix. Full requires independent `0.2.1-alpha.2` technical refusal. Only a validated plugin `0.3.6` full archive requires the three-target maintenance-retirement matrix. Ordinary expects both retirement jobs to skip; other plugin versions’ full plans expect only maintenance-retirement to skip, retaining technical refusal. Aggregation requires all five results—validate, cli-smoke, browser, retired-rejection, maintenance-retirement—and explicit true/false required output. Missing/unknown values, failures, cancellations and other skips fail. Releases use full and consume the same producer without repacking.
|
|
153
155
|
|
|
154
|
-
|
|
156
|
+
Keep fixed-port cases serial per checkout. Local parallelism requires independent source/dist/artifacts/runtime/profile trees, writable node_modules copies and network namespaces; pnpm copy installation and nlink=1 checks prevent shared HMR inode changes.
|
|
155
157
|
|
|
156
|
-
On exact DSH `0.2.2-alpha.3` and `0.2.2-rc.
|
|
158
|
+
On exact DSH `0.2.2-alpha.3`, `0.2.2-rc.1` and `0.2.2-rc.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.
|
|
157
159
|
|
|
158
160
|
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.
|
|
159
161
|
|
|
160
162
|
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.
|
|
161
163
|
|
|
162
|
-
`liveshare.spec.ts`
|
|
164
|
+
`liveshare.spec.ts` retains only real native viewer/index, carrier and administrator isolation on exact `0.2.2-alpha.3`, `0.2.2-rc.1`, `0.2.2-rc.2`. Owner/Relay product flows and exclusive stand-ins are removed. `business-origin-observer.mjs` registers the two exact Owner POST paths through real Connection.fetch, observing native Requests and one restoration pair across HTTP/HTTPS/proxy, real configuration HMR and anonymous/revoked/bad-Origin rejection. It loads no Host/Relay and does not fabricate waterfall results. Production adaptation remains; product flows are unverified, and historical reports certify only their original archive.
|
|
165
|
+
|
|
166
|
+
Candidate `0.3.6` still requires final acceptance and public distribution. Published `0.3.5` retains ten original declarations; `0.2.2-rc.2` support is not retroactive. Acceptance uses one final archive and Linux/Node.js 24 (at least `24.9.0` for the default host)/Chromium; other Node majors do not substitute. Real proxy products, external authorization, non-loopback IPv6 interfaces and other platforms/browsers remain unverified.
|
|
163
167
|
|
|
164
|
-
|
|
168
|
+
Direct development dependencies use DSH `0.2.2-rc.2`, Cordis `4.1.0` and Schemastery `3.19.0`; the actual new host chain uses Loader `1.1.0` and Include `1.1.0`. 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.
|
|
165
169
|
|
|
166
|
-
|
|
170
|
+
`settings-icon.spec.ts` registers on all eight hosts: `0.2.2-alpha.3`, `0.2.2-rc.1` and `0.2.2-rc.2` check the native shield, size/currentColor/selection, light/dark narrow layouts, contribution release/default restoration, genuine declaration withdrawal/recreation without duplicates and disposal; the other five 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.
|
|
167
171
|
|
|
168
|
-
`
|
|
172
|
+
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`, `0.2.2-rc.1` and `0.2.2-rc.2`. 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.
|
|
169
173
|
|
|
170
|
-
|
|
174
|
+
Source, prototypes, stage checks, complete candidates, PR/master/tag producers and post-publication byte checks are separate evidence. See bidirectional inventory entries `DSH-ACCOUNT-SLOT-001`, `DSH-RESOURCE-001` and `DSH-LIVESHARE-001` for private dependencies, exact applicability and retirement conditions.
|