dsh-deeppilot 0.9.4 → 0.9.6

package/docs/DSH_RELEASE_MEMORY.md

@@ -3,7 +3,143 @@
 > This is the durable audit record for DeepPilot's public DSH plugin. Re-audit
 > the next DSH release instead of assuming that an rc upgrade is runtime-safe.
 
-## Current decision
+## Current decision — `dsh-v0.2.1-alpha.4`
+
+- **Audited release:** `dsh-v0.2.1-alpha.4` (official release page:
+  <https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.2.1-alpha.4>),
+  published to npm 2026-10-15T13:08:08Z on the `alpha` dist-tag. It is **not**
+  `latest`; `latest`/`next` still point at `0.2.0-rc.2`, exactly as at alpha.3.
+- **Comparison baseline:** `dsh-v0.2.1-alpha.3` (the previous audited tag).
+- **Plugin runtime verdict: no break, and no `src/` change was needed.** Eight of
+  the ten peer packages ship a byte-identical `lib/` tree; only their
+  `package.json` `version` fields moved. That set includes `dsh-api-gateway`,
+  where alpha.3's first two breaks lived, and all three Client faces the resident
+  interaction client loads (`dsh-typert-registry/client`,
+  `dsh-client-connection/client`, `dsh-api-gateway/client`). Every alpha.3 fix
+  therefore still holds unchanged.
+- **Only `dsh-api-remotes` changed in code, additively.** One new Remote Events
+  entry (`plugin-market/changed`) and the rename of `IncompatiblePlugin.peers` to
+  `requirements`. The plugin reads neither: it subscribes to no Remote Events
+  entry of that name, and its own phone-wire frame registry is a separate
+  vocabulary from DSH Remote Events. Its `lib/client.js` shows a 750-line diff
+  that normalises to zero contract changes — the bulk is `TYPERT_REMOTE$N`
+  renumbering plus `sourceLocation` line drift from the one inserted remote.
+- **Two packages exist for the first time** — `@deepseek-ai/dsh-plugin-market`
+  and `@deepseek-ai/dsh-experimental-plugin-market-bundle` — behind this
+  release's custom plugin index sources. Neither is a dependency of this plugin,
+  the plugin does not name either in `inject`, and the bundle is a purely
+  additive entry in `dsh-app-boot`'s default bundle list.
+- **Activation verdict: one break, and it is the release's own stated
+  migration.** alpha.4 changed the compatibility rule so that a plugin's own
+  `engines.dsh` range **decides alone and `peerDependencies` are ignored**
+  whenever that field is present; only a manifest without `engines.dsh` falls
+  back to the old peer evaluation. This plugin declared no `engines.dsh`, so it
+  kept the peer path, and its exact two-version peer list rejected
+  `0.2.1-alpha.4` — the plugin would not have activated on that host.
+- **Evidence: reproduced against the published bundles, not inferred.** The audit
+  ran each host's own published `evaluatePluginCompatibility` (alpha.3 and
+  alpha.4 installed into separate isolated directories) against this plugin's
+  real `package.json`, over one candidate list. Before any edit, both hosts
+  admitted `0.2.0-rc.2` and `0.2.1-alpha.3` and both refused `0.2.1-alpha.4`,
+  reporting all ten peers unmet. With the new `engines.dsh` range in place, both
+  hosts admit all three audited releases; alpha.4 reports a **single**
+  `engines.dsh` requirement instead of ten peers when it refuses; and
+  `0.2.1-alpha.2`, `0.2.1-alpha.5`, `0.2.1`, and `0.3.0` are still refused.
+  alpha.3 ignores `engines.dsh` entirely — the field did not exist yet — and
+  keeps deciding on `peerDependencies`, which is why both declarations must name
+  the same list.
+- **Install verdict: the two declarations now agree.** `engines.dsh` and all ten
+  `@deepseek-ai/dsh*` peers name `0.2.0-rc.2 || 0.2.1-alpha.3 || 0.2.1-alpha.4`,
+  mirrored in `tests/compatibility-metadata.test.ts`, `package-lock.json`, both
+  READMEs, `COMPATIBILITY.md`, `AGENTS.md`, and the local `docs/决策记录.md`
+  (章节一, 条目3). The dev pins and `DSH_BASELINE` stay at the exact
+  `0.2.0-rc.2` this branch builds and typechecks against.
+- **Vendor peers need no widening.** Both hosts still vendor `cordis
+  4.0.5-alpha.2` and `schemastery 3.18.5-alpha.2`; neither package published a
+  `dsh-0-2-1-alpha-4` dist-tag, and the existing `~4.0.5-alpha.1` /
+  `~3.18.5-alpha.1` ranges already admit them.
+- **Protocol verdict: no phone-protocol change.** Protocol v2, pairing state, and
+  device records are untouched by this release; no phone needs to re-pair.
+- **Unrelated to this plugin, recorded for completeness:** the release also
+  brought per-model reasoning levels for custom API models, discovery and
+  installation from custom plugin index sources, a command/argument input fix, an
+  Office file delivery change, a Developer Tools reload fix, lower Linux command
+  startup overhead, and failed-command status reporting. None of them touches a
+  surface this plugin calls.
+
+### Previous decision — `dsh-v0.2.1-alpha.3`
+
+- **Audited release:** `dsh-v0.2.1-alpha.3` (official release page:
+  <https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.2.1-alpha.3>),
+  published to npm 2026-10-14T13:32:15Z on the `alpha` dist-tag. It is **not**
+  `latest`; `latest`/`next` still point at `0.2.0-rc.2`. Baseline commit
+  `2fbf4359b82fb94c03dcce0b831660d87f12ea5c`, compared against alpha.2's
+  `d743267388641bc76f17c45ce8b4c231aed1d32c` (**852 commits, 3311 changed files,
+  120,978 insertions, 16,632 deletions**).
+- **Comparison baseline:** `dsh-v0.2.1-alpha.2` (the previous audited tag).
+- **Plugin runtime verdict: four confirmed breaks with one root cause — the
+  alpha.3 Peer model — and the resident interaction client does not start.**
+  **Fixed in this audit; see "The fix" below.**
+  This release makes every in-process carrier name a `PeerScope`
+  (`principal` / `signal` / `interactions`) explicitly; nothing defaults to the
+  operator any more. The four landing points, each with its own evidence:
+
+  | # | Upstream change | Plugin seam | Evidence |
+  | --- | --- | --- | --- |
+  | 1 | `TypertGatewayWireStream.open`'s 4th parameter `peer` is required; `assertPeerLive()` reads `peer.signal.aborted` before anything else | `src/dsh-remote-interactions.ts:180` passes `undefined, undefined` | Reproduced against the published bundles: alpha.2 returns normally, alpha.3 throws `TypeError: Cannot read properties of undefined (reading 'signal')` |
+  | 2 | `$events` additionally requires `peer.interactions === 'answer'` (`requireInteractions`) | same call | Reproduced: a peer with `interactions: 'none'` gets `gateway/interactions-forbidden`; a full owner/answer peer passes on **both** versions |
+  | 3 | `ConnectionFetchHandler.fetch(request, peer)` now takes a required Peer | `src/dsh-remote-interactions.ts:204` calls `fetchHandler.fetch(request)` | `lib/types/rpc.d.ts` declares `peer: PeerScope` required, "never defaulted" |
+  | 4 | `./client` gained `node`/`browser` conditions; Node now resolves `lib/client.node.js`, which carries **no** `window.__ModuleLoader__.load` banner | `loadClientFaces()` (`src/dsh-remote-interactions.ts:117`) builds its module table from that banner | `grep -c __ModuleLoader__` is 0 in `client.node.js`, 1 in `client.browser.js` and 1 in alpha.2's `client.js` |
+
+  A fifth, latent one: `installConnection` derives
+  `interactions ?? (location === undefined ? 'none' : 'answer')`, and the
+  plugin's Node context has no `location`, so `apply(ctx)` alone always selects
+  `'none'`. Passing an explicit Peer is not enough by itself — the install call
+  must name `interactions: 'answer'` too.
+- **Failure mode is degradation, not a crash — but only partly contained.**
+  `src/dsh-api-proxy.ts:316` wraps `startDshRemoteInteractions` in `try/catch`
+  and logs `[deeppilot] DSH Remote interaction client unavailable`. Breaks 3 and
+  4 surface while the resident client is being assembled, so they land in that
+  catch. Whether break 1/2 (the Gateway opens its Remote Events generation
+  asynchronously) also lands there is **not confirmed** — an uncaught rejection
+  there would be fatal under Node's default `--unhandled-rejections=throw`.
+  The phone loses approval/question delivery either way.
+- **Fix direction (verified compatible with both hosted versions):** build one
+  owner/answer Peer (`new Peer(ownerCtx, { principal: { kind: 'owner' },
+  interactions: 'answer' })`, falling back to `connection.operator` on alpha.2)
+  and name it in every carrier call — alpha.2 ignores a second `fetch` argument
+  and defaults an absent `open` peer to the operator, so one call form serves
+  both. `loadClientFaces` additionally has to accept the Node bundle's named
+  exports when the banner did not fire; both shapes export `apply`/`inject`
+  (`installConnection`/`transportError` are extra on Node).
+- **Install verdict: the peer range now names this release explicitly.** It moved
+  from the open-ended `>=0.2.0-rc.2 <0.3.0-0` to `0.2.0-rc.2 || 0.2.1-alpha.3`
+  across all ten `@deepseek-ai/dsh*` peers, and the two vendor peers widened to
+  `~4.0.4 || ~4.0.5-alpha.1` and `~3.18.4 || ~3.18.5-alpha.1`. Because DSH
+  evaluates that range on every start, the next DSH release deactivates this
+  plugin until the list is widened deliberately — see `docs/决策记录.md`
+  (章节一, 条目2), which records this as a reversal of the 2026-09-29 policy.
+  The published CLI composed the plugin's patch cleanly before the change (see
+  the 2026-10-14 entry). The plugin's own `lib/client.js` shape was not
+  re-verified against the alpha.3 client-modules scanner.
+- **Protocol verdict: no phone-protocol change.** Protocol v2, pairing state,
+  and device records are untouched by this release; no phone needs to re-pair.
+- **Two host-side migrations this machine must apply** (independent of the
+  plugin): `~/.dsh/profiles/web/cordis.patch.yml` carries
+  `llm-deepseek-account.config.models: []`, and alpha.3 throws on any residual
+  `models` key — **including an empty array** (`resolveAccountOptions`). Also
+  `dsh --profile <name> --from-default-profile <template>` now *replaces* an
+  existing profile directory (it deletes the old `node_modules` and
+  `cordis.patch.yml`); the audit procedure recorded below used that flag.
+- **Capability gaps, not regressions:** the `contextBreakdown` projection was
+  reshaped (`nodes[]` → `systems[]` + `surfaceTokens` + `claim`, stateVersion
+  5→6) and the plugin forwards it by key, so the phone may render empty values;
+  the model catalog shrank (account routes return only the version-gated
+  `offered` subset, pi-ai routes without a resolvable key return `[]`); and
+  `CLIENT_UPGRADE_REQUIRED` / `MODEL_UNSUPPORTED` are new codes with no mapping
+  in `src/wire-errors.ts` yet.
+
+### Previous decision — `dsh-v0.2.1-alpha.2`
 
 - **Audited release:** `dsh-v0.2.1-alpha.2` (official release page:
   <https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.2.1-alpha.2>),
