dsh-deeppilot 0.8.0 → 0.8.2

package/COMPATIBILITY.md

@@ -1,122 +1,29 @@
 # Compatibility
 
-This file separates tested evidence from intended behavior. Passing unit tests does not prove every DSH build, network, Mac, or iPhone combination.
+This branch targets **DSH 0.1.7-rc.1**. The DSH peer dependencies and the development packages are pinned to that exact release. Earlier DSH builds and later release candidates are outside this branch's support scope.
 
-## Public-beta baseline
-
-| Component | Baseline | Evidence |
+| Component | Current contract | 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 (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 |
+| Node.js | 22 or newer | Package engine and CI |
+| DSH CLI and Host API | `0.1.7-rc.1` | Peer metadata, source typecheck, unit tests, bundle build, and config schema projection against rc.1 |
+| 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 |
+
+## DSH interfaces used here
 
-## Protocol boundary
+- The Host adapter uses Session and Workspace controllers, Gateway Remote Events, and `typertGateway.wireStream.open(endpoint, payload, uplink, peer, signal)`. Its in-process carrier passes `undefined` for `uplink` and `peer` and the cancellation signal in argument five.
+- The resident Client sends relative RPC paths such as `api/$events/result`. The in-process transport resolves those paths to a local URL before constructing a Node `Request`; the shared Fetch handler dispatches it without a network request. This is required for iOS approval and question answers to settle at the Gateway.
+- The client settings page binds `configForms.get('deeppilot')` when the service becomes available. The Host reads volatile config references from its profile entry and reconciles transports on `loader/volatile-update`.
+- Typert strict codecs publish `create()` factories. Session opening reads `session.projections` for a complete baseline.
+- The Host adapter retains a stable bridge-facing API so the phone protocol does not depend directly on DSH controller shapes. This adapter is an internal design boundary, not support for an older DSH Host.
 
-- 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`.
-- If a DSH Host API is missing, only the dependent capability should be disabled. The plugin must not crash the Host.
-- Plugin `0.7.x` requires DSH `0.1.5-rc.1` or newer within the `0.1.x` line.
-  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 || >=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, 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`, `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
-  uses none of those surfaces: every host dependency is resolved structurally
-  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
-  Hosts can therefore be listed and opened when the rc.1 Host's own
-  persistence reader accepts their log vocabulary. Unsupported persisted
-  formats still fail closed in the Host without modifying the original log.
+## Separate protocol and data boundaries
 
-## Not yet claimed
+- Protocol v2 is the only supported phone wire version. Protocol-v1 devices must pair again. The LAN listener uses its own TLS identity and certificate pinning; old LAN pairings without a fingerprint must also pair again.
+- The current app accepts the `deeppilot://pair` link and the JSON pairing payload. Bearer authentication, URL credentials, and first-frame shared tokens are rejected; devices register a P-256 public key and sign each WebSocket challenge.
+- The plugin's persisted device and Funnel state migration remains separate from DSH API version support. Session logs written by earlier DSH builds are readable only when the rc.1 Host's own history reader accepts them; this plugin does not rewrite those logs.
+- An unavailable optional OS facility, transport, or controller disables its dependent capability without crashing the Host.
 
-- 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;
-- physical-device performance and every carrier/network combination;
-- production APNs delivery without a real provider credential and device.
+## Evidence limits
 
-When reporting an issue, include `node --version`, the exact DSH package version, plugin commit/tag, macOS version and architecture, connection mode, and sanitized status output. Never include pairing codes, key material, APNs tokens, or message content.
+Unit tests and config schema projection do not prove every network, Mac, Linux, Windows, or iPhone combination. In particular, physical-device performance, signed helper distribution, and production APNs delivery need their own checks. Include the exact DSH version, plugin commit, Node version, OS, connection mode, and sanitized status output when reporting a compatibility issue; never include credentials or message content.

package/README.md

@@ -32,30 +32,16 @@ Host on your own Mac and does not replace or modify the DSH Web UI.
 
 ## Install from npm
 
-Requirements: Node.js 22+ and DSH with a `web` profile. The package includes
+This source checkout targets Node.js 22+ and **DSH 0.1.7-rc.1** with a `web` profile. The package includes
 Funnel helpers for macOS, Linux, and Windows on amd64/arm64; trusted-LAN mode
 does not require the helper.
 
-| Plugin version | Required DSH | How to install |
-|---|---|---|
-| `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.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)
-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.
+The current working tree pins its DSH packages and compatibility checks to
+`0.1.7-rc.1`. A previously published plugin package may still carry its own
+older compatibility declaration until a release is made from this tree.
 
 ```sh
-# DSH 0.1.5-rc.1 or newer (recommended):
 dsh plugin --profile web add dsh-deeppilot
-# DSH 0.1.1-rc.2 through 0.1.2-alpha.1 (previous stable):
-dsh plugin --profile web add dsh-deeppilot@0.5.0
 dsh web
 ```
 
@@ -94,16 +80,12 @@ DeepPilot state under `$DSH_HOME/deeppilot/`.
 
 ## Publishing (maintainers)
 
-`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:
+Release from this branch only after validating against DSH `0.1.7-rc.1`:
 
 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 the `0.1.5-rc.*`, the `0.1.6-*`, and the `0.1.7-*` lines).
