dsh-any-background 0.3.2 → 0.3.3

package/lib/client.js

@@ -997,6 +997,9 @@ window.__ModuleLoader__.load({
 		*  were checked; several rows may share a `channel` when a newer build was
 		*  verified as needing no change to that folder's adapter (as `0.1.7-rc.1` was) —
 		*  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`).
 		*  Adding an ADAPTER means adding a channel plus a folder in
 		*  `client/host-compat/versions/`. */
 		const SUPPORTED_RELEASES = [
@@ -1015,6 +1018,14 @@ window.__ModuleLoader__.load({
 			{
 				channel: "0.1.7-alpha",
 				release: "0.1.7-rc.1"
+			},
+			{
+				channel: "0.1.7-rc",
+				release: "0.1.7-rc.2"
+			},
+			{
+				channel: "0.2.0-rc",
+				release: "0.2.0-rc.1"
 			}
 		];
 		const UNKNOWN_HOST_INFO = {
@@ -1127,37 +1138,6 @@ window.__ModuleLoader__.load({
 		}
 		//#endregion
 		//#region src/client/host-compat/versions/shared.ts
-		/**
-		* Selector + declaration vocabulary shared by every per-version adapter.
-		*
-		* These are the ANCHORS, not the decisions. What varies between releases (which
-		* element slides, whether the panel needs promoting, which header slot keys
-		* exist) is answered in the version folders; what is stable across all of them
-		* lives here so no adapter has to re-type a host selector and get it subtly wrong.
-		*
-		* Verified against the harness release tags (dsh-v0.1.5-rc.2 … dsh-v0.1.7-rc.1),
-		* not inferred:
-		*   · `[data-sidebar-right-panel]` — emitted by `ui-sidebar-right/shell/SidebarRight.tsx`
-		*     on every release in range, with values `push` | `fullscreen`.
-		*   · `[data-dockkit-host]` / `[data-dockkit-empty]` — emitted ONLY by
-		*     `ui-dockkit/components/TabLayout.tsx`, a file that first appears at
-		*     0.1.7-alpha.1. Dockkit itself EXISTS earlier (its `TabMenu` carries
-		*     `[data-dockkit-tab-menu]` on every release), so only these two attributes
-		*     are the 0.1.7 marker — never test "is dockkit installed".
-		*   · `[data-dsh-bottom-panel]` — the optional dsh-better-sidebar workbench, not
-		*     a host element at all. It is a single element on every release, which is
-		*     why it needs no version arm.
-		*   · `[data-plugin-panel]` / `[data-plugin-scope] > ul` — emitted by
-		*     `ui-plugin-manager/src/client/PluginManagerPage.tsx`. That package is NEW AT
-		*     0.1.6-alpha.2: `git ls-tree` shows it absent from 0.1.5-rc.2, 0.1.5-rc.3 and
-		*     0.1.6-alpha.1, where the plugin list lived in `ui-settings-plugin-inventory`
-		*     under `[data-plugin-scope]` alone — no `[data-plugin-panel]`, and no card
-		*     `ul` in that group either. From alpha.2 on, the group markup (`section` →
-		*     `div.groupHead` + `ul.cards`) is byte-identical through 0.1.7-rc.1, so the
-		*     ONE rule below serves all four tags that emit the page.
-		*
-		* @module
-		*/
 		/** The host's own right Sidebar wrapper. */
 		const PANEL_WRAPPER = "[data-sidebar-right-panel]";
 		/** The same wrapper in its fullscreen state; the host raises its own z-index to 40. */
@@ -1192,10 +1172,19 @@ window.__ModuleLoader__.load({
 		* Which releases emit the page decides who gets this string — see `pluginPageRule`
 		* in each version folder.
 		*
+		* The card `ul` is matched through TWO scopes. `0.2.0-rc.1` added a first-read
+		* `ListSkeleton` that reuses `.cards` under `section[data-plugin-loading]`, so a
+		* rule keyed on `[data-plugin-scope]` alone would show the real list frosted and
+		* the loading list bare, then re-frost the block when the data lands. Hosts before
+		* that never emit the attribute, so the extra selector is inert rather than a
+		* version branch.
+		*
 		* BINDING, and why it is not just "put it in the dialog": the block paints from
 		* `--dsh-any-bg-settings-surface` and frosts from `--dsh-any-blur-settings`, i.e.
 		* the settings-opacity / settings-blur pair. On 0.1.7 the page is a child of
-		* `centerCol`, NOT of the settings dialog, so `SETTINGS_STYLE_RULE`'s token
+		* `centerCol`, NOT of the settings dialog (and from `0.1.7-rc.2` the dialog is a
+		* `createPortal` beside `#root`, so it is further away still), therefore
+		* `SETTINGS_STYLE_RULE`'s token
 		* re-scope never reaches it and the list would otherwise follow the homepage card
 		* alpha; reading the plugin-owned variables off `:root` puts them under the slider
 		* that owns this page. The `var(--dsw-alias-bg-layer-2)` fallback covers the window
@@ -1208,10 +1197,104 @@ window.__ModuleLoader__.load({
 		* carries a `plugins.item` slot that third-party plugins fill with their own
 		* controls, so a dialog can legitimately open inside the list.
 		*/
-		const PLUGIN_PAGE_FROST_RULE = "[data-plugin-panel] [data-plugin-scope]>ul{position:relative;isolation:isolate;padding:8px;border-radius:14px}[data-plugin-panel] [data-plugin-scope]>ul:has([role=\"dialog\"]){isolation:auto}[data-plugin-panel] [data-plugin-scope]>ul::before{content:\"\";position:absolute;inset:0;z-index:-1;pointer-events:none;border-radius:inherit;background:var(--dsh-any-bg-settings-surface,var(--dsw-alias-bg-layer-2));-webkit-backdrop-filter:var(--dsh-any-blur-settings,none);backdrop-filter:var(--dsh-any-blur-settings,none)}";
+		const PLUGIN_PAGE_FROST_RULE = "[data-plugin-panel] [data-plugin-scope]>ul,[data-plugin-panel] [data-plugin-loading]>ul{position:relative;isolation:isolate;padding:8px;border-radius:14px}[data-plugin-panel] [data-plugin-scope]>ul:has([role=\"dialog\"]),[data-plugin-panel] [data-plugin-loading]>ul:has([role=\"dialog\"]){isolation:auto}[data-plugin-panel] [data-plugin-scope]>ul::before,[data-plugin-panel] [data-plugin-loading]>ul::before{content:\"\";position:absolute;inset:0;z-index:-1;pointer-events:none;border-radius:inherit;background:var(--dsh-any-bg-settings-surface,var(--dsw-alias-bg-layer-2));-webkit-backdrop-filter:var(--dsh-any-blur-settings,none);backdrop-filter:var(--dsh-any-blur-settings,none)}";
+		/** The host's own `ui-theme` name for "dropdowns, popovers, suggestion lists", and
+		*  the token the plugin has always remapped onto the card slider. Whether it still
+		*  reaches a menu's paint is the question `MenuSurfaceFacts` below answers — from
+		*  `0.1.7-rc.2` the host aliases it AWAY from the menu layer, so declaring it alone
+		*  fades the non-`MenuSurface` overlays and nothing else. */
+		const MENU_FILL_TOKEN = "--dsw-specific-menu";
+		/** Frost by filtering the element itself — the only option where the element is the
+		*  thing that paints, and the shape every release up to `0.1.7-rc.1` presents. Both
+		*  prefixes because Safari needs the `-webkit-` one and the cascade must not let
+		*  them disagree. */
+		function elementFrostDecl(value) {
+			return `-webkit-backdrop-filter:${value};backdrop-filter:${value}`;
+		}
+		/**
+		* ── Where a menu's paint lives ────────────────────────────────────────────────
+		* Verified by reading the emitting source at each tag, not inferred from a changelog.
+		*
+		* `dsh-v0.1.5-rc.2` … `dsh-v0.1.7-rc.1`: the menu ELEMENT paints itself. Its own
+		*   CSS module declares `background:var(--dsw-specific-menu)` — 11 files at
+		*   0.1.5-rc.2/rc.3 and 0.1.6-alpha.1/alpha.2, 15 at 0.1.7-alpha.1/alpha.2, 16 at
+		*   rc.1 (`Menu`, `MenuView`, `PopupSelectView`, `ModelSelect`, `dockkit` TabMenu,
+		*   `stat-dialog`, `QueueDock`, `ContextMeter`, `TodoPanel`, `GoalBar`,
+		*   `JobListAction`, `HoverCard`, `ScheduleCatalogAction`, `SubagentHeaderLineage`,
+		*   `TeamAction`, `CordisPanel`). One token therefore paints every menu, and
+		*   filtering the element is the arm that reaches it.
+		*   Frost is a separate, later fact, and worth recording because it changes what
+		*   the plugin is doing on the older tags: `--dsw-menu-backdrop-filter` has ZERO
+		*   consumers before `0.1.7-alpha.1` (15 there, 16 at rc.1). On `0.1.5`/`0.1.6` the
+		*   host frosts no menu at all, so the card/header blur sliders are the only reason
+		*   a menu has a frost there — which is why the declaration goes on the element
+		*   rather than into a host token the host does not read.
+		*
+		* `dsh-v0.1.7-rc.2` (npm `latest`) and `dsh-v0.2.0-rc.1`: `TabMenu`, `MenuView`,
+		*   `PopupSelectView`, `ModelSelect` and `Menu` all render through the new
+		*   `ui-primitives/src/MenuSurface.tsx` (byte-identical between the two tags),
+		*   which leaves the element unpainted and draws on a `z-index:-1` child instead
+		*   (`MenuSurface.module.css` `.material`: `background:var(--dsw-menu-surface-fill)`
+		*   + `backdrop-filter:var(--dsw-menu-backdrop-filter)`). The four menu stylesheets
+		*   that used to paint the old token (Menu/MenuView/PopupSelectView/dockkit TabMenu)
+		*   drop it at rc.2, which is why the painter count goes 16 → 14.
+		*   Two consequences, both measured from those files:
+		*     · the host FLIPPED ITS ALIAS — `design-platform.css` now declares
+		*       `--dsw-specific-menu:var(--dsw-menu-surface-fill)` where every earlier
+		*       release declared the reverse. So a plugin that retints only the old token
+		*       writes a value nothing on a menu any longer reads, and the card / header
+		*       opacity sliders go inert on exactly the surfaces they were built for.
+		*     · that child layer exists on purpose: its comment says filtering only the
+		*       background "keeps nested menus and fixed overlays free of an ancestor
+		*       backdrop root", and the surface sets `isolation:isolate`. Filtering the
+		*       element anyway installs the backdrop root the layer was written to avoid.
+		*   The frost therefore rides `--dsw-menu-backdrop-filter`, whose consumer set is
+		*   the same 14 stylesheets at both tags (stat dialog, queue dock, context meter,
+		*   todo panel, goal bar, job list, `HoverCard`, `PickerPopover`/`TaskMenu`/
+		*   `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.
+		*/
+		/** 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. */
+		const LEGACY_MENU_SURFACE = {
+			fillTokens: [MENU_FILL_TOKEN],
+			frostDecl: elementFrostDecl
+		};
+		/** The answer for `0.1.7-rc` (`0.1.7-rc.2` onward) and `0.2.0-rc`. The old token
+		*  stays in the list on purpose: 14 surfaces in the same claim set still paint their
+		*  fill from it — the lineage tree, `CordisPanel`, the stat dialog, `QueueDock`,
+		*  `TodoPanel`, `ContextMeter`, `GoalBar`, `JobListAction`, `HoverCard`, `TeamAction`,
+		*  `ModelSelect`'s own card and the schedule trio (`PickerPopover`, `TaskMenu`,
+		*  `ScheduleCatalogAction`) — while the shared menus moved to
+		*  `--dsw-menu-surface-fill`. Dropping either name fades one half of that set. */
+		const LAYERED_MENU_SURFACE = {
+			fillTokens: [MENU_FILL_TOKEN, "--dsw-menu-surface-fill"],
+			frostDecl: (value) => `--dsw-menu-backdrop-filter:${value}`
+		};
+		/** 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:
+		*    · BOTH fill tokens. A custom property nothing reads costs nothing, so this
+		*      half always lands: the fade reaches a self-painting menu through the old
+		*      token and a `MenuSurface` layer through the new one.
+		*    · the ELEMENT's frost, and not the host's blur token, because on `0.1.5` and
+		*      `0.1.6` `--dsw-menu-backdrop-filter` has no consumer at all (verified: zero
+		*      files before 0.1.7-alpha.1) — the token arm would leave those hosts with no
+		*      menu frost whatsoever, while filtering the element frosts every release.
+		*      On a `MenuSurface` host it does not stack: the surface root IS the element
+		*      that carries `role="menu"`, so our filter makes it a backdrop root, and the
+		*      `z-index:-1` layer inside it then has only the (unpainted) surface to sample
+		*      and its own default `blur(40px)` becomes inert. One frost — ours — plus a
+		*      `position:relative` element that hosts nested menus the way the layer was
+		*      written not to. Accepted for a bucket that by definition cannot know. */
+		const UNRESOLVED_MENU_SURFACE = {
+			fillTokens: LAYERED_MENU_SURFACE.fillTokens,
+			frostDecl: elementFrostDecl
+		};
 		/** 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.1.7-rc.1 —
+		*  and all five keys are registered from 0.1.5-rc.2 through 0.2.0-rc.1 —
 		*  verified per tag. Adapters append the keys their own release adds. */
 		const BASE_HEADER_SLOT_KEYS = [
 			"conversation.session.header",
@@ -1243,22 +1326,31 @@ window.__ModuleLoader__.load({
 		* an animated track with its own stacking context, it must be promoted out of it
 		* or the filter has no wallpaper to sample.
 		*
+		* Menus paint themselves here: 11 stylesheets declare
+		* `background:var(--dsw-specific-menu)` on the element (`Menu`, `MenuView`,
+		* `PopupSelectView`, `stat-dialog`, `ModelSelect`, `JobListAction`, `ContextMeter`,
+		* `ScheduleCatalogAction`, `SubagentHeaderLineage`, `TeamAction`, `CordisPanel`),
+		* and `--dsw-menu-backdrop-filter`
+		* has NO consumer on this line at all — the host frosts no menu, so the element is
+		* both the paint and the only place a frost can go. Hence `LEGACY_MENU_SURFACE`.
+		*
 		* @module
 		*/
 		/** The wrapper carries the slide transform on this line, so it carries the blur. */
-		function panelFragments$3() {
+		function panelFragments$5() {
 			return {
 				promotion: `${PANEL_WRAPPER}{position:fixed!important;z-index:26!important}${PANEL_FULLSCREEN}{z-index:40!important}`,
 				blur: panelBlurRule(PANEL_WRAPPER)
 			};
 		}
-		function createAdapter$3(host) {
+		function createAdapter$5(host) {
 			return {
 				id: "0.1.5-rc.2/rc.3",
 				channel: "0.1.5-rc",
 				host,
-				panelFragments: panelFragments$3,
+				panelFragments: panelFragments$5,
 				pluginPageRule: "",
+				menus: LEGACY_MENU_SURFACE,
 				surface: {
 					ownsSidebarGuideSurface: false,
 					headerSlotKeys: BASE_HEADER_SLOT_KEYS
@@ -1288,6 +1380,12 @@ window.__ModuleLoader__.load({
 		* So the panel mechanics match 0.1.5: the wrapper slides, the wrapper takes the
 		* blur, and the wrapper needs promoting.
 		*
+		* Menus too — checked separately at both tags, because that is what this folder is
+		* for: 11 stylesheets paint the menu element from `--dsw-specific-menu` on alpha.1
+		* and alpha.2 alike, and `--dsw-menu-backdrop-filter` has no consumer on either, so
+		* `LEGACY_MENU_SURFACE` serves the whole line. The element is both the paint and
+		* the frost's only possible home.
+		*
 		* @module
 		*/
 		/** The extra session-header anchor this line introduces: the macOS titlebar work
@@ -1320,19 +1418,20 @@ window.__ModuleLoader__.load({
 			const m = /^alpha\.(\d+)$/.exec(pre);
 			return m === null || Number(m[1]) >= 2;
 		}
-		function panelFragments$2() {
+		function panelFragments$4() {
 			return {
 				promotion: `${PANEL_WRAPPER}{position:fixed!important;z-index:26!important}${PANEL_FULLSCREEN}{z-index:40!important}`,
 				blur: panelBlurRule(PANEL_WRAPPER)
 			};
 		}
-		function createAdapter$2(host) {
+		function createAdapter$4(host) {
 			return {
 				id: "0.1.6-alpha.1/alpha.2",
 				channel: "0.1.6-alpha",
 				host,
-				panelFragments: panelFragments$2,
+				panelFragments: panelFragments$4,
 				pluginPageRule: hasPluginManagerPage(host.version) ? PLUGIN_PAGE_FROST_RULE : "",
+				menus: LEGACY_MENU_SURFACE,
 				surface: {
 					ownsSidebarGuideSurface: true,
 					headerSlotKeys: hasLeadingHeaderSlot(host.version) ? [...BASE_HEADER_SLOT_KEYS, "conversation.session.header.leading"] : BASE_HEADER_SLOT_KEYS
@@ -1402,22 +1501,177 @@ window.__ModuleLoader__.load({
 		*     too. Checked against every use in this plugin: the stroke group is inherited
 		*     so a second match changes nothing, and the view-card discovery takes the
 		*     first match, which is still the real flow root. No arm needed.
+		*   · menus still paint THEMSELVES on this line — 15 stylesheets declare
+		*     `background:var(--dsw-specific-menu)` on the element at alpha.1/alpha.2 and 16
+		*     at rc.1, so `LEGACY_MENU_SURFACE` is the answer and the `MenuSurface` child
+		*     layer does not exist yet. Worth noting what DID arrive here:
+		*     `--dsw-menu-backdrop-filter` goes from zero consumers at 0.1.6-alpha.2 to 15 at
+		*     alpha.1 (16 at rc.1), i.e. this is the line where the host started frosting
+		*     menus on the element itself. The plugin's own filter sits on the same element
+		*     and wins the cascade by sheet order, so the element is still the only place a
+		*     frost can go — which is exactly why re-declaring the HOST's token instead
+		*     would be inert on this line and correct on the next one.
 		*
 		* @module
 		*/
-		function panelFragments$1() {
+		function panelFragments$3() {
 			return {
 				promotion: "",
 				blur: panelBlurRule(DOCKKIT_SLIDERS)
 			};
 		}
-		function createAdapter$1(host) {
+		function createAdapter$3(host) {
 			return {
 				id: "0.1.7-alpha.1/alpha.2/rc.1",
 				channel: "0.1.7-alpha",
 				host,
+				panelFragments: panelFragments$3,
+				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
+				menus: LEGACY_MENU_SURFACE,
+				surface: {
+					ownsSidebarGuideSurface: true,
+					headerSlotKeys: BASE_HEADER_SLOT_KEYS
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/host-compat/versions/v0-1-7-rc-2/adapter.ts
+		/**
+		* Adapter for the DSH `0.1.7-rc` channel, verified at `0.1.7-rc.2` (npm `latest`).
+		*
+		* Same patch line as `v0-1-7-alpha-1-2-rc-1`, DIFFERENT ANSWERS — which is why this
+		* folder exists at all rather than another row on that one. Everything the alpha
+		* folder says about panel mechanics still holds here (checked by diffing the panel
+		* CSS, dockkit, the slot renderer and the plugin-manager page tag to tag: no anchor
+		* line moved, and `TabLayout.tsx` / `SidebarRight.module.css` are unchanged from
+		* rc.1). What moved is where a MENU gets its paint.
+		*
+		* Two host changes reach this plugin:
+		*
+		*  1. `ui-primitives/src/MenuSurface.tsx` is NEW, and `TabMenu`, `MenuView`,
+		*     `PopupSelectView`, `ModelSelect` and `Menu` all render through it. The element
+		*     that carries `role="menu"` no longer paints anything: a `z-index:-1` child
+		*     layer does, reading `--dsw-menu-surface-fill` for the fill and
+		*     `--dsw-menu-backdrop-filter` for the frost. And `design-platform.css` flipped
+		*     its alias — `--dsw-specific-menu:var(--dsw-menu-surface-fill)`, where every
+		*     earlier release declared it the other way round. Consequence, read off those
+		*     two files rather than guessed: retinting `--dsw-specific-menu` alone now fades
+		*     nothing on a shared menu, so the card and header opacity sliders go inert on
+		*     exactly the surfaces they were built for. `LAYERED_MENU_SURFACE` is the answer.
+		*     Filtering the menu element would also have kept working, sort of — but the
+		*     child layer's own comment says it exists so that no ANCESTOR becomes a
+		*     backdrop root, so that arm stops being offered here.
+		*
+		*  2. `ui-settings-general/src/client/SettingsRoot.tsx` now renders the dialog
+		*     through `createPortal`, beside `#root`, instead of inline in the column. It
+		*     costs this plugin nothing, recorded so nobody re-derives it:
+		*     `SETTINGS_PANEL_SEL` tests the dialog's own identity (its hashed `_panel`
+		*     class plus `role`/`aria-modal`/`aria-labelledby`, all unchanged), never an
+		*     ancestor, so the retint and the blur land the same way one level higher up.
+		*     The one rule that DID care — `PART_BLUR_RULE`'s
+		*     `:has([role="dialog"]){isolation:auto}` valve, written because a modal mounted
+		*     inside a column kept its z-index local to that column — now never matches, and
+		*     that is fine: the modal it existed to release is no longer inside a column
+		*     either, so the trap and the valve left together.
+		*
+		* Still `0.1.7` facts, restated for the reader who only opens this folder:
+		*   · the panel is a stationary frame; the dockkit children slide, so the blur goes
+		*     on the children and nothing is promoted.
+		*   · `conversation.session.header.leading` is gone; `--dsw-specific-menu` is a
+		*     literal translucent rgba, not an alias of a layer token.
+		*   · the shimmer primitive is STILL `data-text-shimmer` (checked: `data-shimmer`
+		*     does not exist at this tag) — that rename belongs to 0.2.0.
+		*
+		* @module
+		*/
+		function panelFragments$2() {
+			return {
+				promotion: "",
+				blur: panelBlurRule(DOCKKIT_SLIDERS)
+			};
+		}
+		function createAdapter$2(host) {
+			return {
+				id: "0.1.7-rc.2",
+				channel: "0.1.7-rc",
+				host,
+				panelFragments: panelFragments$2,
+				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
+				menus: LAYERED_MENU_SURFACE,
+				surface: {
+					ownsSidebarGuideSurface: true,
+					headerSlotKeys: BASE_HEADER_SLOT_KEYS
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/host-compat/versions/v0-2-0-rc-1/adapter.ts
+		/**
+		* Adapter for the DSH `0.2.0-rc` channel, verified at `0.2.0-rc.1`.
+		*
+		* A new MINOR line, and the panel is not what changed. Checked by reading the
+		* emitting source at the tag rather than a changelog:
+		*   · `ui-sidebar-right/src/client/shell/SidebarRight.module.css` is BYTE-IDENTICAL
+		*     to `0.1.7-rc.2`, and `ui-primitives/src/MenuSurface.tsx` is byte-identical
+		*     too. So the slide owner, the layer variable and where a menu gets its paint
+		*     all answer the same as the `0.1.7-rc` folder — nothing below re-derives them.
+		*   · the five `conversation.session.header*` slot keys are the same five;
+		*     `conversation.session.header.leading` is still deleted.
+		*   · `ui-settings-general/SettingsRoot.tsx` is byte-identical, so the settings
+		*     dialog is still a body-level `createPortal` and `SETTINGS_PANEL_SEL`'s
+		*     identity test still reaches it.
+		*   · the boot peer gate (`app-boot/src/plugin-compatibility.ts`,
+		*     `compatibility-preflight.ts`) is byte-identical, which is what makes the
+		*     manifest change below a HARD requirement rather than metadata: an unlisted
+		*     peer version disables the plugin at profile composition and its modules are
+		*     never imported.
+		*
+		* What did move, and reaches this plugin:
+		*
+		*  1. `ui-dockkit/components/TabLayout.tsx` clamps a FLOATING pane's `top` with
+		*     `max(var(--dsh-dockkit-float-top, 0px), Ypx)`. Only floats: the attributes
+		*     this plugin matches, `data-dockkit-host="dock"` and `data-dockkit-empty`,
+		*     are on unchanged lines (verified by grep at both tags), so the blur arm
+		*     stands as the rc.2 folder wrote it.
+		*
+		*  2. `ui-primitives/src/TextShimmer.tsx` is REWRITTEN. The old primitive set
+		*     `data-text-shimmer` and painted the element itself with a clipped gradient
+		*     (`background-clip:text` + `-webkit-text-fill-color:transparent`) sized by an
+		*     inline `--dsh-text-shimmer-spread`, which no longer exists anywhere in the
+		*     repo. The new one marks its root `data-shimmer` and moves the highlight onto
+		*     an absolutely-positioned overlay (`.decoration` / `.sweep` / `.highlight`)
+		*     tinted by `--dsw-alias-label-shimmer`, so the real glyphs keep their own
+		*     color. Consequence for the stroke sliders: the old failure mode — a stroke
+		*     repainting transparent-filled glyphs as one flat blob — is gone, but
+		*     `-webkit-text-stroke` is still inherited, so the chat stroke would now land
+		*     on BOTH the real text and the sweeping copy and double every glyph while it
+		*     animates. Progress chrome still is not conversation prose, so the exemption
+		*     stays and gains the new attribute (`STROKE_RULE`).
+		*     More rows use it now: `ReasoningRow` and `GenericCommandCard` join
+		*     `ChatGroupSeat` / `MessageItem` / `RunningStatus` / `DisclosureRow`.
+		*
+		*  3. `ui-plugin-manager` gains a first-read `ListSkeleton`. Its card `ul` carries
+		*     the same `.cards` class but sits under `section[data-plugin-loading]`
+		*     instead of `section[data-plugin-scope]`, so the shared frost rule had to
+		*     grow or the plugin page would show an unfrosted list for the length of the
+		*     first read and then re-frost it — see `PLUGIN_PAGE_FROST_RULE`.
+		*
+		* @module
+		*/
+		function panelFragments$1() {
+			return {
+				promotion: "",
+				blur: panelBlurRule(DOCKKIT_SLIDERS)
+			};
+		}
+		function createAdapter$1(host) {
+			return {
+				id: "0.2.0-rc.1",
+				channel: "0.2.0-rc",
+				host,
 				panelFragments: panelFragments$1,
 				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
+				menus: LAYERED_MENU_SURFACE,
 				surface: {
 					ownsSidebarGuideSurface: true,
 					headerSlotKeys: BASE_HEADER_SLOT_KEYS
@@ -1459,6 +1713,7 @@ window.__ModuleLoader__.load({
 				host,
 				panelFragments,
 				pluginPageRule: PLUGIN_PAGE_FROST_RULE,
+				menus: UNRESOLVED_MENU_SURFACE,
 				surface: {
 					ownsSidebarGuideSurface: false,
 					headerSlotKeys: BASE_HEADER_SLOT_KEYS
@@ -1468,9 +1723,11 @@ window.__ModuleLoader__.load({
 		//#endregion
 		//#region src/client/host-compat/versions/registry.ts
 		const ADAPTERS = {
-			"0.1.5-rc": createAdapter$3,
-			"0.1.6-alpha": createAdapter$2,
-			"0.1.7-alpha": createAdapter$1,
+			"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,
 			unknown: createAdapter
 		};
 		/** Pick the adapter for a resolved host. `host.channel` is already narrowed to
@@ -3398,7 +3655,7 @@ window.__ModuleLoader__.load({
 			}
 			try {
 				const forceDark = scheme === "dark";
-				const key = `${h}|${s}|${l}|${verdict}|${scheme}|${hasColor}`;
+				const key = `${h}|${s}|${l}|${verdict}|${scheme}|${hasColor}|${hostAdapter().menus.fillTokens.join(",")}`;
 				if (key !== baseTokenKey) {
 					baseTokenKey = key;
 					if (forceDark) document.body.setAttribute("data-ds-dark-theme", "dsh-any-background");
@@ -3408,6 +3665,13 @@ window.__ModuleLoader__.load({
 						const opVar = OPACITY_VARS[name];
 						decls.push(`${name}:${opVar !== void 0 ? `var(${opVar})` : value}!important`);
 					}
+					if (tokens["--dsw-specific-menu"] !== void 0) {
+						const menuVar = OPACITY_VARS[MENU_FILL_TOKEN];
+						for (const name of hostAdapter().menus.fillTokens) {
+							if (name === "--dsw-specific-menu" || tokens[name] !== void 0) continue;
+							decls.push(`${name}:var(${menuVar})!important`);
+						}
+					}
 					ensureTokenStyle().textContent = `body{${decls.join(";")}}`;
 					for (const name of appliedTokenNames) document.body.style.removeProperty(name);
 					appliedTokenNames = Object.keys(tokens);
@@ -3433,8 +3697,34 @@ window.__ModuleLoader__.load({
 		}
 		const SETTINGS_PANEL_SEL = "[role=\"dialog\"][aria-modal=\"true\"][aria-labelledby][class*=\"_panel\"]";
 		const SETTINGS_STYLE_RULE = `${SETTINGS_PANEL_SEL}{background:var(--dsh-any-bg-settings-surface,var(--dsw-alias-bg-layer-2));backdrop-filter:var(--dsh-any-blur-settings,none);--dsw-alias-bg-layer-1:var(--dsh-any-bg-settings-layer-1);--dsw-alias-bg-layer-2:var(--dsh-any-bg-settings-layer-2);--dsw-alias-bg-layer-3:var(--dsh-any-bg-settings-layer-3)}${SETTINGS_PANEL_SEL} .dab-card{backdrop-filter:var(--dsh-any-blur-card-panels,none);-webkit-backdrop-filter:var(--dsh-any-blur-card-panels,none)}`;
+		const CARD_BLUR_VAR = "--dsh-any-blur-card-panels";
+		const POPOVER_MENU_SEL = `[role="menu"]:not([data-dockkit-tab-menu])`;
+		const POPOVER_OTHER_SEL = "[role=\"listbox\"],body > [role=\"tree\"],body > [role=\"dialog\"]:not([aria-modal=\"true\"])";
+		/** The frost declaration this release's menus want, driven by the named plugin var.
+		*  Every menu-shaped surface group asks through here, so the card group, the header
+		*  group and the exemptions can never disagree about which layer to paint. */
+		function menuFrost(blurVar) {
+			return hostAdapter().menus.frostDecl(`var(${blurVar},none)`);
+		}
+		/** Declare EVERY token this release's menus can paint their fill from with the same
+		*  value. One slider, one value, every layer reached — and a token the host does not
+		*  read is inert, so this is safe to emit on a line that only needs one.
+		*
+		*  Used for values that are guaranteed to resolve. Where the value is a `var()` the
+		*  caller must first confirm the variable it names is actually set: an undefined
+		*  custom property inside `background:var(…)` computes to the guaranteed-invalid
+		*  value and the surface goes fully transparent (see the notes on
+		*  `applyHeaderPopovers` and `applyExemptDefaults`). */
+		function menuFillDecls(value) {
+			return hostAdapter().menus.fillTokens.map((name) => `${name}:${value}`).join(";");
+		}
+		function popoverBlurRule() {
+			return `${POPOVER_MENU_SEL}{${menuFrost(CARD_BLUR_VAR)}}${POPOVER_OTHER_SEL}{${elementFrostDecl(`var(${CARD_BLUR_VAR},none)`)}}`;
+		}
 		const INPUT_FROST_CLASS = "dab-input-frost";
-		const INPUT_BLUR_RULE = `.${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]{--dsw-specific-menu:var(--dsh-any-op-menu-cordis)!important}`;
+		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")}}`;
+		}
 		function applyInputBlur(px) {
 			const root = document.documentElement;
 			if (px > 0) root.classList.add(INPUT_FROST_CLASS);
@@ -3472,9 +3762,22 @@ window.__ModuleLoader__.load({
 		*  taking the card blur. `[role]` is a no-op presence test that raises only the
 		*  tagged arm to (0,2,0); the other three already qualify at (0,2,0)+. */
 		const HEADER_SURFACES_PADDED = [`${HEADER_TAG_SELECTOR}[role]`, ...HEADER_SURFACES.slice(1)];
-		const HEADER_POPOVER_RULE = `${HEADER_SURFACES_PADDED.join(",")}{-webkit-backdrop-filter:var(--dsh-any-blur-header,none);backdrop-filter:var(--dsh-any-blur-header,none)}`;
+		/** The header blur variable, and the rule that frosts the header's dropdown set.
+		*  The declaration comes from the same adapter answer as the card group's menu arm:
+		*  every surface in this set paints its skin from the host's own menu-blur token
+		*  (`SubagentHeaderLineage.module.css:120` uses a pseudo-element, the stat dialog and
+		*  goal bar use their own layer), so handing over the token reaches all of them on
+		*  both paint shapes, while filtering the element would install the ancestor
+		*  backdrop root each of those files documents avoiding. */
+		const HEADER_BLUR_VAR = "--dsh-any-blur-header";
+		function headerPopoverRule() {
+			return `${HEADER_SURFACES_PADDED.join(",")}{${menuFrost(HEADER_BLUR_VAR)}}`;
+		}
+		function exemptDefaultRule() {
+			return `[role="dialog"][aria-modal="true"]:not([aria-labelledby]){backdrop-filter:none;-webkit-backdrop-filter:none}[role="menu"]:has([class*="_danger"]){${hostAdapter().menus.frostDecl("none")};-webkit-text-stroke-width:0}`;
+		}
 		/** Selector the dynamic header token rule targets — the same set as the static
-		*  HEADER_POPOVER_RULE above, so the two can never drift apart. */
+		*  headerPopoverRule above, so the two can never drift apart. */
 		const HEADER_TOKEN_SELECTOR = HEADER_SURFACES_PADDED.join(",");
 		/** Header-popover surfaces: retint the menu token and (re)write the blur.
 		*  Mirrors applyProduced: the static rule above never changes, so a drag only
@@ -3487,9 +3790,9 @@ window.__ModuleLoader__.load({
 			let opacity = rHeaderOpacity();
 			if (opacity < 0) opacity = 0;
 			if (opacity > 1) opacity = 1;
-			const menu = (paletteTokens() ?? readHostOpacityTokens())?.["--dsw-specific-menu"];
+			const menu = (paletteTokens() ?? readHostOpacityTokens())?.[MENU_FILL_TOKEN];
 			const el = ensureHeaderStyle();
-			const css = menu === void 0 ? "" : `${HEADER_TOKEN_SELECTOR}{--dsw-specific-menu:${toRgba(menu, opacity)}}`;
+			const css = menu === void 0 ? "" : `${HEADER_TOKEN_SELECTOR}{${menuFillDecls(toRgba(menu, opacity))}}`;
 			if (el.textContent !== css) el.textContent = css;
 		}
 		let headerStyleEl = null;
@@ -3529,7 +3832,8 @@ window.__ModuleLoader__.load({
 			add("--dsw-alias-bg-layer-1", source?.["--dsw-alias-bg-layer-1"]);
 			add("--dsw-alias-bg-layer-2", source?.["--dsw-alias-bg-layer-2"]);
 			add("--dsw-alias-bg-layer-3", source?.["--dsw-alias-bg-layer-3"]);
-			add("--dsw-specific-menu", source?.["--dsw-specific-menu"]);
+			const menuColor = source?.[MENU_FILL_TOKEN];
+			for (const name of hostAdapter().menus.fillTokens) add(name, menuColor);
 			if (decls.length === 0) {
 				if (el.textContent !== "") el.textContent = "";
 				return;
@@ -3557,7 +3861,7 @@ window.__ModuleLoader__.load({
 			`[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}`,
 			`${PANEL_SURFACES}{-webkit-text-stroke:var(--dsh-any-stroke-panel-w,0px) var(--dsh-any-stroke-panel-c,transparent);paint-order:stroke fill}`,
 			`${HEADER_SURFACES.join(",")}{-webkit-text-stroke:var(--dsh-any-stroke-header-w,0px) var(--dsh-any-stroke-header-c,transparent);paint-order:stroke fill}`,
-			"[data-chat-flow] [role=\"status\"],[data-chat-flow] [data-turn-process],[data-chat-flow] [data-text-shimmer],[data-chat-flow] [style*=\"--dsh-text-shimmer-spread\"]{-webkit-text-stroke-width:0!important;paint-order:normal!important}",
+			"[data-chat-flow] [role=\"status\"],[data-chat-flow] [data-turn-process],[data-chat-flow] [data-text-shimmer],[data-chat-flow] [data-shimmer],[data-chat-flow] [style*=\"--dsh-text-shimmer-spread\"]{-webkit-text-stroke-width:0!important;paint-order:normal!important}",
 			`svg{-webkit-text-stroke-width:0!important;paint-order:normal!important}`,
 			`::placeholder{-webkit-text-stroke-width:0!important}`
 		].join("");
@@ -3774,6 +4078,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}";
 		/** 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
@@ -3800,6 +4105,7 @@ window.__ModuleLoader__.load({
 		function applySettingsOverrides(op) {
 			applyLayerOverrides("--dsh-any-bg-settings", op, true);
 		}
+		const TRAJECTORY_STYLE_RULE = "[data-conversation-composer-overlay]{--dsw-alias-bg-layer-1:var(--dsh-any-traj-layer-1);--dsw-alias-bg-layer-2:var(--dsh-any-traj-layer-2);--dsw-alias-bg-layer-3:var(--dsh-any-traj-layer-3)}";
 		function applyTrajectoryOverrides(op) {
 			applyLayerOverrides("--dsh-any-traj", op, false);
 		}
@@ -4775,9 +5081,10 @@ window.__ModuleLoader__.load({
 		* `wallpaper.ts` — so it is encoded here instead, in one list, with the reason
 		* next to each entry.
 		*
-		* What the release can change lives in one contiguous slot: the panel group
-		* (which element carries the frost) and the plugin-manager page (whether this
-		* release ships that page at all). Everything outside the slot is host-agnostic by
+		* What the release can change lives in the slots marked below: the panel group
+		* (which element carries the frost), the plugin-manager page (whether this release
+		* ships that page at all), and the menu groups (which token a menu's fill comes
+		* from and whose job its frost is). Everything outside a slot is host-agnostic by
 		* construction — it targets attributes every release in range emits.
 		*
 		* The sheet is rebuilt when the release verdict lands. It has to be: `apply` runs
@@ -4794,19 +5101,25 @@ window.__ModuleLoader__.load({
 		/**
 		* The order contract. Later entries override earlier ones at equal specificity,
 		* which several groups rely on:
-		*   · HEADER_POPOVER_RULE after POPOVER_BLUR_RULE — a surface moving from the card
+		*   · headerPopoverRule() after popoverBlurRule() — a surface moving from the card
 		*     group to the header group must win, not merely be listed twice.
 		*   · PRODUCED_RULE / STROKE_RULE after the blur groups — they shield their
 		*     surfaces from an inherited slider.
-		*   · EXEMPT_DEFAULT_RULE last of the token groups — an exemption has to land
+		*   · exemptDefaultRule() last of the token groups — an exemption has to land
 		*     after whatever it exempts.
 		*   · PLACEHOLDER_RULE genuinely last — `::placeholder` resets must survive every
 		*     group above.
+		*
+		* Three of these are FUNCTIONS, not constants, and they are version slots like
+		* `panel.blur`: which declaration frosts a menu, and which token a menu's fill
+		* comes from, is the current adapter's answer (`adapter.menus`). They stay in
+		* place rather than moving next to the other slots because the contract above is
+		* about position — a slot is only safe if it does not have to relocate.
 		*/
 		function buildStaticStyles() {
 			const adapter = rHostAdapter();
 			const panel = adapter.panelFragments();
-			return DARK_GRADIENT + FRAME_CLEAR_RULE + SETTINGS_STYLE_RULE + "[role=\"menu\"]:not([data-dockkit-tab-menu]),[role=\"listbox\"],body > [role=\"tree\"],body > [role=\"dialog\"]:not([aria-modal=\"true\"]){backdrop-filter:var(--dsh-any-blur-card-panels,none);-webkit-backdrop-filter:var(--dsh-any-blur-card-panels,none)}[data-conversation-composer-overlay]{--dsw-alias-bg-layer-1:var(--dsh-any-traj-layer-1);--dsw-alias-bg-layer-2:var(--dsh-any-traj-layer-2);--dsw-alias-bg-layer-3:var(--dsh-any-traj-layer-3)}" + INPUT_BLUR_RULE + MOBILE_HEADER_RULE + PANEL_TOKEN_RULE + panel.promotion + panel.blur + adapter.pluginPageRule + PRODUCED_RULE + STROKE_RULE + HEADER_POPOVER_RULE + "[role=\"dialog\"][aria-modal=\"true\"]:not([aria-labelledby]){backdrop-filter:none;-webkit-backdrop-filter:none}[role=\"menu\"]:has([class*=\"_danger\"]){backdrop-filter:none;-webkit-backdrop-filter:none;-webkit-text-stroke-width:0}[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}";
+			return DARK_GRADIENT + FRAME_CLEAR_RULE + SETTINGS_STYLE_RULE + popoverBlurRule() + TRAJECTORY_STYLE_RULE + inputBlurRule() + MOBILE_HEADER_RULE + PANEL_TOKEN_RULE + panel.promotion + panel.blur + adapter.pluginPageRule + PRODUCED_RULE + STROKE_RULE + headerPopoverRule() + exemptDefaultRule() + PLACEHOLDER_RULE;
 		}
 		/** Append the plugin's stylesheet and keep it matched to the host.
 		*  Returns a teardown for the plugin's effect scope. */