@@ -43,9 +179,40 @@
 
 ### Plugin release verdicts
 
-- **Release verdict (`0.9.4`, prepared 2026-10-10, NOT published):** carries the
-  `projections` adapter fix and the Automation tasks documentation correction
-  described in the 2026-10-09 entry below. `package.json`, both root
+- **发布结论（`0.9.5`，2026-10-15，`v0.9.5` @ `6517ad7`）：** 包含 alpha.3
+  对端（Peer）与客户端兼容修复、两个宿主精确列举策略、跨语言认证向量与恢复说明，
+  以及手动 OIDC 身份认证与来源证明发布。包与锁文件两处根版本、基线快照一致。
+  - **发布前验证：** 干净依赖安装；562 项单元测试通过、零失败、一项既有待办；
+    类型检查、构建、固定宿主的真实配置模型加载、Go 测试、六个辅助程序校验和与
+    包内容检查通过。挑战篡改测试基于当前连接生成变更值，消除了时间碰撞，连续
+    20 次重点回归通过。发布提交的持续集成（CI）和 CodeQL 代码安全扫描通过。
+  - **注册表与来源证明：** npm 于 `2026-10-14T23:29:29.605Z` 发布该版本，
+    `latest`（稳定分发标签）指向 `0.9.5`。下载压缩包共 50,934,088 字节，
+    SHA1 `6a2f356efa1e48849d9bf713f88cd0fd67c7999c` 与工作流上传记录一致；
+    SHA512 与注册表及来源证明中的包摘要一致。来源证明精确对应 `v0.9.5`、
+    `6517ad7b6d7022afc9b3d81d6779b434282c9c56` 和 `.github/workflows/publish.yml`。
+    `npm audit signatures`（npm 签名审计）通过，包含本插件的注册表签名和来源证明；
+    npm 可信发布者绑定显示 `Valid`（有效）。压缩包发布不依赖可选的 `gitHead`
+    字段来确认源码，使用已验证签名的来源证明提交。
+  - **已发布包安装：** 两个独立的新 DSH 主目录分别使用 `0.2.0-rc.2` 与
+    `0.2.1-alpha.3`，从注册表执行 `dsh plugin --profile verify add dsh-deeppilot@0.9.5`。
+    三条插件配置组合成功，版本为 `0.9.5`，安装路径未引用源码工作区，六个辅助程序
+    校验和全部一致；实际配置模型导入未出现本插件相关错误。两个 Web 模板仍各有
+    四项宿主配置模型错误，与未安装插件的基线完全一致；不把整个模板核对说成全绿。
+  - **真实宿主边界：** 隔离的 alpha.3 冒烟检查为 24 项通过、1 项失败、3 项跳过。
+    失败项是未配置模型账号的全新主目录中，模型目录非空的断言；模型目录 RPC 正常
+    且可路由。模型切换、真实提问和模型触发的审批问答未验证，iPhone 真机未验证。
+    已认证连接重复提交认证证明的既有待办保留。
+  - **发布后缓存核对修正：** [首次发布运行](https://github.com/Mars-Sea/dsh-deeppilot/actions/runs/38653869533)
+    上传成功，末尾核对短暂命中缓存的 404 而失败。独立注册表、摘要、签名及安装
+    核验通过后才公开 [GitHub 发布页](https://github.com/Mars-Sea/dsh-deeppilot/releases/tag/v0.9.5)。
+    后续仓库修正为刷新查询、要求元数据重新校验并最多读取重试 12 次；修正后的
+    只读核对步骤已对真实注册表执行通过。未重跑上传、未修改已发布包或移动版本标签。
+    发布说明：`docs/RELEASE_NOTES-0.9.5.md`。
+
+- **Release verdict (`0.9.4`, published 2026-10-10, tag `v0.9.4` @ `e2f77af`):**
+  carries the `projections` adapter fix and the Automation tasks documentation
+  correction described in the 2026-10-09 entry below. `package.json`, both root
   `package-lock.json` version entries, and `tests/apply-baseline.snapshot.json`
   are on `0.9.4`, and `lib/` is regenerated. The full checklist passed locally:
   `npm ci`, 538 unit tests, typecheck, build, the config-schema check against a
@@ -53,9 +220,24 @@
   `npm pack --dry-run` (65 files, 50,916,470 bytes packed). The fix was also
   verified on a live `0.2.1-alpha.2` host against the published `0.9.3` as an
   A/B control (25 pass / 0 fail either way, with the `sessions.projections
-  failed: internal` diagnostic present only on `0.9.3`). Nothing was
-  published, tagged, or pushed; npm `latest` still points at `0.9.3`, so users on
-  `0.2.1-alpha.2` keep hitting the projections defect until this ships.
+  failed: internal` diagnostic present only on `0.9.3`).
+  - **Registry verification after publishing.** `dist-tags.latest` moved off
+    `0.9.3`; `dist.shasum` `85b3c71a802e45e42f5fb1b23444ed2e396d39dc` is
+    byte-identical to the local `npm pack` output at the tag; 65 files,
+    `dist.unpackedSize` 130,789,604. **`gitHead` is `e2f77af`, the tag commit** —
+    the 0.9.3 ordering deviation did not repeat, because the release notes and
+    every other documentation change were committed before the pack. The publish
+    itself needed the maintainer's one-time password, as in 0.9.3; everything up
+    to and after it was done here.
+  - **Clean-profile verification.** A fresh isolated home, built from the shipped
+    Web template and installed with the published `0.2.1-alpha.2` CLI
+    (`dsh plugin --profile verify add dsh-deeppilot@0.9.4`), composed a real
+    profile: `--dump-config` printed the plugin's three rows
+    (`deeppilot-directory-picker-browse`, `…-browse-client`, `deeppilot`) with no
+    missing-module or load error, the installed package's six helper checksums
+    verified, every helper binary embedded `go1.26.9`, and the installed
+    `lib/index.js` carried the projections fix. Only then was the GitHub Release
+    taken out of draft and marked Latest.
   - **The release also had to fix the helper's toolchain and its refresh
     workflow.** CI's `govulncheck` job reported 11 reachable Go standard-library
     vulnerabilities for the pinned `go 1.26.6`; this is time-triggered, not
@@ -207,6 +389,355 @@
   bundle" below. The plugin needs no code change; the phone's copy now points
   at the bundle.
 
+## 2026-10-15 — audit of `dsh-v0.2.1-alpha.4`
+
+`dsh-v0.2.1-alpha.4` reached npm on 2026-10-15T13:08:08Z, roughly 24 hours after
+alpha.3, with the GitHub release following at 13:40:02Z. It is a small release —
+two features, five fixes, and one compatibility-policy change — and
+`latest`/`next` still point at `0.2.0-rc.2`.
+
+### Method
+
+This audit established the change surface from **released artifacts before
+reading any source**, rather than from the release notes, because those notes are
+under 2 KB and all four of alpha.3's breaks had been invisible in its notes.
+Every `@deepseek-ai/dsh*` peer package was fetched from npm at both
+`0.2.1-alpha.3` and `0.2.1-alpha.4`, unpacked into a scratch tree, and compared
+file by file. The one large diff was then re-compared after normalising
+`TYPERT_REMOTE$N` renumbering and `sourceLocation` line/column drift, so that
+mechanical churn could not hide a contract change.
+
+### Change surface
+
+- **Eight of the ten peer packages carry a byte-identical `lib/` tree**:
+  `dsh-api-gateway`, `dsh-client-connection`, `dsh-client-locale`,
+  `dsh-client-ui-settings`, `dsh-client-ui-slots`, `dsh-settings`,
+  `dsh-typert-protocol`, `dsh-typert-registry`. Only their `package.json`
+  `version` fields moved. That set includes every module alpha.3 broke the
+  plugin through.
+- **`dsh-api-remotes`** gained one Remote Events entry (`plugin-market/changed`),
+  renamed `IncompatiblePlugin.peers` to `requirements`, and added a
+  `pluginMarket` remote. Its `lib/client.js` diff spans 750 lines but normalises
+  to zero contract changes — `TYPERT_REMOTE$N` renumbering, `sourceLocation`
+  drift, and one rewritten `productAnalytics/report` description.
+- **`dsh-app-boot`** rewrote the compatibility evaluator (below) and appended
+  `@deepseek-ai/dsh-experimental-plugin-market-bundle` to its default bundle
+  list, which is additive to `DEFAULT_BUNDLES`.
+- **`dsh-plugin-manager`** carried the same `peers` → `requirements` rename
+  through `IncompatiblePlugin` and its diagnostics.
+- **Two packages are new at this release**: `@deepseek-ai/dsh-plugin-market` and
+  `@deepseek-ai/dsh-experimental-plugin-market-bundle`. Neither resolves at
+  alpha.3. Neither is a dependency of this plugin, and neither appears in its
+  `inject`.
+- The `dsh` CLI's own ten `@deepseek-ai/dsh*` dependencies all moved to alpha.4;
+  the vendor pins did **not** move. Both hosts still vendor `cordis
+  4.0.5-alpha.2` and `schemastery 3.18.5-alpha.2`, and neither vendor published a
+  `dsh-0-2-1-alpha-4` dist-tag, so the existing `~4.0.5-alpha.1` /
+  `~3.18.5-alpha.1` ranges already admit what both hosts ship.
+
+### The one break: `engines.dsh` now decides alone
+
+`dsh-app-boot`'s evaluator grew a requirements path that short-circuits the old
+peer loop:
+
+```js
+function unmetRequirements(fields, runtimeVersion) {
+  const engines = Object.hasOwn(fields, "engines") ? objectOf$1(fields.engines, "Plugin manifest engines") : {};
+  if (Object.hasOwn(engines, "dsh")) {
+    const range = engines.dsh;
+    if (typeof range !== "string") throw new Error("Plugin manifest engines.dsh must be a string");
+    return satisfies(runtimeVersion, range) ? {} : { "engines.dsh": range };
+  }
+  if (!Object.hasOwn(fields, "peerDependencies")) return {};
+  // ...otherwise the previous per-peer loop, unchanged
+}
+```
+
+Three consequences matter here. A plugin that declares `engines.dsh` is judged
+**only** by it, and its `peerDependencies` are never read. A plugin that does not
+declare it keeps the previous behaviour — which is the state this plugin was in,
+so its exact two-version peer list refused `0.2.1-alpha.4`. And `engines.dsh` is
+taken verbatim, with none of the `workspace:^` / `workspace:~` / `workspace:*`
+substitution the peer path performs, so any `workspace:` range there is unmet.
+
+### Validation evidence
+
+- **Compatibility decision, reproduced against the published evaluators — before
+  any edit.** Each host's own `evaluatePluginCompatibility` (alpha.3 and alpha.4,
+  installed into separate isolated directories) judged this plugin's real
+  `package.json` over one candidate list. Unchanged, both hosts admitted
+  `0.2.0-rc.2` and `0.2.1-alpha.3` and refused `0.2.1-alpha.4`, listing all ten
+  peers as unmet. With the added `engines.dsh` range, both hosts admit all three
+  audited releases; alpha.4 reports a **single** `engines.dsh` requirement
+  instead of ten peers when it refuses; and `0.2.1-alpha.2`, `0.2.1-alpha.5`,
+  `0.2.1`, and `0.3.0` remain refused. alpha.3 ignores `engines.dsh` entirely
+  and keeps deciding on `peerDependencies`, which is why both declarations must
+  name the same list.
+- **Live A/B install on the published alpha.4 CLI — the evidence that matters.**
+  Under an isolated `DSH_HOME`, the **unchanged** package was rejected outright:
+  `dsh: installation rejected: Plugin dsh-deeppilot@0.9.5 is incompatible with
+  dsh 0.2.1-alpha.4: requirements {…ten peers…}`, `Exact-version exemption: not
+  active`, `dsh: nothing was installed`, exit 1. The **fixed** package installed
+  cleanly, exit 0, linked into the profile manifest's `dsh.profile.bundles`
+  alongside `@deepseek-ai/dsh-sdk-minimal`.
+- **Composed tree:** the same CLI's `--dump-config` produced **162 rows with the
+  plugin and 153 without it**, the plugin's three rows present at
+  `deeppilot-directory-picker-browse`, `deeppilot-directory-picker-browse-client`,
+  and `deeppilot`, with no `skipped`/`incompatible` diagnostic. The single
+  warning is the `sdk-minimal` template's own missing `directory-picker` entry,
+  which alpha.3 recorded as well.
+- **Live boot on a real alpha.4 Web host.** An isolated `DSH_HOME` profile built
+  from the shipped Web template and linked to this working tree booted under the
+  published alpha.4 CLI on `--port 3180` (the default 3080 is held by this
+  machine's own Host). The plugin started fully —
+  `[deeppilot] data plane active (mux + host streams)`,
+  `[deeppilot] LAN TLS identity created`,
+  `[deeppilot] local transport listening on https://0.0.0.0:3098` — and the
+  alpha.3 failure line `DSH Remote interaction client unavailable` **did not
+  appear**. A scan of the whole boot log for `incompatible`, `rejected`,
+  `requirements`, `unavailable`, or `error` returns nothing.
+- **Plugin unit tests:** `npm test` → **564 tests, 563 pass, 0 fail, 1 todo**,
+  including the new `engines.dsh names the same closed host list as the peer
+  range` and the updated peer-range boundary test. `npm run typecheck` passes.
+- **Build and schema:** `npm run build` passes and leaves `lib/` **byte-identical
+  to HEAD** — this fix changes no code, only declarations and documentation, so
+  no host's runtime behaviour can regress. `npm run check:config-schema` passes
+  against the pinned `0.2.0-rc.2` CLI (`/34 → $defs/config19`, volatile fields
+  pinned).
+- **Environment note, not a defect:** `check:config-schema` shells out to
+  `npx --yes @deepseek-ai/dsh@0.2.0-rc.2`, and this machine's `~/.npm/_cacache`
+  contains root-owned files, so the default npm cache fails with `EPERM`. Running
+  it with `npm_config_cache` pointed at a writable directory passes, and the
+  unchanged HEAD build fails identically under the default cache, which is what
+  attributes the failure to the machine rather than to this change.
+
+### Evidence limits
+
+Verified: install admission on alpha.4, profile composition, plugin startup, and
+the full unit/typecheck/build/schema suite. **Not** verified here: a real iPhone
+against this alpha.4 host, the Funnel transport, and a real model turn. The
+phone-side contract is unchanged by this release — protocol v2, pairing state,
+and device records are untouched, so no paired phone needs to re-pair — but that
+is a source-level verdict, not a device run.
+
+## 2026-10-14 — audit of `dsh-v0.2.1-alpha.3`
+
+### Scope and method
+
+Compared `dsh-v0.2.1-alpha.2...dsh-v0.2.1-alpha.3` (**852 commits, 3311 changed
+files, 120,978 insertions, 16,632 deletions**) by fetching the new tag into the
+existing blobless clone (`.audit-dsh-alpha2`, whose HEAD was already the alpha.2
+audit's target SHA `d7432673`), then `git diff --name-status` and per-path
+content diffs into `.audit-alpha3/diffs/`. Four parallel read-only passes
+covered `packages/api` + `apps/cli` + `packages/typert` + `packages/settings` +
+`vendor`, `packages/client/{connection,locale,ui-settings,ui-slots}` +
+`packages/boot` + `packages/bundle`, `packages/{credentials,subagent,session,
+schedule}`, and `packages/{core,host,skill,llm}`. All **14** upgrade guides
+added by this release (under `docs/upgrade-guide/v0.2.0-rc.2/`,
+`v0.2.1-alpha.1/`, `v0.2.1-alpha.2/`) were read in Chinese in full.
+
+The alpha.2 audit's lesson — judge the seams reached through `ctx.get`, not just
+the peer list — is what caught this one: the peer list is *not* where the breaks
+are. `@deepseek-ai/dsh-api-remote-access` is new, `packages/schedule/schedule`
+has **zero** changed source files, and the peer packages' own exported surfaces
+moved far less than the carrier contracts around them.
+
+### The four confirmed breaks
+
+Every one is the same root cause: alpha.3 makes the Peer explicit. `PeerScope`
+(`@deepseek-ai/dsh-typert-protocol`) gained required `principal`, `signal`, and
+`interactions`; `client/connection` added a `Peer` class and deleted
+`OperatorPeer`; the Gateway deleted `operatorPeer()` and its
+`request.peer ?? this.operatorPeer()` fallback.
+
+Reproduction used the **published** bundles, the same technique as the alpha.2
+`projections` break, with the plugin's exact argument list
+(`open('$events', payload, undefined, peer, signal)`):
+
+```sh
+# .audit-alpha3/repro-peer-contract.mjs, against
+#   alpha.2: ~/.npm/_npx/b5c6312874079fe8/node_modules/@deepseek-ai/dsh-api-gateway/lib/index.js
+#   alpha.3: .audit-alpha3/cli-install/node_modules/@deepseek-ai/dsh-api-gateway/lib/index.js
+# A. peer = undefined                       (what the plugin sends today)
+alpha.2: 未抛错
+alpha.3: 抛错 TypeError: Cannot read properties of undefined (reading 'signal')
+# B. peer = { principal: owner, signal, interactions: 'none' }
+alpha.2: 未抛错
+alpha.3: 抛错 TypertGatewayError: $events: forwarded Remote events require interactions=answer
+# C. peer = { principal: owner, signal, interactions: 'answer' }
+alpha.2: 未抛错
+alpha.3: 未抛错
+```
+
+Break 4 was settled by reading the shipped artifacts rather than by inference:
+`@deepseek-ai/dsh-client-connection`'s `./client` now maps `node` →
+`lib/client.node.js`, and that file contains **zero** `__ModuleLoader__`
+occurrences while `client.browser.js` and alpha.2's `client.js` each contain
+one. `loadClientFaces` builds its module table *only* from that banner, so on
+Node the table stays empty. Both shapes export `apply` and `inject`, which is
+what makes a banner-optional fallback possible.
+
+### The fix
+
+One call form serves both audited hosts, because alpha.2 ignores a second
+`fetch` argument and defaults an absent `open` peer to the operator Peer it
+holds:
+
+- `src/dsh-remote-interactions.ts` mints one Peer through
+  `connection.createPeer({ principal: { kind: 'owner' }, interactions: 'answer' })`
+  and falls back to `connection.operator` on a Host without that entry point.
+  The same Peer is named on `fetch` and on `wireStream.open`.
+- The Connection install prefers the explicit
+  `installConnection(ctx, { transport, interactions: 'answer' })`, because
+  `apply(ctx)` cannot name the participation and therefore always selects
+  `'none'` for this caller; `apply` remains the fallback for a host that predates
+  the installer.
+- `loadClientFaces` accepts a Node bundle's named exports when the browser
+  banner did not register them. A banner registration still wins, because the
+  bundle's own internal `require()` resolves against it.
+
+Six regression tests in `tests/dsh-wire-stream-contract.test.ts` pin the
+contract: the operator fallback, the alpha.3 `createPeer` request shape and the
+Peer reaching `wireStream.open`, both installer branches, and both module-table
+branches. The file fails against the previous call form — verified by restoring
+the source and re-running (1 failure) — and passes after the fix.
+
+### Peer range narrowed to the two audited hosts
+
+By explicit user direction the DSH peer range stopped being open-ended:
+`>=0.2.0-rc.2 <0.3.0-0` became `0.2.0-rc.2 || 0.2.1-alpha.3` across all ten
+`@deepseek-ai/dsh*` peers, with `@deepseek-ai/cordis` widened to
+`~4.0.4 || ~4.0.5-alpha.1` and `@deepseek-ai/schemastery` to
+`~3.18.4 || ~3.18.5-alpha.1`. The two vendor peers are outside DSH's own peer
+check — it reads only `@deepseek-ai/dsh` and `@deepseek-ai/dsh-*` — so their
+ranges matter only to npm's install-time resolution, which runs without
+`includePrerelease`; naming both vendored prereleases keeps a clean install on
+either host. `devDependencies` stay pinned to `0.2.0-rc.2`.
+
+The consequence is deliberate: `evaluatePluginCompatibility` runs before a
+profile is composed on every start, so the next DSH release will refuse to
+activate this plugin until the list is widened by an audit. That reversal of the
+2026-09-29 policy is recorded in `docs/决策记录.md` (章节一, 条目2).
+`tests/compatibility-metadata.test.ts` now asserts both admissions, fifteen
+rejections, and the two vendor ranges.
+
+### Host-side changes with no plugin impact
+
+`packages/schedule/schedule/**` has no changed source; the schedule error-code
+table is identical, so `src/wire-errors.ts`'s twelve mappings (including
+`subagent_session → E_PROTOCOL`) stay correct. No session-log format migration
+exists — `session-format*`, `v0-to-v1`…`v3-to-v4`, `session-persistence`,
+`session-projection*`, `session-log-deepseek` changed only their version and
+locale files — so phone history rendering is unaffected. The subagent descriptor
+is still version 3. `host/webserver`'s `port` widening, the macOS directory
+picker, the PTC call registry, and the new `job/registered` / `job/settled`
+events are all unreachable or safely skipped by this plugin (`projectEvent`'s
+`default: return null`). Settings surfaces are unchanged at the contract level:
+`ui-settings`'s `settings.section` slot has the same SHA as alpha.2, and
+`configForms.get()` kept its name. The Web composition still mounts
+`schedule`/`ui-schedule`, and `directory-picker` is still disabled in place, so
+the plugin's three `cordis.patch.yml` rows still land.
+
+### Validation evidence
+
+- **Config schema on the published CLI:** isolated `DSH_HOME`, `dsh
+  --profile deeppilot-audit --from-default-profile sdk-minimal
+  --dump-config-schema --patch cordis.patch.yml` against
+  `@deepseek-ai/dsh@0.2.1-alpha.3` → exit 0, 179,851 bytes, the plugin entry at
+  `/37` reports `status: 'schema'` with `configRef: #/$defs/config24`, all seven
+  volatile assertions pass, no `deeppilot`-attributed diagnostic, and the only
+  warning is the `sdk-minimal` template's own missing `directory-picker` row.
+- **Web composition:** the same CLI composed a real Web profile with the plugin
+  patch → **1225 rows versus 1214 without it**, the plugin's three rows present
+  at `deeppilot-directory-picker-browse` / `…-browse-client` / `deeppilot`, and
+  zero `unrecognized Loader tree carrier` entries on either side.
+- **Plugin unit tests:** `npx tsx --test tests/*.test.ts` → **562 tests, 561
+  pass, 0 fail, 1 todo**, including the six new contract tests. `npm run
+  typecheck`, `npm run build`, and `npm run check:config-schema` (against the
+  pinned `0.2.0-rc.2` CLI) all pass with regenerated `lib/`.
+- **Live A/B on a real `0.2.1-alpha.3` host — the evidence that matters.** An
+  isolated `DSH_HOME` profile built from the shipped Web template and linked to
+  this working tree booted under the published alpha.3 CLI (`--port 3180`; the
+  default 3080 was already held by this machine's own Host). The **unfixed**
+  `0.9.4` build printed
+  `[deeppilot] DSH Remote interaction client unavailable:
+  @deepseek-ai/dsh-typert-registry/client Client bundle returned no exports`
+  and the fixed build printed no such line. The checklist itself scored
+  **23 pass / 1 fail / 4 skipped in both runs** — see the blind spot below.
+- **The regression checklist does not cover this seam.** `scripts/smoke-live.mts`
+  scored identically before and after the fix, because the resident Client it
+  exercises is only reachable through the approval/question waterfall, and step
+  10 is skipped without `--interactions`. The observable difference is the Host
+  log line and the phone's approval/question delivery, not a checklist step. A
+  future revision should assert on that diagnostic directly.
+- **Backward compatibility, same working tree:** the same profile booted under
+  the published `0.2.1-alpha.2` CLI (`--port 3181`) scored **25 pass / 0 fail /
+  0 warn / 3 skipped** with no interaction-client diagnostic — the same result
+  the alpha.2 audit recorded, so the fix does not regress the host users run
+  today.
+- **One checklist difference between the two host versions is real.**
+  `模型目录可读` passes on alpha.2 and fails on alpha.3 in the same isolated
+  home (`0 provider / 0 model, routable=true`): this release stops listing a
+  pi-ai route before its credential resolves and returns only the version-gated
+  subset for the account route. The home has no model credential, so the phone's
+  model list is empty there. That is the documented behavior change, not a
+  plugin defect.
+- **Artifact inspection:** the `node`/`browser` conditional exports and the
+  banner counts above were read from the installed alpha.3 packages, not from
+  the diff.
+
+### Host-side migrations this machine must apply
+
+Neither is a plugin defect, and neither is fixed by the plugin change:
+
+1. **`llm-deepseek-account`'s retired `models` key.**
+   `~/.dsh/profiles/web/cordis.patch.yml:77-79` sets `models: []`.
+   `resolveAccountOptions` throws for *any* own `models` key
+   (`llm-deepseek-account: models is no longer configurable…`), and the
+   upstream test pins `[{ models: [] }, /models is no longer configurable/]`.
+   The empty array is not exempt. The `desktop` profile's row carries no
+   `config` and is unaffected. Whether the throw takes the whole Host down or
+   only retires that route was **not** measured — the guide says the account
+   models stop appearing either way.
+2. **`--from-default-profile` now replaces.** It stages a fresh copy over the
+   target and deletes the previous directory, including `node_modules` and the
+   user's own `cordis.patch.yml`. The re-audit procedure below and the alpha.2
+   entry's schema command both use that flag; from now on it must be pointed at
+   a scratch name.
+
+Checked and **not** required: Azure provider rename (no `azure` /
+`azure-openai-responses` key exists under `~/.dsh/profiles`), credential-file
+extra keys (the file's top level is already `version`/`refs`/`records`), and
+the stored-credential precedence flip (no `refs` name is exported in the shell,
+and the stored value won precedence over `.env` on both sides of the change).
+
+### Still unverified
+
+- Whether breaks 1 and 2 surface inside `dsh-api-proxy.ts`'s catch or escape it
+  as an unhandled rejection — the Gateway opens its Remote Events generation
+  asynchronously, after `startDshRemoteInteractions` has already returned.
+- Whether an old profile that predates `@deepseek-ai/dsh-api-remote-access`
+  still gets the row (the shipped Web template does; `dsh-base` carries it).
+- How the reshaped `contextBreakdown` renders on iOS, and what the phone shows
+  for the unmapped `CLIENT_UPGRADE_REQUIRED` / `MODEL_UNSUPPORTED` codes.
+- Whether the plugin's own `lib/client.js` (banner shape, `dsh.client.inject`,
+  `platform: web`) is still accepted by alpha.3's client-modules scanner; that
+  scanner lives in `packages/client/modules` and `packages/client/web`, which
+  were not read in full.
+
+### Re-audit procedure used
+
+Fetch the new tag into the existing blobless clone at `.audit-dsh-alpha2`
+(`git fetch --filter=blob:none --no-tags origin
+'+refs/tags/<tag>:refs/tags/<tag>'`, ~3 s), slice
+`git diff --name-status` per package, and write each slice's content diff to a
+file before parallel reading — blobless clones fetch blobs on demand, so one
+`git diff` per region is far cheaper than many small reads. Reproduce a
+suspected carrier break against the **published** `lib/` bundles with a stub
+`this`, as above, rather than trusting either the diff or the release notes.
+`npm --cache <workspace dir>` is still required; `~/.npm/_cacache` holds
+root-owned files and fails `npm view` with `EPERM`.
+
 ## 2026-10-09 — audit of `dsh-v0.2.1-alpha.2`
 
 ### Scope and method
@@ -316,12 +847,12 @@ the mirror's `signal` is required, so the compiler keeps it that way.
 own, so a dedicated long-lived controller is not warranted; following the
 existing convention in the same file is enough. `lib/index.js` was regenerated.
 
-The fix ships in `0.9.4`, which is prepared but not published (see "Plugin release
-verdicts"); until it is published, a host on `0.2.1-alpha.2` running the
-published `0.9.3` still loses the on-open projection baseline. That was observed
-directly: on a live `0.2.1-alpha.2` host running published `0.9.3` the diagnostic
-appeared, and on the same host version running this build it did not (see "Live
-run on a real `0.2.1-alpha.2` host" under Validation evidence).
+The fix ships in `0.9.4`, published 2026-10-10 (see "Plugin release verdicts").
+A host on `0.2.1-alpha.2` left on the published `0.9.3` still loses the on-open
+projection baseline. That was observed directly: on a live `0.2.1-alpha.2` host
+running published `0.9.3` the diagnostic appeared, and on the same host version
+running this build it did not (see "Live run on a real `0.2.1-alpha.2` host"
+under Validation evidence).
 
 `tests/dsh-api-proxy.test.ts` adds "projection baseline reads pass the
 AbortSignal the Host now requires": a controller stub that calls