@crazx/dsh-client-test-runtime 0.1.5-rc.2.zw.1 → 0.1.6-alpha.1.zw.2

package/README.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write packages/test-support/client-runtime/README.md
-README.md: 0b6caf7237520ca1a10fe0bbdf3c12c6d793461f
-README.zh.md: ce78a0ad623247ad769e0ea91895daa1db8e7f1b
+README.md: 014bcbf8bc0ed9be596e2a20c07f57c80aaaf7dc
+README.zh.md: a14a5281c58a5ea4a8a49e1a826397ae91e5f115

package/README.md

@@ -9,7 +9,7 @@ English | [中文](README.zh.md)
 
 ## Summary
 
-`dsh-client-test-runtime` lets browser feature specs exercise production slot, store, rendering, update, and disposal behavior in jsdom without reimplementing the UI runtime. Test authors can publish typed Session, Workspace, projection, and Conversation fixtures, query slot-local DOM roots, and script Remote replies or failures. Missing services, unstubbed session behavior, and unexpected file uploads fail at the call site, while disposal is idempotent. Use it only from in-repository browser-oriented Vitest suites through `devDependencies`; it is not a product plugin or general Node test harness.
+`SlotTestRuntime.create()` lets Vitest suites drive production slots, stores, typed Session and Workspace fixtures, and local DOM assertions in jsdom. For plugin activation, reload, reconnect, and cleanup tests, `createClientTest` starts the web profile's bundle roster with endpoint-named Remote mocks, without a business Host. Missing services and unstubbed calls fail explicitly. The whole-client fixture owns startup and disposal; the local runtime provides idempotent disposal. Use this package through `devDependencies` for client tests; it is not a product plugin.
 
 ## Table of Contents
 
@@ -40,7 +40,7 @@ expect(view.container).toMatchSnapshot()
 await runtime.dispose()
 ```
 
-`mount` prechecks required services and fails loud when one is missing — `provide(name, value)` supplies an extra service first. The runtime provides an unavailable `fileUpload` stub so assemblies can mount; replace `runtime.fileUpload.upload` before mounting when a test exercises upload behavior. `storeOf(key, scopeKey)` returns the live store instance the renderer hands a slot's component for identity and action-driven-write assertions.
+`mount` prechecks required services and fails loud when one is missing — `provide(name, value)` supplies an extra service first. The runtime provides a `fileUpload` stub that rejects every call until a suite replaces `runtime.fileUpload.upload`. `storeOf(key, scopeKey)` returns the live store instance the renderer hands a slot's component for identity and action-driven-write assertions.
 
 The optional render options select a keyed entry with `entryKey` or a list item with `only`; `view.update(owner)` retains that selection. `runtime.panelInfo` supplies the default `usePanelInfo` source with no global panel selected. Release it with `releasePanelInfoSource()` before mounting the production Layout owner. `dispose()` releases both default Workspace and panel-info root sources; early release is idempotent and does not remove replacement owners.
 
@@ -64,9 +64,34 @@ remote.goals.create.mockResolvedValue({
 expect(view.getByRole('alert')).toHaveTextContent('goal/not-found')
 ```
 
