dsh-any-background 0.3.3 → 0.3.4

package/README.md

@@ -4,7 +4,7 @@
   <a href="https://www.npmjs.com/package/dsh-any-background"><img alt="npm version" src="https://img.shields.io/npm/v/dsh-any-background?color=4d6bfe"></a>
   <a href="https://www.npmjs.com/package/dsh-any-background"><img alt="npm monthly downloads" src="https://img.shields.io/npm/dm/dsh-any-background?color=4d6bfe"></a>
   <a href="https://github.com/Tkingxiao/dsh-any-background/blob/main/LICENSE"><img alt="License: MIT" src="https://img.shields.io/npm/l/dsh-any-background?color=4d6bfe"></a>
-  <a href="https://www.npmjs.com/package/@deepseek-ai/dsh?activeTab=versions"><img alt="Supported DSH versions: 0.1.5-rc.2 ~ 0.2.0-rc.1" src="https://img.shields.io/badge/DSH-0.1.5--rc.2%20~%200.2.0--rc.1-4d6bfe" /></a>
+  <a href="https://www.npmjs.com/package/@deepseek-ai/dsh?activeTab=versions"><img alt="Supported DSH versions: 0.1.5-rc.2 ~ 0.2.1-alpha.1 and above" src="https://img.shields.io/badge/DSH-0.1.5--rc.2%20~%200.2.1--alpha.1%2B-4d6bfe" /></a>
   <a href="https://github.com/topics/dsh-better-sidebar"><img alt="Plugin ecosystem: GitHub topic dsh-better-sidebar" src="https://img.shields.io/badge/plugin%20ecosystem-topic%20dsh--better--sidebar-4d6bfe" /></a><br /><br />
   <a href="https://github.com/Tkingxiao/dsh-any-background"><img src="https://img.shields.io/github/stars/Tkingxiao/dsh-any-background?style=social" alt="GitHub stars"></a>
   <a href="https://dsh.directory/plugins/tkingxiao/dsh-any-background"><img src="https://dsh.directory/badges/listed.svg" alt="dsh.directory listed"></a>
@@ -12,7 +12,7 @@
 
 English | [中文](README.zh.md)
 
-A **DeepSeek Harness** appearance plugin: custom theme color, background wallpaper (image / video / algorithmically generated), and fine-grained per-surface opacity & blur controls. Compatible with **DSH 0.1.5-rc.2 through the whole 0.1.7 line below 0.2.0, plus `0.2.0-rc.1`** (official-Sidebar UI such as the "Theme" card enables itself where the host exposes the Sidebar registry extension point, and is skipped silently where it does not).
+A **DeepSeek Harness** appearance plugin: custom theme color, background wallpaper (image / video / algorithmically generated), and fine-grained per-surface opacity & blur controls. Compatible with **DSH 0.1.5-rc.2 through `0.2.1-alpha.1` — and every host release above it** (official-Sidebar UI such as the "Theme" card enables itself where the host exposes the Sidebar registry extension point, and is skipped silently where it does not).
 
 ---
 
@@ -91,6 +91,16 @@ A **DeepSeek Harness** appearance plugin: custom theme color, background wallpap
 
 ## Changelog (latest two releases)
 
