dsh-zen-remote 1.1.5 → 1.1.7

package/README.md

@@ -3,7 +3,7 @@
 
 <p align="center">
 <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-0B7285?style=flat-square" alt="MIT"></a>
-<img src="https://img.shields.io/badge/release-v1.1.5-5B4CF0?style=flat-square" alt="v1.1.5">
+<img src="https://img.shields.io/badge/release-v1.1.7-5B4CF0?style=flat-square" alt="v1.1.7">
 <img src="https://img.shields.io/badge/DSH-Web%20Profile-5B4CF0?style=flat-square" alt="DSH Web Profile">
 </p>
 
@@ -39,7 +39,7 @@ dsh plugin add dsh-zen-remote
 ```jsonc
 {
   "dependencies": {
-    "dsh-zen-remote": "^1.1.5"        // 本地开发换成 "link:/path/to/dsh-zen-remote"
+    "dsh-zen-remote": "^1.1.7"        // 本地开发换成 "link:/path/to/dsh-zen-remote"
   },
   "dsh": { "profile": { "bundles": [
     "@deepseek-ai/dsh-base",

package/lib/client.js

@@ -3987,6 +3987,13 @@ exports.HEADER_CSS = `/* ---------- session header five-piece reflow (< 768px) -
      widths, only the center 1fr column shrinks by 16px. */
   [data-phase] header {
     position: relative;
+    /* Above the scroller's plain and relative-positioned message content, so
+       the ::after fade strip below actually paints over the messages sliding
+       under it (positioned z-auto boxes otherwise win by DOM order — the
+       scroller comes after the header). Deliberately tiny: the seat (7),
+       scroll-to-bottom (8) and every overlay this plugin owns (30+) stay
+       above. */
+    z-index: 2;
     padding: 0 8px 28px !important;
   }
   /* No header bottom line — fade instead (real-device round 2, 2026-08-17).
@@ -3994,14 +4001,20 @@ exports.HEADER_CSS = `/* ---------- session header five-piece reflow (< 768px) -
      \`border-bottom\` on the header itself is transparent, just a layout
      reserve — dsh-client-ui-conversation lib/client.js ".wSkVaW_header{
      border-bottom:1px solid #0000}.wSkVaW_header:after{...height:1px;
-     position:absolute;bottom:1px...}", verified live 2026-08-17), so
-     hiding the pseudo-element is enough; the header's own border-bottom
-     never had a visible color to begin with. The message scroller now
-     fades in from under the header instead (styles/composer.css.ts, "no
-     divider above OR below the message list" — the two edges share one
-     mask-image on [class$="_scrollBody"]). */
+     position:absolute;bottom:1px...}", verified live 2026-08-17), so the
+     bar is repurposed rather than hidden: restyled into a 20px strip
+     hanging just below the header that fades the messages in — the same
+     look the scroller's mask-image used to produce, without a mask on a
+     scroll container (iOS WebKit renders that as fog over the header, see
+     composer.css.ts "no divider above OR below the message list",
+     2026-08-23). color-mix instead of the transparent keyword: the host
+     writes its own seat gradient that way, and plain \`transparent\` is
+     rgba(0,0,0,0) — WebKit interpolates it through grey. */
   [data-phase] header::after {
-    display: none !important;
+    height: 20px !important;
+    top: 100% !important;
+    bottom: auto !important;
+    background: linear-gradient(to bottom, var(--dsw-alias-bg-base), color-mix(in srgb, var(--dsw-alias-bg-base) 0%, transparent)) !important;
   }
   /* grid-row: 1 on every item is load-bearing, not decoration (S2.1 fix for
      the "标题被挤下去" report). The three items are placed with explicit
@@ -4673,22 +4686,29 @@ exports.COMPOSER_CSS = `/* ---------- phone composer (< 768px) ---------- */
   }
 
   /* --- 6. no divider above OR below the message list ---
-     Instead of a rule the messages butt against, the message scroller
-     fades out over its last 26px (S3, no divider above the composer) AND
-     fades in over its first 20px (S3.1 real-device round 2: the header's
-     own bottom line is removed too, styles/header.css.ts's
-     \`header::after\` rule). The mask lives on the scroll body (NOT on the
-     header or the composer): a mask clips everything it paints, and both
-     surfaces host position:fixed children (composer's permission/model
-     sheets, any future header overlay) that must not be clipped.
-     \`mask-image\` can only be declared once per element, so both fades are
-     ONE linear-gradient rather than two separate declarations (the second
-     would silently replace the first) — this is the merge of what used to
-     be S3's bottom-only mask. */
-  [class$="_scrollBody"] {
-    -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 20px, #000 calc(100% - 26px), transparent 100%);
-    mask-image: linear-gradient(to bottom, transparent 0, #000 20px, #000 calc(100% - 26px), transparent 100%);
-  }
+     Instead of a rule the messages butt against, they fade near both edges.
+     This used to be ONE mask-image on the message scroller; iOS WebKit
+     turned that into fog over the header (user report 2026-08-23): a mask
+     on a scroll container is applied in CONTENT coordinates there (the fade
+     bands scroll away with the messages) and, worse, it breaks the
+     container's own overflow clipping — content scrolled out of view keeps
+     painting, straight over the header and status bar. Engine bug with no
+     iOS escape hatch (every iOS browser is WebKit), so the fades moved off
+     the scroller entirely:
+
+     - fade-IN under the header: the header's own ::after, restyled into a
+       20px gradient strip — styles/header.css.ts ("no header bottom line").
+     - fade-OUT above the composer: nothing of ours. The official composer
+       seat already carries \`background: linear-gradient(transparent 0,
+       bg 36px)\` on its sticky self (dsh-client-ui-conversation lib/
+       client.js .wSkVaW_composerSeat) and that is the entire visible
+       effect; the mask's own bottom band landed inside the safe-area
+       padding below the card and painted nothing. If the bottom edge ever
+       reads harsh, hang a ::before strip off the seat the same way the
+       header does — do NOT put a mask back on the scroller.
+
+     Painted strips instead of a mask is a fair trade only because the page
+     background is one flat color — which it is (--dsw-alias-bg-base). */
   [class$="_composerSeat"],
   [class$="_composerStack"] {
     border-top: none !important;
@@ -5485,6 +5505,14 @@ const PHONE_QUERY = '(max-width: 767px)';
  *   `=0` opts back out). */
 const DESKTOP_KEY = 'dsh-mobile-nav.turn-fold-desktop';
 const DESKTOP_PARAM = 'mobile-nav-turn-fold';
+/** Last answer the row config gave. The fetch is a round-trip and the phone
+ * breakpoint is not, so a desktop reader used to watch a whole session render
+ * unfolded and then collapse at once, every page load (issue #3). Remembering
+ * the answer switches the fold on before first paint from the second load on.
+ * Enable-only: turning the row knob back off clears this, so that load still
+ * folds and the next one does not — a stale fold is a chip click away, a
+ * one-way `disableDesktop` is a state machine nobody asked for. */
+const DESKTOP_CACHE_KEY = 'dsh-mobile-nav.turn-fold-desktop-seen';
 /** Root attribute the stylesheet keys the width-independent rules on. */
 const DESKTOP_ATTR = 'data-mnav-desktop-fold';
 /** Read (and, when the URL param is present, persist) the per-browser opt-in. */
@@ -5523,10 +5551,12 @@ const TURN_HEAD_KINDS = new Set(['user', 'steering']);
 /** ReasoningRow's own marker (lib/client.js:8966) — the Think disclosure
  * rendered inside an assistant-step row, beside that step's prose. */
 exports.THINK = '[data-variant="think"]';
-/** Attribute the phone stylesheet turns into `display: none`. Still written
- * per element for the one case the stylesheet cannot express on its own: an
- * assistant-step row whose entire body is reasoning, which has to go as a
- * whole row (see {@link foldsWholeRow}). */
+/** Attribute the phone stylesheet turns into `display: none`. Written for the
+ * one case the stylesheet cannot express on its own: an assistant-step row
+ * whose entire body is reasoning, which has to go as a whole row (see
+ * {@link foldsWholeRow}). Because it is the only thing hiding that row, it is
+ * written from {@link markWholeRows} in the observer callback rather than the
+ * scan a frame later — see that function for what the frame cost. */
 const FOLD = 'data-mnav-fold';
 /** Per-item override written while its turn is expanded. */
 exports.OPEN = 'data-mnav-fold-open';
@@ -5537,6 +5567,8 @@ exports.OPEN = 'data-mnav-fold-open';
  * flashes in, then folds away" report, 2026-08-22); it also keeps the
  * stylesheet a no-op — content visible — if this effect never runs. */
 const ACTIVE_ATTR = 'data-mnav-fold-on';
+/** Selector of the one row kind that can fold whole — see {@link foldsWholeRow}. */
+const STEP_SELECTOR = '[data-chat-flow-kind="assistant-step"]';
 /**
  * True when the reasoning rows are the ONLY thing this row renders, so the
  * whole flow item has to go: the flow column is `display: flex` with
@@ -5707,14 +5739,73 @@ function installTurnFold(ctx) {
             // its row-level fold after prose started arriving in the same DOM node
             // (React updates the row in place), hiding the streaming reply until a
             // completion re-render rebuilt the row — the "reply only appears when
-            // the turn finishes" phone bug (2026-08-18).
-            for (const stale of flow.querySelectorAll(`[${FOLD}]`)) {
+            // the turn finishes" phone bug (2026-08-18). {@link OPEN} needs the
+            // same sweep on its own account: it is what releases a row from the
+            // stylesheet's reasoning rules, so a stale one shows the reasoning of
+            // a turn the reader has since folded.
+            for (const stale of flow.querySelectorAll(`[${FOLD}], [${exports.OPEN}]`)) {
                 if (liveItems.has(stale))
                     continue;
                 stale.removeAttribute(FOLD);
                 stale.removeAttribute(exports.OPEN);
             }
         };
+        /**
+         * Fold (or release) the reasoning-only rows this mutation batch touched,
+         * synchronously.
+         *
+         * The full {@link scan} is rAF-coalesced, and React commits after that
+         * frame's rAF phase, so a scan scheduled from a mutation lands one PAINTED
+         * frame later. For everything else that is invisible — the stylesheet
+         * already hid it by the host's own markers before the effect looked. For
+         * the whole-row fold, which nothing but {@link FOLD} hides, the reader saw
+         * that frame: a blank 16px band on the way in (the flow column's gap,
+         * which an emptied flex item still claims), and — worse — the row still
+         * hidden for a frame after prose started arriving into it, so the reply
+         * appeared to stutter (issue #3).
+         *
+         * A MutationObserver callback is a microtask: it runs at the end of the
+         * task that mutated the DOM, before that frame's rendering update. Marking
+         * here is therefore never a frame late, in either direction.
+         *
+         * ponytail: O(rows touched by the batch), not O(rows). If streaming ever
+         * feels heavy, the cheap win is skipping batches whose records are all
+         * characterData — the fold verdict only changes when elements do.
+         */
+        const markWholeRows = (records) => {
+            const rows = new Set();
+            for (const record of records) {
+                const target = record.target;
+                if (target instanceof Element) {
+                    const row = target.closest(STEP_SELECTOR);
+                    if (row !== null)
+                        rows.add(row);
+                }
+                for (const node of record.addedNodes) {
+                    if (!(node instanceof Element))
+                        continue;
+                    if (node.matches(STEP_SELECTOR))
+                        rows.add(node);
+                    for (const nested of node.querySelectorAll(STEP_SELECTOR))
+                        rows.add(nested);
+                }
+            }
+            for (const row of rows) {
+                // Exactly what {@link groupsOf} walks: a direct child of the chat flow
+                // column. This is the scoping that keeps the effect Chat-only — the
+                // mutation records reach the whole document, so without it a row in
+                // any other view that seats chat nodes would get hidden with no chip
+                // to bring it back. It also drops rows detached since the batch.
+                const parent = row.parentElement;
+                if (parent === null || !parent.matches(FLOW))
+                    continue;
+                const thinks = [...row.querySelectorAll(exports.THINK)];
+                if (thinks.length > 0 && foldsWholeRow(row, thinks))
+                    row.setAttribute(FOLD, '');
+                else
+                    row.removeAttribute(FOLD);
+            }
+        };
         const schedule = () => {
             // The locale subscription below lives outside attach/detach, so this
             // guard is what keeps a late dictionary registration from marking up
@@ -5750,7 +5841,7 @@ function installTurnFold(ctx) {
         const clear = () => {
             for (const chip of document.querySelectorAll(CHIP_SELECTOR))
                 chip.remove();
-            for (const item of document.querySelectorAll(`[${FOLD}]`)) {
+            for (const item of document.querySelectorAll(`[${FOLD}], [${exports.OPEN}]`)) {
                 item.removeAttribute(FOLD);
                 item.removeAttribute(exports.OPEN);
             }
@@ -5759,7 +5850,10 @@ function installTurnFold(ctx) {
             if (observer !== null)
                 return;
             document.documentElement.setAttribute(ACTIVE_ATTR, '');
-            observer = new MutationObserver(schedule);
+            observer = new MutationObserver((records) => {
+                markWholeRows(records);
+                schedule();
+            });
             observer.observe(document.body, { childList: true, subtree: true });
             document.addEventListener('click', onClick);
             scan();
@@ -5793,12 +5887,22 @@ function installTurnFold(ctx) {
         if (narrow.matches)
             attach();
         narrow.addEventListener('change', onChange);
-        if (desktopOptIn())
+        // Both switches are synchronous reads, so a returning reader folds before
+        // first paint. Not awaited before phone attach either — folding must not
+        // wait on a round-trip.
+        if (desktopOptIn() || localStorage.getItem(DESKTOP_CACHE_KEY) === '1')
             enableDesktop();
-        // The row config arrives async; a late enable just attaches then. Not
-        // awaited before phone attach — folding must not wait on a round-trip.
-        else
-            void desktopConfigured().then((on) => (on ? enableDesktop() : undefined));
+        // The row config still arrives async, and remains the authority: a late
+        // yes attaches then and is remembered, a no forgets. A late answer after
+        // dispose is a no-op inside enableDesktop.
+        void desktopConfigured().then((on) => {
+            if (on) {
+                localStorage.setItem(DESKTOP_CACHE_KEY, '1');
+                enableDesktop();
+            }
+            else
+                localStorage.removeItem(DESKTOP_CACHE_KEY);
+        });
         // A language switch changes the chip copy of every already-rendered turn.
         const stopLocale = ctx.locale.subscribe(schedule);
         return () => {
@@ -5835,6 +5939,8 @@ exports.TURN_FOLD_CSS = void 0;
 const turn_fold_ts_1 = require("./effects/turn-fold.js");
 /** Mirror of the root attribute effects/turn-fold.ts holds while attached. */
 const ACTIVE = 'data-mnav-fold-on';
+/** One assistant-step row, inside an active fold. */
+const STEP = `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="assistant-step"]`;
 /**
  * Born folded — the reason a new tool call no longer blinks into view.
  *
@@ -5851,21 +5957,43 @@ const ACTIVE = 'data-mnav-fold-on';
  * block is live for exactly the widths the fold is, and hides nothing at all
  * when the effect never ran.
  *
- * One case stays with the effect: an assistant-step row whose whole body is
- * reasoning has to be hidden as a row (an emptied-out flex item still claims
- * the flow column's 16px gap), and "this row has nothing but Think in it" is
- * not a selector. Its rows therefore still fold a frame late — as blank
- * space, not as content, since the Think rows below are hidden here.
+ * The Think rule reads {@link OPEN} off the ROW as well as off the block:
+ * a row folded whole (see {@link WHOLE_STEP}) is the item the effect marks,
+ * so an expanded turn carries the override on the row and its reasoning
+ * would otherwise stay hidden behind this rule — the reader clicked the chip
+ * and got an empty band (issue #3, 2026-08-25).
  */
 const BORN_FOLDED = [
     ...turn_fold_ts_1.PROCESS_KINDS.map((kind) => `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="${kind}"]:not([${turn_fold_ts_1.OPEN}])`),
-    `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="assistant-step"] ${turn_fold_ts_1.THINK}:not([${turn_fold_ts_1.OPEN}])`,
+    `${STEP}:not([${turn_fold_ts_1.OPEN}]) ${turn_fold_ts_1.THINK}:not([${turn_fold_ts_1.OPEN}])`,
 ].join(',\n');
+/*
+ * The one folded item with no selector of its own: an assistant-step row that
+ * holds reasoning and nothing else. It has to go as a ROW — the flow column is
+ * `display: flex` with `gap: 16px`, so a row whose every child is hidden still
+ * claims its gap and the reader sees a blank band — and "this row has nothing
+ * but Think in it" cannot be written as a selector.
+ *
+ * `:has()` looks like it can: "holds reasoning, holds no content block that is
+ * not reasoning". It cannot, safely. Every wrapper between the row and the
+ * blocks is itself a non-reasoning element, so the guard has to name the exact
+ * depth of the blocks — and the real tree is
+ * flowItem > seat > AssistantMarkdown root > body > blocks, one level deeper
+ * than the host's own component suggests, because the slot seat adds a wrapper
+ * the component never sees. A selector pinned to that depth silently stops
+ * matching the day a wrapper moves, with nothing to say why.
+ *
+ * So the row stays with effects/turn-fold.ts, which walks the tree instead of
+ * assuming its shape — but marks it synchronously in the MutationObserver
+ * callback (a microtask, before the frame paints) rather than a rAF later.
+ */
 /** The fold + chip rules, with every selector prefixed by `scope`. */
 const rules = (scope) => `
