dsh-loop-engine-allinone 0.7.0 → 0.7.2

package/CHANGELOG.md

@@ -8,6 +8,45 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 Nothing yet.
 
+## [0.7.2]
+
+### Changed
+
+- **Installation leads with `--profile web` again.** 0.7.1 made `<your-profile>` the
+  primary spelling, on the reasoning that `web` is one of several shipped templates.
+  That is true but the wrong shape for an install section: `dsh web` is the harness
+  CLI's own documented example (`dsh web` = `dsh --profile web`), and every published
+  plugin says `dsh plugin --profile web add ...` — dsh-market included. Forcing a
+  placeholder substitution before the first command is friction with no payoff for the
+  majority.
+
+  The non-`web` case is now a caveat section instead: `desktop`, `headless`, and
+  self-named profiles get both steps, plus the silent failure that follows from doing
+  only the first one. npm / GitHub / local-clone remain the three sources.
+
+## [0.7.1]
+
+### Fixed
+
+- **Installation no longer assumes a `web` profile.** `web` is one of several shipped
+  templates; the Desktop app boots `desktop`, a CI deployment boots `headless`, and
+  many people run a profile they named themselves. The instructions now say
+  `<your-profile>` and give the three real sources: npm, GitHub, and a local clone for
+  plugin development.
+- **A wrong `profile:` is now diagnosable.** The field defaults to `web`, so forgetting
+  it writes the managed block into another profile's patch file while the profile that
+  actually boots never reads it — the plugin mounts, the base `agent-loop` row is never
+  disabled, and no hosted engine is reachable, with **nothing logged**. The harness
+  gives a plugin no way to ask which profile is running, so `apply` now checks whether
+  the target directory holds a profile's `package.json` and warns with the field to set.
+  It is a warning, not a failure: a first boot may legitimately precede the profile's
+  own files.
+
+### Documented
+
+- The engine picker appears in whichever profile renders a web UI, not specifically in
+  `web`.
+
 ## [0.7.0]
 
 ### Added

package/README.md

