Merge branch 'master' into claude/unified-environment-credentials-c8841a

Master removed the TUI package, the `meta` and `upgrade` subcommands, and
`--config-replace`, and made raw `dsh` require a `--config` overlay. Resolved
onto that shape:

- Dropped this branch's TUI edits with the surface itself, including
  `tui.cordis.yml`, `runTui`, and the TUI keyless PTY smoke.
- Dropped the `--config-replace` plumbing rather than reintroducing a flag
  master deliberately removed. The gap this branch fixed remains: `dsh -p`
  still could not name its composition, so it keeps `--config`.
- Kept this branch's deletion of the personal `$DSH_HOME/config.yaml` layer,
  which master still carried, and provided the environment snapshot in the new
  raw `runConfig` surface alongside web and headless.
- Ported the headless shutdown PTY test off the personal overlay onto a named
  `--config` file, which is what proves that flag now exists on `-p`.

docs/user/guide/config.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 docs/user/guide/config.md
-config.md: b1cf3a57b2fd16d4139f1a11a6cd85e54bb957b5
-config.zh.md: dad03d8232851678cfb6dc690f0bbd3f02380fc8
+config.md: 580c62be717efcca3ff5cd01d144722fba703051
+config.zh.md: 7621c846d706e661c118786e34b55cdf23bf730e

docs/user/guide/config.md

@@ -8,7 +8,8 @@ Harness uses `cordis.yml` to describe which plugins an agent loads and the confi
 
 The repository examples are runnable configurations and the most reliable starting points for a new project:
 
-- [the shared `dsh` base](../../../apps/cli/config/base.cordis.yml) plus the [`tui.cordis.yml`](../../../apps/cli/config/tui.cordis.yml) overlay combines the DeepSeek model, Bash, filesystem, compaction, subagents, workflows, and the interactive TUI.
+- [the shared `dsh` base](../../../apps/cli/config/base.cordis.yml) provides the common model, tools, persistence, policy, and telemetry rows; raw `dsh --config <path>` requires a patch list that selects deployment-specific agents and front doors.
+- [the Web overlay](../../../apps/cli/config/web.cordis.yml) adds the browser host, Workspace management, browser interaction, and client plugins.
 - [headless-agent](../../../examples/headless-agent/cordis.yml) exposes the coding composition as a one-shot task.
 - [acp-agent](../../../examples/acp-agent/cordis.yml) exposes fresh sessions to programmatic ACP clients.
 
@@ -50,7 +51,7 @@ Plugins load in file order. Place plugins that depend on services after the appl
 
 ## CLI overlays
 
-The TUI composes `base.cordis.yml` and `tui.cordis.yml`, then applies the optional `dsh --config <path>` overlay. `dsh --config-replace <path>` instead boots the named file as the complete tree, without any shipped layer. Every booting surface takes both flags — `dsh -p`, `dsh web`, `dsh meta`, and `dsh upgrade` included — because naming a file is the only way to compose your own tree.
+Raw `dsh --config <path>` requires a patch list and applies it directly over `base.cordis.yml`; the named file is not a complete replacement tree. `dsh web` and `dsh -p` compose `base.cordis.yml` and `web.cordis.yml`, then any `--config <path>` overlay, then the launcher's own CLI-flag patches. No overlay is discovered on disk: naming a file is the only way to compose your own tree, and `dsh -p` accepts `--config` for exactly that reason.
 
 A patch replaces a row's entire `config` value; it does not deep-merge keys. For example, patching `llm-deepseek` with only `config: { thinking: disabled }` also removes that row's configured `apiKey` and `baseURL`, so restate every key the row must retain.
 

docs/user/guide/config.zh.md

@@ -8,7 +8,8 @@ Harness 使用 `cordis.yml` 描述 Agent 加载哪些插件以及每个插件的
 
 仓库中的示例就是可以运行的配置，也是新项目最可靠的起点：
 
