dsh-any-agent 0.5.2 → 0.6.1

package/CHANGELOG.md

@@ -7,6 +7,143 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.1] — 2026-11-08
+
+### Added
+
+- **Live call-chain view of dispatched work.** The server now appends each
+  conversation's activity — run start/end (with how it was dispatched: send,
+  queue or interject, and which MCP client sent it), tool calls on status change,
+  approvals and their decisions — to `<state dir>/live/<conversation_id>/events.jsonl`.
+  Two new read-only subcommands show it without going through the calling agent:
+  `dsh-any-agent watch` (terminal tree) and `dsh-any-agent dashboard` (local page on
+  `127.0.0.1` with a one-time token and Host check, no controls). Both run as
+  separate processes, never touch the write lock, and merge conversations from
+  every client. `DSH_MCP_LIVE=detail|meta|off` (default `detail`: redacted
+  previews, the same exposure as sentinels) and `DSH_MCP_LIVE_DIR`. Reasoning is
+  never written; write failures never affect a run; files follow the sentinel
+  TTL and are deleted on `forget`. Design: `docs/zh/live-view-design.md`.
+
+## [0.6.0] — 2026-11-07
+
+### Added
+
+- **Zero-config DSH discovery, including the desktop app.** The server now finds
+  the DeepSeek Harness desktop app on its own (Windows uninstall registry via
+  `reg export`, plus default install paths on every platform), reads the CLI's
+  version and `engines` straight out of `resources/app.asar` with plain Node,
+  and launches it on the app's bundled Electron runtime in Node mode
+  (`ELECTRON_RUN_AS_NODE=1`). Previously only npx caches and npm global installs
+  were searched, so with the desktop app on 0.2.2-rc.1 the server silently ran a
+  stale 0.2.1-rc.5 from an npx cache. Candidates are ranked runnable-first →
+  newest → desktop > npm global > npx. `DSH_BIN` stays as an explicit override
+  (it may point inside an `.asar`); new `DSH_RUNTIME` overrides the launcher,
+  both with `DSH_BIN` and on its own for auto-discovered npm/npx installs (whose
+  `engines.node` is then re-checked against it); the desktop app always keeps its
+  bundled runtime.
+- `dsh_doctor`: `dsh_bin` shows the source and runtime; new `dsh_runtime`
+  (launcher's Node vs DSH's `engines.node` — 0.2.2 needs Node ≥ 24.9),
+  `dsh_desktop` (warns when the GUI and this server run different DSH versions
+  over the shared `~/.dsh`), and `dsh_candidates`.
+- Background receipts on Windows carry `sentinel_read_powershell`, a reader that
+  passes `-Encoding UTF8` (Windows PowerShell 5.1 otherwise misreads the BOM-less
+  sentinel and `ConvertFrom-Json` fails on CJK text).
+- `npm run lint` (`scripts/lint.mjs`, no npm dependencies): `node --check` on every
+  `.mjs`, relative import paths that resolve with exact case, named imports that
+  are real exports (including `await import()` destructuring and `node:`
+  builtins), and unused named imports. Runs first in every CI offline cell and at
+  the Node 22.15 floor; `test/lint.mjs` is its regression suite. Its first run
+  removed nine unused imports.
+- **Test counts in the docs are generated, not hand-edited.** `test/run.mjs`
+  writes a machine-readable report (`.state/test-report.json` by default,
+  `--report <path>`; per suite: passed/failed/skipped/duration, plus platform,
+  Node, DSH and client-fixture context), every suite prints a standard summary
+  line, and `npm run docs:counts` rewrites the per-suite counts, totals and the
+  CI scope comment from it; `npm run docs:counts:check` fails on any mismatch.
+  The CI offline job runs the check on the platform-independent suites, and the
+  release checklist includes it. Several hand-maintained numbers were wrong and
+  are corrected (e.g. failure-terminal 10, not 11).
+
+### Changed
+
+- **Internal: `src/hub.mjs` and `src/tools.mjs` are split into cohesive modules**
+  with no behaviour change. From `hub.mjs`: `conversation.mjs` (the `Conversation`
+  class), `git-snapshot.mjs`, `hub-store.mjs` (meta sidecar and forget
+  tombstones), `sentinel.mjs`, `workspace-guard.mjs`, `acp-session.mjs`. From
+  `tools.mjs`: `tool-defs.mjs`, `tool-render.mjs`, `doctor.mjs`. Both files
+  re-export every name they exported before, so existing import paths still work.
+- `model-suites` workflow finds DSH through the project's own `resolveDsh()`
+  (`scripts/detect-dsh.mjs`) instead of `command -v dsh`, so a self-hosted runner
+  with only the desktop app installed works without secrets; `DSH_BIN` stays an
+  optional override.
+- **`dsh-any-agent-workspaces --purge-test-sessions --ids …` now refuses
+  sessions whose cwd is not a test directory**, even when named explicitly, and
+  reports them as skipped. The purge also removes every artifact of a test
+  session (projection cache, registry entry, sentinels, reviews, locks), not
+  just its session directory.
+- Compatibility matrix: DSH 0.2.1-rc.5 and 0.2.2-rc.1 are **verified** (full
+  suites, 2026-11-06); 0.2.3+ is unverified.
+- Server `instructions` cut from ~4.4k to ~1.5k characters with the hard rules
+  first. Clients truncate long instructions (Claude Code dropped the old tail,
+  including the "don't" rules); `smoke` now enforces a 2400-character cap.
+- `node test/run.mjs` runs **every** suite and lists all failures at the end;
+  `--bail` restores stop-at-first-failure. One stale assertion used to hide the
+  eleven model-backed suites after it.
+
+### Fixed
+
+- **Test runs left residue in the real `~/.dsh`.** Purging a test session removed
+  only its session directory; the DSH projection cache
+  (`storages/session_projcache/sessions/<id>.json`) was never removed, so about
+  400 orphan files piled up, and the project's own `runs/`, `reviews/`, `meta/`,
+  `locks/` and registry entries leaked too (eight suites kept their state loose
+  under `%TEMP%`, where nothing cleaned it). Every model-backed suite now purges
+  exactly the sessions it created (plus DSH-spawned subagent sessions) with every
+  artifact in its own `finally`; `test/cleanup.mjs` is only the backstop and also
+  sweeps old orphans. The purge refuses any session whose cwd is not a test
+  directory, even when named by id, and no longer re-registers every temp session
+  on disk into the GUI workspace list as a side effect. New offline suite
+  `residue-purge` proves both halves in a sandboxed `DSH_HOME`. With
+  `DSH_MCP_KEEP_EVIDENCE=1`, `cleanup.mjs` now skips the whole sweep, so the
+  sessions and state directories that `acceptance` / `workspace-effect` keep for
+  inspection survive the end-of-run cleanup.
+- **`dsh_read` merged different tool calls into one entry.** Consecutive tool
+  updates in a turn were concatenated (`read [in_progress]read [completed]pwsh …`)
+  under the first call's `tool_call_id`. Each tool call now has its own entry and
+  a status update replaces it in place; only streamed text is still merged, so an
+  empty turn's start/end markers also stay separate. Because an in-place update
+  can give an earlier entry a higher revision, `dsh_read` now pages in revision
+  order (entries in a page are still returned in time order) so a small `limit`
+  can never skip an unread entry, and `gap` is computed from entries actually
+  evicted from the ring buffer instead of assuming revisions grow along it.
+- **`answer` ran message segments together.** Text DSH sends before and after a
+  tool call is two messages, but the collected answer joined them with no
+  separator (`…where possible.1) package.json…`). A blank line now separates a
+  segment that follows a tool call (none is added when the previous segment
+  already ends with a newline, or before the first text); `dsh_read` entries are
+  unchanged.
+- **A clean repository is a 0-change snapshot, not `null`.** `null` now only means
+  "no snapshot" (not a git repo, git unavailable, disabled). A turn that removed
+  the last change used to report `workspace_changed=true` with `diff_stat=null`.
+- **A cold `session/resume` that DSH never answers is retried once.** A live
+  `test/multi.mjs` run once hit `ACP request timed out: session/resume` (60 s of
+  silence from a freshly spawned DSH); a rerun passed and it did not reproduce in
+  ~70 controlled resume cycles, 40 of them under concurrent load. The write lock is
+  ruled out (DSH takes it with a zero-timeout wait and refuses instantly), so it
+  looks like a rare stall inside the DSH process. `resume` is idempotent and the
+  failure path already kills the process and waits for it to exit, so `ensureAlive`
+  now rebuilds the process and retries exactly once — only for a timeout, never for
+  a write-lock refusal or invalid params, and not on a shared host that still carries
+  other conversations. `AcpProcess` timeout errors now carry `code=ACP_TIMEOUT` and
+  `method`, and the DSH stderr tail at the moment of a timeout goes to the opt-in
+  `DSH_MCP_LOG_STDERR` log. New offline suite `resume-retry` (fake ACP server).
+- Tests: `timeout` asserts that a negative `timeout_ms` is rejected (the 0.4.0
+  behaviour) instead of the old "wait forever" semantics, and no longer passes on
+  an error result; `list` asserts caching via `probe_cached` instead of a 500 ms
+  wall-clock threshold; `integration`'s queue check uses a code token instead of
+  requiring the model to echo a phrase verbatim; `capability` prints the tool
+  error text when a call fails instead of an empty `err=`.
+
 ## [0.5.2] — 2026-11-05
 
 ### Fixed
