dsh-deeppilot 0.7.0 → 0.8.0

package/COMPATIBILITY.md

@@ -7,7 +7,7 @@ This file separates tested evidence from intended behavior. Passing unit tests d
 | Component | Baseline | Evidence |
 |---|---|---|
 | Node.js | 22 or newer | package engine and CI |
-| DSH CLI and Host API | the `0.1.5-rc.*` and `0.1.6-*`/`0.1.6` lines, `0.1.5-rc.1` minimum, for plugin `0.7.x` | plugin source typecheck, unit suite (240 tests) and `tsdown` build run against both the `0.1.5-rc.2` and the `0.1.6-alpha.1` package families; bridge and `/phone` protocol tests |
+| DSH CLI and Host API | the `0.1.5-rc.*` and `0.1.6-*`/`0.1.6` lines, `0.1.5-rc.1` minimum, for plugin `0.7.x` | plugin source typecheck, unit suite (265 tests) and `tsdown` build run against the `0.1.5-rc.2`, `0.1.6-alpha.1` and `0.1.6-alpha.2` package families; the `deeppilot/report` contribution registered through both the `0.1.6-alpha.1` and the `0.1.6-alpha.2` `TypertRegistry`; bridge and `/phone` protocol tests |
 | Host OS | macOS, Linux, Windows on packaged amd64/arm64 helper targets | helper checksums plus user-confirmed Windows/Linux Funnel launch and connection; local LAN validation remains part of alpha testing |
 | Remote access | Tailscale Funnel, ports 443/8443/10000 | helper and supervisor tests |
 | iOS | native DeepPilot client, protocol v2 | simulator build and v2 pairing/challenge evidence |
@@ -15,6 +15,7 @@ This file separates tested evidence from intended behavior. Passing unit tests d
 ## Protocol boundary
 
 - Protocol v2 is the only supported wire version. Existing protocol-v1 devices must pair again after upgrading.
+- The pairing QR now encodes a `deeppilot://pair` link, and the settings page shows that same string in one copy field. An app build that predates the link only parses the JSON payload, so it must be updated before pairing against this plugin; a link pasted into an older app is rejected instead of being half-applied. The current app still accepts the JSON payload.
 - Plugin `0.7.x` serves the LAN listener over self-signed TLS only; devices paired over LAN with `0.6.x` or older must pair again so the app receives the certificate fingerprint. The DSH web server no longer carries `/phone` compatibility routes. Funnel pairings are unaffected.
 - Bearer authentication, URL credentials, and first-frame shared tokens are rejected. A supported client registers a P-256 public key through `/phone/pair` and signs each WebSocket challenge.
 - Without a compatible embedded helper, the core bridge and trusted-LAN mode can still run; remote Funnel reports `unavailable`.
@@ -23,12 +24,18 @@ This file separates tested evidence from intended behavior. Passing unit tests d
   Older plugin versions used developer-preview DSH builds and remain historical
   artifacts.
 - The declared peer range is a disjunction,
-  `^0.1.5-rc.1 || >=0.1.6-alpha.1 <0.2.0-0`, because npm's prerelease rule only
+  `^0.1.5-rc.1 || >=0.1.6-alpha.1 <0.2.0-0 || >=0.1.7-alpha.1 <0.2.0-0`,
+  because npm's prerelease rule only
   lets a prerelease version satisfy a range whose comparators carry a
   prerelease on the same `major.minor.patch` tuple. Neither `^0.1.5-rc.1` nor
-  `>=0.1.5-rc.1` alone admits a `0.1.6` prerelease. `tests/compatibility-metadata.test.ts`
+  `>=0.1.5-rc.1` alone admits a `0.1.6` prerelease, and the `0.1.7-alpha.*`
+  line is likewise rejected by `>=0.1.6-alpha.1 <0.2.0-0` because no
+  comparator there carries a prerelease on the `0.1.7` tuple — every new
+  prerelease line needs its own disjunct.
+  `tests/compatibility-metadata.test.ts`
   asserts the range admits `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`,