-  /* Folded process: tool-call / context / command rows and the Think
-     disclosures inside an assistant step. !important because the official
-     flow item and ReasoningRow both set their own display. */
+  /* The reasoning-only row (see above), which effects/turn-fold.ts marks
+     itself because no selector can find it. Everything else is already hidden
+     by BORN_FOLDED, by the host's own markers — this rule is what that one
+     case rides on. !important because the official flow item and ReasoningRow
+     both set their own display. */
   ${scope} [data-mnav-fold]:not([data-mnav-fold-open]) {
     display: none !important;
   }

package/lib/types/client/effects/turn-fold.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"turn-fold.d.ts","sourceRoot":"","sources":["../../../../src/client/effects/turn-fold.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAA;AA0C3E;;;;;;;sDAOsD;AACtD,eAAO,MAAM,aAAa,8CAA+C,CAAA;AAMzE;sEACsE;AACtE,eAAO,MAAM,KAAK,6BAA2B,CAAA;AAO7C,4DAA4D;AAC5D,eAAO,MAAM,IAAI,wBAAwB,CAAA;AAyFzC;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CA0JxD"}
+{"version":3,"file":"turn-fold.d.ts","sourceRoot":"","sources":["../../../../src/client/effects/turn-fold.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAA;AAkD3E;;;;;;;sDAOsD;AACtD,eAAO,MAAM,aAAa,8CAA+C,CAAA;AAMzE;sEACsE;AACtE,eAAO,MAAM,KAAK,6BAA2B,CAAA;AAS7C,4DAA4D;AAC5D,eAAO,MAAM,IAAI,wBAAwB,CAAA;AA4FzC;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CAyNxD"}

package/lib/types/client/styles/composer.css.d.ts

@@ -1,2 +1,2 @@
-export declare const COMPOSER_CSS = "/* ---------- phone composer (< 768px) ---------- */\n\n/* The file picker the attachment button drives (S7) \u2014 hidden at EVERY width,\n   deliberately OUTSIDE the phone media block below. A bare <input type=\"file\">\n   renders as a native \"Choose Files\" control, and the slot wrapper around it is\n   `display: contents`, so an un-hidden one becomes a flex item of the official\n   tool row. Scoping this to < 768px once put that control in the DESKTOP\n   composer (caught on a live deploy, 2026-08-17): the button that drives it is\n   phone-only, but the input it drives is in the DOM at all widths. */\n[data-mobile-nav=\"attach-picker\"] {\n  display: none !important;\n}\n\n@media (max-width: 767px) {\n  /* --- 1. flatten the two official groups ---\n     `_tools` and `_trailing` only exist to cluster controls left/right.\n     display:contents dissolves them into `_row`, so the six leaf controls\n     become siblings in one flex line and `order` alone drives the layout:\n     [attach \u00B7 + \u00B7 permission \u00B7 model] \u2026elastic gap\u2026 [context ring \u00B7 send]. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] {\n    justify-content: flex-start !important;\n    gap: 5px !important;\n    padding: 2px 8px 8px !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] {\n    display: contents !important;\n  }\n\n  /* --- 2. the running order ---\n     The attachment button (S3 placeholder, S7 wires it up) sits leftmost;\n     the official \"+\" command menu keeps its seat right next to it, where\n     the two \"insert something\" affordances read as one cluster. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] [data-mobile-nav=\"attach\"] {\n    order: 1 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_add\"] {\n    order: 2 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] {\n    order: 3 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    gap: 6px !important;\n  }\n  /* The model seat carries the elastic gap: everything after it is pushed to\n     the right edge, so no spacer element is needed. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] {\n    order: 4 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    margin-right: auto !important;\n  }\n  /* Third-party input.right entries park next to the ring rather than\n     landing at order 0 (= far left) once the groups are flattened. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.right\"] > * {\n    order: 5 !important;\n  }\n  /* ContextMeter \u2014 the only `span` ending in _root inside the row. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > span[class$=\"_root\"] {\n    order: 6 !important;\n    flex: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    order: 7 !important;\n  }\n\n  /* --- 3. permission + model as icon-only pills (real-device round 2, 2026-08-17) ---\n     S3's icon-and-label capsules read as noise on an actual phone \u2014 there\n     is no room to usefully show a preset name or a model id, so the label\n     text is now hidden outright and both triggers collapse to a plain\n     ~44x30 icon button. This AGREES with (rather than fights) the official\n     container query (`@container (width <= 460px) { .trigger:has(.triggerIcon)\n     .triggerLabel { display: none } }`) that S3 had to override \u2014 no need\n     to override it back. Accessible name is unaffected: both official\n     triggers already ship a descriptive aria-label independent of the\n     visible text (PermissionSelect: t('input.accessMode', {name}); the\n     model trigger: t('trigger.aria'/'trigger.ariaEffort')) \u2014 verified live\n     in dsh-client-ui-conversation / dsh-client-ui-model-selection lib/\n     client.js, 2026-08-17 \u2014 so hiding the label costs nothing for screen\n     readers. The permission trigger only renders an icon for the\n     \"read-only\" / \"workspace-write\" presets (permissionGlyphs in\n     dsh-client-ui-conversation) \u2014 \"Full access\" and any host-configured\n     preset name fall back to chevron-only, a known gap in the official\n     markup this plugin cannot fill without inventing new icon meaning.\n     The model trigger never renders an icon at all (only label + optional\n     effort text + chevron), so its ::before below draws one from a\n     primitives icon path (Sparkle \u2014 the closest existing \"model\" glyph) as\n     a CSS-only pseudo-element: it survives React re-renders for free\n     (unlike a DOM-injected node, which would need a MutationObserver, see\n     the preview-full-toggle pitfall in AGENTS.md) and does not touch\n     accessible-name computation (empty generated content). S3's\n     rtl-ellipsis trick on the model label is simply inert under\n     display:none now; left alone rather than unpicked. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [class$=\"_triggerLabel\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"] > [class$=\"_triggerLabel\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"] > [class$=\"_triggerEffort\"] {\n    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] button[class$=\"_trigger\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"] {\n    background: var(--dsw-specific-selector, rgba(127, 127, 127, .12)) !important;\n    width: 44px !important;\n    height: 30px !important;\n    max-width: none !important;\n    min-width: 0 !important;\n    padding: 0 !important;\n    gap: 2px !important;\n    justify-content: center !important;\n    border-radius: 999px !important;\n    touch-action: manipulation !important;\n  }\n  /* PermissionSelect wraps its trigger in the Menu primitive's root span,\n     which must shrink to the icon button's fixed width. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] > span:has(> button[class$=\"_trigger\"]) {\n    flex: 0 0 auto !important;\n    min-width: 0 !important;\n  }\n  /* ic_ds_sparkle_16 (@deepseek-ai/dsh-client-ui-primitives IconSparkle16\n     path, copied verbatim) as a mask so it inherits currentColor like every\n     other icon in the row \u2014 the model trigger has no official icon slot to\n     hook into. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"]::before {\n    content: '';\n    width: 16px;\n    height: 16px;\n    flex: none;\n    background: currentColor;\n    -webkit-mask-image: url(\"data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M6.1 3.1Q6.6 7.8 11.3 8.3Q6.6 8.8 6.1 13.5Q5.6 8.8 0.9 8.3Q5.6 7.8 6.1 3.1Z'/%3E%3Cpath d='M11.9 1Q12.2 3.7 14.9 4Q12.2 4.3 11.9 7Q11.6 4.3 8.9 4Q11.6 3.7 11.9 1Z'/%3E%3C/svg%3E\");\n    mask-image: url(\"data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M6.1 3.1Q6.6 7.8 11.3 8.3Q6.6 8.8 6.1 13.5Q5.6 8.8 0.9 8.3Q5.6 7.8 6.1 3.1Z'/%3E%3Cpath d='M11.9 1Q12.2 3.7 14.9 4Q12.2 4.3 11.9 7Q11.6 4.3 8.9 4Q11.6 3.7 11.9 1Z'/%3E%3C/svg%3E\");\n    -webkit-mask-size: contain;\n    mask-size: contain;\n    -webkit-mask-repeat: no-repeat;\n    mask-repeat: no-repeat;\n  }\n\n  /* --- 4. both menus become bottom sheets ---\n     The permission menu is the Menu primitive (role=menu, absolute, side=top)\n     and the model menu is ModelSelect's own `_menu` (absolute, bottom+right).\n     Neither has a transformed ancestor between it and the viewport, so\n     position:fixed re-anchors both to the screen edge. Only the shell moves \u2014\n     the items, the two-level model panes and every selection handler stay\n     official. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"] {\n    position: fixed !important;\n    left: 0 !important;\n    right: 0 !important;\n    bottom: 0 !important;\n    top: auto !important;\n    transform: none !important;\n    width: 100% !important;\n    min-width: 0 !important;\n    max-width: none !important;\n    max-height: min(70dvh, 520px) !important;\n    box-sizing: border-box !important;\n    border-radius: 16px 16px 0 0 !important;\n    border-bottom: none !important;\n    padding: 8px 8px calc(8px + var(--mnav-sab)) !important;\n    z-index: 60 !important;\n    box-shadow: 0 -8px 32px rgba(0, 0, 0, .18) !important;\n  }\n  /* 44pt+ rows in both sheets (Menu items, model options, and the model\n     sheet's two root cells that drill into the model / effort panes). */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"] [role=\"menuitem\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"] [class$=\"_option\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"] [class$=\"_cell\"] {\n    min-height: 48px !important;\n    border-radius: 12px !important;\n    font-size: 15px !important;\n  }\n  /* --- 4b. the official scroll-to-bottom button must not poke through the\n     sheet (real-device follow-up, 2026-08-17) ---\n     ChatView's own \"jump to latest\" button (aria-label t(\"chat.toBottom\"))\n     is `position: sticky; z-index: 8` inside the message column, not\n     `position: fixed` \u2014 it never escapes to the same top-level stacking\n     context our sheets get promoted to, so raising the sheet's z-index\n     further does nothing (measured live: it still rendered on top at\n     z-index 60 vs 8). Rather than chase engine-specific stacking-context\n     semantics (Chromium and WebKit do not always agree here \u2014 see AGENTS.md\n     CDP/document.hidden lesson for another instance of that), this hides\n     the button outright while either sheet is open and lets it reappear on\n     close: a plain `display: none` behind a live `:has()` read is correct\n     regardless of which stacking rules the engine happens to apply.\n     Selector: no hashed classes (dsh-client-ui-conversation lib/client.js,\n     verified 2026-08-17) \u2014 `data-chat-flow` is the one stable attribute on\n     the message column, and the button's wrapper is its only sibling\n     (ChatView only ever renders the column and, conditionally, this one\n     slot), so the adjacent-sibling combinator pins it precisely. */\n  body:has([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"]) [data-chat-flow] + div,\n  body:has([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"]) [data-chat-flow] + div {\n    display: none !important;\n  }\n  /* --- 5. input box: two lines minimum, five lines maximum ---\n     The official autosizer drives the box off the hidden mirror's height, so\n     a min-height on the mirror IS the min-height of the field; the scroll cap\n     rides the official custom property. 52px = 2 x 24px line box + 4px pad,\n     124px = 5 lines. The hero card keeps its own one-line collapse (misc.css\n     pins _scroll/_grow while the placeholder shows). */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] [class$=\"_mirror\"] {\n    min-height: 52px !important;\n  }\n  [class$=\"_composerSeat\"] {\n    --dsh-composer-text-max-height: 124px;\n  }\n\n  /* --- 6. no divider above OR below the message list ---\n     Instead of a rule the messages butt against, the message scroller\n     fades out over its last 26px (S3, no divider above the composer) AND\n     fades in over its first 20px (S3.1 real-device round 2: the header's\n     own bottom line is removed too, styles/header.css.ts's\n     `header::after` rule). The mask lives on the scroll body (NOT on the\n     header or the composer): a mask clips everything it paints, and both\n     surfaces host position:fixed children (composer's permission/model\n     sheets, any future header overlay) that must not be clipped.\n     `mask-image` can only be declared once per element, so both fades are\n     ONE linear-gradient rather than two separate declarations (the second\n     would silently replace the first) \u2014 this is the merge of what used to\n     be S3's bottom-only mask. */\n  [class$=\"_scrollBody\"] {\n    -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 20px, #000 calc(100% - 26px), transparent 100%);\n    mask-image: linear-gradient(to bottom, transparent 0, #000 20px, #000 calc(100% - 26px), transparent 100%);\n  }\n  [class$=\"_composerSeat\"],\n  [class$=\"_composerStack\"] {\n    border-top: none !important;\n  }\n\n  /* --- 7. dock entries become mini chips above the input card ---\n     conversation.input.dock is display:contents (inline style), so its\n     entries are stacked rows of the composer column. Forcing the slot itself\n     to flex turns them into ONE scrollable chip line outside and above the\n     card. Written against the slot, not against any particular plugin's chip\n     (the git branch chip and the todo panel are third-party and may not be\n     installed at all). */\n  [data-slot=\"conversation.input.dock\"] {\n    display: flex !important;\n    flex-flow: row nowrap !important;\n    align-items: center !important;\n    gap: 6px !important;\n    min-width: 0 !important;\n    margin: 0 16px !important;\n    overflow-x: auto !important;\n    overflow-y: hidden !important;\n    scrollbar-width: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"]::-webkit-scrollbar {\n    display: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > * {\n    flex: 0 0 auto !important;\n    max-width: 70% !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    border-radius: 999px !important;\n    font-size: 11.5px !important;\n    line-height: 18px !important;\n    overflow: hidden !important;\n  }\n  /* The git-graph chip carries a 34px tablet target from misc.css; that\n     selector is more specific, so restate it at the phone breakpoint. */\n  [data-slot=\"conversation.input.dock\"] [data-gitgraph-chip-anchor] [data-gitgraph-chip] {\n    min-height: 26px !important;\n    padding: 0 10px !important;\n    font-size: 11.5px !important;\n  }\n  /* --- 7a. the native to-do card opts OUT of the 26px pill cage ---\n     conversation.input.dock is not only a chip rail: DSH's own TodoPanel\n     (dsh-client-ui-conversation) registers here, and it is an expandable\n     card, not a pill \u2014 tapping its header renders the to-do list INSIDE\n     itself. The cage's max-height:26px + overflow:hidden left that list\n     rendered but clipped to nothing, so on a phone the bar looked dead:\n     aria-expanded flipped, 8 rows mounted at 216px, and the card still\n     painted 26px tall (measured live, 2026-08-20). Give it the official\n     geometry back \u2014 full row, natural height, 12px radius. Its list caps\n     itself at 180px with its own scroller, so this cannot run into the\n     composer. Anchored on the official data-testid, a stable contract\n     marker rather than a hashed class name. */\n  [data-slot=\"conversation.input.dock\"] > [data-testid=\"todo-panel\"] {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    overflow: visible !important;\n    border-radius: 12px !important;\n    /* The cage shrinks dock text to 11.5px/18px; the card's rows inherit it\n       and turn cramped. Restore the official 13px body scale. */\n    font-size: 13px !important;\n    line-height: normal !important;\n  }\n\n  /* --- 7b. attachment chips (S7.1) ---\n     Our own dock entry opts OUT of the 26px pill cage above: an image chip is\n     a 48px tile. The row sits tight under the card's top edge, so the chips\n     read as part of the composer rather than as a floating strip.\n\n     It also takes the LAST line of its own (line policy in 7c): a 48px tile\n     beside the to-do chip on one nowrap line squeezed that chip down to an\n     unreadable stub, with a long file name pushing the rest off-screen\n     (reported 2026-08-22). Its own chips wrap rather than overflow, so\n     several attachments stack instead of scrolling out of reach. */\n  [data-slot=\"conversation.input.dock\"] > [data-mobile-nav=\"attach-chips\"] {\n    display: flex !important;\n    flex: 1 0 100% !important;\n    flex-wrap: wrap !important;\n    order: 2 !important;\n    align-items: center !important;\n    gap: 6px !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    border-radius: 0 !important;\n    overflow: visible !important;\n    margin-bottom: -2px;\n  }\n\n  /* --- 7c. the queue strip opts OUT of the cage, on a line of its own ---\n     Third entry that is not a pill. conversation.input.dock is a `list` slot\n     and DSH's own QueueDock registers into it at order 20 (id `queue`,\n     dsh-client-ui-conversation) \u2014 a 36px row per queued message, or a\n     collapsible \"N \u6761\u6392\u961F\u6D88\u606F\" header once there is more than one. The 26px\n     cage above clipped it to a sliver: on a phone a queued message showed as\n     a grey stub poking out from behind the input card, unreadable and with\n     its edit / delete / send buttons cut off (reported 2026-08-22, same\n     failure the to-do card hit in 7a).\n\n     Two things are restored. Geometry: the official row height back, and the\n     dock's own composer-column sizing dropped \u2014 its width/max-width are\n     calc()s over the composer card variables and its bottom margin is\n     negative by design (upstream tucks the strip UNDER the card), none of\n     which survives being a flex item of our chip rail.\n\n     Layout \u2014 the line policy for the whole rail, now that three things want\n     room on it. The pills (the to-do card, a branch chip, whatever else\n     registers) keep order 0 and share the top line, still scrolling\n     horizontally. The queue takes the next line (order 1). The attachment\n     chips take the last one (order 2, 7b), so what the user is about to send\n     sits closest to the input it will be sent from. The rail only wraps\n     while one of the two full-width entries exists, so a session with\n     neither keeps the original single scrolling chip line. */\n  [data-slot=\"conversation.input.dock\"]:has(> [data-queue-dock], > [data-mobile-nav=\"attach-chips\"]) {\n    flex-wrap: wrap !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] {\n    flex: 1 0 100% !important;\n    order: 1 !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    margin: 0 !important;\n    padding: 0 !important;\n    border-radius: 0 !important;\n    overflow: visible !important;\n    font-size: 13px !important;\n    line-height: normal !important;\n  }\n  /* The panel is the dock's only child; upstream rounds its top corners only\n     and drops the bottom border, because there it is half-hidden behind the\n     card. On its own line it is a free-standing strip, so close it up. */\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] > * {\n    border-radius: 12px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] > *::after {\n    border-bottom: 1px solid var(--dsw-alias-border-l1) !important;\n  }\n\n  [data-mobile-nav=\"attach-chip\"] {\n    position: relative;\n    display: inline-flex;\n    align-items: center;\n    gap: 6px;\n    flex: 0 0 auto;\n    max-width: 62vw;\n    background: var(--dsw-alias-interactive-bg-hover, rgba(127, 127, 127, .12));\n    color: var(--dsw-alias-label-primary, inherit);\n  }\n  [data-mobile-nav=\"attach-chip\"][data-kind=\"file\"] {\n    height: 26px;\n    padding: 0 4px 0 8px;\n    border-radius: 999px;\n    font-size: 11.5px;\n    line-height: 18px;\n  }\n  /* An image chip is the thumbnail: no name line, the filename lives in the\n     title attribute (and in the draft text right below). */\n  [data-mobile-nav=\"attach-chip\"][data-kind=\"image\"] {\n    width: 48px;\n    height: 48px;\n    padding: 0;\n    border-radius: 10px;\n    overflow: hidden;\n  }\n  [data-mobile-nav=\"attach-chip-art\"] {\n    position: relative;\n    display: grid;\n    place-items: center;\n    flex: none;\n    overflow: hidden;\n  }\n  [data-kind=\"file\"] > [data-mobile-nav=\"attach-chip-art\"] {\n    width: 16px;\n    height: 16px;\n    opacity: .7;\n  }\n  [data-kind=\"image\"] > [data-mobile-nav=\"attach-chip-art\"] {\n    width: 100%;\n    height: 100%;\n  }\n  /* The <img> is stacked over the paperclip, not swapped for it: a format the\n     engine cannot decode (HEIC outside WebKit) simply paints nothing and the\n     icon shows through \u2014 no onError state to carry. */\n  [data-mobile-nav=\"attach-chip-art\"] img {\n    position: absolute;\n    inset: 0;\n    width: 100%;\n    height: 100%;\n    object-fit: cover;\n    background: var(--dsw-alias-bg-layer-2, rgba(127, 127, 127, .18));\n  }\n  [data-mobile-nav=\"attach-chip-name\"] {\n    min-width: 0;\n    overflow: hidden;\n    white-space: nowrap;\n  }\n  [data-mobile-nav=\"attach-chip-remove\"] {\n    display: grid;\n    place-items: center;\n    flex: none;\n    width: 18px;\n    height: 18px;\n    padding: 0;\n    border: none;\n    border-radius: 999px;\n    background: transparent;\n    color: inherit;\n    cursor: pointer;\n    touch-action: manipulation;\n  }\n  /* On a tile the \u00D7 floats in the corner over the picture, so it needs its own\n     ground to stay legible against an arbitrary photo. */\n  [data-kind=\"image\"] > [data-mobile-nav=\"attach-chip-remove\"] {\n    position: absolute;\n    top: 2px;\n    right: 2px;\n    background: rgba(0, 0, 0, .55);\n    color: #fff;\n  }\n  [data-mobile-nav=\"attach-chip-remove\"]:active {\n    transform: scale(.9);\n  }\n\n  /* --- 8. the official stats strip leaves the composer ---\n     Its data moves into the session info card (S4). The row is the composer\n     dock's own `_root` entry; the slot itself stays live for later entries. */\n  [data-slot=\"conversation.composer.dock\"] > [class$=\"_root\"] {\n    display: none !important;\n  }\n\n  /* --- 9. the attachment button (S7; its file input is hidden at the top of\n     this file, at every width) --- */\n  [data-mobile-nav=\"attach\"] {\n    position: relative;\n    width: 28px !important;\n    height: 28px !important;\n    flex: none !important;\n    display: grid !important;\n    place-items: center !important;\n    padding: 0 !important;\n    border: none !important;\n    border-radius: 999px !important;\n    background: var(--dsw-specific-selector, rgba(127, 127, 127, .12));\n    color: var(--dsw-alias-label-primary, inherit);\n    cursor: pointer;\n    touch-action: manipulation;\n  }\n  [data-mobile-nav=\"attach\"]:active {\n    transform: scale(.94);\n    transition: transform .12s;\n  }\n  /* Busy: a ring sweeps around the paperclip. Drawn with a conic gradient in\n     a pseudo-element rather than a spinner node, so the official React tree\n     around us has nothing extra to re-render (same reasoning as the model\n     pill's mask icon, S3.1). */\n  [data-mobile-nav=\"attach\"][data-busy]::after {\n    content: \"\";\n    position: absolute;\n    inset: -2px;\n    border-radius: 999px;\n    background: conic-gradient(from 0deg, transparent 0 65%, currentColor 100%);\n    mask: radial-gradient(closest-side, transparent calc(100% - 2px), #000 calc(100% - 2px));\n    -webkit-mask: radial-gradient(closest-side, transparent calc(100% - 2px), #000 calc(100% - 2px));\n    animation: mnav-attach-spin .9s linear infinite;\n    pointer-events: none;\n  }\n  @keyframes mnav-attach-spin {\n    to { transform: rotate(1turn); }\n  }\n  @media (prefers-reduced-motion: reduce) {\n    [data-mobile-nav=\"attach\"][data-busy]::after {\n      animation-duration: 3s;\n    }\n  }\n  /* Failure note: one line above the button, tap-to-dismiss. Sits on the\n     composer card (z 2) rather than in an overlay layer \u2014 nothing here needs\n     to clear the permission/model sheets. */\n  [data-mobile-nav=\"attach-error\"] {\n    position: absolute;\n    bottom: calc(100% + 6px);\n    left: 0;\n    z-index: 2;\n    max-width: 62vw;\n    padding: 5px 8px;\n    border-radius: 8px;\n    font-size: 12px;\n    line-height: 1.3;\n    white-space: nowrap;\n    overflow: hidden;\n    text-overflow: ellipsis;\n    background: var(--dsw-alias-bg-layer-2, rgba(0, 0, 0, .82));\n    color: var(--dsw-alias-label-primary, #fff);\n    box-shadow: 0 2px 8px rgba(0, 0, 0, .24);\n  }\n\n  /* --- 9. home-indicator clearance (S4.1, 2026-08-17) ---\n     Owned HERE, not by the gateway half. That plugin used to carry\n       [data-slot=\"conversation.composer\"] { padding-bottom: max(env(safe-area-inset-bottom), 8px) }\n     in both pwa/app.css and the gateway's inline DEVICE_CSS. Both were\n     INERT and had always been: that slot element is `display: contents`\n     (measured 2026-08-17 \u2014 the slot wrapper generates no box, so padding on\n     it is discarded), which is why raising it never moved anything. The rule\n     is deleted on the PWA side and restated here on an element that actually\n     lays out, reading --mnav-sab so ?mobile-nav-inset=54,34 can regress it\n     off-device (env() is hard 0 on desktop \u2014 the whole reason S2.1 exists).\n\n     Target: the card should look EQUALLY inset on all four sides. This same\n     element carries the card's side inset (`padding: 0 16px` officially,\n     measured 16px left and 16px right at 390px), so the bottom gap is simply\n     capped at that same 16px. Clearing the FULL 34px inset \u2014 the naive\n     max(sab, 8px) \u2014 is what read as \"too thick\": it is more than double the\n     side margin, so the card looked shoved up off the bottom edge.\n\n     clamp() says all three requirements at once:\n       - floor 8px  -> a device with no home indicator (sab: 0) keeps the\n                       official 8px exactly, so this is a strict no-op there;\n       - track sab  -> a shallower inset than 16px is honoured as-is;\n       - cap 16px   -> a full-size indicator (sab: 34) lands on 16px, equal\n                       to the side inset, which is the look being asked for.\n     Keep the 16px in step with the side padding above if that ever changes;\n     that equality IS the spec here, not a coincidence. */\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] {\n    padding-bottom: clamp(8px, var(--mnav-sab), 16px) !important;\n  }\n\n  /* S10 keyboard avoid: effects/keyboard-avoid.ts mirrors the band of the\n     layout viewport hidden behind the software keyboard into --mnav-kb-lift\n     and stamps the html attribute while (and only while) it is non-zero \u2014\n     a resting transform, even translateY(0), would silently become the\n     containing block for any fixed-position descendant of the bar. In every\n     environment where the browser's own focus-reveal works the attribute is\n     simply never set.\n     The target is the slot's _root CHILD, not the slot wrapper: the wrapper\n     is display:contents \u2014 it generates no box, so a transform on it is a\n     silent no-op (found live on-device via CDP, 2026-08-21; the variable and\n     attribute were set and nothing moved). */\n  html[data-mnav-kb] [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] {\n    transform: translateY(calc(-1 * var(--mnav-kb-lift, 0px)));\n  }\n}\n\n/* The attachment button and its preview row only exist for the phone shell.\n   Both render at every width (the slots are not breakpoint-aware), so both\n   need hiding here \u2014 the dock-row rules that shape the chips live in the\n   < 768px block and would otherwise leave a bare, unstyled chip line in the\n   desktop composer. */\n@media (min-width: 768px) {\n  [data-mobile-nav=\"attach\"],\n  [data-mobile-nav=\"attach-chips\"] {\n    display: none !important;\n  }\n}\n";
+export declare const COMPOSER_CSS = "/* ---------- phone composer (< 768px) ---------- */\n\n/* The file picker the attachment button drives (S7) \u2014 hidden at EVERY width,\n   deliberately OUTSIDE the phone media block below. A bare <input type=\"file\">\n   renders as a native \"Choose Files\" control, and the slot wrapper around it is\n   `display: contents`, so an un-hidden one becomes a flex item of the official\n   tool row. Scoping this to < 768px once put that control in the DESKTOP\n   composer (caught on a live deploy, 2026-08-17): the button that drives it is\n   phone-only, but the input it drives is in the DOM at all widths. */\n[data-mobile-nav=\"attach-picker\"] {\n  display: none !important;\n}\n\n@media (max-width: 767px) {\n  /* --- 1. flatten the two official groups ---\n     `_tools` and `_trailing` only exist to cluster controls left/right.\n     display:contents dissolves them into `_row`, so the six leaf controls\n     become siblings in one flex line and `order` alone drives the layout:\n     [attach \u00B7 + \u00B7 permission \u00B7 model] \u2026elastic gap\u2026 [context ring \u00B7 send]. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] {\n    justify-content: flex-start !important;\n    gap: 5px !important;\n    padding: 2px 8px 8px !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] {\n    display: contents !important;\n  }\n\n  /* --- 2. the running order ---\n     The attachment button (S3 placeholder, S7 wires it up) sits leftmost;\n     the official \"+\" command menu keeps its seat right next to it, where\n     the two \"insert something\" affordances read as one cluster. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] [data-mobile-nav=\"attach\"] {\n    order: 1 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_add\"] {\n    order: 2 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] {\n    order: 3 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    gap: 6px !important;\n  }\n  /* The model seat carries the elastic gap: everything after it is pushed to\n     the right edge, so no spacer element is needed. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] {\n    order: 4 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    margin-right: auto !important;\n  }\n  /* Third-party input.right entries park next to the ring rather than\n     landing at order 0 (= far left) once the groups are flattened. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.right\"] > * {\n    order: 5 !important;\n  }\n  /* ContextMeter \u2014 the only `span` ending in _root inside the row. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > span[class$=\"_root\"] {\n    order: 6 !important;\n    flex: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    order: 7 !important;\n  }\n\n  /* --- 3. permission + model as icon-only pills (real-device round 2, 2026-08-17) ---\n     S3's icon-and-label capsules read as noise on an actual phone \u2014 there\n     is no room to usefully show a preset name or a model id, so the label\n     text is now hidden outright and both triggers collapse to a plain\n     ~44x30 icon button. This AGREES with (rather than fights) the official\n     container query (`@container (width <= 460px) { .trigger:has(.triggerIcon)\n     .triggerLabel { display: none } }`) that S3 had to override \u2014 no need\n     to override it back. Accessible name is unaffected: both official\n     triggers already ship a descriptive aria-label independent of the\n     visible text (PermissionSelect: t('input.accessMode', {name}); the\n     model trigger: t('trigger.aria'/'trigger.ariaEffort')) \u2014 verified live\n     in dsh-client-ui-conversation / dsh-client-ui-model-selection lib/\n     client.js, 2026-08-17 \u2014 so hiding the label costs nothing for screen\n     readers. The permission trigger only renders an icon for the\n     \"read-only\" / \"workspace-write\" presets (permissionGlyphs in\n     dsh-client-ui-conversation) \u2014 \"Full access\" and any host-configured\n     preset name fall back to chevron-only, a known gap in the official\n     markup this plugin cannot fill without inventing new icon meaning.\n     The model trigger never renders an icon at all (only label + optional\n     effort text + chevron), so its ::before below draws one from a\n     primitives icon path (Sparkle \u2014 the closest existing \"model\" glyph) as\n     a CSS-only pseudo-element: it survives React re-renders for free\n     (unlike a DOM-injected node, which would need a MutationObserver, see\n     the preview-full-toggle pitfall in AGENTS.md) and does not touch\n     accessible-name computation (empty generated content). S3's\n     rtl-ellipsis trick on the model label is simply inert under\n     display:none now; left alone rather than unpicked. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [class$=\"_triggerLabel\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"] > [class$=\"_triggerLabel\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"] > [class$=\"_triggerEffort\"] {\n    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] button[class$=\"_trigger\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"] {\n    background: var(--dsw-specific-selector, rgba(127, 127, 127, .12)) !important;\n    width: 44px !important;\n    height: 30px !important;\n    max-width: none !important;\n    min-width: 0 !important;\n    padding: 0 !important;\n    gap: 2px !important;\n    justify-content: center !important;\n    border-radius: 999px !important;\n    touch-action: manipulation !important;\n  }\n  /* PermissionSelect wraps its trigger in the Menu primitive's root span,\n     which must shrink to the icon button's fixed width. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] > span:has(> button[class$=\"_trigger\"]) {\n    flex: 0 0 auto !important;\n    min-width: 0 !important;\n  }\n  /* ic_ds_sparkle_16 (@deepseek-ai/dsh-client-ui-primitives IconSparkle16\n     path, copied verbatim) as a mask so it inherits currentColor like every\n     other icon in the row \u2014 the model trigger has no official icon slot to\n     hook into. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_trigger\"]::before {\n    content: '';\n    width: 16px;\n    height: 16px;\n    flex: none;\n    background: currentColor;\n    -webkit-mask-image: url(\"data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M6.1 3.1Q6.6 7.8 11.3 8.3Q6.6 8.8 6.1 13.5Q5.6 8.8 0.9 8.3Q5.6 7.8 6.1 3.1Z'/%3E%3Cpath d='M11.9 1Q12.2 3.7 14.9 4Q12.2 4.3 11.9 7Q11.6 4.3 8.9 4Q11.6 3.7 11.9 1Z'/%3E%3C/svg%3E\");\n    mask-image: url(\"data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M6.1 3.1Q6.6 7.8 11.3 8.3Q6.6 8.8 6.1 13.5Q5.6 8.8 0.9 8.3Q5.6 7.8 6.1 3.1Z'/%3E%3Cpath d='M11.9 1Q12.2 3.7 14.9 4Q12.2 4.3 11.9 7Q11.6 4.3 8.9 4Q11.6 3.7 11.9 1Z'/%3E%3C/svg%3E\");\n    -webkit-mask-size: contain;\n    mask-size: contain;\n    -webkit-mask-repeat: no-repeat;\n    mask-repeat: no-repeat;\n  }\n\n  /* --- 4. both menus become bottom sheets ---\n     The permission menu is the Menu primitive (role=menu, absolute, side=top)\n     and the model menu is ModelSelect's own `_menu` (absolute, bottom+right).\n     Neither has a transformed ancestor between it and the viewport, so\n     position:fixed re-anchors both to the screen edge. Only the shell moves \u2014\n     the items, the two-level model panes and every selection handler stay\n     official. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"] {\n    position: fixed !important;\n    left: 0 !important;\n    right: 0 !important;\n    bottom: 0 !important;\n    top: auto !important;\n    transform: none !important;\n    width: 100% !important;\n    min-width: 0 !important;\n    max-width: none !important;\n    max-height: min(70dvh, 520px) !important;\n    box-sizing: border-box !important;\n    border-radius: 16px 16px 0 0 !important;\n    border-bottom: none !important;\n    padding: 8px 8px calc(8px + var(--mnav-sab)) !important;\n    z-index: 60 !important;\n    box-shadow: 0 -8px 32px rgba(0, 0, 0, .18) !important;\n  }\n  /* 44pt+ rows in both sheets (Menu items, model options, and the model\n     sheet's two root cells that drill into the model / effort panes). */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"] [role=\"menuitem\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"] [class$=\"_option\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"] [class$=\"_cell\"] {\n    min-height: 48px !important;\n    border-radius: 12px !important;\n    font-size: 15px !important;\n  }\n  /* --- 4b. the official scroll-to-bottom button must not poke through the\n     sheet (real-device follow-up, 2026-08-17) ---\n     ChatView's own \"jump to latest\" button (aria-label t(\"chat.toBottom\"))\n     is `position: sticky; z-index: 8` inside the message column, not\n     `position: fixed` \u2014 it never escapes to the same top-level stacking\n     context our sheets get promoted to, so raising the sheet's z-index\n     further does nothing (measured live: it still rendered on top at\n     z-index 60 vs 8). Rather than chase engine-specific stacking-context\n     semantics (Chromium and WebKit do not always agree here \u2014 see AGENTS.md\n     CDP/document.hidden lesson for another instance of that), this hides\n     the button outright while either sheet is open and lets it reappear on\n     close: a plain `display: none` behind a live `:has()` read is correct\n     regardless of which stacking rules the engine happens to apply.\n     Selector: no hashed classes (dsh-client-ui-conversation lib/client.js,\n     verified 2026-08-17) \u2014 `data-chat-flow` is the one stable attribute on\n     the message column, and the button's wrapper is its only sibling\n     (ChatView only ever renders the column and, conditionally, this one\n     slot), so the adjacent-sibling combinator pins it precisely. */\n  body:has([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"]) [data-chat-flow] + div,\n  body:has([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [data-slot=\"conversation.input.model\"] > [class$=\"_root\"] > [class$=\"_menu\"]) [data-chat-flow] + div {\n    display: none !important;\n  }\n  /* --- 5. input box: two lines minimum, five lines maximum ---\n     The official autosizer drives the box off the hidden mirror's height, so\n     a min-height on the mirror IS the min-height of the field; the scroll cap\n     rides the official custom property. 52px = 2 x 24px line box + 4px pad,\n     124px = 5 lines. The hero card keeps its own one-line collapse (misc.css\n     pins _scroll/_grow while the placeholder shows). */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] [class$=\"_mirror\"] {\n    min-height: 52px !important;\n  }\n  [class$=\"_composerSeat\"] {\n    --dsh-composer-text-max-height: 124px;\n  }\n\n  /* --- 6. no divider above OR below the message list ---\n     Instead of a rule the messages butt against, they fade near both edges.\n     This used to be ONE mask-image on the message scroller; iOS WebKit\n     turned that into fog over the header (user report 2026-08-23): a mask\n     on a scroll container is applied in CONTENT coordinates there (the fade\n     bands scroll away with the messages) and, worse, it breaks the\n     container's own overflow clipping \u2014 content scrolled out of view keeps\n     painting, straight over the header and status bar. Engine bug with no\n     iOS escape hatch (every iOS browser is WebKit), so the fades moved off\n     the scroller entirely:\n\n     - fade-IN under the header: the header's own ::after, restyled into a\n       20px gradient strip \u2014 styles/header.css.ts (\"no header bottom line\").\n     - fade-OUT above the composer: nothing of ours. The official composer\n       seat already carries `background: linear-gradient(transparent 0,\n       bg 36px)` on its sticky self (dsh-client-ui-conversation lib/\n       client.js .wSkVaW_composerSeat) and that is the entire visible\n       effect; the mask's own bottom band landed inside the safe-area\n       padding below the card and painted nothing. If the bottom edge ever\n       reads harsh, hang a ::before strip off the seat the same way the\n       header does \u2014 do NOT put a mask back on the scroller.\n\n     Painted strips instead of a mask is a fair trade only because the page\n     background is one flat color \u2014 which it is (--dsw-alias-bg-base). */\n  [class$=\"_composerSeat\"],\n  [class$=\"_composerStack\"] {\n    border-top: none !important;\n  }\n\n  /* --- 7. dock entries become mini chips above the input card ---\n     conversation.input.dock is display:contents (inline style), so its\n     entries are stacked rows of the composer column. Forcing the slot itself\n     to flex turns them into ONE scrollable chip line outside and above the\n     card. Written against the slot, not against any particular plugin's chip\n     (the git branch chip and the todo panel are third-party and may not be\n     installed at all). */\n  [data-slot=\"conversation.input.dock\"] {\n    display: flex !important;\n    flex-flow: row nowrap !important;\n    align-items: center !important;\n    gap: 6px !important;\n    min-width: 0 !important;\n    margin: 0 16px !important;\n    overflow-x: auto !important;\n    overflow-y: hidden !important;\n    scrollbar-width: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"]::-webkit-scrollbar {\n    display: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > * {\n    flex: 0 0 auto !important;\n    max-width: 70% !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    border-radius: 999px !important;\n    font-size: 11.5px !important;\n    line-height: 18px !important;\n    overflow: hidden !important;\n  }\n  /* The git-graph chip carries a 34px tablet target from misc.css; that\n     selector is more specific, so restate it at the phone breakpoint. */\n  [data-slot=\"conversation.input.dock\"] [data-gitgraph-chip-anchor] [data-gitgraph-chip] {\n    min-height: 26px !important;\n    padding: 0 10px !important;\n    font-size: 11.5px !important;\n  }\n  /* --- 7a. the native to-do card opts OUT of the 26px pill cage ---\n     conversation.input.dock is not only a chip rail: DSH's own TodoPanel\n     (dsh-client-ui-conversation) registers here, and it is an expandable\n     card, not a pill \u2014 tapping its header renders the to-do list INSIDE\n     itself. The cage's max-height:26px + overflow:hidden left that list\n     rendered but clipped to nothing, so on a phone the bar looked dead:\n     aria-expanded flipped, 8 rows mounted at 216px, and the card still\n     painted 26px tall (measured live, 2026-08-20). Give it the official\n     geometry back \u2014 full row, natural height, 12px radius. Its list caps\n     itself at 180px with its own scroller, so this cannot run into the\n     composer. Anchored on the official data-testid, a stable contract\n     marker rather than a hashed class name. */\n  [data-slot=\"conversation.input.dock\"] > [data-testid=\"todo-panel\"] {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    overflow: visible !important;\n    border-radius: 12px !important;\n    /* The cage shrinks dock text to 11.5px/18px; the card's rows inherit it\n       and turn cramped. Restore the official 13px body scale. */\n    font-size: 13px !important;\n    line-height: normal !important;\n  }\n\n  /* --- 7b. attachment chips (S7.1) ---\n     Our own dock entry opts OUT of the 26px pill cage above: an image chip is\n     a 48px tile. The row sits tight under the card's top edge, so the chips\n     read as part of the composer rather than as a floating strip.\n\n     It also takes the LAST line of its own (line policy in 7c): a 48px tile\n     beside the to-do chip on one nowrap line squeezed that chip down to an\n     unreadable stub, with a long file name pushing the rest off-screen\n     (reported 2026-08-22). Its own chips wrap rather than overflow, so\n     several attachments stack instead of scrolling out of reach. */\n  [data-slot=\"conversation.input.dock\"] > [data-mobile-nav=\"attach-chips\"] {\n    display: flex !important;\n    flex: 1 0 100% !important;\n    flex-wrap: wrap !important;\n    order: 2 !important;\n    align-items: center !important;\n    gap: 6px !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    border-radius: 0 !important;\n    overflow: visible !important;\n    margin-bottom: -2px;\n  }\n\n  /* --- 7c. the queue strip opts OUT of the cage, on a line of its own ---\n     Third entry that is not a pill. conversation.input.dock is a `list` slot\n     and DSH's own QueueDock registers into it at order 20 (id `queue`,\n     dsh-client-ui-conversation) \u2014 a 36px row per queued message, or a\n     collapsible \"N \u6761\u6392\u961F\u6D88\u606F\" header once there is more than one. The 26px\n     cage above clipped it to a sliver: on a phone a queued message showed as\n     a grey stub poking out from behind the input card, unreadable and with\n     its edit / delete / send buttons cut off (reported 2026-08-22, same\n     failure the to-do card hit in 7a).\n\n     Two things are restored. Geometry: the official row height back, and the\n     dock's own composer-column sizing dropped \u2014 its width/max-width are\n     calc()s over the composer card variables and its bottom margin is\n     negative by design (upstream tucks the strip UNDER the card), none of\n     which survives being a flex item of our chip rail.\n\n     Layout \u2014 the line policy for the whole rail, now that three things want\n     room on it. The pills (the to-do card, a branch chip, whatever else\n     registers) keep order 0 and share the top line, still scrolling\n     horizontally. The queue takes the next line (order 1). The attachment\n     chips take the last one (order 2, 7b), so what the user is about to send\n     sits closest to the input it will be sent from. The rail only wraps\n     while one of the two full-width entries exists, so a session with\n     neither keeps the original single scrolling chip line. */\n  [data-slot=\"conversation.input.dock\"]:has(> [data-queue-dock], > [data-mobile-nav=\"attach-chips\"]) {\n    flex-wrap: wrap !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] {\n    flex: 1 0 100% !important;\n    order: 1 !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    margin: 0 !important;\n    padding: 0 !important;\n    border-radius: 0 !important;\n    overflow: visible !important;\n    font-size: 13px !important;\n    line-height: normal !important;\n  }\n  /* The panel is the dock's only child; upstream rounds its top corners only\n     and drops the bottom border, because there it is half-hidden behind the\n     card. On its own line it is a free-standing strip, so close it up. */\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] > * {\n    border-radius: 12px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] > *::after {\n    border-bottom: 1px solid var(--dsw-alias-border-l1) !important;\n  }\n\n  [data-mobile-nav=\"attach-chip\"] {\n    position: relative;\n    display: inline-flex;\n    align-items: center;\n    gap: 6px;\n    flex: 0 0 auto;\n    max-width: 62vw;\n    background: var(--dsw-alias-interactive-bg-hover, rgba(127, 127, 127, .12));\n    color: var(--dsw-alias-label-primary, inherit);\n  }\n  [data-mobile-nav=\"attach-chip\"][data-kind=\"file\"] {\n    height: 26px;\n    padding: 0 4px 0 8px;\n    border-radius: 999px;\n    font-size: 11.5px;\n    line-height: 18px;\n  }\n  /* An image chip is the thumbnail: no name line, the filename lives in the\n     title attribute (and in the draft text right below). */\n  [data-mobile-nav=\"attach-chip\"][data-kind=\"image\"] {\n    width: 48px;\n    height: 48px;\n    padding: 0;\n    border-radius: 10px;\n    overflow: hidden;\n  }\n  [data-mobile-nav=\"attach-chip-art\"] {\n    position: relative;\n    display: grid;\n    place-items: center;\n    flex: none;\n    overflow: hidden;\n  }\n  [data-kind=\"file\"] > [data-mobile-nav=\"attach-chip-art\"] {\n    width: 16px;\n    height: 16px;\n    opacity: .7;\n  }\n  [data-kind=\"image\"] > [data-mobile-nav=\"attach-chip-art\"] {\n    width: 100%;\n    height: 100%;\n  }\n  /* The <img> is stacked over the paperclip, not swapped for it: a format the\n     engine cannot decode (HEIC outside WebKit) simply paints nothing and the\n     icon shows through \u2014 no onError state to carry. */\n  [data-mobile-nav=\"attach-chip-art\"] img {\n    position: absolute;\n    inset: 0;\n    width: 100%;\n    height: 100%;\n    object-fit: cover;\n    background: var(--dsw-alias-bg-layer-2, rgba(127, 127, 127, .18));\n  }\n  [data-mobile-nav=\"attach-chip-name\"] {\n    min-width: 0;\n    overflow: hidden;\n    white-space: nowrap;\n  }\n  [data-mobile-nav=\"attach-chip-remove\"] {\n    display: grid;\n    place-items: center;\n    flex: none;\n    width: 18px;\n    height: 18px;\n    padding: 0;\n    border: none;\n    border-radius: 999px;\n    background: transparent;\n    color: inherit;\n    cursor: pointer;\n    touch-action: manipulation;\n  }\n  /* On a tile the \u00D7 floats in the corner over the picture, so it needs its own\n     ground to stay legible against an arbitrary photo. */\n  [data-kind=\"image\"] > [data-mobile-nav=\"attach-chip-remove\"] {\n    position: absolute;\n    top: 2px;\n    right: 2px;\n    background: rgba(0, 0, 0, .55);\n    color: #fff;\n  }\n  [data-mobile-nav=\"attach-chip-remove\"]:active {\n    transform: scale(.9);\n  }\n\n  /* --- 8. the official stats strip leaves the composer ---\n     Its data moves into the session info card (S4). The row is the composer\n     dock's own `_root` entry; the slot itself stays live for later entries. */\n  [data-slot=\"conversation.composer.dock\"] > [class$=\"_root\"] {\n    display: none !important;\n  }\n\n  /* --- 9. the attachment button (S7; its file input is hidden at the top of\n     this file, at every width) --- */\n  [data-mobile-nav=\"attach\"] {\n    position: relative;\n    width: 28px !important;\n    height: 28px !important;\n    flex: none !important;\n    display: grid !important;\n    place-items: center !important;\n    padding: 0 !important;\n    border: none !important;\n    border-radius: 999px !important;\n    background: var(--dsw-specific-selector, rgba(127, 127, 127, .12));\n    color: var(--dsw-alias-label-primary, inherit);\n    cursor: pointer;\n    touch-action: manipulation;\n  }\n  [data-mobile-nav=\"attach\"]:active {\n    transform: scale(.94);\n    transition: transform .12s;\n  }\n  /* Busy: a ring sweeps around the paperclip. Drawn with a conic gradient in\n     a pseudo-element rather than a spinner node, so the official React tree\n     around us has nothing extra to re-render (same reasoning as the model\n     pill's mask icon, S3.1). */\n  [data-mobile-nav=\"attach\"][data-busy]::after {\n    content: \"\";\n    position: absolute;\n    inset: -2px;\n    border-radius: 999px;\n    background: conic-gradient(from 0deg, transparent 0 65%, currentColor 100%);\n    mask: radial-gradient(closest-side, transparent calc(100% - 2px), #000 calc(100% - 2px));\n    -webkit-mask: radial-gradient(closest-side, transparent calc(100% - 2px), #000 calc(100% - 2px));\n    animation: mnav-attach-spin .9s linear infinite;\n    pointer-events: none;\n  }\n  @keyframes mnav-attach-spin {\n    to { transform: rotate(1turn); }\n  }\n  @media (prefers-reduced-motion: reduce) {\n    [data-mobile-nav=\"attach\"][data-busy]::after {\n      animation-duration: 3s;\n    }\n  }\n  /* Failure note: one line above the button, tap-to-dismiss. Sits on the\n     composer card (z 2) rather than in an overlay layer \u2014 nothing here needs\n     to clear the permission/model sheets. */\n  [data-mobile-nav=\"attach-error\"] {\n    position: absolute;\n    bottom: calc(100% + 6px);\n    left: 0;\n    z-index: 2;\n    max-width: 62vw;\n    padding: 5px 8px;\n    border-radius: 8px;\n    font-size: 12px;\n    line-height: 1.3;\n    white-space: nowrap;\n    overflow: hidden;\n    text-overflow: ellipsis;\n    background: var(--dsw-alias-bg-layer-2, rgba(0, 0, 0, .82));\n    color: var(--dsw-alias-label-primary, #fff);\n    box-shadow: 0 2px 8px rgba(0, 0, 0, .24);\n  }\n\n  /* --- 9. home-indicator clearance (S4.1, 2026-08-17) ---\n     Owned HERE, not by the gateway half. That plugin used to carry\n       [data-slot=\"conversation.composer\"] { padding-bottom: max(env(safe-area-inset-bottom), 8px) }\n     in both pwa/app.css and the gateway's inline DEVICE_CSS. Both were\n     INERT and had always been: that slot element is `display: contents`\n     (measured 2026-08-17 \u2014 the slot wrapper generates no box, so padding on\n     it is discarded), which is why raising it never moved anything. The rule\n     is deleted on the PWA side and restated here on an element that actually\n     lays out, reading --mnav-sab so ?mobile-nav-inset=54,34 can regress it\n     off-device (env() is hard 0 on desktop \u2014 the whole reason S2.1 exists).\n\n     Target: the card should look EQUALLY inset on all four sides. This same\n     element carries the card's side inset (`padding: 0 16px` officially,\n     measured 16px left and 16px right at 390px), so the bottom gap is simply\n     capped at that same 16px. Clearing the FULL 34px inset \u2014 the naive\n     max(sab, 8px) \u2014 is what read as \"too thick\": it is more than double the\n     side margin, so the card looked shoved up off the bottom edge.\n\n     clamp() says all three requirements at once:\n       - floor 8px  -> a device with no home indicator (sab: 0) keeps the\n                       official 8px exactly, so this is a strict no-op there;\n       - track sab  -> a shallower inset than 16px is honoured as-is;\n       - cap 16px   -> a full-size indicator (sab: 34) lands on 16px, equal\n                       to the side inset, which is the look being asked for.\n     Keep the 16px in step with the side padding above if that ever changes;\n     that equality IS the spec here, not a coincidence. */\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] {\n    padding-bottom: clamp(8px, var(--mnav-sab), 16px) !important;\n  }\n\n  /* S10 keyboard avoid: effects/keyboard-avoid.ts mirrors the band of the\n     layout viewport hidden behind the software keyboard into --mnav-kb-lift\n     and stamps the html attribute while (and only while) it is non-zero \u2014\n     a resting transform, even translateY(0), would silently become the\n     containing block for any fixed-position descendant of the bar. In every\n     environment where the browser's own focus-reveal works the attribute is\n     simply never set.\n     The target is the slot's _root CHILD, not the slot wrapper: the wrapper\n     is display:contents \u2014 it generates no box, so a transform on it is a\n     silent no-op (found live on-device via CDP, 2026-08-21; the variable and\n     attribute were set and nothing moved). */\n  html[data-mnav-kb] [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] {\n    transform: translateY(calc(-1 * var(--mnav-kb-lift, 0px)));\n  }\n}\n\n/* The attachment button and its preview row only exist for the phone shell.\n   Both render at every width (the slots are not breakpoint-aware), so both\n   need hiding here \u2014 the dock-row rules that shape the chips live in the\n   < 768px block and would otherwise leave a bare, unstyled chip line in the\n   desktop composer. */\n@media (min-width: 768px) {\n  [data-mobile-nav=\"attach\"],\n  [data-mobile-nav=\"attach-chips\"] {\n    display: none !important;\n  }\n}\n";
 //# sourceMappingURL=composer.css.d.ts.map

package/lib/types/client/styles/composer.css.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"composer.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/composer.css.ts"],"names":[],"mappings":"AAsBA,eAAO,MAAM,YAAY,g36BAqkBxB,CAAA"}
+{"version":3,"file":"composer.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/composer.css.ts"],"names":[],"mappings":"AAsBA,eAAO,MAAM,YAAY,2x7BA4kBxB,CAAA"}

package/lib/types/client/styles/header.css.d.ts

@@ -1,2 +1,2 @@
-export declare const HEADER_CSS = "/* ---------- session header five-piece reflow (< 768px) ---------- */\n\n/* New elements render unconditionally (React does not know about media\n   queries); default them to hidden so 768px+ never sees them, then\n   re-enable inside the phone block below. Belt-and-braces alongside the\n   scoped rules \u2014 mirrors the existing [data-mobile-nav=\"*\"] desktop no-op\n   list in misc.css.ts. */\n[data-mobile-nav=\"header-back\"],\n[data-mobile-nav=\"header-viewrow\"],\n[data-mobile-nav=\"header-activity\"],\n[data-mobile-nav=\"header-info\"],\n[data-mobile-nav=\"header-workbench\"],\n/* The workbench close pill's default-hidden used to live in compat.css.ts \u2014\n   but EVERYTHING in layout/compat/misc sits inside one shared\n   (max-width: 1023px) block (opened at the top of layout, closed at the end\n   of misc), so that \"top-level\" rule silently never applied at >=1024 and\n   the pill rendered as an unstyled button on desktop (2026-08-17 report).\n   This file is appended after the shared block closes, so here it is truly\n   global; the <=767px :has() show rule in compat overrides it with\n   !important. */\n[data-mobile-nav=\"better-sidebar-close\"] {\n  display: none;\n}\n\n@media (max-width: 767px) {\n  /* The Files action targeted the dsh-web-ui-all (aionui) explorer sheet \u2014\n     a different, unrelated suite from the workbench entry this slice adds\n     (dsh-better-sidebar). Hidden here only; 768-1023px keeps it exactly as\n     v1.0.0 shipped it. */\n  [data-mobile-nav=\"files\"] {\n    display: none !important;\n  }\n\n  /* --- three-column header: [back 92px] [title, truly centered] [utilities 92px] --- */\n  /* The bottom padding is the view-switch row's seat: that row is\n     position:absolute (see the bottom of this file \u2014 it renders two levels\n     deep inside headerActions and can never be a grid item of titleRow), so\n     without a reserve it would hang over the message list. 28px = its\n     height. Unconditional rather than header:has([data-mobile-nav=\n     \"header-viewrow\"]) on purpose: :has() is silently dropped by pre-105\n     WebViews (see AGENTS.md) and a 28px overlap on the first message is a\n     worse failure than 28px of empty band in the (never observed in\n     practice) single-view session. Total header chrome: 48 + 28 = 76px.\n     Left/right 8px (S2.1 report leftover, fixed in S4): the official header\n     had zero horizontal padding, so the utilities button cluster's right\n     edge sat flush against the screen edge (x=390 at 390px width, no\n     margin). The 92px grid columns absorb this fine \u2014 they're fixed track\n     widths, only the center 1fr column shrinks by 16px. */\n  [data-phase] header {\n    position: relative;\n    padding: 0 8px 28px !important;\n  }\n  /* No header bottom line \u2014 fade instead (real-device round 2, 2026-08-17).\n     The official header draws its border as a `::after` 1px bar (the\n     `border-bottom` on the header itself is transparent, just a layout\n     reserve \u2014 dsh-client-ui-conversation lib/client.js \".wSkVaW_header{\n     border-bottom:1px solid #0000}.wSkVaW_header:after{...height:1px;\n     position:absolute;bottom:1px...}\", verified live 2026-08-17), so\n     hiding the pseudo-element is enough; the header's own border-bottom\n     never had a visible color to begin with. The message scroller now\n     fades in from under the header instead (styles/composer.css.ts, \"no\n     divider above OR below the message list\" \u2014 the two edges share one\n     mask-image on [class$=\"_scrollBody\"]). */\n  [data-phase] header::after {\n    display: none !important;\n  }\n  /* grid-row: 1 on every item is load-bearing, not decoration (S2.1 fix for\n     the \"\u6807\u9898\u88AB\u6324\u4E0B\u53BB\" report). The three items are placed with explicit\n     grid-column but arrive in DOM order crumbs(2) \u2192 headerActions(1) \u2192\n     headerUtilities(3): sparse auto-placement never moves its cursor\n     backwards, so headerActions and headerUtilities were pushed onto an\n     implicit SECOND row. Measured at 390px: row1 = crumbs 28px, row2 =\n     back button 44px, titleRow = 72px with the title stuck at the top\n     instead of centered. Pinning the row makes it one 48px band again. */\n  [data-phase] header [class$=\"_titleRow\"] {\n    position: relative;\n    display: grid;\n    grid-template-columns: 92px 1fr 92px;\n    grid-template-rows: minmax(48px, auto);\n    align-items: center;\n    min-height: 48px;\n    padding: 0 !important;\n  }\n  /* Flatten the official cluster so its two children (crumbs, headerActions)\n     become direct grid items of titleRow instead of a nested flex box. */\n  [data-phase] header [class$=\"_titleCluster\"] {\n    display: contents;\n  }\n  /* margin-left: 0 cancels layout.css.ts's shared <=1023px\n     \"margin-left: auto !important\" on this exact selector (it pushed the\n     Files button to the row's right edge in the old non-grid header;\n     inside our grid column it instead shoves the back button 48px right of\n     the column's start \u2014 the auto margin absorbs the leftover space\n     between the button's content width and the 92px column). */\n  [data-phase] header [class$=\"_headerActions\"] {\n    grid-column: 1;\n    grid-row: 1;\n    justify-self: start;\n    margin-left: 0 !important;\n    display: flex;\n    align-items: center;\n    min-width: 0;\n  }\n  /* layout.css.ts's shared <=1023px block hides this element outright\n     (header > :first-child > :last-child { display: none !important },\n     specificity (0,3,1) \u2014 v1.0.0 relocated the desktop Session-log capsule\n     to the drawer footer on every narrow width). That selector is repeated\n     here at equal specificity so the later source order wins the display\n     property; the class-suffix selector alone (0,2,1) would silently lose. */\n  [data-phase] header [class$=\"_headerUtilities\"],\n  [data-phase] header > :first-child > :last-child {\n    grid-column: 3;\n    grid-row: 1;\n    justify-self: end;\n    display: flex !important;\n    align-items: center;\n    gap: 4px;\n    min-width: 0;\n  }\n  /* justify-self: stretch (the grid default) so this fills the whole 1fr\n     column as a definite-width box \u2014 center/center-content happens inside\n     it. justify-self: center (tried first) sizes the item to its content\n     with no automatic column cap, and the obvious fix \u2014 max-width: 100% \u2014\n     resolves against the WRONG box here (measured 93.6px at 390px, where\n     the column is ~206px): the item's DOM parent (titleCluster) is\n     display:contents, and percentage max-width does not reliably resolve\n     through a boxless ancestor to the grid track. Stretching sidesteps the\n     percentage entirely \u2014 but layout.css.ts's shared <=1023px block ALSO\n     caps this exact selector at max-width: 24vw !important (93.6px at\n     390px \u2014 the value this rule used to silently inherit once its own\n     max-width was dropped in favor of stretch), so that must be reset to\n     none here too. */\n  [data-phase] header [class$=\"_crumbs\"] {\n    grid-column: 2;\n    grid-row: 1;\n    justify-self: stretch;\n    max-width: none !important;\n    display: flex;\n    align-items: center;\n    justify-content: center;\n    min-width: 0;\n    overflow: hidden;\n  }\n  /* Subagent sessions keep ONE ancestor crumb (2026-08-18): the PC header\n     lets you tap the parent session's title to switch back \u2014 that affordance\n     was lost on phone when the whole parent chain was hidden as \"\u591A\u4F59\u9879\".\n     Show only the immediate parent (for agent-teams member sessions that IS\n     the captain/main session; deeper ancestors stay hidden \u2014 a 3-level chain\n     cannot fit the ~206px center column at 390px). The parent crumb is the\n     official breadcrumb <button> (dsh-client-ui-conversation renders\n     open(parentId) as its onClick), so tapping needs no JS from this plugin,\n     and main sessions (chain length 1) have no :nth-last-child(2) seg at\n     all \u2014 the centered single title is pixel-identical to before. */\n  [data-phase] header [class$=\"_crumbSeg\"]:not(:nth-last-child(-n+2)) {\n    display: none !important;\n  }\n  [data-phase] header [class$=\"_crumbSeg\"]:nth-last-child(2) {\n    display: inline-flex;\n    align-items: center;\n    flex: none;\n    min-width: 0;\n    max-width: 38%;\n  }\n  /* Ancestors BEFORE the parent seg are hidden, which would leave the\n     parent seg's own leading \"/\" dangling at the start of the title. */\n  [data-phase] header [class$=\"_crumbSeg\"]:nth-last-child(2) [class$=\"_crumbSep\"] {\n    display: none !important;\n  }\n  /* Parent crumb: small tertiary text so the 19px current title stays the\n     visual anchor; min-height keeps a finger-sized target inside the 48px\n     row. Specificity (0,4,1) outranks the shared 19px _crumb rule below. */\n  [data-phase] header [class$=\"_crumbSeg\"]:nth-last-child(2) [class$=\"_crumb\"] {\n    font-size: 13px;\n    font-weight: 400;\n    color: var(--dsw-alias-label-tertiary, rgba(0, 0, 0, .45));\n    min-height: 44px;\n    display: inline-flex;\n    align-items: center;\n    padding: 0 2px 0 6px;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-phase] header [class$=\"_crumbSeg\"]:last-child {\n    display: flex;\n    align-items: center;\n    min-width: 0;\n    max-width: 100%;\n  }\n  /* The last seg's own \"/\" is the divider between parent and current title \u2014\n     it only exists when there IS an ancestor (index > 0), so it can simply\n     stay visible now that the parent seg shows. (It used to be hidden here:\n     with the parent hidden it dangled before the title.) */\n  /* BOTH selectors are required: [class$=] matches the whole class\n     ATTRIBUTE's suffix, and the current-session title button's attribute is\n     \"wSkVaW_crumb wSkVaW_crumbCurrent\" \u2014 it ends in _crumbCurrent, so the _crumb\n     suffix selector alone silently missed the one element that matters\n     (measured live: the title stayed 14px while the rule sat in the bundle,\n     2026-08-17). */\n  [data-phase] header [class$=\"_crumb\"],\n  [data-phase] header [class$=\"_crumbCurrent\"] {\n    overflow: hidden;\n    text-overflow: ellipsis;\n    white-space: nowrap;\n    min-width: 0;\n    max-width: 100%;\n    /* Real-device feedback (2026-08-17): the session title read too small\n       next to the enlarged header icons \u2014 19px sits just under the home\n       screen's 22px workspace title, keeping the two-level hierarchy. */\n    font-size: 19px;\n    font-weight: 600;\n  }\n\n  /* Running-status dot: no official element to reposition (the header\n     renders only the crumb title, the two action slots, and the tablist \u2014\n     no status indicator), so this is the plan's documented fallback \u2014\n     read the data ourselves and draw it (effects/header-status.ts stamps\n     data-mobile-nav-dot on the frame). A ::after on the title crumb keeps\n     it truly inline with the (centered, truncated) text instead of a\n     separately positioned box that would fight the centering math. */\n  [data-phase] header [class$=\"_crumbCurrent\"]::after {\n    content: '';\n    display: none;\n    width: 6px;\n    height: 6px;\n    margin-left: 6px;\n    border-radius: 50%;\n    vertical-align: middle;\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot] header [class$=\"_crumbCurrent\"]::after {\n    display: inline-block;\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot=\"ongoing\"] header [class$=\"_crumbCurrent\"]::after {\n    background: var(--dsw-alias-state-business-primary, #4f6ef7);\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot=\"warning\"] header [class$=\"_crumbCurrent\"]::after {\n    background: var(--dsw-alias-state-warn-primary, #d97706);\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot=\"done\"] header [class$=\"_crumbCurrent\"]::after {\n    background: var(--dsw-alias-state-success-primary, #16a34a);\n  }\n\n  /* Everything else the official header puts in these two list slots \u2014 the\n     agent-preset mode badge, the jobs/subagent trigger, the desktop\n     Session-log download capsule, and this plugin's own legacy directory\n     toggle \u2014 is the \"\u4E0D\u5E38\u9A7B\" set the design defers to the S4 info card.\n     Scoped by the slots' own [data-slot] wrapper (a stable, non-hashed\n     contract marker) rather than enumerating each registrant, so a future\n     third-party header action is hidden by default too. */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > *,\n  [data-phase] header [data-slot=\"conversation.session.header.utilities\"] > * {\n    display: none !important;\n  }\n  /* Native background-task / subagent entries (rewritten for DSH 0.1.1,\n     2026-08-21). Three upstream changes killed the old \"park the root as a\n     zero-width anchor, hide the trigger, forward the tap\" design at once:\n\n     - the subagent entry moved out of header.actions into the new\n       conversation.session.header.lineage slot (inside the breadcrumb);\n     - its root's class attribute is now \"ZKlsPq_root \" \u2014 with a TRAILING\n       SPACE \u2014 so a [class$=\"_root\"] anchor matches nothing at all;\n     - the trigger only reacts to TRUSTED input: .click() and synthetic\n       pointer/mouse events leave aria-expanded untouched (measured on device\n       with every plugin override stripped), so forwarding a tap in JS can\n       never open it again.\n\n     The trigger's geometry is therefore owned at runtime by\n     effects/native-trigger-overlay.ts, which lays the REAL button\n     transparently over the activity pill \u2014 a genuine finger tap lands on the\n     official element. Nothing in this stylesheet may size, hide, or set\n     pointer-events on the trigger: that is exactly what would take the tap\n     target away again.\n\n     CSS keeps only two chores. Dissolve the root so its box (and its\n     stray separator, hidden below) stops occupying the breadcrumb, and let\n     the trigger participate from wherever the overlay pins it. And no menu\n     re-anchoring anymore: the 0.1.1 popover portals to <body> as\n     position:fixed and positions itself from the trigger's viewport rect\n     (measured 336px wide, fully on screen at 411px). */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > *:has(> button[class$=\"_trigger\"]),\n  [data-phase] header [data-slot=\"conversation.session.header.lineage\"] > *:has(> button[class$=\"_trigger\"]) {\n    display: contents !important;\n  }\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] [class$=\"_separator\"],\n  [data-phase] header [data-slot=\"conversation.session.header.lineage\"] [class$=\"_separator\"] {\n    display: none !important;\n  }\n  /* The agent-preset mode badge specifically survives the blanket hide\n     above: layout.css.ts's shared <=1023px block targets it directly\n     (header [class$=\"_label\"]:has(> svg) { display: block !important }),\n     specificity (0,3,1), higher than the [data-slot] wrapper rule (0,2,1) \u2014\n     display wins on specificity before source order, so a same-selector\n     override is needed here too. */\n  [data-phase] header [class$=\"_label\"]:has(> svg) {\n    display: none !important;\n  }\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > [data-mobile-nav=\"header-back\"] {\n    display: inline-flex !important;\n  }\n  /* header-viewrow is position:absolute (see below), so its re-shown\n     display value must match the flex layout its own rule declares. */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > [data-mobile-nav=\"header-viewrow\"] {\n    display: flex !important;\n  }\n  /* Our own chip lives in the same slot, so the blanket hide above swallows\n     it unless it is named here too (it was, on the first build: the chip\n     rendered with the right counts and painted nothing). */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > [data-mobile-nav=\"header-activity\"] {\n    display: inline-flex !important;\n  }\n  [data-phase] header [data-slot=\"conversation.session.header.utilities\"] > [data-mobile-nav=\"header-info\"],\n  [data-phase] header [data-slot=\"conversation.session.header.utilities\"] > [data-mobile-nav=\"header-workbench\"] {\n    display: inline-flex !important;\n  }\n\n  /* Back button: 44pt touch target, leftmost column. */\n  [data-mobile-nav=\"header-back\"] {\n    display: inline-flex;\n    align-items: center;\n    justify-content: center;\n    width: 44px;\n    height: 44px;\n    padding: 0;\n    border: none;\n    background: transparent;\n    color: var(--dsw-alias-label-primary, inherit);\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"header-back\"]:active {\n    opacity: .6;\n  }\n\n  /* Info + workbench utility buttons, rightmost column. */\n  [data-mobile-nav=\"header-info\"],\n  [data-mobile-nav=\"header-workbench\"] {\n    display: inline-flex;\n    align-items: center;\n    justify-content: center;\n    width: 34px;\n    height: 34px;\n    padding: 0;\n    border: none;\n    border-radius: 50%;\n    background: transparent;\n    color: var(--dsw-alias-label-secondary, inherit);\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"header-info\"]:active,\n  [data-mobile-nav=\"header-workbench\"]:active {\n    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n  }\n  /* Icon family unification (real-device round 2, 2026-08-17): the \u24D8 text\n     glyph is gone (MobileSessionHeader.tsx now renders IconInfoOutline16,\n     a local 16px SVG built to match the primitives icon family) and the\n     workbench button's IconPanelLeftOutline16 is mirrored into a\n     panel-RIGHT glyph \u2014 there's no IconPanelRightOutline16 in primitives\n     (checked lib/types/icons/index.d.ts), and the plugin's own right-side\n     panel semantics are exactly the left icon flipped. Both buttons now\n     carry a same-size (16px), same-stroke-weight icon. */\n  [data-mobile-nav=\"header-workbench\"] svg {\n    transform: scaleX(-1);\n  }\n\n  /* Official Chat/Trajectory tablist: removed from layout entirely (S2.1 \u2014\n     visibility:hidden still held a 27px row, so the header carried the\n     view-switch row's band TWICE: 72 + 27 + gap = 104px measured at 390px,\n     and a real iPhone added ~54px of notch on top of that). The header's own\n     padding-bottom above is now the row's seat.\n     display:none does NOT break the view switch: HTMLElement.click()\n     dispatches synthetically and fires React's handler regardless of\n     rendering \u2014 only real pointer hit-testing needs a box, and this plugin\n     never relies on it (MobileSessionHeader always calls .click()). */\n  [data-phase] header [class$=\"_tabs\"][role=\"tablist\"] {\n    display: none;\n  }\n\n  /* View-switch row: \"current view name + dots\", replacing the (still\n     present, still clickable) official tablist visually. It renders inside\n     headerActions/headerUtilities, but titleRow's own position:relative\n     (set above) makes IT the containing block for absolute descendants \u2014\n     display:contents on titleCluster does not break that search \u2014 so\n     top:100% sits directly under the title regardless of the title row's\n     actual height, with no hardcoded offset to keep in sync. */\n  /* Activity chip (subagents / background tasks) rides the right end of the\n     same band. It is a SIBLING of the switch button, not a child \u2014 that\n     button spans the full row, so nesting would make every tap on the chip\n     switch views too \u2014 and it shares titleRow as its containing block, so\n     top:100% lands both on the same 28px line. z-index puts it above the\n     row it overlaps. */\n  [data-mobile-nav=\"header-activity\"] {\n    position: absolute;\n    right: 0;\n    top: 100%;\n    z-index: 1;\n    display: inline-flex;\n    align-items: center;\n    gap: 9px;\n    height: 28px;\n    padding: 0 2px 0 10px;\n    border: none;\n    background: transparent;\n    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));\n    font-family: inherit;\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  /* pointer-events:none so the invisible official trigger laid over this pill\n     (effects/native-trigger-overlay.ts) is what a tap reaches. The pill is\n     visuals only. */\n  [data-mobile-nav=\"activity-pill\"] {\n    pointer-events: none;\n    display: inline-flex;\n    align-items: center;\n    gap: 3px;\n    height: 28px;\n    padding: 0;\n    border: none;\n    background: transparent;\n    color: inherit;\n    font-family: inherit;\n    font-size: 12px;\n    line-height: 18px;\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"activity-pill\"]:active {\n    opacity: .55;\n  }\n  [data-mobile-nav=\"activity-count\"] {\n    font-variant-numeric: tabular-nums;\n  }\n  /* Steady green = everything settled. */\n  [data-mobile-nav=\"activity-dot\"] {\n    display: block;\n    width: 6px;\n    height: 6px;\n    margin-left: 1px;\n    border-radius: 50%;\n    background: var(--dsw-alias-state-success-primary, #16a34a);\n  }\n  /* A job that failed or was killed is not a success \u2014 never paint it green. */\n  [data-activity-state=\"warning\"] [data-mobile-nav=\"activity-dot\"] {\n    background: var(--dsw-alias-state-warn-primary, #d97706);\n  }\n  /* Pulsing blue = still running. Same state palette as the session dot. */\n  [data-activity-state=\"running\"] [data-mobile-nav=\"activity-dot\"] {\n    background: var(--dsw-alias-state-business-primary, #4f6ef7);\n    animation: dsh-zen-activity-pulse 1.4s ease-in-out infinite;\n  }\n  @keyframes dsh-zen-activity-pulse {\n    0%, 100% { opacity: 1; transform: scale(1); }\n    50% { opacity: .45; transform: scale(.72); }\n  }\n  @media (prefers-reduced-motion: reduce) {\n    [data-activity-state=\"running\"] [data-mobile-nav=\"activity-dot\"] {\n      animation: none;\n    }\n  }\n\n  [data-mobile-nav=\"header-viewrow\"] {\n    position: absolute;\n    left: 0;\n    right: 0;\n    top: 100%;\n    display: flex;\n    align-items: center;\n    justify-content: center;\n    gap: 6px;\n    height: 28px;\n    padding: 0;\n    border: none;\n    background: transparent;\n    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));\n    font-family: inherit;\n    font-size: 13px;\n    line-height: 18px;\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"header-viewrow-dots\"] {\n    display: inline-flex;\n    align-items: center;\n    gap: 3px;\n  }\n  [data-mobile-nav=\"header-viewrow-dots\"] > i {\n    display: block;\n    width: 4px;\n    height: 4px;\n    border-radius: 50%;\n    background: currentColor;\n    opacity: .35;\n    font-style: normal;\n  }\n  [data-mobile-nav=\"header-viewrow-dots\"] > i[data-active] {\n    opacity: 1;\n  }\n}\n";
+export declare const HEADER_CSS = "/* ---------- session header five-piece reflow (< 768px) ---------- */\n\n/* New elements render unconditionally (React does not know about media\n   queries); default them to hidden so 768px+ never sees them, then\n   re-enable inside the phone block below. Belt-and-braces alongside the\n   scoped rules \u2014 mirrors the existing [data-mobile-nav=\"*\"] desktop no-op\n   list in misc.css.ts. */\n[data-mobile-nav=\"header-back\"],\n[data-mobile-nav=\"header-viewrow\"],\n[data-mobile-nav=\"header-activity\"],\n[data-mobile-nav=\"header-info\"],\n[data-mobile-nav=\"header-workbench\"],\n/* The workbench close pill's default-hidden used to live in compat.css.ts \u2014\n   but EVERYTHING in layout/compat/misc sits inside one shared\n   (max-width: 1023px) block (opened at the top of layout, closed at the end\n   of misc), so that \"top-level\" rule silently never applied at >=1024 and\n   the pill rendered as an unstyled button on desktop (2026-08-17 report).\n   This file is appended after the shared block closes, so here it is truly\n   global; the <=767px :has() show rule in compat overrides it with\n   !important. */\n[data-mobile-nav=\"better-sidebar-close\"] {\n  display: none;\n}\n\n@media (max-width: 767px) {\n  /* The Files action targeted the dsh-web-ui-all (aionui) explorer sheet \u2014\n     a different, unrelated suite from the workbench entry this slice adds\n     (dsh-better-sidebar). Hidden here only; 768-1023px keeps it exactly as\n     v1.0.0 shipped it. */\n  [data-mobile-nav=\"files\"] {\n    display: none !important;\n  }\n\n  /* --- three-column header: [back 92px] [title, truly centered] [utilities 92px] --- */\n  /* The bottom padding is the view-switch row's seat: that row is\n     position:absolute (see the bottom of this file \u2014 it renders two levels\n     deep inside headerActions and can never be a grid item of titleRow), so\n     without a reserve it would hang over the message list. 28px = its\n     height. Unconditional rather than header:has([data-mobile-nav=\n     \"header-viewrow\"]) on purpose: :has() is silently dropped by pre-105\n     WebViews (see AGENTS.md) and a 28px overlap on the first message is a\n     worse failure than 28px of empty band in the (never observed in\n     practice) single-view session. Total header chrome: 48 + 28 = 76px.\n     Left/right 8px (S2.1 report leftover, fixed in S4): the official header\n     had zero horizontal padding, so the utilities button cluster's right\n     edge sat flush against the screen edge (x=390 at 390px width, no\n     margin). The 92px grid columns absorb this fine \u2014 they're fixed track\n     widths, only the center 1fr column shrinks by 16px. */\n  [data-phase] header {\n    position: relative;\n    /* Above the scroller's plain and relative-positioned message content, so\n       the ::after fade strip below actually paints over the messages sliding\n       under it (positioned z-auto boxes otherwise win by DOM order \u2014 the\n       scroller comes after the header). Deliberately tiny: the seat (7),\n       scroll-to-bottom (8) and every overlay this plugin owns (30+) stay\n       above. */\n    z-index: 2;\n    padding: 0 8px 28px !important;\n  }\n  /* No header bottom line \u2014 fade instead (real-device round 2, 2026-08-17).\n     The official header draws its border as a `::after` 1px bar (the\n     `border-bottom` on the header itself is transparent, just a layout\n     reserve \u2014 dsh-client-ui-conversation lib/client.js \".wSkVaW_header{\n     border-bottom:1px solid #0000}.wSkVaW_header:after{...height:1px;\n     position:absolute;bottom:1px...}\", verified live 2026-08-17), so the\n     bar is repurposed rather than hidden: restyled into a 20px strip\n     hanging just below the header that fades the messages in \u2014 the same\n     look the scroller's mask-image used to produce, without a mask on a\n     scroll container (iOS WebKit renders that as fog over the header, see\n     composer.css.ts \"no divider above OR below the message list\",\n     2026-08-23). color-mix instead of the transparent keyword: the host\n     writes its own seat gradient that way, and plain `transparent` is\n     rgba(0,0,0,0) \u2014 WebKit interpolates it through grey. */\n  [data-phase] header::after {\n    height: 20px !important;\n    top: 100% !important;\n    bottom: auto !important;\n    background: linear-gradient(to bottom, var(--dsw-alias-bg-base), color-mix(in srgb, var(--dsw-alias-bg-base) 0%, transparent)) !important;\n  }\n  /* grid-row: 1 on every item is load-bearing, not decoration (S2.1 fix for\n     the \"\u6807\u9898\u88AB\u6324\u4E0B\u53BB\" report). The three items are placed with explicit\n     grid-column but arrive in DOM order crumbs(2) \u2192 headerActions(1) \u2192\n     headerUtilities(3): sparse auto-placement never moves its cursor\n     backwards, so headerActions and headerUtilities were pushed onto an\n     implicit SECOND row. Measured at 390px: row1 = crumbs 28px, row2 =\n     back button 44px, titleRow = 72px with the title stuck at the top\n     instead of centered. Pinning the row makes it one 48px band again. */\n  [data-phase] header [class$=\"_titleRow\"] {\n    position: relative;\n    display: grid;\n    grid-template-columns: 92px 1fr 92px;\n    grid-template-rows: minmax(48px, auto);\n    align-items: center;\n    min-height: 48px;\n    padding: 0 !important;\n  }\n  /* Flatten the official cluster so its two children (crumbs, headerActions)\n     become direct grid items of titleRow instead of a nested flex box. */\n  [data-phase] header [class$=\"_titleCluster\"] {\n    display: contents;\n  }\n  /* margin-left: 0 cancels layout.css.ts's shared <=1023px\n     \"margin-left: auto !important\" on this exact selector (it pushed the\n     Files button to the row's right edge in the old non-grid header;\n     inside our grid column it instead shoves the back button 48px right of\n     the column's start \u2014 the auto margin absorbs the leftover space\n     between the button's content width and the 92px column). */\n  [data-phase] header [class$=\"_headerActions\"] {\n    grid-column: 1;\n    grid-row: 1;\n    justify-self: start;\n    margin-left: 0 !important;\n    display: flex;\n    align-items: center;\n    min-width: 0;\n  }\n  /* layout.css.ts's shared <=1023px block hides this element outright\n     (header > :first-child > :last-child { display: none !important },\n     specificity (0,3,1) \u2014 v1.0.0 relocated the desktop Session-log capsule\n     to the drawer footer on every narrow width). That selector is repeated\n     here at equal specificity so the later source order wins the display\n     property; the class-suffix selector alone (0,2,1) would silently lose. */\n  [data-phase] header [class$=\"_headerUtilities\"],\n  [data-phase] header > :first-child > :last-child {\n    grid-column: 3;\n    grid-row: 1;\n    justify-self: end;\n    display: flex !important;\n    align-items: center;\n    gap: 4px;\n    min-width: 0;\n  }\n  /* justify-self: stretch (the grid default) so this fills the whole 1fr\n     column as a definite-width box \u2014 center/center-content happens inside\n     it. justify-self: center (tried first) sizes the item to its content\n     with no automatic column cap, and the obvious fix \u2014 max-width: 100% \u2014\n     resolves against the WRONG box here (measured 93.6px at 390px, where\n     the column is ~206px): the item's DOM parent (titleCluster) is\n     display:contents, and percentage max-width does not reliably resolve\n     through a boxless ancestor to the grid track. Stretching sidesteps the\n     percentage entirely \u2014 but layout.css.ts's shared <=1023px block ALSO\n     caps this exact selector at max-width: 24vw !important (93.6px at\n     390px \u2014 the value this rule used to silently inherit once its own\n     max-width was dropped in favor of stretch), so that must be reset to\n     none here too. */\n  [data-phase] header [class$=\"_crumbs\"] {\n    grid-column: 2;\n    grid-row: 1;\n    justify-self: stretch;\n    max-width: none !important;\n    display: flex;\n    align-items: center;\n    justify-content: center;\n    min-width: 0;\n    overflow: hidden;\n  }\n  /* Subagent sessions keep ONE ancestor crumb (2026-08-18): the PC header\n     lets you tap the parent session's title to switch back \u2014 that affordance\n     was lost on phone when the whole parent chain was hidden as \"\u591A\u4F59\u9879\".\n     Show only the immediate parent (for agent-teams member sessions that IS\n     the captain/main session; deeper ancestors stay hidden \u2014 a 3-level chain\n     cannot fit the ~206px center column at 390px). The parent crumb is the\n     official breadcrumb <button> (dsh-client-ui-conversation renders\n     open(parentId) as its onClick), so tapping needs no JS from this plugin,\n     and main sessions (chain length 1) have no :nth-last-child(2) seg at\n     all \u2014 the centered single title is pixel-identical to before. */\n  [data-phase] header [class$=\"_crumbSeg\"]:not(:nth-last-child(-n+2)) {\n    display: none !important;\n  }\n  [data-phase] header [class$=\"_crumbSeg\"]:nth-last-child(2) {\n    display: inline-flex;\n    align-items: center;\n    flex: none;\n    min-width: 0;\n    max-width: 38%;\n  }\n  /* Ancestors BEFORE the parent seg are hidden, which would leave the\n     parent seg's own leading \"/\" dangling at the start of the title. */\n  [data-phase] header [class$=\"_crumbSeg\"]:nth-last-child(2) [class$=\"_crumbSep\"] {\n    display: none !important;\n  }\n  /* Parent crumb: small tertiary text so the 19px current title stays the\n     visual anchor; min-height keeps a finger-sized target inside the 48px\n     row. Specificity (0,4,1) outranks the shared 19px _crumb rule below. */\n  [data-phase] header [class$=\"_crumbSeg\"]:nth-last-child(2) [class$=\"_crumb\"] {\n    font-size: 13px;\n    font-weight: 400;\n    color: var(--dsw-alias-label-tertiary, rgba(0, 0, 0, .45));\n    min-height: 44px;\n    display: inline-flex;\n    align-items: center;\n    padding: 0 2px 0 6px;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-phase] header [class$=\"_crumbSeg\"]:last-child {\n    display: flex;\n    align-items: center;\n    min-width: 0;\n    max-width: 100%;\n  }\n  /* The last seg's own \"/\" is the divider between parent and current title \u2014\n     it only exists when there IS an ancestor (index > 0), so it can simply\n     stay visible now that the parent seg shows. (It used to be hidden here:\n     with the parent hidden it dangled before the title.) */\n  /* BOTH selectors are required: [class$=] matches the whole class\n     ATTRIBUTE's suffix, and the current-session title button's attribute is\n     \"wSkVaW_crumb wSkVaW_crumbCurrent\" \u2014 it ends in _crumbCurrent, so the _crumb\n     suffix selector alone silently missed the one element that matters\n     (measured live: the title stayed 14px while the rule sat in the bundle,\n     2026-08-17). */\n  [data-phase] header [class$=\"_crumb\"],\n  [data-phase] header [class$=\"_crumbCurrent\"] {\n    overflow: hidden;\n    text-overflow: ellipsis;\n    white-space: nowrap;\n    min-width: 0;\n    max-width: 100%;\n    /* Real-device feedback (2026-08-17): the session title read too small\n       next to the enlarged header icons \u2014 19px sits just under the home\n       screen's 22px workspace title, keeping the two-level hierarchy. */\n    font-size: 19px;\n    font-weight: 600;\n  }\n\n  /* Running-status dot: no official element to reposition (the header\n     renders only the crumb title, the two action slots, and the tablist \u2014\n     no status indicator), so this is the plan's documented fallback \u2014\n     read the data ourselves and draw it (effects/header-status.ts stamps\n     data-mobile-nav-dot on the frame). A ::after on the title crumb keeps\n     it truly inline with the (centered, truncated) text instead of a\n     separately positioned box that would fight the centering math. */\n  [data-phase] header [class$=\"_crumbCurrent\"]::after {\n    content: '';\n    display: none;\n    width: 6px;\n    height: 6px;\n    margin-left: 6px;\n    border-radius: 50%;\n    vertical-align: middle;\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot] header [class$=\"_crumbCurrent\"]::after {\n    display: inline-block;\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot=\"ongoing\"] header [class$=\"_crumbCurrent\"]::after {\n    background: var(--dsw-alias-state-business-primary, #4f6ef7);\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot=\"warning\"] header [class$=\"_crumbCurrent\"]::after {\n    background: var(--dsw-alias-state-warn-primary, #d97706);\n  }\n  [data-mobile-nav=\"frame\"][data-mobile-nav-dot=\"done\"] header [class$=\"_crumbCurrent\"]::after {\n    background: var(--dsw-alias-state-success-primary, #16a34a);\n  }\n\n  /* Everything else the official header puts in these two list slots \u2014 the\n     agent-preset mode badge, the jobs/subagent trigger, the desktop\n     Session-log download capsule, and this plugin's own legacy directory\n     toggle \u2014 is the \"\u4E0D\u5E38\u9A7B\" set the design defers to the S4 info card.\n     Scoped by the slots' own [data-slot] wrapper (a stable, non-hashed\n     contract marker) rather than enumerating each registrant, so a future\n     third-party header action is hidden by default too. */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > *,\n  [data-phase] header [data-slot=\"conversation.session.header.utilities\"] > * {\n    display: none !important;\n  }\n  /* Native background-task / subagent entries (rewritten for DSH 0.1.1,\n     2026-08-21). Three upstream changes killed the old \"park the root as a\n     zero-width anchor, hide the trigger, forward the tap\" design at once:\n\n     - the subagent entry moved out of header.actions into the new\n       conversation.session.header.lineage slot (inside the breadcrumb);\n     - its root's class attribute is now \"ZKlsPq_root \" \u2014 with a TRAILING\n       SPACE \u2014 so a [class$=\"_root\"] anchor matches nothing at all;\n     - the trigger only reacts to TRUSTED input: .click() and synthetic\n       pointer/mouse events leave aria-expanded untouched (measured on device\n       with every plugin override stripped), so forwarding a tap in JS can\n       never open it again.\n\n     The trigger's geometry is therefore owned at runtime by\n     effects/native-trigger-overlay.ts, which lays the REAL button\n     transparently over the activity pill \u2014 a genuine finger tap lands on the\n     official element. Nothing in this stylesheet may size, hide, or set\n     pointer-events on the trigger: that is exactly what would take the tap\n     target away again.\n\n     CSS keeps only two chores. Dissolve the root so its box (and its\n     stray separator, hidden below) stops occupying the breadcrumb, and let\n     the trigger participate from wherever the overlay pins it. And no menu\n     re-anchoring anymore: the 0.1.1 popover portals to <body> as\n     position:fixed and positions itself from the trigger's viewport rect\n     (measured 336px wide, fully on screen at 411px). */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > *:has(> button[class$=\"_trigger\"]),\n  [data-phase] header [data-slot=\"conversation.session.header.lineage\"] > *:has(> button[class$=\"_trigger\"]) {\n    display: contents !important;\n  }\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] [class$=\"_separator\"],\n  [data-phase] header [data-slot=\"conversation.session.header.lineage\"] [class$=\"_separator\"] {\n    display: none !important;\n  }\n  /* The agent-preset mode badge specifically survives the blanket hide\n     above: layout.css.ts's shared <=1023px block targets it directly\n     (header [class$=\"_label\"]:has(> svg) { display: block !important }),\n     specificity (0,3,1), higher than the [data-slot] wrapper rule (0,2,1) \u2014\n     display wins on specificity before source order, so a same-selector\n     override is needed here too. */\n  [data-phase] header [class$=\"_label\"]:has(> svg) {\n    display: none !important;\n  }\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > [data-mobile-nav=\"header-back\"] {\n    display: inline-flex !important;\n  }\n  /* header-viewrow is position:absolute (see below), so its re-shown\n     display value must match the flex layout its own rule declares. */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > [data-mobile-nav=\"header-viewrow\"] {\n    display: flex !important;\n  }\n  /* Our own chip lives in the same slot, so the blanket hide above swallows\n     it unless it is named here too (it was, on the first build: the chip\n     rendered with the right counts and painted nothing). */\n  [data-phase] header [data-slot=\"conversation.session.header.actions\"] > [data-mobile-nav=\"header-activity\"] {\n    display: inline-flex !important;\n  }\n  [data-phase] header [data-slot=\"conversation.session.header.utilities\"] > [data-mobile-nav=\"header-info\"],\n  [data-phase] header [data-slot=\"conversation.session.header.utilities\"] > [data-mobile-nav=\"header-workbench\"] {\n    display: inline-flex !important;\n  }\n\n  /* Back button: 44pt touch target, leftmost column. */\n  [data-mobile-nav=\"header-back\"] {\n    display: inline-flex;\n    align-items: center;\n    justify-content: center;\n    width: 44px;\n    height: 44px;\n    padding: 0;\n    border: none;\n    background: transparent;\n    color: var(--dsw-alias-label-primary, inherit);\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"header-back\"]:active {\n    opacity: .6;\n  }\n\n  /* Info + workbench utility buttons, rightmost column. */\n  [data-mobile-nav=\"header-info\"],\n  [data-mobile-nav=\"header-workbench\"] {\n    display: inline-flex;\n    align-items: center;\n    justify-content: center;\n    width: 34px;\n    height: 34px;\n    padding: 0;\n    border: none;\n    border-radius: 50%;\n    background: transparent;\n    color: var(--dsw-alias-label-secondary, inherit);\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"header-info\"]:active,\n  [data-mobile-nav=\"header-workbench\"]:active {\n    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n  }\n  /* Icon family unification (real-device round 2, 2026-08-17): the \u24D8 text\n     glyph is gone (MobileSessionHeader.tsx now renders IconInfoOutline16,\n     a local 16px SVG built to match the primitives icon family) and the\n     workbench button's IconPanelLeftOutline16 is mirrored into a\n     panel-RIGHT glyph \u2014 there's no IconPanelRightOutline16 in primitives\n     (checked lib/types/icons/index.d.ts), and the plugin's own right-side\n     panel semantics are exactly the left icon flipped. Both buttons now\n     carry a same-size (16px), same-stroke-weight icon. */\n  [data-mobile-nav=\"header-workbench\"] svg {\n    transform: scaleX(-1);\n  }\n\n  /* Official Chat/Trajectory tablist: removed from layout entirely (S2.1 \u2014\n     visibility:hidden still held a 27px row, so the header carried the\n     view-switch row's band TWICE: 72 + 27 + gap = 104px measured at 390px,\n     and a real iPhone added ~54px of notch on top of that). The header's own\n     padding-bottom above is now the row's seat.\n     display:none does NOT break the view switch: HTMLElement.click()\n     dispatches synthetically and fires React's handler regardless of\n     rendering \u2014 only real pointer hit-testing needs a box, and this plugin\n     never relies on it (MobileSessionHeader always calls .click()). */\n  [data-phase] header [class$=\"_tabs\"][role=\"tablist\"] {\n    display: none;\n  }\n\n  /* View-switch row: \"current view name + dots\", replacing the (still\n     present, still clickable) official tablist visually. It renders inside\n     headerActions/headerUtilities, but titleRow's own position:relative\n     (set above) makes IT the containing block for absolute descendants \u2014\n     display:contents on titleCluster does not break that search \u2014 so\n     top:100% sits directly under the title regardless of the title row's\n     actual height, with no hardcoded offset to keep in sync. */\n  /* Activity chip (subagents / background tasks) rides the right end of the\n     same band. It is a SIBLING of the switch button, not a child \u2014 that\n     button spans the full row, so nesting would make every tap on the chip\n     switch views too \u2014 and it shares titleRow as its containing block, so\n     top:100% lands both on the same 28px line. z-index puts it above the\n     row it overlaps. */\n  [data-mobile-nav=\"header-activity\"] {\n    position: absolute;\n    right: 0;\n    top: 100%;\n    z-index: 1;\n    display: inline-flex;\n    align-items: center;\n    gap: 9px;\n    height: 28px;\n    padding: 0 2px 0 10px;\n    border: none;\n    background: transparent;\n    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));\n    font-family: inherit;\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  /* pointer-events:none so the invisible official trigger laid over this pill\n     (effects/native-trigger-overlay.ts) is what a tap reaches. The pill is\n     visuals only. */\n  [data-mobile-nav=\"activity-pill\"] {\n    pointer-events: none;\n    display: inline-flex;\n    align-items: center;\n    gap: 3px;\n    height: 28px;\n    padding: 0;\n    border: none;\n    background: transparent;\n    color: inherit;\n    font-family: inherit;\n    font-size: 12px;\n    line-height: 18px;\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"activity-pill\"]:active {\n    opacity: .55;\n  }\n  [data-mobile-nav=\"activity-count\"] {\n    font-variant-numeric: tabular-nums;\n  }\n  /* Steady green = everything settled. */\n  [data-mobile-nav=\"activity-dot\"] {\n    display: block;\n    width: 6px;\n    height: 6px;\n    margin-left: 1px;\n    border-radius: 50%;\n    background: var(--dsw-alias-state-success-primary, #16a34a);\n  }\n  /* A job that failed or was killed is not a success \u2014 never paint it green. */\n  [data-activity-state=\"warning\"] [data-mobile-nav=\"activity-dot\"] {\n    background: var(--dsw-alias-state-warn-primary, #d97706);\n  }\n  /* Pulsing blue = still running. Same state palette as the session dot. */\n  [data-activity-state=\"running\"] [data-mobile-nav=\"activity-dot\"] {\n    background: var(--dsw-alias-state-business-primary, #4f6ef7);\n    animation: dsh-zen-activity-pulse 1.4s ease-in-out infinite;\n  }\n  @keyframes dsh-zen-activity-pulse {\n    0%, 100% { opacity: 1; transform: scale(1); }\n    50% { opacity: .45; transform: scale(.72); }\n  }\n  @media (prefers-reduced-motion: reduce) {\n    [data-activity-state=\"running\"] [data-mobile-nav=\"activity-dot\"] {\n      animation: none;\n    }\n  }\n\n  [data-mobile-nav=\"header-viewrow\"] {\n    position: absolute;\n    left: 0;\n    right: 0;\n    top: 100%;\n    display: flex;\n    align-items: center;\n    justify-content: center;\n    gap: 6px;\n    height: 28px;\n    padding: 0;\n    border: none;\n    background: transparent;\n    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));\n    font-family: inherit;\n    font-size: 13px;\n    line-height: 18px;\n    cursor: pointer;\n    touch-action: manipulation;\n    -webkit-tap-highlight-color: transparent;\n  }\n  [data-mobile-nav=\"header-viewrow-dots\"] {\n    display: inline-flex;\n    align-items: center;\n    gap: 3px;\n  }\n  [data-mobile-nav=\"header-viewrow-dots\"] > i {\n    display: block;\n    width: 4px;\n    height: 4px;\n    border-radius: 50%;\n    background: currentColor;\n    opacity: .35;\n    font-style: normal;\n  }\n  [data-mobile-nav=\"header-viewrow-dots\"] > i[data-active] {\n    opacity: 1;\n  }\n}\n";
 //# sourceMappingURL=header.css.d.ts.map

package/lib/types/client/styles/header.css.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"header.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/header.css.ts"],"names":[],"mappings":"AAiBA,eAAO,MAAM,UAAU,k2tBAuftB,CAAA"}
+{"version":3,"file":"header.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/header.css.ts"],"names":[],"mappings":"AAiBA,eAAO,MAAM,UAAU,8rvBAogBtB,CAAA"}