-- [共享的 `dsh` base](../../../apps/cli/config/base.cordis.yml) 叠加 [`tui.cordis.yml`](../../../apps/cli/config/tui.cordis.yml) overlay，组合 DeepSeek 模型、Bash、文件系统、压缩、子代理、工作流和交互式 TUI。
+- [共享的 `dsh` base](../../../apps/cli/config/base.cordis.yml) 提供通用的模型、工具、持久化、策略与遥测配置项；原始 `dsh --config <path>` 要求传入一份 patch 列表，用于选择部署特定的 agent 和前端入口。
+- [Web overlay](../../../apps/cli/config/web.cordis.yml) 添加浏览器宿主、Workspace 管理、浏览器交互与客户端插件。
 - [headless-agent](../../../examples/headless-agent/cordis.yml) 以单次任务形式暴露 coding 组装。
 - [acp-agent](../../../examples/acp-agent/cordis.yml) 向程序化 ACP（Agent Client Protocol）客户端提供全新会话。
 
@@ -50,7 +51,7 @@ Harness 使用 `cordis.yml` 描述 Agent 加载哪些插件以及每个插件的
 
 ## CLI 覆盖层
 
-TUI 先组合 `base.cordis.yml` 与 `tui.cordis.yml`，再应用可选的 `dsh --config <path>` 覆盖。`dsh --config-replace <path>` 则把指定文件作为完整配置树启动，不使用任何已交付层。每个会启动的界面都接受这两个标志，包括 `dsh -p`、`dsh web`、`dsh meta` 和 `dsh upgrade`——因为点名一个文件是组合自己配置树的唯一途径。
+裸 `dsh --config <path>` 要求给出一个补丁列表，并将其直接应用在 `base.cordis.yml` 之上；指定的文件不是完整的替换树。`dsh web` 与 `dsh -p` 组合 `base.cordis.yml` 与 `web.cordis.yml`，随后是任何 `--config <path>` 覆盖，最后是启动器自身的命令行标志补丁。磁盘上不会自动发现任何覆盖：点名一个文件是组合自己配置树的唯一途径，`dsh -p` 接受 `--config` 正是为此。
 
 补丁会替换目标行的整个 `config` 值，而不是深度合并各个键。例如，只用 `config: { thinking: disabled }` 修补 `llm-deepseek`，也会移除该行原有的 `apiKey` 与 `baseURL`；因此必须重新写出该行需要保留的全部键。
 

docs/user/guide/index.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 docs/user/guide/index.md
-index.md: cefb978019c21a24e9fb57f96ab8e0fee82dc812
-index.zh.md: 2f1298b5bf5ce44f7d653154b263cb533a3b3ba4
+index.md: 4bb9f2e0056792a160877515f142eb36d4f680ac
+index.zh.md: 2792547a146b5ca6186bcb69c1c026744e80b326

docs/user/guide/index.md

@@ -14,17 +14,13 @@ Harness implements every capability an AI agent needs—including LLM calls, too
   config:
     apiKey: !!js process.env.DEEPSEEK_API_KEY
 
-# Select the agent the interactive front door drives
-- id: agent-loop
-  name: '@deepseek-ai/dsh-agent-loop'
+# Select the one-shot application
+- id: cli-agent
+  name: '@deepseek-ai/dsh-cli-demo'
   config:
-    agents:
-      - id: main
-        provider: deepseek-official
-        model: deepseek-v4-flash
-
-# Select the interactive front door
-- name: '@deepseek-ai/dsh-tui'
+    provider: deepseek-official
+    model: deepseek-v4-flash
+    workspaceContext: false
 ```
 
 ## Who it is for

docs/user/guide/index.zh.md

@@ -14,17 +14,13 @@ Harness 将一个 AI Agent（智能体） 所需要的所有能力——LLM 调
   config:
     apiKey: !!js process.env.DEEPSEEK_API_KEY
 
-# Select the agent the interactive front door drives
-- id: agent-loop
-  name: '@deepseek-ai/dsh-agent-loop'
+# Select the one-shot application
+- id: cli-agent
+  name: '@deepseek-ai/dsh-cli-demo'
   config:
-    agents:
-      - id: main
-        provider: deepseek-official
-        model: deepseek-v4-flash
-
-# Select the interactive front door
-- name: '@deepseek-ai/dsh-tui'
+    provider: deepseek-official
+    model: deepseek-v4-flash
+    workspaceContext: false
 ```
 
 ## 适合谁