+### v0.3.4 (Two new host lines: `0.2.0-rc.2` and `0.2.1-alpha.1`)
+
+- **A sticky menu group heading got its own token on `0.2.0-rc.2`** (`--dsw-alias-menu-group-header-fill`, replacing `ModelSelect`'s `.groupTitle{background:var(--dsw-specific-menu)}`), so the model list's heading follows the card / header opacity slider and the picked theme color again instead of sitting on the faded menu as an untinted, near-opaque band. This is the first patch line that needed two folders — rc.1 and rc.2 are the same prerelease channel with different facts — so its folder is named for the build.
+- **The turn-event row now fades in its own color**: since rc.2 it fills from `--dsw-alias-turn-trigger-bg` (dark mode points that at the interactive-hover fill, not the code-block one). The plugin reads the same chain the host writes, fallback included, so a newer host takes its new color, an older one takes the code-block color, and no release test enters the styling code.
+- **DSH `0.2.1-alpha.1` is supported**: `design-platform.css`, `MenuGroup` and `MenuSurface` are byte-identical to rc.2, and the new `shell.bottom` strip paints `--dsw-alias-bg-base` — the main-background token — so the existing slider already owns it.
+- **Small host releases no longer need a plugin release**: `engines.dsh`, the six gated `@deepseek-ai/dsh-*` peers and `dsh.compatibility` now close with `|| 0.2.1-alpha.1 || >=0.1.7-alpha.1` — the umbrella has no upper bound. From `0.1.7-rc.1` the host disables any plugin whose peer ranges do not name the running release, and a range that runs out is a wall in front of a plugin that would have kept working: an uncapped range hands a future 0.2.x or 0.3.x build the closest verified adapter plus a log line saying how far from `exact` that is, and the worst a wrong guess can cost is one slider not fading a surface it no longer recognizes. Installing on a new host still needs a `dsh web` restart — the peer check runs while the profile is composed.
+- **The cards that take the composer seat now frost with the input blur.** Approval, plan review and the question composer render *beside* `[data-composer-card]` and fill from the same `--dsw-specific-input-major`, so they faded with the input slider while the blur slider had nothing to act on — the card you are meant to read went straight onto the wallpaper. They now get the capsule's `::before` underlay, gated on a non-zero blur so the plugin still adds no stacking context for free, and the answer field joins the input group's stroke and placeholder bindings. The anchors (`[data-approval-key]`, `[data-plan-review-key]`, `[data-question-key]`) are unchanged from `0.1.5-rc.2` through `0.2.1-alpha.1`, so this is a range-wide binding in shared host facts, not a per-version one.
+- **The `invariant` companion is gone** (`lib/invariant.js`, its `exports` entry, its `@deepseek-ai/dsh-invariants` peer): nothing ever loaded it, and `0.2.1-alpha.1` deletes that package.
+- **The settings page's stylesheet now carries the plugin tag the other sheets have.** Through rc.2 the host's module system claimed *any* untagged `<style>` present while a plugin materialized and deleted it if that plugin failed; `0.2.1-alpha.1` narrowed the claim to the tags a factory added itself. Tagged, the sheet is safe on both.
+
 ### v0.3.3 (Menu paint per release, DSH 0.2.0-rc.1 supported)
 
 - **The card and header sliders drive menus on `0.1.7-rc.2` again.** That build moved a menu's fill and frost onto a child layer and turned `--dsw-specific-menu` into an alias, so the token the plugin had always been writing was no longer read by anything on a menu. Which tokens a menu paints from, and which layer does the frosting, is now a fact each version folder supplies instead of an assumption baked into shared code.
@@ -99,16 +109,6 @@ A **DeepSeek Harness** appearance plugin: custom theme color, background wallpap
 - **The plugin page's loading skeleton** gets the same frosted card as the list it stands in for.
 - Installing on a 0.2.0 host needs a `dsh web` restart: since `0.1.7-rc.1` the host decides whether a plugin loads from its peer ranges, and a release it does not name is disabled before a single module is imported.
 
-### v0.3.2 (Produced artifacts fully bound, 0.1.7-rc.2 loads again)
-
-- **The produced slider now covers every artifact 0.1.7 renders**: tool-detail cards, turn-event rows, diff blocks, the changed-files card, inline `code` frost and the hover preview window — that last one portals its card to `<body>`, which is why no slider reached it before.
-- **Code-card headers follow the theme again** instead of staying a pale slab that ignored the slider.
-- **dsh-better-sidebar's workbench now belongs to the produced slider**; the panel row means only the host's own right Sidebar.
-- **One artifact card no longer answers to two sliders** — its root reads the produced slider's own raw layer token.
-- **The composer stops carrying a stacking context once its blur returns to 0.**
-- **antd confirm dialogs are no longer mistaken for the settings panel**: they inherited its surface colour, frost and outline group, because the old selector only asked for the three ARIA attributes antd also emits.
-- **`0.1.7-rc.2` loads again, and later 0.1.x builds with it**: `engines.dsh`, the seven `@deepseek-ai/dsh-*` peers and `dsh.compatibility` now close with `|| 0.1.7-rc.2 || >=0.1.7-alpha.1 <0.2.0-alpha.0` — a bare `>=0.1.7` would match no prerelease build at all.
-
 ## Installation
 
 ### Method 1: npm install (Recommended)
@@ -151,14 +151,14 @@ pnpm dsh web
 
 ## Compatibility
 
-- **[`dsh web`](https://github.com/deepseek-ai/deepseek-harness) 0.1.5-rc.2 ~ &lt;0.2.0, plus `0.2.0-rc.1`** — `engines.dsh`, the seven `@deepseek-ai/dsh-*` `peerDependencies` and `dsh.compatibility.dsh` list the `0.1.5-rc` and `0.1.6-alpha` builds this plugin has been checked against one by one, close that part of the range with `>=0.1.7-alpha.1 <0.2.0-alpha.0` so every 0.1.7 release loads, and then name `0.2.0-rc.1` on its own — the umbrella stops below 0.2.0 deliberately, because a 0.2.0 build this plugin has not diffed is a different host and its facts belong in their own folder. `0.1.7-rc.1` / `0.1.7-rc.2` and `0.2.0-rc.1` were checked by diffing their tags, the builds before them hands-on. From `0.1.7-rc.1` the host itself enforces that peer list — a release the ranges do not name is disabled before its modules are imported — so naming it is what makes the plugin load, not documentation; the declarations in `dsh.compatibility.dshReleases` record which builds were checked. That enforcement is also why a machine already on 0.2.0 needs a plugin release (or a manual exact-version exemption) *and* a host restart: the check runs while the profile is composed, not when the plugin is updated. The host release is resolved on the Node half at runtime, and features that depend on a specific host release channel (the right Sidebar's panel blur, the official Sidebar's "Theme" card) enable themselves only where the corresponding host structure exists; everything else behaves identically across the range.
-- **Isolated per-version adaptation**: the release is resolved on the Node half from the app manifest the process was composed from (`ctx.profileContext.installAnchor`, with the launcher's on-disk layout behind it — the client context exposes no version) and, once handed down through the `read` RPC, is routed only by the front-layer adapter — `src/host-compat/` detects and buckets channels, while `src/client/host-compat/versions/` holds **one folder per release** (`v0-1-5-rc-2-3` / `v0-1-6-alpha-1-2` / `v0-1-7-alpha-1-2-rc-1` / `v0-1-7-rc-2` / `v0-2-0-rc-1` / `unknown`), each describing that version's panel mechanics, header slot keys, plugin-page shape and where a menu's paint lives. Base code just asks the adapter questions (who owns the guide surface, which layer carries the blur, which token fades a menu) and never compares version strings. Another build on a verified patch line (`0.1.6-alpha.4` against a table checked at `alpha.2`) keeps that line's adapter, and a patch line nothing was checked against clamps to the nearest one with a log line saying so. Only a release that will not parse at all falls into `unknown` and probes the DOM shape instead of guessing (`:has()` dual arms); supporting a new host means adding one folder and registering it.
+- **[`dsh web`](https://github.com/deepseek-ai/deepseek-harness) 0.1.5-rc.2 ~ `0.2.1-alpha.1`, and everything above it with it** — `engines.dsh`, the six gated `@deepseek-ai/dsh-*` `peerDependencies` and `dsh.compatibility.dsh` name the `0.1.5-rc` / `0.1.6-alpha` builds this plugin was checked against one by one — those have to be listed, since the umbrella starts above them — keep naming every build it has since diffed (`0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, `0.2.1-alpha.1`) for the record, and close with an uncapped `>=0.1.7-alpha.1`, so every 0.1.7, 0.2 and later release loads. The uncapped umbrella is the deliberate choice: from `0.1.7-rc.1` the host enforces exactly this peer list — a release it does not name is disabled before a single module is imported — so a range that runs out is a wall in front of a plugin that would have gone on working. An unseen release gets the closest verified adapter plus a log line saying how far from `exact` that is, and the worst a stale guess can cost is one slider no longer fading a surface the host has since moved; a version check that failed closed would have cost the whole plugin. `dsh.compatibility.dshReleases` records which builds were checked and how: `0.1.7-rc.1` / `0.1.7-rc.2`, `0.2.0-rc.1` / `0.2.0-rc.2` and `0.2.1-alpha.1` were checked by diffing their tags, the builds before them hands-on. That enforcement still means a `dsh web` restart when the plugin is installed or updated — the check runs while the profile is composed, not when the plugin is updated — but the uncapped umbrella is what spares a machine that has already moved to a newer host from needing a plugin release or a manual exact-version exemption (`dsh plugin allow-version`) first. The host release is resolved on the Node half at runtime, and features that depend on a specific host release channel (the right Sidebar's panel blur, the official Sidebar's "Theme" card) enable themselves only where the corresponding host structure exists; everything else behaves identically across the range.
+- **Isolated per-version adaptation**: the release is resolved on the Node half from the app manifest the process was composed from (`ctx.profileContext.installAnchor`, with the launcher's on-disk layout behind it — the client context exposes no version) and, once handed down through the `read` RPC, is routed only by the front-layer adapter — `src/host-compat/` detects and buckets channels, while `src/client/host-compat/versions/` holds **one folder per set of verified facts** (`v0-1-5-rc-2-3` / `v0-1-6-alpha-1-2` / `v0-1-7-alpha-1-2-rc-1` / `v0-1-7-rc-2` / `v0-2-0-rc-1` / `v0-2-0-rc-2` / `v0-2-1-alpha-1` / `unknown`), each describing that version's panel mechanics, header slot keys, plugin-page shape and where a menu's paint lives. A folder is keyed to what its facts cover, not to the shape of the version number: `0.2.0-rc.1` and `0.2.0-rc.2` are one prerelease channel, but rc.2 renamed the token a sticky menu group heading paints from, so the line carries two folders and the newer one is named for the build that opened it. Base code just asks the adapter questions (who owns the guide surface, which layer carries the blur, which token fades a menu) and never compares version strings. Another build on a verified patch line (`0.1.6-alpha.4` against a table checked at `alpha.2`) keeps that line's adapter, and a patch line nothing was checked against clamps to the nearest one with a log line saying so — which is the arm that now serves every release above `0.2.1-alpha.1`. Only a release that will not parse at all falls into `unknown` and probes the DOM shape instead of guessing (`:has()` dual arms); supporting a new host means adding one folder and registering it.
 - **[DSHA](https://github.com/DSH-APP/DSHA)** — DeepSeek Harness Android launcher (ROOT-free, Termux-free). Its bundled `dsh` is `0.1.5-rc.2`, inside the supported range; the mobile UI shell is provided by `dsh-web-mobile`.
 - **[deepseek-harness-desktop](https://github.com/anywhere-labs/deepseek-harness-desktop)** — Supported
 
 ## Permissions, side effects & boundaries
 
-- **Integration form**: official Profile Bundle — `package.json` declares `dsh.bundle.patch: ./cordis.patch.yml` (a loader insert layer), the repository ships prebuilt runtime artifacts ready to use (`lib/index.js`, `lib/invariant.js`, `lib/client.js`), and there are no install scripts, no `postinstall`, no native binaries, and no build step at install time.
+- **Integration form**: official Profile Bundle — `package.json` declares `dsh.bundle.patch: ./cordis.patch.yml` (a loader insert layer), the repository ships prebuilt runtime artifacts ready to use (`lib/index.js`, `lib/client.js`), and there are no install scripts, no `postinstall`, no native binaries, and no build step at install time.
 - **Filesystem**: the server half reads and writes only inside `<dsh home>/.dsh-any-background-data/` (config JSON, wallpaper, rotation pool, video, font) and touches nothing outside it; config writes are atomic (temp file + rename). These files live on the real disk, so they are **outside generation restore — it neither captures nor rolls them back**; deleting the directory is a full plugin reset.
 - **Network**: one outbound fetch happens only when the user pastes an http/https image or video URL and presses Apply; no telemetry, no other external calls.
 - **Shell / native**: none. No `child_process`, no native modules, no dynamically downloaded executables.

package/README.zh.md

@@ -4,7 +4,7 @@
   <a href="https://www.npmjs.com/package/dsh-any-background"><img alt="npm 版本" src="https://img.shields.io/npm/v/dsh-any-background?color=4d6bfe"></a>
   <a href="https://www.npmjs.com/package/dsh-any-background"><img alt="npm 月下载量" src="https://img.shields.io/npm/dm/dsh-any-background?color=4d6bfe"></a>
   <a href="https://github.com/Tkingxiao/dsh-any-background/blob/main/LICENSE"><img alt="License: MIT" src="https://img.shields.io/npm/l/dsh-any-background?color=4d6bfe"></a>
-  <a href="https://www.npmjs.com/package/@deepseek-ai/dsh?activeTab=versions"><img alt="支持的 DSH 版本：0.1.5-rc.2 ~ 0.2.0-rc.1" src="https://img.shields.io/badge/DSH-0.1.5--rc.2%20~%200.2.0--rc.1-4d6bfe" /></a>
+  <a href="https://www.npmjs.com/package/@deepseek-ai/dsh?activeTab=versions"><img alt="支持的 DSH 版本：0.1.5-rc.2 ~ 0.2.1-alpha.1 及其上" src="https://img.shields.io/badge/DSH-0.1.5--rc.2%20~%200.2.1--alpha.1%2B-4d6bfe" /></a>
   <a href="https://github.com/topics/dsh-better-sidebar"><img alt="插件生态：GitHub topic dsh-better-sidebar" src="https://img.shields.io/badge/%E6%8F%92%E4%BB%B6%E7%94%9F%E6%80%81-topic%20dsh--better--sidebar-4d6bfe" /></a><br /><br />
   <a href="https://github.com/Tkingxiao/dsh-any-background"><img src="https://img.shields.io/github/stars/Tkingxiao/dsh-any-background?style=social" alt="GitHub stars"></a>
   <a href="https://dsh.directory/plugins/tkingxiao/dsh-any-background"><img src="https://dsh.directory/badges/listed.svg" alt="dsh.directory listed"></a>
@@ -12,7 +12,7 @@
 
 [English](README.md) | 中文
 
-一个 **DeepSeek Harness** 外观插件：自定义主题色、背景壁纸（图片 / 视频 / 算法动态生成），以及逐表面的透明度与模糊度控制。兼容 **DSH 0.1.5-rc.2 起、0.2.0 之前的整条 0.1.7 线，外加 `0.2.0-rc.1`**（官方右侧栏「主题」卡片等界面按宿主是否提供右侧栏注册表扩展点自动启用，缺失时静默跳过）。
+一个 **DeepSeek Harness** 外观插件：自定义主题色、背景壁纸（图片 / 视频 / 算法动态生成），以及逐表面的透明度与模糊度控制。兼容 **DSH 0.1.5-rc.2 直至 `0.2.1-alpha.1`，其上所有版本一并放行**（官方右侧栏「主题」卡片等界面按宿主是否提供右侧栏注册表扩展点自动启用，缺失时静默跳过）。
 
 ---
 
@@ -91,6 +91,16 @@
 
 ## 更新日志（只保留最近两个版本）
 
+### v0.3.4（新增两条宿主线：`0.2.0-rc.2` 与 `0.2.1-alpha.1`）
+
+- **`0.2.0-rc.2` 给吸顶的菜单分组标题另发了令牌**（`--dsw-alias-menu-group-header-fill`，取代 `ModelSelect` 自己的 `.groupTitle{background:var(--dsw-specific-menu)}`）：模型列表的分组标题重新跟着「卡片」「顶栏选项」两组滑块与所选主题色走，不再以一条不套色、近乎不透明的白带压在淡出的菜单上。这是第一条需要两个目录的补丁行——rc.1 与 rc.2 同属一个预发布渠道却交出不同的事实——所以新目录按构建命名。
+- **事件行改用他自己的颜色淡出**：rc.2 起该行从 `--dsw-alias-turn-trigger-bg` 取底（深色模式下这个别名指向交互态底色，不再是代码块那一层）。插件按宿主写下的链条去读，连带回退值一起，于是新构建拿新颜色、旧构建拿代码块颜色，样式代码里不引入任何版本判断。
+- **支持 DSH `0.2.1-alpha.1`**：`design-platform.css`、`MenuGroup`、`MenuSurface` 与 rc.2 逐字节相同；新增的 `shell.bottom` 条带画的是 `--dsw-alias-bg-base`——主背景令牌——背景透明度滑块本来就管着它。
+- **宿主小版本更新不再需要插件跟着发版**：`engines.dsh`、六个受门禁的 `@deepseek-ai/dsh-*` peer 与 `dsh.compatibility` 现在以 `|| 0.2.1-alpha.1 || >=0.1.7-alpha.1` 收尾——总括不设上界。从 `0.1.7-rc.1` 起，peer 范围没点名当前 release 的插件会被整个禁用，而一条写到头的范围等于在一款还能继续工作的插件前面砌墙：不设上界的范围会把未来的 0.2.x、0.3.x 构建交给最近的一份已核对事实，并在日志里写清它离 `exact` 有多远；猜错的最坏代价是某个滑块不再淡出它已认不出的表面。装到新宿主仍要重启 `dsh web`——peer 检查发生在 profile 组装时。
+- **接管输入位的那几张卡片现在跟着「输入模糊」磨砂了**：审批、计划回顾与问题卡渲染在 `[data-composer-card]` 的*旁边*，却填的是同一个 `--dsw-specific-input-major`——于是它们会随输入透明度淡出，模糊滑块却对它们无事可做，正是最该看清的那张卡直接压在壁纸上。现在它们拿到输入胶囊同款 `::before` 衬底，并且和胶囊一样只在模糊值非零时挂上，零值时插件不额外制造层叠上下文；答案输入框一并接进输入组的描边与占位符绑定。三张卡的锚点（`[data-approval-key]` / `[data-plan-review-key]` / `[data-question-key]`）从 `0.1.5-rc.2` 到 `0.2.1-alpha.1` 没有变过，所以这条绑定是全范围的事实，放在共享层而不是某个版本目录里。
+- **删掉 `invariant` 伴生入口**（`lib/invariant.js`、它的 `exports` 条目、它的 `@deepseek-ai/dsh-invariants` peer）：从来没有任何一行装载它，而 `0.2.1-alpha.1` 已把这个包从宿主里移除。
+- **设置页那份样式表补上了其它表都有的插件标记**：到 rc.2 为止，宿主的模块系统会把当时*所有*未打标的 `<style>` 判给正在装配的那个插件，并在该插件失败时把它们删掉；`0.2.1-alpha.1` 把认领范围收窄到工厂自己新增的那些。打上标记后，两种宿主都动不了它。
+
 ### v0.3.3（菜单按版本交出绘制事实，支持 DSH 0.2.0-rc.1）
 
 - **`0.1.7-rc.2` 上「卡片」「顶栏选项」两组滑块对菜单又有效了**：那个构建把菜单的底色与磨砂移到子层，并把 `--dsw-specific-menu` 改成别名，插件一直在写的令牌在菜单上再没有别的读者。「菜单从哪些令牌取色、磨砂由哪一层承担」现在由每个版本目录各自交出，公共代码里不再留假设。
@@ -99,16 +109,6 @@
 - **插件页首屏的加载骨架屏**拿到与它所代替的那张卡片列表相同的磨砂底。
 - 装到 0.2.0 宿主上要重启 `dsh web`：从 `0.1.7-rc.1` 起宿主按 peer 范围决定插件能不能加载，没被点名的版本在导入任何模块之前就被整行禁用。
 
-### v0.3.2（产出物表面全量绑定，0.1.7-rc.2 恢复加载）
-
-- **产出物滑块覆盖 0.1.7 渲染的每一件产物**：工具详情卡片、事件行、diff 块、变更文件卡片、内联 `code` 磨砂，以及悬浮预览窗——它把卡片 portal 到 `<body>`，所以此前不归任何滑块管。
-- **代码卡片的头部横幅恢复跟随主题**，不再是一块无视滑块的近白条。
-- **dsh-better-sidebar 的工作台改由产出物滑块接管**；面板行现在只代表宿主自己的右侧栏。
-- **一张产物卡片不再同时听两个滑块**：它的根节点改读产出物自己的原始层级令牌。
-- **输入框模糊回到 0 之后不再残留层叠上下文。**
-- **antd 的确认弹窗不再被当成设置面板**：它原先继承了设置表面色、磨砂与描边分组，因为旧选择器只认那三个 antd 同样会发出的 ARIA 属性。
-- **`0.1.7-rc.2` 恢复加载，其后的 0.1.x 一并放行**：`engines.dsh`、七个 `@deepseek-ai/dsh-*` peer 与 `dsh.compatibility` 都以 `|| 0.1.7-rc.2 || >=0.1.7-alpha.1 <0.2.0-alpha.0` 收尾——只写 `>=0.1.7` 一个预发布构建都匹配不到。
-
 ## 安装
 
 ### 方式一：npm 安装（推荐）
@@ -151,14 +151,14 @@ pnpm dsh web
 
 ## 兼容性
 
-- **[`dsh web`](https://github.com/deepseek-ai/deepseek-harness) 0.1.5-rc.2 ~ &lt;0.2.0，外加 `0.2.0-rc.1`** — `engines.dsh`、七个 `@deepseek-ai/dsh-*` 的 `peerDependencies` 与 `dsh.compatibility.dsh` 先逐一列出本插件核对过的 `0.1.5-rc` 与 `0.1.6-alpha` 各构建，再以 `>=0.1.7-alpha.1 <0.2.0-alpha.0` 收尾让 0.1.7 全线加载，最后单独写上 `0.2.0-rc.1`——总括刻意停在 0.2.0 之前，因为没比对过的 0.2.0 构建就是另一个宿主，它的事实要由它自己的目录来写。`0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1` 以逐包比对 tag 核对，它们之前的构建是实测过的。从 `0.1.7-rc.1` 起宿主自己强制这份 peer 列表——范围没写到的版本会在模块被导入之前整个禁用——所以列不列决定插件能不能跑，它不是写给人看的说明；`dsh.compatibility.dshReleases` 里则记录哪些构建真的核对过。同一道门禁也解释了为什么已经在 0.2.0 上的机器需要插件发版（或手工授予精确版本豁免）**并**重启宿主：检查发生在 profile 组装时，而不是插件更新时。宿主版本在运行时由 Node 半侧解析，依赖特定宿主版本渠道的功能（右侧栏面板模糊、官方侧栏「主题」卡片）只在对应宿主结构存在时启用，其余功能在整个范围内表现一致。
-- **版本适配隔离**：release 由 Node 半侧从进程自身那份 `@deepseek-ai/dsh/package.json` 读出（客户端上下文不暴露版本；`ctx.profileContext.installAnchor` 指不到时退回启动器的磁盘布局），经 `read` RPC 下发后只由前置适配层路由——`src/host-compat/` 负责探测与渠道归类，`src/client/host-compat/versions/` 下**每个版本一个目录**（`v0-1-5-rc-2-3` / `v0-1-6-alpha-1-2` / `v0-1-7-alpha-1-2-rc-1` / `v0-1-7-rc-2` / `v0-2-0-rc-1` / `unknown`），各自描述该版本的面板力学、头部槽位键、插件页形状，以及菜单的底色与磨砂落在哪一层。底码只向适配层提问（引导页表面归谁、模糊挂在哪一层、菜单该重写哪些令牌），不比较版本字符串。同一补丁行内的其它构建（`0.1.6-alpha.4` 之于核对基准 `0.1.6-alpha.2`）用该行的档位；整条补丁行都不在已核对范围内才收边取最近的一档并写日志。只有解析不到 release 时归入 `unknown`，回退到按 DOM 形状探测（`:has()` 双臂）而不是猜一个版本；适配新宿主 = 新增一个版本目录并在注册表登记。
+- **[`dsh web`](https://github.com/deepseek-ai/deepseek-harness) 0.1.5-rc.2 ~ `0.2.1-alpha.1`，其上所有版本一并放行** — `engines.dsh`、六个受门禁的 `@deepseek-ai/dsh-*` 的 `peerDependencies` 与 `dsh.compatibility.dsh` 先逐一列出本插件核对过的 `0.1.5-rc` 与 `0.1.6-alpha` 各构建——总括从它们之上开始，所以这些必须写全——继续点名此后逐个 diff 过的版本（`0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1`、`0.2.0-rc.2`、`0.2.1-alpha.1`）作为记录，最后以不设上界的 `>=0.1.7-alpha.1` 收尾，让 0.1.7、0.2 及其后的每一个 release 都能加载。不设上界是有意选的：从 `0.1.7-rc.1` 起宿主强制的正是这份 peer 列表——范围没写到的版本会在导入任何模块之前被整行禁用——一条写到头的范围等于在一款还能正常工作的插件前面砌墙。没见过的 release 会取最近的一份事实，并在日志里写清它离 `exact` 有多远；一份过期事实最坏的代价是某个滑块不再淡出宿主已经搬走的那个表面，而一道失败关闭的版本检查代价是整个插件。`dsh.compatibility.dshReleases` 记录哪些构建核对过、怎么核对的：`0.1.7-rc.1` / `0.1.7-rc.2`、`0.2.0-rc.1` / `0.2.0-rc.2` 与 `0.2.1-alpha.1` 以逐包比对 tag 核对，它们之前的构建是实测过的。这道门禁也意味着安装或更新插件后仍需重启 `dsh web`——检查发生在 profile 组装时，而不是插件更新时——但不设上界的总括，正让已经升到更新宿主的机器不再需要先等插件发版（或手工授予精确版本豁免 `dsh plugin allow-version`）。宿主版本在运行时由 Node 半侧解析，依赖特定宿主版本渠道的功能（右侧栏面板模糊、官方侧栏「主题」卡片）只在对应宿主结构存在时启用，其余功能在整个范围内表现一致。
+- **版本适配隔离**：release 由 Node 半侧从进程自身那份 `@deepseek-ai/dsh/package.json` 读出（客户端上下文不暴露版本；`ctx.profileContext.installAnchor` 指不到时退回启动器的磁盘布局），经 `read` RPC 下发后只由前置适配层路由——`src/host-compat/` 负责探测与渠道归类，`src/client/host-compat/versions/` 下**每个事实集合一个目录**（`v0-1-5-rc-2-3` / `v0-1-6-alpha-1-2` / `v0-1-7-alpha-1-2-rc-1` / `v0-1-7-rc-2` / `v0-2-0-rc-1` / `v0-2-0-rc-2` / `v0-2-1-alpha-1` / `unknown`），各自描述该版本的面板力学、头部槽位键、插件页形状，以及菜单的底色与磨砂落在哪一层。目录按它覆盖的事实命名，不按版本号的形状：`0.2.0-rc.1` 与 `0.2.0-rc.2` 同属一个预发布渠道，但 rc.2 改了吸顶菜单分组标题取色的令牌，于是这条补丁行上并着两个目录，较新的那个按开启它的那个构建命名。底码只向适配层提问（引导页表面归谁、模糊挂在哪一层、菜单该重写哪些令牌），不比较版本字符串。同一补丁行内的其它构建（`0.1.6-alpha.4` 之于核对基准 `0.1.6-alpha.2`）用该行的档位；整条补丁行都不在已核对范围内才收边取最近的一档并写日志——`0.2.1-alpha.1` 之上的每一个 release 如今就是靠这一档加载的。只有解析不到 release 时归入 `unknown`，回退到按 DOM 形状探测（`:has()` 双臂）而不是猜一个版本；适配新宿主 = 新增一个版本目录并在注册表登记。
 - **[DSHA](https://github.com/DSH-APP/DSHA)** — DeepSeek Harness 安卓启动器（免 ROOT、免 Termux）。其包内 dsh 为 `0.1.5-rc.2`，落在兼容范围内；移动端界面由 `dsh-web-mobile` 提供。
 - **[deepseek-harness-desktop](https://github.com/anywhere-labs/deepseek-harness-desktop)** — 支持
 
 ## 权限、副作用与边界
 
-- **接入形态**：官方 Profile Bundle——`package.json` 声明 `dsh.bundle.patch: ./cordis.patch.yml`（loader 插入层），仓库提交可直接使用的预构建运行时制品（`lib/index.js`、`lib/invariant.js`、`lib/client.js`），无安装脚本、无 postinstall、无 native 二进制、安装时不执行任何构建。
+- **接入形态**：官方 Profile Bundle——`package.json` 声明 `dsh.bundle.patch: ./cordis.patch.yml`（loader 插入层），仓库提交可直接使用的预构建运行时制品（`lib/index.js`、`lib/client.js`），无安装脚本、无 postinstall、无 native 二进制、安装时不执行任何构建。
 - **文件系统**：服务端仅在 `<dsh 主目录>/.dsh-any-background-data/` 内读写（配置 JSON、壁纸、轮换池、视频、字体），不触碰该目录之外的任何路径；配置写入为原子写（临时文件 + rename）。这些文件落在真实磁盘上，**不受 generation 恢复影响，也不会被其回滚**——清除它们即彻底重置插件。
 - **网络**：仅在用户主动粘贴 http/https 图片或视频网址并点击「应用」时发起一次出站请求下载该资源；除此之外无遥测、无外部服务调用。
 - **Shell / native**：无。不使用 `child_process`、不加载 native 模块、不运行动态下载的二进制。

package/lib/client.js

@@ -999,7 +999,9 @@ window.__ModuleLoader__.load({
 		*  a row then reports `exact` instead of `line`, and no new folder appears.
 		*  Rows may ALSO share a patch line while carrying different channels, which is
 		*  how a line says "the facts changed halfway through it" (`0.1.7-alpha.2` and
-		*  `0.1.7-rc.1` speak for `0.1.7-alpha`, `0.1.7-rc.2` opens `0.1.7-rc`).
+		*  `0.1.7-rc.1` speak for `0.1.7-alpha`, `0.1.7-rc.2` opens `0.1.7-rc`, and
+		*  `0.2.0-rc.2` opens a second answer on a line that had one — see the note on
+		*  `HostChannel` for why that row is keyed to the build).
 		*  Adding an ADAPTER means adding a channel plus a folder in
 		*  `client/host-compat/versions/`. */
 		const SUPPORTED_RELEASES = [
@@ -1026,6 +1028,14 @@ window.__ModuleLoader__.load({
 			{
 				channel: "0.2.0-rc",
 				release: "0.2.0-rc.1"
+			},
+			{
+				channel: "0.2.0-rc.2",
+				release: "0.2.0-rc.2"
+			},
+			{
+				channel: "0.2.1-alpha",
+				release: "0.2.1-alpha.1"
 			}
 		];
 		const UNKNOWN_HOST_INFO = {
@@ -1148,6 +1158,23 @@ window.__ModuleLoader__.load({
 		*  PRODUCED slider (0.3.2): a conversation artifact that happens to open in a
 		*  panel, not a page column — so it fades and frosts with the produced surfaces. */
 		const BETTER_SIDEBAR_PANEL = "[data-dsh-bottom-panel]";
+		/** The cards that take the composer seat away from the input bar: approval
+		*  (`ui-approval`), plan review and the question composer (`ui-user-questions`).
+		*  They are siblings of `[data-composer-card]`, not its children — the seat
+		*  renders the elected takeover beside the fallback bar (verified per tag in
+		*  `ConversationContent.tsx` and both packages' `slots.inject('conversation.composer')`)
+		*  — and each paints the capsule's own `--dsw-specific-input-major`, from
+		*  `dsh-v0.1.5-rc.2` through `dsh-v0.2.1-alpha.1`.
+		*
+		*  The marker sits on the wrapper, the fill on its child card:
+		*  `[data-approval-key] > div`, `[data-plan-review-key] > section`,
+		*  `[data-question-key] > section`. */
+		const COMPOSER_TAKEOVER_CARD = "[data-approval-key]>div,[data-plan-review-key]>section,[data-question-key]>section";
+		/** The takeover cards' free-text answer field — only the question composer has
+		*  one (approval and plan review are button rows). Form controls do not inherit
+		*  text properties, so the stroke group needs the editor spelled out; appending
+		*  a suffix to `COMPOSER_TAKEOVER_CARD` would bind to its LAST arm only. */
+		const COMPOSER_TAKEOVER_EDITOR = "[data-question-key]>section textarea";
 		/** Every surface the panel opacity slider owns — the host's own right Sidebar.
 		*  Layout-neutral token re-scope. (The dsh-better-sidebar workbench used to be
 		*  listed here; it moved to the produced group, see `PRODUCED_RULE`.) */
@@ -1254,6 +1281,23 @@ window.__ModuleLoader__.load({
 		*   `ScheduleCatalogAction`, the subagent lineage, `TeamAction`, `CordisPanel`,
 		*   `MenuSurface` itself) — re-declaring the token reaches the frost whoever ends up
 		*   applying it, and does not depend on any element being the painting element.
+		*
+		* `dsh-v0.2.0-rc.2` (npm `latest`) and `dsh-v0.2.1-alpha.1`: the layer and the frost
+		*   are the same files — `MenuSurface.tsx` and `MenuSurface.module.css` are
+		*   byte-identical to rc.1, and every `--dsw-menu-backdrop-filter` consumer is too —
+		*   but the sticky GROUP HEADING inside those menus changed owner. Through rc.1 the
+		*   only grouped menu was `ModelSelect`, whose own stylesheet painted that heading
+		*   from the menu token (`ModelSelect.module.css` `.groupTitle{position:sticky;
+		*   background:var(--dsw-specific-menu)}`), so the card slider drove it and a picked
+		*   wallpaper color tinted it. At rc.2 the rule is deleted and both grouped popups
+		*   (`ModelSelect`, `PopupSelectView`) render the new `ui-primitives/MenuGroup.tsx`,
+		*   whose heading stays transparent until `data-stuck` and then paints
+		*   `--dsw-alias-menu-group-header-fill` (light `rgba(248,249,250,.94)`, dark
+		*   `rgba(48,49,54,.94)`, declared in the `body` blocks of `design-platform.css`).
+		*   The surface did not go away — its token was RENAMED, and `ModelSelect.module.css`
+		*   is the one `--dsw-specific-menu` consumer that disappears at rc.2. Left alone, it
+		*   is the single menu element the fade no longer reaches: an untinted, near-opaque
+		*   band sitting on top of every row in the list the moment that list scrolls.
 		*/
 		/** The answer for the releases whose menus paint themselves: `0.1.5-rc`,
 		*  `0.1.6-alpha`, `0.1.7-alpha`. The unresolved bucket is its own variant below. */
@@ -1272,6 +1316,28 @@ window.__ModuleLoader__.load({
 			fillTokens: [MENU_FILL_TOKEN, "--dsw-menu-surface-fill"],
 			frostDecl: (value) => `--dsw-menu-backdrop-filter:${value}`
 		};
+		/** The fill the sticky group heading of a shared menu paints from — `MenuGroup`'s
+		*  own contribution to the menu's look, first emitted at `0.2.0-rc.2`. */
+		const MENU_GROUP_HEADER_FILL_TOKEN = "--dsw-alias-menu-group-header-fill";
+		/** The answer for `0.2.0-rc` from `0.2.0-rc.2` and for `0.2.1-alpha`: everything
+		*  `LAYERED_MENU_SURFACE` says, plus the heading `MenuGroup` renamed.
+		*
+		*  Riding `fillTokens` rather than being left out is a decision with evidence on
+		*  both sides, so state it: the host's README calls this token "independent of the
+		*  menu material" and gives it a 94% fill while the surface layer sits at 58%/45%.
+		*  That is a choice about an OPAQUE menu. This plugin's whole product is a menu the
+		*  wallpaper shows through, and one release earlier the very same heading read the
+		*  very same token as the card it sits on — so following it keeps rc.1's contract
+		*  ("the card slider owns every layer of a menu, in the picked color") instead of
+		*  leaving an untinted stock band inside a tinted, faded card.
+		*  Compositing is on its side too: the heading stacks on the surface layer it sticks
+		*  to, so a heading and a card at the same alpha still read as a band roughly
+		*  twice-as-dense as the card (1-(1-a)²) — occluding, at the slider's level, exactly
+		*  as it did when both came from one token. */
+		const LAYERED_MENU_SURFACE_WITH_GROUP_HEADER = {
+			fillTokens: [...LAYERED_MENU_SURFACE.fillTokens, MENU_GROUP_HEADER_FILL_TOKEN],
+			frostDecl: LAYERED_MENU_SURFACE.frostDecl
+		};
 		/** The answer when the release could not be resolved, and neither of the two
 		*  verified shapes can be asserted. Each half is chosen so that being on the
 		*  wrong line costs an inert declaration rather than a wrong pixel:
@@ -1294,7 +1360,7 @@ window.__ModuleLoader__.load({
 		};
 		/** Session-header slot anchors present on EVERY release in range. The slot
 		*  renderer stamps `data-slot="<key>"` unconditionally (`ui-renderer/scoped-slots.tsx`),
-		*  and all five keys are registered from 0.1.5-rc.2 through 0.2.0-rc.1 —
+		*  and all five keys are registered from 0.1.5-rc.2 through 0.2.1-alpha.1 —
 		*  verified per tag. Adapters append the keys their own release adds. */
 		const BASE_HEADER_SLOT_KEYS = [
 			"conversation.session.header",
@@ -1337,18 +1403,18 @@ window.__ModuleLoader__.load({
 		* @module
 		*/
 		/** The wrapper carries the slide transform on this line, so it carries the blur. */
-		function panelFragments$5() {
+		function panelFragments$7() {
 			return {
 				promotion: `${PANEL_WRAPPER}{position:fixed!important;z-index:26!important}${PANEL_FULLSCREEN}{z-index:40!important}`,
 				blur: panelBlurRule(PANEL_WRAPPER)
 			};
 		}
-		function createAdapter$5(host) {
+		function createAdapter$7(host) {
 			return {
 				id: "0.1.5-rc.2/rc.3",
 				channel: "0.1.5-rc",
 				host,
-				panelFragments: panelFragments$5,
+				panelFragments: panelFragments$7,
 				pluginPageRule: "",
 				menus: LEGACY_MENU_SURFACE,
 				surface: {
@@ -1418,18 +1484,18 @@ window.__ModuleLoader__.load({
 			const m = /^alpha\.(\d+)$/.exec(pre);
 			return m === null || Number(m[1]) >= 2;
 		}
-		function panelFragments$4() {
+		function panelFragments$6() {
 			return {
 				promotion: `${PANEL_WRAPPER}{position:fixed!important;z-index:26!important}${PANEL_FULLSCREEN}{z-index:40!important}`,
 				blur: panelBlurRule(PANEL_WRAPPER)
 			};
 		}
-		function createAdapter$4(host) {
+		function createAdapter$6(host) {
 			return {
 				id: "0.1.6-alpha.1/alpha.2",
 				channel: "0.1.6-alpha",
 				host,
-				panelFragments: panelFragments$4,
+				panelFragments: panelFragments$6,
 				pluginPageRule: hasPluginManagerPage(host.version) ? PLUGIN_PAGE_FROST_RULE : "",
 				menus: LEGACY_MENU_SURFACE,
 				surface: {
@@ -1514,18 +1580,18 @@ window.__ModuleLoader__.load({
 		*
 		* @module
 		*/
-		function panelFragments$3() {
+		function panelFragments$5() {
 			return {
 				promotion: "",
 				blur: panelBlurRule(DOCKKIT_SLIDERS)
 			};
 		}
-		function createAdapter$3(host) {
+		function createAdapter$5(host) {
 			return {
 				id: "0.1.7-alpha.1/alpha.2/rc.1",
 				channel: "0.1.7-alpha",
 				host,
-				panelFragments: panelFragments$3,
+				panelFragments: panelFragments$5,
 				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
 				menus: LEGACY_MENU_SURFACE,
 				surface: {
@@ -1584,18 +1650,18 @@ window.__ModuleLoader__.load({
 		*
 		* @module
 		*/
-		function panelFragments$2() {
+		function panelFragments$4() {
 			return {
 				promotion: "",
 				blur: panelBlurRule(DOCKKIT_SLIDERS)
 			};
 		}
-		function createAdapter$2(host) {
+		function createAdapter$4(host) {
 			return {
 				id: "0.1.7-rc.2",
 				channel: "0.1.7-rc",
 				host,
-				panelFragments: panelFragments$2,
+				panelFragments: panelFragments$4,
 				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
 				menus: LAYERED_MENU_SURFACE,
 				surface: {
@@ -1658,18 +1724,18 @@ window.__ModuleLoader__.load({
 		*
 		* @module
 		*/
-		function panelFragments$1() {
+		function panelFragments$3() {
 			return {
 				promotion: "",
 				blur: panelBlurRule(DOCKKIT_SLIDERS)
 			};
 		}
-		function createAdapter$1(host) {
+		function createAdapter$3(host) {
 			return {
 				id: "0.2.0-rc.1",
 				channel: "0.2.0-rc",
 				host,
-				panelFragments: panelFragments$1,
+				panelFragments: panelFragments$3,
 				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
 				menus: LAYERED_MENU_SURFACE,
 				surface: {
@@ -1679,6 +1745,144 @@ window.__ModuleLoader__.load({
 			};
 		}
 		//#endregion
+		//#region src/client/host-compat/versions/v0-2-0-rc-2/adapter.ts
+		/**
+		* Adapter for the DSH `0.2.0-rc` line from `0.2.0-rc.2` on, verified at `0.2.0-rc.2`.
+		*
+		* The first case where one patch line AND one prerelease channel carry two
+		* answers, so this folder opens a second channel (see the note on `HostChannel`).
+		* What it took was one renamed token, and it is a menu token, which is the class of
+		* fact this table exists for:
+		*
+		*   · `ui-primitives/src/MenuGroup.tsx` + `.module.css` are NEW at rc.2 and the
+		*     headings of both grouped popups (`ModelSelect`, `PopupSelectView`) now come
+		*     from them. `ModelSelect.module.css` loses `.groupTitle{background:var(
+		*     --dsw-specific-menu)}` in the same breath — the sticky heading's paint moved
+		*     to `--dsw-alias-menu-group-header-fill`, a token that does not exist before
+		*     this tag (`git grep` at `0.1.7-rc.2` and `0.2.0-rc.1`: absent). Hence
+		*     `LAYERED_MENU_SURFACE_WITH_GROUP_HEADER` rather than the rc.1 constant: the
+		*     old claim set stayed true, it just stopped covering one element.
+		*   · the rest of the menu layer is the same code — `MenuSurface.tsx` and
+		*     `MenuSurface.module.css` are byte-identical to `0.2.0-rc.1`, and so is every
+		*     consumer of `--dsw-menu-backdrop-filter`.
+		*
+		* Also verified at this tag, and NOT a reason for a folder of its own:
+		*   · `SidebarRight.module.css` and `ui-dockkit/src/components/TabLayout.tsx` are
+		*     unchanged, so the panel is still a stationary frame whose dockkit children
+		*     slide (`panelBlurRule(DOCKKIT_SLIDERS)`, no promotion).
+		*   · the five `conversation.session.header*` slot keys, and still no `…leading`.
+		*   · `PluginManagerPage.tsx` still emits `section[data-plugin-panel]` with the card
+		*     `ul` under `[data-plugin-scope]` and `[data-plugin-loading]`.
+		*   · `TextShimmer` keeps the rc.1 shape (`data-shimmer`), so the stroke exemption
+		*     stands as written.
+		*
+		* What moved that reached this plugin WITHOUT a version branch, because the host
+		* wrote it as a chain with a fallback:
+		*   · `TurnTriggerNodeView.module.css` now fills from
+		*     `var(--dsw-alias-turn-trigger-bg, var(--dsw-alias-markdown-code-block))` and
+		*     hovers with `var(--dsw-alias-turn-trigger-bg-hover, var(--dsw-alias-interactive-bg-hover))`,
+		*     both aliases declared in `design-platform.css` at this tag. The produced
+		*     slider's arm reads the SAME chain (see `PRODUCED_RULE`), so older hosts take
+		*     the fallback and this one takes the new alias — without any release test. That
+		*     matters here rather than being pedantry: dark mode repoints the alias at
+		*     `--dsw-alias-interactive-bg-hover`, so an arm still mixing on the code-block
+		*     token would keep overriding the row with the OLD color and the row would stop
+		*     tracking its own hover.
+		*
+		* @module
+		*/
+		function panelFragments$2() {
+			return {
+				promotion: "",
+				blur: panelBlurRule(DOCKKIT_SLIDERS)
+			};
+		}
+		function createAdapter$2(host) {
+			return {
+				id: "0.2.0-rc.2",
+				channel: "0.2.0-rc.2",
+				host,
+				panelFragments: panelFragments$2,
+				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
+				menus: LAYERED_MENU_SURFACE_WITH_GROUP_HEADER,
+				surface: {
+					ownsSidebarGuideSurface: true,
+					headerSlotKeys: BASE_HEADER_SLOT_KEYS
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/host-compat/versions/v0-2-1-alpha-1/adapter.ts
+		/**
+		* Adapter for the DSH `0.2.1-alpha` line, verified at `0.2.1-alpha.1`.
+		*
+		* A new MINOR line opened with a prerelease, and the answer is the `0.2.0-rc.2`
+		* folder's — which is a statement this file has to earn, because "same as the
+		* release before" is exactly the reasoning that went wrong when `0.1.7-rc.2` moved
+		* the menu paint. Read at the tag instead:
+		*   · `ui-theme/src/styles/design-platform.css` is BYTE-IDENTICAL to `0.2.0-rc.2`
+		*     (`git diff --numstat` empty), so every token this plugin writes — the menu
+		*     pair, the specific-menu alias, the turn-trigger chain — resolves to the same
+		*     values.
+		*   · `MenuGroup.tsx`, `MenuGroup.module.css`, `MenuSurface.tsx` and
+		*     `MenuSurface.module.css` are byte-identical too, and `MenuGroup` is still the
+		*     only consumer of `--dsw-alias-menu-group-header-fill`. That is why the menus
+		*     here answer with `LAYERED_MENU_SURFACE_WITH_GROUP_HEADER`, the same facts the
+		*     rc.2 folder checked, and not by re-typing them.
+		*   · `ui-sidebar-right/shell/SidebarRight.module.css` and
+		*     `ui-dockkit/src/components/TabLayout.tsx` unchanged (only `.tsx` service
+		*     wiring moved), so the panel stays a stationary frame with sliding dockkit
+		*     children and no promotion.
+		*   · the five `conversation.session.header*` slot keys, still no `…leading`.
+		*   · `PluginManagerPage.tsx` still emits the three anchors of the card list.
+		*   · `TextShimmer` still marks its root `data-shimmer`, so the stroke exemption
+		*     written for rc.1 stands.
+		*
+		* What did move, and why none of it needs a fact from this folder:
+		*
+		*  1. `ui-layout/AppFrame` gains a second grid row, `div.bottomRow[data-shell-bottom]`
+		*     holding the new `shell.bottom` slot, and it paints `--dsw-alias-bg-base` —
+		*     the main-background token, which `applyCustomTokensNow` already re-emits on
+		*     `body`, so the strip follows the main-bg slider with no new binding. The row
+		*     is `min-height:0` and empty unless a plugin fills the slot, so an untouched
+		*     install shows nothing. It also sits AFTER `RightbarColumn` in the frame's
+		*     children, which is the side `discoverParts()` does not count from: it anchors
+		*     on `data-rightbar-col` and reads `rightIdx-2` / `rightIdx-1`, so the sidebar
+		*     and center column are still the same two children.
+		*  2. `ui-primitives/InlineEditor.module.css` is the new home of the inline editor's
+		*     `.editor{background:var(--dsw-alias-bg-base)}`. Same token, so the same slider
+		*     reaches it wherever the component moved to.
+		*  3. `modules/system.ts` narrowed `claimStyles` to the tags a factory itself added
+		*     (see `ensureUiCss` for what that changed about our own sheet).
+		*  4. `@deepseek-ai/dsh-invariants` is DELETED at this tag — `git ls-tree` shows no
+		*     `packages/runtime-diagnostics/invariants`, and the boot/app plugin loader never
+		*     looked for a plugin's `invariant` export. This plugin's no-op companion was
+		*     therefore already dead weight here, and it goes rather than claiming a peer
+		*     version for a package the host no longer ships.
+		*
+		* @module
+		*/
+		function panelFragments$1() {
+			return {
+				promotion: "",
+				blur: panelBlurRule(DOCKKIT_SLIDERS)
+			};
+		}
+		function createAdapter$1(host) {
+			return {
+				id: "0.2.1-alpha.1",
+				channel: "0.2.1-alpha",
+				host,
+				panelFragments: panelFragments$1,
+				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
+				menus: LAYERED_MENU_SURFACE_WITH_GROUP_HEADER,
+				surface: {
+					ownsSidebarGuideSurface: true,
+					headerSlotKeys: BASE_HEADER_SLOT_KEYS
+				}
+			};
+		}
+		//#endregion
 		//#region src/client/host-compat/versions/unknown/adapter.ts
 		/**
 		* Stand-in for "we could not resolve the release".
@@ -1723,11 +1927,13 @@ window.__ModuleLoader__.load({
 		//#endregion
 		//#region src/client/host-compat/versions/registry.ts
 		const ADAPTERS = {
-			"0.1.5-rc": createAdapter$5,
-			"0.1.6-alpha": createAdapter$4,
-			"0.1.7-alpha": createAdapter$3,
-			"0.1.7-rc": createAdapter$2,
-			"0.2.0-rc": createAdapter$1,
+			"0.1.5-rc": createAdapter$7,
+			"0.1.6-alpha": createAdapter$6,
+			"0.1.7-alpha": createAdapter$5,
+			"0.1.7-rc": createAdapter$4,
+			"0.2.0-rc": createAdapter$3,
+			"0.2.0-rc.2": createAdapter$2,
+			"0.2.1-alpha": createAdapter$1,
 			unknown: createAdapter
 		};
 		/** Pick the adapter for a resolved host. `host.channel` is already narrowed to
@@ -3723,7 +3929,7 @@ window.__ModuleLoader__.load({
 		}
 		const INPUT_FROST_CLASS = "dab-input-frost";
 		function inputBlurRule() {
-			return `.${INPUT_FROST_CLASS} [data-composer-card]{position:relative;isolation:isolate}.${INPUT_FROST_CLASS} [data-composer-card]::before{content:"";position:absolute;inset:0;z-index:-1;pointer-events:none;border-radius:inherit;-webkit-backdrop-filter:var(--dsh-any-input-blur,none);backdrop-filter:var(--dsh-any-input-blur,none)}[data-cordis-panel]{-webkit-backdrop-filter:var(--dsh-any-input-blur,none);backdrop-filter:var(--dsh-any-input-blur,none)}[data-cordis-panel]{${menuFillDecls("var(--dsh-any-op-menu-cordis)!important")}}`;
+			return `.${INPUT_FROST_CLASS} [data-composer-card]{position:relative;isolation:isolate}.${INPUT_FROST_CLASS} [data-composer-card]::before{content:"";position:absolute;inset:0;z-index:-1;pointer-events:none;border-radius:inherit;-webkit-backdrop-filter:var(--dsh-any-input-blur,none);backdrop-filter:var(--dsh-any-input-blur,none)}.${INPUT_FROST_CLASS} ${COMPOSER_TAKEOVER_CARD}{position:relative;isolation:isolate}.${INPUT_FROST_CLASS} ${COMPOSER_TAKEOVER_CARD}::before{content:"";position:absolute;inset:0;z-index:-1;pointer-events:none;border-radius:inherit;-webkit-backdrop-filter:var(--dsh-any-input-blur,none);backdrop-filter:var(--dsh-any-input-blur,none)}[data-cordis-panel]{-webkit-backdrop-filter:var(--dsh-any-input-blur,none);backdrop-filter:var(--dsh-any-input-blur,none)}[data-cordis-panel]{${menuFillDecls("var(--dsh-any-op-menu-cordis)!important")}}`;
 		}
 		function applyInputBlur(px) {
 			const root = document.documentElement;
@@ -3851,11 +4057,11 @@ window.__ModuleLoader__.load({
 			document.head.appendChild(exemptStyleEl);
 			return exemptStyleEl;
 		}
-		const PRODUCED_RULE = `[data-code-block-content] pre,[data-code-block-banner],[data-composer-chip],[data-changed-files],[data-terminal],[data-read],[data-diff],[data-context-injection-body],[data-search],[data-web],[class*="_ioCard"],[data-inspect],[data-turn-trigger],[style*="--dsh-hover-preview-fade"],:not(pre)>code{-webkit-backdrop-filter:var(--dsh-any-blur-prod,none);backdrop-filter:var(--dsh-any-blur-prod,none)}[data-markdown-variant="compact"] :not(pre)>code{-webkit-backdrop-filter:none;backdrop-filter:none}${BETTER_SIDEBAR_PANEL}{-webkit-backdrop-filter:var(--dsh-any-blur-prod,none);backdrop-filter:var(--dsh-any-blur-prod,none)}${BETTER_SIDEBAR_PANEL}{--dsw-alias-bg-base:var(--dsh-any-prod-panel-bg-base);--dsw-alias-bg-layer-1:var(--dsh-any-prod-panel-layer-1);--dsw-alias-bg-layer-2:var(--dsh-any-prod-panel-layer-2);--dsw-alias-bg-layer-3:var(--dsh-any-prod-panel-layer-3)}@supports (background:color-mix(in srgb,red 50%,transparent)){.md-code-block{background:transparent!important}.md-code-block>div{background-color:transparent!important}.md-code-block [data-code-block-content] pre{background-color:color-mix(in srgb,var(--dsl-code-block-background,var(--dsw-alias-markdown-code-block,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}.md-code-block [data-code-block-banner]{background-color:color-mix(in srgb,var(--dsl-code-block-banner-background-color,var(--dsw-alias-markdown-code-block-banner,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}[data-code-block-banner]{background-color:color-mix(in srgb,var(--dsl-code-block-banner-background-color,var(--dsl-code-block-background,var(--dsw-alias-markdown-code-block,transparent))) var(--dsh-any-prod-pct,100%),transparent)!important}[data-code-block-content]{--shiki-background:color-mix(in srgb,var(--dsw-alias-markdown-code-block,var(--dsl-code-block-background,transparent)) var(--dsh-any-prod-pct,100%),transparent)}:not(pre)>code{background-color:color-mix(in srgb,var(--dsw-alias-markdown-inline-code,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-composer-chip]>*{background-color:color-mix(in srgb,var(--dsw-alias-interactive-bg-hover,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-terminal]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-terminal] button{background-color:transparent!important}[data-read],[data-diff]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-read]>div:first-child:not([data-code-block-banner]),[data-diff]>div:first-child:not([data-code-block-banner]){background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block-banner,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-context-injection-body]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-inspect],[data-turn-trigger]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-turn-trigger]:hover{background-color:color-mix(in srgb,var(--dsw-alias-interactive-bg-hover,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-changed-files]{background-color:var(--dsh-any-prod-layer-1,var(--dsw-alias-bg-layer-1,transparent))!important}[data-changed-files]>button:first-child{background-color:color-mix(in srgb,var(--changes-fill,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-changed-files]>button:first-child:hover{background-color:color-mix(in srgb,var(--changes-hover,var(--changes-fill,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}[data-changed-files]>button:first-child>span:first-child{background-color:color-mix(in srgb,var(--changes-fill,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[style*="--dsh-hover-preview-fade"]{background-color:color-mix(in srgb,var(--dsw-hovercard-bg,#2c2c2e) var(--dsh-any-prod-pct,100%),transparent)!important}[style*="--dsh-hover-preview-fade"][class*="_preview"]{background-color:var(--dsh-any-prod-layer-1,var(--dsw-alias-bg-layer-1,transparent))!important}[data-search]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-web]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[class*="_ioCard"]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}}`;
+		const PRODUCED_RULE = `[data-code-block-content] pre,[data-code-block-banner],[data-composer-chip],[data-changed-files],[data-terminal],[data-read],[data-diff],[data-context-injection-body],[data-search],[data-web],[class*="_ioCard"],[data-inspect],[data-turn-trigger],[style*="--dsh-hover-preview-fade"],:not(pre)>code{-webkit-backdrop-filter:var(--dsh-any-blur-prod,none);backdrop-filter:var(--dsh-any-blur-prod,none)}[data-markdown-variant="compact"] :not(pre)>code{-webkit-backdrop-filter:none;backdrop-filter:none}${BETTER_SIDEBAR_PANEL}{-webkit-backdrop-filter:var(--dsh-any-blur-prod,none);backdrop-filter:var(--dsh-any-blur-prod,none)}${BETTER_SIDEBAR_PANEL}{--dsw-alias-bg-base:var(--dsh-any-prod-panel-bg-base);--dsw-alias-bg-layer-1:var(--dsh-any-prod-panel-layer-1);--dsw-alias-bg-layer-2:var(--dsh-any-prod-panel-layer-2);--dsw-alias-bg-layer-3:var(--dsh-any-prod-panel-layer-3)}@supports (background:color-mix(in srgb,red 50%,transparent)){.md-code-block{background:transparent!important}.md-code-block>div{background-color:transparent!important}.md-code-block [data-code-block-content] pre{background-color:color-mix(in srgb,var(--dsl-code-block-background,var(--dsw-alias-markdown-code-block,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}.md-code-block [data-code-block-banner]{background-color:color-mix(in srgb,var(--dsl-code-block-banner-background-color,var(--dsw-alias-markdown-code-block-banner,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}[data-code-block-banner]{background-color:color-mix(in srgb,var(--dsl-code-block-banner-background-color,var(--dsl-code-block-background,var(--dsw-alias-markdown-code-block,transparent))) var(--dsh-any-prod-pct,100%),transparent)!important}[data-code-block-content]{--shiki-background:color-mix(in srgb,var(--dsw-alias-markdown-code-block,var(--dsl-code-block-background,transparent)) var(--dsh-any-prod-pct,100%),transparent)}:not(pre)>code{background-color:color-mix(in srgb,var(--dsw-alias-markdown-inline-code,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-composer-chip]>*{background-color:color-mix(in srgb,var(--dsw-alias-interactive-bg-hover,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-terminal]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-terminal] button{background-color:transparent!important}[data-read],[data-diff]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-read]>div:first-child:not([data-code-block-banner]),[data-diff]>div:first-child:not([data-code-block-banner]){background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block-banner,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-context-injection-body]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-inspect]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-turn-trigger]{background-color:color-mix(in srgb,var(--dsw-alias-turn-trigger-bg,var(--dsw-alias-markdown-code-block,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}[data-turn-trigger]:hover{background-color:color-mix(in srgb,var(--dsw-alias-turn-trigger-bg-hover,var(--dsw-alias-interactive-bg-hover,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}[data-changed-files]{background-color:var(--dsh-any-prod-layer-1,var(--dsw-alias-bg-layer-1,transparent))!important}[data-changed-files]>button:first-child{background-color:color-mix(in srgb,var(--changes-fill,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-changed-files]>button:first-child:hover{background-color:color-mix(in srgb,var(--changes-hover,var(--changes-fill,transparent)) var(--dsh-any-prod-pct,100%),transparent)!important}[data-changed-files]>button:first-child>span:first-child{background-color:color-mix(in srgb,var(--changes-fill,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[style*="--dsh-hover-preview-fade"]{background-color:color-mix(in srgb,var(--dsw-hovercard-bg,#2c2c2e) var(--dsh-any-prod-pct,100%),transparent)!important}[style*="--dsh-hover-preview-fade"][class*="_preview"]{background-color:var(--dsh-any-prod-layer-1,var(--dsw-alias-bg-layer-1,transparent))!important}[data-search]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[data-web]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}[class*="_ioCard"]{background-color:color-mix(in srgb,var(--dsw-alias-markdown-code-block,transparent) var(--dsh-any-prod-pct,100%),transparent)!important}}`;
 		const STROKE_RULE = [
 			`${SETTINGS_PANEL_SEL}{-webkit-text-stroke:var(--dsh-any-stroke-settings-w,0px) var(--dsh-any-stroke-settings-c,transparent);paint-order:stroke fill}`,
 			"[role=\"menu\"]:not([data-dockkit-tab-menu]),[role=\"listbox\"],body>[role=\"tree\"],body>[role=\"dialog\"]:not([aria-modal=\"true\"]){-webkit-text-stroke:var(--dsh-any-stroke-card-w,0px) var(--dsh-any-stroke-card-c,transparent);paint-order:stroke fill}",
-			"[data-composer-card],[data-cordis-panel],[data-composer-card] textarea,[data-composer-card] input,[data-composer-card] [contenteditable],[data-cordis-panel] input,[data-cordis-panel] textarea{-webkit-text-stroke:var(--dsh-any-stroke-input-w,0px) var(--dsh-any-stroke-input-c,transparent);paint-order:stroke fill}",
+			`[data-composer-card],[data-cordis-panel],[data-composer-card] textarea,[data-composer-card] input,[data-composer-card] [contenteditable],[data-cordis-panel] input,[data-cordis-panel] textarea,${COMPOSER_TAKEOVER_CARD},${COMPOSER_TAKEOVER_EDITOR}{-webkit-text-stroke:var(--dsh-any-stroke-input-w,0px) var(--dsh-any-stroke-input-c,transparent);paint-order:stroke fill}`,
 			`[data-chat-flow]{-webkit-text-stroke:var(--dsh-any-stroke-chat-w,0px) var(--dsh-any-stroke-chat-c,transparent);paint-order:stroke fill}`,
 			`[data-conversation-composer-overlay]{-webkit-text-stroke:var(--dsh-any-stroke-trajectory-w,0px) var(--dsh-any-stroke-trajectory-c,transparent);paint-order:stroke fill}`,
 			`[data-code-block-content] pre,[data-code-block-content],[data-code-block-banner],[data-composer-chip],:not(pre)>code,[data-changed-files],[data-terminal],[data-read],[data-diff],[data-inspect],[data-turn-trigger],[data-context-injection-body],[data-search],[data-web],[class*="_ioCard"],[style*="--dsh-hover-preview-fade"],${BETTER_SIDEBAR_PANEL}{-webkit-text-stroke:var(--dsh-any-stroke-produced-w,0px) var(--dsh-any-stroke-produced-c,transparent);paint-order:stroke fill}`,
@@ -4078,7 +4284,7 @@ window.__ModuleLoader__.load({
 			if (px > 0) document.documentElement.style.setProperty("--dsh-any-blur-panel", `blur(${px}px)`);
 			else document.documentElement.style.removeProperty("--dsh-any-blur-panel");
 		}
-		const PLACEHOLDER_RULE = "[data-composer-card] textarea::placeholder,[data-composer-card] input::placeholder,[data-composer-card] [contenteditable]::placeholder,[data-cordis-panel] input::placeholder,[data-cordis-panel] textarea::placeholder,.dab-input::placeholder,.dab-input textarea::placeholder,.dab-input input::placeholder{color:var(--dsh-any-placeholder,var(--dsw-alias-label-caption,#8a8f98))!important;font-style:italic;opacity:.85}";
+		const PLACEHOLDER_RULE = `[data-composer-card] textarea::placeholder,[data-composer-card] input::placeholder,[data-composer-card] [contenteditable]::placeholder,[data-cordis-panel] input::placeholder,[data-cordis-panel] textarea::placeholder,${COMPOSER_TAKEOVER_EDITOR}::placeholder,.dab-input::placeholder,.dab-input textarea::placeholder,.dab-input input::placeholder{color:var(--dsh-any-placeholder,var(--dsw-alias-label-caption,#8a8f98))!important;font-style:italic;opacity:.85}`;
 		/** Re-scope one surface group's layer tokens onto plugin-owned variables so a
 		*  dedicated slider owns its alpha (the host has no per-surface opacity). The
 		*  settings group additionally retints its dialog surface variable. Always
@@ -5603,6 +5809,7 @@ window.__ModuleLoader__.load({
 			if (!el) {
 				el = document.createElement("style");
 				el.id = CSS_ID;
+				el.dataset.plugin = "dsh-any-background-ui-css";
 				document.head.appendChild(el);
 			}
 			if (el.textContent !== UI_CSS) el.textContent = UI_CSS;