dsh-model-switch 0.4.25 → 0.4.27

package/CHANGELOG.md

@@ -1,3 +1,28 @@
+## v0.4.27
+
+A fix for a regression v0.4.26 introduced on DSH `0.2.1-rc.2`, plus the architecture change that removes its cause: the plugin no longer ships static copies of DSH's agent presets.
+
+- **What broke (v0.4.26, DSH 0.2.1 only).** Every turn failed before the first token with `unknown prompt variable "{{cwd}}" in section "deployment:persona-suffix"`, and the composer needed the plugin disabled to continue. Cause: `cordis.patch.yml` replaced `preset-standard` / `preset-ptc` / `preset-cordis` wholesale with copies captured from the **0.2.0** presets. Those copies carried `suffix: Your working directory is {{cwd}}.` in the `persona` row; DSH 0.2.1 validates prompt variables and registers only `provider` and `model`, and its own presets dropped the `cwd` variable — so composing the persona suffix threw for every new turn. The copies had also drifted: they lacked the `time-context` and `tool-schedule` rows that 0.2.1 moved into presets, so even without the fatal error those rows would have been missing.
+- **Fix: bridge the nested compaction engine at Host startup instead of copying presets (`src/preset-sync.ts`, wired from `ModelSwitchRuntime`).** On startup the Host finds each `@deepseek-ai/dsh-agent-preset` declaring row in the loader, walks its nested entry lists, disables the nested `@deepseek-ai/dsh-compaction-basic` row, and inserts `model-switch-compaction` directly after it. Every other row, prompt text, and `!!js` expression is left exactly as the installed DSH (or a deployment that edited the preset in the Web editor) wrote it. An entry that has not started yet gets its raw config swapped in place; a started entry is reloaded through the public loader `entry.update`. A failure is logged once and the official preset stays mounted, so the turn still runs and compaction simply keeps the official default route.
+- **Why the copies are gone for good.** The static copies were a pinned snapshot that silently hid every later DSH preset change — this regression is exactly that failure mode. Reading each installed release's own preset definition removes the per-release re-sync step and restored the `time-context` / `tool-schedule` rows on 0.2.1.
+- **Verification.** `pnpm run check` green (52 test files / 450 tests + pack gate). `tests/preset-patch.spec.ts` was rewritten to pin the bridge instead of the copies: 0.2.0-shaped (persona `{{cwd}}` suffix) and 0.2.1-shaped preset configs, idempotency, a preset without a compaction group, matching by package + preset id, both bridge paths (raw-config swap and loader reload), reload-failure logging, and a check that the patch no longer replaces any preset row. Lab plane on `0.2.1-rc.2` (`DSH_HOME=~/.dsh-lab`, port 3082): the composed tree now carries the official presets (`persona` prefix only, no `{{cwd}}`, with `time-context` and `tool-schedule` restored) and a headless host with 0.4.27 ran a full turn end to end — the answer streamed normally, and the naming record shows the new chain: a failed group candidate (`apigoto/no-such-title-model`) fell through to the deployment pair, `session/title-llm-request` recorded `apigoto/mimo-v2.6-flash` with `reasoningEffort: off` on the 0.2.1 call shape, and the provider title replaced the fallback title.
+- **Residual.** The desktop app updated to `0.2.1-rc.2` is still running v0.4.26 with the plugin disabled; re-enable it after updating to 0.4.27 to confirm the live turn on that machine. 0.1.7 / 0.2.0 compositions are untouched by this change: with no preset row replacement, they keep their own shipped presets, and only the nested compaction swap is applied by the bridge at startup.
+
+## v0.4.26
+
+Two coordinated changes: automatic session naming now survives a failing title route (the auxiliary call is retried and then falls through the candidate routes instead of leaving the deterministic fallback title in place forever), and official DSH `0.2.1-rc.2` is declared compatible — that release replaced the shared title call with a provider-prepared one and replaced the Subagent start surface with its activation API, so both seams are now handled per installed line.
+
+- **Session naming: one failing route no longer owns the title (`src/session-title.ts`).** Evidence from the five sessions that showed a `session/title-llm-request` and no provider title: all five routed to `ark/ark-code-latest`, each fired 1–5 ms after the main request header on the same account, and each session's main loop carried that account's `RATE_LIMIT` (`RequestBurstTooFast` / `AccountQuotaExceeded`) or `TRANSPORT` failures — the auxiliary call has no retry and no fallback, so one rejected call left the deterministic fallback. The row now tries the resolved route first (session provider group's title pair → deployment-wide pair → the row's own pair → the session's logged route, deduplicated) and **only moves on after a failure**: a max-token failure gets one widened-budget retry on the same route (`min(4 × maxOutputTokens, 4096)`), other failures fall through to the next candidate, and when every candidate fails the row logs one warning naming the routes and rethrows, so the official fallback still applies. The configured route stays the first choice and nothing is persisted.
+- **DSH 0.2.1 naming line (`executeSessionTitleLlm`).** `0.2.1-rc.2` removed `generateSessionTitleWithLlm` / `registerSessionTitleLlmProvider` and split the shared policy: the new `executeSessionTitleLlm(ctx, config, request, id, prepared)` returns assembled blocks plus the terminal finish reason, each provider owns its system instruction, input framing, reasoning-effort selection, and output interpretation, and `targetWords` / `targetCjkCharacters` moved into the provider's own config. The row detects the installed line at runtime and mirrors the shipped 0.2.1 provider exactly: same system instruction (including the best-effort line and, for all-prompts, the current-title stability rules anchored on a provider-sourced `currentTitle`), same JSON framing, the route's least supported reasoning effort, and the same finish-reason / whole-line-emphasis / empty-output acceptance rules. `cordis.patch.yml` also disables the `optional-session-title-all-prompts` row that 0.2.1's experimental session-titles bundle inserts (unknown-row warning on profiles without it, like the optional auto-review row).
+- **DSH 0.2.1 compatibility review (0.2.0-rc.2 → 0.2.1-rc.2, public API only).**
+  - **Naming:** the service keeps `register` / `ensureFallback` / the `first-prompt` gate and only adds an optional `currentTitle` to the provider request; `onMainRequest` dropped one boundary-freshness condition. The provider request shape this row returns is unchanged.
+  - **Auto review:** the official gate now resolves the reviewing agent's directory through `ctx.workingDirectory.ensure(...)` and injects `workingDirectory`; `dsh-base` 0.2.1 mounts the `working-directory` row, so the official `apply` runs unchanged under this row's scoped `llm`.
+  - **Compaction and presets:** `dsh-compaction-basic` and `dsh-agent-preset` are byte-identical to 0.2.0, so the wholesale preset copies and the compaction engine need no re-sync.
+  - **Unchanged surfaces this plugin calls:** `llm.stream(GenerateOptions)` (with `prepareCall` added beside it), `web.registerSearchProvider`, `tools/pre-execute` (`exec.agent` kept), session `snapshotEvents` / `requestHeader` / `requestContext` / `append`, and the composer's `conversation.input.model` seat.
+  - **Subagents:** `@deepseek-ai/dsh-subagent` replaced `start()` / `startContinuable()` with `startActivation(spec)` plus a provider registry. The routed runtime therefore cannot override the new entry point; this row mounts the untouched official runtime (fail-closed) and logs one explicit notice. Recorded in `docs/seam-gap.md` for a later upstream proposal.
+- **Verification.** `pnpm run check` green (`tsc` + `tsdown`, 52 test files / 437 tests, pack gate). New coverage: both auxiliary-LLM lines end to end, route-candidate ordering and dedup, max-token widening, fall-through, all-candidate failure reporting, cancelled requests staying silent, provider-prepared prompt/framing/anchor/effort selection, and the replaced-Subagent notice. Both official lines were also exercised end to end against the **real published packages** (0.2.1 `executeSessionTitleLlm`, 0.1.7 `generateSessionTitleWithLlm`): registration through the real policy validator, route selection, the `session/title-llm-request` record, the official system prompt, the least reasoning effort (0.2.1), and title acceptance all agree. **Lab plane:** `DSH_HOME=~/.dsh-lab` with the npm-installed `0.2.1-rc.2` runtime and the packed `dsh-model-switch-0.4.26.tgz` — profile composition `exit 0` with the naming, compaction, auto-review, and subagent rows composed from this plugin, and the Web Host booted on port 3082 serving the auth-gated page. **Residual (honest):** the 3082 capability RPC was not exercised from a browser (no browser automation is available in this environment), and the live desktop is still `0.2.0-rc.2`, so the 0.2.1 claim rests on the package-surface review, the unit suite, the real-package line checks, and the lab boot; the naming differential on a live 0.2.1 desktop is re-checked after the app update.
+- **Post-release probe (2026-10-19 ~00:08 +0800, after the pinned Ark account's weekly quota reset).** The route was probed with the exact recorded system prompt and framed input. Before the reset it answered `HTTP 429 AccountQuotaExceeded`; with quota available the same route returns `finish: stop` and a complete title in 2.6–5.0 s with thinking enabled (57–134 reasoning tokens) versus 0.5–0.7 s and 6 tokens with thinking disabled. Tight budgets (`max_tokens` 8/16/24) still return a complete title, so truncation was not the observed failure mode — the route fall-through, not the widened retry, is the primary fix on this account. Evidence table and fix mapping in `docs/session-title-failure-mode.md`.
+
 ## v0.4.25
 
 Three coordinated changes: Provider groups now cover all four per-session capabilities (compaction, auto review, session naming, and subagents) with mid-session provider-switch following; capability switches stay disabled until the model catalog has loaded (and while any row save is in flight) so clicks are never silently dropped; and send-time switch compaction (`compactOnSwitch` / `src/switch-compact.ts`) has been removed completely.

package/PRODUCT.md

@@ -13,9 +13,9 @@
 - **Plan Review:** intercepts the official `plan-review` composer takeover with a header execution-model picker and right-aligned Discuss in chat / Reject / Set as goal and run / Confirm actions. Confirm commits the selected model before answering; a refused commit leaves the review pending and retryable. Reject carries optional human feedback as the answer's own `custom` text, which plan mode reports to the model. **Set as goal and run** arms this Plan as the session's goal through the released `remote.goals.create` — replacing an unfinished goal with `get` + `clear` first so the new Plan receives a fresh round cap — and only then answers, so `dsh-goal-round-driver` carries the Plan after plan mode exits. The goal is set before the answer, a refusal keeps the review pending and retryable, and a deployment that mounts no goal service disables the action with an explicit reason; the plugin stores no goal state, schedules no rounds, and owns no part of the goal domain. The card body carries only the official two-part summary (first line, first paragraph); the full plan opens in the right sidebar through ui-plan's registered preview opener, which this card drives because a composer-takeover entry cannot declare the official actions slot. Discuss in chat withdraws the takeover through the Host's own verb — `dismiss()` where the Host publishes it, `cancel()` on the older generation — and names the Host when neither seam exists, so a settled review is never a dead end. The same runtime reservation applies.
 - **Auto review:** the reviewer model for the official `@deepseek-ai/dsh-experimental-auto-review` per-call gate, off by default — both fields empty means reviews follow the session's own model. On pins a deployment-wide provider/model, and each review resolves its route per session: the session's provider group's reviewer pair → the flat card pair → the session's own model. Session correlation rides an outer `{ prepend: true }` `tools/pre-execute` listener on the review scope (`exec.agent.session`), so parallel sessions on different providers never interfere and mid-session provider switches take effect on the very next review.
 - **Compaction:** the summarization model behind `/compact` and DSH's automatic compaction, off by default — both fields empty means compaction follows the conversation target model. On pins a deployment-wide provider/model, and each summarization call resolves its route per session: the session's provider group's compaction pair → the flat card pair → the official row's `modelPolicies` / conversation-target default. When a per-session route applies, the child context's `llm` wrapper updates `options.provider`/`options.model` in place on `purpose === 'compaction'` calls so `summarizeWithLlm` returns and durably records the exact route that wrote the summary in `compaction/summary`.
-- **Session naming:** the model behind DSH's automatic session titles, off by default — both fields empty means naming follows the session's own model, which is the official behavior. On pins a deployment-wide provider/model that each session re-resolves per request: provider group → flat pair → the session's own model. The route is read through on every naming request, so a save applies to the very next request with no restart and never interrupts an in-flight request; the exact pair used is recorded in the session's own `session/title-llm-request` event by the official naming implementation, so the record and the request always agree. The plugin replaces the official `session-title-llm` row (one registered naming provider per context) and mirrors the cadence that row declared; naming cadence and title policy remain DSH's.
+- **Session naming:** the model behind DSH's automatic session titles, off by default — both fields empty means naming follows the session's own model, which is the official behavior. On pins a deployment-wide provider/model that each session re-resolves per request: provider group → flat pair → the session's own model. The route is read through on every naming request, so a save applies to the very next request with no restart and never interrupts an in-flight request; the exact pair used is recorded in the session's own `session/title-llm-request` event by the official naming implementation, so the record and the request always agree. The first candidate is used unless its call fails: a max-token failure gets one widened output-budget retry on the same route, any other failure falls through to the next candidate (provider group → flat pair → the row's own pair → the session's own model), and only when every candidate fails does naming keep DSH's deterministic fallback title, after one warning that names the routes tried. A fallback neither writes settings nor changes the stored route. The plugin replaces the official `session-title-llm` row (one registered naming provider per context), mirrors the cadence that row declared, and follows whichever official auxiliary title call the installed DSH line publishes; naming cadence and title policy remain DSH's.
 
-Model choices are capability-driven. Invalid, unavailable, or unsupported selections remain visible to configuration surfaces and fail loudly at use; routing never silently falls back.
+Model choices are capability-driven. Invalid, unavailable, or unsupported selections remain visible to configuration surfaces and fail loudly at use; routing never silently falls back. The one exception is the session-naming per-call route fallback above: it engages only after the pinned route's call failed, is reported once when every candidate fails, and never changes the stored route.
 
 ## Preset modes
 
@@ -27,7 +27,7 @@ The settings surface aggregates public Settings namespaces, reads and mutates wi
 
 ## Exclusions
 
-Send-time switch compaction (`compactOnSwitch`) was removed in 0.4.25: injecting plugin-authored compaction checkpoints and notices during model switches interacted with the official `compaction-basic` step-pressure loop when a session's working set stayed near the target window's pressure threshold. All compaction policy and triggers belong exclusively to DSH's official compaction engine (`/compact` and automatic pressure/overflow compaction). The Auto reviewer route override rides a name-matched replacement of the experimental auto-review row and changes only the review request's provider/model. The compaction summarization route override rides a name-matched replacement of the official compaction-basic engine and changes only the summarization request's provider/model, forwarding the row's own engine config unchanged. Because the Web surface runs session compaction inside each agent preset's isolated compaction group and profile patches cannot address rows inside a preset's plugins list, the plugin replaces the shipped preset rows wholesale (the Web preset editor's own save mechanism) to swap that group's engine; the copies are re-synced per DSH release during the existing compatibility verification, and a deployment that edits presets in the Web editor owns the merge from its own wholesale row. Model Switch does not own global compaction policy, titles, fetch routing, fallback, load balancing, provider credentials, CLI/API, config migration, or DSH Core modifications.
+Send-time switch compaction (`compactOnSwitch`) was removed in 0.4.25: injecting plugin-authored compaction checkpoints and notices during model switches interacted with the official `compaction-basic` step-pressure loop when a session's working set stayed near the target window's pressure threshold. All compaction policy and triggers belong exclusively to DSH's official compaction engine (`/compact` and automatic pressure/overflow compaction). The Auto reviewer route override rides a name-matched replacement of the experimental auto-review row and changes only the review request's provider/model. The compaction summarization route override rides a name-matched replacement of the official compaction-basic engine and changes only the summarization request's provider/model, forwarding the row's own engine config unchanged. Because the Web surface runs session compaction inside each agent preset's isolated compaction group and profile patches cannot address rows inside a preset's plugins list, the Host bridges that nested row at startup (`src/preset-sync.ts`): it disables the group's official `compaction-basic` and inserts `model-switch-compaction` directly after it, leaving every other row exactly as the installed DSH (or a deployment's own Web-editor save) wrote it. The plugin ships no preset copies: a DSH preset change needs no re-sync, and a deployment's preset edits are preserved. Model Switch does not own global compaction policy, titles, fetch routing, fallback, load balancing, provider credentials, CLI/API, config migration, or DSH Core modifications.
 
 Official `settings.section` has no icon field. The Settings nav glyph is a label-matched DOM swap, the same published pattern as usage-monitor, until an official icon seam exists. The Plan Review takeover uses priority -5, and the composer model seat uses priority -10.
 

package/README.md

@@ -111,7 +111,7 @@ Each summarization call (`options.purpose === 'compaction'`) also resolves its r
         summarizationModel: deepseek-reasoner
 ```
 
-How the route reaches the engine depends on where the deployment runs its agent plane. The Web surface moves compaction into each agent preset's isolated `compaction` group, and profile patches cannot address rows inside a preset's `plugins` list — so this plugin replaces each shipped preset row wholesale (the same id-targeted mechanism the Web preset editor saves with) and swaps that group's official `compaction-basic` for `model-switch-compaction`, which mounts the **same official `BasicCompactionEngine`** under `compactionScope`. Surfaces that compose the agent process-wide (the TUI) use the top-level row replacement instead. Two consequences: a DSH release that edits those presets needs the copies re-synced (this plugin's per-release verification covers it), and a deployment that edits presets in the Web editor writes its own wholesale row that then owns the merge.
+How the route reaches the engine depends on where the deployment runs its agent plane. The Web surface moves compaction into each agent preset's isolated `compaction` group, and profile patches cannot address rows inside a preset's `plugins` list — so the Host bridges that nested row at startup (`src/preset-sync.ts`): it disables the group's official `compaction-basic` and inserts `model-switch-compaction` directly after it, which mounts the **same official `BasicCompactionEngine`** under `compactionScope`. Every other preset row is left exactly as the installed DSH (or a deployment's own Web-editor save) wrote it; the plugin ships no preset copies, so a DSH preset change needs no re-sync and a deployment's preset edits are preserved. Surfaces that compose the agent process-wide (the TUI) use the top-level row replacement instead.
 
 Known issue (upstream; recorded in `docs/seam-gap.md`): while the working set stays above the official engine's pressure threshold, automatic compaction can fire on every step and keep re-attempting ranges whose summaries fail the engine's own "summary must be smaller" guard — a visible loop of automatic compactions that this plugin does not control (verified in a session A/B with the plugin enabled and disabled). Mitigations on the forwarded row config: `auto: false` (keeps `/compact`), a higher `thresholdRatio`, a smaller mounted tool schema, or a pinned compaction model whose summaries are leaner.
 
@@ -148,10 +148,10 @@ dsh plugin --profile web add --force dsh-model-switch
 A packed tarball installs the same build without a registry:
 
 ```sh
-dsh plugin --profile web add --force ./dsh-model-switch-0.4.17.tgz
+dsh plugin --profile web add --force ./dsh-model-switch-0.4.26.tgz
 ```
 
-Then install only the provider adapters you use. This release was checked against official DeepSeek Harness `0.1.7-rc.2` and verified on `0.2.0-rc.2`:
+Then install only the provider adapters you use. This release was checked against official DeepSeek Harness `0.1.7-rc.2` and verified on `0.2.0-rc.2` and `0.2.1-rc.2`:
 
 ```sh
 dsh plugin --profile web add --force \

package/README.zh.md

@@ -109,7 +109,7 @@ Plan Review 拥有独立于会话当前路由的执行模型草稿。**确认执
         summarizationModel: deepseek-reasoner
 ```
 
-路由如何到达压缩引擎取决于部署在哪一层组合 agent。Web 面把压缩放进每个 Agent 预设的隔离 `compaction` 组里，而 profile patch 无法寻址 preset `plugins` 列表内部的行——因此本插件整表替换各预设行（与 Web 预设编辑器保存修改用的是同一套 id 定位机制），把该组的官方 `compaction-basic` 换成 `model-switch-compaction`，由它在 `compactionScope` 下挂载**同一份官方 `BasicCompactionEngine`**。进程级组合 agent 的面（如 TUI）则走顶层行替换。两个后果：DSH 发布若改动这些预设，随包副本需要同步（本插件的逐版本核对覆盖这一步）；部署若用 Web 编辑器改预设，会写出自己的整表行、并从那之后自行负责合并。
+路由如何到达压缩引擎取决于部署在哪一层组合 agent。Web 面把压缩放进每个 Agent 预设的隔离 `compaction` 组里，而 profile patch 无法寻址 preset `plugins` 列表内部的行——因此 Host 在启动时桥接那一行（`src/preset-sync.ts`）：禁用该组的官方 `compaction-basic`，并在其后插入 `model-switch-compaction`，由它在 `compactionScope` 下挂载**同一份官方 `BasicCompactionEngine`**。其余预设行一律保持安装版 DSH（或部署在 Web 编辑器里保存的版本）的原样；插件不再随包携带预设副本，所以 DSH 改预设无需再同步副本，部署自己的预设修改也不会被覆盖。进程级组合 agent 的面（如 TUI）则走顶层行替换。
 
 已知问题（上游侧，见 `docs/seam-gap.md`）：当工作集持续超过官方引擎的压力阈值时，自动压缩可能每步触发，并反复重试摘要过不了官方「摘要必须更小」守卫的小片段——表现为"不停自动压缩"，本插件不控制该行为（已在同一会话做过插件开/关 A/B 对照）。可用的缓解（都在转发行配置上）：`auto: false`（保留 `/compact`）、调高 `thresholdRatio`、减少挂载的工具 schema，或固定一个摘要更精炼的压缩模型。
 
@@ -180,7 +180,7 @@ DeepSeek 薄适配器调用官方公开 `DeepSeekSearchProvider`，复用用户
 
 DSH Host peer 和开发依赖接受 `>=0.1.7-alpha.2`，包括 rc.1 和后续版本。开发锁文件解析到 rc.2。Cordis 接受 `>=4.0.4 <5.0.0`。
 
-已验证版本：`0.1.7-alpha.2`、`0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.2`。0.2.0 的声明覆盖三处差异：Host 改名的提问撤下动词（`cancel()` → `dismiss()`）、`session.selectModel` 不 await 的部署默认值写入、以返回值报出的 `ModelDirectory.select` 拒绝；三者均已在 lab（3082/3085）与真实桌面会话中逐一验证。
+已验证版本：`0.1.7-alpha.2`、`0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.2`、`0.2.1-rc.2`。0.2.0 的声明覆盖三处差异：Host 改名的提问撤下动词（`cancel()` → `dismiss()`）、`session.selectModel` 不 await 的部署默认值写入、以返回值报出的 `ModelDirectory.select` 拒绝；三者均已在 lab（3082/3085）与真实桌面会话中逐一验证。0.2.1 的声明覆盖两处被替换的 seam：共享命名调用改为 provider 自备提示词与解析的 `executeSessionTitleLlm`（本插件按安装行在运行时适配，并镜像官方 0.2.1 的提示词、取最低 reasoning effort 与 `currentTitle` 锚定）；Subagent 运行时以 `startActivation` 取代 `start()`/`startContinuable()`，路由版运行时在新 Host 上不可用，本插件改为挂载未经改动的官方运行时并输出一条明确提示（记录于 `docs/seam-gap.md`）。0.2.1 的 lab 证据为：npm 安装的 0.2.1 运行时 + 打包后的 0.4.26 组合 `exit 0`、命名/压缩/自动审查/子代理四行均来自本插件、Web Host 在 3082 启动并服务需要鉴权的页面；该次未经浏览器调用 3082 能力 RPC，真实桌面的 0.2.1 命名差分在应用升级后复验。0.2.1 还暴露出一处预设层面的差异（0.2.1 校验提示词变量、只有 `provider`/`model`，且把 `time-context`/`tool-schedule` 移进预设）：0.4.26 的静态预设副本因此让每一轮都报 `unknown prompt variable "{{cwd}}"`，0.4.27 删除副本改为启动期运行时桥接，并在 lab 的 0.2.1 headless 真实回合中验证通过（展开见 CHANGELOG 0.4.27）。
 
 `package.json#dsh.compatibility.dshReleases` 中的已验证版本是证据，不是允许列表。新增验证声明前要审查公开 API 变化并测试新 Host 版本。
 

package/cordis.patch.yml

@@ -34,479 +34,25 @@
   name: '@deepseek-ai/dsh-session-title-first-prompt-llm'
   disabled: true
 
-# The Web surface moves the agent plane (tools, compaction, delegation) into
-# per-session agent presets: session /compact and official automatic compaction
-# run against the compaction service inside each preset's isolated `compaction`
-# group, not the top-level row disabled above. The Loader's patch index cannot
-# address rows inside a preset's `config.plugins` list, so Model Switch replaces
-# each preset row wholesale — the same id-targeted mechanism the Web preset
-# editor saves with — and swaps that group's official compaction-basic for
-# model-switch-compaction. The copies come from
-# @deepseek-ai/dsh-web-app/presets/*.patch.yml (minimal has no compaction
-# group); a DSH release that edits those presets needs the copies re-synced as
-# part of the per-release verification, and a deployment that edits presets in
-# the Web editor writes its own wholesale row that owns the merge from there.
-# standard: agent-preset row replaced wholesale so its compaction group runs
-# model-switch-compaction (configurable summarization route) instead of the
-# official compaction-basic. Source: @deepseek-ai/dsh-web-app/presets/standard.patch.yml.
-- id: preset-standard
-  name: '@deepseek-ai/dsh-agent-preset'
-  config:
-    id: standard
-    order: 1
-    plugins:
-      - id: persona
-        name: '@deepseek-ai/dsh-persona'
-        config:
-          suffix: Your working directory is {{cwd}}.
-          prefix: You are a coding agent powered by the {{model}} model.
-      - id: agent-instructions
-        name: '@deepseek-ai/dsh-agent-instructions'
-        config:
-          maxBytes: 65536
-      - id: tool-bash
-        name: '@deepseek-ai/dsh-tool-bash'
-        disabled: !!js process.platform === 'win32'
-      - id: tool-pwsh
-        name: '@deepseek-ai/dsh-tool-pwsh'
-        disabled: !!js process.platform !== 'win32'
-      - id: tool-fs
-        name: '@deepseek-ai/dsh-tool-fs'
-      - id: tool-fs-search
-        name: '@deepseek-ai/dsh-tool-fs-search'
-        config:
-          sampleOverCapGlobResults: false
-      - id: tool-jobs
-        name: '@deepseek-ai/dsh-tool-jobs'
-      - id: skill-filesystem
-        name: '@deepseek-ai/dsh-skill-filesystem'
-      - id: tool-skill
-        name: '@deepseek-ai/dsh-tool-skill'
-      - id: command-goal
-        name: '@deepseek-ai/dsh-command-goal'
-      - id: tool-goal
-        name: '@deepseek-ai/dsh-tool-goal'
-      - id: planning
-        name: cordis:group
-        group: true
-        isolate:
-          planMode: true
-        config:
-          - id: plan-mode
-            name: '@deepseek-ai/dsh-plan-mode'
-            config:
-              section: |
-                You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement 鈥?including an answer confirming something you asked 鈥?approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
-
-                Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
-
-                The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
-
-                Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
-
-                Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
-
-                When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
-      - id: compaction
-        name: cordis:group
-        group: true
-        isolate:
-          compaction: true
-          toolResultPruner: true
-        config:
-          - id: compaction-basic
-            name: '@deepseek-ai/dsh-compaction-basic'
-            disabled: true
-          - id: model-switch-compaction
-            name: 'dsh-model-switch/compaction'
-          - id: command-compact
-            name: '@deepseek-ai/dsh-command-compact'
-          - id: tool-result-pruner
-            name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
-            config:
-              thresholdChars: 8192
-              headChars: 4096
-              tailChars: 1024
-      - id: delegation
-        name: cordis:group
-        group: true
-        isolate:
-          workflowEngine: true
-        config:
-          - id: tool-subagent-control
-            name: '@deepseek-ai/dsh-tool-subagent-control'
-          - id: tool-subagent-list-agents
-            name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
-          - id: tool-subagent
-            name: '@deepseek-ai/dsh-tool-subagent'
-            config:
-              provider: spawn
-              toolName: subagent
-              modelSelectionSettings: true
-              backgroundMode: continuable
-          - id: tool-subagent-fork
-            name: '@deepseek-ai/dsh-tool-subagent'
-            config:
-              provider: fork
-              toolName: subagent_fork
-              backgroundMode: continuable
-          - id: tool-subagent-codex
-            name: '@deepseek-ai/dsh-tool-subagent'
-            disabled: true
-            config:
-              provider: codex
-              toolName: subagent_codex
-              backgroundMode: one-shot
-              maxDepth: provider-managed
-          - id: tool-subagent-claude-code
-            name: '@deepseek-ai/dsh-tool-subagent'
-            disabled: true
-            config:
-              provider: claude-code
-              toolName: subagent_claude_code
-              backgroundMode: one-shot
-              maxDepth: provider-managed
-          - id: workflow-ptc
-            name: '@deepseek-ai/dsh-workflow-ptc'
-            config:
-              provider: spawn
-          - id: tool-workflow
-            name: '@deepseek-ai/dsh-tool-workflow'
-          - id: tool-ralph
-            name: '@deepseek-ai/dsh-tool-ralph'
-            disabled: true
-            config:
-              subagentProvider: spawn
-              maxRounds: 64
-      - id: tool-ask-user
-        name: '@deepseek-ai/dsh-tool-ask-user'
-      - id: tool-todo
-        name: '@deepseek-ai/dsh-tool-todo'
-        config:
-          allowParallelInProgress: true
-      - id: tool-web
-        name: '@deepseek-ai/dsh-tool-web'
-        config:
-          fetch: true
-          searchTimeoutMs: 60000
-      - id: present
-        name: '@deepseek-ai/dsh-tool-present'
-      - id: tool-plugin-manager
-        name: '@deepseek-ai/dsh-plugin-manager/tools'
-        disabled: true
-
-# ptc: agent-preset row replaced wholesale so its compaction group runs
-# model-switch-compaction (configurable summarization route) instead of the
-# official compaction-basic. Source: @deepseek-ai/dsh-web-app/presets/ptc.patch.yml.
-- id: preset-ptc
-  name: '@deepseek-ai/dsh-agent-preset'
-  config:
-    id: ptc
-    order: 2
-    plugins:
-      - id: persona
-        name: '@deepseek-ai/dsh-persona'
-        config:
-          suffix: Your working directory is {{cwd}}.
-          prefix: You are a coding agent powered by the {{model}} model.
-      - id: agent-instructions
-        name: '@deepseek-ai/dsh-agent-instructions'
-        config:
-          maxBytes: 65536
-      - id: tool-bash
-        name: '@deepseek-ai/dsh-tool-bash'
-        disabled: !!js process.platform === 'win32'
-      - id: tool-pwsh
-        name: '@deepseek-ai/dsh-tool-pwsh'
-        disabled: !!js process.platform !== 'win32'
-      - id: tool-fs
-        name: '@deepseek-ai/dsh-tool-fs'
-      - id: tool-fs-search
-        name: '@deepseek-ai/dsh-tool-fs-search'
-        config:
-          sampleOverCapGlobResults: false
-      - id: tool-jobs
-        name: '@deepseek-ai/dsh-tool-jobs'
-      - id: skill-filesystem
-        name: '@deepseek-ai/dsh-skill-filesystem'
-      - id: tool-skill
-        name: '@deepseek-ai/dsh-tool-skill'
-      - id: command-goal
-        name: '@deepseek-ai/dsh-command-goal'
-      - id: tool-goal
-        name: '@deepseek-ai/dsh-tool-goal'
-      - id: planning
-        name: cordis:group
-        group: true
-        isolate:
-          planMode: true
-        config:
-          - id: plan-mode
-            name: '@deepseek-ai/dsh-plan-mode'
-            config:
-              section: |
-                You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement 鈥?including an answer confirming something you asked 鈥?approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
-
-                Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
-
-                The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
-
-                Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
-
-                Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
-
-                When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
-      - id: compaction
-        name: cordis:group
-        group: true
-        isolate:
-          compaction: true
-          toolResultPruner: true
-        config:
-          - id: compaction-basic
-            name: '@deepseek-ai/dsh-compaction-basic'
-            disabled: true
-          - id: model-switch-compaction
-            name: 'dsh-model-switch/compaction'
-          - id: command-compact
-            name: '@deepseek-ai/dsh-command-compact'
-          - id: tool-result-pruner
-            name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
-            config:
-              thresholdChars: 8192
-              headChars: 4096
-              tailChars: 1024
-      - id: delegation
-        name: cordis:group
-        group: true
-        isolate:
-          workflowEngine: true
-        config:
-          - id: tool-subagent-control
-            name: '@deepseek-ai/dsh-tool-subagent-control'
-          - id: tool-subagent-list-agents
-            name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
-          - id: tool-subagent
-            name: '@deepseek-ai/dsh-tool-subagent'
-            config:
-              provider: spawn
-              toolName: subagent
-              modelSelectionSettings: true
-              backgroundMode: continuable
-          - id: tool-subagent-fork
-            name: '@deepseek-ai/dsh-tool-subagent'
-            config:
-              provider: fork
-              toolName: subagent_fork
-              backgroundMode: continuable
-          - id: tool-subagent-codex
-            name: '@deepseek-ai/dsh-tool-subagent'
-            disabled: true
-            config:
-              provider: codex
-              toolName: subagent_codex
-              backgroundMode: one-shot
-              maxDepth: provider-managed
-          - id: tool-subagent-claude-code
-            name: '@deepseek-ai/dsh-tool-subagent'
-            disabled: true
-            config:
-              provider: claude-code
-              toolName: subagent_claude_code
-              backgroundMode: one-shot
-              maxDepth: provider-managed
-          - id: workflow-ptc
-            name: '@deepseek-ai/dsh-workflow-ptc'
-            disabled: true
-            config:
-              provider: spawn
-          - id: tool-workflow
-            name: '@deepseek-ai/dsh-tool-workflow'
-            disabled: true
-          - id: tool-ralph
-            name: '@deepseek-ai/dsh-tool-ralph'
-            disabled: true
-            config:
-              subagentProvider: spawn
-              maxRounds: 64
-      - id: tool-ask-user
-        name: '@deepseek-ai/dsh-tool-ask-user'
-      - id: tool-todo
-        name: '@deepseek-ai/dsh-tool-todo'
-        config:
-          allowParallelInProgress: true
-      - id: tool-web
-        name: '@deepseek-ai/dsh-tool-web'
-        config:
-          fetch: true
-          searchTimeoutMs: 60000
-      - id: tool-presentation
-        name: '@deepseek-ai/dsh-agent-tool-presentation'
-        config:
-          mode: ptc
-      - id: present
-        name: '@deepseek-ai/dsh-tool-present'
-      - id: tool-plugin-manager
-        name: '@deepseek-ai/dsh-plugin-manager/tools'
-        disabled: true
-
-# cordis: agent-preset row replaced wholesale so its compaction group runs
-# model-switch-compaction (configurable summarization route) instead of the
-# official compaction-basic. Source: @deepseek-ai/dsh-web-app/presets/cordis.patch.yml.
-- id: preset-cordis
-  name: '@deepseek-ai/dsh-agent-preset'
-  config:
-    id: cordis
-    order: 4
-    plugins:
-      # Same persona as `standard`: tool descriptions and the skill catalog carry
-      # the operating detail, and the skills own the preset-authoring rules.
-      - id: persona
-        name: '@deepseek-ai/dsh-persona'
-        config:
-          suffix: Your working directory is {{cwd}}.
-          prefix: >-
-            You are a coding agent powered by the {{model}} model.
-      - id: agent-instructions
-        name: '@deepseek-ai/dsh-agent-instructions'
-        config:
-          maxBytes: 65536
-      - id: tool-bash
-        name: '@deepseek-ai/dsh-tool-bash'
-        disabled: !!js process.platform === 'win32'
-      - id: tool-pwsh
-        name: '@deepseek-ai/dsh-tool-pwsh'
-        disabled: !!js process.platform !== 'win32'
-      - id: tool-fs
-        name: '@deepseek-ai/dsh-tool-fs'
-      - id: tool-fs-search
-        name: '@deepseek-ai/dsh-tool-fs-search'
-        config:
-          sampleOverCapGlobResults: false
-      - id: tool-jobs
-        name: '@deepseek-ai/dsh-tool-jobs'
-      - id: command-goal
-        name: '@deepseek-ai/dsh-command-goal'
-      - id: tool-goal
-        name: '@deepseek-ai/dsh-tool-goal'
-      - id: planning
-        name: cordis:group
-        group: true
-        isolate:
-          planMode: true
-        config:
-          - id: plan-mode
-            name: '@deepseek-ai/dsh-plan-mode'
-            config:
-              section: |
-                You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement 鈥?including an answer confirming something you asked 鈥?approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
-
-                Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
-
-                The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
-
-                Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
-
-                Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
-
-                When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
-      - id: compaction
-        name: cordis:group
-        group: true
-        isolate:
-          compaction: true
-          toolResultPruner: true
-        config:
-          - id: compaction-basic
-            name: '@deepseek-ai/dsh-compaction-basic'
-            disabled: true
-          - id: model-switch-compaction
-            name: 'dsh-model-switch/compaction'
-          - id: command-compact
-            name: '@deepseek-ai/dsh-command-compact'
-          - id: tool-result-pruner
-            name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
-            config:
-              thresholdChars: 8192
-              headChars: 4096
-              tailChars: 1024
-      - id: delegation
-        name: cordis:group
-        group: true
-        isolate:
-          workflowEngine: true
-        config:
-          - id: tool-subagent-control
-            name: '@deepseek-ai/dsh-tool-subagent-control'
-          - id: tool-subagent-list-agents
-            name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
-          - id: tool-subagent
-            name: '@deepseek-ai/dsh-tool-subagent'
-            config:
-              provider: spawn
-              toolName: subagent
-              modelSelectionSettings: true
-              backgroundMode: continuable
-          - id: tool-subagent-fork
-            name: '@deepseek-ai/dsh-tool-subagent'
-            config:
-              provider: fork
-              toolName: subagent_fork
-              backgroundMode: continuable
-          - id: tool-subagent-codex
-            name: '@deepseek-ai/dsh-tool-subagent'
-            disabled: true
-            config:
-              provider: codex
-              toolName: subagent_codex
-              backgroundMode: one-shot
-              maxDepth: provider-managed
-          - id: tool-subagent-claude-code
-            name: '@deepseek-ai/dsh-tool-subagent'
-            disabled: true
-            config:
-              provider: claude-code
-              toolName: subagent_claude_code
-              backgroundMode: one-shot
-              maxDepth: provider-managed
-          - id: workflow-ptc
-            name: '@deepseek-ai/dsh-workflow-ptc'
-            config:
-              provider: spawn
-          - id: tool-workflow
-            name: '@deepseek-ai/dsh-tool-workflow'
-          - id: tool-ralph
-            name: '@deepseek-ai/dsh-tool-ralph'
-            disabled: true
-            config:
-              subagentProvider: spawn
-              maxRounds: 64
-      - id: tool-ask-user
-        name: '@deepseek-ai/dsh-tool-ask-user'
-      - id: tool-todo
-        name: '@deepseek-ai/dsh-tool-todo'
-        config:
-          allowParallelInProgress: true
-      - id: tool-web
-        name: '@deepseek-ai/dsh-tool-web'
-        config:
-          fetch: true
-          searchTimeoutMs: 60000
-      - id: tool-cordis
-        name: '@deepseek-ai/dsh-tool-cordis'
-      - id: skill-filesystem
-        name: '@deepseek-ai/dsh-skill-filesystem'
-        config:
-          customSkillDirs:
-            - !!js process.getBuiltinModule('node:path').join(process.getBuiltinModule('node:path').dirname(process.getBuiltinModule('node:module').createRequire(baseUrl).resolve('@deepseek-ai/dsh-agent-preset/package.json')), 'skills')
-      - id: tool-skill
-        name: '@deepseek-ai/dsh-tool-skill'
-      - id: present
-        name: '@deepseek-ai/dsh-tool-present'
-      - id: tool-plugin-manager
-        name: '@deepseek-ai/dsh-plugin-manager/tools'
-        disabled: !!js "!ctx.get('profileContext')"
+# DSH 0.2.1's optional experimental session-titles bundle disables the row above
+# and inserts its own all-prompts provider row. Model Switch owns this seam as
+# well, so that row is disabled by its id too; a profile that never enabled the
+# bundle has no such row and the non-insert target is skipped with a warning,
+# exactly like the optional auto-review row above.
+- id: optional-session-title-all-prompts
+  name: '@deepseek-ai/dsh-session-title-all-prompts-llm'
+  disabled: true
 
+# The Web surface runs session compaction inside each agent preset's isolated
+# compaction group, and the Loader patch index cannot address rows inside a
+# preset's config.plugins list. This plugin therefore bridges the nested
+# compaction engine at Host startup (src/preset-sync.ts): the shipped (or a
+# deployment-edited) preset definition stays authoritative, and only the
+# official compaction-basic row is disabled and followed by
+# model-switch-compaction. Static copies of the shipped presets are gone —
+# they broke DSH 0.2.1 turns, whose prompt-variable validation rejects the
+# older copies' persona suffix (unknown prompt variable {{cwd}}), and local
+# copies would hide every later preset change from the deployment.
 
 - insert:
     # Register Model Switch Host Settings/Main runtime before routed Subagents.

package/lib/auto-review.js

@@ -1,4 +1,4 @@
-import { n as sessionProviderOf, t as resolveCapabilityRoute } from "./session-route-BCQFzqRP.js";
+import { i as sessionProviderOf, r as resolveCapabilityRoute } from "./session-route-BjNPlliu.js";
 import { AsyncLocalStorage } from "node:async_hooks";
 //#region lib/types/auto-review.js
 /**

package/lib/compaction.js

@@ -1,4 +1,4 @@
-import { n as sessionProviderOf, t as resolveCapabilityRoute } from "./session-route-BCQFzqRP.js";
+import { i as sessionProviderOf, r as resolveCapabilityRoute } from "./session-route-BjNPlliu.js";
 //#region lib/types/compaction.js
 /** Official compaction row this module supersedes. */
 const OFFICIAL_COMPACTION_ROW = "compaction-basic";