-  `0.1.6-beta.1` and `0.1.6`, and rejects `0.2.0`.
+  `0.1.6-beta.1`, `0.1.6`, `0.1.7-alpha.1` and `0.1.7`,
+  and rejects `0.2.0`.
 - DSH `0.1.6-alpha.1` replaced `agent/session-start` with `agent/created`,
   deprecated the synchronous `snapshotEvents`/`eventAt`/`ownEvents` history
   readers, and renamed the PTC packages to the `ptc-runtime` family. The plugin
@@ -36,6 +43,62 @@ This file separates tested evidence from intended behavior. Passing unit tests d
   from the Cordis context (`sessionController`, `workspaceController`,
   `directoryPickerController`, `sessionProjections`) and the `session/event`
   and `api-session/*` events, all of which kept their `0.1.5-rc` shape.
+- DSH `0.1.6-alpha.2` changed the strict codec shape carried by an
+  `InvocationDescriptor`. Through `0.1.6-alpha.1` a descriptor published the
+  schema value itself and every consumer called `codec.schema.parse(value)`;
+  `alpha.2` instead validates a lazy `create()` factory at registration and the
+  Gateway parses through `codec.create().parse(value)`. A codec carrying only
+  `schema` is rejected by the `alpha.2` registry
+  (`typert: … strict codec has no create() factory`), which aborts plugin
+  activation. One `strictCodec()` helper in `src/report-wire.ts` emits both
+  keys — the same hand-written, dependency-free codec — so a single published
+  package registers and parses on either generation, and
+  `tests/report-wire.test.ts` pins both access paths.
+  The other `alpha.2` Typert change — a contributed schema's materialized
+  `schema` becoming a lazy `create()` factory — does not apply here: this
+  Remote contributes no schemas, which the same test asserts.
+- DSH `0.1.7-alpha.1` rewrote the settings subsystem: `installSection`,
+  `SettingsSectionHooks`, and the client `settingsScope` service are gone,
+  section values persist in this plugin own profile config entry, and the
+  settings UI refuses writes to fields the schema does not declare
+  `.volatile()`. The plugin adapts across both generations: `live()` in
+  `src/config.ts` feature-detects the volatile method and, on schemastery
+  3.18.2, writes the same metadata through `extra('volatile', true)` (an
+  unconditional `.volatile()` throws at import on ≤ 0.1.6 and kills
+  activation); volatile fields are exactly the ones the settings surface
+  writes (`enabled`, `local`, `remote`, plus read-time `debug`) while
+  `devicesPath`, `historyBufferMax`, and `push` keep remount-on-edit
+  semantics; `normalizeOptions` unwraps the `{ get() }`
+  references 0.1.7 carries in `apply()` options (a surviving reference fails
+  every plain-value comparison the bridge makes), the host re-runs its
+  transport reconciles on `loader/volatile-update`, and the client binds
+  `ctx.configForms.get('deeppilot')` through `src/client/settings-scope.ts`
+  when `settingsScope` is absent. Neither seam is declared in the client
+  entry's `inject`: a service name no running host provides keeps the whole
+  entry pending (`dsh-deeppilot: pending (waiting for service: settingsScope)`
+  on the first 0.1.7 boot), so both are awaited as optional injections, and
+  both are read through `ctx.get()` because a Cordis context proxy throws
+  `cannot get property "settingsScope" without inject` on an undeclared
+  service read; `tests/client-entry.test.ts` activates the real entry against
+  a Cordis context shaped like each generation and pins that audit. The same
+  release added
+  `session.projections`; the bridge feature-detects it via
+  `supportsProjections` and refreshes a session projection baseline on open,
+  while older hosts keep list-row projection hints. Plugin-manager display
+  metadata (`locale/*.json`, `package.json.icon`) and `--dump-config-schema`
+  are additive and inert on older hosts; `npm run check:config-schema`
+  projects this package Config through the pinned 0.1.7 CLI in CI and pins
+  the volatile annotations on the four live fields (devDependency floor:
+  `@deepseek-ai/schemastery` 3.18.3, which is also what a profile install
+  resolves through the `^3.18.2` peer range).
+- DSH `0.1.6-alpha.2` made runtime plugin removal real, through both the
+  Plugin Manager and the client entry reconciler. Every long-lived resource is
+  registered through `ctx.effect`, and the settings-page stylesheet stamps
+  `data-plugin="dsh-deeppilot"` so the module system's `removeOwnedStyles()`
+  can delete it; the module system only auto-claims styles present during
+  factory materialization, while this sheet is injected from `apply()`.
+  Without that stamp, disabling the plugin would leave its sheet styling the
+  page.
 - The compatibility facade converts the
   current Session controller's raw event arrays into the stable wrapped
   history entries consumed by the phone bridge. Sessions persisted by earlier