package/lib/types/client/styles/turn-fold.css.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"turn-fold.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/turn-fold.css.ts"],"names":[],"mappings":"AAsIA,eAAO,MAAM,aAAa,QAyBzB,CAAA"}
+{"version":3,"file":"turn-fold.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/turn-fold.css.ts"],"names":[],"mappings":"AAgKA,eAAO,MAAM,aAAa,QAyBzB,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-zen-remote",
-  "version": "1.1.5",
+  "version": "1.1.7",
   "description": "把 DeepSeek Harness 变成手机 App：移动端界面重排（两级页面栈、会话列表主屏、composer 重排、手势、附件上传）+ 配对码认证网关 + PWA 安装 + 真 Web Push。Complete mobile plugin for DeepSeek Harness (DSH): app-shell mobile UI, pairing-code gateway for public-internet access behind your own reverse proxy, installable PWA, offline service worker, and real Web Push agent-done notifications.",
   "license": "MIT",
   "type": "module",

package/src/client/effects/turn-fold.ts

@@ -14,6 +14,14 @@ const PHONE_QUERY = '(max-width: 767px)'
  *   `=0` opts back out). */
 const DESKTOP_KEY = 'dsh-mobile-nav.turn-fold-desktop'
 const DESKTOP_PARAM = 'mobile-nav-turn-fold'