docs/user/guide/quickstart.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 docs/user/guide/quickstart.md
-quickstart.md: 1f01c7f4c9935c5a4772f6c702f023e691d911fc
-quickstart.zh.md: 8b5d4608525a603725136e1568aef7217756293f
+quickstart.md: 199b3f092159fa6fbaf3ae298151487c924ac6f1
+quickstart.zh.md: 9327ed646ba211bcce6426beb6bf76fca50acbf6

docs/user/guide/quickstart.md

@@ -40,19 +40,20 @@ pnpm run demo:headless "summarize the architecture of this workspace"
 
 Headless runs one complete model/tool turn, persists the session, prints the result, and exits. Use `--output-format stream-json` when you need the canonical event stream.
 
-## Step 3: use the TUI
+## Step 3: use the Web UI
 
-Start the interactive coding agent:
+Build and start the browser interface:
 
 ```sh
-pnpm run demo:tui
+pnpm run build
+pnpm run dsh web
 ```
 
-The full-screen agent can read and write files, run commands, delegate subtasks, and track a plan. Try: `Create hello.js in the current directory, print "Hello from Harness!", and run it`.
+Open `http://127.0.0.1:3080`. The agent can read and write files, run commands, delegate subtasks, and track a plan. Try: `Create hello.js in the current directory, print "Hello from Harness!", and run it`.
 
 ## What happened
 
-headless-agent uses the `@deepseek-ai/dsh-cli-demo` app; the interactive `dsh` surface instead composes [`apps/cli/config/base.cordis.yml`](../../../apps/cli/config/base.cordis.yml) with the `tui.cordis.yml` overlay and no app bundle. Both load the same providerless agent spine, while their `cordis.yml` files select the DeepSeek model and capability plugins appropriate to each surface.
+headless-agent uses the `@deepseek-ai/dsh-cli-demo` app. `dsh web` instead composes [`apps/cli/config/base.cordis.yml`](../../../apps/cli/config/base.cordis.yml) with [`apps/cli/config/web.cordis.yml`](../../../apps/cli/config/web.cordis.yml) and no app bundle. Both select the DeepSeek model and capability plugins appropriate to their entry mode.
 
 ## Next steps
 

docs/user/guide/quickstart.zh.md

@@ -40,19 +40,20 @@ pnpm run demo:headless "summarize the architecture of this workspace"
 
 Headless 运行一个完整的模型/工具轮次，持久化会话，打印结果后退出。需要规范事件流时可使用 `--output-format stream-json`。
 
-## 第三步：使用 TUI
+## 第三步：使用 Web UI
 
-启动交互式 coding agent：
+构建并启动浏览器界面：
 
 ```sh
-pnpm run demo:tui
+pnpm run build
+pnpm run dsh web
 ```
 
-这个全屏 Agent 可以读写文件、运行命令、分配子任务和跟踪计划。可以尝试：`Create hello.js in the current directory, print "Hello from Harness!", and run it`。
+打开 `http://127.0.0.1:3080`。agent 可以读写文件、运行命令、分配子任务和跟踪计划。可以尝试：`Create hello.js in the current directory, print "Hello from Harness!", and run it`。
 
 ## 回头看
 
-headless-agent 使用 `@deepseek-ai/dsh-cli-demo` app；交互式 `dsh` surface 则以 [`apps/cli/config/base.cordis.yml`](../../../apps/cli/config/base.cordis.yml) 叠加 `tui.cordis.yml` overlay 组合而成，不使用 app 组合包。二者加载同一个 providerless agent spine，并通过各自的 `cordis.yml` 为对应 surface 选择 DeepSeek 模型和能力插件。
+headless-agent 使用 `@deepseek-ai/dsh-cli-demo` app。`dsh web` 则组合 [`apps/cli/config/base.cordis.yml`](../../../apps/cli/config/base.cordis.yml) 与 [`apps/cli/config/web.cordis.yml`](../../../apps/cli/config/web.cordis.yml)，不使用 app 组合包。二者都会根据各自入口模式选择 DeepSeek 模型和能力插件。
 
 ## 下一步