@@ -47,6 +110,9 @@ This file separates tested evidence from intended behavior. Passing unit tests d
 
 - Intel macOS support for the embedded helper;
 - signed/notarized helper distribution;
+- validation against the `0.1.7-*` package line: the peer range admits
+  `0.1.7-alpha.1` and later `0.1.7` releases, but typecheck, unit-suite, and
+  runtime evidence against those host packages have not been produced yet;
 - repair or migration of persisted history rejected by the Host's own session
   reader;
 - every DSH developer-preview revision;

package/README.md

@@ -38,16 +38,18 @@ does not require the helper.
 
 | Plugin version | Required DSH | How to install |
 |---|---|---|
-| `0.7.x` (current stable, `latest`) | DSH `0.1.5-rc.1` or newer | `dsh plugin --profile web add dsh-deeppilot` |
-| `0.6.x` (previous stable) | DSH `0.1.5-rc.1` or newer | `dsh plugin --profile web add dsh-deeppilot@0.6.2` |
-| `0.5.x` (legacy) | DSH `0.1.1-rc.2`–`0.1.2-alpha.1` | `dsh plugin --profile web add dsh-deeppilot@0.5.0` |
+| `0.8.x` (current stable, `latest`) | DSH `0.1.5-rc.1` or newer | `dsh plugin --profile web add dsh-deeppilot` |
+| `0.7.x` (previous stable) | DSH `0.1.5-rc.1` or newer | `dsh plugin --profile web add dsh-deeppilot@0.7.1` |
+| `0.6.x` (legacy) | DSH `0.1.5-rc.1` or newer | `dsh plugin --profile web add dsh-deeppilot@0.6.2` |
 
-`0.7.x` is built and typechecked against the DSH
+`0.8.x` is built and typechecked against the DSH
 [0.1.5-rc.1](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.5-rc.1)
-Host and client package family. It uses the Gateway multi-client Remote Events
-routing that keeps Web and DeepPilot independently answerable. Earlier plugin
-alphas remain historical artifacts; users installing the `alpha` tag for
-pre-release testing should update DSH to `0.1.5-rc.1` or newer.
+and [0.1.7-alpha.1](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.7-alpha.1)
+Host and client package families — the config-schema release check projects the
+plugin's Config through the pinned 0.1.7 CLI. It uses the Gateway multi-client
+Remote Events routing that keeps Web and DeepPilot independently answerable.
+Earlier plugin alphas remain historical artifacts; users installing the `alpha`
+tag for pre-release testing should update DSH to `0.1.5-rc.1` or newer.
 
 ```sh
 # DSH 0.1.5-rc.1 or newer (recommended):
@@ -58,8 +60,12 @@ dsh web
 ```
 
 After DSH restarts, open **Settings → DeepPilot**, enable the connection, show
-the pairing QR code, and scan it in the DeepPilot app. The same panel also
-shows a copyable pairing code for Simulator or manual entry.
+the pairing QR code, and scan it in the DeepPilot app. Below the QR code the same
+panel shows one copyable piece of pairing info (address, single-use code and
+certificate fingerprint) that can be pasted into the app in one step — useful for
+Simulator or when the camera is unavailable. Switching between the LAN and
+public address issues a matching new QR code and string immediately, with the
+panel staying open.
 
 LAN access is enabled by default on the plugin's independent TCP port `3098`
 and is TLS-only. The plugin generates a self-signed certificate on first start