+### Whole-client tier
+
+The slot tier above mounts one feature against doubles. The whole-client tier boots the real assembly: `TestClient.start(plan, mock, options)` imports every roster row's `/client` module in-process (or takes the plan's `provide` replacement), binds `{ rpc: mock.rpc }` to that client's Connection module, synthesizes the boot graph with `graphFromRoster` and hands the loaded modules to the production module system, boots through the production `bootClient`, optionally mounts `uiRenderer`, and waits for `ctx.connection.state === 'connected'`. It lives behind a deep import so slot-tier specs never load it:
+
+```text
+// @vitest-environment jsdom
+import { createClientTest, webApp } from '@deepseek-ai/dsh-client-test-runtime/src/assembly/index.ts'
+import { ok } from '@deepseek-ai/dsh-remote-mock'
+
+const test = createClientTest({ roster: webApp }, { mount: true })
+test('registers into the sidebar', async ({ remote, start }) => {
+  remote.settings.describe.mockResolvedValue(ok({ writable: true, hasDocument: false, namespaces: [] }))
+  const client = await start()
+  expect(client.ctx.slots.entries('sidebar.settings')).toHaveLength(1)
+})
+```
+
+`createClientTest` uses native Vitest fixtures: each test gets a fresh `mock` loaded with `remoteDefaultResponses`, a `remote` proxy equal to `mock.remote`, and a `start()` that boots only after the test configures its responses. Repeated starts share one promise; await it to observe startup errors. Fixture teardown waits for startup, disposes the client even after a failed assertion, checks missing responses, and refuses a saved `start` after the test. Use `TestClient.start` directly for independently owned clients. These fixtures isolate their own state, not page globals such as `location`.
+
+The [generic Remote proxy](../remote-mock/README.md#remote-proxy) supports every namespace in both tiers. An assembled test uses the `remote` fixture; a local `TestRemote` can receive `{ settings: mock.remote.settings }`. Configure returned data and read native `.mock.calls` directly. A mutation response does not update later describe answers automatically: change `remote.settings.describe.mockResolvedValue(...)` explicitly when the scenario publishes new data. The proxy documentation owns unbuilt typing and the required build-backed local typecheck.
+
+### Roster and startup behavior
+
+`webApp` is the `web` profile's browser roster, read when the assembly entry is first imported from its bundles (`dsh-base`, then `dsh-web-app`) as the launcher composes them, except that a patch matching nothing throws here where the launcher warns: each bundle's `dsh.bundle.patch` list is parsed with the include plugin's YAML dialect and composed by its `applyEntryPatches`, and every enabled row whose package declares `dsh.client.platform === 'web'` becomes a row carrying that declaration's `inject` and `immediately`; `bundleRoster(bundles)` does the same for any bundle list. Nothing is copied from the bundles, so a bundle change is visible at the next test run. `webApp.closure(names)` keeps the named rows plus everything they inject, transitively (the rows a spec needs to boot those plugins as the bundle composes them), `webApp.pick(names)` and `webApp.without(names)` cut it down by hand, all three throw on unknown names, and `ClientRoster.of(rows)` builds one inline. `remoteDefaultResponses` holds default responses for exactly the Remote endpoints the roster calls while booting with no sessions, no workspaces, and default settings; a spec layers its own `RemoteTable` on top with `mock.load(table)`, and any call without a rule fails the test at `dispose()` through `mock.assertNoUnmatched()`. `mount` requires a roster that provides `uiRenderer`; `start` fails loud otherwise instead of returning an empty container. `client.connection` is the roster's Connection service (no `Context` augmentation declares it), and `connectTimeoutMs` bounds the readiness wait, whose failure message lists the mock log. `reload(name)` rebuilds one Loader entry the way client-hmr does (registry-first teardown, then `entry.refresh()`); each client retains its own module system and instance-bound Connection replacement, so starts and reloads can overlap without changing a page global. `unload(name)` removes an entry and waits for plugin cleanup; `flush()` settles React inside `act`. jsdom implements neither `EventSource` (client-hmr opens one at apply) nor `ResizeObserver` (layout components observe size at mount), so `start` reference-counts inert stubs for whichever global is absent and `dispose` removes exactly those — a jsdom gap, not a client identity channel. The `@deepseek-ai/dsh-api-remotes` row is dropped from every roster: its generated Remote clients exist only in built `lib/`, and `remote.<ns>` is what the tier replaces anyway. `start` instead provides one contract-free proxy per `remote.<ns>` service the roster injects (plus the namespaces the mock has rules for at that point; a namespace first registered later has no proxy); `ctx.remote.<ns>.<method>(...args)` becomes a call on the endpoint `<ns>/<method>` carrying the positional args, a stream when the mock registered a `stream()` script and a unary call otherwise, with the generated client's outcome folding (`gateway/internal` for carrier throws, `gateway/cancelled` on abort). An endpoint without a rule is still dispatched, so the mock logs it and `dispose()` fails the test.
+
 ### When to use it
 
-Use the bench for feature suites that exercise slots, stores, rendering, and disposal under a real runtime — the production `SlotRegistry`, renderer, and provide-bundle materialization are mounted, never reimplemented. It is browser-side test infrastructure: it never reaches a model request, and feature packages depend on it in `devDependencies` only.
+Use the bench for feature suites that exercise slots, stores, rendering, and disposal under a real runtime — the production `SlotRegistry`, renderer, and provide-bundle materialization are mounted, never reimplemented. It is client-side test infrastructure: it never reaches a model request, and feature packages depend on it in `devDependencies` only.
 
 ### What can go wrong
 
@@ -99,6 +124,13 @@ The bench copies no production logic: it mounts the production `SlotRegistry`, p
 | [`src/remote.ts`](src/remote.ts) | `TestRemote` double for host RPC, `RemoteError` value re-export |
 | [`src/translate.ts`](src/translate.ts) + [`src/locale-env.ts`](src/locale-env.ts) | Translation and pinned-browser-language test helpers |
 | [`src/settings-scope.ts`](src/settings-scope.ts) | `stubSettingsScope` with test-driven publications and a write spy |
+| [`src/assembly/roster.ts`](src/assembly/roster.ts) | `ClientRosterRow`, `ClientRoster` (`of`/`closure`/`pick`/`without`), the `AssemblyPlan` it annotates, and `graphFromRoster` |
+| [`src/assembly/modules.ts`](src/assembly/modules.ts) | Source `/client` imports and replacements, registered through the production module facade's pending factory queue |
+| [`src/assembly/test-client.ts`](src/assembly/test-client.ts) | `TestClient`: instance-bound Connection, shared jsdom shims, `bootClient`, mount, readiness wait, `reload`/`unload`/`dispose` |
+| [`src/assembly/vitest.ts`](src/assembly/vitest.ts) | Test-scoped `mock` and lazy `start` fixtures |
+| [`src/assembly/remote-default-responses.ts`](src/assembly/remote-default-responses.ts) | `remoteDefaultResponses`: default responses of the Remote endpoints the roster calls at boot |
+| [`src/assembly/remote-proxies.ts`](src/assembly/remote-proxies.ts) | Contract-free `remote.<ns>` proxies over the Connection: `remoteNamespacesOf`, `remoteProxiesPlugin` |
+| [`src/assembly/bundle-roster.ts`](src/assembly/bundle-roster.ts) | `bundleRoster` and `webApp`: the browser roster read from bundle patch files with the include plugin's own schema and patch application |
 | — | No runtime invariant companion is published; this test-support package owns no production event stream or mutable data — it assembles the runtime SlotRegistry and renderer (whose packages own their invariants) around test doubles; its own behavior is exercised by its package tests. |
 
 ### Lifecycle
@@ -138,7 +170,10 @@ None; this package neither assembles nor sends a provider request.
 
 These limits define how the bench is consumed. They are current package constraints, not a task backlog.
 
-- **Vitest and jsdom only** — every consumer is an in-repository browser-oriented Vitest suite. The package is not a product plugin or a general Node test harness.
+- **The whole-client tier does not run the generated Remote clients** — `remote.<ns>` proxies forward positional arguments without the generated zod validation, wire-name mapping, or scoped-identity injection; mock handlers receive those arguments directly, and the generated clients stay covered by the built-artifact e2e lanes.
+- **Proxied calls bypass the Gateway client's `invoke` and `invokeStream`** — no `$mount` lifecycle check runs, stream failures are not re-marked through `normalizeConnectionStream`, and a unary rejection is folded by the proxy itself with the Gateway client's exported `carrierFailure` and `cancelledFailure`. `ctx.remote.$stream`, `$on`, and `$host` are the real Gateway client's.
+- **An undeclared endpoint is dispatched as a unary call** — the proxy learns each endpoint's mode from the mock's registrations; a stream endpoint the spec neither scripts nor declares (`RemoteTable.streams`, `mock.stream(endpoint)`) is logged as a `unary` miss and product code receives a folded result rather than a failing stream. `remoteDefaultResponses` declares the roster's later-opened streams; `dispose()` fails the test either way.
+- **The package's client compile program adds the `node` ambient types** so the roster reader can use `node:fs`; the slot-tier sources compile against them as well.
 - **Session, Conversation, and Chat fixtures stay separate** — `sessionSnapshot` contains only Session Controller state, `conversationSnapshot` contains target-neutral Conversation state, and `chatSnapshot` contains Chat target state. Assembly tests provide Session event entries instead of adding Conversation or Chat fields to `SessionSnapshot`.
 
 <a id="dev-note"></a>

package/README.zh.md

@@ -9,7 +9,7 @@ kind: "package-library"
 
 ## 概述
 
-`dsh-client-test-runtime` 让浏览器功能测试在 jsdom 中检验生产 slot、存储、渲染、更新与销毁行为，而无需重实现 UI 运行时。测试作者可以发布带类型的 Session、Workspace、projection 与 Conversation fixture（测试前置数据），查询 slot 局部 DOM 根，并脚本化 Remote 应答或失败。缺失服务、未打桩的会话行为与意外文件上传都会在调用点失败，销毁则保持幂等。仅限仓内、面向浏览器的 Vitest 套件通过 `devDependencies` 使用本包；它不是产品插件或通用 Node 测试 harness。
+`SlotTestRuntime.create()` 让 Vitest 套件在 jsdom 中驱动生产 slot、store、带类型的 Session 与 Workspace fixture，并对局部 DOM 断言。面向插件激活、重载、重连与清理的测试，`createClientTest` 使用具名端点 Remote mock 启动 web profile 的 bundle roster，无需业务 Host。缺失服务与未打桩调用会明确失败。整机 fixture 拥有启动和销毁，局部 runtime 提供幂等销毁。通过 `devDependencies` 将本包用于客户端测试；它不是产品插件。
 
 ## 目录
 
@@ -40,7 +40,7 @@ expect(view.container).toMatchSnapshot()
 await runtime.dispose()
 ```
 
-`mount` 会预检必需服务，缺失时自明报错——先用 `provide(name, value)` 提供额外服务。运行时会提供不可用的 `fileUpload` 替身，使装配可以挂载；测试上传行为时，需要在挂载前替换 `runtime.fileUpload.upload`。`storeOf(key, scopeKey)` 返回渲染器交给 slot 组件的实时存储实例，用于身份与动作驱动写入断言。
+`mount` 会预检必需服务，缺失时自明报错——先用 `provide(name, value)` 提供额外服务。运行时提供的 `fileUpload` 替身会拒绝每次调用，直到测试套件替换 `runtime.fileUpload.upload`。`storeOf(key, scopeKey)` 返回渲染器交给 slot 组件的实时存储实例，用于身份与动作驱动写入断言。
 
 可选渲染参数通过 `entryKey` 选择 keyed 条目，或通过 `only` 选择 list 条目；`view.update(owner)` 保留该选择。`runtime.panelInfo` 提供默认的 `usePanelInfo` 数据源，初始不选中全局面板。挂载生产 Layout 所有者之前，先调用 `releasePanelInfoSource()` 释放该数据源。`dispose()` 同时释放默认的工作区与面板信息根数据源；提前释放是幂等的，不会移除替代它们的所有者。
 
@@ -64,9 +64,34 @@ remote.goals.create.mockResolvedValue({
 expect(view.getByRole('alert')).toHaveTextContent('goal/not-found')
 ```
 
+### 整体档
+
+上面的 slot 档把一个功能挂在替身上。整体档起真实装配：`TestClient.start(plan, mock, options)` 进程内 import 每个 roster 行的 `/client` 模块（或取计划里的 `provide` 替换），把 `{ rpc: mock.rpc }` 绑定到该客户端的 Connection 模块，用 `graphFromRoster` 合成启动图并把已加载模块交给生产模块系统，经生产 `bootClient` 启动，按需挂载 `uiRenderer`，再等 `ctx.connection.state === 'connected'`。它藏在深 import 后面，slot 档测试永不加载它：
+
+```text
+// @vitest-environment jsdom
+import { createClientTest, webApp } from '@deepseek-ai/dsh-client-test-runtime/src/assembly/index.ts'
+import { ok } from '@deepseek-ai/dsh-remote-mock'
+
+const test = createClientTest({ roster: webApp }, { mount: true })
+test('registers into the sidebar', async ({ remote, start }) => {
+  remote.settings.describe.mockResolvedValue(ok({ writable: true, hasDocument: false, namespaces: [] }))
+  const client = await start()
+  expect(client.ctx.slots.entries('sidebar.settings')).toHaveLength(1)
+})
+```
+
+`createClientTest` 使用原生 Vitest fixture：每个测试获得已加载 `remoteDefaultResponses` 的新 `mock`、等同于 `mock.remote` 的 `remote` Proxy，以及配置应答后才起机的 `start()`。重复启动共用一个 Promise，调用方必须 await 它来观察启动错误。fixture 收尾等待启动，即使断言失败也销毁客户端、检查漏配，并拒绝测试结束后保存的 `start` 调用。需要分别拥有多个客户端时直接用 `TestClient.start`。这些 fixture 隔离自己的状态，不隔离 `location` 等页面全局。
+
+两档测试的所有命名空间都使用[通用 Remote Proxy](../remote-mock/README.zh.md#remote-proxy)。装配测试使用 `remote` fixture；局部 `TestRemote` 可以接收 `{ settings: mock.remote.settings }`。直接配置返回数据，并读取原生 `.mock.calls`。mutation 应答不会自动更新后续 describe 应答：场景发布新数据时，显式修改 `remote.settings.describe.mockResolvedValue(...)`。Proxy 文档拥有无构建类型说明和必需的构建后本地类型检查规则。
+
+### Roster 与启动行为
+
+`webApp` 是 `web` profile 的浏览器 roster，首次 import 装配入口时从它的 bundle（先 `dsh-base`、再 `dsh-web-app`）按启动器的方式现读，只是匹配不到任何行的补丁在这里抛错、启动器只警告：每个 bundle 的 `dsh.bundle.patch` 列表用 include 插件的 YAML 方言解析、用它的 `applyEntryPatches` 合成，每个未禁用且其包声明 `dsh.client.platform === 'web'` 的行成为一行，带上该声明的 `inject` 与 `immediately`；`bundleRoster(bundles)` 对任意 bundle 列表做同样的事。没有任何东西从 bundle 拷贝出来，bundle 一改下次跑测试就能看见。`webApp.closure(names)` 保留点名的行及其传递注入的全部行（即按 bundle 组合方式起这些插件所需的行），`webApp.pick(names)` 与 `webApp.without(names)` 手工裁剪，三者都对未知名字抛错，`ClientRoster.of(rows)` 内联构造一份。`remoteDefaultResponses` 是 roster 在没有 session、没有 workspace、默认设置下启动时恰好会打的那些 Remote 端点的默认响应；测试用 `mock.load(table)` 在其上叠加自己的 `RemoteTable`，任何没有规则的调用都会在 `dispose()` 时经 `mock.assertNoUnmatched()` 让测试失败。`mount` 要求 roster 提供 `uiRenderer`；否则 `start` 响亮失败而不是返回一个空容器。`client.connection` 是 roster 的 Connection 服务（没有任何 `Context` 增强声明它），`connectTimeoutMs` 限定等就绪的时长，超时消息列出 mock log。`reload(name)` 按 client-hmr 的方式重建一个 Loader entry（先拆 registry，再 `entry.refresh()`）；每个客户端都保留自己的模块系统和绑定实例的 Connection 替换，因此启动与重载可以重叠而无需改写页面全局变量。`unload(name)` 移除 entry 并等待插件清理完成，`flush()` 在 `act` 内让 React 落定。jsdom 既没有 `EventSource`（client-hmr 在 apply 时打开一个）也没有 `ResizeObserver`（布局组件挂载时观察尺寸），所以 `start` 对缺失的全局惰性桩做引用计数，`dispose` 只移除它装的那些——这是 jsdom 的缺口，不是客户端身份通道。每个 roster 里的 `@deepseek-ai/dsh-api-remotes` 行都会被去掉：它生成的 Remote 客户端只存在于构建后的 `lib/`，而 `remote.<ns>` 正是本档要替掉的东西。`start` 改为给 roster 注入的每个 `remote.<ns>` 服务（加上此刻 mock 登记过规则的命名空间；之后才首次登记的命名空间没有代理）提供一个无契约代理；`ctx.remote.<ns>.<method>(...args)` 变成对端点 `<ns>/<method>` 的调用，携带位置参数，mock 登记了 `stream()` 脚本的走流、否则走一元，并沿用生成客户端的结果折叠（载体抛错折成 `gateway/internal`，中止折成 `gateway/cancelled`）。没有规则的端点照样发出，所以 mock 会记下它、`dispose()` 让测试失败。
+
 ### 何时使用
 
-当功能套件要在真实运行时下检验 slot、存储、渲染与销毁时使用本测试台——生产 `SlotRegistry`、渲染器与 provide bundle 物化都会被挂载，绝不重实现。它是浏览器侧测试基础设施：永远不触及模型请求，功能包仅以 `devDependencies` 依赖之。
+当功能套件要在真实运行时下检验 slot、存储、渲染与销毁时使用本测试台——生产 `SlotRegistry`、渲染器与 provide bundle 物化都会被挂载，绝不重实现。它是客户端测试基础设施：永远不触及模型请求，功能包仅以 `devDependencies` 依赖之。
 
 ### 可能出什么问题
 
@@ -99,7 +124,14 @@ expect(view.getByRole('alert')).toHaveTextContent('goal/not-found')
 | [`src/remote.ts`](src/remote.ts) | 用于 host RPC 的 `TestRemote` 替身、`RemoteError` 值转出 |
 | [`src/translate.ts`](src/translate.ts) + [`src/locale-env.ts`](src/locale-env.ts) | 翻译与固定浏览器语言测试辅助 |
 | [`src/settings-scope.ts`](src/settings-scope.ts) | 带测试驱动发布与写入 spy 的 `stubSettingsScope` |
-| — | 不发布运行时不变式伴生入口；本测试支持包不拥有任何生产事件流或可变数据；它围绕测试替身组装运行时 SlotRegistry 与渲染器，其所属包拥有各自的不变式；本包自身行为由本包测试检验。 |
+| [`src/assembly/roster.ts`](src/assembly/roster.ts) | `ClientRosterRow`、`ClientRoster`（`of`/`closure`/`pick`/`without`）、它所标注的 `AssemblyPlan`，以及 `graphFromRoster` |
+| [`src/assembly/modules.ts`](src/assembly/modules.ts) | 源码 `/client` 导入及替换，通过生产模块 facade 的待注册工厂队列登记 |
+| [`src/assembly/test-client.ts`](src/assembly/test-client.ts) | `TestClient`：绑定实例的 Connection、共享 jsdom 桩、`bootClient`、挂载、等就绪、`reload`/`unload`/`dispose` |
+| [`src/assembly/vitest.ts`](src/assembly/vitest.ts) | 测试级 `mock` 与懒启动 `start` fixture |
+| [`src/assembly/remote-default-responses.ts`](src/assembly/remote-default-responses.ts) | `remoteDefaultResponses`：roster 启动期 Remote 端点的默认响应 |
+| [`src/assembly/remote-proxies.ts`](src/assembly/remote-proxies.ts) | 经 Connection 的无契约 `remote.<ns>` 代理：`remoteNamespacesOf`、`remoteProxiesPlugin` |
+| [`src/assembly/bundle-roster.ts`](src/assembly/bundle-roster.ts) | `bundleRoster` 与 `webApp`：用 include 插件自己的 schema 与补丁应用从 bundle 补丁文件读出浏览器 roster |
+| — | 不发布运行时不变式伴生入口；本测试支持包不拥有生产事件流或可变数据，而是围绕测试替身组装生产 SlotRegistry 与渲染器。所挂载的生产包拥有各自的不变式，本包行为由本包测试检验。 |
 
 ### 生命周期
 
@@ -138,7 +170,10 @@ expect(view.getByRole('alert')).toHaveTextContent('goal/not-found')
 
 这些限制说明本测试台如何被消费。它们是当前包约束，不是任务积压。
 
-- **仅限 Vitest 与 jsdom**——所有消费方都是仓内、面向浏览器的 Vitest 套件。本包不是产品插件，也不是通用 Node 测试 harness。
+- **整体档不运行生成的 Remote 客户端**——`remote.<ns>` 代理转发位置参数，不经过生成的 zod 校验、wire 名映射或 scoped 身份注入；mock handler 直接接收这些参数，生成客户端仍由 built-artifact e2e 车道覆盖。
+- **代理调用绕过 Gateway 客户端的 `invoke` 与 `invokeStream`**——不做 `$mount` 生命周期检查，流失败不经 `normalizeConnectionStream` 重新标记，一元拒绝由代理自己用 Gateway 客户端导出的 `carrierFailure` 与 `cancelledFailure` 折叠。`ctx.remote.$stream`、`$on`、`$host` 是真 Gateway 客户端的。
+- **未声明的端点按一元调用发出**——代理从 mock 的登记学到每个端点的模式；spec 既没给脚本也没声明（`RemoteTable.streams`、`mock.stream(endpoint)`）的流端点记为 `unary` 漏配，产品代码收到的是折叠结果而不是失败的流。`remoteDefaultResponses` 声明了 roster 启动后才打开的流；无论哪种，`dispose()` 都会让测试失败。
+- **本包的 client 编译程序加了 `node` 环境类型**，好让 roster 读取器使用 `node:fs`；slot 档的源码也在这些类型下编译。
 - **Session、Conversation 与 Chat fixture 保持分离**——`sessionSnapshot` 只包含 Session 控制器状态，`conversationSnapshot` 包含与目标无关的 Conversation 状态，`chatSnapshot` 包含 Chat 目标状态。组装测试提供 Session 事件条目，而不是向 `SessionSnapshot` 添加 Conversation 或 Chat 字段。
 
 <a id="dev-note"></a>

package/lib/index.js

@@ -818,6 +818,25 @@ var TestWorkspaces = class {
 			draft.archivedSessionIds = [...draft.archivedSessionIds, sessionId];
 		});
 	}