+   and inspect `npm pack --dry-run --json`. The compatibility metadata test
+   enforces the exact rc.1 peer and development dependency versions.
 2. Commit the release and push it. `npm publish` runs `prepack` (build) and
    `prepublishOnly` (test + typecheck) automatically.
 3. Publish pre-releases without touching `latest`:
@@ -112,10 +94,8 @@ compatible with DSH `0.1.1-rc.2`–`0.1.2-alpha.1`. Keep them published:
    npm publish --tag alpha
    ```
 
-   After a successful publish, `npm view dsh-deeppilot dist-tags --json` shows
-   `"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.
+   After a successful publish, verify the dist tag and install the package in
+   a DSH `0.1.7-rc.1` profile before pointing users at it.
 4. Tag the release commit `vX.Y.Z` and prepare a GitHub Release
    (English + 简体中文 notes) that links this README section.
 5. Publish stable releases with `npm publish --tag latest`, which moves

package/README.zh-CN.md

@@ -30,28 +30,14 @@
 
 ## 从 npm 安装
 
-需要 Node.js 22+ 和带 `web` profile 的 DSH。npm 包内置 macOS、Linux、Windows
+当前源码仅面向 Node.js 22+ 与带 `web` profile 的 **DSH 0.1.7-rc.1**。npm 包内置 macOS、Linux、Windows
 的 amd64/arm64 Funnel helper；可信局域网模式不依赖 helper。
 