@@ -88,15 +94,16 @@ DeepPilot state under `$DSH_HOME/deeppilot/`.
 
 ## Publishing (maintainers)
 
-`0.7.x` targets DSH `0.1.5-rc.1`+; `0.6.x` keeps the pre-TLS LAN transport for
-the same DSH family during the migration window, and `0.5.x` stays compatible
-with DSH `0.1.1-rc.2`–`0.1.2-alpha.1`. Keep them published:
+`0.8.x` targets DSH `0.1.5-rc.1`+ and adapts to the DSH 0.1.7 settings rewrite;
+`0.7.x` keeps the pre-0.1.7 settings API during the migration window, `0.6.x`
+keeps the pre-TLS LAN transport for the same DSH family, and `0.5.x` stays
+compatible with DSH `0.1.1-rc.2`–`0.1.2-alpha.1`. Keep them published:
 
 1. Bump `version` in `package.json` and in the root `""` entry of
    `package-lock.json`, then run `npm test && npm run typecheck && npm run build`
    and inspect `npm pack --dry-run --json` (the check
    `tests/compatibility-metadata.test.ts` enforces the peer range and asserts it
-   admits both the `0.1.5-rc.*` and the `0.1.6-*` lines).
+   admits the `0.1.5-rc.*`, the `0.1.6-*`, and the `0.1.7-*` lines).
 2. Commit the release and push it. `npm publish` runs `prepack` (build) and
    `prepublishOnly` (test + typecheck) automatically.
 3. Publish pre-releases without touching `latest`:
@@ -106,7 +113,7 @@ with DSH `0.1.1-rc.2`–`0.1.2-alpha.1`. Keep them published:
    ```
 
    After a successful publish, `npm view dsh-deeppilot dist-tags --json` shows
-   `"latest": "0.7.x"` and `"alpha": "0.7.x-alpha.y"`. Verify the published
+   `"latest": "0.8.x"` and `"alpha": "0.8.x-alpha.y"`. Verify the published
    package by installing it into a DSH `0.1.5-rc.1` profile before pointing
    users at it.
 4. Tag the release commit `vX.Y.Z` and prepare a GitHub Release

package/README.zh-CN.md

@@ -35,13 +35,15 @@
 
 | 插件版本 | 所需 DSH | 安装命令 |
 |---|---|---|
-| `0.7.x`（当前稳定版，`latest`） | DSH `0.1.5-rc.1` 或更高 | `dsh plugin --profile web add dsh-deeppilot` |
-| `0.6.x`（旧版稳定版） | DSH `0.1.5-rc.1` 或更高 | `dsh plugin --profile web add dsh-deeppilot@0.6.2` |
-| `0.5.x`（历史版本） | DSH `0.1.1-rc.2`–`0.1.2-alpha.1` | `dsh plugin --profile web add dsh-deeppilot@0.5.0` |
+| `0.8.x`（当前稳定版，`latest`） | DSH `0.1.5-rc.1` 或更高 | `dsh plugin --profile web add dsh-deeppilot` |
+| `0.7.x`（旧版稳定版） | DSH `0.1.5-rc.1` 或更高 | `dsh plugin --profile web add dsh-deeppilot@0.7.1` |
+| `0.6.x`（历史版本） | DSH `0.1.5-rc.1` 或更高 | `dsh plugin --profile web add dsh-deeppilot@0.6.2` |
 
-`0.7.x` 基于 DSH
+`0.8.x` 基于 DSH
 [0.1.5-rc.1](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.5-rc.1)
-的 Host 与 client 包族构建并完成类型检查。它使用 Gateway 多 Client Remote Events
+与 [0.1.7-alpha.1](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.7-alpha.1)
+的 Host 与 client 包族构建并完成类型检查 —— 发布前的 config-schema 检查会通过
+固定的 0.1.7 CLI 投影本插件的 Config。它使用 Gateway 多 Client Remote Events
 路由，使 Web 与 DeepPilot 能独立处理同一交互。旧 alpha 仅保留为历史产物；安装
 `alpha` tag 进行预发布测试的用户应先把 DSH 更新到 `0.1.5-rc.1` 或更高版本。
 
@@ -54,7 +56,9 @@ dsh web
 ```
 
 DSH 重启后，打开 **设置 → DeepPilot**，启用连接并显示配对二维码，然后在
