dsh-deeppilot 0.9.6 → 0.9.8

package/COMPATIBILITY.md

@@ -1,25 +1,27 @@
 # Compatibility
 
-This branch targets exactly **three DSH releases**: `0.2.0-rc.2`, which the npm
-`latest`/`next` channels point at, and `0.2.1-alpha.3` and `0.2.1-alpha.4`, which
-the `alpha` channel has pointed at in turn. All three are named in both
-`engines.dsh` and `peerDependencies`; no other version is accepted. DSH evaluates
-that declaration before composing a profile — on every start, not only on
-install — so a newly published DSH release deactivates this plugin until the
-list is widened deliberately. That is the intended trade: a plugin that cannot
-run on an unaudited host fails visibly instead of misbehaving quietly. The
-decision and the reversal it represents are recorded in
+This branch targets exactly **five DSH releases**: `0.2.0-rc.2`, which the npm
+`latest` channel points at; `0.2.1-alpha.3`, `0.2.1-alpha.4`, and
+`0.2.1-alpha.5`, which the `alpha` channel has pointed at in turn; and
+`0.2.1-rc.2`, which the `next` channel points at. All five are
+named in both `engines.dsh` and `peerDependencies`; no other version is accepted.
+DSH evaluates that declaration before composing a profile — on every start, not
+only on install — so a newly published DSH release deactivates this plugin until
+the list is widened deliberately. That is the intended trade: a plugin that
+cannot run on an unaudited host fails visibly instead of misbehaving quietly.
+The decision and the reversal it represents are recorded in
 [`docs/决策记录.md`](./docs/决策记录.md) (章节一), with the supporting audit in
 [`docs/DSH_RELEASE_MEMORY.md`](./docs/DSH_RELEASE_MEMORY.md).
 
 The development packages this branch builds and typechecks against stay pinned
-to the exact release-candidate baseline, currently `0.2.0-rc.2`; the alpha host
-is covered by the isolated compose and live-runs recorded in the release memory.
+to the exact release-candidate baseline, currently `0.2.0-rc.2`; the audited
+`alpha` and `rc` hosts are covered by the isolated composes and live runs
+recorded in the release memory.
 
 | Component | Current contract | Evidence |
 |---|---|---|
 | Node.js | 22 or newer | Package engine and CI |
-| DSH CLI and Host API | `engines.dsh` and `peerDependencies` both name `0.2.0-rc.2 \|\| 0.2.1-alpha.3 \|\| 0.2.1-alpha.4` (dev pins `0.2.0-rc.2`) | Peer metadata, source typecheck, unit tests, bundle build, and config schema projection against a real 0.2.0-rc.2 CLI, plus isolated composes and live phone-protocol runs with the published 0.2.1-alpha.2, 0.2.1-alpha.3, and 0.2.1-alpha.4 CLIs |
+| DSH CLI and Host API | `engines.dsh` and `peerDependencies` both name `0.2.0-rc.2 \|\| 0.2.1-alpha.3 \|\| 0.2.1-alpha.4 \|\| 0.2.1-alpha.5 \|\| 0.2.1-rc.2` (dev pins `0.2.0-rc.2`) | Peer metadata, source typecheck, unit tests, bundle build, and config schema projection against a real 0.2.0-rc.2 CLI, plus isolated composes and live phone-protocol runs with the published 0.2.1-alpha.2, 0.2.1-alpha.3, and 0.2.1-alpha.4 CLIs, an isolated 0.2.1-alpha.5 host where this plugin now composes, starts, and answers `/phone/health` with 200 on its own LAN listener, and a pre-widening 0.2.1-rc.2 host run where the unchanged declaration is refused at compose time (audits below) |
 | iOS bridge | DeepPilot protocol v2 | Bridge protocol tests; device behavior must be checked with the running Host and app |
 | Remote access | Tailscale Funnel on ports 443, 8443, or 10000 | Helper and supervisor tests |
 
@@ -71,6 +73,99 @@ carries the old top-level `debug: true` is accepted but that value is ignored:
 verbose logging must be turned on again from the settings page. No other config
 field changed shape, and the old key is not read anywhere in this version.
 