+	/**
+	* Unarchive a session (recorded). The default mirrors the production face's
+	* observable effect: the id leaves the list state's archive set.
+	* @param sessionId - session to unarchive.
+	*/
+	async unarchiveSession(sessionId) {
+		this.calls.push({
+			method: "unarchiveSession",
+			args: [sessionId]
+		});
+		const stub = this.stubs.get("unarchiveSession");
+		if (stub !== void 0) {
+			await stub(sessionId);
+			return;
+		}
+		await this.update((draft) => {
+			draft.archivedSessionIds = draft.archivedSessionIds.filter((id) => id !== sessionId);
+		});
+	}
 };
 //#endregion
 //#region lib/types/settings-scope.js
@@ -868,61 +887,6 @@ function stubSettingsScope() {
 	};
 }
 //#endregion
-//#region lib/types/settings-remote.js
-/** Test double for the `settings` Remote namespace a bench's plugins inject. */
-/**
-* Build a scripted `settings` Remote namespace for a bench. Each write answers
-* with the addressed namespace unchanged, so a bench that only needs its
-* plugins to activate scripts nothing; one asserting a write reads the
-* corresponding spy or replaces the face.
-* @param namespaces - namespace views the first describe answers with.
-* @param options - deployment facts the describe answer reports.
-* @returns the face and its controls.
-*/
-function scriptedSettingsRemote(namespaces = [], options = {}) {
-	let served = namespaces;
-	const writable = options.writable ?? true;
-	const hasDocument = options.hasDocument ?? false;
-	const answer = (ns) => {
-		const view = served.find((candidate) => candidate.ns === ns);
-		return Promise.resolve(view === void 0 ? {
-			ok: false,
-			error: {
-				code: "settings/rejected",
-				message: `no scripted namespace "${ns}"`,
-				details: { ns }
-			}
-		} : {
-			ok: true,
-			value: view
-		});
-	};
-	const update = vi.fn((ns, _patch, _expectedRevision) => answer(ns));
-	const replace = vi.fn((ns, _section, _expectedRevision) => answer(ns));
-	const mutate = vi.fn((ns, _ops, _expectedRevision) => answer(ns));
-	return {
-		settings: {
-			describe: () => Promise.resolve({
-				ok: true,
-				value: {
-					writable,
-					hasDocument,
-					namespaces: served
-				}
-			}),
-			update: (ns, patch, expectedRevision) => update(ns, patch, expectedRevision),
-			replace: (ns, section, expectedRevision) => replace(ns, section, expectedRevision),
-			mutate: (ns, ops, expectedRevision) => mutate(ns, ops, expectedRevision)
-		},
-		update,
-		replace,
-		mutate,
-		publish(next) {
-			served = next;
-		}
-	};
-}
-//#endregion
 //#region lib/types/remote.js
 /**
 * Remote service test double for the forwarded-event path. Feature specs need
@@ -1214,10 +1178,7 @@ var SlotTestRuntime = class SlotTestRuntime {
 		this.root = new TestRoot(slots, this.stabilizer);
 		this.sessions = new TestSessions(this.stabilizer, ctx);
 		this.workspaces = new TestWorkspaces(this.stabilizer);
-		this.fileUpload = {
-			available: false,
-			upload: () => Promise.reject(/* @__PURE__ */ new Error("client test runtime: file upload is not stubbed"))
-		};
+		this.fileUpload = { upload: () => Promise.reject(/* @__PURE__ */ new Error("client test runtime: file upload is not stubbed")) };
 		ctx.provide("sessions", this.sessions);
 		ctx.provide("workspaces", this.workspaces);
 		ctx.provide("fileUpload", this.fileUpload);
