dsh-deeppilot 0.7.1 → 0.8.1

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 (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 |
+| 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 (301 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 |
@@ -24,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
@@ -51,6 +57,69 @@ This file separates tested evidence from intended behavior. Passing unit tests d
   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` reordered the Host `typertGateway.wireStream.open`
+  parameters from `(endpoint, payload, signal)` to
+  `(endpoint, payload, uplink, peer, signal)`. The reorder is not additive: a
+  3-argument call lands the `AbortSignal` in the `uplink` slot, leaves `signal`
+  undefined, and the Host fails every stream inside
+  `AbortSignal.any([signal, …])` with
+  `TypeError [ERR_INVALID_ARG_TYPE]: The "signals[0]" argument must be an
+  instance of AbortSignal`. The resident Client's Connection treats that dead
+  generation as a lost connection and prints an endless
+  `[connection] connection lost, retry #N` loop with exponential backoff while
+  the phone's approval and question round-trips stay broken.
+  `openHostStream()` in `src/dsh012-remote-interactions.ts` selects the
+  contract from the published arity (`open.length`) and passes `undefined` for
+  both `uplink` and `peer` on 0.1.7 — the documented "operator's in-process
+  carrier" case, since DeepPilot's carrier owns the Host in process and has no
+  Client-to-Host uplink. `tests/dsh012-wire-stream-contract.test.ts` pins the
+  argument binding for a 3-arity and a 5-arity Host, and asserts the signal
+  lands in each contract's declared slot.
+- 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).
+- `icon.svg` is a vector recreation of the iOS app icon, built from the
+  private app's own Icon Composer sources (`ios/DeepPilot.icon/icon.json`
+  plus `Assets/deepseek.svg`) and the in-app composition its
+  `AppIconArtwork` applies: a white field, the DeepSeek brand glyph fitted
+  with 13% padding, and a `Color(white: 0.25)` → black vertical gradient.
+  The app's `.icon` bundle is not distributable through npm — the host
+  inlines a single relative SVG, PNG, JPEG, or WebP file under 256 KiB as a
+  `data:` URI — so the recreation is the only way to keep the two icons
+  visually identical. `tests/package-meta.test.ts` pins the host's reader
+  rules; regenerate the SVG from the app sources whenever the app icon
+  changes.
 - 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
@@ -70,6 +139,12 @@ 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, and the `wireStream.open`
+  reorder that release introduced is adapted and pinned by
+  `tests/dsh012-wire-stream-contract.test.ts`, but the unit suite still runs
+  against the `0.1.5-rc.1`/`0.1.6-*` package families and no `0.1.7`
+  typecheck or full-suite evidence has 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):
@@ -92,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`:
@@ -110,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` 或更高版本。
 
@@ -80,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`：
@@ -97,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,12 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 128 128" role="img" aria-label="DeepPilot">
+  <defs>
+    <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" 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

@@ -4064,6 +4064,74 @@ 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];
+		}
+		/**
+		* 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.
+		*/
+		function plainSection(value) {
+			if (value === null || typeof value !== "object") return value;
+			if (typeof value.get === "function") return plainSection(value.get());
+			const plain = {};
+			for (const [key, item] of Object.entries(value)) plain[key] = item !== null && typeof item === "object" ? plainSection(item) : item;
+			return plain;
+		}
+		/**
+		* Adapt one 0.1.7 config form to the settings-scope face.
+		*
+		* The form resolves writes as `Promise<boolean>` (false = the Host rejected or
+		* could not recover the write) where the scope face signals failure by
+		* rejecting — the page's optimistic-write rollback only runs on rejection, so
+		* 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.
+		* @returns the adapted scope, or undefined when the service cannot resolve it.
+		*/
+		function adaptConfigForm(forms, entryId) {
+			const form = forms?.get?.(entryId);
+			if (form === void 0) return void 0;
+			const accept = async (pending) => {
+				if (!await pending) throw new Error("host rejected the settings write");
+			};
+			return {
+				getSnapshot: () => {
+					const snapshot = form.getSnapshot();
+					return {
+						status: snapshot.status,
+						value: plainSection(snapshot.value),
+						writable: snapshot.writable
+					};
+				},
+				subscribe: (listener) => form.subscribe(listener),
+				set: (field, value) => accept(form.set(field, value)),
+				unset: (field) => accept(form.unset(field))
+			};
+		}
+		/**
+		* 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).
+		*/
+		function bindSettingsScope(ctx) {
+			return readSeam(ctx, "settingsScope")?.bind({ namespace: "deeppilot" }) ?? adaptConfigForm(readSeam(ctx, "configForms"), "deeppilot");
+		}
+		//#endregion
 		//#region src/client/index.ts
 		/** Polls the report remote and owns the page state transitions. */
 		var ReportController = class {
@@ -4116,11 +4184,21 @@ window.__ModuleLoader__.load({
 				} catch {}
 			}
 		};
+		/**
+		* 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.
+		*/
 		const inject = [
 			"slots",
 			"locale",
-			"remote",
-			"settingsScope"
+			"remote"
 		];
 		function apply(ctx) {
 			if (typeof document !== "undefined") injectCss();
@@ -4196,7 +4274,10 @@ window.__ModuleLoader__.load({
 				status: "loading",
 				enabled: true
 			});
-			const scope = anyCtx.settingsScope?.bind({ namespace: "deeppilot" });
+			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. */
+			const scopeAdoptions = [];
 			const adoptEnabled = () => {
 				if (scope === void 0) return;
 				const snap = scope.getSnapshot();
@@ -4209,10 +4290,7 @@ window.__ModuleLoader__.load({
 					enabled: true
 				});
 			};
-			if (scope !== void 0) {
-				scope.subscribe(adoptEnabled);
-				adoptEnabled();
-			}
+			scopeAdoptions.push(adoptEnabled);
 			const lastConfirmedEnabled = () => {
 				const snap = scope?.getSnapshot();
 				if (snap?.status === "ready" && snap.value !== void 0) return snap.value.enabled !== false;
@@ -4285,10 +4363,7 @@ window.__ModuleLoader__.load({
 					});
 				}
 			};
-			if (scope !== void 0) {
-				scope.subscribe(adoptLocal);
-				adoptLocal();
-			}
+			scopeAdoptions.push(adoptLocal);
 			const setDeepPilotLocalEnabled = (value) => {
 				const previous = lastConfirmedLocalEnabled();
 				localEnabledStore.set({
@@ -4363,9 +4438,27 @@ window.__ModuleLoader__.load({
 					});
 				}
 			};
-			if (scope !== void 0) {
-				scope.subscribe(adoptRemoteEnabled);
-				adoptRemoteEnabled();
+			scopeAdoptions.push(adoptRemoteEnabled);
+			const attachScope = () => {
+				if (scope === void 0) return;
+				for (const adopt of scopeAdoptions) {
+					scope.subscribe(adopt);
+					adopt();
+				}
+			};
+			attachScope();
+			if (scope === void 0) {
+				const bindScopeFrom = (sub) => {
+					if (scope !== void 0) return;
+					scope = bindSettingsScope(sub);
+					attachScope();
+				};
+				ctx.inject(["settingsScope"], (sub) => {
+					bindScopeFrom(sub);
+				});
+				ctx.inject(["configForms"], (sub) => {
+					bindScopeFrom(sub);
+				});
 			}
 			const setDeepPilotRemoteEnabled = (value) => {
 				const previous = lastConfirmedRemoteEnabled();