-| 插件版本 | 所需 DSH | 安装命令 |
-|---|---|---|
-| `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.8.x` 基于 DSH
-[0.1.5-rc.1](https://www.npmjs.com/package/@deepseek-ai/dsh/v/0.1.5-rc.1)
-与 [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` 或更高版本。
+当前工作树的 DSH 包和兼容性检查均固定为 `0.1.7-rc.1`。从此工作树发布新版本前，
+已发布的旧插件包仍可能带有各自的旧兼容声明。
 
 ```sh
-# DSH 0.1.5-rc.1 或更高（推荐）：
 dsh plugin --profile web add dsh-deeppilot
-# DSH 0.1.1-rc.2 至 0.1.2-alpha.1（旧版稳定）：
-dsh plugin --profile web add dsh-deeppilot@0.5.0
 dsh web
 ```
 
@@ -82,14 +68,12 @@ dsh plugin --profile web remove dsh-deeppilot
 
 ## 发布说明（维护者）
 
-`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`，各版本线都要保持发布：
+此分支仅在 DSH `0.1.7-rc.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-*` 与 `0.1.7-*` 三条线）。
+   并检查 `npm pack --dry-run --json`。兼容性元数据测试会校验 peer 与开发依赖
+   均固定为 rc.1。
 2. 提交发布并推送。`npm publish` 会自动执行 `prepack`（构建）与
    `prepublishOnly`（测试 + 类型检查）。
 3. 发布预发布版本，不要动 `latest`：
@@ -98,9 +82,7 @@ dsh plugin --profile web remove dsh-deeppilot
    npm publish --tag alpha
    ```
 
-   发布成功后，`npm view dsh-deeppilot dist-tags --json` 应显示
-   `"latest": "0.8.x"` 与 `"alpha": "0.8.x-alpha.y"`。向用户推荐前，请先在
-   DSH `0.1.5-rc.1` profile 中安装验证发布的包。
+   发布成功后检查 dist tag，并在 DSH `0.1.7-rc.1` profile 中安装验证发布的包。
 4. 为发布提交打 `vX.Y.Z` tag，并准备包含英文与简体中文说明的
    GitHub Release，链接本 README 的发布说明。
 5. 稳定版用 `npm publish --tag latest` 发布，使 `latest` 切换到新版本。

package/icon.svg

@@ -1,13 +1,12 @@
 <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 id="dp-glyph" x1="0" y1="-18.1112" x2="0" y2="52.2563" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#404040"/>
+      <stop offset="1" stop-color="#000000"/>
     </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"/>
+  <rect width="128" height="128" fill="#ffffff"/>
+  <g transform="translate(17.5525 17.0725) scale(3.950123)">
+    <path fill="url(#dp-glyph)" fill-rule="evenodd" d="M23.748 4.482c-.254-.124-.364.113-.512.234-.051.039-.094.09-.137.136-.372.397-.806.657-1.373.626-.829-.046-1.537.214-2.163.848-.133-.782-.575-1.248-1.247-1.548-.352-.156-.708-.311-.955-.65-.172-.241-.219-.51-.305-.774-.055-.16-.11-.323-.293-.35-.2-.031-.278.136-.356.276-.313.572-.434 1.202-.422 1.84.027 1.436.633 2.58 1.838 3.393.137.093.172.187.129.323-.082.28-.18.552-.266.833-.055.179-.137.217-.329.14a5.526 5.526 0 01-1.736-1.18c-.857-.828-1.631-1.742-2.597-2.458a11.365 11.365 0 00-.689-.471c-.985-.957.13-1.743.388-1.836.27-.098.093-.432-.779-.428-.872.004-1.67.295-2.687.684a3.055 3.055 0 01-.465.137 9.597 9.597 0 00-2.883-.102c-1.885.21-3.39 1.102-4.497 2.623C.082 8.606-.231 10.684.152 12.85c.403 2.284 1.569 4.175 3.36 5.653 1.858 1.533 3.997 2.284 6.438 2.14 1.482-.085 3.133-.284 4.994-1.86.47.234.962.327 1.78.397.63.059 1.236-.03 1.705-.128.735-.156.684-.837.419-.961-2.155-1.004-1.682-.595-2.113-.926 1.096-1.296 2.746-2.642 3.392-7.003.05-.347.007-.565 0-.845-.004-.17.035-.237.23-.256a4.173 4.173 0 001.545-.475c1.396-.763 1.96-2.015 2.093-3.517.02-.23-.004-.467-.247-.588zM11.581 18c-2.089-1.642-3.102-2.183-3.52-2.16-.392.024-.321.471-.235.763.09.288.207.486.371.739.114.167.192.416-.113.603-.673.416-1.842-.14-1.897-.167-1.361-.802-2.5-1.86-3.301-3.307-.774-1.393-1.224-2.887-1.298-4.482-.02-.386.093-.522.477-.592a4.696 4.696 0 011.529-.039c2.132.312 3.946 1.265 5.468 2.774.868.86 1.525 1.887 2.202 2.891.72 1.066 1.494 2.082 2.48 2.914.348.292.625.514.891.677-.802.09-2.14.11-3.054-.614zm1-6.44a.306.306 0 01.415-.287.302.302 0 01.2.288.306.306 0 01-.31.307.303.303 0 01-.304-.308zm3.11 1.596c-.2.081-.399.151-.59.16a1.245 1.245 0 01-.798-.254c-.274-.23-.47-.358-.552-.758a1.73 1.73 0 01.016-.588c.07-.327-.008-.537-.239-.727-.187-.156-.426-.199-.688-.199a.559.559 0 01-.254-.078c-.11-.054-.2-.19-.114-.358.028-.054.16-.186.192-.21.356-.202.767-.136 1.146.016.352.144.618.408 1.001.782.391.451.462.576.685.914.176.265.336.537.445.848.067.195-.019.354-.25.452z"/>
   </g>
 </svg>

package/lib/client.js

@@ -290,28 +290,11 @@ window.__ModuleLoader__.load({
 			if (typeof value !== "boolean") reject("boolean");
 			return value;
 		} };
-		/**
-		* One strict boundary codec carrying both generation shapes of the supported
-		* `0.1.x` host family.
-		*
-		* Through `0.1.6-alpha.1` a descriptor published the schema value itself and
-		* every consumer parsed through `codec.schema.parse(value)`. `0.1.6-alpha.2`
-		* switched to a lazily materialized process-realm factory: `TypertRegistry`
-		* now rejects a strict codec without `create()`, and the Gateway parses
-		* through `codec.create().parse(value)`.
-		*
-		* Publishing both keys — `create()` returning the same hand-written,
-		* dependency-free codec — keeps one package valid across the entire declared
-		* peer range instead of forking the wire contract per host generation. The
-		* cast is required because each generation's `TypertCodec` declares only its
-		* own key, so a fresh object literal carrying both fails excess-property
-		* checking against either one.
-		*/
+		/** The rc.1 Gateway materializes each strict codec through `create()`. */
 		function strictCodec(typeSymbol, schema) {
 			return {
 				mode: "strict",
 				typeSymbol,
-				schema,
 				create: () => schema
 			};
 		}
@@ -579,7 +562,7 @@ window.__ModuleLoader__.load({
 				"diag.mountFailed": "报告远程未挂载（remote mount 失败）— 请确认宿主包含 typert 组合",
 				"diag.mountFailedShort": "remote mount 失败: ",
 				"diag.callFailed": "report remote 调用失败",
-				"diag.settingsUnavailable": "设置命名空间不可用（settingsScope 未提供）",
+				"diag.settingsUnavailable": "设置表单不可用（configForms 未提供）",
 				"diag.missingReportHook": "useDeepPilotReport hook 缺失",
 				"diag.missingEnabledHook": "useDeepPilotEnabled hook 缺失",
 				"diag.missingLocalEnabledHook": "useDeepPilotLocalEnabled hook 缺失",
@@ -762,7 +745,7 @@ window.__ModuleLoader__.load({
 				"diag.mountFailed": "Report remote not mounted (mount failed) — confirm the host includes the typert composition",
 				"diag.mountFailedShort": "remote mount failed: ",
 				"diag.callFailed": "report remote call failed",
-				"diag.settingsUnavailable": "Settings namespace unavailable (settingsScope not provided)",
+				"diag.settingsUnavailable": "Settings form unavailable (configForms not provided)",
 				"diag.missingReportHook": "useDeepPilotReport hook missing",
 				"diag.missingEnabledHook": "useDeepPilotEnabled hook missing",
 				"diag.missingLocalEnabledHook": "useDeepPilotLocalEnabled hook missing",
@@ -949,8 +932,8 @@ window.__ModuleLoader__.load({
 		* materialization; this sheet is injected from `apply()`, which runs after
 		* that point, so it would never be attributed to us. Stamping `data-plugin`
 		* ourselves lets the module system's `removeOwnedStyles(id)` delete the sheet
-		* when the plugin is unloaded at runtime — the Plugin Manager and the client
-		* entry reconciler both support live removal from 0.1.6-alpha.2 on, and an
+		* when the plugin is unloaded at runtime — the rc.1 Plugin Manager and client
+		* entry reconciler both support live removal, and an
 		* orphaned sheet would otherwise keep styling a page we no longer own.
 		*/
 		function injectCss() {
@@ -4064,19 +4047,12 @@ window.__ModuleLoader__.load({
 			}, translateWith(props.t, "update.badge")) : null), diag.length > 0 ? (0, react.createElement)("p", { className: "pbb-diag" + (failed ? " pbb-diagBad" : "") }, translateWith(props.t, "diag.prefix") + diag.join(" | ")) : null);
 		}
 		//#endregion
-		//#region src/client/settings-scope.ts
-		/** Read one optional settings seam without an inject declaration on this entry. */
-		function readSeam(ctx, name) {
-			if (typeof ctx.get === "function") return ctx.get(name) ?? void 0;
-			return ctx[name];
-		}
+		//#region src/client/config-form.ts
 		/**
 		* Deep-unwrap live-update references in a snapshot section.
 		*
-		* If a host parses section values through a volatile-capable schema, leaves
-		* can arrive as `{ get() }` references; the settings page compares plain
-		* values, so unwrap defensively at this single boundary regardless of which
-		* schemastery instance produced the snapshot.
+		* Volatile fields can arrive as `{ get() }` references. The settings page
+		* compares plain values, so unwrap them at this boundary.
 		*/
 		function plainSection(value) {
 			if (value === null || typeof value !== "object") return value;
@@ -4086,7 +4062,7 @@ window.__ModuleLoader__.load({
 			return plain;
 		}
 		/**
-		* Adapt one 0.1.7 config form to the settings-scope face.
+		* Adapt one config form to the settings page's local contract.
 		*
 		* The form resolves writes as `Promise<boolean>` (false = the Host rejected or
 		* could not recover the write) where the scope face signals failure by
@@ -4094,7 +4070,7 @@ window.__ModuleLoader__.load({
 		* a `false` must be translated into one.
 		*
 		* @param forms - the 0.1.7 configForms service, if the host provides it.
-		* @param entryId - profile entry id; identical to the legacy namespace here.
+		* @param entryId - profile entry id.
 		* @returns the adapted scope, or undefined when the service cannot resolve it.
 		*/
 		function adaptConfigForm(forms, entryId) {
@@ -4118,18 +4094,11 @@ window.__ModuleLoader__.load({
 			};
 		}
 		/**
-		* Bind the settings scope for whichever host generation is running.
-		*
-		* Prefers the legacy settingsScope (present ≤ 0.1.6); falls back to the 0.1.7
-		* config form when its service is already provisioned. Safe to call from any
-		* context — including one that declares neither service, which on a Cordis
-		* context is the difference between `undefined` and a thrown
-		* `cannot get property "settingsScope" without inject`. Callers that apply
-		* before `configForms` is provided re-run this inside the optional
-		* `ctx.inject(['configForms'], …)` callback (see client index.ts).
+		* Bind the rc.1 form if its service is already provisioned. Callers that
+		* apply first retry inside `ctx.inject(['configForms'], …)`.
 		*/
-		function bindSettingsScope(ctx) {
-			return readSeam(ctx, "settingsScope")?.bind({ namespace: "deeppilot" }) ?? adaptConfigForm(readSeam(ctx, "configForms"), "deeppilot");
+		function bindConfigForm(ctx) {
+			return adaptConfigForm(ctx.get("configForms"), "deeppilot");
 		}
 		//#endregion
 		//#region src/client/index.ts
@@ -4187,13 +4156,9 @@ window.__ModuleLoader__.load({
 		/**
 		* Services this client entry cannot start without.
 		*
-		* The settings seam is deliberately NOT here: DSH ≤ 0.1.6 provides
-		* `settingsScope`, 0.1.7 removed it in favor of `configForms`, and a name no
-		* running host provides keeps the whole entry pending forever — the 0.1.7 boot
-		* reported exactly `dsh-deeppilot: pending (waiting for service:
-		* settingsScope)` while every other service resolved and the entry never
-		* applied. Both settings seams are optional injections inside `apply`
-		* instead; see the scope binding below.
+		* `configForms` is provided by the settings-page fiber, which may activate
+		* after this entry. It is attached through an optional injection below so
+		* the entry can activate before the settings page does.
 		*/
 		const inject = [
 			"slots",
@@ -4274,9 +4239,9 @@ window.__ModuleLoader__.load({
 				status: "loading",
 				enabled: true
 			});
-			let scope = bindSettingsScope(anyCtx);
-			/** Adopters registered before attachScope runs, so a late-bound scope (0.1.7
-			*  configForms provisioned after this plugin applies) still subscribes all. */
+			let scope = bindConfigForm(anyCtx);
+			/** Adopters registered before attachScope runs, so a late-bound config form
+			*  still subscribes all. */
 			const scopeAdoptions = [];
 			const adoptEnabled = () => {
 				if (scope === void 0) return;
@@ -4450,12 +4415,9 @@ window.__ModuleLoader__.load({
 			if (scope === void 0) {
 				const bindScopeFrom = (sub) => {
 					if (scope !== void 0) return;
-					scope = bindSettingsScope(sub);
+					scope = bindConfigForm(sub);
 					attachScope();
 				};
-				ctx.inject(["settingsScope"], (sub) => {
-					bindScopeFrom(sub);
-				});
 				ctx.inject(["configForms"], (sub) => {
 					bindScopeFrom(sub);
 				});