@@ -1386,4 +1347,4 @@ var SlotTestRuntime = class SlotTestRuntime {
 	}
 };
 //#endregion
-export { FixtureSession, RemoteError, SlotTestRuntime, TestRemote, TestRoot, TestSessions, TestWorkspaces, bindSnapshotSelector, chatSnapshot, conversationSnapshot, createSlotRenderer, domSnapshotSerializer, makeTranslate, registerDomSnapshotSerializer, scriptedSettingsRemote, sessionSnapshot, stubSettingsScope, usePinnedBrowserLanguages, workspaceSnapshot };
+export { FixtureSession, RemoteError, SlotTestRuntime, TestRemote, TestRoot, TestSessions, TestWorkspaces, bindSnapshotSelector, chatSnapshot, conversationSnapshot, createSlotRenderer, domSnapshotSerializer, makeTranslate, registerDomSnapshotSerializer, sessionSnapshot, stubSettingsScope, usePinnedBrowserLanguages, workspaceSnapshot };

package/lib/types/assembly/bundle-roster.d.ts

@@ -0,0 +1,15 @@
+import { ClientRoster } from './roster.ts';
+/** The `web` profile's bundle layers, in the order `dsh --profile web` applies them (app-boot `PROFILE_TEMPLATES.web`). */
+export declare const WEB_PROFILE_BUNDLES: readonly string[];
+/**
+ * Compose the browser roster of `bundles`, applied in order.
+ * @param bundles - bundle package names in application order.
+ * @param anchor - file whose package resolution locates the bundles; default this package.
+ * @returns the roster in composition order, one row per package.
+ * @throws {Error} when a bundle, its patch file, or an enabled row's package does not resolve, when the patch list
+ * is not a list or does not apply as written, or when a browser row's `disabled` is a `!!js` expression.
+ */
+export declare function bundleRoster(bundles: readonly string[], anchor?: string): ClientRoster;
+/** The `web` profile's browser roster, composed from its bundles at import. */
+export declare const webApp: ClientRoster;
+//# sourceMappingURL=bundle-roster.d.ts.map