@@ -7,7 +7,7 @@
 
 **dsh-loop-engine-allinone** is an all-in-one agent loop engine switcher for **[DeepSeek Harness](https://github.com/deepseek-ai)** (`dsh`). It enables per-session engine switching across **10 hosted engines** (Claude Code, Codex, Pi, Kimi Code, Antigravity, ZCode, Qoder CN, Hermes Agent, Grok Build, MiniMax Code) alongside the built-in `in-process` loop.
 
-> `dsh` is the harness CLI. `dsh web` boots its **web profile**, which is the UI this plugin's engine picker and settings page live in.
+> `dsh` is the harness CLI. `dsh --profile <name>` boots one of its **profiles**, and the engine picker plus this plugin's settings page appear in whichever profile renders a web UI (the shipped `web` template is one; the Desktop app uses `desktop`).
 
 Sessions are fully independent: run Codex in one chat while another runs Kimi Code or Antigravity simultaneously. Handover between two hosted engines happens seamlessly in place; switching to or from the native `in-process` engine performs an in-browser reload without restarting the backend process. All without modifying the DeepSeek Harness core codebase.
 
@@ -33,40 +33,64 @@ Sessions are fully independent: run Codex in one chat while another runs Kimi Co
 ## Installation
 
 ```sh
-# From npm (recommended)
 dsh plugin --profile web add dsh-loop-engine-allinone
 ```
 
-Then boot the web profile once and open **Settings → Loop engine**:
+Restart `dsh web`, then open **Settings → Loop engine**.
+
+### From GitHub instead of npm
 
 ```sh
-dsh web
+dsh plugin --profile web add yaliklinty/dsh-loop-engine-allinone
 ```
 
-Installing into a profile other than `web` (the Desktop app's `desktop`, a
-`headless` deployment, a renamed profile) means naming that profile instead:
-`dsh plugin --profile desktop add dsh-loop-engine-allinone`, **and** setting
-`profile: desktop` in the composition entry — see the notes below, because
-forgetting the second half is the one mistake that leaves the plugin mounted but
-unable to run any engine.
-
-### Installation Notes
-
-- **Profile Configuration**: The installer automatically injects a managed configuration block into your profile's `cordis.patch.yml`. All other custom configuration in that file is preserved.
-- **Non-web Profiles**: When installing into non-web profiles (such as `desktop` or headless), explicitly specify `profile: <name>` in the composition entry:
-  ```yaml
-  - id: loop-engine
-    config:
-      profile: desktop
-  ```
-  *(Without this, configuration defaults to `web` and the plugin will not attach to custom profiles.)*
-- **Uninstallation**: Run `dsh plugin --profile web remove dsh-loop-engine-allinone`, then remove the managed `loop-engine` block from `cordis.patch.yml`.
-- **pnpm 10+**: If dependency build scripts are blocked (`ERR_PNPM_IGNORED_BUILDS` mentioning `esbuild`, `@google/genai`, etc.), run `pnpm approve-builds`.
-- **Harness from Source**: If launching the harness directly from a source checkout, bridge peer dependencies using `file:` shims as described in [docs/source-checkout.md](docs/source-checkout.md).
+### From a local clone
 
----
+Only when you are working on the plugin itself:
 
----
+```sh
+git clone https://github.com/yaliklinty/dsh-loop-engine-allinone.git
+dsh plugin --profile web add ./dsh-loop-engine-allinone
+```
+
+### Not on the `web` profile?
+
+`web` is the profile the harness's own CLI documents (`dsh web` is short for
+`dsh --profile web`), so it is the right default. But the Desktop app boots
+`desktop`, a CI deployment may boot `headless`, and you may have made your own. In
+that case:
+
+1. install with that profile's name — `dsh plugin --profile desktop add
+   dsh-loop-engine-allinone`;
+2. **and** set the same name in the composition entry:
+
+   ```yaml
+   - id: loop-engine
+     config:
+       profile: desktop
+   ```
+
+Step 2 is the one that bites. The field defaults to `web`, so omitting it makes the
+plugin write its managed block into `profiles/web/cordis.patch.yml` while the profile
+you actually boot never reads it: the plugin mounts, but the base `agent-loop` row is
+never disabled, the router cannot take the agent-factory slot, and **no hosted engine
+is reachable** — with nothing logged. This release also warns when it detects that
+shape, naming the field to set.
+
+### Installation notes
+
+- The installer rewrites one managed block in the profile's `cordis.patch.yml`; every
+  other byte you wrote there is preserved, so upgrading needs no hand edit.
+- **Uninstall**: `dsh plugin --profile web remove dsh-loop-engine-allinone`, **then
+  delete the managed `loop-engine` block** from that profile's `cordis.patch.yml`. The
+  block outlives the plugin, and while it is present the profile has no agent factory,
+  so no session can be created.
+- **pnpm 10+** may block dependency build scripts (`ERR_PNPM_IGNORED_BUILDS` naming
+  `esbuild`, `@google/genai`, `protobufjs`). Run `pnpm approve-builds`, or add an
+  `allowBuilds` entry, and retry — only the installing project can grant this.
+- **Harness from source**: bridge the profile's harness peers with `file:` shims, or
+  session resume fails with `agent-presets: refusing to compose an unscoped context`.
+  Steps in [docs/source-checkout.md](docs/source-checkout.md).
 
 ## Supported Engines
 

package/README.zh.md

@@ -7,6 +7,8 @@
 
 **dsh-loop-engine-allinone** 是专为 [DeepSeek Harness](https://github.com/deepseek-ai)（`dsh`）打造的 Agent 循环引擎全功能切换插件。支持**按会话独立切换** 10 家主流外部引擎与 Harness 原生 `in-process` 循环。
 
+> `dsh` 是 harness 的命令行程序；`dsh --profile <名字>` 启动它的某个 **profile**。引擎选择器与本插件的设置页出现在**任何渲染 web UI 的 profile** 里（随附的 `web` 模板是其中之一，桌面版用的是 `desktop`）。
+
 各会话完全隔离互不干扰：一个窗口运行 Codex，另一个窗口可同时运行 Kimi Code 或 Antigravity。托管引擎之间支持**无缝原地热换**；切换至原生 `in-process` 时会自动刷新页面重新挂载（无需重启 `dsh web` 后端进程）。**全程无需修改 DeepSeek Harness 主仓库源码**。
 
 > **Fork 说明**：本项目基于 [`kuun993/dsh-loop-engine`](https://github.com/kuun993/dsh-loop-engine) 进行深度重构与扩展。  
@@ -30,42 +32,59 @@
 
 ## 安装说明
 
-通过 `dsh plugin` 命令行直接安装：
-
 ```sh
-# 从 npm 安装（推荐）
 dsh plugin --profile web add dsh-loop-engine-allinone
 ```
 
-然后启动一次 web profile，打开 **Settings → Loop engine**：
+重启 `dsh web`，打开 **Settings → Loop engine**。
+
+### 想从 GitHub 装而不是 npm
 
 ```sh
