@ran-sh/dsh-crew 0.4.2 → 0.5.0

package/README.md

@@ -22,7 +22,9 @@ Start the official Harness on port 3080 as usual:
 npx -y @deepseek-ai/dsh web --host 127.0.0.1 --port 3080
 ```
 
-Open <http://127.0.0.1:3080> and go to **Settings → DSH Crew**. The official 3080 process displays the UI; Crew work stays in an isolated backend on `127.0.0.1:3210`, which the bridge starts in the background when needed.
+Open <http://127.0.0.1:3080> and go to the single **Settings → DSH Crew** entry. The official 3080 process is the daily console; Crew work stays in the isolated backend at `127.0.0.1:3210`. Use **Open 3210 Crew Harness →** only for low-level Provider and Harness Model settings.
+
+The shared client is surface-aware: 3080 renders the complete Crew control plane, host readiness, and task status; 3210 renders only a minimal Crew runtime panel while its native Harness menus continue to own Providers, Harness Models, Agent presets, and low-level settings. Detection uses the structured bridge/runtime endpoints, not a hard-coded browser port, and fails closed when evidence is missing. See [UI surface architecture](./docs/ui-surfaces.md).
 
 ## Configure
 
@@ -32,7 +34,7 @@ Open <http://127.0.0.1:3080> and go to **Settings → DSH Crew**. The official 3
 4. Reviewer defaults to **Manual**; enable automatic review only when wanted.
 5. Keep **worktree** isolation for coding tasks.
 
-With one configured model, both roles simply use that model. With several models, each role tries its ordered list and falls back to the next available model. Settings modules are collapsible and show their effective state while closed.
+With one configured model, both roles simply use that model. With several models, each role tries its ordered list and falls back to the next available model. Settings modules are collapsible and show their effective state while closed. The task section shows a compact Worker/Reviewer table plus process-local model call counts, sources, and last-call times; prompts, results, and credentials are not collected for this overview.
 
 ## Use from Codex or Claude
 
@@ -102,7 +104,7 @@ pnpm run build:client
 node scripts/setup.mjs uninstall
 ```
 
-More detail: [Changelog](./CHANGELOG.md) · [Readiness matrix](./docs/readiness-matrix.md) · [Job contracts](./docs/job-contracts.md)
+More detail: [Changelog](./CHANGELOG.md) · [UI surfaces](./docs/ui-surfaces.md) · [Readiness matrix](./docs/readiness-matrix.md) · [Job contracts](./docs/job-contracts.md)
 · [GPT-first extension](./docs/gpt-relay-extension.md)
 
 ## License

package/README.zh.md

@@ -22,7 +22,9 @@ dsh-crew integrate
 npx -y @deepseek-ai/dsh web --host 127.0.0.1 --port 3080
 ```
 
-打开 <http://127.0.0.1:3080>，进入 **设置 → DSH Crew**。3080 只显示官方界面；Crew 的任务与模型执行继续隔离在 `127.0.0.1:3210`，需要时由桥接在后台自动启动。
+打开 <http://127.0.0.1:3080>，进入唯一的 **设置 → DSH Crew**。3080 是日常控制台；Crew 的任务与模型执行继续隔离在 `127.0.0.1:3210`。只有配置底层 Provider 和 Harness Models 时才点击“打开 3210 Crew Harness →”。
+
+共享客户端会识别当前 surface：3080 显示完整 Crew 控制面、宿主就绪度和任务状态；3210 的 DSH Crew 入口只显示最小运行时诊断，Provider、Harness Models、Agent 预设和底层设置仍由 Harness 原生菜单管理。识别依赖结构化 bridge/runtime 接口，不硬编码浏览器端口；证据缺失时会保守隐藏控制面。详见 [UI surface 架构](./docs/ui-surfaces.md)。
 
 ## 配置
 
@@ -32,7 +34,7 @@ npx -y @deepseek-ai/dsh web --host 127.0.0.1 --port 3080
 4. Reviewer 默认 **Manual**；确实需要自动复审时再开启。
 5. 编码任务建议保持 **worktree** 隔离。
 
-只配置一个模型时，两个角色直接使用它。配置多个模型时，每个角色按自己的排序调用，失败后依次回退。设置模块可以展开/收起，收起后仍显示当前状态。
+只配置一个模型时，两个角色直接使用它。配置多个模型时，每个角色按自己的排序调用，失败后依次回退。设置模块可以展开/收起，收起后仍显示当前状态。任务区用紧凑表格显示 Worker/Reviewer，并聚合当前进程内的模型调用次数、来源和最近调用时间；不会为此采集提示词、结果或凭据。
 
 ## 在 Codex 或 Claude 中使用
 
@@ -101,7 +103,7 @@ pnpm run build:client
 node scripts/setup.mjs uninstall
 ```
 
-更多资料：[Changelog](./CHANGELOG.md) · [Readiness Matrix](./docs/readiness-matrix.md) · [任务契约](./docs/job-contracts.md)
+更多资料：[Changelog](./CHANGELOG.md) · [UI surfaces](./docs/ui-surfaces.md) · [Readiness Matrix](./docs/readiness-matrix.md) · [任务契约](./docs/job-contracts.md)
 · [GPT-first 扩展接入](./docs/gpt-relay-extension.md)
 
 ## License

package/docs/ui-surfaces.md

@@ -0,0 +1,47 @@
+# 3080 and 3210 UI responsibilities
+
+DSH Crew deliberately presents two different user experiences from one shared
+client build.
+
+## 3080: daily Crew control plane
+
+The official Harness `web` profile on `127.0.0.1:3080` owns day-to-day Crew
+management:
+
+- Crew workflow and global enablement
+- Worker and Reviewer policy
+- model priority, fallback, review, and adaptive routing
+- runtime and activation-boundary information
+- Codex and Claude installation actions and structured readiness
+- task status and bounded model-invocation summaries
+- the link to the underlying 3210 Crew Harness
+
+The lightweight official-web bridge keeps these requests same-origin and
+proxies only the `/_dsh/dsh-crew/*` contract to the isolated backend.
+
+## 3210: isolated native Harness
+
+The Crew-owned `dsh-crew` profile on `127.0.0.1:3210` owns model execution and
+low-level Harness configuration. Its native Harness menus remain the place for
+Providers, Harness Models, Agent presets, and native runtime settings.
+
+The DSH Crew settings entry on this surface is intentionally diagnostics-only:
+it shows bounded runtime identity and a link back to 3080. It does not duplicate
+Worker/Reviewer policy, host integrations, tasks, or orchestration controls.
+
+## 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 bridge control plane.
+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 minimal 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.
+