+/** Last answer the row config gave. The fetch is a round-trip and the phone
+ * breakpoint is not, so a desktop reader used to watch a whole session render
+ * unfolded and then collapse at once, every page load (issue #3). Remembering
+ * the answer switches the fold on before first paint from the second load on.
+ * Enable-only: turning the row knob back off clears this, so that load still
+ * folds and the next one does not — a stale fold is a chip click away, a
+ * one-way `disableDesktop` is a state machine nobody asked for. */
+const DESKTOP_CACHE_KEY = 'dsh-mobile-nav.turn-fold-desktop-seen'
 /** Root attribute the stylesheet keys the width-independent rules on. */
 const DESKTOP_ATTR = 'data-mnav-desktop-fold'
 
@@ -58,10 +66,12 @@ const TURN_HEAD_KINDS = new Set(['user', 'steering'])
  * rendered inside an assistant-step row, beside that step's prose. */
 export const THINK = '[data-variant="think"]'
 
-/** Attribute the phone stylesheet turns into `display: none`. Still written
- * per element for the one case the stylesheet cannot express on its own: an
- * assistant-step row whose entire body is reasoning, which has to go as a
- * whole row (see {@link foldsWholeRow}). */
+/** Attribute the phone stylesheet turns into `display: none`. Written for the
+ * one case the stylesheet cannot express on its own: an assistant-step row
+ * whose entire body is reasoning, which has to go as a whole row (see
+ * {@link foldsWholeRow}). Because it is the only thing hiding that row, it is
+ * written from {@link markWholeRows} in the observer callback rather than the
+ * scan a frame later — see that function for what the frame cost. */
 const FOLD = 'data-mnav-fold'
 /** Per-item override written while its turn is expanded. */
 export const OPEN = 'data-mnav-fold-open'