package/lib/types/assembly/index.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Whole-client tier entry (deep import only:
+ * `@deepseek-ai/dsh-client-test-runtime/src/assembly/index.ts`). Kept out of
+ * the package root so slot-tier specs do not load the assembly machinery.
+ * @module @deepseek-ai/dsh-client-test-runtime/src/assembly
+ */
+export { ClientRoster } from './roster.ts';
+export type { AssemblyPlan, ClientPluginModule, ClientRosterRow } from './roster.ts';
+export { TestClient } from './test-client.ts';
+export type { TestClientOptions } from './test-client.ts';
+export { remoteDefaultResponses } from './remote-default-responses.ts';
+export { bundleRoster, webApp } from './bundle-roster.ts';
+export { createClientTest } from './vitest.ts';
+export type { ClientTestFixtures } from './vitest.ts';
+//# sourceMappingURL=index.d.ts.map

package/lib/types/assembly/modules.d.ts

@@ -0,0 +1,25 @@
+import type { ClientModuleLoader, WebBootGraph } from '@deepseek-ai/dsh-client-modules/client';
+import type { AssemblyPlan, ClientPluginModule } from './roster.ts';
+/** The bootstrap row: always this process's static namespace, never a dynamic import or a `provide` replacement. */
+export declare const MODULES_PACKAGE = "@deepseek-ai/dsh-client-modules";
+/**
+ * Resolve each roster row to its plugin module: `plan.provide[name]` when
+ * present, otherwise a `/client` import resolved by the repository's tsconfig
+ * path aliases under Vitest. The bootstrap row is the
+ * statically imported `@deepseek-ai/dsh-client-modules/client` namespace.
+ * @param plan - validated plan.
+ * @returns package name → module, in roster order.
+ * @throws {Error} when an import fails (the package name prefixes the original message) or the bootstrap row is provided.
+ */
+export declare function loadPluginModules(plan: AssemblyPlan): Promise<ReadonlyMap<string, ClientPluginModule>>;
+/**
+ * Build the production module system over queued factories returning the
+ * loaded namespaces. The bootstrap row uses `bootstrapModule`; `staticModules`
+ * is empty because namespaces already hold their own imports. Missing factories
+ * reject through `loadBundle` without fetching.
+ * @param graph - raw boot graph from `graphFromRoster`; `createClientModuleSystem` parses it.
+ * @param modules - loaded plugin modules keyed by package name.
+ * @returns module system to install as `loader.internal`; its `manifest` is the parsed graph.
+ */
+export declare function createInProcessModules(graph: WebBootGraph, modules: ReadonlyMap<string, ClientPluginModule>): ClientModuleLoader;
+//# sourceMappingURL=modules.d.ts.map

