dsh-super-code 0.3.6 → 0.3.8

package/cordis.patch.yml

@@ -17,7 +17,7 @@
           - id: super-code
             name: dsh-super-code/super-code
             config:
-              presetVersion: 0.3.6
+              presetVersion: 0.3.8
               presetInstallation: bundle:dsh-super-code
           - id: compaction
             name: cordis:group

package/docs/Changelog.md

@@ -1,5 +1,24 @@
 # 版本记录 · Changelog
 
+- **0.3.8 · 2026-10-26**：新增默认关闭、仅监听 `127.0.0.1` 且需凭证认证的 Streamable HTTP MCP 服务，提供 `dsh_sessions`、`dsh_run`、`dsh_wait`、`dsh_send`、`dsh_cancel` 与 `dsh_request_directory`。外部客户端可委派原生 DSH 对话、读取进度、跟进和取消，沿用宿主模型、预设及权限，不改变普通会话提示词，也不自动批准工具权限。保留幂等请求、重启中断状态、有界输出及 Git 工作区观察。[MCP 连接](UsageGuide.md#mcp-连接--mcp-connection)
+  **0.3.8 · 2026-10-26**: Adds an opt-in, token-authenticated Streamable HTTP MCP service bound to `127.0.0.1`, with `dsh_sessions`, `dsh_run`, `dsh_wait`, `dsh_send`, `dsh_cancel`, and `dsh_request_directory`. External clients can delegate native DSH conversations, inspect progress, follow up, and cancel using the host model, preset, and permissions. Normal conversation prompts and tool approvals are unchanged. Includes idempotent requests, interrupted-state recovery without automatic replay, bounded output, and Git workspace observations. [MCP connection](UsageGuide.md#mcp-连接--mcp-connection)
+
+  连接后可按允许目录查询本服务持有的最近对话与连接容量，由调用方明确复用指定任务或新建，不默认复用最新对话。最大连接数与任务并发同步，默认均为 3，保留用户已保存的上限。目录改为工作区与自定义目录勾选列表，每次打开刷新；外部申请新目录需要用户在 DSH 弹窗中批准，撤权后不能通过复用绕过限制。
+  Lists recent service-owned conversations and connection capacity by allowed directory, so callers explicitly reuse a selected task or create a new conversation; the latest conversation is never selected automatically. Connection and task-concurrency limits stay synchronized, default to three, and preserve saved user limits. Workspace and custom-directory checklists refresh when opened. External requests for new directories require consent in DSH, and reuse cannot bypass revoked directory access.
+
+  设置新增首页概览，集中展示预设状态与版本、删除保护等级、MCP 开关及在线/历史对话数量；客户端和关联会话详情归连接页，删除保护独立成页，预设配置直接展开。连接修改自动保存，凭证默认展开；修复工作区实体 getter 丢失导致“目录不可用”和无法启用连接的问题。保留 `0.1.5-alpha.1` 至 `0.2.1-rc.2` 的已适配范围，分批宿主验证及平台限制见[兼容性记录](Compatibility.md)，本次不新增效果评测成绩。
+  Adds a Home overview for preset status and versions, deletion protection, the MCP switch, and connected/past conversation counts. Client and linked-session details live in Connection; deletion protection has a separate tab, and preset configuration displays directly. Connection changes save automatically and credentials open expanded. Fixes missing Workspace getters that marked valid directories unavailable and prevented activation. Retains the adapted `0.1.5-alpha.1`–`0.2.1-rc.2` range; see [compatibility records](Compatibility.md) for staged host checks and platform limits. No new effectiveness scores are claimed.
+
+- **0.3.7 · 2026-10-24**：新增关闭、宽松、严格三档删除保护，默认宽松：提示优先使用可恢复的 `trash`，脚本中同样建议使用，用户明确要求时可用 `rm`；严格模式识别永久删除命令并逐次请求确认，官方预设另设开关且默认关闭。兼容旧布尔设置与 v4 日志。[删除保护](UsageGuide.md#删除保护--deletion-protection)
+  **0.3.7 · 2026-10-24**: Adds Off, Relaxed, and Strict deletion protection, defaulting to Relaxed: prefer recoverable `trash`, including in scripts, while honoring explicit `rm` requests. Strict mode recognizes permanent-deletion commands and requests per-call approval; official presets opt in separately. Supports legacy boolean settings and v4 journals. [Deletion protection](UsageGuide.md#删除保护--deletion-protection)
+
+  Super Code 侧栏新增只读任务状态并默认展开，从现有记录展示目标、步骤进度、动作和成功文件操作；Agent 名字只在任务根显示。任务、步骤、已加载动作全部展开，使用变高虚拟滚动，保留阅读位置、键盘导航和运行指示。保留原圆圈执行树与记忆库，三项互斥切换。任务状态不改提示词、模型请求、工具定义或执行行为；文件记录不等同完整 Git diff，缺失与截断明确提示。[任务状态](UsageGuide.md#任务状态--task-status)
+  Adds a read-only Task status section, open by default, showing recorded objectives, step counts, activity, and successful file operations. Agent names appear only at task roots. All loaded tasks, steps, and activity stay expanded in a variable-height virtual list with reading-position retention, keyboard navigation, and running indicators. Preserves the circular Agent graph and memory library with exclusive section switching. Task status changes no prompts, model requests, tool definitions, or execution behavior. File records are not a complete Git diff; missing or bounded data is labeled. [Task status](UsageGuide.md#任务状态--task-status)
+
+README 仅保留最近三个版本，完整记录见本页；[评测说明](EvaluationResults.md) 列出各组 DSH、插件与模型版本，以及 GLM 迁移和新版预算对照。
+
+README shows the three most recent releases; this page retains the full history. The [evaluation report](EvaluationResults.md) identifies DSH, plugin, and model versions, with GLM transfer and newer-host budget comparisons.
+
 - **0.3.6 · 2026-10-20**：排查发现新版 Harness 预算收紧后出现效果退化，因此增加插件内预算配置，并默认使用此前 Pro 测试中效果更好的旧预算，无需用户手动填写：按完整上下文窗口计算、80% 触发压缩、保留最近 16% 原文、摘要上限 8,192 Token，压缩追加尝试与溢出重试各 1 次，支持新版 PTC 的宿主默认执行时限和上限均为 600 秒。保留原有宿主默认值提示、用户自定义覆盖及运行中 Agent 的配置快照；旧宿主按能力禁用时限覆盖，始终遵守宿主时限上限。官方预设仍需手动开启应用。该修复不代表新增或改写历史评测成绩。[预算设置](UsageGuide.md#运行预算--runtime-budgets)
   **0.3.6 · 2026-10-20**: Investigation found regressions after newer Harness versions reduced their budgets. Adds in-plugin budget settings and defaults to the older budgets that performed better in the Pro tests, without manual setup: full-context-window accounting, compression at 80%, 16% recent verbatim retention, an 8,192-token summary cap, one additional compression attempt and one overflow retry, and 600-second default/maximum deadlines on hosts with the newer PTC provider. Preserves host-default hints, user overrides, and running Agents' configuration snapshots. Older hosts disable unsupported deadline overrides, and host ceilings always apply. Official presets remain opt-in. This fix does not add or revise historical evaluation scores. [Budget settings](UsageGuide.md#运行预算--runtime-budgets)
 

package/docs/Compatibility.md

@@ -1,5 +1,49 @@
 # 宿主兼容性 · Host Compatibility
 
+## 0.3.8 · MCP 连接 · MCP Connection · 2026-10-26
+
+**会话列表与显式复用增量（2026-10-26）：** 253 项测试通过，覆盖真实 MCP HTTP 会话查询、目录过滤、显式复用/新建、连接容量、默认上限 3、旧配置迁移及撤权边界。日常 NEXT `2.0.19-next` 安装候选后，真实 MCP SDK 握手发现六个工具，按四个工作目录查询到六条历史任务；凭证、已有对话和用户上限 10 均保留，任务并发同步为 10，未发送模型提示词。最新会话列表/复用仅完成上述集成测试及 NEXT 增量验证，下述 26 目标基础矩阵和四端设置验证属于较早候选的证据，未全部重跑。每条对话的在线连接数反映当前关联连接（0 或 1），不代表多客户端租约或原子会话锁。
+
+**Conversation-list and explicit-reuse delta (2026-10-26):** All 253 tests pass, including real MCP HTTP session queries, directory filtering, explicit reuse/create, connection capacity, the default limit of three, legacy-setting migration, and revocation boundaries. After installing the candidate on daily NEXT `2.0.19-next`, a real MCP SDK handshake discovers six tools and queries six historical tasks across four working directories. Credentials, conversations, and the user's limit of ten are preserved, with task concurrency synchronized to ten; no model prompt is sent. The latest list/reuse changes have only these integration and NEXT delta checks. The 26-target baseline and four-host settings checks below are evidence for earlier candidates, not a full rerun. Per-conversation connection counts reflect the current associated connection (zero or one), not multi-client leases or an atomic conversation lock.
+
+**工作区目录与自动保存修复（2026-10-26）：** 显式读取 Workspace 实体的路径、名称 getter，修复空路径被误判为“目录不可用”、无法选择有效目录启用 MCP 的问题。连接设置改为自动保存，移除保存/取消按钮；串行处理后续修改，无效输入与失败不误报成功，撤销最后一个允许目录时同时关闭 MCP。249 项测试、类型检查、构建与客户端语法检查通过。最低 Web `0.1.5-alpha.1`、最高已适配 Web `0.2.1-rc.2`、官方 macOS arm64 Desktop `0.2.1-rc.2`、NEXT `2.0.19-next` 均完成单实例串行增量验收：通过宿主公开 API 创建含中文、空格的真实工作区，确认路径/名称/可用性；修改端口与连接数自动持久化，真实 MCP SDK 客户端可认证并发现工具，目录撤权、重新启用与页面重载均通过。独立浏览器另验证切页保存、关闭设置时提交最后一次输入及无效值不落盘。四端页面脚本错误为零；此前目录测试未覆盖 Workspace 原型 getter，此次已补齐。中间版本保留此前记录，原生目录选择确认/取消限制不变。
+
+**Workspace and automatic-save fix (2026-10-26):** Explicitly reading Workspace path/title getters fixes blank paths incorrectly marked unavailable, which prevented valid workspace selection and MCP activation. Connection changes now save automatically without save/cancel buttons. Writes are serialized, invalid inputs and failures are not reported as saved, and revoking the final directory also turns MCP off. All 249 tests, type checking, build and client syntax checks pass. Sequential single-instance checks pass on Web `0.1.5-alpha.1` and `0.2.1-rc.2`, official macOS arm64 Desktop `0.2.1-rc.2`, and NEXT `2.0.19-next`. They create real workspaces with Chinese characters and spaces through host APIs, verify getter-backed paths/titles and availability, persist port/connection limits automatically, authenticate a real MCP SDK client and discover tools, revoke access, re-enable and reload. Separate browser checks cover tab changes, flushing the last edit when settings close, and rejecting invalid values. No page script errors occurred. Earlier directory checks missed prototype getters; this regression now has coverage. Intermediate versions retain prior evidence and native-picker confirmation/cancellation remains outside the verified scope.
+
+**设置第二轮与目录审批（2026-10-26）：** 243 项测试、类型检查、构建和客户端语法检查通过。最低 Web `0.1.5-alpha.1`、最高已适配 Web `0.2.1-rc.2`、官方 macOS arm64 Desktop `0.2.1-rc.2`、已安装 NEXT `2.0.19-next`（Harness `0.2.1-rc.2`）完成单实例串行增量验收：五标签首页、预设状态归首页、保护独立保存、目录勾选、默认展示凭证、真实 MCP 客户端连接及设置关闭时的全局目录审批；批准后同一连接可在新目录创建并完成原生会话，拒绝不会授予访问权限。四端保存了截图，页面脚本错误为零。Web 的 SSH 启动情境另验证了网页目录浏览器和取消。原生目录选择器入口已调用，但系统辅助功能接口超时，尚未完成原生文件选择的确认/取消验收；不将它算作通过。下述 26 目标全矩阵仍是上一候选的历史证据，不宣称本轮全部复验。
+
+**Settings and directory-consent delta (2026-10-26):** All 243 tests, type checking, build and client syntax checks pass. Single-instance sequential checks cover Web `0.1.5-alpha.1` and `0.2.1-rc.2`, official macOS arm64 Desktop `0.2.1-rc.2`, and installed NEXT `2.0.19-next` (Harness `0.2.1-rc.2`). They verify the Home overview, separate protection settings, directory checkboxes, expanded credentials, actual MCP connections and global consent with settings closed. Approval enables native session execution over the same connection; rejection grants nothing. Screenshots were saved with no page script errors. Web checks also exercise browse-directory selection and cancellation in an SSH launch scenario. The native picker entry was invoked, but OS accessibility timed out; native selection confirmation/cancellation remains unverified. The 26-target matrix below is evidence for the previous candidate, not a full rerun of this delta.
+
+2026-10-26 后续布局调整：关联会话及客户端详情移至“连接”，首页仅展示在线/历史对话数量；预设配置改为直接展示，去掉折叠和重复标题。245 项测试、类型检查、构建和客户端语法检查通过。最低 Web `0.1.5-alpha.1`、最高已适配 Web `0.2.1-rc.2`、官方 macOS arm64 Desktop `0.2.1-rc.2` 与 NEXT `2.0.19-next` 完成单实例串行增量验收并保存截图，页面脚本错误为零：连接页断开后会话归入历史，经新连接明确继续后恢复在线且不重复显示；幂等找回仅更新关联，不重复派发。独立浏览器组件检查另覆盖空状态和打开会话。中间版本未重跑本次布局，原生目录选择确认/取消的限制仍同上。
+
+The subsequent layout delta on 2026-10-26 moves client and linked-session details to Connection, keeps only connected/past conversation counts on Home, and displays the preset form directly without repeated headings. All 245 tests, type checking, build and client syntax checks pass. Sequential single-instance checks with screenshots pass on minimum Web `0.1.5-alpha.1`, latest adapted Web `0.2.1-rc.2`, official macOS arm64 Desktop `0.2.1-rc.2`, and NEXT `2.0.19-next`, with no page script errors. Disconnecting from Connection moves the conversation to history; an explicit follow-up over a new connection restores its connected status without duplication. Idempotent retries update the association without dispatching again. Separate browser component checks also cover empty states and opening conversations. Intermediate versions were not rerun for this layout; the native-picker confirmation/cancellation limitation above remains.
+
+`0.3.8` 基于正式版 `0.3.7`，合入 `feat/mcp-delegation` 的默认关闭本机 MCP 服务与连接设置。下方运行预算矩阵中的 **20 个 Web 版本、5 个官方 macOS arm64 Desktop 版本及 DSH NEXT** 均通过基础连接验收：设置保存、真实 MCP SDK 客户端认证、原生 Super Code 根会话、重复请求去重、同会话补充要求与运行中取消。宿主使用隔离 profile，不修改日常配置。
+
+Version `0.3.8`, based on released `0.3.7`, merges the opt-in local MCP service and connection settings from `feat/mcp-delegation`. The **20 Web versions, five official macOS arm64 Desktop versions and DSH NEXT** in the runtime-budget matrix below pass baseline connection checks: settings persistence, authentication with a real MCP SDK client, native Super Code root sessions, duplicate-request coalescing, follow-ups and live cancellation. Isolated profiles leave daily configuration untouched.
+
+早期三标签候选的增量验收覆盖最低 Web `0.1.5-alpha.1`、已适配最高 Web `0.2.1-rc.2`、官方 Desktop `0.2.1-rc.2` 和 NEXT `2.0.17-next`。四端均通过三标签设置、独立连接草稿、凭证轮换时保留草稿、切页隐藏凭证、通用“连接 Prompt”、原生子 Agent 执行和整树取消。冷进程重启保留启用设置、凭证与任务 ID；未完成任务没有自动重发或误报成功，显式补充要求后可继续同一会话。官方 Desktop `0.2.0-rc.1/rc.2` 另通过上一 UI 候选的串行增量检查，其余版本保留基础候选记录，不宣称全部复验最终文案。
+
+Earlier three-tab candidate checks cover minimum Web `0.1.5-alpha.1`, latest adapted Web `0.2.1-rc.2`, official Desktop `0.2.1-rc.2`, and NEXT `2.0.17-next`. All four pass three-tab settings, independent drafts, draft preservation during token rotation, token hiding on tab changes, the generic Connection Prompt, native child-Agent execution and whole-tree cancellation. Cold process restarts retain enabled settings, credentials and task IDs without replaying pending prompts or reporting false success; an explicit follow-up resumes the same session. Official Desktop `0.2.0-rc.1/rc.2` also passed serial delta checks on the preceding UI candidate. Other versions retain baseline evidence rather than a claim that all final wording was rerun.
+
+上述早期增量与重启验收严格单实例串行运行，退出前一宿主后才启动下一宿主。241 项全量测试、类型检查、构建及客户端语法检查通过，包含真实 MCP HTTP、幂等冲突、任务归属、目录边界、断线、权限等待、取消、恢复和 Git 工作区观察。测试模型为本地确定性 LlmAdapter，经过真实宿主 Agent 与工具链；没有调用外部大模型，不代表模型效果评测。Web 使用 Chromium，原生仅覆盖 macOS arm64；Windows/Linux、macOS x64、Safari 专属行为与客户端根据 Prompt 自动配置连接的能力未验收。
+
+Those earlier delta and restart runs use one DSH instance at a time, stopping the previous host before starting the next. All 241 tests, type checking, build and client syntax checks pass, including real MCP HTTP, idempotency conflicts, ownership, directory boundaries, disconnects, permission waits, cancellation, recovery and Git workspace observations. A local deterministic LlmAdapter drives actual host Agents and tools; no external model is called and this is not an effectiveness evaluation. Web uses Chromium and native coverage is macOS arm64 only. Windows/Linux, macOS x64, Safari-specific behavior and clients’ ability to configure MCP automatically from a prompt remain unvalidated.
+
+## 0.3.7 · 删除保护与任务状态 · Deletion Protection and Task Status · 2026-10-24
+
+正式发布候选保留稳定记忆库，未包含开发中的版本化记忆或任务 skills。229 项测试、类型检查、构建和客户端语法检查通过。下方相同的 20 个 Web、5 个官方 macOS arm64 Desktop 与 DSH NEXT，均在真实宿主组件上通过 25 项删除保护/任务投影检查，包含旧设置、官方预设隔离、逐次确认、旧/新日志、嵌套 PTC、文件归属和任务状态不干预模型请求的回归。
+
+The release candidate retains the stable memory library and excludes experimental versioned memory and task skills. All 229 tests, type checking, build, and client syntax checks pass. The same 20 Web versions, five official macOS arm64 Desktop versions, and DSH NEXT listed below pass 25 deletion-protection/task-projection checks each against actual host components, including legacy settings, official-preset isolation, per-call approval, old/new journals, nested PTC, file attribution, and regression checks that task feedback leaves model requests unchanged.
+
+页面增量复验覆盖最低 Web `0.1.5-alpha.1`、已适配最高 Web `0.2.1-rc.2`、官方 Desktop `0.2.1-rc.2` 和 NEXT `2.0.17-next`。每端通过 7 项任务状态检查，涵盖全部展开、实时更新、原圆圈树、减少动态效果、长文本、失败状态、373/374 行列表的滚动/键盘访问/锚点与缩短数据；仅挂载视口附近行。每端另通过 6 项删除保护设置检查，包含三档切换、独立官方开关、保存重载、旧布尔配置和恢复默认。
+
+Incremental UI checks cover minimum Web `0.1.5-alpha.1`, latest adapted Web `0.2.1-rc.2`, official Desktop `0.2.1-rc.2`, and NEXT `2.0.17-next`. Each passes seven task-status checks covering expansion, live updates, the circular graph, reduced motion, wrapped text, failures, and scrolling/keyboard access/anchors/shrinking data across 373/374 rows while mounting only nearby rows. Each also passes six deletion-settings checks covering modes, independent official opt-in, save/reload, legacy booleans, and reset.
+
+任务状态页面使用真实宿主 API 和构造日志，不新增模型调用，不将夹具文件记录当作真实文件编辑。运行环和暗色主题 tokens 已检查，不宣称所有宿主主题设置组合或十万行真实浏览器性能已测。严格删除确认的引擎检查由测试驱动器答复真实宿主审批服务，不等同人工点击原生确认对话框。NEXT 测试外壳已知的两条 ready 诊断另列，任务页面插件异常和其他控制台错误/警告为零。未重跑未变的安装器或扩展平台范围；中间版本页面沿用既有验证记录，Windows/Linux 原生客户端仍未验收。
+
+Task-status UI uses real host APIs with constructed journals, with no new model calls or claims of real file edits. Running indicators and dark-theme tokens are checked; this is not every host theme-setting combination or a 100,000-row browser benchmark. Strict-deletion engine checks answer the real host approval service through the driver, not manual clicks in native approval dialogs. Two known NEXT test-shell ready diagnostics are recorded separately; task pages have no plugin exceptions or other console errors/warnings. Unchanged installers and additional platforms were not retested; intermediate-version pages retain prior evidence, and native Windows/Linux clients remain unvalidated.
+
 ## 0.3.6 · 旧预算默认配置 · Legacy Budget Defaults · 2026-10-20
 
 0.3.6 默认使用此前 Pro 测试的旧预算：完整上下文窗口、80% 压缩触发、16% 原文保留、8,192 Token 摘要、压缩追加与溢出重试各 1 次；提供新版 PTC 的宿主默认/上限为 600 秒，仍受宿主上限约束。用户保存值和加载配置优先，运行中的 Agent 保留快照，恢复默认会回到旧预算。括号内宿主默认值提示保持不变，官方预设仍默认不应用。

package/docs/EvaluationResults.md

@@ -1,15 +1,19 @@
 # SWE-bench Pro hard-100 · 校正结果 / Corrected Results
 
-截至 2026-10-09，版本对比中的五组都完成了同一批 100 题的官方评分。0.2.0 使用冻结的分层记忆候选，0.3.0 使用冻结的 Batch.3 候选成绩。官方预设对比另列于下方，截至 2026-10-15，极简、标准、PTC 和创造的五组均已完成。
+截至 2026-10-09，版本对比中的五组都完成了同一批 100 题的官方评分。0.2.0 使用冻结的分层记忆候选，0.3.0 使用冻结的 Batch.3 候选成绩。官方预设对比另列于下方，最新官方预设进度与评分校正见下表。
 
-As of October 9, 2026, all five version-comparison runs have official scores for the same 100 tasks. Version 0.2.0 refers to the frozen memory-hierarchy candidate; 0.3.0 reports the frozen Batch.3 candidate. The official-preset comparison appears separately below. As of October 15, 2026, all five minimal, standard, PTC, and creative runs are complete.
+As of October 9, 2026, all five version-comparison runs have official scores for the same 100 tasks. Version 0.2.0 refers to the frozen memory-hierarchy candidate; 0.3.0 reports the frozen Batch.3 candidate. The official-preset comparison appears separately below. Current official-preset progress and grading corrections are listed below.
 
 ## 版本对比 · Version Comparison
 
+本表均使用 **DSH `0.1.5-rc.2`**、**`deepseek-v4.1-flash`** 与 `high` 思考等级。
+
+All rows use **DSH `0.1.5-rc.2`**, **`deepseek-v4.1-flash`**, and `high` reasoning.
+
 | 指标 / Metric | 官方 minimal + high | 0.0.9 | 0.1.2 | 0.2.0 分层记忆 | 0.3.0 Batch.3 |
 |---|---:|---:|---:|---:|---:|
 | 有效评分 / Valid scores | 100 | 100 | 100 | 100 | 100 |
-| 通过题数 / Passed | 44 | 48 | 52 | 52 | 54 |
+| 通过 / Passed | 46 | 50 | 53 | 54 | 56 |
 | 平均回答耗时（历史）/ Original mean minutes | 25.685 | 16.458 | 16.011 | 15.148 | 13.461 |
 | 耗时中位数 / Median minutes | 26.138 | 14.398 | 13.736 | 13.510 | 12.197 |
 | 耗时 P90 / P90 minutes | 43.696 | 28.816 | 29.360 | 24.145 | 21.381 |
@@ -27,92 +31,164 @@ As of October 9, 2026, all five version-comparison runs have official scores for
 
 Tool counts use host `tool/call` events. One PTC call can execute several operations, so this column does not compare the number of underlying file reads or commands.
 
+五组均按相同规则复核，通过数包含已核实的测试名称差异修正。仅当原始测试全部通过、每个缺失的必需测试名均能精确对应到通过测试时，才修正为通过；原始判分与修正依据保留在逐题数据中。用量和耗时保持原作答数据。
+
+All five runs were reviewed under the same rules. Pass counts include verified test-name corrections, accepted only when every raw test passes and every missing required name maps exactly to a passing test. Per-task data retains the original grader verdict and correction evidence. Original usage and timing are unchanged.
+
 ## 官方预设对比 · Official Preset Comparison
 
-截至 **2026-10-15 08:38（UTC+8）**，以下五组均已完成同一批 100 题。标准 + max 已暂停，部分成绩另列，未完成题不算错。
+本表使用 **DSH `0.1.5-rc.2`** 和 **`deepseek-v4.1-flash`**，思考等级按列标明；成绩包含后续原补丁复评与测试名称修正。各列只统计有效结果，未满 100 题的列不参与完整 100 题排名。
+
+This table uses **DSH `0.1.5-rc.2`** and **`deepseek-v4.1-flash`**, with reasoning effort shown per column. Scores include subsequent original-patch regrades and verified test-name corrections. Each column uses valid scores only; incomplete columns are excluded from full 100-task rankings.
+
+| 指标 / Metric | 极简 minimal + high | 极简 minimal + max | 标准 standard + high | PTC + high | 创造 creative + high | 标准 standard + max |
+|---|---:|---:|---:|---:|---:|---:|
+| 有效进度 / Valid scores | 100/100 | 100/100 | 100/100 | 100/100 | 100/100 | 99/100 |
+| 通过/有效 / Passed / valid | 46/100 | 50/100 | 51/100 | 47/100 | 49/100 | 49/99 |
+| 待环境复评 / Pending regrades | 0 | 0 | 0 | 0 | 0 | 0 |
+| 净耗时中位数 / Median net minutes | 25.598 | 32.167 | 16.639 | 13.455 | 16.452 | 16.887 |
+| 净耗时 P90 / P90 net minutes | 41.658 | 45.179 | 36.681 | 25.031 | 30.104 | 34.583 |
+| 原始分钟/题 / Original minutes | 25.685 | 32.529 | 20.683 | 17.302 | 19.856 | 20.452 |
+| 净分钟/题 / Net minutes | 25.122 | 32.009 | 18.826 | 15.122 | 18.714 | 19.561 |
+| 模型调用/题 / Model calls | 124.660 | 138.920 | 92.370 | 71.160 | 93.600 | 101.061 |
+| 顶层工具调用/题 / Top-level tool calls | 127.360 | 150.070 | 110.480 | 70.990 | 113.780 | 124.636 |
+| 总输入 token/题 / Input tokens | 11,477,169.950 | 14,849,497.540 | 8,771,693.040 | 6,160,934.650 | 9,205,287.290 | 11,417,324.020 |
+| 总 token/题 / Total tokens | 11,578,046.900 | 14,966,097.260 | 8,854,513.910 | 6,238,434.510 | 9,292,949.400 | 11,526,872.192 |
+| 缓存输入 token/题 / Cached input | 11,404,101.120 | 14,770,140.160 | 8,713,578.230 | 6,099,266.510 | 9,145,025.240 | 11,349,317.818 |
+| 非缓存输入 token/题 / Uncached input | 73,068.830 | 79,357.380 | 58,114.810 | 61,668.140 | 60,262.050 | 68,006.202 |
+| 输出 token/题 / Output | 100,876.950 | 116,599.720 | 82,820.870 | 77,499.860 | 87,662.110 | 109,548.172 |
+| 输入缓存率 / Input cache hit rate | 99.363% | 99.466% | 99.337% | 98.999% | 99.345% | 99.404% |
+| 扣除重试分钟（全组）/ Retry minutes excluded, total | 56.323 | 51.936 | 185.717 | 217.996 | 114.226 | 88.220 |
+| 缺少用量的请求 / Requests without usage | 3 | 11 | 4 | 5 | 2 | 0 |
+
+净耗时扣除最终有效作答中的失败请求和重试等待；两种耗时均不含官方评分。调用次数排除已记录的失败请求。总 token = 缓存输入 + 非缓存输入 + 输出，输出含思考 token。复评分保留原作答的用量和耗时；有效题目范围变化时，均值会随之变化。未返回的用量不估算，数字不等于完整账单。
+
+Net time excludes failed requests and retry waits in the final valid answer; both time measures exclude grading. Call counts exclude logged failed requests. Total tokens = cached input + uncached input + output, including reasoning. Regrading preserves each answer's original usage and timing; means change when the valid subset changes. Missing usage is not estimated, so these figures are not a complete bill.
+
+创造保留官方预设与工具定义；评测隔离禁止 `cordis_run` 在宿主上执行动态代码，只读检查仍可使用。极简 + high 复用历史基线，宿主修订与本轮不同，不能把差异完全归因于思考等级。
+
+Creative retains the official preset and tools; evaluation isolation blocks host-side dynamic execution through `cordis_run`, while read-only inspection remains available. Minimal + high reuses a historical baseline with different Harness revisions, so the results do not isolate reasoning effort.
+
+此前发现的 12 条 Node 构建依赖下载异常均已完成原补丁复评分：11 条恢复通过、1 条仍失败。每条需要两次无环境异常且一致的官方结果；存在分歧时保留待确认，不挑选最好一次。已有历史环境复核所带来的修正仍保留，未重复加分。
+
+All 12 previously identified Node dependency-download failures have been regraded with the original patches: 11 recovered to a pass and one remained a failure. Each requires two consistent official scores without environmental errors. Conflicting scores remain unresolved; the best retry is never selected. Earlier environmental corrections remain in place and are not counted twice.
+
+全量复核覆盖 3,296 条保留的 Pro / Dev 主记录，包含不同候选、历史批次和重复保留记录，不代表独立题数。全部完成原始日志重解析；Dev 的 1,212 条记录判分一致，原补丁及 base/gold 环境检查均通过。公开历史四版本的 400 条记录均精确绑定原始摘要和评分日志。旧实验中新发现的 7 项环境异常均已完成原补丁复评：3 项恢复通过、4 项仍失败。本次复核不新增模型调用。
+
+The full review covers 3,296 preserved Pro / Dev primary records across candidates and historical batches, including retained duplicates rather than unique tasks. All raw logs were reparsed. All 1,212 Dev verdicts agree, with patch identities and base/gold environment checks verified. All 400 published historical-version records bind exactly to original summaries and grading logs. All seven newly identified environmental failures in older experiments have been regraded with their original patches: three recovered to a pass and four remained failures. This review adds no model calls.
+
+此前标为“缺日志”的两条记录，实际保存在旧复评目录中，现已找到并复核：早期 minimal 冒烟第 4 题的 175 项测试全部通过；旧 Graph 第 623 题解析出 93 项通过，但仍缺 15 项必需测试，保留失败。另一条旧 Graph 冒烟第 99 题，摘要误用了第 378 题的补丁、会话和用量信息；本题实际执行补丁正确，17 项必需测试失败，保留失败。原摘要保留，更正依据单独记录；这三条均不属于上述五组发布成绩，公开正确率与用量不变。
+
+The two records previously marked as missing logs were found in legacy regrading directories. The early minimal smoke test for task 4 passed all 175 tests. Old Graph task 623 parsed 93 passing tests but still missed 15 required tests, so it remains a failure. A separate old Graph smoke summary for task 99 copied patch, session, and usage metadata from task 378. Task 99 was graded with its own correct patch and failed 17 required tests, so its failure also stands. Original summaries are retained with separate correction evidence. These three records are outside the five published runs above; published scores and usage are unchanged.
+
+共有 31 条记录只存在已确认的测试名称差异：OpenLibrary 的 16 条动态年份，以及 NodeBB 的 15 条末尾引号或空格。原始测试分别为 92 项、714 项全部通过，必需测试缺失集合逐项精确对应。复核只接受这两种已核实的名称映射，不做模糊匹配，也不根据同题其他版本的成绩加分。上述各版本与官方预设均已按相同规则检查，确认通过的记录已计入通过数；原始判分与精确名称映射留作追溯。
+
+There are 31 confirmed test-name mismatch records: 16 dynamic-year cases in OpenLibrary and 15 trailing-quote or space cases in NodeBB. Raw results show all 92 or 714 tests passing, with every missing required name mapped exactly. Review accepts only these two verified mappings, without fuzzy matching or borrowing a pass from another candidate. The versions and official presets above were checked under the same rules. Confirmed passes are included in pass counts; original verdicts and exact name mappings remain available for review.
+
+请求明细核算覆盖 3,224 条记录，调用数、Token 汇总和缺失用量数均与摘要一致，未发现重复请求 ID；72 条没有保留请求明细。但加总一致不代表归属正确：对全部摘要的会话路径和用量来源检查后，发现上述旧 Graph 第 99 题这一条串题记录，已从旧实验的用量均值中排除。其本题主会话收据已找回，但旧清单未保证覆盖所有请求，不能视为完整账单。3,274 条摘要的 Token 加总关系一致，22 条缺少完整指标。本次检查不等于重新核对所有原始会话或供应商账单。
+
+Saved request ledgers were reconciled for 3,224 records: call counts, token sums, and unknown-usage counts agree with summaries, with no duplicate request IDs. Seventy-two records lack a saved ledger. Matching sums do not prove task ownership: checks of session paths and usage sources across all summaries found the single cross-task record for old Graph task 99 described above. Its copied metrics are excluded from historical experiment averages. Its own main-session receipt was recovered, but the old request inventory does not establish complete coverage. Token totals are internally consistent in 3,274 summaries; 22 lack complete metrics. This is not a full audit of raw sessions or provider bills.
+
+[逐条评分复核](../eval/results/swebench-pro-final-100/GradingReviewResults.json) · [官方预设逐题快照](../eval/results/swebench-pro-final-100/OfficialPresetResults.json)
+
+[Per-case grading review](../eval/results/swebench-pro-final-100/GradingReviewResults.json) · [Official-preset snapshot](../eval/results/swebench-pro-final-100/OfficialPresetResults.json)
+
+## 跨模型迁移 · Cross-Model Transfer
+
+将模型换为 **`glm-5.3-flash`**，思考等级统一为 **`max`**，仍使用同一批 hard-100。两组均完成 100 题：Super Code 使用 **DSH `0.1.5-rc.2` + 插件 `0.3.4`**；对照使用完整原生 **ZCode Desktop `3.14.4` / CLI `0.16.9`**，没有抽取部分源码模拟 Agent。
+
+Both runs completed the same hard-100 set using **`glm-5.3-flash`** with **`max`** reasoning. Super Code ran on **DSH `0.1.5-rc.2` + plugin `0.3.4`**; the comparison used the complete native **ZCode Desktop `3.14.4` / CLI `0.16.9`**, rather than an extracted Agent implementation.
+
+| 指标 / Metric | DSH + Super Code 0.3.4 | 原生 ZCode / Native ZCode |
+|---|---:|---:|
+| 通过 / Passed | 44/100 | 28/100 |
+| 净分钟/题 / Net minutes | 32.896 | 52.320 |
+| 模型调用/题 / Model calls | 66.890 | 64.310 |
+| 总 token/题 / Total tokens | 5,499,154.470 | 3,609,511.930 |
+| 缓存输入 token/题 / Cached input | 5,302,796.160 | 3,356,862.720 |
+| 非缓存输入 token/题 / Uncached input | 126,050.640 | 144,405.020 |
+| 输出 token/题 / Output | 70,307.670 | 108,244.190 |
+| 缺少用量的请求 / Requests without usage | 29 | 120 |
+
+这轮 Super Code 通过率高 **16 个百分点**，平均净耗时更少，但 token 更多。这说明方案可在 GLM 上运行并取得有效结果；对照比较的是两套完整系统，不能据此分离插件的贡献，也不能推及所有模型。缺失用量未估算。[测试脚本与记录](../eval/glm/README.md)
 
-As of **October 15, 2026, 08:38 (UTC+8)**, all five runs below have completed the same 100 tasks. The paused standard + max run is listed separately; pending tasks are not counted as failures.
+Super Code passed **16 percentage points** more tasks and used less net time, but more tokens. This demonstrates working transfer to GLM in this run. The comparison covers two complete systems, so it neither isolates the plugin's contribution nor establishes gains across all models. Missing usage is not estimated. [Scripts and records](../eval/glm/README.md)
 
-| 指标 / Metric | 极简 minimal + high | 极简 minimal + max | 标准 standard + high | PTC + high | 创造 creative + high |
-|---|---:|---:|---:|---:| ---: |
-| 有效进度 / Valid scores | 100/100 | 100/100 | 100/100 | 100/100 | 100/100 |
-| 通过/有效 / Passed / valid | 44/100 | 48/100 | 49/100 | 44/100 | 46/100 |
-| 原始分钟/题 / Original minutes | 25.685 | 32.529 | 20.683 | 17.302 | 19.856 |
-| 净分钟/题 / Net minutes | 25.122 | 32.009 | 18.826 | 15.122 | 18.714 |
-| 净耗时中位数 / Median net minutes | 25.598 | 32.167 | 16.639 | 13.455 | 16.452 |
-| 净耗时 P90 / P90 net minutes | 41.658 | 45.179 | 36.681 | 25.031 | 30.104 |
-| 模型调用/题 / Model calls | 124.660 | 138.920 | 92.370 | 71.160 | 93.600 |
-| 顶层工具调用/题 / Top-level tool calls | 127.360 | 150.070 | 110.480 | 70.990 | 113.780 |
-| 总输入 token/题 / Input tokens | 11,477,169.950 | 14,849,497.540 | 8,771,693.040 | 6,160,934.650 | 9,205,287.290 |
-| 总 token/题 / Total tokens | 11,578,046.900 | 14,966,097.260 | 8,854,513.910 | 6,238,434.510 | 9,292,949.400 |
-| 缓存输入 token/题 / Cached input | 11,404,101.120 | 14,770,140.160 | 8,713,578.230 | 6,099,266.510 | 9,145,025.240 |
-| 非缓存输入 token/题 / Uncached input | 73,068.830 | 79,357.380 | 58,114.810 | 61,668.140 | 60,262.050 |
-| 输出 token/题 / Output | 100,876.950 | 116,599.720 | 82,820.870 | 77,499.860 | 87,662.110 |
-| 输入缓存率 / Input cache hit rate | 99.363% | 99.466% | 99.337% | 98.999% | 99.345% |
-| 扣除重试分钟（全组）/ Retry minutes excluded, total | 56.323 | 51.936 | 185.717 | 217.996 | 114.226 |
-| 缺少用量的请求 / Requests without usage | 3 | 11 | 4 | 5 | 2 |
+## 新版 DSH 与预算 · New DSH and Budgets
 
-| 方案 / Mode | 状态 / Status | 有效进度 / Valid scores | 通过 / Passed | 净分钟/题 / Net minutes | 模型调用/题 / Model calls | 总 token/题 / Total tokens |
-|---|---|---:|---:|---:|---:|---:|
-| 标准 standard + max | 已暂停 / Paused | 2/100 | 0/2 | 18.273 | 110.500 | 14,100,705.000 |
+以下四组均使用 **DSH `0.2.1-rc.2`**、新模型 **`deepseek-v4.1-flash-1017`**（调用标识 `deepseek/deepseek-flash`）和 **`high`** 思考，完成同一批 100 题。这里只展示官方预设与正式插件版本。
 
-标准 + max 的均值只覆盖其 2 道有效完成题，不参与完整 100 题排名。
+All four runs completed the same 100 tasks on **DSH `0.2.1-rc.2`**, using the newer **`deepseek-v4.1-flash-1017`** model (API ID: `deepseek/deepseek-flash`) with **`high`** reasoning. Only official presets and released plugin versions are shown here.
 
-Standard + max means cover its two valid completed tasks and are excluded from the completed 100-task ranking.
+| 指标 / Metric | 标准 / Standard · 默认 / Default | Super Code 0.3.4 · 默认 / Default | 标准 / Standard · 旧预算 / Legacy | Super Code 0.3.5 · 旧预算 / Legacy |
+|---|---:|---:|---:|---:|
+| 通过/有效 / Passed / valid | 45/100 | 40/99 | 46/100 | 48/99 |
+| 待核查 / Pending review | 0 | 1 | 0 | 1 |
+| 净分钟/题 / Net minutes | 17.875 | 20.458 | 20.870 | 16.486 |
+| 模型调用/题 / Model calls | 85.050 | 69.051 | 91.980 | 68.616 |
+| 总 token/题 / Total tokens | 6,832,805.820 | 5,125,240.424 | 7,806,295.960 | 5,131,724.556 |
+| 缓存输入 token/题 / Cached input | 6,710,566.400 | 5,008,071.111 | 7,679,298.560 | 5,016,822.909 |
+| 非缓存输入 token/题 / Uncached input | 59,268.620 | 55,443.192 | 59,291.340 | 53,125.495 |
+| 输出 token/题 / Output | 62,970.800 | 61,726.121 | 67,706.060 | 61,776.152 |
+| 缺少用量的请求 / Requests without usage | 0 | 0 | 0 | 1 |
 
-极简 + high 复用历史基线，其宿主修订与本轮不同，不能把差异完全归因于思考等级。极简 + max、标准 + high、PTC + high 和创造 + high 使用同一冻结 Harness 修订和原生 Web RPC，插件未加载。各组均使用同一固定 100 题和官方评分器。
+两组 Super Code 各有一条 NodeBB 环境异常待核查，暂不计入有效评分和均值。npm 依赖已离线打包，但参考答案仍遇到初始化超时；原答案、判分记录和用量保留。
 
-Minimal + high reuses the historical baseline, whose host revision differs from this run; reasoning effort alone cannot explain the difference. Minimal + max, standard + high, PTC + high, and creative + high use the same frozen Harness revision and native Web RPC, without the plugin. All modes target the same frozen 100 tasks and official grader.
+Each Super Code run has one NodeBB environment issue pending review, excluded from valid-score counts and means. npm dependencies are bundled offline, but reference setup still times out; original answers, verdicts, and usage are retained.
 
-创造保留官方预设与工具定义；评测隔离禁止 `cordis_run` 在宿主上执行动态代码，只读检查仍可使用。
+- **新版组合出现退化。** 相比旧 DSH / 旧模型，标准通过数从 51 降到 45，Super Code 从 0.3.0 候选的 56 降到 0.3.4 的 40；这同时涉及宿主、模型和插件版本变化。
+- **预算是已定位的影响因素。** 新版更早压缩上下文、保留更少原文，PTC 执行时限也有变化。恢复旧预算后，Super Code 从 40 回升至 48，标准从 45 到 46。**0.3.6 已默认恢复旧预算**；表中验证组实际是 **0.3.5 + 显式旧预算**，不是另跑的 0.3.6 成绩。
+- **结果仍有波动。** v4.1 的多轮实验中，同一道题存在一轮通过、另一轮失败的情况。后续版本会尝试改善这种不稳定性；各轮配置也有变化，本轮回升不代表已消除波动，也不能证明全部退化都由预算造成。
 
-Creative retains the official preset and tool definitions. Evaluation isolation blocks host-side dynamic execution through `cordis_run`; read-only inspection remains available.
+- **The newer combination regressed.** Standard fell from 51 passes on the older host/model to 45; Super Code fell from 56 for the 0.3.0 candidate to 40 for 0.3.4. Host, model, and plugin versions changed together.
+- **Budgets are one identified factor.** The newer host compresses earlier, retains less verbatim context, and changes PTC execution deadlines. Restoring the older budgets raised Super Code from 40 to 48 and standard from 45 to 46. **Version 0.3.6 restores these defaults.** The measured row is **0.3.5 with explicit legacy budgets**, not a separate 0.3.6 run.
+- **Run-to-run variation remains.** Across v4.1 experiments, the same task has both passed and failed. Future versions will aim to reduce this variability. Configurations also changed between runs; the recovery does not establish stability or attribute the entire regression to budgets.
 
-“原始分钟”是最终有效作答的 Web RPC 耗时，不含镜像准备和官方评分。“净分钟”进一步扣除该次作答中的失败模型请求与重试等待，不扣除正常思考、工具或测试时间。
+预算恢复的配置包括：按完整上下文窗口计算压力、80% 触发压缩、保留最近 16% 原文、摘要上限 8,192 token、压缩追加与溢出重试各 1 次，以及新版 PTC 默认 / 最大 600 秒。它是多项预算的联合恢复，不是某个参数的单变量实验。官方标准的旧预算组仅覆盖宿主预算，未加载 Super Code；插件对官方预设的预算覆盖需用户主动开启。[预算设置](UsageGuide.md#运行预算--runtime-budgets)
 
-Original minutes measure Web RPC time for the final valid answer, excluding image preparation and grading. Net minutes additionally remove failed model requests and retry waits within that answer, while retaining normal reasoning, tool calls, and tests.
+The restored configuration uses the full context window for pressure accounting, an 80% compression threshold, 16% recent verbatim retention, an 8,192-token summary cap, one additional compression attempt and one overflow retry, plus 600-second default/maximum PTC deadlines on newer hosts. Several budgets were restored together; this is not a single-parameter experiment. The standard legacy-budget run overrides host budgets without loading Super Code. Applying plugin budget settings to official presets remains opt-in. [Budget settings](UsageGuide.md#运行预算--runtime-budgets)
 
-本次逐题核对了极简 + high 的全部 100 份原始证据、补丁及会话日志。已记录 29 次失败请求，扣除失败请求及等待共 **56.323 分钟**，净耗时为 **25.122 分钟/题**。旧调用统计已排除其中 10 次，但仍多计 19 次，本次修正后为 **124.660 次/题**；这 19 次没有有效用量，Token 总量不变。旧统计的 7 次缺失用量中，4 次属于失败请求，剩余 **3 次**发生在预算结束时，日志未返回 usage，无法补齐。版本表同步修正极简的调用数和缺失用量数，历史 JSON 保留原貌。
+[宿主集成探针](../eval/results/swebench-pro-final-100/HostBudgetDiagnostics.json)固定 1,000,000 token 窗口、384,000 输出预留，实际测得压缩阈值从 800,000 变为 550,464，原文尾部预算从 160,000 变为 98,560；两版摘要指令相同，摘要请求上限则从 8,192 变为 65,536。探针使用确定性摘要适配器，不代表摘要质量评测，也不能证明每道 Pro 题都触发了这些变化。更换模型和宿主的历史结果只用于呈现现象；确定因果仍需固定其他条件的重复对照。
 
-This audit checked all 100 original minimal + high receipts, patches, and session logs. It identified 29 failed requests and excluded **56.323 minutes** of failed-request and retry time, giving **25.122 net minutes per task**. The old call count had already excluded ten failures but still included 19; the corrected count is **124.660 calls per task**. Those 19 requests added no valid usage, so token totals are unchanged. Four of the seven previously unknown-usage requests were failures. The remaining **three** occurred at the budget cutoff and have no recorded usage to recover. The version table uses the corrected minimal call and unknown-usage counts; historical JSON remains unchanged.
+A [host integration probe](../eval/results/swebench-pro-final-100/HostBudgetDiagnostics.json) fixed a 1,000,000-token window with 384,000 reserved output tokens. The measured compression threshold changed from 800,000 to 550,464, and recent verbatim retention from 160,000 to 98,560. Summary instructions were identical; the summary request cap changed from 8,192 to 65,536. The probe used deterministic summaries, so it neither measures summary quality nor shows that every Pro task triggered these changes. Historical host/model comparisons describe observations; causal attribution requires repeated controls with other conditions fixed.
 
-标准 + high、PTC + high、极简 + max 和创造 + high 的净计时已覆盖全部有效题。其余缺失用量也已检查原始结算和流记录，未找到可恢复的 usage；这些缺失不会被估算成零费用。调用数排除已记录的失败请求，预算结束时尚未结算用量的请求仍计入次数并单列为缺失用量。总 token = 缓存输入 + 非缓存输入 + 输出，输出含思考 token，不再次叠加。数字保留三位小数，独立舍入可能造成末位差异。
+逐题对照中，Super Code 旧预算组相较默认预算组新增通过 12 题、回退 4 题，净增 8 题；标准对应新增 7 题、回退 6 题，净增 1 题。这证实了跨轮通过集合并不固定，但预算和插件配置也在变，尚不能据此估计固定配置下的随机波动率。评分环境异常的原补丁复核与模型重新作答是两回事，不把前者当作模型不稳定的证据。
 
-Net timing covers every valid task for standard + high, PTC + high, minimal + max, and creative + high. Original settlement and stream records were also checked for the remaining missing usage, with no recoverable usage found; this does not imply zero cost. Call counts exclude logged failed requests. Requests interrupted at the budget cutoff remain counted and are marked as unknown usage. Total tokens = cached input + uncached input + output, which already includes reasoning. Do not add reasoning again. Values use three decimal places; independent rounding can produce a last-digit difference.
+Paired task results show 12 gains and four regressions for Super Code under legacy budgets, a net gain of eight. Standard has seven gains and six regressions, a net gain of one. Passing sets differ across runs, but budget/plugin configurations also changed; these comparisons do not estimate random variability under a fixed configuration. Regrading an unchanged patch after an environmental failure is distinct from generating a new answer and is not evidence of model instability.
 
-[官方预设逐题快照](../eval/results/swebench-pro-final-100/OfficialPresetResults.json)保留全部 **502 个有效结果**（五组各 100 题、标准 + max 2 题）的成绩、用量、原始 / 净耗时、核算说明与证据哈希。README 和本表来自同一快照。
+[新版 DSH 逐题快照](../eval/results/swebench-pro-final-100/HarnessRc2Results.json) · [GLM 逐题快照](../eval/results/swebench-pro-final-100/GLMComparison.json)
 
-The [official-preset snapshot](../eval/results/swebench-pro-final-100/OfficialPresetResults.json) contains all **502 valid results**—100 for each of the five completed modes and 2 for standard + max—with usage, raw/net timing, audit notes, and evidence hashes. README and this table use the same snapshot.
+[New-DSH per-task snapshot](../eval/results/swebench-pro-final-100/HarnessRc2Results.json) · [GLM per-task snapshot](../eval/results/swebench-pro-final-100/GLMComparison.json)
 
 ## 相比官方 minimal · Relative to Official minimal
 
 | 版本 / Version | 通过率变化 / Pass-rate change | 平均耗时 / Mean time | 总 token / Total tokens | 新通过 / Gains | 回退 / Regressions |
 |---|---:|---:|---:|---:|---:|
 | 0.0.9 | +4.000 pp | -35.923% | -16.884% | 7 | 3 |
-| 0.1.2 | +8.000 pp | -37.663% | -14.164% | 10 | 2 |
+| 0.1.2 | +7.000 pp | -37.663% | -14.164% | 10 | 3 |
 | 0.2.0 | +8.000 pp | -41.025% | -19.683% | 11 | 3 |
 | 0.3.0 Batch.3 | +10.000 pp | -47.593% | -44.879% | 13 | 3 |
 
-Batch.3 相比 0.2.0 平均耗时减少 11.1%、总 token 减少 31.4%、模型调用减少 26.2%，通过数从 52 增至 54；逐题新通过 8 题、回退 6 题。这是同题单轮结果，2 题的净增不能据此认定为稳定的质量提升。
+Batch.3 相比 0.2.0 平均耗时减少 11.1%、总 token 减少 31.4%、模型调用减少 26.2%，通过数从 54 增至 56；逐题新通过 8 题、回退 6 题。这是同题单轮结果，2 题的净增不能据此认定为稳定的质量提升。
 
-Against 0.2.0, Batch.3 uses 11.1% less time, 31.4% fewer total tokens, and 26.2% fewer model calls. Passes rise from 52 to 54, with eight gains and six regressions. This is one run on the same tasks; a net gain of two does not establish a stable quality improvement.
+Against 0.2.0, Batch.3 uses 11.1% less time, 31.4% fewer total tokens, and 26.2% fewer model calls. Passes rise from 54 to 56, with eight gains and six regressions. This is one run on the same tasks; a net gain of two does not establish a stable quality improvement.
 
-0.2.0 与 0.1.2 都通过 52 题，平均耗时下降 5.4%、总 token 下降 6.4%，但逐题有 6 题改善、6 题回退。相对 minimal，0.2.0 新通过 11 题、回退 3 题（37、396、503），净增 8 题。不能把总体提升写成“原先正确的都没有退化”。
+0.2.0 通过 54 题，0.1.2 通过 53 题；平均耗时下降 5.4%、总 token 下降 6.4%，逐题有 7 题改善、6 题回退。相对 minimal，0.2.0 新通过 11 题、回退 3 题（37、396、503），净增 8 题。不能把总体提升写成“原先正确的都没有退化”。
 
-Both 0.2.0 and 0.1.2 pass 52 tasks. Version 0.2.0 uses 5.4% less time and 6.4% fewer total tokens, with six gains and six regressions. Against minimal, it gains 11 tasks and regresses on three (37, 396, 503), for a net gain of eight. Aggregate improvement does not mean every previous pass is preserved.
+Version 0.2.0 passes 54 tasks versus 53 for 0.1.2. It uses 5.4% less time and 6.4% fewer total tokens, with seven gains and six regressions. Against minimal, it gains 11 tasks and regresses on three (37, 396, 503), for a net gain of eight. Aggregate improvement does not mean every previous pass is preserved.
 
 ## 修正了什么 · What Was Corrected
 
-| 版本 / Version | 原始通过 / Original passes | 校正通过 / Corrected passes | 复核题数 / Regraded tasks |
+| 版本 / Version | 原始通过 / Original passes | 通过 / Passed | 环境复评题数 / Environment regrades |
 |---|---:|---:|---:|
-| minimal | 41 | 44 | 4 |
-| 0.0.9 | 46 | 48 | 3 |
-| 0.1.2 | 49 | 52 | 4 |
-| 0.2.0 | 48 | 52 | 5 |
+| minimal | 41 | 46 | 4 |
+| 0.0.9 | 46 | 50 | 3 |
+| 0.1.2 | 49 | 53 | 4 |
+| 0.2.0 | 48 | 54 | 5 |
 
-16 条评分记录出现 ConfigFileTest 500ms 超时或 Jest worker SIGKILL 等环境异常，已用**原补丁**重新运行官方评分；每条取两次无该异常且一致的结果，不采用“重试到通过”的取优口径。12 条恢复通过，4 条仍失败。复评分没有新增模型调用，原始评分、用量和补丁均保留。
+16 条评分记录出现 ConfigFileTest 500ms 超时或 Jest worker SIGKILL 等环境异常，已用**原补丁**重新运行官方评分；每条取两次无该异常且一致的结果，不采用“重试到通过”的取优口径。12 条恢复通过，4 条仍失败。表中通过数还包含这四组已核实的 7 条测试名称差异修正。复评分没有新增模型调用，原始评分、用量和补丁均保留。
 
-Sixteen grading records had anomalies such as the ConfigFileTest 500 ms timeout or a killed Jest worker. Each was regraded with the **original patch**, requiring two matching results without that anomaly—not selecting the best result from retries. Twelve recovered to a pass and four remained failures. Regrading added no model calls; the original scores, usage, and patches are preserved.
+Sixteen grading records had anomalies such as the ConfigFileTest 500 ms timeout or a killed Jest worker. Each was regraded with the **original patch**, requiring two matching results without that anomaly—not selecting the best result from retries. Twelve recovered to a pass and four remained failures. Pass counts also include seven verified test-name corrections across these four runs. Regrading added no model calls; the original scores, usage, and patches are preserved.
 
 [四版本逐题数据](../eval/results/swebench-pro-final-100/CorrectedFourVersions.json)包含全部 400 条评分、调用数、token、耗时、补丁与证据哈希，以及逐条修正原因。历史 JSON 保留原貌；极简的调用数和缺失用量数采用上述原会话核算，其余版本指标来自这份校正汇总。结果文件留在仓库，不重复放进 npm 包。
 
@@ -124,15 +200,15 @@ The separate [Batch.3 per-task data](../eval/results/swebench-pro-final-100/Batc
 
 ## 如何理解 · How to Read These Results
 
-- **同题比较：** 固定题集标识为 `swebench-pro-hard-100-ddd22492f1c38839`，使用同一开发测试模型、原生 DSH Web RPC 和官方评分器。版本表均为 `high` 思考等级，官方预设表的等级按列标明。这 100 题按既有难度方法选出，并非官方认定的“最难 100 题”；用于候选冻结后的效果评测及 bug 排查，不参与效果调优。
-  **Same tasks:** The frozen selection is `swebench-pro-hard-100-ddd22492f1c38839`, using the same development test model, native DSH Web RPC, and the official grader. All version-comparison runs use `high` reasoning; the official-preset table labels each effort level. These 100 tasks were selected using the existing difficulty-ranking method, rather than an official hardest-100 designation. They are used to evaluate frozen candidates and investigate bugs, not for performance tuning.
+- **同题比较：** 固定题集标识为 `swebench-pro-hard-100-ddd22492f1c38839`，使用官方评分器。旧版本与官方预设表使用 DSH `0.1.5-rc.2` / `deepseek-v4.1-flash`；GLM 与新版 DSH 对照的宿主、模型、预算另列。DSH 通过原生 Web RPC 执行，ZCode 使用完整原生 CLI。版本表均为 `high` 思考等级，官方预设表的等级按列标明。这 100 题按既有难度方法选出，并非官方认定的“最难 100 题”；用于候选冻结后的效果评测及 bug 排查，不参与效果调优。
+  **Same tasks:** The frozen selection is `swebench-pro-hard-100-ddd22492f1c38839`, using the official grader. Historical version and official-preset tables use DSH `0.1.5-rc.2` / `deepseek-v4.1-flash`; GLM and newer-DSH tables identify their own hosts, models, and budgets. DSH uses native Web RPC; ZCode uses its complete native CLI. All version-comparison runs use `high` reasoning; the official-preset table labels each effort level. These 100 tasks were selected using the existing difficulty-ranking method, rather than an official hardest-100 designation. They are used to evaluate frozen candidates and investigate bugs, not for performance tuning.
 - **时间：** 版本表保留每题最终有效作答的原始 Web RPC 耗时，不计官方评分、下载镜像和复评分，但未逐项扣除该次作答内部的失败请求与重试等待。中位数取第 50、51 项均值，P90 取排序后的第 90 项。0.0.9 的旧文档曾写 16.27 分钟，这里按历史统一口径为 16.458 分钟。官方预设表另列净耗时，两种口径不混用。
   **Time:** The version table retains raw Web RPC time for each final valid answer, excluding grading, image downloads, and regrading, but without subtracting individual failed requests and retry waits within that answer. The median averages the 50th and 51st values; P90 is the 90th ordered value. An older 0.0.9 document reported 16.27 minutes; the historical convention gives 16.458 minutes. The official-preset table reports net time separately; the two measures must not be mixed.
-- **用量：** 纳入每题最终评分尝试的已记录调用，先逐题合计再对 100 题取平均。输入包含缓存读取，输出包含思考 token；缓存率为全部缓存输入除以全部输入，而非逐题缓存率的平均。未返回用量的请求不估算，因此 token 不代表完整账单费用，也不包括先前被放弃的尝试成本。
-  **Usage:** Recorded calls from each task’s final scored attempt are summed per task, then averaged over 100 tasks. Input includes cache reads and output includes reasoning tokens; the cache rate is total cached input divided by total input, not the mean per-task rate. Missing usage is not estimated, so tokens do not represent a complete bill or the cost of earlier abandoned attempts.
+- **用量：** 纳入每题最终评分尝试的已记录调用，先逐题合计再对有效评分题数取平均；待环境核查的题目暂不计入均值。输入包含缓存读取，输出包含思考 token；缓存率为全部缓存输入除以全部输入，而非逐题缓存率的平均。未返回用量的请求不估算，因此 token 不代表完整账单费用，也不包括先前被放弃的尝试成本。
+  **Usage:** Recorded calls from each task’s final scored attempt are summed per task, then averaged over tasks with valid scores; pending environmental reviews are excluded from means. Input includes cache reads and output includes reasoning tokens; the cache rate is total cached input divided by total input, not the mean per-task rate. Missing usage is not estimated, so tokens do not represent a complete bill or the cost of earlier abandoned attempts.
 - **候选身份：** 0.2.0 表示已评测的分层记忆候选，其实验包内部版本仍为 0.1.3，包 SHA-256 为 `164cc1b505c05288f01b6f12c0756af049dbde8f1a49bdb11f9a320a19c925f5`。新整合的记忆 UI 与兼容改动进行单测及真实宿主回归，未重新运行这 100 次模型任务。
   **Candidate identity:** The evaluated memory-hierarchy candidate is reported as 0.2.0; its experimental package still carried version 0.1.3 and SHA-256 `164cc1b505c05288f01b6f12c0756af049dbde8f1a49bdb11f9a320a19c925f5`. The integrated memory UI and compatibility changes undergo unit and real-host regression checks, not a fresh 100-task model run.
 - **0.3.0 来源：** 本页成绩属于内部版本 `0.3.0-batch.3` 的实际安装候选。整合时按冻结的运行模块逐文件核对，保留主干 0.2.1 的语言资源和兼容改动；发布包做类型、单测、打包及真实宿主回归，没有重新执行这 100 次模型任务。Batch.3 与分层记忆候选的 Harness 提交同为 `649bfcddf0e3532510a38380b9620570d8b13818`，仍不能分离提示词和工具呈现方式各自的作用。
   **0.3.0 source:** These scores belong to the installed candidate carrying internal version `0.3.0-batch.3`. Integration checks the frozen runtime modules individually and retains main's 0.2.1 locale and compatibility updates. The release package undergoes type checks, unit tests, package checks, and real-host regression rather than rerunning those 100 model tasks. Batch.3 and the memory-hierarchy candidate share Harness commit `649bfcddf0e3532510a38380b9620570d8b13818`; their results still do not isolate prompt changes from tool presentation changes.
-- **归因与隐私：** 各轮 Harness 提交不同，记忆工具实际触发也有限，不能把全部差异归因于记忆或单一改动。公开数据仅保留核对所需字段，不包含开发模型路由、凭据、环境变量、本机路径或用户消息原文。
-  **Attribution and privacy:** Harness revisions differ, and memory-tool use was limited; these results do not isolate memory or any single change. Public data retains audit fields without development model routes, credentials, environment variables, machine paths, or verbatim user messages.
+- **归因与隐私：** 各轮 Harness 提交不同，记忆工具实际触发也有限，不能把全部差异归因于记忆或单一改动。公开数据仅保留核对所需字段，不包含私有提供方地址、凭据、环境配置、本机路径或用户消息原文。
+  **Attribution and privacy:** Harness revisions differ, and memory-tool use was limited; these results do not isolate memory or any single change. Public data retains audit fields without private provider addresses, credentials, environment configuration, machine paths, or verbatim user messages.

package/docs/UsageGuide.md

@@ -24,6 +24,58 @@ The default guidance calls for parallel reads when useful, ordered writes, tests
 
 Batching reduces round trips between the model and tools. It does not guarantee that every operation runs faster or change model, permission, or memory settings.
 
+## 任务状态 · Task Status
+
+Super Code 侧边栏依次显示“任务状态”“协作执行”“记忆库”。任务状态默认展开，三项互斥且始终保留一项展开；原圆圈 Agent 执行树保留在“协作执行”中。每个 Agent 的任务树根节点显示其名字，步骤、动作、文件条目不重复标注名字。
+
+The Super Code sidebar contains Task status, Agent execution, and Memory library in that order. Task status opens by default; exactly one section stays open. The original circular Agent graph remains under Agent execution. Each Agent's name appears at its task-tree root only.
+
+任务状态只读取已有会话记录：目标取已有任务/目标记录，缺少时展示用户原文；步骤取模型已经写入的待办，进度显示已完成数/总数；动作与结果取工具日志。运行结束不会被当作任务完成。没有步骤时不会补造计划、百分比或阶段说明。
+
+This view reads existing journal facts: recorded objectives or the user's original request, existing todos and their completed/total counts, and tool activity and results. A stopped run is not treated as a completed objective. Missing plans or progress are not invented.
+
+任务、步骤、已加载动作和补充要求都直接展开，不需要逐项点击。任务状态使用单一虚拟滚动列表，只渲染视口附近的行；长文本按实际高度显示，滚动即可查看所有已加载记录和文件，无需点击“更多”。切换侧栏区块后保留阅读位置。运行环遵循系统的“减少动态效果”设置。
+
+Tasks, steps, loaded activity, and follow-up requests are fully expanded. One virtualized list renders rows near the viewport and measures wrapped text at its actual height. Scroll through every loaded record and file without a More button. Switching sections retains the reading position, and running indicators respect reduced-motion preferences.
+
+文件变更记录列出已成功执行并能从工具参数或结果 diff 元数据确认的文件操作，包含普通和 PTC 嵌套调用。它不是当前工作区的完整 Git diff：终端或外部脚本的间接修改可能缺失，历史操作也不代表文件当前仍有净修改。未完成、失败、只读操作及子 Agent 继承的历史不会被计作本次成功修改。
+
+File operations show successful mutations identifiable from tool arguments or result diff metadata, including native and nested PTC calls. This is not a complete current Git diff: indirect terminal/script changes may be absent, and historical operations do not establish a current net change. Pending, failed, read-only, and fork-inherited operations are not counted as that Agent's successful changes.
+
+此功能不增加提示词、模型请求、工具定义或执行钩子，也不向模型上下文写入界面内容；不要求使用特定模型、预设、Skill 或固定步骤。未知工具仍显示其调用与结果，缺少结构化记录时只减少相应展示，不影响模型继续工作。记录有显示上限，未加载或超出范围时会提示；完整执行内容可打开详情查看。
+
+This feature adds no instructions, model requests, tool definitions, or execution hooks, and never writes display data into model context. It requires no specific model, preset, Skill, or workflow. Unknown tools retain their activity and results; absent structured facts reduce the displayed detail only. Bounded or unloaded records are labeled, with full execution content available in details.
+
+## 删除保护 · Deletion Protection
+
+“上下文配置”中的“删除保护”支持三种模式，**默认宽松**。
+
+| 模式 / Mode | 行为 / Behavior |
+| --- | --- |
+| 关闭 / Off | 不添加删除保护提示，不额外拦截命令。No deletion instructions or extra command interception. |
+| 宽松 / Relaxed（默认 / default） | 默认使用 `trash`，脚本中也建议使用；用户明确要求时可使用 `rm`，无需本插件额外二次确认。Prefer recoverable trash, including in scripts; explicit user requests may use `rm` without additional plugin confirmation. |
+| 严格 / Strict | 脚本也禁止直接使用 `rm`；识别到永久删除命令时，仅临时文件或构建产物清理可经用户逐次二次确认放行。Scripts must also avoid `rm`; recognized permanent deletion requires one-time confirmation for each temporary-file or build-artifact cleanup. |
+
+宽松模式保留指令：**删除文件或目录默认用 `trash <path>`（可恢复）；仅清理临时文件、构建产物且我已确认时才用 `rm`。** 脚本、内联脚本和间接调用中也建议使用回收站。用户明确说明使用 `rm` 时，该要求可作为确认，并按用户指定范围执行；宽松依靠指令引导，不增加命令拦截，宿主原有权限检查仍然有效。
+
+Relaxed mode instructs Agents to use recoverable `trash <path>` by default and prefer it in scripts and indirect calls. An explicit request to use `rm` counts as confirmation within the requested scope. Guidance is prompt-based; host permission checks still apply.
+
+默认只保护 Super Code。“同时应用到官方预设”开关默认关闭，与预算的同名开关独立；开启后，所选模式也应用到标准、PTC、极简、创造预设。关闭模式时保留此开关的选择。保存后作用于后续命令。旧配置 `true` 保留为严格，`false` 保留为关闭；缺省配置及恢复默认使用宽松。
+
+Only Super Code is protected by default. “Also apply to official presets” defaults off, independently of official-preset budgets, and applies the chosen mode to Standard, PTC, Minimal, and Create. Off retains this preference. Saved changes affect subsequent calls. Legacy `true` maps to Strict and `false` to Off; missing settings and reset use Relaxed.
+
+极简预设通过可记录、可回放的插件消息接收规则，模式变化时明确替代先前规则，兼容 v4 会话日志。
+
+Minimal receives rules through logged, replayable plugin messages compatible with v4 session logs; mode changes explicitly replace earlier rules.
+
+严格模式在终端执行前识别 `rm`、常见包装、内联 shell 脚本及 PowerShell 删除别名（如 `Remove-Item`），PTC 内的终端调用也适用。宿主对当前命令和工作目录请求一次性确认；拒绝、取消、确认不可用或出错均拦截。此确认不授予后续调用权限，也不代替宿主其他权限检查。缺少 `trash` 时应使用其他可恢复方式或停止。
+
+Strict mode checks terminal calls, including those nested in PTC, for `rm`, common wrappers, inline shell scripts, and PowerShell deletion aliases such as `Remove-Item`. Only a real one-time host approval for the current command and working directory proceeds. Rejection, cancellation, unavailable approval, and errors block execution. If trash is unavailable, use another recoverable mechanism or stop.
+
+严格模式的命令识别并非操作系统沙箱：不解析外部脚本文件或任意混淆程序，不覆盖所有语言的文件删除 API；脚本仍须遵守指令，需要进程级隔离时继续使用宿主沙箱。
+
+Strict command recognition is not an OS sandbox: it does not inspect external script files, arbitrary obfuscated programs, or every language's deletion API. Scripts must follow the instructions; use the host sandbox for process-level isolation.
+
 ## 运行预算 · Runtime Budgets
 
 打开设置中的“Super Code 模式”（部分版本位于“插件”→“插件配置”）。顶部“预设状态”用于查看和安装预设；“上下文配置”用于调整预算。插件默认已使用此前 Pro 测试中的旧预算，无需手动填写。界面使用百分数和秒；括号内仍显示当前宿主的默认值，便于与输入框中的实际配置比较。
@@ -212,3 +264,63 @@ These are recorded host actions, not proof that the model understood or followed
 历史会话的记忆可直接查看，不需要恢复 Agent 或再次调用模型。记忆库支持新增、编辑、取消、保存和删除。编辑时可修改类型、标题和内容；取消不保存，删除需要确认。手动保存的条目标为“手动维护”，仅保留当前内容，不保留版本历史。
 
 You can browse memory from stored conversations without resuming an Agent or making another model call. The library supports Add, Edit, Cancel, Save, and Delete. Edit the type, title, and content; Cancel discards the draft, and Delete asks for confirmation. Manually saved entries are marked accordingly. Only current content is kept, with no version history.
+
+
+## MCP 连接 · MCP Connection
+
+设置 → Super Code 模式默认打开“首页”，集中显示预设状态与版本、保护等级、MCP 开关，以及正在连接和历史对话的数量。客户端和关联会话详情、打开会话及断开操作位于“连接”标签。预设、上下文、删除保护、连接分别配置；预设配置页直接展示表单。MCP 默认关闭，在“连接”标签中勾选允许的工作目录、调整本机端口和最大连接数；修改会自动保存，无需确认按钮。服务只监听 `127.0.0.1`，地址以页面显示为准；端口冲突会显示错误。
+
+Settings → Super Code opens **Home**, with preset status and versions, protection level, the MCP switch, and counts of connected and past conversations. Client and linked-session details, opening conversations and disconnect actions are in **Connection**. Preset, context, deletion protection and connection settings have separate tabs. Preset configuration shows its form directly. MCP is disabled by default. In **Connection**, select allowed working directories and adjust the local port and maximum connections. Changes save automatically without a confirmation button. The service listens on `127.0.0.1` only; use the displayed URL. Port conflicts are reported explicitly.
+
+工作目录以勾选列表展示，每次进入连接页会重新读取 DSH 工作区。首次配置时预选已有有效工作区，修改后自动保存并保留用户选择；后来新增的工作区不会静默获得访问权限。可以通过目录选择器添加目录，取消勾选会撤销该目录的入口授权，取消最后一个允许目录时会同时关闭 MCP。手动添加但未勾选的目录仍保留在列表中。允许目录包含其子目录。
+
+Directories appear as a checkbox list refreshed from DSH workspaces when opening Connection. Existing valid workspaces are initially selected in the first configuration draft; edits save automatically and later workspaces are never silently granted access. Add directories with the directory picker. Unchecking revokes that directory's admission grant; removing the last grant also turns MCP off. Unchecked manually added directories remain listed. Each grant includes descendants.
+
+最大连接数限制真实 MCP 协议会话（默认 3，上限 32），并同时作为任务执行并发上限。在连接页可以断开客户端，空闲 10 分钟也会释放连接；断开不会取消已接收任务。正在连接的对话按其关联 MCP 连接是否在线统计，断开后计入历史；与任务是否执行完成无关。连接凭证默认展开，离开连接页后隐藏，再次进入时重新读取。
+
+Maximum connections counts MCP protocol sessions (default 3, maximum 32) and is also the task execution concurrency limit. Disconnect clients from Connection; idle connections also expire after 10 minutes. Disconnecting does not cancel accepted tasks. Conversations count as connected while their linked MCP connection is online, regardless of task completion; after disconnect they count as past conversations. The token is expanded by default in Connection, cleared when leaving the tab and reloaded on return.
+
+### 连接 Prompt · Connection Prompt
+
+1. 在连接页复制“连接 Prompt”，交给支持 Streamable HTTP MCP 的客户端配置连接。提示词包含页面当前地址、认证方式、六项工具与任务状态约定，不包含真实凭证，也不绑定特定客户端。连接后先调用 `dsh_sessions` 按工作目录查看最近对话、状态和连接额度，再由调用方选择传 `taskId` 复用历史或传 `newConversation: true` 新建；不会默认复用最新对话。
+2. 单独复制连接凭证，在客户端安全保存并配置为 `Authorization: Bearer <连接凭证>`。不要把实际凭证写进仓库或共享提示词。
+3. 保持提供连接的 DSH Web 服务或桌面应用运行。更换凭证后同步更新客户端；旧凭证立即失效。客户端是否允许由提示词自动配置 MCP，取决于客户端自身能力；也可以使用页面地址和认证方式手动配置。
+
+Copy **Connection Prompt** from the Connection tab and give it to a client that supports Streamable HTTP MCP. It contains the current URL, authentication method, six tools and task-state conventions, without an actual token or client-specific command. After connecting, call `dsh_sessions` for the working directory to see recent conversations, statuses and connection capacity. Let the caller choose whether to pass `taskId` to reuse history or `newConversation: true` to create a new root; `dsh_run` never defaults to the latest conversation. Copy the token separately and securely configure `Authorization: Bearer <connection token>` in the client. Keep the serving DSH process running, and update the client after token rotation. Whether a prompt can configure MCP automatically depends on the client; manual setup using the shown URL and authentication is also supported. Never put actual credentials in repository files or shared prompts.
+
+| 工具 / Tool | 用途 / Behavior |
+|---|---|
+| `dsh_sessions` | 连接后按允许的工作目录返回最近对话、状态、可复用标记、每条对话的连接数，以及当前/最大/剩余连接数和任务并发占用。调用方据此选择复用或新建。 / After connecting, list recent conversations for an allowed working directory with status, reuse availability, per-conversation connection count, current/maximum/available connections, and active task capacity. Use it to choose reuse or a new root. |
+| `dsh_run` | 传 `taskId` 精确复用历史根会话；传 `newConversation: true` 明确新建，未传时为兼容旧客户端也新建。相同 `requestId` 与相同输入不会重复提交，输入不同会报冲突。 / Pass `taskId` to reuse an exact history entry; pass `newConversation: true` to make a new root explicit. Omitting both also creates a new root for backward compatibility. Retrying identical input with the same request ID does not dispatch again; conflicting input is rejected. |
+| `dsh_wait` | 提供任务 ID 时读取状态、输出、工作区观察及游标后的事件，最长等待 30 秒；省略任务 ID 时分页列出本服务持有的任务。 / Read task state, output, workspace observations and events after a cursor, with waits bounded to 30 seconds; omit the task ID to list owned tasks. |
+| `dsh_send` | 在同一根会话补充要求或明确继续，使用新的请求 ID；不会代替用户批准宿主权限。 / Queue a follow-up or explicitly continue the same root session with a new request ID. Does not approve host permissions. |
+| `dsh_request_directory` | 申请新增工作目录，由 DSH 用户明确批准；重复请求查询审批状态。 / Request additional directory access with explicit consent in DSH; repeat to poll the decision. |
+| `dsh_cancel` | 请求取消根会话及受管理后代；需继续观察真实状态，不能把取消请求当成全部停止。 / Request cancellation of the root and managed descendants; observe the resulting state to confirm execution stopped. |
+
+### 新增目录申请 · Additional Directory Requests
+
+外部会话可调用 `dsh_request_directory`，提交稳定的 `requestId`、已存在的绝对 `path` 和 `reason`。DSH 会在全局弹出确认对话框，显示客户端名称、实际目录和申请理由，不需要先打开设置。只有用户点击“允许访问”，才会将该目录加入列表并勾选；审批沿用最新配置，不覆盖同时发生的其他设置修改，也不会断开已有 MCP 连接。申请不会触发模型调用，且不能由模型的自动审批策略代为同意。
+
+重复相同输入可查询 `pending` / `approved` / `rejected` / `expired` 状态；相同 ID 改变输入会报冲突。批准前不能在该目录委派任务。待审批请求最多 8 条，5 分钟过期；拒绝、关闭服务或重启均不自动授权。请求历史为有界的进程内记录（最多 100 条），已批准的目录配置会保存。客户端名称和理由来自客户端，仅供辨认。
+
+External sessions call `dsh_request_directory` with a stable `requestId`, an existing absolute `path` and a `reason`. A global DSH dialog shows the client name, canonical directory and reason even when settings is closed. Only the user's **Allow access** action adds and selects the directory. Approval merges into the latest configuration without overwriting concurrent changes or disconnecting clients. It does not invoke a model and cannot be approved by a model's automatic permission policy.
+
+Repeat identical input to read `pending`, `approved`, `rejected` or `expired`; changing input under the same ID conflicts. Delegation is blocked until access is approved. At most eight pending requests are allowed, expiring after five minutes. Rejection, service shutdown and restart never grant access. Request history is in memory and bounded to 100 entries; approved directory settings persist. Client names and reasons are supplied by the caller for identification.
+
+### 状态、权限与恢复 · State, Permissions and Recovery
+
+任务沿用当前宿主的默认模型、Super Code 预设和权限；不修改普通会话的提示词或执行策略，也不会自动放行权限。调用方的沙箱不会自动传播到 DSH。允许目录限制用于任务入口，不构成文件系统沙箱；实际工具权限由 DSH 管理。同一工作区不会并行委派，可由调用方自行准备独立 worktree；插件不创建、删除或合并 worktree。
+
+Tasks use the host’s default model, Super Code preset and permissions without changing ordinary conversation prompts or execution strategy. Caller sandbox restrictions do not automatically propagate to DSH. Allowed directories govern task admission, not filesystem isolation; DSH controls tool permissions. Delegations in the same workspace do not run concurrently. Callers may supply separate worktrees; the plugin does not create, delete or merge them.
+
+`waiting_confirmation` 表示需要在 DSH 处理权限确认或受阻的回合。`finished` 仅表示根会话和已观测的受管理后代执行结束，返回的 `acceptance` 始终为 `not-verified`，需要调用方验证结果。文件信息来自执行前基线与当前 Git 工作区的有界观察，会保留原有脏文件列表，不能证明全部变化均由本任务产生；非 Git 目录、超出观察上限或读取失败时会标记不可用。
+
+`waiting_confirmation` requires action in DSH. `finished` means the root and observed managed descendants have settled; it does not certify acceptance. Results carry `acceptance: not-verified`. File information is a bounded Git workspace observation relative to the starting baseline, including pre-existing dirty files, and does not establish exclusive attribution. Non-Git directories, exceeded observation limits and read failures are reported as unavailable.
+
+等待超时或客户端断线不会取消执行。关闭连接停止接收请求，已接收任务继续由 DSH 管理。重启或热重载后不自动重发 prompt；可通过 `dsh_sessions` 或任务列表找回 ID，先观察会话，再明确继续。无法确认状态时保留 `interrupted` 或 `unavailable`，避免误报完成；未确认停止的任务会继续占用并发额度。
+
+Wait timeouts and client disconnections do not cancel execution. Disabling the connection stops accepting requests while DSH continues managing accepted work. Restart and hot reload never automatically replay prompts. Recover task IDs through `dsh_sessions` or the task listing, inspect the session, then explicitly continue. Unconfirmed tasks remain interrupted or unavailable and retain their concurrency reservation.
+
+任务记录、配置和凭证保存在当前 profile 的 `super-code-connection` 目录中，目录权限为 0700，文件为 0600；同一配置目录只允许一个服务实例持有。当前上限为 200 个任务记录、每任务 128 个补充操作和最近 200 条状态事件，输出保留最后 12,000 个字符。达到记录上限会明确拒绝新任务，不会悄悄丢弃幂等记录并重跑。
+
+State, configuration and credentials are stored in the profile’s `super-code-connection` directory, with directory mode 0700 and file mode 0600. A profile has one service owner. Limits are 200 task records, 128 follow-up operations per task, the latest 200 state events, and the last 12,000 output characters. Reaching the history limit explicitly rejects new tasks rather than silently discarding idempotency records and redispatching work.