@ran-sh/dsh-crew 1.9.0 → 1.10.0

package/docs/readiness-matrix.md

@@ -1,85 +1,85 @@
-# DSH Crew Readiness Matrix
-
-The readiness matrix is a conservative diagnostic surface for release and environment confidence. Its primary rule is simple:
-
-> Missing evidence is never PASS.
-
-The matrix is emitted by `hubStatus()` and is therefore visible inside the existing `dsh_worker_config` response under `hub_compatibility.readiness_matrix`.
-
-## Statuses
-
-- `PASS` — direct evidence confirms the row.
-- `FAIL` — a check actually ran and produced an incompatible or failed result.
-- `BLOCKED` — the check could not run because required infrastructure or authorization was unavailable.
-- `SKIP` — the row is intentionally not applicable for the active policy/path.
-- `NOT_RUN` — no trusted evidence has been supplied for the row.
-
-`BLOCKED` and `SKIP` are not failures. `NOT_RUN` is not success.
-
-## Evidence classes
-
-The matrix separates three kinds of evidence:
-
-1. `live-runtime` — facts the current process can directly observe, such as Hub reachability and protocol compatibility.
-2. `ci` — platform validation such as Linux deterministic, Windows regressions, and future macOS smoke.
-3. `real-execution` — provider/model and workflow behavior that requires a genuine DSH execution.
-
-Live checks are populated automatically. The config report also consumes the
-compatible Hub's bounded job registry, so a completed Worker or Reviewer can
-promote the corresponding generic real-execution row. Other CI and execution
-rows remain `NOT_RUN` until a trusted higher layer supplies explicit evidence.
-
-## Target rows
-
-- `linux_deterministic`
-- `windows_regressions`
-- `macos_smoke`
-- `hub_compatibility`
-- `provider_catalog`
-- `provider_health`
-- `reviewer_health`
-- `model_execution`
-- `deepseek_flash`
-- `deepseek_pro`
-- `opencode_go_mimo_qwen`
-- `reviewer_pipeline`
-- `cancellation_timeout_escalation`
-- `standalone_official`
-
-`provider_health` and `reviewer_health` describe only the currently resolved
-Worker and Reviewer routes. A fresh negative observation overrides historical
-success; unrelated providers and stale observations do not. Historical jobs
-count only when their provider/model matches the corresponding current route,
-with escalation evidence matched against the current escalation route.
-
-## Provider/catalog rule
-
-The Hub client does not know the active worker provider mode, so its embedded matrix leaves `provider_catalog` as `NOT_RUN` with `PROVIDER_MODE_UNKNOWN` rather than guessing.
-
-When a higher layer knows the provider mode and has actually read the Harness catalog, it may build a more specific matrix:
-
-- DeepSeek Official strict mode: catalog row may be `SKIP` / `PROVIDER_CATALOG_NOT_REQUIRED`.
-- Follow-DSH with successful catalog read: `PASS` / `PROVIDER_CATALOG_RESOLVED`.
-- Follow-DSH with an attempted but failed catalog read: `FAIL` / `PROVIDER_CATALOG_UNAVAILABLE`.
-- Hub unavailable/incompatible before catalog access: `BLOCKED`, not `FAIL`.
-
-## Credential safety
-
-The matrix never reads or returns credential values, provider configuration payloads, quota data, pricing, cookies, tokens, or raw exception dumps. The standalone row defaults to `NOT_RUN` / `CREDENTIAL_STATUS_NOT_PROBED` unless an authorized real-environment validation explicitly reports evidence.
-
-## Trusted evidence
-
-`buildReadinessMatrix()` accepts an optional evidence map so CI/report aggregation can be added later without changing row semantics. Evidence can set only the existing status vocabulary. Invalid statuses are ignored rather than broadening the contract.
-
-An evidence record may contain:
-
-```json
-{
-  "status": "PASS",
-  "reason_code": "CI_GREEN",
-  "evidence_source": "github-actions",
-  "evidence_ref": "run-123"
-}
-```
-
-The matrix does not fetch or trust arbitrary remote data by itself. Loading and authenticating an evidence source is the responsibility of the higher layer that calls the builder.
+# DSH Crew Readiness Matrix
+
+The readiness matrix is a conservative diagnostic surface for release and environment confidence. Its primary rule is simple:
+
+> Missing evidence is never PASS.
+
+The matrix is emitted by `hubStatus()` and is therefore visible inside the existing `dsh_worker_config` response under `hub_compatibility.readiness_matrix`.
+
+## Statuses
+
+- `PASS` — direct evidence confirms the row.
+- `FAIL` — a check actually ran and produced an incompatible or failed result.
+- `BLOCKED` — the check could not run because required infrastructure or authorization was unavailable.
+- `SKIP` — the row is intentionally not applicable for the active policy/path.
+- `NOT_RUN` — no trusted evidence has been supplied for the row.
+
+`BLOCKED` and `SKIP` are not failures. `NOT_RUN` is not success.
+
+## Evidence classes
+
+The matrix separates three kinds of evidence:
+
+1. `live-runtime` — facts the current process can directly observe, such as Hub reachability and protocol compatibility.
+2. `ci` — platform validation such as Linux deterministic, Windows regressions, and future macOS smoke.
+3. `real-execution` — provider/model and workflow behavior that requires a genuine DSH execution.
+
+Live checks are populated automatically. The config report also consumes the
+compatible Hub's bounded job registry, so a completed Worker or Reviewer can
+promote the corresponding generic real-execution row. Other CI and execution
+rows remain `NOT_RUN` until a trusted higher layer supplies explicit evidence.
+
+## Target rows
+
+- `linux_deterministic`
+- `windows_regressions`
+- `macos_smoke`
+- `hub_compatibility`
+- `provider_catalog`
+- `provider_health`
+- `reviewer_health`
+- `model_execution`
+- `deepseek_flash`
+- `deepseek_pro`
+- `opencode_go_mimo_qwen`
+- `reviewer_pipeline`
+- `cancellation_timeout_escalation`
+- `standalone_official`
+
+`provider_health` and `reviewer_health` describe only the currently resolved
+Worker and Reviewer routes. A fresh negative observation overrides historical
+success; unrelated providers and stale observations do not. Historical jobs
+count only when their provider/model matches the corresponding current route,
+with escalation evidence matched against the current escalation route.
+
+## Provider/catalog rule
+
+The Hub client does not know the active worker provider mode, so its embedded matrix leaves `provider_catalog` as `NOT_RUN` with `PROVIDER_MODE_UNKNOWN` rather than guessing.
+
+When a higher layer knows the provider mode and has actually read the Harness catalog, it may build a more specific matrix:
+
+- DeepSeek Official strict mode: catalog row may be `SKIP` / `PROVIDER_CATALOG_NOT_REQUIRED`.
+- Follow-DSH with successful catalog read: `PASS` / `PROVIDER_CATALOG_RESOLVED`.
+- Follow-DSH with an attempted but failed catalog read: `FAIL` / `PROVIDER_CATALOG_UNAVAILABLE`.
+- Hub unavailable/incompatible before catalog access: `BLOCKED`, not `FAIL`.
+
+## Credential safety
+
+The matrix never reads or returns credential values, provider configuration payloads, quota data, pricing, cookies, tokens, or raw exception dumps. The standalone row defaults to `NOT_RUN` / `CREDENTIAL_STATUS_NOT_PROBED` unless an authorized real-environment validation explicitly reports evidence.
+
+## Trusted evidence
+
+`buildReadinessMatrix()` accepts an optional evidence map so CI/report aggregation can be added later without changing row semantics. Evidence can set only the existing status vocabulary. Invalid statuses are ignored rather than broadening the contract.
+
+An evidence record may contain:
+
+```json
+{
+  "status": "PASS",
+  "reason_code": "CI_GREEN",
+  "evidence_source": "github-actions",
+  "evidence_ref": "run-123"
+}
+```
+
+The matrix does not fetch or trust arbitrary remote data by itself. Loading and authenticating an evidence source is the responsibility of the higher layer that calls the builder.