+## 0.2.1-rc.2 audit outcome
+
+The artifact-level audit of `dsh-v0.2.1-rc.2` against `dsh-v0.2.1-alpha.5` found
+no change that reaches this plugin's call surface. Fifteen packages were compared
+as whole trees rather than by `lib/` alone: all ten peer packages carry
+**byte-identical `lib/` trees**, and across 137 modules **no export symbol is
+added or removed**. The 245 dependency differences are spec-value moves only,
+with zero structural difference: 78 `@deepseek-ai/dsh*` entries are pinned to
+`0.2.1-rc.2`, and five vendor ranges are promoted from prerelease to GA —
+`cordis ~4.0.5-alpha.2` → `~4.0.5`, `schemastery ~3.18.5-alpha.2` → `~3.18.5`,
+plus `cordis-plugin-include`, `cordis-plugin-loader`, and `cordis-plugin-timer`.
+No dependency package name is added or removed.
+
+**One file outside `package.json` differs, and it is additive.**
+`@deepseek-ai/dsh-web-app/cordis.patch.yml` gained one hunk / +3−0 that inserts
+the `ui-deepseek-model-label-1017` bundle (the DeepSeek-V4.1-Flash-1017
+adaptation named in the rc.2 release notes). It cannot reach this plugin: the
+patch anchor this plugin targets, `id: directory-picker`, is byte-identical at
+lines 113–114 on both sides, the new entry sits at lines 412–417, and the new
+package name appears zero times in this plugin's `cordis.patch.yml` and
+`package.json`.
+
+That file is also why the audit method changed: **comparing only `lib/` would
+have missed it**, and it is exactly the surface this plugin's own patch layer
+acts on. Whole-tree comparison is now a required step of every future audit, not
+a fallback.
+
+The vendor peers need no widening either. `0.2.1-rc.2` vendors the same GA pair
+as `0.2.1-alpha.5` — `cordis 4.0.5` and `schemastery 3.18.5` — and four
+independent solver paths (host-tree and repository `semver`, each with and
+without `includePrerelease`) agree that both already satisfy the existing
+`~4.0.4 || ~4.0.5-alpha.1` / `~3.18.4 || ~3.18.5-alpha.1` ranges.
+
+The activation verdict is the same shape as alpha.5: rc.2 resolves the
+requirements path from a declared `engines.dsh` alone, so its refusal names that
+single requirement rather than the ten peers, and `exempted` is false because no
+profile exemption file exists on the audit machine. Before the widening, a real
+rc.2 CLI refused the unchanged declaration —
+
+```text
+dsh: skipping profile bundle "dsh-deeppilot": … Plugin dsh-deeppilot@0.9.7 is incompatible with dsh 0.2.1-rc.2: requirements {"engines.dsh":"0.2.0-rc.2 || 0.2.1-alpha.3 || 0.2.1-alpha.4 || 0.2.1-alpha.5"}. … Exact-version exemption: not active.
+```
+
+— while the host itself still booted and served its web port. Three published
+evaluators agree on all 14 candidates, and the widened declaration admits
+`0.2.1-rc.2` while adding no other acceptance. **`0.2.1-rc.1` is deliberately not
+added and remains refused**: the rc line reached this plugin one release later, so
+admitting the earlier rc would extend support to a host that was never audited as
+its own. `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.0-rc.1`, `0.2.0`, `0.2.1`,
+`0.2.1-rc.3`, `0.3.0-rc.1`, `0.3.0`, `1.0.0`, and `0.1.7-rc.2` remain refused.
+
+**Audit limits, stated rather than implied.** Loading this plugin on a real
+isolated `0.2.1-rc.2` host — the positive half of the rc.2 verification — had
+**not** been completed when this entry was written; the rc.2 evidence here is the
+pre-widening refusal log plus the published evaluators' verdict on the widened
+declaration. Until the positive load and the full release check set run against
+that host, this release is recorded as audited at the declaration and
+artifact-diff level only; no plugin release has been made from this tree, and
+nothing here claims one.
+
+## 0.2.1-alpha.5 audit outcome
+
+The source-level audit of `dsh-v0.2.1-alpha.5` against `dsh-v0.2.1-alpha.4` found
+no runtime break. Of the ten peer packages, **nine have byte-identical `lib/`
+trees** — including `dsh-api-gateway` and the three Client faces the resident
+interaction client loads — so every alpha.3 fix still holds unchanged. Only
+`dsh-api-remotes/lib/client.js` differs: three hunks / 36 lines, all inside the
+`account/getUnnotifiedBonuses` result schema, where the new optional `title`
+field arrives while `campaign`, `amount`, `currency`, and `grantedAt` become
+optional and are forwarded without validation. The file's exported symbols are
+identical, and this plugin does not consume that endpoint, so the change is
+additive from here.
+
+The vendor peers need no widening either: both hosts' vendor pins moved from
+prerelease to GA — `cordis 4.0.5-alpha.2` → `4.0.5` and `schemastery
+3.18.5-alpha.2` → `3.18.5` — and both GA releases already satisfy the existing
+`~4.0.5-alpha.1` / `~3.18.5-alpha.1` ranges.
+
+The activation verdict is the same shape as alpha.4, with one difference: alpha.5
+resolves the requirements path from a declared `engines.dsh` alone, so its
+refusal names that single requirement rather than the ten peers. Adding
+`0.2.1-alpha.5` to the closed list therefore makes it activate, and the four
+audited hosts pass while `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.0-rc.1`, `0.2.0`,
+`0.2.1-rc.1`, `0.2.1`, `0.3.0-rc.1`, `0.3.0`, `1.0.0`, and `0.1.7-rc.2` remain
+refused.
+
+**Audit limits, stated rather than implied.** Loading this plugin on a real
+isolated `0.2.1-alpha.5` host, and the full release check set (unit tests,
+typecheck, build, config-schema check, helper tests) against that host, had
+**not** been completed when this entry was written. Until they are, this release
+is recorded as audited at the declaration and source-diff level only; no plugin
+release has been made from this tree, and nothing here claims one.
+
 ## 0.2.1-alpha.4 audit outcome
 
 The source-level audit of `dsh-v0.2.1-alpha.4` against `dsh-v0.2.1-alpha.3` found
@@ -89,10 +184,11 @@ plugin's `engines.dsh` range **alone**, ignoring `peerDependencies` entirely
 whenever that field is present. A package that declares no `engines.dsh` — as
 this one did — keeps the older peer evaluation, so the previously exact peer
 list rejected `0.2.1-alpha.4` and the plugin would not have activated on it.
-Both declarations now name the same three releases. The audit reproduced that
-refusal against the published `evaluatePluginCompatibility` of both hosts before
-changing anything, and the same harness confirms the three audited hosts pass
-while `0.2.1-alpha.2`, `0.2.1-alpha.5`, `0.2.1`, and `0.3.0` still fail.
+Both declarations were widened from the previous three-release list to the same
+four releases. The audit reproduced that refusal against the published
+`evaluatePluginCompatibility` of both hosts before changing anything, and the
+same harness confirms the four audited hosts pass while `0.2.1-alpha.2`,
+`0.2.1`, and `0.3.0` still fail.
 
 Nothing else moved. Protocol v2, pairing state, and device records are untouched,
 so no paired phone needs to re-pair, and the vendor peers need no widening: both