@@ -1016,7 +1153,12 @@ First public release, published to npm as [`dsh-any-agent`](https://www.npmjs.co
   profiles, sessions and client configs. The product name changed; the on-disk
   contract did not. See the README FAQ.
 
-[Unreleased]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.3.9...HEAD
+[Unreleased]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.6.0...HEAD
+[0.6.0]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.5.2...v0.6.0
+[0.5.2]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.5.1...v0.5.2
+[0.5.1]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.5.0...v0.5.1
+[0.5.0]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.4.0...v0.5.0
+[0.4.0]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.3.9...v0.4.0
 [0.3.9]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.3.8...v0.3.9
 [0.3.8]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.3.7...v0.3.8
 [0.3.7]: https://github.com/xmtlzzz/dsh-any-agent/compare/v0.3.6...v0.3.7

package/USAGE-NOTES.en.md

@@ -24,7 +24,7 @@ Practical gotchas and trade-offs you *will* hit when letting Claude / Codex driv
 
 **1.4 Never register dsh-any-agent into DSH's own MCP list.** DSH is an MCP client, this server is an MCP server; pointing one at the other recurses forever.
 
-**1.5 `DSH CLI entry not found`.** Set `DSH_BIN` explicitly (auto-detection scans the npx cache, npm global, and common paths).
+**1.5 `DSH CLI entry not found`.** Auto-detection finds the DeepSeek Harness desktop app (Windows uninstall registry plus default install paths on every platform; the CLI inside `app.asar` runs on the app's bundled runtime), npm global installs and the npx cache. Check `dsh_candidates` in `dsh_doctor`; for portable or custom locations set `DSH_BIN` explicitly (it may point inside `app.asar`).
 
 ## 2. Cost and budget
 
@@ -94,6 +94,8 @@ Practical gotchas and trade-offs you *will* hit when letting Claude / Codex driv
 
 **6.3 Temp directories are skipped by default** (`DSH_MCP_REGISTER_WORKSPACE=project`) so test runs don't flood your GUI. Use `all` to include them.
 
+**6.4 Running the tests must not leave anything in `~/.dsh`.** Symptom: the session count under `~/.dsh` keeps growing, and `storages/session_projcache/sessions/` holds many orphan files whose session directories are long gone. Cause: model-backed tests use your real `~/.dsh` (the credentials live there, so it cannot be isolated), and the old cleanup removed the session directory but neither the projection cache nor this project's own `runs/reviews/meta/locks`. Now: every model-backed suite removes the sessions it created, with every artifact, in its own `finally`, and `node test/cleanup.mjs` is the global backstop. **Only sessions whose cwd is a test directory are ever deleted** — naming an id does not bypass that. See `docs/en/tests.md`.
+
 ## 7. Privacy
 
 **7.1 Silent by default** — not one byte. MCP's stdout is the protocol channel, and stderr lands in Claude/Codex's logs.

package/USAGE-NOTES.md

@@ -37,8 +37,10 @@
 
 ### 1.5 `DSH_BIN` 探测失败
 - **现象**：启动即报 `DSH CLI 入口未找到`。
-- **原因**：DSH 装在非常规位置（本服务按 npx 缓存 → npm 全局 → 常见路径的顺序通配搜索）。
-- **对策**：显式设置 `DSH_BIN=/path/to/node_modules/@deepseek-ai/dsh/lib/bin.js`。
+- **原因**：DSH 装在非常规位置。本服务自动识别 DeepSeek Harness 桌面版（Windows 卸载注册表 +
+  各平台默认安装位置，用桌面版自带运行时跑 asar 里的 CLI）、npm 全局安装和 npx 缓存。
+- **对策**：先跑 `dsh_doctor` 看 `dsh_candidates`；便携版/自定义位置再显式设置
+  `DSH_BIN=/path/to/node_modules/@deepseek-ai/dsh/lib/bin.js`（可指进 `app.asar` 内部）。
 
 ---
 
@@ -226,6 +228,11 @@
 - **原因**：跑测试会在 `%TEMP%` 下建一堆工作区，全登记会把你 GUI 灌满。
 - **对策**：默认模式 `project` 会跳过临时目录。要连临时目录一起登记就设 `DSH_MCP_REGISTER_WORKSPACE=all`。
 
+### 6.4 跑测试不该在 `~/.dsh` 里留东西
+- **现象**：`~/.dsh` 里会话数越攒越多；`storages/session_projcache/sessions/` 里有大量会话目录早已不在的孤儿文件。
+- **原因**：真机测试用的是你真实的 `~/.dsh`（凭据在那里，没法隔离）；旧版清理只删会话目录，不删投影缓存，也不清本项目自己的 `runs/reviews/meta/locks`。
+- **现状**：每个真机套件在 `finally` 里清掉自己造的会话及全部产物，全局 `node test/cleanup.mjs` 兜底；**只有 cwd 是测试目录的会话才会被删**，点名 id 也绕不过。详见 `docs/zh/tests.md`。
+
 ---
 
 ## 七、隐私与日志

package/bin/dsh-any-agent-workspaces.mjs

@@ -15,8 +15,11 @@
  *   node bin/dsh-any-agent-workspaces.mjs --purge-test-sessions [--dry-run] [--ids=a,b]
  *
  * 只有 --purge-test-sessions 会动磁盘上的会话文件，且规则很死：只删
- * "cwd 在 tmpdir()/dsh-any-agent-* 下" 或 "cwd 在 Desktop\dsh-any-agent-test-*" 的会话，
- * 外加 --ids 显式指定的。**不会**删除用户在 %TEMP% 里自己的真实项目会话。
+ * "cwd 在 tmpdir()/dsh-any-agent-* 下"、"cwd 在 Desktop\dsh-any-agent-test-A|B" 或本仓库
+ * ".state/ws-probe-*" 的会话。**不会**删除用户在 %TEMP% 里自己的真实项目会话。
+ * --ids=a,b 只清点名的那几个，但**点名也绕不过护栏**：cwd 不是测试目录的会被拒绝并列出。
+ * 每个被删会话的全部产物一并清掉（日志、投影缓存、工作区登记、墓碑，以及本项目的
+ * 注册表/元数据/哨兵/审核/锁登记）；另外清掉投影缓存里的测试孤儿。
  */
 
 import {
@@ -24,10 +27,10 @@ import {
   listWorkspaces,
   pruneEmptyWorkspaces,
   pruneTempWorkspaces,
-  purgeTestSessions,
   WORKSPACE_FILE,
   SESSIONS_ROOT,
 } from '../src/workspace.mjs';
+import { purgeTestResidue, sweepTestResidue } from '../src/residue.mjs';
 
 const argv = process.argv.slice(2);
 const has = (f) => argv.includes(f);
@@ -46,14 +49,18 @@ const ids = (val('--ids') ?? '').split(',').map((s) => s.trim()).filter(Boolean)
 
 // ── 清理测试会话（唯一会删文件的动作） ──────────────────────
 if (has('--purge-test-sessions')) {
-  const res = purgeTestSessions({ dryRun, ids, testOnly: true });
+  // 点名（--ids）= 只清这几个；否则全盘扫荡。两条路都会连带清本项目侧的 per-run 数据。
+  const full = ids.length ? purgeTestResidue({ ids, dryRun }) : sweepTestResidue({ dryRun });
+  const res = full.sessions;
   console.log(`${flag}清理测试会话：${res.count} 个`);
   for (const v of res.victims) {
     console.log(`  - ${v.id}  [${v.reason}]${v.origin ? ` origin=${v.origin}` : ''}  cwd=${v.cwd}`);
     if (v.error) console.log(`      ⚠️ 删除失败: ${v.error}`);
   }
+  for (const s of res.skipped ?? []) console.log(`  ✗ 拒绝 ${s.id}：${s.reason}  cwd=${s.cwd}`);
   if (!res.count) console.log('  （没有命中任何会话）');
-  if (!dryRun) console.log('  已同步从工作区注册表摘除这些会话 id');
+  if (!dryRun) console.log('  已同步清掉这些会话的投影缓存、工作区登记、墓碑与本项目 per-run 数据');
+  if (full.orphans) console.log(`${flag}  投影缓存测试孤儿：${full.orphans.count} 个`);
   console.log('');
 }
 

package/bin/dsh-any-agent.mjs

@@ -3,7 +3,8 @@
  * dsh-any-agent 入口：以 MCP stdio 服务端方式运行，用 DSH (ACP) 作为后端。
  *
  * 环境变量：
- *   DSH_BIN                     DSH CLI 入口（默认探测 npx 缓存位置）
+ *   DSH_BIN                     DSH CLI 入口（默认自动识别：桌面版 → npm 全局 → npx 缓存）
+ *   DSH_RUNTIME                 拉起 DSH 的可执行文件（默认：桌面版用其自带运行时，其余用本进程 node）
  *   DSH_MCP_PROFILE             驱动用的 DSH profile（默认 dsh-mcp）
  *   DSH_MCP_STATE               会话注册表路径（默认 $DSH_HOME/.dsh-any-agent/conversations.json）
  *   DSH_MCP_PERMISSION          新建会话的默认权限档（默认 danger-full-access）
@@ -38,6 +39,8 @@ if (argv.includes('--help') || argv.includes('-h')) {
     '  dsh-any-agent                 run the MCP server on stdio\n' +
     '  dsh-any-agent team on|off     enable/disable Agent Teams (writes settings.json)\n' +
     '  dsh-any-agent team status     show the effective team mode\n' +
+    '  dsh-any-agent watch [conv]    live call chain of dispatched runs in this terminal\n' +
+    '  dsh-any-agent dashboard       same, as a read-only local web page (127.0.0.1 + token)\n' +
     '  dsh-any-agent --version       print the version and exit\n' +
     '  dsh-any-agent --help          this text\n\n' +
     'Register it with your client:\n' +
@@ -45,16 +48,29 @@ if (argv.includes('--help') || argv.includes('-h')) {
     '  dsh-any-agent-setup --yes     apply\n\n' +
     'Key environment variables (all optional):\n' +
     '  DSH_BIN                  path to @deepseek-ai/dsh/lib/bin.js; auto-detected\n' +
+    '                           (desktop app -> npm global -> npx cache)\n' +
+    '  DSH_RUNTIME              executable that launches DSH; auto (desktop app\'s own runtime)\n' +
     '  DSH_MCP_PROFILE          DSH profile to drive (default dsh-mcp)\n' +
     '  DSH_MCP_PERMISSION       danger-full-access | workspace-write | read-only\n' +
     '  DSH_MCP_APPROVAL         auto-allow | auto-deny | ask\n' +
     '  DSH_MCP_REVIEW           advisory (default) | off — caller review ticket on results\n' +
-    '  DSH_MCP_LOG              silent (default) | info | debug\n\n' +
+    '  DSH_MCP_LOG              silent (default) | info | debug\n' +
+    '  DSH_MCP_LIVE             detail (default) | meta | off — live event stream for watch/dashboard\n\n' +
     'Docs: https://github.com/xmtlzzz/dsh-any-agent\n',
   );
   process.exit(0);
 }
 
+/**
+ * `dsh-any-agent watch` / `dsh-any-agent dashboard`：只读查看 live 事件流（调用链）。
+ * 独立进程，不启动 Hub、不碰写锁、不连 DSH —— 必须在启动 Hub 之前分派。
+ */
+if (argv[0] === 'watch' || argv[0] === 'dashboard') {
+  const cli = await import('../src/live-cli.mjs');
+  const code = argv[0] === 'watch' ? await cli.runWatch(argv.slice(1)) : await cli.runDashboard(argv.slice(1));
+  process.exit(code);
+}
+
 /**
  * `dsh-any-agent team on|off|status`
  *
@@ -125,6 +141,15 @@ await hub.load();
 hub.startReaper();
 // 启动时清一次过期哨兵（哨兵内含正文，长期不清理会无声堆积）
 const prunedSentinels = hub.pruneSentinels();
+// live 事件流与哨兵同一 TTL（单独调用，不改 pruneSentinels 的返回形状）
+try {
+  const { pruneLive } = await import('../src/live.mjs');
+  const { SENTINEL_TTL_MS } = await import('../src/config.mjs');
+  const prunedLive = pruneLive(SENTINEL_TTL_MS);
+  if (prunedLive.pruned) log.info(`[dsh-any-agent] 启动清理：删除 ${prunedLive.pruned} 个过期 live 事件文件`);
+} catch {
+  /* 清理失败不影响启动 */
+}
 if (prunedSentinels.pruned || prunedSentinels.reviews_pruned) {
   log.info(
     `[dsh-any-agent] 启动清理：删除 ${prunedSentinels.pruned} 个过期哨兵、` +

package/bin/restore.mjs

@@ -19,7 +19,7 @@
 import { chmodSync, existsSync, readFileSync, readdirSync, statSync } from 'node:fs';
 import { basename, dirname, join } from 'node:path';
 
-import { atomicWrite, backupFile, clientList, resolveDirs, ENTRY_NAME } from '../src/clients.mjs';
+import { atomicWrite, backupFile, clientList, resolveDirs } from '../src/clients.mjs';
 
 const argv = process.argv.slice(2);
 const has = (f) => argv.includes(f);

package/docs/en/compatibility.md

@@ -12,7 +12,8 @@ upgrading DSH, and run `dsh_doctor` afterwards.
 |---|---|---|---|
 | 0.5.x | `0.1.7-rc.1` or newer | ✅ Verified | ACP and the experimental Agent Teams packages are available; team mode is opt-in via `dsh-any-agent team on` |
 | 0.5.x | `0.1.5-rc.1` | ⚠️ Partial | ACP basics work; no team packages, so team mode stays off |
-| 0.5.x | `0.2.x` | ⚠️ Unverified | The ACP `session/*` surface may change; team packages must match the DSH version. Run `dsh_doctor` and the offline suite before upgrading |
+| 0.5.x | `0.2.1-rc.5` – `0.2.2-rc.1` | ✅ Verified | Full suites run on 2026-11-06 (0.2.1-rc.5 from npm, 0.2.2-rc.1 on the desktop app's bundled runtime); from 0.2.2 DSH requires Node ≥ 24.9 |
+| 0.5.x | `0.2.3` or newer | ⚠️ Unverified | The ACP `session/*` surface may change; team packages must match the DSH version. Run `dsh_doctor` and the offline suite before upgrading |
 | 0.4.x | `0.1.7-rc.1` | ✅ Verified | Team mode was on by default at that time |
 | 0.4.x | `0.1.5-rc.1` | ⚠️ Partial | No team packages |
 
@@ -22,22 +23,41 @@ upgrading DSH, and run `dsh_doctor` afterwards.
 
 ## Runtime requirements
 
-- **Node.js ≥ 22.15** (uses `zstdDecompressSync` from `node:zlib` to read DSH session headers);
+- **Node.js ≥ 22.15** for this server (uses `zstdDecompressSync` from `node:zlib` to read DSH session headers);
 - DSH installed and `~/.dsh` already has a working provider and credentials (the GUI can chat);
+- **DSH's own Node requirement** (`engines.node`, ≥ 24.9 from 0.2.2) is met by whatever runtime launches DSH:
+  the desktop app's bundled runtime when DSH comes from the desktop app (no local Node 24 needed), or this server's node for npm/npx installs;
 - Team mode also requires DSH `>= 0.1.7-0` and a profile that actually mounts both team packages.
 
+## Where DSH comes from (auto-detected, no configuration)
+
+The server finds DSH on its own, in this order — **no need to set `DSH_BIN`**:
+
+1. **DeepSeek Harness desktop app**: on Windows the install directory comes from the uninstall
+   registry (HKCU/HKLM); default install locations are checked on every platform. The CLI lives
+   inside `resources/app.asar`, so the server runs it with the app's bundled Electron in Node mode
+   (`ELECTRON_RUN_AS_NODE=1`) — the same DSH and the same runtime the GUI uses;
+2. **npm global install** (`npm i -g @deepseek-ai/dsh`);
+3. **npx cache** (can vanish at any time; lowest priority when otherwise equal).
+
+When several exist: candidates whose runtime satisfies `engines.node` first → higher version →
+desktop > global > npx. `DSH_BIN` (may point inside an `.asar`) and `DSH_RUNTIME` (the executable
+that launches DSH) are explicit overrides only.
+
 ## How to check
 
 ```bash
 dsh-any-agent --version          # this server
-node <DSH_BIN> --version         # DSH version (set DSH_BIN to pin it)
 dsh-any-agent team status        # team switch and profile
 ```
 
 In an MCP client, call `dsh_doctor` and look at:
 
-- `dsh_bin`: DSH entry point and version; **warn** when it resolves from an npx cache (`_npx/<hash>/`), which disappears on cache cleanup — install DSH globally or pin `DSH_BIN`;
-- `dsh_version`: the version graded against the table above — `verified` is ok; `partial` / `unsupported` / `unverified` (e.g. 0.2.x) / unreadable are **warn**;
+- `dsh_bin`: DSH entry point, version, source (desktop / npm global / npx cache / DSH_BIN) and runtime; **warn** when it resolves from an npx cache (`_npx/<hash>/`), which disappears on cache cleanup;
+- `dsh_runtime`: whether the launching runtime's Node satisfies DSH's `engines.node`; **warn** if not;
+- `dsh_desktop`: the desktop app's version; **warn** when it differs from the DSH this server uses (both share the `~/.dsh` session store);
+- `dsh_candidates`: every DSH found and which one was picked;
+- `dsh_version`: the version graded against the table above — `verified` is ok; `partial` / `unsupported` / `unverified` (e.g. 0.2.3+) / unreadable are **warn**;
 - `profile`: exists, drift, route source;
 - `team`: `on` / `off` / `requested but unavailable` (version or profile lacks the team package);
 - `config`: effective permission, idle reaping, shared process, and so on.
@@ -49,4 +69,5 @@ In an MCP client, call `dsh_doctor` and look at:
 3. If team mode will not turn on, check `dsh-any-agent team status` and `dsh_doctor`'s
    `team` check, then verify `~/.dsh/profiles/dsh-team/cordis.patch.yml` contains
    `@deepseek-ai/dsh-experimental-agent-team`;
-4. To pin a DSH version, set `DSH_BIN` explicitly instead of letting the npx cache pick one.
+4. By default the server follows the desktop app: after the app updates, the next DSH launch picks
+   up the new version (discovery is cached for 60 s). Set `DSH_BIN` only to pin a specific version.

package/docs/en/reference.md

@@ -4,7 +4,8 @@
 
 | Variable | Default | Purpose |
 |---|---|---|
-| `DSH_BIN` | auto-detected | Path to `@deepseek-ai/dsh/lib/bin.js` |
+| `DSH_BIN` | auto-detected (desktop app → npm global → npx cache) | Explicit path to `@deepseek-ai/dsh/lib/bin.js` (may point inside the desktop app's `app.asar`) |
+| `DSH_RUNTIME` | auto | Explicit executable that launches DSH (e.g. a Node 24). Used with `DSH_BIN`, or on its own for auto-discovered npm global / npx installs (their `engines.node` is re-checked against it); the desktop app always keeps its bundled runtime (only it can read the asar). Unset: the desktop app's bundled runtime, otherwise this server's node |
 | `DSH_HOME` | `~/.dsh` | DSH home shared with the GUI (credentials, sessions, workspace registry). Point it elsewhere only for isolation/multi-account |
 | `DSH_MCP_PROFILE` | `dsh-mcp` (`dsh-team` when team is on) | DSH profile to drive; an explicit value wins |
 | `DSH_MCP_TEAM` | `0` (off) | Team mode, opt-in. `dsh-any-agent team on` writes the settings file; this env var overrides it. When on, uses the `dsh-team` profile and injects a "form a team when needed" line before `dsh_send`; per call use `dsh_send(team=false)` |
@@ -29,6 +30,8 @@
 | `DSH_MCP_SENTINEL_INCLUDE_REASONING` | unset | `1` writes `result.thinking` into the sentinel (**breaks the never-on-disk guarantee**); answer/error/title/tool inputs are still credential-redacted |
 | `DSH_MCP_REVIEW` | `advisory` | Caller-review policy. `advisory` (default) attaches a review ticket (checklist + evidence + `dsh_review` entry) to every result and sentinel **without blocking later sends**; `off` disables automatic tickets. Per-conversation/per-send overrides use the `review` argument |
 | `DSH_MCP_REVIEWS_DIR` | `<state file dir>/reviews` | Where review verdicts are written (`<this>/<conversation_id>/<run_id>.review.json`). Must be writable, or startup fails loudly |
+| `DSH_MCP_LIVE` | `detail` | Live event stream level (the data behind `watch` / `dashboard`). `detail` adds redacted prompt / command / path previews; `meta` keeps tool names, status, timing and approval kinds only; `off` writes nothing. Reasoning is never written at any level |
+| `DSH_MCP_LIVE_DIR` | `<state file dir>/live` | Live event stream directory (`<this>/<conversation_id>/events.jsonl`, rolled to `.1` at 5 MB). Write failures are skipped silently and never affect a run; pruned by `DSH_MCP_SENTINEL_TTL_MS` |
 | `DSH_MCP_PERMISSION` | `workspace-write` | Default tier for `dsh_start`. `danger-full-access` additionally requires `DSH_MCP_ALLOW_FULL_ACCESS=1` |
 | `DSH_MCP_ALLOW_FULL_ACCESS` | `0` | Whether `permission=danger-full-access` is allowed. Denied by default: it hands the caller whole-machine write access |
 | `DSH_MCP_REASONING_EFFORT` | `max` | Default reasoning effort |

package/docs/en/release.md

@@ -13,6 +13,10 @@ npm version patch --no-git-tag-version
 node test/run.mjs
 node test/package-check.mjs
 npm run check:release   # version / CHANGELOG / doc links / package contents agree
+npm run docs:counts:check   # check counts in tests.md and the CI comment = the report node test/run.mjs just wrote
+#    A mismatch means tests changed without the numbers being refreshed:
+#    node test/run.mjs --all --report .state/test-report.json && npm run docs:counts
+#    (model-suite numbers only move with a report made using --all; see "After changing tests" in docs/en/tests.md)
 
 # 3. Verify the tarball itself: builds, installs, starts.
 npm pack --dry-run

package/docs/en/security.md

@@ -64,5 +64,6 @@ Silent by default — **not one byte is written**.
 - **The async completion sentinel persists the answer, usage and tool inputs** (it must, so a caller can collect offline) but **strips `result.thinking`** and always reports `thinking_omitted` (true when reasoning was removed, false when there was none). Tool inputs are passed through the same credential redaction as approvals, but the sentinel still contains commands and file contents — treat it as sensitive. A test asserts that even when `reasoning=full` is requested, no reasoning text appears in the sentinel — while `dsh_get(run_id)` still returns it from memory. Set `DSH_MCP_SENTINEL_INCLUDE_REASONING=1` to break this on purpose.
 - **Review records are the second intentional on-disk artifact.** `<state dir>/reviews/<conversation_id>/<run_id>.review.json` holds the verdict, the reviewer's `notes`/`findings`, the checklist and an evidence summary. `notes`/`findings`, the task preview, the evidence **and each checklist item** pass through the same credential redaction (the checklist can interpolate `result.error`); reasoning is never included. Treat review records as sensitive too (they can quote code or paths).
 - Sentinels **and review records** are pruned after 7 days by default (`DSH_MCP_SENTINEL_TTL_MS`; `0` keeps them forever).
+- The live event stream (`<state dir>/live/`, read by `watch` / `dashboard`) carries **redacted** command, path and prompt previews by default — no more than the sentinels already hold — never reasoning, and is pruned on the same 7-day TTL. Set `DSH_MCP_LIVE=meta` to drop the previews or `off` to write nothing. `dashboard` binds `127.0.0.1` only, requires a one-time token, checks the Host header, and is read-only.
 
 > ⚠️ **DSH writes its own session log under `~/.dsh/sessions` and that log contains the full reasoning text** (even with `reasoning=hide`). It is what makes resume possible and is outside this server's control. The absolute "reasoning never reaches disk" claim applies to *this server's* artifacts only.