package/docs/ui-surfaces.md

@@ -1,107 +1,107 @@
-# 3210 and 3080 UI responsibilities
-
-The desktop entry opens the official frontend with a simple Crew panel on 3080. Crew runs hidden on 3210;
-its web page is an explicit advanced-settings entry, not the default browser tab.
-The background watcher manages only 3210. Desktop launch may start the official
-program but never uses it as authority to restart, update or roll back Crew.
-The simple panel is mounted through a `--patch` file under the Crew-owned home,
-with immutable frontend revisions kept independently of backend release cleanup.
-The 3080 button opens 3210; the 3210 button opens 3080.
-
-DSH Crew is a plugin attached to the official DeepSeek Harness. Current installs
-register it in a dedicated official Harness `dsh-crew` profile whose native 3210
-page is the canonical full Crew control and execution surface. An older
-installation may still expose a narrow 3080 quick-controls bundle, but that
-legacy surface is external to Crew ownership, optional, and deprecated. Crew
-treats the official profile as read-only. The legacy surface
-never starts, owns, or supervises 3210.
-
-## 3210: official Harness profile with the Crew plugin
-
-The Crew-owned official Harness `dsh-crew` profile on `127.0.0.1:3210` loads the
-DSH Crew plugin and owns day-to-day Crew management and model execution:
-
-- Crew workflow and global enablement
-- Worker and Reviewer policy
-- model priority, fallback, review, and adaptive routing
-- multimodal (vision/imagegen) capability switches
-- providers lifecycle (migrate/delete/rollback/quarantine)
-- credential references lifecycle
-- workspaces, presets, jobs
-- installation integrations (Codex, Claude, ZCode)
-- task status and bounded model-invocation summaries
-
-Bundle: `lib/client.js` (module `@ran-sh/dsh-crew`), built from
-`src/client/entry.tsx`.
-
-## 3080: official frontend; optional legacy Crew controls
-
-An older official Harness `web` profile on `127.0.0.1:3080` may still host a
-NARROW quick-controls card — and nothing else:
-
-- master switch (`subagents_enabled`)
-- Flash / Pro model priority lists (add/remove/reorder only)
-- vision / imagegen toggles + providers (restart-pending flow)
-- deep link to the 3210 full control plane (`http://127.0.0.1:3210/`)
-
-Bundle: `official-web-bridge/lib/client.js` (module
-`@ran-sh/dsh-crew-web-bridge`), built from `src/client/quick-entry.tsx`.
-It physically contains none of the full control-plane code (no credential
-purge, no provider delete/migration, no install integration).
-
-The 3080 bridge proxies ONLY two exact endpoints to 3210:
-`quick-config` and `quick-status`. Restart and rollback belong to 3210;
-the quick panel links there when needed. Everything else on the Crew namespace is 404 on
-3080, and `/supervisor/restart` returns 410 Gone pointing at 3210.
-
-The official `~/.dsh` tree is strictly read-only for Crew; the 3080 quick
-surface itself is optional — Crew works fully with 3080 closed.
-
-## UNKNOWN: diagnostics only
-
-Unknown surfaces render diagnostics and never gain write authority.
-
-## Surface detection and failure behavior
-
-The client does not infer responsibility from a hard-coded browser port. It
-uses two same-origin, structured signals:
-
-1. `/_dsh/dsh-crew/bridge-status` identifies the official quick bridge.
-2. `/_dsh/dsh-crew/runtime` identifies the native Crew-owned runtime.
-
-The bridge signal wins on 3080 because the proxied runtime response correctly
-describes the 3210 backend. If neither contract can be verified, the client
-fails closed to the diagnostics view. Missing evidence never enables the
-full control plane and never becomes `READY`.
-
-The split changes presentation only. Crew state, credentials, routing policy,
-and model execution remain isolated under the Crew-owned home and profile.
-
-## Local trust model
-
-Both surfaces listen on loopback only and share one request guard
-(`src/local-request-guard.mjs`). A request is trusted when it proves, in
-order: (1) the TCP peer is a loopback address, (2) the `Host` header names a
-loopback host, (3) browser fetch-metadata (`Sec-Fetch-Site`) is `same-origin`
-or absent/`none`, and (4) when an `Origin` header is present it names a
-loopback host — on the 3080 bridge the `Origin` authority must additionally
-equal the request authority, while the 3210 hub accepts any loopback origin
-because the 3080 panel calls it cross-port.
-
-There is deliberately no bearer token: every process running as the local
-user is inside the trust boundary and may control Crew. The guards keep
-off-machine browsers, DNS-rebinding pages, and cross-machine proxies out;
-they do not authenticate local users. If a deployment ever needs to separate
-local principals, add a per-install random token to state-changing calls and
-inject it server-side in the bridge — do not use browser `Origin` as
-authentication.
-
-## Process ownership
-
-The Windows launcher supervisor (`windows/start-dsh-crew.ps1` watch mode) is
-the ONLY process authority for the Crew-owned 3210 service. The official 3080
-surface never starts, owns, or supervises 3210. Restart and maintenance go
-through durable request files the hub writes and the launcher executes
-(`supervisor/restart-request.mjs`). Ordinary backend startup does not probe the
-legacy bridge. Desktop opening uses the official process and root HTTP response,
-independently of whether that process has any Crew plugin installed.
+# 3210 and 3080 UI responsibilities
+
+The desktop entry opens the official frontend with a simple Crew panel on 3080. Crew runs hidden on 3210;
+its web page is an explicit advanced-settings entry, not the default browser tab.
+The background watcher manages only 3210. Desktop launch may start the official
+program but never uses it as authority to restart, update or roll back Crew.
+The simple panel is mounted through a `--patch` file under the Crew-owned home,
+with immutable frontend revisions kept independently of backend release cleanup.
+The 3080 button opens 3210; the 3210 button opens 3080.
+
+DSH Crew is a plugin attached to the official DeepSeek Harness. Current installs
+register it in a dedicated official Harness `dsh-crew` profile whose native 3210
+page is the canonical full Crew control and execution surface. An older
+installation may still expose a narrow 3080 quick-controls bundle, but that
+legacy surface is external to Crew ownership, optional, and deprecated. Crew
+treats the official profile as read-only. The legacy surface
+never starts, owns, or supervises 3210.
+
+## 3210: official Harness profile with the Crew plugin
+
+The Crew-owned official Harness `dsh-crew` profile on `127.0.0.1:3210` loads the
+DSH Crew plugin and owns day-to-day Crew management and model execution:
+
+- Crew workflow and global enablement
+- Worker and Reviewer policy
+- model priority, fallback, review, and adaptive routing
+- multimodal (vision/imagegen) capability switches
+- providers lifecycle (migrate/delete/rollback/quarantine)
+- credential references lifecycle
+- workspaces, presets, jobs
+- installation integrations (Codex, Claude, ZCode)
+- task status and bounded model-invocation summaries
+
+Bundle: `lib/client.js` (module `@ran-sh/dsh-crew`), built from
+`src/client/entry.tsx`.
+
+## 3080: official frontend; optional legacy Crew controls
+
+An older official Harness `web` profile on `127.0.0.1:3080` may still host a
+NARROW quick-controls card — and nothing else:
+
+- master switch (`subagents_enabled`)
+- Flash / Pro model priority lists (add/remove/reorder only)
+- vision / imagegen toggles + providers (restart-pending flow)
+- deep link to the 3210 full control plane (`http://127.0.0.1:3210/`)
+
+Bundle: `official-web-bridge/lib/client.js` (module
+`@ran-sh/dsh-crew-web-bridge`), built from `src/client/quick-entry.tsx`.
+It physically contains none of the full control-plane code (no credential
+purge, no provider delete/migration, no install integration).
+
+The 3080 bridge proxies ONLY two exact endpoints to 3210:
+`quick-config` and `quick-status`. Restart and rollback belong to 3210;
+the quick panel links there when needed. Everything else on the Crew namespace is 404 on
+3080, and `/supervisor/restart` returns 410 Gone pointing at 3210.
+
+The official `~/.dsh` tree is strictly read-only for Crew; the 3080 quick
+surface itself is optional — Crew works fully with 3080 closed.
+
+## UNKNOWN: diagnostics only
+
+Unknown surfaces render diagnostics and never gain write authority.
+
+## Surface detection and failure behavior
+
+The client does not infer responsibility from a hard-coded browser port. It
+uses two same-origin, structured signals:
+
+1. `/_dsh/dsh-crew/bridge-status` identifies the official quick bridge.
+2. `/_dsh/dsh-crew/runtime` identifies the native Crew-owned runtime.
+
+The bridge signal wins on 3080 because the proxied runtime response correctly
+describes the 3210 backend. If neither contract can be verified, the client
+fails closed to the diagnostics view. Missing evidence never enables the
+full control plane and never becomes `READY`.
+
+The split changes presentation only. Crew state, credentials, routing policy,
+and model execution remain isolated under the Crew-owned home and profile.
+
+## Local trust model
+
+Both surfaces listen on loopback only and share one request guard
+(`src/local-request-guard.mjs`). A request is trusted when it proves, in
+order: (1) the TCP peer is a loopback address, (2) the `Host` header names a
+loopback host, (3) browser fetch-metadata (`Sec-Fetch-Site`) is `same-origin`
+or absent/`none`, and (4) when an `Origin` header is present it names a
+loopback host — on the 3080 bridge the `Origin` authority must additionally
+equal the request authority, while the 3210 hub accepts any loopback origin
+because the 3080 panel calls it cross-port.
+
+There is deliberately no bearer token: every process running as the local
+user is inside the trust boundary and may control Crew. The guards keep
+off-machine browsers, DNS-rebinding pages, and cross-machine proxies out;
+they do not authenticate local users. If a deployment ever needs to separate
+local principals, add a per-install random token to state-changing calls and
+inject it server-side in the bridge — do not use browser `Origin` as
+authentication.
+
+## Process ownership
+
+The Windows launcher supervisor (`windows/start-dsh-crew.ps1` watch mode) is
+the ONLY process authority for the Crew-owned 3210 service. The official 3080
+surface never starts, owns, or supervises 3210. Restart and maintenance go
+through durable request files the hub writes and the launcher executes
+(`supervisor/restart-request.mjs`). Ordinary backend startup does not probe the
+legacy bridge. Desktop opening uses the official process and root HTTP response,
+independently of whether that process has any Crew plugin installed.