package/lib/types/assembly/remote-default-responses.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Default responses for every Remote endpoint the web assembly calls while
+ * booting and rendering with no sessions, no workspaces, and default settings.
+ * The comment above each row names the plugin that calls it; endpoints boot
+ * never touches stay absent so a new call fails loud. `$events` is built into
+ * `RemoteMock`.
+ * @module @deepseek-ai/dsh-client-test-runtime/src/assembly/remote-default-responses
+ */
+import { type RemoteTable } from '@deepseek-ai/dsh-remote-mock';
+/** Default responses of the boot-time Remote endpoints; a spec loads it first and layers its own table on top. */
+export declare const remoteDefaultResponses: RemoteTable;
+//# sourceMappingURL=remote-default-responses.d.ts.map

package/lib/types/assembly/remote-proxies.d.ts

@@ -0,0 +1,20 @@
+import type { RemoteMock } from '@deepseek-ai/dsh-remote-mock';
+import type { ClientPluginModule } from './roster.ts';
+/** The assembly row the proxies stand in for; its generated clients exist only in built `lib/`. */
+export declare const REMOTES_PACKAGE = "@deepseek-ai/dsh-api-remotes";
+/**
+ * Namespaces to provide: every `remote.<ns>` a roster module injects, plus the
+ * namespace of every endpoint the mock has a rule for.
+ * @param modules - loaded roster modules.
+ * @param mock - the spec's mock.
+ * @returns sorted namespace names.
+ */
+export declare function remoteNamespacesOf(modules: Iterable<ClientPluginModule>, mock: RemoteMock): readonly string[];
+/**
+ * Plugin providing the namespace proxies; `TestClient.start` mounts it before the Loader rows.
+ * @param namespaces - namespaces to provide.
+ * @param mock - the spec's mock, asked for each endpoint's mode.
+ * @returns the plugin.
+ */
+export declare function remoteProxiesPlugin(namespaces: readonly string[], mock: RemoteMock): ClientPluginModule;
+//# sourceMappingURL=remote-proxies.d.ts.map

package/lib/types/assembly/roster.d.ts

@@ -0,0 +1,80 @@
+/**
+ * Client roster: the ordered package-name rows a whole-client test boots, and
+ * the plan that annotates one with the rows the test provides itself. `webApp`
+ * and `bundleRoster` (`./bundle-roster.ts`) read rosters from the bundle patch
+ * files; a spec may also build one inline with {@link ClientRoster.of}.
+ * @module @deepseek-ai/dsh-client-test-runtime/src/assembly/roster
+ */
+import type { Context } from '@deepseek-ai/cordis';
+import type { WebBootGraph } from '@deepseek-ai/dsh-client-modules/client';
+/** One browser plugin row as `dsh.client` declares it, keyed by package name. */
+export interface ClientRosterRow {
+    /** Package name (== manifest entry id == Loader entry name). */
+    readonly name: string;
+    /** Package-name dependency edges from `dsh.client.inject` ([] when absent). */
+    readonly inject: readonly string[];
+    /** Stage-one prefetch mark from `dsh.client.immediately` (false when absent). */
+    readonly immediately: boolean;
+}
+/**
+ * Synthesize the raw `WebBootGraph` for `rows`: one `application` batch
+ * holding every row, `rev: 'local'`, placeholder `/plugins/<name>/client.js`
+ * URLs, since every module is seeded in process and never fetched. Validation
+ * stays with the production `parseBootManifest` inside the module system:
+ * duplicate names and an empty roster are rejected there, not here.
+ * @param rows - roster rows in composition order.
+ * @returns the unparsed graph, as `createClientModuleSystem` consumes it.
+ */
+export declare function graphFromRoster(rows: readonly ClientRosterRow[]): WebBootGraph;
+/** Immutable, name-addressable roster. */
+export declare class ClientRoster {
+    readonly rows: readonly ClientRosterRow[];
+    /**
+     * Build a roster from rows; duplicate names throw.
+     * @param rows - roster rows in composition order.
+     * @returns roster.
+     */
+    static of(rows: readonly ClientRosterRow[]): ClientRoster;
+    private constructor();
+    /**
+     * Keep only `names`, preserving roster order; an unknown name throws with the roster listed.
+     * @param names - package names to keep.
+     * @returns sub-roster.
+     */
+    pick(names: readonly string[]): ClientRoster;
+    /**
+     * The named rows plus every row they inject, transitively, in roster order: the rows a spec needs to boot the
+     * named plugins as the bundle composes them. The shell's platform modules (`PLATFORM_MODULES`, seeded statically
+     * rather than loaded as rows) end the walk. An unknown name throws with the roster listed; a row injecting any
+     * other package outside the roster throws, since the bundle itself would not boot.
+     * @param names - package names whose dependency cone to keep.
+     * @returns sub-roster.
+     */
+    closure(names: readonly string[]): ClientRoster;
+    /**
+     * Drop `names`; an unknown name throws with the roster listed.
+     * @param names - package names to drop.
+     * @returns sub-roster.
+     */
+    without(names: readonly string[]): ClientRoster;
+    private known;
+}
+/** The module face the Loader materializes for one client plugin row. */
+export interface ClientPluginModule {
+    apply(ctx: Context, config?: unknown): unknown;
+    readonly inject?: readonly string[] | Readonly<Record<string, unknown>>;
+    readonly Config?: unknown;
+}
+/** What to boot and what the test supplies itself. */
+export interface AssemblyPlan {
+    readonly roster: ClientRoster;
+    /** Row replacements by package name (the test's own implementation of that row). Names outside the roster throw. */
+    readonly provide?: Readonly<Record<string, ClientPluginModule>>;
+}
+/**
+ * Validate a plan against its roster.
+ * @param plan - plan to check.
+ * @throws {Error} naming any `provide` key outside the roster.
+ */
+export declare function assertPlan(plan: AssemblyPlan): void;
+//# sourceMappingURL=roster.d.ts.map

package/lib/types/assembly/test-client.d.ts