@@ -175,8 +271,13 @@ needs a documentation update, not a peer-range widening.
 > versions actually audited, `0.2.0-rc.2` and `0.2.1-alpha.3`; see the
 > 0.2.1-alpha.3 outcome above and `docs/决策记录.md` (章节一). The paragraphs in
 > this historical entry describe the policy as it stood on 2026-09-29.
-> `0.2.1-alpha.4` was added the next day by the same deliberate audit step, and
-> the list now lives in `engines.dsh` as well as in `peerDependencies`.
+> **This note is in turn superseded:** `0.2.1-alpha.4` was added the next day by
+> the same deliberate audit step, `0.2.1-alpha.5` on 2026-10-16, and
+> `0.2.1-rc.2` on 2026-10-17 — each one its own audit, never an automatic
+> consequence of a new DSH tag. The closed five-release list now lives in
+> `engines.dsh` as well as in `peerDependencies`. `0.2.1-rc.1` shows zero code
+> delta on this plugin's call surface but is deliberately left out, because it
+> was never audited as its own host. See the 0.2.1-rc.2 outcome above.
 
 ## 0.2.0-rc.1 audit outcome
 

package/README.md

@@ -32,17 +32,19 @@ Host on your own computer and does not replace or modify the DSH Web UI.
 
 ## Install from npm
 
-This source checkout targets Node.js 22+ and the three DSH releases it has been
-audited against — `0.2.0-rc.2` (the `latest`/`next` channels) and the `alpha`
-channel releases `0.2.1-alpha.3` and `0.2.1-alpha.4` — with a `web` profile. DSH
-checks a plugin's declared requirements before composing a profile, on every
-start rather than only on install, so any other host version refuses to activate
-this plugin. From DSH `0.2.1-alpha.4` on, that check reads `engines.dsh` and
-ignores `peerDependencies`; older hosts know only the peer range, so both name
-the same three releases. The package includes Funnel helpers for macOS, Linux,
-and Windows on amd64/arm64; trusted-LAN mode does not require the helper.
-
-The current working tree names exactly those three versions in `engines.dsh` and
+This source checkout targets Node.js 22+ and the five DSH releases it has been
+audited against — `0.2.0-rc.2` (the `latest` channel), the `alpha` channel
+releases `0.2.1-alpha.3`, `0.2.1-alpha.4`, and `0.2.1-alpha.5`, and `0.2.1-rc.2`
+(the `next` channel) — with a `web` profile. DSH checks a plugin's declared
+requirements before composing a profile, on every start rather than only on
+install, so any other host version refuses to activate this plugin. From DSH
+`0.2.1-alpha.4` on, that check reads `engines.dsh` and ignores
+`peerDependencies`; older hosts know only the peer range, so both name the same
+five releases. The package includes Funnel helpers
+for macOS, Linux, and Windows on amd64/arm64; trusted-LAN mode does not require
+the helper.
+
+The current working tree names exactly those five versions in `engines.dsh` and
 `peerDependencies` and is built/typechecked against `0.2.0-rc.2`. A previously
 published plugin package may still carry its own older compatibility
 declaration until a release is made from this tree.

package/README.zh-CN.md

@@ -30,16 +30,17 @@
 
 ## 从 npm 安装
 
-当前源码面向 Node.js 22+ 与带 `web` profile 的**三个已审计 DSH 版本**：
-`0.2.0-rc.2`（`latest`/`next` 通道），以及 `alpha` 通道的 `0.2.1-alpha.3`
-与 `0.2.1-alpha.4`。DSH 在组合 profile 前会校验插件声明的兼容要求，且
-**每次启动都会校验**（不只是安装时），因此其他宿主版本会拒绝激活本插件。
-从 DSH `0.2.1-alpha.4` 起，该校验只读 `engines.dsh` 并忽略
-`peerDependencies`；更早的宿主只认 peer 范围，因此两处列出同一组三个版本。
+当前源码面向 Node.js 22+ 与带 `web` profile 的**五个已审计 DSH 版本**：
+`0.2.0-rc.2`（`latest` 通道）、`alpha` 通道的 `0.2.1-alpha.3`、
+`0.2.1-alpha.4` 与 `0.2.1-alpha.5`，以及 `0.2.1-rc.2`（`next` 通道）。
+DSH 在组合 profile 前会校验插件声明的
+兼容要求，且**每次启动都会校验**（不只是安装时），因此其他宿主版本会拒绝
+激活本插件。从 DSH `0.2.1-alpha.4` 起，该校验只读 `engines.dsh` 并忽略
+`peerDependencies`；更早的宿主只认 peer 范围，因此两处列出同一组五个版本。
 npm 包内置 macOS、Linux、Windows 的 amd64/arm64 Funnel helper；可信局域网
 模式不依赖 helper。
 
-当前工作树的 `engines.dsh` 与 `peerDependencies` 精确列出这三个版本，构建与
+当前工作树的 `engines.dsh` 与 `peerDependencies` 精确列出这五个版本，构建与
 类型检查针对 `0.2.0-rc.2`。从此工作树发布新版本前，已发布的旧插件包仍可能
 带有各自旧的兼容声明。
 

package/docs/DSH_RELEASE_MEMORY.md

@@ -3,7 +3,196 @@
 > 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 — `dsh-v0.2.1-alpha.4`