package/official-web-bridge/cordis.patch.yml

@@ -1,4 +1,4 @@
-# Lightweight official-web bridge. The full Crew Hub remains isolated on 3210.
-- insert:
-    - id: dsh-crew-official-web-bridge
-      name: '@ran-sh/dsh-crew-web-bridge'
+# Lightweight official-web bridge. The full Crew Hub remains isolated on 3210.
+- insert:
+    - id: dsh-crew-official-web-bridge
+      name: '@ran-sh/dsh-crew-web-bridge'

package/official-web-bridge/entry.mjs

@@ -1 +1 @@
-export { apply, registerOfficialWebBridge } from '../src/official-web-bridge.mjs';
+export { apply, registerOfficialWebBridge } from '../src/official-web-bridge.mjs';

package/official-web-bridge/overlay-entry.mjs

@@ -1,59 +1,59 @@
-// UI-only overlay host. No process lifecycle, installer or profile mutations.
-import { localRequestCore, originAuthorityMatches } from '../src/local-request-guard.mjs';
-import { readFileSync } from 'node:fs';
-
-const PREFIX = '/_dsh/dsh-crew';
-const BACKEND = 'http://127.0.0.1:3210';
-const REVISION = JSON.parse(readFileSync(new URL('./package.json', import.meta.url), 'utf8')).dshCrewFrontendRevision ?? null;
-
-function trusted(req) {
-  return localRequestCore(req) && (req.headers.origin === undefined
-    || originAuthorityMatches(req.headers.origin, req.headers.host));
-}
-
-function send(res, status, body) {
-  res.writeHead(status, { 'content-type': 'application/json; charset=utf-8', 'cache-control': 'no-store' });
-  res.end(JSON.stringify(body));
-}
-
-export function registerFrontend(ctx, { fetchImpl = globalThis.fetch } = {}) {
-  return ctx.inject(['webServer'], ({ webServer }) => {
-    const disposers = [];
-    disposers.push(webServer.register({ kind: 'exact', path: `${PREFIX}/bridge-status`, handler(req, res) {
-      if (!trusted(req)) return send(res, 403, { ok: false, code: 'LOCAL_SAME_ORIGIN_ONLY' });
-      send(res, 200, { ok: true, surface: 'official-bridge', ui_role: 'quick-controls', frontend_revision: REVISION, full_control_plane_url: `${BACKEND}/` });
-    } }));
-    for (const suffix of ['/quick-config', '/quick-status']) {
-      disposers.push(webServer.register({ kind: 'exact', path: `${PREFIX}${suffix}`, async handler(req, res) {
-        if (!trusted(req)) return send(res, 403, { ok: false, code: 'LOCAL_SAME_ORIGIN_ONLY' });
-        const method = req.method ?? 'GET';
-        if (method !== 'GET' && !(suffix === '/quick-config' && method === 'POST')) return send(res, 405, { ok: false, code: 'METHOD_NOT_ALLOWED' });
-        try {
-          const identityResponse = await fetchImpl(`${BACKEND}${PREFIX}/runtime`, { signal: AbortSignal.timeout(2500) });
-          const identity = await identityResponse.json();
-          if (!identityResponse.ok || identity.ok !== true || identity.service !== 'dsh-crew-hub'
-            || identity.profile !== 'dsh-crew' || identity.execution_plane !== 'hub-3210'
-            || identity.listen_port !== 3210 || identity.protocol_version !== 1) throw new Error('incompatible backend');
-          const chunks = [];
-          let size = 0;
-          if (method === 'POST') for await (const chunk of req) {
-            size += chunk.length;
-            if (size > 64 * 1024) return send(res, 413, { ok: false, code: 'BODY_TOO_LARGE' });
-            chunks.push(Buffer.from(chunk));
-          }
-          const response = await fetchImpl(`${BACKEND}${PREFIX}${suffix}`, {
-            method, headers: { 'content-type': 'application/json' },
-            ...(method === 'POST' ? { body: Buffer.concat(chunks) } : {}),
-            signal: AbortSignal.timeout(5000),
-          });
-          send(res, response.status, await response.json());
-        } catch {
-          send(res, 503, { ok: false, ready: false, code: 'CREW_BACKEND_UNAVAILABLE' });
-        }
-      } }));
-    }
-    return () => { for (const dispose of disposers) dispose?.(); };
-  });
-}
-
-export function apply(ctx) { registerFrontend(ctx); }
+// UI-only overlay host. No process lifecycle, installer or profile mutations.
+import { localRequestCore, originAuthorityMatches } from '../src/local-request-guard.mjs';
+import { readFileSync } from 'node:fs';
+
+const PREFIX = '/_dsh/dsh-crew';
+const BACKEND = 'http://127.0.0.1:3210';
+const REVISION = JSON.parse(readFileSync(new URL('./package.json', import.meta.url), 'utf8')).dshCrewFrontendRevision ?? null;
+
+function trusted(req) {
+  return localRequestCore(req) && (req.headers.origin === undefined
+    || originAuthorityMatches(req.headers.origin, req.headers.host));
+}
+
+function send(res, status, body) {
+  res.writeHead(status, { 'content-type': 'application/json; charset=utf-8', 'cache-control': 'no-store' });
+  res.end(JSON.stringify(body));
+}
+
+export function registerFrontend(ctx, { fetchImpl = globalThis.fetch } = {}) {
+  return ctx.inject(['webServer'], ({ webServer }) => {
+    const disposers = [];
+    disposers.push(webServer.register({ kind: 'exact', path: `${PREFIX}/bridge-status`, handler(req, res) {
+      if (!trusted(req)) return send(res, 403, { ok: false, code: 'LOCAL_SAME_ORIGIN_ONLY' });
+      send(res, 200, { ok: true, surface: 'official-bridge', ui_role: 'quick-controls', frontend_revision: REVISION, full_control_plane_url: `${BACKEND}/` });
+    } }));
+    for (const suffix of ['/quick-config', '/quick-status']) {
+      disposers.push(webServer.register({ kind: 'exact', path: `${PREFIX}${suffix}`, async handler(req, res) {
+        if (!trusted(req)) return send(res, 403, { ok: false, code: 'LOCAL_SAME_ORIGIN_ONLY' });
+        const method = req.method ?? 'GET';
+        if (method !== 'GET' && !(suffix === '/quick-config' && method === 'POST')) return send(res, 405, { ok: false, code: 'METHOD_NOT_ALLOWED' });
+        try {
+          const identityResponse = await fetchImpl(`${BACKEND}${PREFIX}/runtime`, { signal: AbortSignal.timeout(2500) });
+          const identity = await identityResponse.json();
+          if (!identityResponse.ok || identity.ok !== true || identity.service !== 'dsh-crew-hub'
+            || identity.profile !== 'dsh-crew' || identity.execution_plane !== 'hub-3210'
+            || identity.listen_port !== 3210 || identity.protocol_version !== 1) throw new Error('incompatible backend');
+          const chunks = [];
+          let size = 0;
+          if (method === 'POST') for await (const chunk of req) {
+            size += chunk.length;
+            if (size > 64 * 1024) return send(res, 413, { ok: false, code: 'BODY_TOO_LARGE' });
+            chunks.push(Buffer.from(chunk));
+          }
+          const response = await fetchImpl(`${BACKEND}${PREFIX}${suffix}`, {
+            method, headers: { 'content-type': 'application/json' },
+            ...(method === 'POST' ? { body: Buffer.concat(chunks) } : {}),
+            signal: AbortSignal.timeout(5000),
+          });
+          send(res, response.status, await response.json());
+        } catch {
+          send(res, 503, { ok: false, ready: false, code: 'CREW_BACKEND_UNAVAILABLE' });
+        }
+      } }));
+    }
+    return () => { for (const dispose of disposers) dispose?.(); };
+  });
+}
+
+export function apply(ctx) { registerFrontend(ctx); }

