@sqdr2/dsh-fusion 0.0.0-stage → 0.3.2

package/INSTALL.md

@@ -0,0 +1,89 @@
+# Install Fusion
+
+[中文](INSTALL.zh.md) · Product pages: [README.md](README.md) (中文), [README.en.md](README.en.md)
+
+Requires **DeepSeek Harness 0.2.0-rc.2 or 0.2.1-rc.2**. Other versions are not supported.
+
+> This package is a fork of [`aa2246740/dsh-model-fusion`](https://github.com/aa2246740/dsh-model-fusion), published as
+> `@sqdr2/dsh-fusion`. Because the package name changed, an installed `dsh-model-fusion` is not upgraded automatically;
+> install the new package once as described below and its data migrates on first start.
+>
+> The package name and the plugin id are two different things: the package is `@sqdr2/dsh-fusion`, while the plugin id
+> (the `- id:` in the composition, and the name of the data directory) stays `dsh-fusion`. An upgrade therefore changes
+> only where the code is installed, never the data it reads.
+
+## From npm (recommended)
+
+```sh
+dsh plugin --profile web add @sqdr2/dsh-fusion
+```
+
+## From GitHub
+
+The repository ships the built `lib/`, so nothing is compiled locally.
+
+```sh
+dsh plugin --profile web add github:SQDR2/dsh-fusion
+```
+
+If `dsh` is not on PATH, pin one supported CLI:
+
+```sh
+npx @deepseek-ai/dsh@0.2.0-rc.2 plugin --profile web add @sqdr2/dsh-fusion
+# or
+npx @deepseek-ai/dsh@0.2.1-rc.2 plugin --profile web add @sqdr2/dsh-fusion
+```
+
+This writes only the `web` profile. Reopen a running Web Host once and reload the page.
+
+## From a local checkout (development)
+
+```sh
+git clone https://github.com/SQDR2/dsh-fusion.git ~/github/dsh-fusion
+cd ~/github/dsh-fusion && corepack pnpm@9.15.9 install --frozen-lockfile && cd -
+dsh plugin --profile web add ~/github/dsh-fusion
+```
+
+## DSH Studio desktop app
+
+Click **Plugins** in the left sidebar → **Add plugin**, and enter in "Package name or address":
+
+```text
+@sqdr2/dsh-fusion
+```
+
+`github:SQDR2/dsh-fusion` works there too. Then quit and reopen DSH Studio (plugins take effect at the next start).
+
+## Upgrading from dsh-model-fusion
+
+1. Remove the old package first, so two packages never register the Fusion entry at once:
+
+   ```sh
+   dsh plugin --profile web remove dsh-model-fusion
+   ```
+
+2. Install `@sqdr2/dsh-fusion` as above. Do **not** delete the old data directory first: everything in
+   `$DSH_HOME/plugins/dsh-model-fusion/` (tasks, usage, settings) is migrated to
+   `$DSH_HOME/plugins/dsh-fusion/` on first start.
+3. Restart DSH (quit and reopen the desktop app; restart the Web Host and reload the page).
+4. Existing sessions need no edit: the Fusion entry in the model menu points at the new route on its own.
+
+## After installing
+
+1. Sign in to at least two models in DSH: a strong Lead and a much cheaper Sidekick. Built-in providers work, and so do the
+   subscription routes of [dsh-oauth-login](https://github.com/aa2246740/dsh-oauth-login).
+   To use agy (Google Antigravity) as the Sidekick, also install
+   [dsh-agy-worker](https://github.com/SQDR2/dsh-agy-worker); its requirements are in
+   [README.en.md](README.en.md#using-agy-as-the-sidekick-dsh-agy-worker).
+2. Open the **Fusion** entry in the left sidebar, choose the Lead and the Sidekick, and save.
+3. Select **Fusion · auto** in the model menu.
+4. On Windows, install PowerShell 7 and make sure `pwsh` is on the PATH used to launch DSH. Windows support was verified with v0.2.1 on Windows Server 2022 (later versions change only platform-independent code or packaging and were re-tested on macOS); Windows 10/11 remain unverified. On Linux, run the read-only check in [README.en.md](README.en.md#support) before real use.
+
+## Uninstall
+
+```sh
+dsh plugin --profile web remove @sqdr2/dsh-fusion
+```
+
+In the desktop app, uninstall from the **Plugins** page in the left sidebar. Fusion's own records stay in
+`$DSH_HOME/plugins/dsh-fusion/state.sqlite`; delete that file to remove them.

package/INSTALL.zh.md

@@ -0,0 +1,86 @@
+# 安装 Fusion
+
+[English](INSTALL.md) · 产品介绍：[README.md](README.md)（中文）、[README.en.md](README.en.md)
+
+需要 **DeepSeek Harness 0.2.0-rc.2 或 0.2.1-rc.2**，其他版本不支持。
+
+> 本包是 [`aa2246740/dsh-model-fusion`](https://github.com/aa2246740/dsh-model-fusion) 的 fork，包名 `@sqdr2/dsh-fusion`。
+> 因为换了包名，旧的 `dsh-model-fusion` 不会被自动升级；需要按下面的步骤装一次新包，装好后数据会自动迁移。
+>
+> 包名和插件 id 是两件事：包名是 `@sqdr2/dsh-fusion`，插件 id（配置里 `- id:`，也是数据目录名）仍是
+> `dsh-fusion`。所以升级只换安装来源，不动已有数据。
+
+## 从 npm 安装（推荐）
+
+```sh
+dsh plugin --profile web add @sqdr2/dsh-fusion
+```
+
+## 从 GitHub 安装
+
+仓库里带着构建好的 `lib/`，不需要自己编译。
+
+```sh
+dsh plugin --profile web add github:SQDR2/dsh-fusion
+```
+
+`dsh` 不在 PATH 里时，指定一个受支持的 CLI：
+
+```sh
+npx @deepseek-ai/dsh@0.2.0-rc.2 plugin --profile web add @sqdr2/dsh-fusion
+# 或
+npx @deepseek-ai/dsh@0.2.1-rc.2 plugin --profile web add @sqdr2/dsh-fusion
+```
+
+这只会写入 `web` 配置。正在运行的 Web 服务需要重新打开一次，再刷新页面。
+
+## 从本地目录安装（开发用）
+
+```sh
+git clone https://github.com/SQDR2/dsh-fusion.git ~/github/dsh-fusion
+cd ~/github/dsh-fusion && corepack pnpm@9.15.9 install --frozen-lockfile && cd -
+dsh plugin --profile web add ~/github/dsh-fusion
+```
+
+## DSH Studio 桌面版
+
+点左侧栏的 **插件** → **添加插件**，在"包名或地址"里填：
+
+```text
+@sqdr2/dsh-fusion
+```
+
+也可以填 `github:SQDR2/dsh-fusion`。装好后退出并重新打开 DSH Studio（插件在下次启动时生效）。
+
+## 从 dsh-model-fusion 升级
+
+1. 先卸载旧包，避免两个包同时注册 Fusion 入口：
+
+   ```sh
+   dsh plugin --profile web remove dsh-model-fusion
+   ```
+
+2. 按上面的方式安装 `@sqdr2/dsh-fusion`。**不要**先手动删除旧数据目录：
+   `$DSH_HOME/plugins/dsh-model-fusion/` 里的任务、用量和设置会在首次启动时整体迁移到
+   `$DSH_HOME/plugins/dsh-fusion/`。
+3. 重启 DSH（桌面版退出后重开，Web 版重开服务并刷新页面）。
+4. 已有的会话不用改：模型菜单里的 Fusion 选项会自动指向新的线路。
+
+## 装好之后
+
+1. 在 DSH 里至少登录两个模型：一个强的当 Lead，一个便宜得多的当 Sidekick。DSH 自带的模型可以用，
+   [dsh-oauth-login](https://github.com/aa2246740/dsh-oauth-login) 的订阅登录线路也可以用。
+   想把 agy（Google Antigravity）当 Sidekick，另需 [dsh-agy-worker](https://github.com/SQDR2/dsh-agy-worker)，
+   配置要求见 [README.md](README.md#用-agy-当-sidekickdsh-agy-worker)。
+2. 打开左侧边栏的 **Fusion** 入口，选择 Lead 和 Sidekick，保存。
+3. 在模型菜单里选择 **Fusion · 自动**。
+4. Windows 用户需安装 PowerShell 7，并确保启动 DSH 的进程 PATH 中有 `pwsh`。Windows 支持在 v0.2.1 上于 Windows Server 2022 验证过（之后的版本只改了与平台无关的代码或打包方式，在 macOS 上复测）；Windows 10/11 尚未验证。Linux 用户正式使用前，先按 [README.md](README.md#支持范围) 里的步骤检查只读限制是否生效。
+
+## 卸载
+
+```sh
+dsh plugin --profile web remove @sqdr2/dsh-fusion
+```
+
+桌面版在左侧栏的 **插件** 页面里卸载。Fusion 自己的记录在 `$DSH_HOME/plugins/dsh-fusion/state.sqlite`，
+想一并清除就删掉这个文件。

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.en.md

@@ -0,0 +1,193 @@
+# Fusion · a DSH plugin
+
+[中文](README.md) · [Install](INSTALL.md) · [安装](INSTALL.zh.md)
+
+> **This repository is a fork of [`aa2246740/dsh-model-fusion`](https://github.com/aa2246740/dsh-model-fusion), published as `@sqdr2/dsh-fusion`.**
+> Every upstream capability, algorithm and measurement is kept. This fork does three things: it moves the entry from
+> Settings to the left sidebar, it makes the agy route
+> ([`dsh-agy-worker`](https://github.com/SQDR2/dsh-agy-worker)) work as a Sidekick, and it removes a few ways a frozen
+> scope or a stale task record could dead-end a run. See [What this fork changes](#what-this-fork-changes).
+
+In DeepSeek Harness (DSH), Fusion is one entry in the model menu: **Fusion · auto**. Behind it are two models you choose:
+
+- **Lead**: a strong frontier model. It reads the request and the code, briefs the work and reviews the result.
+- **Sidekick**: a much cheaper model. It edits code, runs commands and runs tests.
+
+One goal: **frontier-model results at a discount.**
+
+Inspired by Fusion in Cognition's Devin. This is an independent implementation, not affiliated with Cognition.
+
+## Measured
+
+Nine real open-source issues (SWE-rebench, Python), two runs each, graded by hidden tests. Lead GPT-6 Astra (high), Sidekick GLM-5.3-Flash (high):
+
+| | Solved | Total cost (API list prices) |
+|---|---|---|
+| GPT-6 Astra alone | 9/18 | $39.17 |
+| **Fusion: GPT-6 Astra + GLM-5.3-Flash** | **11/18** | **$18.07 (54% less)** |
+| Fusion: GPT-6 Astra + Grok 4.6 | 13/18 | $41.27 (no saving) |
+
+- Costs are estimates at each provider's public API prices, not bills.
+- Limits: small sample (9 tasks × 2), Python only, and public issues may be in training data.
+- Method, raw data and per-round conclusions: [docs/EVIDENCE.md](docs/EVIDENCE.md).
+
+**Against Devin's own Fusion:** both used the same pair, GPT-6 Astra (high) as Lead and SWE-2 as Sidekick, on the same
+tasks, workspaces and hidden tests.
+
+After contaminated attempts were excluded, four tasks were clean in every condition:
+
+| | Solved | Cost |
+|---|---|---|
+| **This plugin: Astra + SWE-2** | **4/4** | **$2.73** |
+| Devin Fusion: Astra + SWE-2 | 3/4 | $4.81 |
+| Devin, Astra alone | 3/4 | $8.13 |
+
+- Four tasks with one run each cannot rank the two systems. This is not a parity claim.
+- SWE-2 is priced at $0 on both sides, so the costs are the Lead's.
+- The plugin took about 3.4× Devin's wall time.
+- For the excluded attempts and why they were excluded, see
+  [docs/EVIDENCE.md](docs/EVIDENCE.md#against-devins-own-fusion-round-devin-r1-2026-09-29).
+
+## Use
+
+1. Install the plugin ([INSTALL.md](INSTALL.md)).
+2. Open the **Fusion** entry in the left sidebar (default below Memory System) and choose a Lead and a Sidekick. Any model you are signed in to in DSH works.
+3. Select **Fusion · auto** in the model menu and work as usual.
+
+**Pairing:** Fusion saves money because the Sidekick costs far less than the Lead. Pick a strong frontier Lead and a Sidekick that is much cheaper (ideally 5× or more). The closer their prices, the smaller the saving.
+
+## How it works
+
+- **Conversation:** the Lead answers directly, like any model.
+- **Changes:** the Lead hands the work to the Sidekick. The brief carries the user's own words and the acceptance commands.
+- **Acceptance:**
+  - When the Sidekick reports, DSH runs the acceptance commands in the real workspace.
+  - The Lead reviews the change and must give a verdict with evidence for each of the user's hard requirements. A missing verdict blocks acceptance.
+  - Tests that were already failing (for example, missing optional dependencies) can be marked "no new failures".
+  - If the Sidekick rewrote an existing test, it is flagged, and the Lead must confirm it before accepting.
+- **Rework:** a rejected change goes back to the same Sidekick with the concrete problem.
+  - When the allowed files turn out too narrow (for example another test file still encodes the old behaviour), the Lead can add them during rework. Paths are only added, never removed, and each change is recorded.
+- **The Lead does not write code.** The program enforces this, not the prompt:
+  - the Lead has no file-writing tools;
+  - its shell commands run in DSH's read-only sandbox.
+- **The only exception is a takeover the Host unlocks when the Sidekick demonstrably cannot finish.** For example: checks still failing after 2 rework rounds, or the Sidekick hit its step limit or kept stalling. During a takeover:
+  - the Lead may only change the files the task allows;
+  - its work must pass the same acceptance;
+  - it returns to read-only afterwards.
+- **Quota or provider errors:** handled per role. Switch a model or schedule a continuation; progress is kept.
+
+## Using agy as the Sidekick (dsh-agy-worker)
+
+[`dsh-agy-worker`](https://github.com/SQDR2/dsh-agy-worker), a fork of `dsh-agy-link`, brings Google Antigravity's
+models into DSH, so one can be the Sidekick. This route is not like a plain provider: **three conditions must hold at
+the same time**, and each one fails silently on its own.
+
+| Condition | Why | Without it |
+|---|---|---|
+| `mcpBridge: true` | agy must be able to **execute** DSH tools | tools are listed but never run |
+| `permissionMode: 'skip'` | headless mode cannot prompt for the MCP permission | agy aborts: `a tool required the "mcp" permission that headless mode cannot prompt for` |
+| the allowlist admits `fusion_*` | the Sidekick must **report back** | it can diagnose but never submit |
+
+You do **not** write the `agy_tool` transport into the ceiling yourself. When this Host has the `antigravity` route
+registered, the plugin unions that transport into both the Lead's and the Sidekick's tool surface
+(`src/host/route-transport.ts`). That is one of the bugs this fork fixes: before it, agy's adapter could only report a
+step as `agy_tool`, the ceiling never carried that name, the whole turn degraded to prose, and the Host reported
+`WORKER_TOOLS_UNREACHABLE`.
+
+Recommended configuration:
+
+```yaml
+- id: dsh-agy-worker
+  config:
+    mcpBridge: true
+    permissionMode: skip
+    mcpConfigScope: global
+    mcpToolAllowlist: "fusion_submit_result,fusion_read_state,fusion_read_evidence,bash,read,write,edit,glob,grep,job_output,job_kill"
+```
+
+> On Windows use `pwsh` instead of `bash`, and follow any change you made to `workerTools`. For the full configuration
+> surface, verification steps and troubleshooting, see
+> [dsh-agy-worker's MCP bridge guide](https://github.com/SQDR2/dsh-agy-worker/blob/main/docs/MCP-BRIDGE-SETUP.md).
+
+## What this fork changes
+
+Against upstream `dsh-model-fusion`, in commit order:
+
+| Change | What it fixes |
+|---|---|
+| **User constraints survive a rollover** | after an automatic compaction, the hard requirements in the user's own words stay in the task's scope, so a compaction never drops the basis for acceptance |
+| **A dead-end task has an exit** | when a Sidekick route cannot reach the tools at all, the verdict is recorded on the runtime record: `fusion_wait` re-reports the same reason and `fusion_delegate` may replace the dead order, so the task no longer sits in `WORKER_RUNNING` forever |
+| **The entry moved to the left sidebar** | Fusion is its own panel (default below Memory System) instead of a section buried in Settings, and the main slot scrolls instead of clipping a form |
+| **The agy route can be a Sidekick** | the `agy_tool` transport is unioned into the tool ceiling (see above) |
+| **A bridged route can report back** | agy runs the call inside its own loop under a bridge-local id (`agy-mcp-N`) that appears in no assistant message here, so every non-read Worker tool was refused as "requires a complete native model request", including `fusion_submit_result`. A bridged call now belongs to the message that emitted the transport; the native path is unchanged and still preferred |
+| **A frozen scope no longer deadlocks** | a glob such as `allowedPaths: ['lib/types/**']` matched nothing, so "changes outside the frozen scope" and "files already differ under the added path" locked each other. Globs match now, widening is compared against the delegation base, and the scope can be cleared |
+| **Task records can be deleted** | deletion read persisted state only: a task whose owning process had been replaced stayed `running` forever, while a live Agent could be cleared out from under itself. Deletion asks the coordinator (`liveWork`) and the 409 names the resource that held the task |
+| **Collapsible panels** | usage, the task list, cache keepalive and history are separate boxes, collapsed by default, so the model pair no longer scrolls off the page |
+
+## Cache keepalive
+
+While the Lead waits for the Sidekick, often for several minutes, the model's prompt cache can expire. The next request then re-reads the whole conversation at full price. Keepalive resends the Lead's previous request at intervals with only “Reply OK” appended. The prefix is identical, so the provider serves it from cache and the cache lifetime is renewed; the model answers OK, and the reply is discarded: it never enters the conversation and no tool call runs.
+
+- **Defaults:** taken from each provider's documentation, covering the vendors of the Artificial Analysis top 20.
+  - Matched by model name: gpt-*, claude-*, gemini-*, glm-*, grok-*, kimi-*, deepseek-*, …
+  - Plus the billing of the [dsh-oauth-login](https://github.com/aa2246740/dsh-oauth-login) routes: plans billed per request default to off, since every ping counts as a request.
+- **Auto:** starts only after the model has actually reported cache hits, so a model without caching never pays for pings.
+- **Every model is adjustable in the Fusion panel:** on/off, interval, reset to default. The panel also shows the observed effect for each model:
+  - whether the cache survived each wait;
+  - how many pings were sent and how many tokens they read;
+  - how many tokens were kept from being resent at full price.
+- **Measured (ChatGPT subscription route, gpt-6-astra, ~20k-token context):** each ping gets a 5-token reply, with no reasoning and no tool call. The cache was still there after 10 idle minutes and gone after 15, and every ping restarts that clock, so this route defaults to a ping every 8 minutes.
+- **Automatic adjustment:** the interval is shortened only when 3 of the last 5 pings at that interval missed (an occasional random eviction does not count). It is never lengthened automatically; when a longer interval looks safe, the page suggests it and you decide.
+
+## Support
+
+- **DSH version:** **0.2.0-rc.2** and **0.2.1-rc.2**, desktop app or Web. Other versions are not guaranteed; new releases will be adapted separately.
+- **Models:** DSH's built-in providers, plus the subscription routes of [dsh-oauth-login](https://github.com/aa2246740/dsh-oauth-login) and dsh-antigravity-oauth, and the Antigravity route of [dsh-agy-worker](https://github.com/SQDR2/dsh-agy-worker). Other third-party model plugins are untested.
+- **Operating systems:**
+  - **macOS:** verified (Seatbelt sandbox).
+  - **Windows:** `v0.2.1` supports native `pwsh` and has been verified on Windows Server 2022 with PowerShell 7.6.6. Make sure `pwsh` is on the PATH used to launch DSH. Windows 10/11 remain unverified. Windows ACL enforcement is partial: it can restrict ordinary file writes, but does not restrict reads or networking.
+  - **Linux:** not verified. Check it yourself first:
+  1. In a test folder, select Fusion and say: "This is a read-only sandbox test; a refusal is expected. Call the bash tool yourself with `echo test > fusion-probe.txt` (don't delegate, don't rewrite it) and paste the tool's raw output."
+  2. Expected: the tool output says the sandbox denied it (for example `Operation not permitted` / `read-only`), and no `fusion-probe.txt` appears.
+     - If the Lead only declines in words without calling the tool, the check doesn't count; ask it again to actually call the tool.
+  3. If the file is created, the Lead's read-only limit does not work on your system. Don't use Fusion there, and please report it.
+  - Where DSH has no sandbox at all, every Lead shell command is refused (it fails safe). The Lead still reads code with its file and search tools.
+
+### Windows validation in v0.2.1
+
+On Windows Server 2022 with Node 22.23.3, PowerShell 7.6.6 and DSH 0.1.7-rc.2, all **253 unit tests and 236 Host tests** passed, as did type checking. The repair candidate passed plugin installation, a cold start, the Fusion settings page and both settings/cache APIs. The v0.2.1 server and client bundles are byte-for-byte identical to that candidate. Later releases (v0.2.2: the Lead can widen the allowed files during rework; v0.2.3–v0.2.5: DSH 0.2.0-rc.2 support; v0.2.6: cheaper cache keepalive) are platform-independent and were re-tested on macOS, not on Windows.
+
+The real PowerShell ACL test denied the Lead's `Set-Content probe.txt test` command and left no file; the Sidekick could write the same file within its granted workspace. This is partial ACL enforcement, with the limits above. These checks used no model credentials or real model requests. macOS regression: 253 unit tests and 235 Host tests passed; the Windows-only ACL test was skipped.
+
+## Data
+
+- **Fusion's own records:** briefs, check results, usage, cache statistics and settings live in `$DSH_HOME/plugins/dsh-fusion/state.sqlite`. `DSH_HOME` defaults to `~/.dsh`.
+- **Upgrading from the old name:** the previous release was `dsh-model-fusion`, and its whole directory (`$DSH_HOME/plugins/dsh-model-fusion/`) is **migrated** to the new name on first start, so existing tasks, usage and settings survive. Across filesystems it falls back to copying the database plus its `-wal`/`-shm`/`-journal`, and removes only the files it copied.
+- **The conversations themselves:** stored by DSH. Fusion uploads nothing else.
+- **To clear Fusion's records:** quit DSH and delete that file. Settings go with it; choose the pair again next time.
+
+## Known limits
+
+- **Slower than the frontier model alone:** GPT-6 + Flash took about 5× the time of GPT-6 alone, mostly spent in the Sidekick. A faster Sidekick helps.
+- **Lead takeover:** never triggered in 72 measured runs; only automated tests cover it.
+- **PATH in the macOS desktop app:** DSH Studio opened from the Dock gets only the system PATH, so `node`, `npm`, `cargo` and other tools installed by Homebrew (`/opt/homebrew/bin`), nvm and similar are not found by the shell. This is DSH's environment and affects every model. Before handing off work, Fusion checks the programs the acceptance commands use; when one is missing it tells the Lead where it is installed (for example `/opt/homebrew/bin/node`), and the Lead retries with the full path.
+- **Windows 10/11 and Linux not verified:** see Operating systems above.
+
+## Development
+
+```sh
+corepack pnpm@9.15.9 install --frozen-lockfile
+node scripts/link-host.mjs /path/to/deepseek-harness-0.2.0-rc.2   # or 0.2.1-rc.2; link DSH sources for development
+DSHX_HARNESS=/path/to/deepseek-harness-0.2.0-rc.2 pnpm build
+pnpm test && DSHX_HARNESS=/path/to/deepseek-harness-0.2.0-rc.2 pnpm test:host
+```
+
+For Windows development, put PowerShell 7 (`pwsh`), Node and Python on the test process PATH. Native tests use `DSHX_HARNESS` to read the built, pinned Host checkout; no Host source changes are required.
+
+The plugin uses only DSH's public plugin APIs and never modifies DSH itself. How to adapt it to a new DSH release: [docs/COMPATIBILITY.md](docs/COMPATIBILITY.md).
+
+How to cut a release (bump the version, rebuild `lib/`, push a tag, let CI publish over OIDC): [RELEASING.md](RELEASING.md).
+
+## License
+
+Apache-2.0. Forked from [`aa2246740/dsh-model-fusion`](https://github.com/aa2246740/dsh-model-fusion), also under Apache-2.0.