-dsh web
+dsh plugin --profile web add yaliklinty/dsh-loop-engine-allinone
 ```
 
-> `dsh` 是 harness 的命令行程序；`dsh web` 启动它的 **web profile**——本插件的引擎选择器与设置页就在那个界面里。
+### 从本地克隆安装
 
-装到 `web` 以外的 profile（桌面版的 `desktop`、`headless` 部署、改过名的 profile）时，
-要把 `--profile web` 换成对应名字，**并且**在组合条目里写 `profile: <名字>`。
-只做前一半是本插件最容易犯的错：插件挂上了，却一个引擎都跑不起来。详见下方安装须知。
+只在开发插件本身时才需要：
 
-### 安装注意事项
+```sh
+git clone https://github.com/yaliklinty/dsh-loop-engine-allinone.git
+dsh plugin --profile web add ./dsh-loop-engine-allinone
+```
 
-- **Profile 自动配置**：安装时会自动在对应 Profile 的 `cordis.patch.yml` 中写入一段受管配置块，原有配置内容均逐字节安全保留。
-- **非 Web Profile 部署**：若安装至桌面版 `desktop` 或 headless 等自定义 profile，需在配置中显式指定 `profile: <name>`：
-  ```yaml
-  - id: loop-engine
-    config:
-      profile: desktop
-  ```
-  *(若未指定，插件默认挂载到 `web` profile，导致自定义 profile 无法生效。)*
-- **卸载插件**：执行 `dsh plugin --profile web remove dsh-loop-engine-allinone`，并手动清理 `cordis.patch.yml` 中残留的 `loop-engine` 受管块。
-- **pnpm 10+ 构建拦截**：若遇到 `ERR_PNPM_IGNORED_BUILDS`（提示 `esbuild`、`@google/genai` 等构建被忽略），执行 `pnpm approve-builds` 允许即可。
-- **源码模式运行 Harness**：若通过源码启动 Harness，需按照 [docs/source-checkout.md](docs/source-checkout.md) 说明配置 `file:` shim 桥接依赖包。
+### 不是 `web` profile？
 
----
+`web` 是 harness 自己的 CLI 文档里用的那个 profile（`dsh web` 就是 `dsh --profile web`
+的简写），所以它是正确的默认值。但桌面版启动的是 `desktop`，CI 部署可能用 `headless`，
+你也可能自己建过一个。这种情况下：
 
----
+1. 用那个 profile 的名字安装 —— `dsh plugin --profile desktop add dsh-loop-engine-allinone`；
+2. **并且**在组合条目里写上同一个名字：
+
+   ```yaml
+   - id: loop-engine
+     config:
+       profile: desktop
+   ```
+
+**第 2 步才是会咬人的地方。** 该字段默认是 `web`，漏写会让插件把受管块写进
+`profiles/web/cordis.patch.yml`，而你实际启动的 profile 永远读不到它：插件挂上了，
+但基础 `agent-loop` 行没被禁，路由器拿不到 agent factory 槽位，**任何托管引擎都不可达**
+——而且不报错。本版本会在检测到这种情形时告警，并指出该设哪个字段。
+
+### 安装注意事项
+
+- 安装会重写该 profile `cordis.patch.yml` 里的一段受管块；你写的其它内容逐字节保留，升级不需要手工改。
+- **卸载**：`dsh plugin --profile web remove dsh-loop-engine-allinone`，**然后手动删掉**
+  该 profile `cordis.patch.yml` 里的 `loop-engine` 受管块。块会比插件活得久，而它还在时
+  profile 里没有任何 agent factory，会话一条也建不出来。
+- **pnpm 10+** 可能拦下依赖的 build script（`ERR_PNPM_IGNORED_BUILDS`，列出 `esbuild`、
+  `@google/genai`、`protobufjs`）。执行 `pnpm approve-builds`，或加一条 `allowBuilds`，然后重试
+  ——只有安装方能授予这个权限。
+- **用源码启动 harness** 时，要用 `file:` shim 把 profile 的 harness peer 包桥接到 checkout 源码，
+  否则恢复会话会报 `agent-presets: refusing to compose an unscoped context`。
+  步骤见 [docs/source-checkout.md](docs/source-checkout.md)。
 
 ## 支持引擎一览
 

package/lib/index.js

@@ -89,7 +89,7 @@ var __callDispose = (stack, error, hasError) => {
 };
 
 // src/index.ts
-import { readFileSync as readFileSync5 } from "node:fs";
+import { existsSync as existsSync8, readFileSync as readFileSync5 } from "node:fs";
 import { mkdir as mkdir2, readFile as readFile6, rename as rename2, writeFile as writeFile2 } from "node:fs/promises";
 import { randomUUID as randomUUID3 } from "node:crypto";
 import { dirname as dirname7, join as join21 } from "node:path";
@@ -11476,9 +11476,18 @@ function readPatchFileSync(path) {
     throw error;
   }
 }
+function warnIfProfileLooksWrong(ctx, config, patchPath) {
+  const profileDir = dirname7(patchPath);
+  if (existsSync8(join21(profileDir, "package.json"))) return;
+  const named = config.profile ?? "web";
+  ctx.logger.warn(
+    `loop-engine: profile "${named}" has no package.json beside "${patchPath}". If you boot a different profile, set \`profile: <that-name>\` in this plugin's composition entry - otherwise its managed block is written here, the profile you actually boot never reads it, and no hosted engine will be reachable.`
+  );
+}
 function apply(ctx, config) {
   const summarizer = resolveSummarizerTarget(config);
   const patchPath = resolvePatchPath(config);
+  warnIfProfileLooksWrong(ctx, config, patchPath);
   const patchText = readPatchFileSync(patchPath);
   const legacyEngine = legacyBlockEngineOf(patchText);
   const needsWrite = hasLegacyManagedBlock(patchText) || !hasManagedBlock(patchText);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-loop-engine-allinone",
   "description": "Web-switchable agent loop engine selection for the DeepSeek Harness - out-of-tree plugin with a data-driven engine registry and a pluggable driver layer. Ten engines: Claude Code / Codex / Pi / Kimi Code / Antigravity / ZCode / Qoder CN / Hermes / Grok Build / MiniMax Code. All-in-one fork of kuun993/dsh-loop-engine.",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/"
   },