package/official-web-bridge/package.json

@@ -1,25 +1,25 @@
-{
-  "name": "@ran-sh/dsh-crew-web-bridge",
-  "version": "0.3.8",
-  "private": true,
-  "type": "module",
-  "main": "./entry.mjs",
-  "exports": {
-    ".": "./entry.mjs",
-    "./client": "./lib/client.js",
-    "./package.json": "./package.json"
-  },
-  "dsh": {
-    "bundle": {
-      "patch": "./cordis.patch.yml"
-    },
-    "client": {
-      "inject": [
-        "@deepseek-ai/dsh-client-ui-renderer",
-        "@deepseek-ai/dsh-client-locale",
-        "@deepseek-ai/dsh-client-ui-settings"
-      ],
-      "platform": "web"
-    }
-  }
-}
+{
+  "name": "@ran-sh/dsh-crew-web-bridge",
+  "version": "0.3.8",
+  "private": true,
+  "type": "module",
+  "main": "./entry.mjs",
+  "exports": {
+    ".": "./entry.mjs",
+    "./client": "./lib/client.js",
+    "./package.json": "./package.json"
+  },
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    },
+    "client": {
+      "inject": [
+        "@deepseek-ai/dsh-client-ui-renderer",
+        "@deepseek-ai/dsh-client-locale",
+        "@deepseek-ai/dsh-client-ui-settings"
+      ],
+      "platform": "web"
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ran-sh/dsh-crew",
-  "version": "1.9.0",
+  "version": "1.10.0",
   "type": "module",
   "main": "./src/hub/entry.mjs",
   "bin": {
@@ -29,7 +29,8 @@
     "build:client": "tsdown src/client/entry.tsx --format cjs --platform browser --target es2022 --tsconfig tsconfig.client.json --deps.never-bundle react --deps.never-bundle react/jsx-runtime --deps.never-bundle react-dom --deps.never-bundle react-dom/client --out-dir .client-build --clean --logLevel warn && tsdown src/client/quick-entry.tsx --format cjs --platform browser --target es2022 --tsconfig tsconfig.client.json --deps.never-bundle react --deps.never-bundle react/jsx-runtime --deps.never-bundle react-dom --deps.never-bundle react-dom/client --out-dir .client-build --no-clean --logLevel warn && node scripts/build-client.mjs",
     "verify:npm-install": "node scripts/verify-npm-install.mjs",
     "verify:npm-install:official": "node scripts/verify-npm-install.mjs --with-official-dsh",
-    "verify:official-bridge": "node scripts/verify-official-bridge-e2e.mjs --diagnostic-only"
+    "verify:official-bridge": "node scripts/verify-official-bridge-e2e.mjs --diagnostic-only",
+    "test": "node --test \"test/*.test.mjs\""
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.25.4",