-DeepPilot App 中扫码。同一面板也会显示可复制的配对码，供模拟器或手动输入使用。
+DeepPilot App 中扫码。二维码下方同时显示一段可复制的「配对信息」（含地址、一次性配对码
+与证书指纹），在 App 里粘贴一次即可完成配对，适合模拟器或相机不可用时使用；在「内网 /
+公网」之间切换会立即为所选地址生成新的二维码与配对信息，面板保持展开。
 
 局域网连接默认使用插件独立的 TCP `3098` 端口，且只提供 TLS。插件首次启动时生成
 自签证书（私钥位于 `$DSH_HOME/deeppilot/lan-tls/`），配对二维码携带其公钥指纹，
@@ -78,14 +82,14 @@ dsh plugin --profile web remove dsh-deeppilot
 
 ## 发布说明（维护者）
 
-`0.7.x` 面向 DSH `0.1.5-rc.1`+；`0.6.x` 在同一 DSH 版本族上保留 TLS 化之前的
-局域网传输，供迁移期使用；`0.5.x` 保持兼容 DSH
-`0.1.1-rc.2`–`0.1.2-alpha.1`，各版本线都要保持发布：
+`0.8.x` 面向 DSH `0.1.5-rc.1`+ 并适配 DSH 0.1.7 的设置系统重写；迁移期内
+`0.7.x` 保留 0.1.7 之前的设置 API，`0.6.x` 在同一 DSH 版本族上保留 TLS 化之前的
+局域网传输，`0.5.x` 保持兼容 DSH `0.1.1-rc.2`–`0.1.2-alpha.1`，各版本线都要保持发布：
 
 1. 同步修改 `package.json` 与 `package-lock.json` 根 `""` 条目中的
    `version`，然后运行 `npm test && npm run typecheck && npm run build`，
    并检查 `npm pack --dry-run --json`（`tests/compatibility-metadata.test.ts`
-   会强制校验 peer 范围，并断言它同时接纳 `0.1.5-rc.*` 与 `0.1.6-*` 两条线）。
+   会强制校验 peer 范围，并断言它同时接纳 `0.1.5-rc.*`、`0.1.6-*` 与 `0.1.7-*` 三条线）。
 2. 提交发布并推送。`npm publish` 会自动执行 `prepack`（构建）与
    `prepublishOnly`（测试 + 类型检查）。
 3. 发布预发布版本，不要动 `latest`：
@@ -95,7 +99,7 @@ dsh plugin --profile web remove dsh-deeppilot
    ```
 
    发布成功后，`npm view dsh-deeppilot dist-tags --json` 应显示
-   `"latest": "0.7.x"` 与 `"alpha": "0.7.x-alpha.y"`。向用户推荐前，请先在
+   `"latest": "0.8.x"` 与 `"alpha": "0.8.x-alpha.y"`。向用户推荐前，请先在
    DSH `0.1.5-rc.1` profile 中安装验证发布的包。
 4. 为发布提交打 `vX.Y.Z` tag，并准备包含英文与简体中文说明的
    GitHub Release，链接本 README 的发布说明。

package/icon.svg

@@ -0,0 +1,13 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 128 128" role="img" aria-label="DeepPilot">
+  <defs>
+    <linearGradient id="dp-bg" x1="0" y1="0" x2="128" y2="128" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#2563eb"/>
+      <stop offset="1" stop-color="#0c1b4a"/>
+    </linearGradient>
+  </defs>
+  <rect width="128" height="128" rx="28" fill="url(#dp-bg)"/>
+  <g transform="translate(24 24) scale(3.5)" fill="none" stroke="#ffffff" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
+    <path d="m22 2-7 20-4-9-9-4Z"/>
+    <path d="M22 2 11 13"/>
+  </g>
+</svg>