@@ -0,0 +1,83 @@
+/**
+ * Whole-client test carrier: boots an {@link AssemblyPlan} through the
+ * production `bootClient` over an in-process module table, with a
+ * `RemoteMock` bound to that client's Connection plugin instance.
+ * @module @deepseek-ai/dsh-client-test-runtime/src/assembly/test-client
+ */
+import { Context } from '@deepseek-ai/cordis';
+import { type ConnectionHandle } from '@deepseek-ai/dsh-client-connection/client';
+import type { RemoteMock } from '@deepseek-ai/dsh-remote-mock';
+import { type AssemblyPlan } from './roster.ts';
+/** Carrier options. */
+export interface TestClientOptions {
+    /**
+     * Mount `uiRenderer` into an element (a fresh `document.body` child when `true`); requires jsdom and a roster
+     * that provides `uiRenderer`. Default false.
+     */
+    readonly mount?: boolean | HTMLElement;
+    /** Wait for `ctx.connection.state === 'connected'` before returning. Default true. */
+    readonly awaitConnected?: boolean;
+    /** Readiness budget in milliseconds before `start` rejects with the mock log summary. Default 5000. */
+    readonly connectTimeoutMs?: number;
+}
+/** A booted client under test. */
+export declare class TestClient {
+    readonly ctx: Context;
+    readonly mock: RemoteMock;
+    readonly container: HTMLElement | undefined;
+    private readonly restore;
+    /**
+     * Load the roster's modules, bind this client's mock to its Connection row,
+     * hold the jsdom shims, and boot through `bootClient` over the synthesized
+     * boot graph; afterwards optionally mount and wait for the connection. The
+     * bound row replaces only the page-global input adapter: both paths call
+     * `installConnection`, while this path supplies the mock carrier, uses
+     * default recovery timings, and captures the current page hostname once for
+     * later reloads. A caller-provided Connection row remains unchanged and owns
+     * its readiness behavior. The `@deepseek-ai/dsh-api-remotes` row is
+     * dropped from the roster: its generated Remote clients exist only in built
+     * `lib/`, and the `remote.<ns>` services the roster injects (plus the
+     * namespaces the mock has rules for at this point) are provided as
+     * contract-free proxies over the same Connection instead; a `provide` entry
+     * for that row is refused. On any failure the context is disposed, an owned
+     * mount removed, and this client's hold on the shims released before the
+     * original error is rethrown.
+     * @param plan - roster and annotations.
+     * @param mock - Remote mock answering every Gateway call.
+     * @param options - mount and readiness options.
+     * @returns the booted client.
+     */
+    static start(plan: AssemblyPlan, mock: RemoteMock, options?: TestClientOptions): Promise<TestClient>;
+    private disposing;
+    private constructor();
+    /** The roster's Connection service (no `Context` augmentation declares it); throws when the roster provides none. */
+    get connection(): ConnectionHandle;
+    /** Flush pending React work and microtasks inside `act` (plain microtask flush without a DOM). */
+    flush(): Promise<void>;
+    /**
+     * Rebuild one Loader entry: client-hmr's registry-first fiber teardown, then
+     * `entry.refresh()`. Each client's module table retains its own instance-bound
+     * Connection plugin, so reloads do not coordinate through process globals.
+     * Requires a live client: after `dispose()` the Loader holds no entries and
+     * the lookup throws before teardown.
+     * @param name - package name of the row.
+     */
+    reload(name: string): Promise<void>;
+    /**
+     * Remove one Loader entry and wait for its plugin cleanup.
+     * @param name - package name of the row.
+     */
+    unload(name: string): Promise<void>;
+    /**
+     * Dispose the plugin tree, then drop an owned mount and release this
+     * client's hold on the shared jsdom shims even when the tree fails to dispose,
+     * then `mock.assertNoUnmatched()` last so its failure is the test's reason
+     * without skipping the cleanup; when both the tree and the check fail, one
+     * error carries both messages. The first call owns the teardown and reports
+     * its failure; every later call waits for that teardown and resolves.
+     */
+    dispose(): Promise<void>;
+    private teardown;
+    private entryOf;
+}
+//# sourceMappingURL=test-client.d.ts.map

package/lib/types/assembly/vitest.d.ts

@@ -0,0 +1,24 @@
+/** Test-scoped Remote mock and lazy client boot, owned by native Vitest fixtures. */
+import { type TestAPI } from 'vitest';
+import { RemoteMock, type MockedRemote } from '@deepseek-ai/dsh-remote-mock';
+import type { AssemblyPlan } from './roster.ts';
+import { TestClient, type TestClientOptions } from './test-client.ts';
+/** Per-test controls; configure the mock before awaiting `start()`. */
+export interface ClientTestFixtures {
+    /** Fresh mock with the assembly's default responses already loaded. */
+    mock: RemoteMock;
+    /** Namespace proxy backed by the same native mocks used by the Connection carrier. */
+    remote: MockedRemote;
+    /** Await the one client owned by this test; rejects after the fixture closes. */
+    start: () => Promise<TestClient>;
+}
+/**
+ * Extend Vitest with a fresh mock and a lazy, automatically disposed client. Repeated `start()` calls share one
+ * promise. Await it to observe startup failures; cleanup waits for startup but does not rethrow its rejection.
+ * Missing mock responses still fail teardown even when no client was started. Page globals remain environment-owned.
+ * @param plan - roster and replacement modules, shared as configuration rather than as a running client.
+ * @param options - mount and readiness settings passed to `TestClient.start`.
+ * @returns Vitest's test function with test-scoped `mock` and `start` fixtures.
+ */
+export declare function createClientTest(plan: AssemblyPlan, options?: TestClientOptions): TestAPI<ClientTestFixtures>;
+//# sourceMappingURL=vitest.d.ts.map

package/lib/types/index.d.ts

@@ -27,8 +27,6 @@ export { domSnapshotSerializer, registerDomSnapshotSerializer } from './snapshot
 export { FixtureSession, TestSessions } from './sessions.ts';
 export { stubSettingsScope } from './settings-scope.ts';
 export type { StubSettingsScope } from './settings-scope.ts';
-export { scriptedSettingsRemote } from './settings-remote.ts';
-export type { ScriptedNamespace, ScriptedSettingsRemote } from './settings-remote.ts';
 export { TestWorkspaces } from './workspaces.ts';
 export { RemoteError, TestRemote } from './remote.ts';
 export { chatSnapshot, conversationSnapshot, sessionSnapshot, workspaceSnapshot, } from './fixtures.ts';
@@ -81,8 +79,6 @@ export interface FeatureHandle {
 }
 /** Mutable fail-loud file-upload stub installed by {@link SlotTestRuntime}. */
 export interface TestFileUpload {
-    /** Availability reported to the feature under test. */
-    available: boolean;
     /** Test-supplied upload behavior; the default rejects every call. */
     upload: (sessionId: SessionId, ...args: unknown[]) => Promise<unknown>;
 }

package/lib/types/workspaces.d.ts

