dsh-any-background 0.3.6 → 0.3.7

package/lib/client.js

@@ -1014,36 +1014,15 @@ window.__ModuleLoader__.load({
 		//#region src/host-compat/channel.ts
 		/** What this plugin supports, in upgrade order. One row = one build whose facts
 		*  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) —
+		*  verified as needing no change to that folder's adapter (as `0.2.1-alpha.2` 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`, 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).
+		*  how a line says "the facts changed halfway through it" (`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 = [
-			{
-				channel: "0.1.5-rc",
-				release: "0.1.5-rc.2"
-			},
-			{
-				channel: "0.1.6-alpha",
-				release: "0.1.6-alpha.2"
-			},
-			{
-				channel: "0.1.7-alpha",
-				release: "0.1.7-alpha.2"
-			},
-			{
-				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"
@@ -1055,6 +1034,10 @@ window.__ModuleLoader__.load({
 			{
 				channel: "0.2.1-alpha",
 				release: "0.2.1-alpha.1"
+			},
+			{
+				channel: "0.2.1-alpha",
+				release: "0.2.1-alpha.2"
 			}
 		];
 		const UNKNOWN_HOST_INFO = {
@@ -1110,8 +1093,8 @@ window.__ModuleLoader__.load({
 		/** Pick the adapter for a release, clamping to the nearest verified line when the
 		*  release is outside everything this plugin has seen.
 		*
-		*  A release is matched by PATCH LINE before anything else: `0.1.6-alpha.4` and a
-		*  future `0.1.6` stable both belong to the line verified at `0.1.6-alpha.2`, and
+		*  A release is matched by PATCH LINE before anything else: `0.2.1-alpha.3` and a
+		*  future `0.2.1` stable both belong to the line verified at `0.2.1-alpha.1/2`, and
 		*  handing them that adapter beats giving up — the DOM probes only cover panel
 		*  mechanics, not the surface decisions the line is known for.
 		*
@@ -1157,14 +1140,6 @@ window.__ModuleLoader__.load({
 		function channelOf(version) {
 			return classifyRelease(version).channel;
 		}
-		/** Prerelease tag of a release string (`alpha.2` in `0.1.6-alpha.2`), or null
-		*  when the version is bare/undetermined. Needed because a channel is coarser
-		*  than reality: `conversation.session.header.leading` ships in exactly one
-		*  build within the 0.1.6-alpha line. */
-		function prereleaseOf(version) {
-			if (version === null) return null;
-			return /^\d+\.\d+\.\d+-([0-9A-Za-z.-]+)$/.exec(version)?.[1] ?? null;
-		}
 		//#endregion
 		//#region src/client/host-compat/versions/shared.ts
 		/** The host's own right Sidebar wrapper. */
@@ -1183,7 +1158,7 @@ window.__ModuleLoader__.load({
 		*  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`.
+		*  `dsh-v0.1.5-rc.2` through `dsh-v0.2.1-alpha.2`.
 		*
 		*  The marker sits on the wrapper, the fill on its child card:
 		*  `[data-approval-key] > div`, `[data-plan-review-key] > section`,
@@ -1268,33 +1243,22 @@ window.__ModuleLoader__.load({
 		*  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. */
+		*  thing that paints. 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.
+		* The era this table now starts in (`0.2.0-rc.1`) already presents the shape below;
+		* the 0.1.5 / 0.1.6 / 0.1.7-alpha line, where the menu ELEMENT painted itself and the
+		* host frosted nothing at all before `0.1.7-alpha.1`, is recorded in
+		* `LAYERED_MENU_SURFACE`'s first bullet rather than in an adapter, because no adapter
+		* answers for it any more.
 		*
-		* `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
+		* `0.1.7-rc.2` 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)`
@@ -1312,18 +1276,23 @@ window.__ModuleLoader__.load({
 		*       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 same 14 stylesheets at every tag in the table (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. A 15th file names the same token without consuming it:
+		*   `ui-theme/src/styles/gradient-shadow-text.css` DECLARES it on `body` —
+		*   `blur(40px) saturate(150%)`, no media query — which is exactly why writing the
+		*   token on a menu with a `none` fallback deletes a frost the host always had
+		*   (see `CARD_FROST_GATE` in `wallpaper.ts`). `MenuSurface.tsx` / `.module.css` are
+		*   byte-identical from rc.2 through `0.2.1-alpha.2`, and the consumer set moved only
+		*   in line numbers (the same 15 files at every tag in the table, checked per tag).
 		*
-		* `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;
+		* `dsh-v0.2.0-rc.2` … `dsh-v0.2.1-alpha.2`: 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`,
@@ -1335,13 +1304,7 @@ window.__ModuleLoader__.load({
 		*   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. */
-		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
+		/** The answer for `0.2.0-rc` and for `0.2.1-alpha`. 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`,
@@ -1406,307 +1369,6 @@ window.__ModuleLoader__.load({
 			"conversation.session.header.lineage"
 		];
 		//#endregion
-		//#region src/client/host-compat/versions/v0-1-5-rc-2-3/adapter.ts
-		/**
-		* Adapter for the DSH 0.1.5-rc channel (`0.1.5-rc.2`, `0.1.5-rc.3`).
-		*
-		* Nothing here is inferred from a neighbouring release — each fact below was
-		* checked against the harness tags `dsh-v0.1.5-rc.2` / `dsh-v0.1.5-rc.3`.
-		*
-		* Host shape this line presents:
-		*   `ui-sidebar-right/shell/SidebarRight.module.css`
-		*     .panel { position:absolute; z-index:10; transform:translateX(100%); visibility:hidden }
-		*     .panel[data-sidebar-right-open] { transform:none }
-		*     .panel[data-sidebar-right-panel='fullscreen'] { position:fixed; inset:0; z-index:40 }
-		*   `ui-dockkit` ships WITHOUT `TabLayout.tsx`, so `[data-dockkit-host]` and
-		*   `[data-dockkit-empty]` are never rendered on this line.
-		*   `ui-plugin-manager` (the page behind `PLUGIN_PAGE_FROST_RULE`) is not a package
-		*   on this line at all, and neither tag emits `[data-plugin-panel]`.
-		*
-		* Consequence for the panel slider: the WRAPPER is what slides, so the
-		* `backdrop-filter` belongs on the wrapper — and because the wrapper sits inside
-		* 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$7() {
-			return {
-				promotion: `${PANEL_WRAPPER}{position:fixed!important;z-index:26!important}${PANEL_FULLSCREEN}{z-index:40!important}`,
-				blur: panelBlurRule(PANEL_WRAPPER)
-			};
-		}
-		function createAdapter$7(host) {
-			return {
-				id: "0.1.5-rc.2/rc.3",
-				channel: "0.1.5-rc",
-				host,
-				panelFragments: panelFragments$7,
-				pluginPageRule: "",
-				menus: LEGACY_MENU_SURFACE,
-				surface: {
-					ownsSidebarGuideSurface: false,
-					headerSlotKeys: BASE_HEADER_SLOT_KEYS
-				}
-			};
-		}
-		//#endregion
-		//#region src/client/host-compat/versions/v0-1-6-alpha-1-2/adapter.ts
-		/**
-		* Adapter for the DSH 0.1.6-alpha channel (`0.1.6-alpha.1`, `0.1.6-alpha.2`).
-		*
-		* Facts checked per tag against `dsh-v0.1.6-alpha.1` / `dsh-v0.1.6-alpha.2` —
-		* deliberately not copied over from the 0.1.5 folder, even where the two lines
-		* turned out to agree. If a future 0.1.6 patch diverges, only this file moves.
-		*
-		* Host shape this line presents:
-		*   `SidebarRight.module.css` is unchanged from the 0.1.5 line for the parts that
-		*   matter: `.panel` still carries `position:absolute` + `transform:translateX(100%)`,
-		*   `data-sidebar-right-open` still clears it with `transform:none`, and the panel
-		*   width is still an inline `width` with no `--dsh-sidebar-width` variable.
-		*   alpha.2 appends fullscreen window chrome (`.63` windows / `.77` darwin), which
-		*   does not move the blur target, AND the `ui-plugin-manager` package — so the
-		*   plugin-page frost below is prerelease-gated rather than channel-wide.
-		*   `ui-dockkit` still has no `TabLayout.tsx`, so no `[data-dockkit-host]` /
-		*   `[data-dockkit-empty]` on this line either.
-		*
-		* 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
-		*  added `conversation.session.header.leading`. It was deleted again at
-		*  0.1.7-alpha.1 with no shim, so it is unique to this line — which is why the
-		*  channel alone is not enough to answer it and the prerelease is read.
-		*  `alpha.1` predates it.
-		*
-		* Erring toward "included": a slot key the host never emits simply matches
-		*  nothing, whereas a key we omit hides a header area from the plugin for the
-		*  whole session. */
-		function hasLeadingHeaderSlot(version) {
-			const pre = prereleaseOf(version);
-			if (pre === null) return true;
-			const m = /^alpha\.(\d+)$/.exec(pre);
-			return m === null || Number(m[1]) >= 2;
-		}
-		/** The other thing this line splits on: `ui-plugin-manager` — the package that
-		*  renders `设置 → 插件` and stamps `[data-plugin-panel]` — was CREATED at
-		*  alpha.2. Until then the plugin list was a settings tab in
-		*  `ui-settings-plugin-inventory`, which carries `[data-plugin-scope]` but no
-		*  card list to frame, so alpha.1 has nothing for the frost rule to apply to.
-		*
-		*  Same erring-toward-included convention as `hasLeadingHeaderSlot`: the rule's
-		*  own `[data-plugin-panel]` prefix means an over-broad arm cannot paint, while
-		*  an over-narrow one leaves a page bare for the whole session. */
-		function hasPluginManagerPage(version) {
-			const pre = prereleaseOf(version);
-			if (pre === null) return true;
-			const m = /^alpha\.(\d+)$/.exec(pre);
-			return m === null || Number(m[1]) >= 2;
-		}
-		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$6(host) {
-			return {
-				id: "0.1.6-alpha.1/alpha.2",
-				channel: "0.1.6-alpha",
-				host,
-				panelFragments: panelFragments$6,
-				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
-				}
-			};
-		}
-		//#endregion
-		//#region src/client/host-compat/versions/v0-1-7-alpha-1-2-rc-1/adapter.ts
-		/**
-		* Adapter for the DSH 0.1.7-alpha channel (`0.1.7-alpha.1`, `0.1.7-alpha.2`),
-		* re-verified unchanged at `0.1.7-rc.1`.
-		*
-		* This is the line the panel mechanics actually changed on — verified against
-		* `dsh-v0.1.6-alpha.2` → `dsh-v0.1.7-alpha.1`, where `SidebarRight.module.css`
-		* was rewritten (116 lines changed) and `ui-dockkit/src/components/TabLayout.tsx`
-		* was ADDED. Both facts were checked, not assumed.
-		*
-		* `0.1.7-rc.1` was checked the same way, by diffing every package that emits an
-		* anchor this plugin matches (the panel CSS, dockkit, the plugin-manager page, the
-		* slot renderer, the theme tokens): no anchor line moved, and the two UI changes it
-		* carries do not reach us —
-		*   · `ui-plugin-manager`: a new `InstallDialog` failure screen plus compatibility
-		*     wording. The card block (`section` → `div.groupHead` + `ul.cards`) is
-		*     untouched, and the dialog is a body-level `Modal`, so the `:has()` valve of
-		*     `PLUGIN_PAGE_FROST_RULE` never even has to fire for it.
-		*   · `ui-conversation`: `.titleRow` gains `container-type:inline-size`, which makes
-		*     it a stacking context and a containing block. Header slots sit inside that
-		*     row, but this plugin reaches them through background/blur tokens, and the
-		*     dropdowns they trigger portal to `document.body` (see `header-tag.ts`), so
-		*     nothing of ours lands inside the new containment.
-		*
-		* Host shape this line presents:
-		*   .panel { position:absolute; --dsh-dockkit-dock-layer:10; pointer-events:none }
-		*     — no transform, no visibility, and no z-index of its own any more.
-		*   .panel :global([data-dockkit-host='dock']),
-		*   .panel :global([data-dockkit-empty]),
-		*   .panel :global([data-dockkit-divider]) { transform:translateX(var(--dsh-sidebar-width)); visibility:hidden }
-		*   .panel[data-sidebar-right-open] :global(…) { transform:none }
-		*     — the DOCKED CHILDREN are what slide.
-		*   .panel[data-sidebar-right-panel='fullscreen'] { --dsh-dockkit-dock-layer:40 }
-		*     — fullscreen no longer flips the panel to `position:fixed`; it raises a
-		*       layer variable, and the width becomes `100vw` on the absolute panel.
-		*
-		* Consequences encoded below:
-		*   1. The blur belongs on the children. On the wrapper it frosted a stationary
-		*      frame — "the blur stays put while the sidebar moves".
-		*   2. The promotion must NOT be emitted. `position:fixed` detaches the panel from
-		*      the track the host animates, which is the whole reason 2 the blur stopped
-		*      travelling. The host's own sheet documents the content root as owning "no
-		*      stacking context or transform", so `backdrop-filter` resolves against the
-		*      page and samples the wallpaper unaided.
-		*   3. `[data-dockkit-empty]` must be included alongside `[data-dockkit-host]`: a
-		*      pane with no tabs renders the empty host instead, and keying on `host`
-		*      alone mis-detects that (transient) shape.
-		*
-		* Also true of this line, recorded so the next reader does not re-derive it:
-		*   · `conversation.session.header.leading` was DELETED here with no shim, so this
-		*     folder deliberately does not list it (see the 0.1.6 folder).
-		*   · `--dsw-specific-menu` was severed from `--dsw-alias-bg-layer-3` and became a
-		*     literal translucent rgba, plus a `html[data-platform='darwin']` re-override.
-		*     The plugin already samples and writes that token directly, so the severance
-		*     needs no adapter of its own — but note the consequence: `toRgba()` REPLACES
-		*     alpha, so the header slider now overrides the host's own 0.58 rather than
-		*     fading an opaque layer. Intended (the slider means "this opacity"), worth
-		*     knowing if the 0.1.7 header ever looks too thin.
-		*   · `[data-chat-flow]` is stamped on a nested `ChatGroupSeat` content element
-		*     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$5() {
-			return {
-				promotion: "",
-				blur: panelBlurRule(DOCKKIT_SLIDERS)
-			};
-		}
-		function createAdapter$5(host) {
-			return {
-				id: "0.1.7-alpha.1/alpha.2/rc.1",
-				channel: "0.1.7-alpha",
-				host,
-				panelFragments: panelFragments$5,
-				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$4() {
-			return {
-				promotion: "",
-				blur: panelBlurRule(DOCKKIT_SLIDERS)
-			};
-		}
-		function createAdapter$4(host) {
-			return {
-				id: "0.1.7-rc.2",
-				channel: "0.1.7-rc",
-				host,
-				panelFragments: panelFragments$4,
-				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`.
@@ -1848,9 +1510,10 @@ window.__ModuleLoader__.load({
 			};
 		}
 		//#endregion
-		//#region src/client/host-compat/versions/v0-2-1-alpha-1/adapter.ts
+		//#region src/client/host-compat/versions/v0-2-1-alpha-1-2/adapter.ts
 		/**
-		* Adapter for the DSH `0.2.1-alpha` line, verified at `0.2.1-alpha.1`.
+		* Adapter for the DSH `0.2.1-alpha` line, verified at `0.2.1-alpha.1` AND
+		* `0.2.1-alpha.2`.
 		*
 		* 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
@@ -1874,6 +1537,18 @@ window.__ModuleLoader__.load({
 		*   · `TextShimmer` still marks its root `data-shimmer`, so the stroke exemption
 		*     written for rc.1 stands.
 		*
+		* Re-checked at `0.2.1-alpha.2`, same list: `design-platform.css` still byte-identical
+		* (`--dsw-menu-surface-fill` / `--dsw-specific-menu` / `--dsw-alias-menu-group-header-fill`
+		* on both scheme blocks); `MenuSurface.tsx`/`.module.css` byte-identical (blob hashes
+		* match); the `--dsw-specific-menu` and `--dsw-menu-backdrop-filter` file sets are the
+		* same 15 at both tags (the frost side being 14 consumers plus the `body` declaration
+		* in `gradient-shadow-text.css`);
+		* `[data-sidebar-right-panel]` and the dockkit slide unchanged; the five header slot
+		* keys unchanged; `AppFrame.tsx` / `AppFrame.module.css` untouched. The plugin-manager
+		* page gained a third `[data-plugin-scope]` group (`data-plugin-group="more"`) inside
+		* the same `[data-plugin-panel]`, which the existing rule already frames, so no new
+		* fact lands here.
+		*
 		* 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]`
@@ -1895,6 +1570,38 @@ window.__ModuleLoader__.load({
 		*     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.
+		*  5. `ui-theme/src/styles/base.css` restructured the font tokens: the built-in stacks
+		*     moved to `--dsh-font-family-text-default` / `-code-default`, and the host now
+		*     composes the tokens itself on `body` —
+		*     `--dsw-font-family: var(--dsh-font-family-text, …), …` — fed by the per-role user
+		*     font lists `ThemePresenter` publishes (`--dsh-font-family-text` / `-code` /
+		*     `-terminal`, new at this tag). That is a NEW `body`-level declaration of the very
+		*     token this plugin's custom-font feature writes, at the same specificity as its
+		*     rule — so which one wins became a question of stylesheet order. `applyFontFace`
+		*     now asserts its `--dsw-font-family` with `!important`, the way the token sheet
+		*     already does, so a host re-injecting its base styles cannot quietly drop the
+		*     picked font. Code typography (`--ds-font-family-code`, plus the new
+		*     `--dsh-code-font-size` axis) stays untouched — this plugin never owned it.
+		*  6. AT `0.2.1-alpha.2`, `ui-jobs/JobListAction` moved its background-task list out of
+		*     the header row and into a `createPortal(…, document.body)` painted
+		*     `position:fixed; z-index:100` — and the list is a bare `<ul>` with NO `role`, so
+		*     `header-tag.ts`'s `[role="menu"|"tree"|"dialog"]` probe can never claim it and the
+		*     `ul[class*="_menu"]` class shape is the only thing that still styles it.
+		*     Through `0.2.1-alpha.1` the same list is IN-PLACE — `{open ? <ul className={css.menu}
+		*     style={{left: menuShift}}/> : null}` with `.menu{position:absolute; top:calc(100% +
+		*     5px); z-index:100}` under a `.root{position:relative}` — which is the exact DOM the
+		*     reported bug was captured from (`style="left: 0px;"`, no `top`, no role). The portal
+		*     is therefore what HID the bug on the newest tag, not what fixed it: an absolutely
+		*     positioned `z-index:100` child of the header row is only buried by the page once
+		*     something makes that row a stacking context, and the thing that did was this
+		*     plugin's own 「标题栏」 frost. Nothing here is a per-release fact to route on —
+		*     `0.2.1-alpha.2` merely swapped which header component gets caught by it, because
+		*     `ui-schedule/TaskMenu` (registered into `…header.utilities` on every release in
+		*     range) is `role="menu"` + `position:absolute; z-index:100` in place whenever the
+		*     Menu primitive is not in portal mode. The compensation lives with the injury: see
+		*     the `z-index` note on `HEADER_BAR_RULE` in `wallpaper.ts`. (Checked and rejected:
+		*     `ui-conversation/ContextMeter`'s `position:fixed` panel is NOT row chrome —
+		*     `InputBar.tsx` mounts it in the composer, so the row never re-anchored it.)
 		*
 		* @module
 		*/
@@ -1906,7 +1613,7 @@ window.__ModuleLoader__.load({
 		}
 		function createAdapter$1(host) {
 			return {
-				id: "0.2.1-alpha.1",
+				id: "0.2.1-alpha.1/alpha.2",
 				channel: "0.2.1-alpha",
 				host,
 				panelFragments: panelFragments$1,
@@ -1963,10 +1670,6 @@ window.__ModuleLoader__.load({
 		//#endregion
 		//#region src/client/host-compat/versions/registry.ts
 		const ADAPTERS = {
-			"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,
@@ -2372,7 +2075,7 @@ window.__ModuleLoader__.load({
 		*
 		* Everything downstream asks a QUESTION ("who owns the guide surface?", "which CSS
 		* arm applies?") and gets an answer from the current adapter. No consumer names a
-		* release. That is what keeps the per-version folders honest: when 0.1.8 needs a
+		* release. That is what keeps the per-version folders honest: when a newer line needs a
 		* new behaviour, a consumer changes by reading a new adapter field, not by growing
 		* another version comparison.
 		*
@@ -3943,6 +3646,14 @@ window.__ModuleLoader__.load({
 		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])`;
+		/** The `MenuSurface` root's own marker (`ui-primitives/MenuSurface.tsx`), present on
+		*  every release whose menus paint through that layer. It joins the card group because
+		*  the role set cannot reach all of them: `ModelSelect` renders its model pane as
+		*  `role="group"` (ModelSelect.tsx:486), so keyed on `[role="menu"]` alone that card
+		*  fades with the slider — its fill comes off `body` — and never frosts with it.
+		*  The dockkit exclusion has to be spelled again here: a tab menu IS a `MenuSurface`
+		*  now, and it stays owned by its own layer token, not by the menu one. */
+		const MENU_MATERIAL_SEL = `[data-menu-material]: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
@@ -3950,6 +3661,34 @@ window.__ModuleLoader__.load({
 		function menuFrost(blurVar) {
 			return hostAdapter().menus.frostDecl(`var(${blurVar},none)`);
 		}
+		/** The `<html>` classes that let the two menu groups write their frost token at all.
+		*
+		*  WHY A GATE IS NEEDED AND `:where()` IS ENOUGH: the host declares its own menu frost
+		*  on `body` (`ui-theme/src/styles/gradient-shadow-text.css` —
+		*  `--dsw-menu-backdrop-filter: blur(40px) saturate(150%)`, no media query), and every
+		*  menu frosts from that INHERITED value, whether it filters itself (the background-job
+		*  `<ul>`) or hands the value to a `MenuSurface` `.material` child. An element's own
+		*  declaration always beats what it inherits, so writing the token with a `none`
+		*  fallback does not "add no blur" at slider 0 — it DELETES the host's frost. The
+		*  result is a faded menu with nothing behind it: the page shows through it crisp and
+		*  bright, so the popup stops reading as a raised surface at all. (This is a DIFFERENT
+		*  defect from the reported "the background-job list is under the conversation" one,
+		*  which is a stacking-context injury the row takes with its own frost — see the
+		*  `z-index` note on `HEADER_BAR_RULE`. Both were live at once on `0.2.0-rc.1`.)
+		*  `none` stays correct for the exempt group: `applyExemptDefaults` pins those
+		*  surfaces at alpha 1 alongside the cleared frost, so they are opaque by design.
+		*
+		*  `:where()` keeps the gate free: this plugin's menu cascade is ORDERED (card group →
+		*  header group → exemptions) at equal specificity, and a class prefix with real
+		*  specificity would have lifted the card group over the exemption it must lose to. */
+		const CARD_FROST_GATE = "dab-card-frost";
+		const HEADER_FROST_GATE = "dab-header-frost";
+		/** Prefix every arm of a selector list with a `:where()` gate. A joined list is one
+		*  selector per entry, so prefixing the string once would gate only the first arm and
+		*  leave the rest always on. */
+		function gated(gate, selectors) {
+			return selectors.split(",").map((sel) => `:where(.${gate}) ${sel}`).join(",");
+		}
 		/** 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.
@@ -3963,7 +3702,7 @@ window.__ModuleLoader__.load({
 			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)`)}}`;
+			return `${gated(CARD_FROST_GATE, `${POPOVER_MENU_SEL},${MENU_MATERIAL_SEL}`)}{${menuFrost(CARD_BLUR_VAR)}}${POPOVER_OTHER_SEL}{${elementFrostDecl(`var(${CARD_BLUR_VAR},none)`)}}`;
 		}
 		const INPUT_FROST_CLASS = "dab-input-frost";
 		const TAKEOVER_FROST_CLASS = "dab-takeover-frost";
@@ -4043,8 +3782,48 @@ window.__ModuleLoader__.load({
 		}
 		/** The bar's paint. The variables are written by `applyHeaderBar`; the class is
 		*  only ever added when they are, so a host the plugin is not theming keeps its
-		*  own header untouched. */
-		const HEADER_BAR_RULE = `.${HEADER_BAR_CLASS}{background:var(--dsh-any-op-header-bar,transparent)!important;backdrop-filter:var(--dsh-any-blur-header-bar,none);-webkit-backdrop-filter:var(--dsh-any-blur-header-bar,none)}`;
+		*  own header untouched.
+		*
+		*  WHY THE ROW NEEDS A `z-index`: the 「标题栏」 card frosts the row, and a
+		*  `backdrop-filter` other than `none` makes the element a STACKING CONTEXT — which the
+		*  row cannot avoid wanting, since the frost is the feature. The row is not an empty
+		*  strip: the host mounts its header chrome INTO it (`conversation.session.header
+		*  .actions|.utilities|.corner`), and that chrome raises its overlays from inside the
+		*  row:
+		*    · `ui-jobs/JobListAction.module.css` — `.root{position:relative}` +
+		*      `.menu{position:absolute; top:calc(100% + 5px); z-index:100}` on every release
+		*      through `0.2.1-alpha.1` (the `{open ? <ul style={{left: menuShift}}/> : null}`
+		*      the bug was captured from; `0.2.1-alpha.2` portaled it to `body`, which is why
+		*      that build hid the symptom rather than fixed it);
+		*    · `ui-schedule/TaskMenu.module.css` — the list root carries `role="menu"` and is
+		*      `position:absolute; top:calc(100% + 4px); z-index:100` whenever the primitive is
+		*      NOT in portal mode, and it sits in `…header.utilities` on every release in range.
+		*  Once the row is a stacking context those `z-index:100`s stop being page-level values:
+		*  they only order the overlays WITHIN the row, and the row itself then paints at its
+		*  own level — under the conversation body, the composer seat and `.root`'s background,
+		*  all of which follow it in the column. The menu was not demoted by the host; it was
+		*  confined by us, and confining it is what "the list is behind the chat" meant.
+		*
+		*  THE COMPENSATION IS THE ROW'S OWN `z-index`, not a release of the frost: a `:has()`
+		*  valve dropping the blur while an overlay is open was the first attempt, and it
+		*  visibly re-tints the whole title bar every time anyone opens a header menu — the
+		*  part's two sliders appear to change state on their own. Raising the row instead keeps
+		*  the frost steady and restores the order the host assumed. The value has to clear the
+		*  in-column chrome the row hangs over — `.seat` 9 (composer), the back-to-bottom control
+		*  8, the footer 7, `.tabs` 1 (all measured from `ConversationRoot.module.css`) — while
+		*  staying UNDER every page-level surface, because the centre column is not itself a
+		*  stacking context unless the background blur is on: portaled menus/tooltips are 100,
+		*  modal overlays 1000, stat and context panels 1100 (`Menu.module.css`, `Modal.module.css`,
+		*  `ContextMeter.module.css` — the last lives in `InputBar`, NOT in this row, so the row's
+		*  filter never had to be blamed for its anchoring). 10 sits in that gap: above 9, far
+		*  below 100, so a portaled list still covers the title row exactly as the host intends.
+		*
+		*  `z-index` needs no `position` here and none is written: the row is a flex ITEM of
+		*  `ConversationRoot .root{display:flex;flex-direction:column}` on every release in range,
+		*  and z-index applies to flex items as they are. Writing `position:relative` would also
+		*  make the row a containing block — and deciding a host box's positioning is the exact
+		*  race this plugin lost once already (issue #24). */
+		const HEADER_BAR_RULE = `.${HEADER_BAR_CLASS}{background:var(--dsh-any-op-header-bar,transparent)!important;backdrop-filter:var(--dsh-any-blur-header-bar,none);-webkit-backdrop-filter:var(--dsh-any-blur-header-bar,none);z-index:10}`;
 		/** The 「标题栏」card's paint: the card's material at the card's opacity, empty
 		*  where the plugin is not theming. The conversation header row, the Windows
 		*  caption band, and — through the desktop preload's probe — the native
@@ -4103,13 +3882,37 @@ window.__ModuleLoader__.load({
 		*  plugin's own discovery (`discoverParts`), not a guessed hashed class name. The
 		*  probe selector is a verified shape: an inline style that mentions the sidebar
 		*  token on a body-level span is the desktop preload's caption probe and nothing
-		*  else, so no match means no desktop caption and the rule is inert. */
+		*  else, so no match means no desktop caption and the rule is inert.
+		*
+		*  THE BAND IS TWO REGIONS, NOT ONE. `AppFrame.module.css` paints the whole caption
+		*  with one box (`.frame::before`, `inset: 0 0 auto` at `--dsh-windows-titlebar-height`)
+		*  in `--dsw-specific-sidebar-fill` — the SIDEBAR's token — while the sidebar column
+		*  below it (`AppFrame.tsx`'s first grid track, `${cols.sidebar}px`) is the surface
+		*  that slider actually owns. The 标题栏 card took the band over in 0.3.6, which made
+		*  the strip above the sidebar follow the session title row instead of the sidebar. So
+		*  the band is now cut at the sidebar's own width:
+		*    · `::before` keeps the host's box (and its `-webkit-app-region: drag`) and is
+		*      CLIPPED to everything right of that width — `clip-path:inset(0 0 0 …)` clips
+		*      the paint AND the backdrop-filter's effect, so the region under the cut is
+		*      genuinely untouched rather than frosted twice.
+		*    · `::after` (a box `.frame` does not use on any release in range) paints exactly
+		*      that left segment from `--dsh-any-op-sidebar` — the same literal the sidebar
+		*      column is painted with — and frosts from the sidebar blur's root mirror, so the
+		*      column and the strip above it are one surface under one opacity + blur pair.
+		*  `--dsh-windows-sidebar-width` is published INLINE ON THE FRAME by the host
+		*  (`AppFrame.tsx`, Windows builds only, `${cols.sidebar}px`) and both pseudo-elements
+		*  inherit it, so the split tracks a dragged or collapsed sidebar with no observer of
+		*  our own. Collapsed is `0px`: the `::after` box vanishes and `::before` un-clips, so
+		*  the band goes back to being entirely the 标题栏 card's.
+		*  The native button block still reads the probe as `transparent`, and it sits at the
+		*  window's right edge — inside the region that stays 标题栏-owned. */
 		function applyNativeCaption(surfaces) {
 			if (!document.documentElement.hasAttribute("data-windows-titlebar")) return;
 			const src = surfaces === void 0 ? paletteTokens() ?? readHostOpacityTokens() : surfaces;
 			const fill = captionFill(src);
 			const paint = headerBarPaint(src) || fill;
-			const css = fill === "" ? "" : `${WCO_PROBE_SEL}{--dsw-specific-sidebar-fill:transparent}[data-windows-titlebar] .${CAPTION_FRAME_CLASS}::before{background:var(--dsh-any-op-header-bar,${paint})!important;backdrop-filter:var(--dsh-any-blur-header-bar,none);-webkit-backdrop-filter:var(--dsh-any-blur-header-bar,none)}[data-windows-titlebar] .${FLAT_CENTER_CLASS}{border-top-left-radius:0!important}`;
+			const width = "var(--dsh-windows-sidebar-width,0px)";
+			const css = fill === "" ? "" : `${WCO_PROBE_SEL}{--dsw-specific-sidebar-fill:transparent}[data-windows-titlebar] .${CAPTION_FRAME_CLASS}::before{background:var(--dsh-any-op-header-bar,${paint})!important;backdrop-filter:var(--dsh-any-blur-header-bar,none);-webkit-backdrop-filter:var(--dsh-any-blur-header-bar,none);clip-path:inset(0 0 0 ${width});-webkit-clip-path:inset(0 0 0 ${width})}[data-windows-titlebar] .${CAPTION_FRAME_CLASS}::after{content:"";position:absolute;top:0;left:0;width:${width};height:var(--dsh-windows-titlebar-height,40px);background:var(--dsh-any-op-sidebar,${fill});backdrop-filter:var(--dsh-any-blur-sidebar-band,none);-webkit-backdrop-filter:var(--dsh-any-blur-sidebar-band,none);-webkit-app-region:drag}[data-windows-titlebar] .${FLAT_CENTER_CLASS}{border-top-left-radius:0!important}`;
 			const el = ensureWcoStyle();
 			if (el.textContent !== css) el.textContent = css;
 			discoverParts();
@@ -4122,6 +3925,13 @@ window.__ModuleLoader__.load({
 				centerEl?.classList.add(FLAT_CENTER_CLASS);
 			}
 		}
+		/** Mirror of the sidebar-part blur on `:root`, for the caption segment above the
+		*  sidebar column. `--dsh-any-part-blur` is written INLINE on the column and the band
+		*  is a pseudo-element of the FRAME, one level up, so it can never inherit it. */
+		function applySidebarBandBlur(px) {
+			if (px > 0) document.documentElement.style.setProperty("--dsh-any-blur-sidebar-band", `blur(${px}px)`);
+			else document.documentElement.style.removeProperty("--dsh-any-blur-sidebar-band");
+		}
 		/** Mirror of the bg-part blur on :root. --dsh-any-part-blur is element-scoped
 		*  to the columns, so surfaces outside their subtree (the mobile header, or
 		*  third-party styles) can never inherit it. */
@@ -4160,7 +3970,7 @@ window.__ModuleLoader__.load({
 		*  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)}}`;
+			return `${gated(HEADER_FROST_GATE, 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}`;
@@ -4174,8 +3984,13 @@ window.__ModuleLoader__.load({
 		function applyHeaderPopovers() {
 			const root = document.documentElement;
 			const px = rBlurs().header;
-			if (px > 0) root.style.setProperty("--dsh-any-blur-header", `blur(${px}px)`);
-			else root.style.removeProperty("--dsh-any-blur-header");
+			if (px > 0) {
+				root.style.setProperty(HEADER_BLUR_VAR, `blur(${px}px)`);
+				root.classList.add(HEADER_FROST_GATE);
+			} else {
+				root.style.removeProperty(HEADER_BLUR_VAR);
+				root.classList.remove(HEADER_FROST_GATE);
+			}
 			let opacity = rHeaderOpacity();
 			if (opacity < 0) opacity = 0;
 			if (opacity > 1) opacity = 1;
@@ -4243,7 +4058,7 @@ window.__ModuleLoader__.load({
 		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}",
+			"[role=\"menu\"]:not([data-dockkit-tab-menu]),[data-menu-material]: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,${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}`,
 			`.${HEADER_BAR_CLASS}{-webkit-text-stroke:var(--dsh-any-stroke-headerBar-w,0px) var(--dsh-any-stroke-headerBar-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}`,
@@ -4382,7 +4197,7 @@ window.__ModuleLoader__.load({
 			if (typeof getComputedStyle !== "undefined") stack = getComputedStyle(document.documentElement).getPropertyValue("--dsw-font-family").trim();
 			if (stack === "") stack = "-apple-system, BlinkMacSystemFont, 'Segoe UI', 'PingFang SC', sans-serif";
 			const fmt = fontFormatForMime(mime);
-			fontStyleEl.textContent = `@font-face{font-family:'${FONT_FAMILY}';src:url('${url}') format('${fmt}');font-display:swap}body{--dsw-font-family:'${FONT_FAMILY}',${stack}}input,textarea,select,button{font-family:var(--dsw-font-family)}`;
+			fontStyleEl.textContent = `@font-face{font-family:'${FONT_FAMILY}';src:url('${url}') format('${fmt}');font-display:swap}body{--dsw-font-family:'${FONT_FAMILY}',${stack}!important}input,textarea,select,button{font-family:var(--dsw-font-family)}`;
 		}
 		/** Teardown only: drop the @font-face + token override. */
 		function removeFontFace() {
@@ -4705,10 +4520,17 @@ window.__ModuleLoader__.load({
 		/** Blur of the option panels inside the settings dialog (.dab-card), owned by
 		*  the "dialog option panel" (card) blur slider. Written as a plugin-owned
 		*  variable consumed by SETTINGS_STYLE_RULE — deliberately NOT applied to the
-		*  homepage center column, which this slider must never touch. */
+		*  homepage center column, which this slider must never touch. The gate class is
+		*  what hands the menu frost token over at all (see `CARD_FROST_GATE`). */
 		function applyCardPanelsBlur(px) {
-			if (px > 0) document.documentElement.style.setProperty("--dsh-any-blur-card-panels", `blur(${px}px)`);
-			else document.documentElement.style.removeProperty("--dsh-any-blur-card-panels");
+			const root = document.documentElement;
+			if (px > 0) {
+				root.style.setProperty(CARD_BLUR_VAR, `blur(${px}px)`);
+				root.classList.add(CARD_FROST_GATE);
+			} else {
+				root.style.removeProperty(CARD_BLUR_VAR);
+				root.classList.remove(CARD_FROST_GATE);
+			}
 		}
 		/** Apply per-part interface blur to the AppFrame columns + settings panel. */
 		function applyPartBlurs(blurs) {
@@ -4718,6 +4540,7 @@ window.__ModuleLoader__.load({
 			setBlur(centerEl, blurs.bg);
 			setBlur(rightEl, 0);
 			applyBgBlurGlobal(blurs.bg);
+			applySidebarBandBlur(blurs.sidebar);
 			applyCardPanelsBlur(blurs.card);
 			applySettingsBlur(blurs.settings);
 			applyInputBlur(blurs.input);
@@ -4788,7 +4611,10 @@ window.__ModuleLoader__.load({
 			if (part === "bg") {
 				setBlur(centerEl, v);
 				applyBgBlurGlobal(v);
-			} else setBlur(sidebarEl, v);
+				return;
+			}
+			setBlur(sidebarEl, v);
+			applySidebarBandBlur(v);
 		}
 		const VIEW_CARDS = [{
 			sel: "[data-chat-flow]",
@@ -5435,10 +5261,11 @@ window.__ModuleLoader__.load({
 				const name = set[k];
 				if (name) document.documentElement.style.removeProperty(name);
 			}
-			document.documentElement.classList.remove(INPUT_FROST_CLASS);
+			document.documentElement.classList.remove(INPUT_FROST_CLASS, CARD_FROST_GATE, HEADER_FROST_GATE);
 			applyTakeoverFrost(0);
 			document.documentElement.style.removeProperty("--dsh-any-op-header-bar");
 			document.documentElement.style.removeProperty("--dsh-any-blur-header-bar");
+			document.documentElement.style.removeProperty("--dsh-any-blur-sidebar-band");
 			document.querySelectorAll(`.${HEADER_BAR_CLASS}`).forEach((el) => el.classList.remove(HEADER_BAR_CLASS));
 			headerBarEl = null;
 			frameEl?.classList.remove(CAPTION_FRAME_CLASS);