@@ -73,6 +83,9 @@ export const OPEN = 'data-mnav-fold-open'
  * stylesheet a no-op — content visible — if this effect never runs. */
 const ACTIVE_ATTR = 'data-mnav-fold-on'
 
+/** Selector of the one row kind that can fold whole — see {@link foldsWholeRow}. */
+const STEP_SELECTOR = '[data-chat-flow-kind="assistant-step"]'
+
 /**
  * True when the reasoning rows are the ONLY thing this row renders, so the
  * whole flow item has to go: the flow column is `display: flex` with
@@ -237,14 +250,67 @@ export function installTurnFold(ctx: ClientContext): void {
       // its row-level fold after prose started arriving in the same DOM node
       // (React updates the row in place), hiding the streaming reply until a
       // completion re-render rebuilt the row — the "reply only appears when
-      // the turn finishes" phone bug (2026-08-18).
-      for (const stale of flow.querySelectorAll(`[${FOLD}]`)) {
+      // the turn finishes" phone bug (2026-08-18). {@link OPEN} needs the
+      // same sweep on its own account: it is what releases a row from the
+      // stylesheet's reasoning rules, so a stale one shows the reasoning of
+      // a turn the reader has since folded.
+      for (const stale of flow.querySelectorAll(`[${FOLD}], [${OPEN}]`)) {
         if (liveItems.has(stale)) continue
         stale.removeAttribute(FOLD)
         stale.removeAttribute(OPEN)
       }
     }
 
+    /**
+     * Fold (or release) the reasoning-only rows this mutation batch touched,
+     * synchronously.
+     *
+     * The full {@link scan} is rAF-coalesced, and React commits after that
+     * frame's rAF phase, so a scan scheduled from a mutation lands one PAINTED
+     * frame later. For everything else that is invisible — the stylesheet
+     * already hid it by the host's own markers before the effect looked. For
+     * the whole-row fold, which nothing but {@link FOLD} hides, the reader saw
+     * that frame: a blank 16px band on the way in (the flow column's gap,
+     * which an emptied flex item still claims), and — worse — the row still
+     * hidden for a frame after prose started arriving into it, so the reply
+     * appeared to stutter (issue #3).
+     *
+     * A MutationObserver callback is a microtask: it runs at the end of the
+     * task that mutated the DOM, before that frame's rendering update. Marking
+     * here is therefore never a frame late, in either direction.
+     *
+     * ponytail: O(rows touched by the batch), not O(rows). If streaming ever
+     * feels heavy, the cheap win is skipping batches whose records are all
+     * characterData — the fold verdict only changes when elements do.
+     */
+    const markWholeRows = (records: readonly MutationRecord[]): void => {
+      const rows = new Set<Element>()
+      for (const record of records) {
+        const target = record.target
+        if (target instanceof Element) {
+          const row = target.closest(STEP_SELECTOR)
+          if (row !== null) rows.add(row)
+        }
+        for (const node of record.addedNodes) {
+          if (!(node instanceof Element)) continue
+          if (node.matches(STEP_SELECTOR)) rows.add(node)
+          for (const nested of node.querySelectorAll(STEP_SELECTOR)) rows.add(nested)
+        }
+      }
+      for (const row of rows) {
+        // Exactly what {@link groupsOf} walks: a direct child of the chat flow
+        // column. This is the scoping that keeps the effect Chat-only — the
+        // mutation records reach the whole document, so without it a row in
+        // any other view that seats chat nodes would get hidden with no chip
+        // to bring it back. It also drops rows detached since the batch.
+        const parent = row.parentElement
+        if (parent === null || !parent.matches(FLOW)) continue
+        const thinks = [...row.querySelectorAll(THINK)]
+        if (thinks.length > 0 && foldsWholeRow(row, thinks)) row.setAttribute(FOLD, '')
+        else row.removeAttribute(FOLD)
+      }
+    }
+
     const schedule = (): void => {
       // The locale subscription below lives outside attach/detach, so this
       // guard is what keeps a late dictionary registration from marking up
@@ -275,7 +341,7 @@ export function installTurnFold(ctx: ClientContext): void {
 
     const clear = (): void => {
       for (const chip of document.querySelectorAll(CHIP_SELECTOR)) chip.remove()
-      for (const item of document.querySelectorAll(`[${FOLD}]`)) {
+      for (const item of document.querySelectorAll(`[${FOLD}], [${OPEN}]`)) {
         item.removeAttribute(FOLD)
         item.removeAttribute(OPEN)
       }
@@ -284,7 +350,10 @@ export function installTurnFold(ctx: ClientContext): void {
     const attach = (): void => {
       if (observer !== null) return
       document.documentElement.setAttribute(ACTIVE_ATTR, '')
-      observer = new MutationObserver(schedule)
+      observer = new MutationObserver((records) => {
+        markWholeRows(records)
+        schedule()
+      })
       observer.observe(document.body, { childList: true, subtree: true })
       document.addEventListener('click', onClick)
       scan()
@@ -317,10 +386,17 @@ export function installTurnFold(ctx: ClientContext): void {
 
     if (narrow.matches) attach()
     narrow.addEventListener('change', onChange)
-    if (desktopOptIn()) enableDesktop()
-    // The row config arrives async; a late enable just attaches then. Not
-    // awaited before phone attach — folding must not wait on a round-trip.
-    else void desktopConfigured().then((on) => (on ? enableDesktop() : undefined))
+    // Both switches are synchronous reads, so a returning reader folds before
+    // first paint. Not awaited before phone attach either — folding must not
+    // wait on a round-trip.
+    if (desktopOptIn() || localStorage.getItem(DESKTOP_CACHE_KEY) === '1') enableDesktop()
+    // The row config still arrives async, and remains the authority: a late
+    // yes attaches then and is remembered, a no forgets. A late answer after
+    // dispose is a no-op inside enableDesktop.
+    void desktopConfigured().then((on) => {
+      if (on) { localStorage.setItem(DESKTOP_CACHE_KEY, '1'); enableDesktop() }
+      else localStorage.removeItem(DESKTOP_CACHE_KEY)
+    })
     // A language switch changes the chip copy of every already-rendered turn.
     const stopLocale = ctx.locale.subscribe(schedule)
     return () => {

package/src/client/styles/composer.css.ts

@@ -227,22 +227,29 @@ export const COMPOSER_CSS = `/* ---------- phone composer (< 768px) ---------- *
   }
 
   /* --- 6. no divider above OR below the message list ---
-     Instead of a rule the messages butt against, the message scroller
-     fades out over its last 26px (S3, no divider above the composer) AND
-     fades in over its first 20px (S3.1 real-device round 2: the header's
-     own bottom line is removed too, styles/header.css.ts's
-     \`header::after\` rule). The mask lives on the scroll body (NOT on the
-     header or the composer): a mask clips everything it paints, and both
-     surfaces host position:fixed children (composer's permission/model
-     sheets, any future header overlay) that must not be clipped.
-     \`mask-image\` can only be declared once per element, so both fades are
-     ONE linear-gradient rather than two separate declarations (the second
-     would silently replace the first) — this is the merge of what used to
-     be S3's bottom-only mask. */
-  [class$="_scrollBody"] {
-    -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 20px, #000 calc(100% - 26px), transparent 100%);
-    mask-image: linear-gradient(to bottom, transparent 0, #000 20px, #000 calc(100% - 26px), transparent 100%);
-  }
+     Instead of a rule the messages butt against, they fade near both edges.
+     This used to be ONE mask-image on the message scroller; iOS WebKit
+     turned that into fog over the header (user report 2026-08-23): a mask
+     on a scroll container is applied in CONTENT coordinates there (the fade
+     bands scroll away with the messages) and, worse, it breaks the
+     container's own overflow clipping — content scrolled out of view keeps
+     painting, straight over the header and status bar. Engine bug with no
+     iOS escape hatch (every iOS browser is WebKit), so the fades moved off
+     the scroller entirely:
+
+     - fade-IN under the header: the header's own ::after, restyled into a
+       20px gradient strip — styles/header.css.ts ("no header bottom line").
+     - fade-OUT above the composer: nothing of ours. The official composer
+       seat already carries \`background: linear-gradient(transparent 0,
+       bg 36px)\` on its sticky self (dsh-client-ui-conversation lib/
+       client.js .wSkVaW_composerSeat) and that is the entire visible
+       effect; the mask's own bottom band landed inside the safe-area
+       padding below the card and painted nothing. If the bottom edge ever
+       reads harsh, hang a ::before strip off the seat the same way the
+       header does — do NOT put a mask back on the scroller.
+
+     Painted strips instead of a mask is a fair trade only because the page
+     background is one flat color — which it is (--dsw-alias-bg-base). */
   [class$="_composerSeat"],
   [class$="_composerStack"] {
     border-top: none !important;

package/src/client/styles/header.css.ts

@@ -65,6 +65,13 @@ export const HEADER_CSS = `/* ---------- session header five-piece reflow (< 768
      widths, only the center 1fr column shrinks by 16px. */
   [data-phase] header {
     position: relative;
+    /* Above the scroller's plain and relative-positioned message content, so
+       the ::after fade strip below actually paints over the messages sliding
+       under it (positioned z-auto boxes otherwise win by DOM order — the
+       scroller comes after the header). Deliberately tiny: the seat (7),
+       scroll-to-bottom (8) and every overlay this plugin owns (30+) stay
+       above. */
+    z-index: 2;
     padding: 0 8px 28px !important;
   }
   /* No header bottom line — fade instead (real-device round 2, 2026-08-17).
@@ -72,14 +79,20 @@ export const HEADER_CSS = `/* ---------- session header five-piece reflow (< 768
      \`border-bottom\` on the header itself is transparent, just a layout
      reserve — dsh-client-ui-conversation lib/client.js ".wSkVaW_header{
      border-bottom:1px solid #0000}.wSkVaW_header:after{...height:1px;
-     position:absolute;bottom:1px...}", verified live 2026-08-17), so
-     hiding the pseudo-element is enough; the header's own border-bottom
-     never had a visible color to begin with. The message scroller now
-     fades in from under the header instead (styles/composer.css.ts, "no
-     divider above OR below the message list" — the two edges share one
-     mask-image on [class$="_scrollBody"]). */
+     position:absolute;bottom:1px...}", verified live 2026-08-17), so the
+     bar is repurposed rather than hidden: restyled into a 20px strip
+     hanging just below the header that fades the messages in — the same
+     look the scroller's mask-image used to produce, without a mask on a
+     scroll container (iOS WebKit renders that as fog over the header, see
+     composer.css.ts "no divider above OR below the message list",
+     2026-08-23). color-mix instead of the transparent keyword: the host
+     writes its own seat gradient that way, and plain \`transparent\` is
+     rgba(0,0,0,0) — WebKit interpolates it through grey. */
   [data-phase] header::after {
-    display: none !important;
+    height: 20px !important;
+    top: 100% !important;
+    bottom: auto !important;
+    background: linear-gradient(to bottom, var(--dsw-alias-bg-base), color-mix(in srgb, var(--dsw-alias-bg-base) 0%, transparent)) !important;
   }
   /* grid-row: 1 on every item is load-bearing, not decoration (S2.1 fix for
      the "标题被挤下去" report). The three items are placed with explicit

package/src/client/styles/turn-fold.css.ts

@@ -21,6 +21,9 @@ import { OPEN, PROCESS_KINDS, THINK } from '../effects/turn-fold.ts'
 /** Mirror of the root attribute effects/turn-fold.ts holds while attached. */
 const ACTIVE = 'data-mnav-fold-on'
 
+/** One assistant-step row, inside an active fold. */
+const STEP = `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="assistant-step"]`
+
 /**
  * Born folded — the reason a new tool call no longer blinks into view.
  *
@@ -37,22 +40,45 @@ const ACTIVE = 'data-mnav-fold-on'
  * block is live for exactly the widths the fold is, and hides nothing at all
  * when the effect never ran.
  *
- * One case stays with the effect: an assistant-step row whose whole body is
- * reasoning has to be hidden as a row (an emptied-out flex item still claims
- * the flow column's 16px gap), and "this row has nothing but Think in it" is
- * not a selector. Its rows therefore still fold a frame late — as blank
- * space, not as content, since the Think rows below are hidden here.
+ * The Think rule reads {@link OPEN} off the ROW as well as off the block:
+ * a row folded whole (see {@link WHOLE_STEP}) is the item the effect marks,
+ * so an expanded turn carries the override on the row and its reasoning
+ * would otherwise stay hidden behind this rule — the reader clicked the chip
+ * and got an empty band (issue #3, 2026-08-25).
  */
 const BORN_FOLDED = [
   ...PROCESS_KINDS.map((kind) => `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="${kind}"]:not([${OPEN}])`),
-  `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="assistant-step"] ${THINK}:not([${OPEN}])`,
+  `${STEP}:not([${OPEN}]) ${THINK}:not([${OPEN}])`,
 ].join(',\n')
 
+/*
+ * The one folded item with no selector of its own: an assistant-step row that
+ * holds reasoning and nothing else. It has to go as a ROW — the flow column is
+ * `display: flex` with `gap: 16px`, so a row whose every child is hidden still
+ * claims its gap and the reader sees a blank band — and "this row has nothing
+ * but Think in it" cannot be written as a selector.
+ *
+ * `:has()` looks like it can: "holds reasoning, holds no content block that is
+ * not reasoning". It cannot, safely. Every wrapper between the row and the
+ * blocks is itself a non-reasoning element, so the guard has to name the exact
+ * depth of the blocks — and the real tree is
+ * flowItem > seat > AssistantMarkdown root > body > blocks, one level deeper
+ * than the host's own component suggests, because the slot seat adds a wrapper
+ * the component never sees. A selector pinned to that depth silently stops
+ * matching the day a wrapper moves, with nothing to say why.
+ *
+ * So the row stays with effects/turn-fold.ts, which walks the tree instead of
+ * assuming its shape — but marks it synchronously in the MutationObserver
+ * callback (a microtask, before the frame paints) rather than a rAF later.
+ */
+
 /** The fold + chip rules, with every selector prefixed by `scope`. */
 const rules = (scope: string): string => `
-  /* Folded process: tool-call / context / command rows and the Think
-     disclosures inside an assistant step. !important because the official
-     flow item and ReasoningRow both set their own display. */
+  /* The reasoning-only row (see above), which effects/turn-fold.ts marks
+     itself because no selector can find it. Everything else is already hidden
+     by BORN_FOLDED, by the host's own markers — this rule is what that one
+     case rides on. !important because the official flow item and ReasoningRow
+     both set their own display. */
   ${scope} [data-mnav-fold]:not([data-mnav-fold-open]) {
     display: none !important;
   }