@@ -84,6 +84,12 @@ export declare class TestWorkspaces implements IWorkspaces {
      * @param sessionId - session to archive.
      */
     archiveSession(sessionId: SessionId): Promise<void>;
+    /**
+     * Unarchive a session (recorded). The default mirrors the production face's
+     * observable effect: the id leaves the list state's archive set.
+     * @param sessionId - session to unarchive.
+     */
+    unarchiveSession(sessionId: SessionId): Promise<void>;
 }
 export {};
 //# sourceMappingURL=workspaces.d.ts.map

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@crazx/dsh-client-test-runtime",
-  "description": "jsdom slot test runtime: real Cordis Context + SlotRegistry + UI renderer with test-owned session/workspace doubles for feature specs",
-  "version": "0.1.5-rc.2.zw.1",
+  "description": "Browser test runtimes: a jsdom slot bench with test-owned Session and Workspace doubles, and a whole-client tier that boots the web roster through the production bootClient over an endpoint-named Remote mock",
+  "version": "0.1.6-alpha.1.zw.2",
   "publishConfig": {
     "access": "public"
   },
@@ -25,46 +25,67 @@
   "dependencies": {
     "@testing-library/dom": "^10.4.1",
     "@testing-library/react": "^16.3.2",
+    "js-yaml": "^4.2.0",
     "vitest": "^4.1.8"
   },
   "peerDependencies": {
-    "@deepseek-ai/dsh-api-session-controller": "0.1.5-rc.2.zw.1",
-    "@deepseek-ai/dsh-api-workspace-controller": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-attachment": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-connection": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-store": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-chat": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-conversation": "0.1.5-rc.2.zw.1",
-    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-session": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-settings": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-session": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-subagent": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-typert-protocol": "^0.1.5-rc.2",
     "@deepseek-ai/cordis": "^4.0.2",
+    "@deepseek-ai/cordis-plugin-include": "^1.0.7",
+    "@deepseek-ai/cordis-plugin-loader": "^1.0.3",
+    "@deepseek-ai/dsh-api-gateway": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-api-session-controller": "0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-api-workspace-controller": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-attachment": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-connection": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-hmr": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-modules": "0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-client-store": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-chat": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-session": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-settings": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-slots": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-web": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-remote-mock": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-session": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-subagent": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-typert-protocol": "^0.1.6-alpha.1",
     "react": "^18.2.0",
     "react-dom": "^18.2.0"
   },
   "devDependencies": {
-    "@deepseek-ai/dsh-api-session-controller": "npm:@crazx/dsh-api-session-controller@0.1.5-rc.2.zw.1",
-    "@deepseek-ai/dsh-api-workspace-controller": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-attachment": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-connection": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-store": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-chat": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-conversation": "npm:@crazx/dsh-client-ui-conversation@0.1.5-rc.2.zw.1",
-    "@deepseek-ai/dsh-client-ui-layout": "npm:@crazx/dsh-client-ui-layout@0.1.5-rc.2.zw.1",
-    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-session": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-settings": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-session": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-subagent": "^0.1.5-rc.2",
-    "@deepseek-ai/dsh-typert-protocol": "^0.1.5-rc.2",
+    "@deepseek-ai/cordis": "^4.0.2",
+    "@deepseek-ai/cordis-plugin-include": "^1.0.7",
+    "@deepseek-ai/cordis-plugin-loader": "^1.0.3",
+    "@deepseek-ai/dsh-api-gateway": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-api-remotes": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-api-session-controller": "npm:@crazx/dsh-api-session-controller@0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-api-workspace-controller": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-attachment": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-base": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-connection": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-hmr": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-locale": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-modules": "npm:@crazx/dsh-client-modules@0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-client-store": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-chat": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "npm:@crazx/dsh-client-ui-conversation@0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-client-ui-layout": "npm:@crazx/dsh-client-ui-layout@0.1.6-alpha.1.zw.2",
+    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-session": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-settings": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-ui-slots": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-client-web": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-remote-mock": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-session": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-settings": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-subagent": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-typert-protocol": "^0.1.6-alpha.1",
+    "@deepseek-ai/dsh-web-app": "^0.1.6-alpha.1",
+    "@types/js-yaml": "^4.0.9",
     "@types/react": "~18.3.1",
     "@types/react-dom": "~18.3.0",
-    "@deepseek-ai/cordis": "^4.0.2",
     "react": "^18.2.0",
     "react-dom": "^18.2.0"
   },

package/lib/types/settings-remote.d.ts

@@ -1,83 +0,0 @@
-/** Test double for the `settings` Remote namespace a bench's plugins inject. */
-import { vi } from 'vitest';
-/** The minimum a scripted namespace view carries for the double's own bookkeeping. */
-export interface ScriptedNamespace {
-    /** Namespace key the write addresses. */
-    ns: string;
-}
-/** One scripted `settings` namespace face plus the controls a bench drives it with. */
-export interface ScriptedSettingsRemote<View extends ScriptedNamespace> {
-    /**
-     * The namespace face handed to `TestRemote` as `settings`. A plugin injecting
-     * `remote.settings` unparks on it, which is what most benches need; the
-     * describe answer is the same one the shared mirror would read.
-     */
-    settings: {
-        describe(): Promise<{
-            ok: true;
-            value: {
-                writable: boolean;
-                hasDocument: boolean;
-                namespaces: readonly View[];
-            };
-        }>;
-        update(ns: string, patch: unknown, expectedRevision: number | undefined): Promise<{
-            ok: true;
-            value: View;
-        } | {
-            ok: false;
-            error: {
-                code: string;
-                message: string;
-                details: object;
-            };
-        }>;
-        replace(ns: string, section: unknown, expectedRevision: number | undefined): Promise<{
-            ok: true;
-            value: View;
-        } | {
-            ok: false;
-            error: {
-                code: string;
-                message: string;
-                details: object;
-            };
-        }>;
-        mutate(ns: string, ops: unknown, expectedRevision: number | undefined): Promise<{
-            ok: true;
-            value: View;
-        } | {
-            ok: false;
-            error: {
-                code: string;
-                message: string;
-                details: object;
-            };
-        }>;
-    };
-    /** Spy behind `settings.update`, for argument assertions. */
-    update: ReturnType<typeof vi.fn>;
-    /** Spy behind `settings.replace`, for argument assertions. */
-    replace: ReturnType<typeof vi.fn>;
-    /** Spy behind `settings.mutate`, for argument assertions. */
-    mutate: ReturnType<typeof vi.fn>;
-    /**
-     * Replace what the next describe answers with, as a Host commit would.
-     * @param namespaces - the namespace views to serve from now on.
-     */
-    publish(namespaces: readonly View[]): void;
-}
-/**
- * Build a scripted `settings` Remote namespace for a bench. Each write answers
- * with the addressed namespace unchanged, so a bench that only needs its
- * plugins to activate scripts nothing; one asserting a write reads the
- * corresponding spy or replaces the face.
- * @param namespaces - namespace views the first describe answers with.
- * @param options - deployment facts the describe answer reports.
- * @returns the face and its controls.
- */
-export declare function scriptedSettingsRemote<View extends ScriptedNamespace>(namespaces?: readonly View[], options?: {
-    writable?: boolean;
-    hasDocument?: boolean;
-}): ScriptedSettingsRemote<View>;
-//# sourceMappingURL=settings-remote.d.ts.map