+## Current decision — `dsh-v0.2.1-rc.2`
+
+- **Audited release:** `dsh-v0.2.1-rc.2`, published 2026-10-17T08:36:31.655Z. It is
+  **not** `latest`: `latest` still points at `0.2.0-rc.2`, and `alpha` still points
+  at `0.2.1-alpha.5`. It **is** the npm **`next`** channel release — this is the
+  first release on the rc line to enter the supported list.
+- **Comparison baseline:** `dsh-v0.2.1-alpha.5` (the previous audited tag).
+- **Plugin runtime verdict: no break, and no `src/` change was needed.** Fifteen
+  packages were compared **as whole trees, not by `lib/` alone**: all ten peer
+  packages ship a byte-identical `lib/` tree, and across 137 modules **no export
+  symbol is added or removed**, so every earlier fix still holds unchanged.
+- **The one file outside `package.json` that differs is additive.**
+  `@deepseek-ai/dsh-web-app/cordis.patch.yml` gained one hunk / +3−0 inserting the
+  `ui-deepseek-model-label-1017` bundle (the DeepSeek-V4.1-Flash-1017 adaptation
+  named in the release notes). The patch anchor this plugin targets,
+  `id: directory-picker`, is byte-identical at lines 113–114 on both sides, the new
+  entry sits at lines 412–417, and the new package name appears zero times in this
+  plugin's `cordis.patch.yml` and `package.json`, so the change cannot reach any
+  patch this plugin applies.
+- **Methodology change, now mandatory.** Comparing only `lib/` would have missed
+  exactly that file — and it is the surface this plugin's own patch layer acts on.
+  Whole-tree comparison is a required step of every future audit; do not fall back
+  to a `lib/`-only diff. See "Re-audit rule" below.
+- **Activation verdict: the new release is admitted by both declarations, and the
+  earlier rc on the same line is deliberately left out.** This is the fourth
+  consecutive release on this line to trip the closed-list policy: rc.2 was refused
+  before the widening. rc.2 reads a declared `engines.dsh` alone, so its refusal
+  reported a **single** `engines.dsh` requirement rather than ten peers, and
+  `exempted: false` — the list is the only thing that admits a host, and no
+  exemption fallback exists on this machine (no profile `compatibility.json` under
+  `DSH_HOME`). Widening admits `0.2.1-rc.2` and nothing else. `0.2.1-rc.1` stays
+  refused even though it shows **zero code delta on this plugin's call surface**:
+  it was never audited as its own host, and the rc line reached this plugin one
+  release later.
+- **Evidence: the published artifacts, the published evaluators, and a real rc.2
+  CLI run — all taken before any declaration changed.**
+  - **Change surface:** `.rc2-verify/CHANGE_SURFACE.md`. Raw logs:
+    `.rc2-verify/logs/lib-hash-compare.txt` and `lib-diff-exitcodes.txt` (10 of 10
+    peer `lib/` trees byte-identical), `whole-tree-compare.txt` (the 15-package
+    whole-tree fallback, which is what surfaced the `dsh-web-app` patch file),
+    `export-symbol-diff.out.json` (137 modules, zero symbol changes),
+    `pkg-manifest-delta.out.json` (245 spec-value differences, zero structural
+    differences), `webapp-cordis-patch-diff.txt` and `patch-anchor-verification.txt`
+    (the one differing file and its anchor), `rc1-delta.txt` (`0.2.1-rc.1` has zero
+    code delta on this plugin's call surface), and `evaluator-repro.out.json`
+    (three published evaluators × 14 candidates, all agreeing).
+  - **Activation decision, reproduced against rc.2's own published evaluator
+    before any edit:** `.rc2-verify/ACTIVATION.md` and `rc2-matrix.out.json`.
+    Unchanged, rc.2 was refused with a single `engines.dsh` requirement and
+    `exempted: false`; deleting `engines.dsh` from a copy of the manifest fell back
+    to all ten peers, confirming the short-circuit is unchanged. Projecting the
+    widening in memory admitted exactly `0.2.1-rc.2` with zero new refusals, while
+    `0.2.1-rc.3`, `0.2.1-rc.20`, `0.2.1-rc.2.1`, `0.2.1-RC.2`, and `0.2.1-rc.10`
+    stayed refused (`rc2-matrix-projected.out.json`).
+  - **Real CLI refusal, captured while the declaration was still unchanged:**
+    `.rc2-verify/PRECHANGE-BOOT.md`. Under an isolated `DSH_HOME` the real rc.2 CLI
+    printed `dsh: skipping profile bundle "dsh-deeppilot": … incompatible with dsh
+    0.2.1-rc.2: requirements {"engines.dsh":…}` plus `Exact-version exemption: not
+    active.`, `--dump-config` exited 0 with no plugin row in the composed tree, and
+    the host itself still booted (web port answered, while the plugin's own port
+    3098 had no listener). Raw logs: `PRECHANGE-dumpconfig.stderr.txt`,
+    `PRECHANGE-dumpconfig.stdout.txt`, `PRECHANGE-host.log`, `PRECHANGE-probes.txt`.
+    A control run of the same profile under the `0.2.1-alpha.5` CLI — which admits
+    `0.9.7` — loaded the plugin and answered `200` on port 3098
+    (`PRECHANGE-control-alpha5-host.log`, `PRECHANGE-control-alpha5-probes.txt`),
+    showing the negative probe has discriminating power.
+- **Vendor pins: no range change needed.** rc.2 vendors the same GA pair as
+  alpha.5 — `cordis 4.0.5` and `schemastery 3.18.5` — and four independent solver
+  paths (host-tree and repository `semver`, each with and without
+  `includePrerelease`) agree both already satisfy the existing `~4.0.4 ||
+  ~4.0.5-alpha.1` / `~3.18.4 || ~3.18.5-alpha.1` ranges
+  (`.rc2-verify/rc2-vendor.out.json`). Neither vendor published a new
+  per-DSH-release dist-tag for rc.2; their `latest` is already `4.0.5` / `3.18.5`.
+- **Install verdict: the two declarations now agree on five releases.**
+  `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 || 0.2.1-alpha.5 || 0.2.1-rc.2`, mirrored in
+  `tests/compatibility-metadata.test.ts`, `package-lock.json` (root entry only),
+  both READMEs, `COMPATIBILITY.md`, `AGENTS.md`, and the local
+  `docs/决策记录.md` (章节一, 条目5). The tests now also pin `0.2.1-rc.1` and
+  `0.2.1-rc.3` as negative probes, so neither the skipped rc nor the next rc can be
+  admitted by accident. The dev pins and `DSH_BASELINE` stay at the exact
+  `0.2.0-rc.2` this branch builds and typechecks against.
+- **Protocol verdict: no phone-protocol change.** Protocol v2, pairing state, and
+  device records are untouched by this release; no phone needs to re-pair.
+- **Audit limits, stated rather than implied.** The positive half of the rc.2
+  verification — loading this plugin on a real isolated `0.2.1-rc.2` host after the
+  widening — had **not** been completed when this entry was written, and neither had
+  the full release check set against that host. Until they run, rc.2 is recorded as
+  audited at the artifact-diff and declaration level only; no plugin release has
+  been made from this tree.
+
+### Previous decision — `dsh-v0.2.1-alpha.5`
+
+- **Audited release:** `dsh-v0.2.1-alpha.5`, the newest `alpha` channel release.
+  It is **not** `latest`; `latest`/`next` still point at `0.2.0-rc.2`.
+  *(Superseded 2026-10-17 by `dsh-v0.2.1-rc.2`: `next` now points at
+  `0.2.1-rc.2`. `alpha` still points at `0.2.1-alpha.5` and `latest` still points
+  at `0.2.0-rc.2`. See the current decision above.)*
+- **Comparison baseline:** `dsh-v0.2.1-alpha.4` (the previous audited tag).
+- **Plugin runtime verdict: no break, and no `src/` change was needed.** Nine of
+  the ten peer packages ship a byte-identical `lib/` tree, including
+  `dsh-api-gateway` and the three Client faces the resident interaction client
+  loads, so every alpha.3 fix still holds unchanged.
+- **The one code difference is schema-only and additive.**
+  `@deepseek-ai/dsh-api-remotes/lib/client.js` is the only differing `lib/` file
+  among the ten peers: **three hunks, 36 changed lines** (14 insertions, 22
+  deletions), all inside the `account/getUnnotifiedBonuses` result schema. The
+  new `title` field is added as optional; `campaign`, `amount`, `currency`, and
+  `grantedAt` are relaxed to optional and the first three lose their validation
+  (`campaign` becomes "forwarded without validation", `amount` and `currency`
+  become unconstrained JSON); only the descriptions of `expiresAt` changed.
+  `orderId`, `expiresAt`, and `message` stay required. The module's **exported
+  symbols are identical** — both versions assign exactly `exports.apply` and
+  `exports.inject` — and this plugin does not consume that endpoint, so the
+  change cannot reach any call it makes.
+- **Activation verdict: the new release is admitted by both declarations.** This
+  is the third consecutive release on this line to trip the deliberate
+  closed-list policy: alpha.5 was refused before the widening. alpha.5 reads a
+  declared `engines.dsh` alone, so its refusal reported a **single**
+  `engines.dsh` requirement rather than ten peers, and `exempted: false` — the
+  list is the only thing that admits a host, and no exemption fallback exists on
+  this machine (no profile `compatibility.json`).
+- **Evidence: reproduced against the published evaluator, plus an isolated
+  host run.** The audit called alpha.5's own published
+  `evaluatePluginCompatibility` with empty exemptions against this plugin's real
+  `package.json`, over one candidate list. Raw output:
+  `.alpha5-verify/tmp-matrix-early.out.json` (13 candidates, `matrixAllPass:
+  true`) and `.alpha5-verify/stage1-baseline.out.json` (the pre-change baseline).
+  Accepted after the change: `0.2.1-alpha.5`, `0.2.1-alpha.3`,
+  `0.2.1-alpha.4`, and the stable `latest` host. Still refused:
+  `0.2.1-alpha.1`, `0.2.1-alpha.2`, `0.2.0-rc.1`, `0.2.0`, `0.2.1-rc.1`,
+  `0.2.1`, `0.3.0-rc.1`, `0.3.0`, `1.0.0`, and `0.1.7-rc.2`. The same file
+  confirms declaration sync: `engines.dsh` equals the `@deepseek-ai/dsh` peer
+  range, all ten peers share one range, and the token count is 4.
+  `.alpha5-verify/VERIFICATION.md` separately records the refusal on an isolated
+  alpha.5 host: `dsh: skipping profile bundle "dsh-deeppilot": … incompatible
+  with dsh 0.2.1-alpha.5: requirements {"engines.dsh":…}`, with the host itself
+  still booting (`/phone/health` → 404, so the plugin was genuinely not loaded).
+  `.alpha5-verify/stage1-dumpconfig-phaseA.stderr.txt`,
+  `stage1-dumpconfig-phaseA.stdout.txt`, and `stage1-host-phaseA.log` hold the
+  raw logs.
+- **Vendor pins promoted to GA, with no range change needed.** Both hosts'
+  vendored third parties moved from prerelease to GA — `cordis
+  4.0.5-alpha.2` → `4.0.5`, `schemastery 3.18.5-alpha.2` → `3.18.5`. Both GA
+  releases already satisfy the existing `~4.0.5-alpha.1` / `~3.18.5-alpha.1`
+  ranges, so the two vendor peers stay as they are.
+  `.alpha5-verify/stage1-semver-vendor.out.json` cross-checks that with four
+  independent solver paths (host `semver` and repo `semver`, each with and
+  without `includePrerelease`), all four agreeing.
+- **Install verdict: the two declarations now agree on four releases.**
+  `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 || 0.2.1-alpha.5`, mirrored in
+  `tests/compatibility-metadata.test.ts`, `package-lock.json` (root entry only),
+  both READMEs, `COMPATIBILITY.md`, `AGENTS.md`, and the local
+  `docs/决策记录.md` (章节一, 条目4). The dev pins and `DSH_BASELINE` stay at the
+  exact `0.2.0-rc.2` this branch builds and typechecks against.
+- **Protocol verdict: no phone-protocol change.** Protocol v2, pairing state, and
+  device records are untouched by this release; no phone needs to re-pair.
+- **Post-widening verification — completed for the 0.9.7 preparation.**
+  - **C7 — real load on an isolated alpha.5 host: passed.** With the widened
+    declaration in place, the profile that used to be refused now composes and
+    starts. `--dump-config` writes nothing to stderr and no longer emits
+    `skipping profile bundle` (the pre-change baseline emitted 21 such lines); the
+    composed tree contains `# == dsh-deeppilot` together with
+    `# == @deepseek-ai/dsh-web-app, patched by dsh-deeppilot`; the running host
+    logs four `[deeppilot]` lines (`device registry loaded`, `data plane active`,
+    `LAN TLS identity created`, `local transport listening on https://0.0.0.0:3098`);
+    and `https://127.0.0.1:3098/phone/health` answers `200` with
+    `{"ok":true,"enabled":true,"protocolVersion":2,"serverVersion":"0.9.6","dataPlane":true}`.
+  - **Probe note — use the plugin's own listener, not DSH's web port.** The
+    pre-change baseline cited `http://127.0.0.1:3281/phone/health = 404` as its
+    refusal evidence. That probe has no discriminating power: `/phone/health` is
+    served by this plugin's own narrow LAN listener (`src/phone-server.ts`), which
+    by design never inherits DSH's wider web/API route surface, so the DSH web
+    port answers 404 whether or not the plugin loaded. The valid refusal evidence
+    was the skip warning; the valid positive evidence is port 3098.
+  - **C5/C6 — the full check set: passed in the release tree.** Clean `npm ci`,
+    repo-wide `npm test` (564 tests, 563 pass, 0 fail, 1 pre-existing TODO),
+    `npm run typecheck`, `npm run build` (regenerated `lib/` byte-identical to the
+    committed tree), `npm run check:config-schema` against the pinned
+    `0.2.0-rc.2` CLI, `go test ./...` for the helper, and all six
+    `bin/SHA256SUMS` entries verified.
+- **Published as 0.9.7 on 2026-10-17.** `npm view dsh-deeppilot dist-tags` reads
+  `latest: 0.9.7`, and the version carries an npm provenance attestation
+  (`https://slsa.dev/provenance/v1`). The release commit `bf18755` is on `main`,
+  the annotated tag `v0.9.7` dereferences to it, and the GitHub release was made
+  public only after a clean-profile install had been verified — see the publish
+  verification section below.
+
+### Previous 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>),
@@ -45,15 +234,20 @@
   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.
+  *(Historical: `0.2.1-alpha.5` was admitted the next day by the audit above.)*
   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
+- **Install verdict: the two declarations agreed at that point (widened since).**
+  `engines.dsh` and all ten `@deepseek-ai/dsh*` peers named `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.
+  `0.2.0-rc.2` this branch builds and typechecks against. **Historical note:**
+  `0.2.1-alpha.5` was appended to both lists on 2026-10-16 by the audit above,
+  which now owns the current list; the four documentation mirrors that still
+  said「三个版本」were corrected there.
 - **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` /
@@ -389,6 +583,120 @@
   bundle" below. The plugin needs no code change; the phone's copy now points
   at the bundle.
 
+## 2026-10-16 — audit of `dsh-v0.2.1-alpha.5`
+
+The first release on this line whose entire plugin-facing change surface is
+additive. It is the third consecutive release to trip the closed-list policy: a
+new DSH tag refuses to activate this plugin until the list is widened by an
+audit, which is the behaviour the 2026-10-14 reversal chose on purpose.
+
+### Method
+
+The comparison used the **installed artifacts** of the alpha.4 and alpha.5 hosts
+already unpacked on this machine, not release notes and not the monorepo: every
+`@deepseek-ai/dsh*` peer package's `lib/` directory was compared file by file,
+and the single differing file was then read as a diff. `dsh-client-ui-slots` is
+not hoisted into either host's `node_modules` root (it resolves only inside a
+composed profile), so both of its published versions were pulled from npm
+(`0.2.1-alpha.4` and `0.2.1-alpha.5`, 31,973 bytes each) and compared in full to
+close that gap rather than assume it.
+
+### Change surface
+
+- **Nine of the ten peer packages carry a byte-identical `lib/` tree**:
+  `dsh`, `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`. The tenth is `dsh-api-remotes`.
+- **`dsh-api-remotes/lib/client.js` — three hunks, 36 changed lines.** Every
+  hunk is the `account/getUnnotifiedBonuses` result schema:
+  - `title` is added, optional, described as a server-localised plain-text title
+    that absent responses replace with the localised bonus title.
+  - `campaign`, `amount`, `currency`, and `grantedAt` become optional; `campaign`
+    becomes unvalidated pass-through JSON, `amount` and `currency` lose their
+    string / `CNY|USD` constraints, and `grantedAt` loses its description.
+  - The JSON Schema side mirrors that: `title` is added to `properties`, and
+    `campaign`, `amount`, `currency`, and `grantedAt` are dropped from
+    `required`. `orderId`, `expiresAt`, and `message` remain required.
+  - **The exported symbols are unchanged**: the module assigns exactly
+    `exports.apply` and `exports.inject` on both sides.
+  - This plugin does not call `account/getUnnotifiedBonuses`, so even the field
+    that did tighten (`expiresAt`'s documented semantics) cannot reach it.
+- **The vendor pins moved from prerelease to GA.** The `dsh` CLI's vendored
+  third parties went `cordis 4.0.5-alpha.2` → `4.0.5` and `schemastery
+  3.18.5-alpha.2` → `3.18.5`. Both GA releases already satisfy the plugin's
+  existing `~4.0.5-alpha.1` / `~3.18.5-alpha.1` ranges, so **no vendor widening
+  was needed**; the ranges were left untouched.
+- **The activation rule did not change again.** alpha.5 keeps alpha.4's
+  requirements path: a declared `engines.dsh` decides alone and short-circuits the
+  peer loop. That is why the refusal is reported as one requirement instead of
+  ten.
+
+### Validation evidence
+
+- **Compatibility matrix against the published evaluator.** alpha.5's own
+  published `evaluatePluginCompatibility`, called with empty exemptions against
+  this plugin's real `package.json` over 13 candidates →
+  `.alpha5-verify/tmp-matrix-early.out.json`, `matrixAllPass: true`. Accepted:
+  `0.2.1-alpha.5` (the target), `0.2.1-alpha.3`, `0.2.1-alpha.4`, and the stable
+  host. Refused, each with `exempted: false`: `0.2.1-alpha.1`,
+  `0.2.1-alpha.2`, `0.2.0-rc.1`, `0.2.0`, `0.2.1-rc.1`, `0.2.1`, `0.3.0-rc.1`,
+  `0.3.0`, `1.0.0`, `0.1.7-rc.2`. The same file's `declarationSync` block
+  reports `engines.dsh === @deepseek-ai/dsh peer range`, all ten peers on one
+  range, and four unique `engines.dsh` tokens.
+- **Pre-change baseline, the same evaluator.** `.alpha5-verify/stage1-baseline.out.json`
+  shows the unchanged declaration refusing `0.2.1-alpha.5` with
+  `requirements: { "engines.dsh": "0.2.0-rc.2 || 0.2.1-alpha.3 || 0.2.1-alpha.4" }`
+  and `exempted: false` — the failure this audit removes.
+- **Isolated alpha.5 host, pre-change.** `.alpha5-verify/VERIFICATION.md` and
+  `stage1-dumpconfig-phaseA.stderr.txt` record the real CLI refusing the plugin:
+  `dsh: skipping profile bundle "dsh-deeppilot": Error: Plugin
+  dsh-deeppilot@0.9.6 is incompatible with dsh 0.2.1-alpha.5: requirements
+  {"engines.dsh":…}`, `Exact-version exemption: not active`. The host still
+  booted (`stage1-host-phaseA.log`, `--port 3280`) and `/phone/health` returned
+  404, which is what shows the plugin really was not loaded rather than silently
+  active.
+- **Vendor semver, four independent paths.** `.alpha5-verify/stage1-semver-vendor.out.json`
+  resolves the two vendor ranges with the host tree's `semver` and the repo's
+  `semver`, each with and without `includePrerelease`; all four agree that
+  `4.0.5` and `3.18.5` (and the previously audited `4.0.4`, `4.0.5-alpha.2`,
+  `3.18.4`, `3.18.5-alpha.2`) satisfy, and that `9.9.9` does not.
+- **Targeted unit test.** `node --import tsx --test tests/compatibility-metadata.test.ts`
+  → 5 tests, 5 pass, 0 fail, after `DSH_PEER_RANGE`, `DSH_ENGINES_RANGE`,
+  `DSH_ALPHA_HOSTS`, the rejection lists, and the vendor pins were updated. The
+  test file's contrast set still refuses `0.2.1-alpha.1`, `0.2.1-alpha.2`,
+  `0.2.0`, `0.2.1-rc.1`, `0.2.1`, `0.3.0`, and `1.0.0`, so the widening did not
+  turn into an open range.
+
+### Verification status
+
+- **C7 — real load on an isolated alpha.5 host: passed.** The same isolated
+  profile that was refused before the widening now composes and starts: no
+  `skipping profile bundle` warning (0 bytes on stderr, was 21 lines), the tree
+  contains `# == dsh-deeppilot` and the web-app patch, the host logs four
+  `[deeppilot]` lines, and `https://127.0.0.1:3098/phone/health` answers `200`
+  with `serverVersion` matching the tree under test. The run happened before the
+  version bump, so that field read `0.9.6`; the release tree differs from the tree
+  under test only in the declaration documents and the version fields. Port 3098 —
+  not DSH's web port — is the probe with discriminating power; see the note under
+  Current decision.
+- **The full check set for this tree (C5/C6): passed.** Clean `npm ci`, repo-wide
+  `npm test` (564 tests, 563 pass, 0 fail, 1 pre-existing TODO),
+  `npm run typecheck`, `npm run build` with a byte-identical regenerated `lib/`,
+  `npm run check:config-schema` against the pinned `0.2.0-rc.2` CLI, the Go helper
+  tests, and the six `bin/SHA256SUMS` entries.
+- **Release action completed — 0.9.7 published on 2026-10-17.** The annotated tag
+  `v0.9.7` points at `bf18755` on `main`; the publish workflow ran on that tag and
+  all of its steps passed, including the post-publish registry check whose retry
+  window this release widened. Registry `latest` reads `0.9.7` with provenance,
+  and a clean isolated profile installed `dsh-deeppilot@0.9.7` from npm, composed
+  it on a real `0.2.1-alpha.5` host, and answered `/phone/health` with `200` and
+  `serverVersion: "0.9.7"`.
+- **The declaration mirrors have drifted historically.** `README.md`,
+  `README.zh-CN.md`, `COMPATIBILITY.md`, and `AGENTS.md` all said "three
+  releases" while `package.json` already named four; that contradiction was
+  corrected in this pass. Any future widening must update all of them together —
+  the unit test only pins `package.json` and `package-lock.json`.
+
 ## 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
@@ -470,9 +778,10 @@ substitution the peer path performs, so any `workspace:` range there is unmet.
   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.
+  `0.2.1`, and `0.3.0` remain refused.
+  *(Historical: `0.2.1-alpha.5` was admitted the next day — see the audit of that
+  release above.)* 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
@@ -1435,3 +1744,30 @@ For every future DSH release, compare the new tag against the last audited tag,
 inspect the package/service surfaces actually imported by this repository,
 classify install/runtime/protocol risk separately, and append a dated decision
 here. Do not treat a release-note summary as proof of compatibility.
+
+Compare **whole package trees**, not just `lib/`. The rc.2 audit found its only
+non-`package.json` difference in `@deepseek-ai/dsh-web-app/cordis.patch.yml`, a
+file outside every `lib/` directory and the exact surface this plugin's own patch
+layer acts on; a `lib/`-only diff would have reported "no difference" and missed
+it. Take the published registry tarballs as the source of truth, enumerate the
+package set explicitly (peers, plus every package raw `dsh` dependencies add or
+remove, plus any peer that is not hoisted into the host tree), and only then read
+release notes.
+
+## 2026-10-15 — 移动端技能发现扩展
+
+新增可选的 `skills` 手机能力，使用官方 `sessionSkillCatalog.list({sessionId}, AbortSignal)` 服务，已对照本机 `0.2.0-rc.2` 和 `0.2.1-alpha.3` 发行声明。缺少服务只关闭该特性，晚挂载服务会重新探测，不缓存缺席。未修改宿主版本范围、鉴权、包版本或命令派发契约。手机只接收元数据，技能注册表和会话预设、工作目录变化触发目录失效。完整文档清单与四类差异表见《技能提示对接说明》。此源码改动尚未发布，真实主机与真机技能加载仍未验收。
+
+## 2026-10-16 — 移动端系统指令扩展
+
+1. 安装：本轮命令改动未调整依赖范围、包版本或发布状态。命令接口核对基于 `0.2.0-rc.2` 与 `0.2.1-alpha.3`；工作区并行的 `alpha.4` 兼容改动以其独立审计为准，不把本轮合成测试算作新版本真实业务验收。
+2. 运行：对照两版生成声明和实现，使用公开 `typertGateway.invoke` 的 `commands/list`、`commands/execute`、`fileUploads/upload`、`permissionPresets/catalog`、`sessionFeedback/record`；当前权限来自会话投影，日志复用官方共享 Fetch 归档路由。alpha.3 创建不参与审批的 owner Peer，rc.2 回退既有 operator。详情及上游全接口清单见[移动端命令对接说明](移动端命令对接说明.md)。
+3. 手机协议：v2 可选 `commands` 能力和五个新请求；读取使用 `sessions.read`，执行/反馈使用 `prompt.send`，小组件默认拒绝。旧手机忽略新字段，旧桥接不展示新增入口。导出分块不重放，接收方完整校验后分享。
+4. 验证：576 项测试通过、1 项原有待办；类型检查、构建和配置检查通过。新增逻辑为合成服务测试，未在两版真实 Host 会话执行系统指令，不据此声称运行验收或发布完成。
+
+## 2026-10-16 — 移动端目录缓存
+
+1. 安装与主机 API：本轮不改安装范围或依赖；读取沿用现有技能、命令和模型接口。工作区另有 alpha.4 兼容改动，命令对接已重新枚举该版 29 包、144 个接口，相关主机实现与 alpha.3 相同；不据此宣称真实业务验收。
+2. 手机协议：模型当前选择投影新增 `s2c.models.changed`，受 `sessions.read` 控制；原生权限执行可附加 `expectedDefinitionId`，重读目录核对来源，旧客户端字段缺省兼容。无新增周期轮询或第二层主机时间缓存。
+3. 客户端：内存五分钟、磁盘最长七天，重启旧目录先展示并校验，按配对身份/主机/会话隔离；当前模型、权限和执行结果不落盘。具体约定和格式重建见[移动端目录缓存](移动端目录缓存.md)。
+4. 验证：插件 577 项通过、1 项原有待办，类型检查、生成产物构建和使用本机固定版本的离线配置校验通过；两端缓存单元与模拟器证据见各自文档。未发布。