dsh-zen-remote 2.3.7 → 2.3.9

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/* The composer-chips strip (effects/model-sheet-extras.ts) \u2014 same\n   every-width default as the picker above: the phone block re-shows it\n   inside the dock rail; the desktop shell keeps none. */\n[data-mobile-nav=\"composer-chips\"] {\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    /* One line, always: the model pill is the only shrinkable item (its\n       label ellipsizes), so wrapping would only ever push the send button\n       to a second row (real-device report, 2026-08-25). */\n    flex-wrap: nowrap !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  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] {\n    display: contents !important;\n  }\n\n  /* --- 2. the running order ---\n     The attachment button (S3 placeholder, S7 wires it up) sits leftmost and\n     is a PERMANENT resident now (#31): on DSH 0.2.x the standalone paperclip\n     moved into the \"+\" command menu while its hidden <input type=\"file\">\n     stayed in _tools, so the old host-attach stand-down probe matched on\n     every host and the phone composer was left with no attach affordance at\n     all. 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  /* DSH \u2264 0.1.5 still renders that second _add button (the standalone\n     paperclip) as a direct _tools child; hide it below 768px so the row\n     keeps exactly one attach control \u2014 ours, which uploads into the session\n     workspace the phone can actually reach. On 0.2.x the only button in\n     _tools is the first of its type, so this never matches. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > button[class$=\"_add\"]:nth-of-type(2) {\n    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] {\n    order: 3 !important;\n    /* Rigid on purpose. This seat holds the permission chip, whose own\n       wrapper (the plugin's element inside _modes) is `flex: 0 0 auto` and\n       will NOT follow the seat down \u2014 so a shrinkable seat does not make the\n       chip narrower, it just slices the seat out from under a chip that\n       stays 44px wide, and the overflow lands on top of the model pill.\n       Measured 2026-09-04 on DSH 0.1.2 at 390px: seat 90-120 (29.7px) with\n       the chip still 90-134, model starting at 125 \u2014 a 9px overlap, exactly\n       the \"the two chips touch\" report. With the seat rigid: seat 90-134,\n       model 139-246, overlap 0; and at 320px the model pill shrinks to 52px\n       and still nothing overlaps.\n       This also restores what section 1 says out loud \u2014 the model pill is\n       the ONLY shrinkable item in the row. `min-width: 0` is gone with the\n       shrink: it only ever mattered as the companion of `flex: 0 1`. */\n    flex: 0 0 auto !important;\n    gap: 6px !important;\n  }\n  /* The elastic gap used to live here as `margin-right: auto`, which broke\n     the moment a session had no model pill: a subagent session has none, so\n     the gap vanished and the stop / send buttons bunched up in the middle of\n     the row instead of sitting at the right edge (reported 2026-09-06). The\n     gap belongs to the RIGHT group, not to the last item of the left one \u2014\n     see the two rules below the order list. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) {\n    order: 4 !important;\n    /* A definite flex-basis (not auto) breaks the circular sizing between\n       this seat and the trigger's max-width:100%: the seat's width comes\n       from flex resolution, the trigger fills up to it, the label\n       ellipsizes inside. Under nowrap pressure this is the only\n       min-width:0 seat, so it absorbs all shrink. */\n    flex: 0 1 min(48vw, 200px) !important;\n    min-width: 0 !important;\n    max-width: min(48vw, 200px) !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\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.right\"] > * {\n    order: 5 !important;\n  }\n  /* ContextMeter. 0.1.7 moved it out of the row into ROOT's `_dock`, a\n     line UNDER the card \u2014 on the phone that dropped the ring to the very\n     bottom of the screen (user report, 2026-09-28). Lifted back beside send\n     without moving any official node: ROOT becomes a one-cell grid and the\n     dock shares the card's cell, pinned to the card's bottom-right corner,\n     over a placeholder the row reserves in front of send (row::before at\n     order 6, below). Anchoring to the card \u2014 not to ROOT's bottom edge \u2014\n     matters: ROOT's bottom padding follows the safe-area inset, so an\n     absolute `bottom` offset measured in the emulator sat low on a real\n     iPhone (user screenshot, 2026-09-29). Vertical: the row's 8px bottom\n     pad, 34px tall = the send button's box. Horizontal: row pad 8 + send 34\n     + gap 5. The percentage is dropped on the phone (user call): ring only. */\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) {\n    display: grid !important;\n    grid-template-columns: minmax(0, 1fr) !important;\n    justify-items: center !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) > [class$=\"_card\"] {\n    grid-area: 1 / 1 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] > [class$=\"_dock\"] {\n    grid-area: 1 / 1 !important;\n    align-self: end !important;\n    justify-self: end !important;\n    position: relative !important;\n    z-index: 1;\n    height: 34px !important;\n    margin: 0 47px 8px 0 !important;\n    padding: 0 !important;\n    gap: 0 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] > [class$=\"_dock\"] button[class$=\"_trigger\"] {\n    padding: 8px !important;\n    gap: 0 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] > [class$=\"_dock\"] button[class$=\"_trigger\"] > span {\n    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) > [class$=\"_card\"] > [class$=\"_row\"]::before {\n    content: '';\n    order: 6;\n    flex: 0 0 30px;\n    margin-left: auto;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    order: 7 !important;\n  }\n  /* The elastic gap. It sits in front of whichever of the two right-hand\n     items comes first, so the group hugs the right edge no matter what the\n     left side happens to contain \u2014 with a model pill, without one (subagent\n     sessions), with or without the third-party entries at order 5.\n     Send carries `margin-left: auto` on its own; when the lifted ring's\n     placeholder (row::before, above) precedes it, the placeholder carries\n     the auto margin instead and the rule below takes it back off send \u2014\n     two auto margins would SHARE the free space and open a second gap\n     between the ring and send. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    margin-left: auto !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) > [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    margin-left: 0 !important;\n  }\n\n  /* --- 3. permission as icon-only pill; model as name+effort pill ---\n     (real-device round 2, 2026-08-17; model pill reworked 2026-08-25:\n     the user wants to SEE which model/effort is active, so only the\n     permission trigger stays icon-only \u2014 its label is hidden and it\n     collapses to a plain ~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    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] button[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  /* Model trigger: name + effort pill (2026-08-25 user request \u2014 the\n     icon-only form hid which model was active). The effort text must stay\n     whole; the model NAME is the elastic part and ellipsizes. max-width\n     caps the pill so the row's elastic gap survives extreme model ids;\n     the label rules below override the <=1023px grow rules in\n     layout.css.ts (flex 1 1 auto) that would otherwise pad the pill. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_trigger\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > button {\n    background: var(--dsw-specific-selector, rgba(127, 127, 127, .12)) !important;\n    height: 30px !important;\n    width: auto !important;\n    max-width: 100% !important;\n    min-width: 0 !important;\n    padding: 0 10px !important;\n    gap: 4px !important;\n    justify-content: flex-start !important;\n    border-radius: 999px !important;\n    touch-action: manipulation !important;\n    font-size: 12px !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_trigger\"] > [class$=\"_triggerLabel\"] {\n    display: block !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n    white-space: nowrap !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_trigger\"] > [class$=\"_triggerEffort\"] {\n    display: block !important;\n    flex: none !important;\n    white-space: nowrap !important;\n  }\n  /* Third-party model selectors (\u2026codex-ui) render a bare <button> with no\n     _trigger classes and text straight inside it; give that button the same\n     shrink+truncate contract the official label gets, so a long model id\n     ellipsizes instead of stretching the row. The official trigger also\n     matches this (harmless: it already ellipsizes its own label). */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > button {\n    max-width: 100% !important;\n    min-width: 0 !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n    white-space: nowrap !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  /* (2026-08-25) The model trigger's CSS-only Sparkle ::before icon is gone:\n     the pill now shows the model name + effort text itself, so an icon would\n     just eat label width. */\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     under the pill on \u2264 0.1.2; a body portal on 0.1.5+ \u2014 see MODEL_MENU).\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  /* T70: the SAME permission menu, portaled to body on DSH 0.2.0 \u2014 the\n     descendant selector above cannot reach it there. The marker is written\n     by effects/permission-sheet.ts: the trigger's click arms a short window\n     and the first body-level menu to land inside it is ours \u2014 the host has\n     many other portal Menus (preset pickers, preference rows, the sidebar's\n     \u2026, open-in-app, deliverables, \u2026), and none opens through this trigger\n     while no marked menu is up. */\n  body > div[role=\"menu\"][data-zen-sheet=\"perm\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) {\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    /* 60 for the body-portaled menu too: the host gives it 1100 for desktop\n       stacking, but nothing of ours or the host's sits between 60 and the\n       sheet on a phone (hit-tested at four points on 0.1.5-rc.2, 2026-09-21),\n       and 60 keeps it under the session-info sheet's 70 like the PERM one. */\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     The model panes are matched by ROLE too: on DSH 0.2.0 the selected\n     option's class list ends in `_selected` (`\u2026_option \u2026_selected`), so the\n     class-suffix selector missed exactly the checked row \u2014 it fell back to\n     the host's 34px pill while its siblings got 48px. The root cells are\n     role=menuitem, the options role=menuitemradio; the class forms stay for\n     older hosts. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"] [role=\"menuitem\"],\n  body > div[role=\"menu\"][data-zen-sheet=\"perm\"] [role=\"menuitem\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [role=\"menuitem\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [role=\"menuitemradio\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [class$=\"_option\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [class$=\"_cell\"] {\n    min-height: 48px !important;\n    border-radius: 12px !important;\n    font-size: 15px !important;\n  }\n  /* --- 4a. third-party composer entries live in the dock's chip strip ---\n     effects/model-sheet-extras.ts collects the composer's secondary controls\n     (input.right, input.left, and anything a third party parks directly into\n     _tools / _standardControls / _trailing / _row) and moves the REAL nodes\n     into [data-mobile-nav=\"composer-chips\"] \u2014 a 26px horizontally\n     scrollable strip the effect mounts at the head of the dock rail above\n     the card. Always visible, one tap, no sheet in between.\n\n     In the row: hidden, but ONLY once the effect has marked them. Two opt-in\n     markers, both written by the effect: the input.right CONTAINER gets\n     data-zen-sheet-extras (so an emptied wrapper leaves no flex gap), and\n     every collected node gets data-zen-composer-extra. Visibility comes back\n     the moment a node is parked (=\"open\") or the effect releases it (marker\n     removed) \u2014 a version of the effect that declines to act, or never runs\n     at all, leaves every control exactly where the host put it; nothing can\n     end up hidden from both places at once (the 2026-09-06 review's rule). */\n  [data-slot=\"conversation.input.right\"][data-zen-sheet-extras],\n  [data-zen-composer-extra]:not([data-zen-composer-extra=\"open\"]) {\n    display: none !important;\n  }\n  /* The strip itself: one 26px line at the rail's head (order 0, document\n     order first via the effect's prepend), scrolling sideways when the\n     collected controls overflow. Scoped to the dock CHILD \u2014 the generic\n     marker also sits on the emptied input.right container in the row, where\n     nothing but the opt-in hide above may touch it. This specificity (0,2,0)\n     is what beats the section 7 `> *` cage wherever they overlap (overflow,\n     max-width, radius are all !important there too). */\n  [data-slot=\"conversation.input.dock\"] > [data-mobile-nav=\"composer-chips\"] {\n    display: flex !important;\n    flex-flow: row nowrap !important;\n    align-items: center !important;\n    gap: 6px !important;\n    order: 0 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    max-width: 100% !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    border-radius: 0 !important;\n    overflow-x: auto !important;\n    overflow-y: hidden !important;\n    scrollbar-width: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-mobile-nav=\"composer-chips\"]::-webkit-scrollbar {\n    display: none !important;\n  }\n  /* Parked controls shrink from whatever the row allowed them to the rail's\n     26px pill scale: auto width again (no full-width rows here), tight\n     height, and the chip font the rest of the rail uses. */\n  [data-mobile-nav=\"composer-chips\"] > * {\n    flex: 0 0 auto !important;\n    order: 0 !important;\n    display: inline-flex !important;\n    align-items: center !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    width: auto !important;\n    max-width: none !important;\n  }\n  [data-mobile-nav=\"composer-chips\"] button {\n    box-sizing: border-box !important;\n    height: 26px !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    width: auto !important;\n    padding: 0 10px !important;\n    gap: 5px !important;\n    border-radius: 999px !important;\n    font-size: 11.5px !important;\n    line-height: 18px !important;\n    white-space: nowrap !important;\n  }\n  /* The vision toggle is squeezed to a 28px icon-only button in the row\n     (compat.css.ts); in the strip it is a 14px icon + text pill, so its\n     label comes back. */\n  [data-mobile-nav=\"composer-chips\"] [data-vision-router-mode-toggle] > span {\n    display: inline !important;\n  }\n  [data-mobile-nav=\"composer-chips\"] [data-vision-router-mode-toggle] > svg:first-of-type {\n    width: 14px !important;\n    height: 14px !important;\n  }\n  /* The speed chip opens a menu of its own, anchored `bottom: 100%` to its\n     trigger. Inside the strip \u2014 which is `overflow-x: auto`, so its content\n     clips at the strip's box \u2014 that menu would be cut off. Same escape\n     section 4 uses for the host's two menus: position: fixed leaves the clip\n     behind and it lands as its own bottom sheet over the composer. */\n  [class$=\"_composerSeat\"]:has([data-zen-sheet-extras] [role=\"menu\"]) {\n    z-index: 60 !important;\n  }\n  [data-zen-sheet-extras] [role=\"menu\"] {\n    position: fixed !important;\n    left: 0 !important;\n    right: 0 !important;\n    bottom: 0 !important;\n    top: auto !important;\n    margin: 0 !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    /* Above the page content behind the seat (the seat is raised to 60 by\n       the rule above while a parked menu is open), below the session-info\n       sheet's 70 (info.css.ts). */\n    z-index: 61 !important;\n    box-shadow: 0 -8px 32px rgba(0, 0, 0, .18) !important;\n  }\n  [data-zen-sheet-extras] [role=\"menu\"] [role=\"menuitemradio\"] {\n    min-height: 48px !important;\n    border-radius: 12px !important;\n    font-size: 15px !important;\n  }\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\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"]) [data-chat-flow] + div,\n  body:has(> [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [data-chat-flow] + div,\n  /* T70: the portaled permission menu (marked by effects/permission-sheet.ts). */\n  body:has(> div[role=\"menu\"][data-zen-sheet=\"perm\"]) [data-chat-flow] + div,\n  /* T-issue30: an inline menu a parked chip opened (escaped to a fixed\n     sheet by 4a). */\n  body:has([data-zen-sheet-extras] [role=\"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  /* Pull the text in from the card's left border. Upstream insets the editing\n     host by 16px while the control row below it starts 8px in (row padding,\n     section 1), so the placeholder sat noticeably further out than the\n     buttons under it and the field read as over-padded on a phone (reported\n     2026-09-06). 12px squares it with the 12px of clear space on the right,\n     giving the text a symmetric box, and closes most of the gap with the\n     button row. Anchored on the editing host's own contract attribute rather\n     than a hashed class. */\n  [data-slot=\"conversation.composer.bar\"] [data-composer-input] {\n    padding-left: 12px !important;\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    /* The dock is itself a flex ITEM of the composer stack, and the\n       new-session hero pins that stack to a fixed height. overflow-x:auto\n       above makes this a scroll container, which drops a flex item's\n       automatic minimum size to 0 \u2014 so the hero squeezed the dock to ~5px\n       and the attachment chips slid under the card drawn after it (only the\n       top sliver of a thumbnail showed; reported from a real phone,\n       2026-08-26). Refuse the squeeze: natural height, the stack centers a\n       few px lower instead. In-chat the column is not height-pinned and this\n       is a no-op. */\n    flex-shrink: 0 !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    /* A whole line to itself. It shared line 0 with the pills until the goal\n       bar turned up (2026-09-06): two full-width things on one nowrap line\n       meant the to-do header shrank to a stub and the goal bar ran off the\n       right edge. Both are status strips you read at a glance, so they stack\n       \u2014 see the line policy in 7c. */\n    flex: 1 0 100% !important;\n    order: 1 !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: 4 !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  /* --- 7b2. the T34 remote-status banner opts OUT of the cage ---\n     Same class of entry as the to-do card (7a): a full-width status strip,\n     not a pill. dsh-zen-remote's remote banner registers into this dock at\n     order 15 when a remote session is offline or closed (T34) \u2014 the 26px\n     cage would clip the copy to one unreadable sliver. A whole line of its\n     own, natural height. */\n  [data-slot=\"conversation.input.dock\"] > [data-zen-remote=\"remote-banner\"] {\n    flex: 1 0 100% !important;\n    order: 2 !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    font-size: 12px !important;\n    line-height: 18px !important;\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\"], > [data-testid=\"todo-panel\"], > [data-goal-bar]) {\n    flex-wrap: wrap !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] {\n    flex: 1 0 100% !important;\n    order: 3 !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  /* dsh-client-ui-goal's status strip (its own `data-goal-bar` marker; it\n     registers into this dock at order 10). Fourth thing here that is not a\n     pill: a row carrying the objective text plus pause / edit / delete\n     buttons, so the 26px cage clipped its buttons off the right edge and the\n     nowrap line pushed what was left off screen (reported 2026-09-06). Same\n     treatment the queue gets \u2014 a line of its own, official geometry back. */\n  [data-slot=\"conversation.input.dock\"] > [data-goal-bar] {\n    flex: 1 0 100% !important;\n    order: 2 !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    border-radius: 12px !important;\n    overflow: visible !important;\n    font-size: 13px !important;\n    line-height: normal !important;\n  }\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  [data-slot=\"conversation.composer.dock\"] > [data-composer-stat] {\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/* The composer-chips strip (effects/model-sheet-extras.ts) \u2014 same\n   every-width default as the picker above: the phone block re-shows it\n   inside the dock rail; the desktop shell keeps none. */\n[data-mobile-nav=\"composer-chips\"] {\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    /* One line, always: the model pill is the only shrinkable item (its\n       label ellipsizes), so wrapping would only ever push the send button\n       to a second row (real-device report, 2026-08-25). */\n    flex-wrap: nowrap !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  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] {\n    display: contents !important;\n  }\n\n  /* --- 2. the running order ---\n     The attachment button (S3 placeholder, S7 wires it up) sits leftmost and\n     is a PERMANENT resident now (#31): on DSH 0.2.x the standalone paperclip\n     moved into the \"+\" command menu while its hidden <input type=\"file\">\n     stayed in _tools, so the old host-attach stand-down probe matched on\n     every host and the phone composer was left with no attach affordance at\n     all. 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  /* DSH \u2264 0.1.5 still renders that second _add button (the standalone\n     paperclip) as a direct _tools child; hide it below 768px so the row\n     keeps exactly one attach control \u2014 ours, which uploads into the session\n     workspace the phone can actually reach. On 0.2.x the only button in\n     _tools is the first of its type, so this never matches. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > button[class$=\"_add\"]:nth-of-type(2) {\n    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] {\n    order: 3 !important;\n    /* Rigid on purpose. This seat holds the permission chip, whose own\n       wrapper (the plugin's element inside _modes) is `flex: 0 0 auto` and\n       will NOT follow the seat down \u2014 so a shrinkable seat does not make the\n       chip narrower, it just slices the seat out from under a chip that\n       stays 44px wide, and the overflow lands on top of the model pill.\n       Measured 2026-09-04 on DSH 0.1.2 at 390px: seat 90-120 (29.7px) with\n       the chip still 90-134, model starting at 125 \u2014 a 9px overlap, exactly\n       the \"the two chips touch\" report. With the seat rigid: seat 90-134,\n       model 139-246, overlap 0; and at 320px the model pill shrinks to 52px\n       and still nothing overlaps.\n       This also restores what section 1 says out loud \u2014 the model pill is\n       the ONLY shrinkable item in the row. `min-width: 0` is gone with the\n       shrink: it only ever mattered as the companion of `flex: 0 1`. */\n    flex: 0 0 auto !important;\n    gap: 6px !important;\n  }\n  /* The elastic gap used to live here as `margin-right: auto`, which broke\n     the moment a session had no model pill: a subagent session has none, so\n     the gap vanished and the stop / send buttons bunched up in the middle of\n     the row instead of sitting at the right edge (reported 2026-09-06). The\n     gap belongs to the RIGHT group, not to the last item of the left one \u2014\n     see the two rules below the order list. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) {\n    order: 4 !important;\n    /* A definite flex-basis (not auto) breaks the circular sizing between\n       this seat and the trigger's max-width:100%: the seat's width comes\n       from flex resolution, the trigger fills up to it, the label\n       ellipsizes inside. Under nowrap pressure this is the only\n       min-width:0 seat, so it absorbs all shrink. */\n    flex: 0 1 min(48vw, 200px) !important;\n    min-width: 0 !important;\n    max-width: min(48vw, 200px) !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\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.right\"] > * {\n    order: 5 !important;\n  }\n  /* ContextMeter. 0.1.7 moved it out of the row into ROOT's `_dock`, a\n     line UNDER the card \u2014 on the phone that dropped the ring to the very\n     bottom of the screen (user report, 2026-09-28). Lifted back beside send\n     without moving any official node: ROOT becomes a one-cell grid and the\n     dock shares the card's cell, pinned to the card's bottom-right corner,\n     over a placeholder the row reserves in front of send (row::before at\n     order 6, below). Anchoring to the card \u2014 not to ROOT's bottom edge \u2014\n     matters: ROOT's bottom padding follows the safe-area inset, so an\n     absolute `bottom` offset measured in the emulator sat low on a real\n     iPhone (user screenshot, 2026-09-29). Vertical: the row's 8px bottom\n     pad, 34px tall = the send button's box. Horizontal: row pad 8 + send 34\n     + gap 5. The percentage is dropped on the phone (user call): ring only. */\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) {\n    display: grid !important;\n    grid-template-columns: minmax(0, 1fr) !important;\n    justify-items: center !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) > [class$=\"_card\"] {\n    grid-area: 1 / 1 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] > [class$=\"_dock\"] {\n    grid-area: 1 / 1 !important;\n    align-self: end !important;\n    justify-self: end !important;\n    position: relative !important;\n    z-index: 1;\n    height: 34px !important;\n    margin: 0 47px 8px 0 !important;\n    padding: 0 !important;\n    gap: 0 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] > [class$=\"_dock\"] button[class$=\"_trigger\"] {\n    padding: 8px !important;\n    gap: 0 !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"] > [class$=\"_dock\"] button[class$=\"_trigger\"] > span {\n    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) > [class$=\"_card\"] > [class$=\"_row\"]::before {\n    content: '';\n    order: 6;\n    flex: 0 0 30px;\n    margin-left: auto;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    order: 7 !important;\n  }\n  /* The elastic gap. It sits in front of whichever of the two right-hand\n     items comes first, so the group hugs the right edge no matter what the\n     left side happens to contain \u2014 with a model pill, without one (subagent\n     sessions), with or without the third-party entries at order 5.\n     Send carries `margin-left: auto` on its own; when the lifted ring's\n     placeholder (row::before, above) precedes it, the placeholder carries\n     the auto margin instead and the rule below takes it back off send \u2014\n     two auto margins would SHARE the free space and open a second gap\n     between the ring and send. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    margin-left: auto !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] > [class$=\"_root\"]:has(> [class$=\"_dock\"] button) > [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_primary\"] {\n    margin-left: 0 !important;\n  }\n\n  /* --- 3. permission as icon-only pill; model as name+effort pill ---\n     (real-device round 2, 2026-08-17; model pill reworked 2026-08-25:\n     the user wants to SEE which model/effort is active, so only the\n     permission trigger stays icon-only \u2014 its label is hidden and it\n     collapses to a plain ~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    display: none !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] button[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  /* Model trigger: name + effort pill (2026-08-25 user request \u2014 the\n     icon-only form hid which model was active). The effort text must stay\n     whole; the model NAME is the elastic part and ellipsizes. max-width\n     caps the pill so the row's elastic gap survives extreme model ids;\n     the label rules below override the <=1023px grow rules in\n     layout.css.ts (flex 1 1 auto) that would otherwise pad the pill. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_trigger\"],\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > button {\n    background: var(--dsw-specific-selector, rgba(127, 127, 127, .12)) !important;\n    height: 30px !important;\n    width: auto !important;\n    max-width: 100% !important;\n    min-width: 0 !important;\n    padding: 0 10px !important;\n    gap: 4px !important;\n    justify-content: flex-start !important;\n    border-radius: 999px !important;\n    touch-action: manipulation !important;\n    font-size: 12px !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_trigger\"] > [class$=\"_triggerLabel\"] {\n    display: block !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n    white-space: nowrap !important;\n  }\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_trigger\"] > [class$=\"_triggerEffort\"] {\n    display: block !important;\n    flex: none !important;\n    white-space: nowrap !important;\n  }\n  /* Third-party model selectors (\u2026codex-ui) render a bare <button> with no\n     _trigger classes and text straight inside it; give that button the same\n     shrink+truncate contract the official label gets, so a long model id\n     ellipsizes instead of stretching the row. The official trigger also\n     matches this (harmless: it already ellipsizes its own label). */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > button {\n    max-width: 100% !important;\n    min-width: 0 !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n    white-space: nowrap !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  /* (2026-08-25) The model trigger's CSS-only Sparkle ::before icon is gone:\n     the pill now shows the model name + effort text itself, so an icon would\n     just eat label width. */\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     under the pill on \u2264 0.1.2; a body portal on 0.1.5+ \u2014 see MODEL_MENU).\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  /* T70: the SAME permission menu, portaled to body on DSH 0.2.0 \u2014 the\n     descendant selector above cannot reach it there. The marker is written\n     by effects/permission-sheet.ts: the trigger's click arms a short window\n     and the first body-level menu to land inside it is ours \u2014 the host has\n     many other portal Menus (preset pickers, preference rows, the sidebar's\n     \u2026, open-in-app, deliverables, \u2026), and none opens through this trigger\n     while no marked menu is up. */\n  body > div[role=\"menu\"][data-zen-sheet=\"perm\"],\n  /* UX-3: the hero page's workspace menu, marked by the same effect through\n     its own two triggers (the WorkspaceChip and the placeholder card) with\n     the workspace value \u2014 a distinct marker so the pick that starts the\n     workspace switch (effects/permission-sheet.ts) can key on THIS sheet\n     without ever touching permission options. */\n  body > div[role=\"menu\"][data-zen-sheet=\"workspace\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) {\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    /* 60 for the body-portaled menu too: the host gives it 1100 for desktop\n       stacking, but nothing of ours or the host's sits between 60 and the\n       sheet on a phone (hit-tested at four points on 0.1.5-rc.2, 2026-09-21),\n       and 60 keeps it under the session-info sheet's 70 like the PERM one. */\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     The model panes are matched by ROLE too: on DSH 0.2.0 the selected\n     option's class list ends in `_selected` (`\u2026_option \u2026_selected`), so the\n     class-suffix selector missed exactly the checked row \u2014 it fell back to\n     the host's 34px pill while its siblings got 48px. The root cells are\n     role=menuitem, the options role=menuitemradio; the class forms stay for\n     older hosts. */\n  [data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_tools\"] > [class$=\"_modes\"] [role=\"menu\"] [role=\"menuitem\"],\n  body > div[role=\"menu\"][data-zen-sheet=\"perm\"] [role=\"menuitem\"],\n  body > div[role=\"menu\"][data-zen-sheet=\"workspace\"] [role=\"menuitem\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [role=\"menuitem\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [role=\"menuitemradio\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [class$=\"_option\"],\n  :is([data-slot=\"conversation.composer.bar\"] [class$=\"_card\"] > [class$=\"_row\"] > [class$=\"_trailing\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"], body > [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [class$=\"_cell\"] {\n    min-height: 48px !important;\n    border-radius: 12px !important;\n    font-size: 15px !important;\n  }\n  /* --- 4a. third-party composer entries live in the dock's chip strip ---\n     effects/model-sheet-extras.ts collects the composer's secondary controls\n     (input.right, input.left, and anything a third party parks directly into\n     _tools / _standardControls / _trailing / _row) and moves the REAL nodes\n     into [data-mobile-nav=\"composer-chips\"] \u2014 a 26px horizontally\n     scrollable strip the effect mounts at the head of the dock rail above\n     the card. Always visible, one tap, no sheet in between.\n\n     In the row: hidden, but ONLY once the effect has marked them. Two opt-in\n     markers, both written by the effect: the input.right CONTAINER gets\n     data-zen-sheet-extras (so an emptied wrapper leaves no flex gap), and\n     every collected node gets data-zen-composer-extra. Visibility comes back\n     the moment a node is parked (=\"open\") or the effect releases it (marker\n     removed) \u2014 a version of the effect that declines to act, or never runs\n     at all, leaves every control exactly where the host put it; nothing can\n     end up hidden from both places at once (the 2026-09-06 review's rule). */\n  [data-slot=\"conversation.input.right\"][data-zen-sheet-extras],\n  [data-zen-composer-extra]:not([data-zen-composer-extra=\"open\"]) {\n    display: none !important;\n  }\n  /* The strip itself: one 26px line at the rail's head (order 0, document\n     order first via the effect's prepend), scrolling sideways when the\n     collected controls overflow. Scoped to the dock CHILD \u2014 the generic\n     marker also sits on the emptied input.right container in the row, where\n     nothing but the opt-in hide above may touch it. This specificity (0,2,0)\n     is what beats the section 7 `> *` cage wherever they overlap (overflow,\n     max-width, radius are all !important there too). */\n  [data-slot=\"conversation.input.dock\"] > [data-mobile-nav=\"composer-chips\"] {\n    display: flex !important;\n    flex-flow: row nowrap !important;\n    align-items: center !important;\n    gap: 6px !important;\n    order: 0 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    max-width: 100% !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    border-radius: 0 !important;\n    overflow-x: auto !important;\n    overflow-y: hidden !important;\n    scrollbar-width: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-mobile-nav=\"composer-chips\"]::-webkit-scrollbar {\n    display: none !important;\n  }\n  /* Parked controls shrink from whatever the row allowed them to the rail's\n     26px pill scale: auto width again (no full-width rows here), tight\n     height, and the chip font the rest of the rail uses. */\n  [data-mobile-nav=\"composer-chips\"] > * {\n    flex: 0 0 auto !important;\n    order: 0 !important;\n    display: inline-flex !important;\n    align-items: center !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    width: auto !important;\n    max-width: none !important;\n  }\n  [data-mobile-nav=\"composer-chips\"] button {\n    box-sizing: border-box !important;\n    height: 26px !important;\n    min-height: 26px !important;\n    max-height: 26px !important;\n    width: auto !important;\n    padding: 0 10px !important;\n    gap: 5px !important;\n    border-radius: 999px !important;\n    font-size: 11.5px !important;\n    line-height: 18px !important;\n    white-space: nowrap !important;\n  }\n  /* The vision toggle is squeezed to a 28px icon-only button in the row\n     (compat.css.ts); in the strip it is a 14px icon + text pill, so its\n     label comes back. */\n  [data-mobile-nav=\"composer-chips\"] [data-vision-router-mode-toggle] > span {\n    display: inline !important;\n  }\n  [data-mobile-nav=\"composer-chips\"] [data-vision-router-mode-toggle] > svg:first-of-type {\n    width: 14px !important;\n    height: 14px !important;\n  }\n  /* The speed chip opens a menu of its own, anchored `bottom: 100%` to its\n     trigger. Inside the strip \u2014 which is `overflow-x: auto`, so its content\n     clips at the strip's box \u2014 that menu would be cut off. Same escape\n     section 4 uses for the host's two menus: position: fixed leaves the clip\n     behind and it lands as its own bottom sheet over the composer. */\n  [class$=\"_composerSeat\"]:has([data-zen-sheet-extras] [role=\"menu\"]) {\n    z-index: 60 !important;\n  }\n  [data-zen-sheet-extras] [role=\"menu\"] {\n    position: fixed !important;\n    left: 0 !important;\n    right: 0 !important;\n    bottom: 0 !important;\n    top: auto !important;\n    margin: 0 !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    /* Above the page content behind the seat (the seat is raised to 60 by\n       the rule above while a parked menu is open), below the session-info\n       sheet's 70 (info.css.ts). */\n    z-index: 61 !important;\n    box-shadow: 0 -8px 32px rgba(0, 0, 0, .18) !important;\n  }\n  [data-zen-sheet-extras] [role=\"menu\"] [role=\"menuitemradio\"] {\n    min-height: 48px !important;\n    border-radius: 12px !important;\n    font-size: 15px !important;\n  }\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\"] > [class$=\"_standardControls\"] > [data-slot=\"conversation.input.model\"] > *:not([data-mobile-nav]) > [class$=\"_menu\"]) [data-chat-flow] + div,\n  body:has(> [id$=\"-menu\"][class$=\"_menu\"]:is([role=\"menu\"], [role=\"group\"])) [data-chat-flow] + div,\n  /* T70: the portaled permission menu (marked by effects/permission-sheet.ts). */\n  body:has(> div[role=\"menu\"][data-zen-sheet=\"perm\"]) [data-chat-flow] + div,\n  /* UX-3: the portaled hero workspace menu, same treatment. */\n  body:has(> div[role=\"menu\"][data-zen-sheet=\"workspace\"]) [data-chat-flow] + div,\n  /* T-issue30: an inline menu a parked chip opened (escaped to a fixed\n     sheet by 4a). */\n  body:has([data-zen-sheet-extras] [role=\"menu\"]) [data-chat-flow] + div {\n    display: none !important;\n  }\n  /* --- 4c. UX-3: the workspace switch lock ---\n     Between picking a workspace in the hero sheet and the new blank session\n     landing (selectWorkspace \u2192 POST /api/session/create \u2192 replaceMain\n     remounts the conversation), the composer still belongs to the OLD blank\n     session: a message sent in that window lands there and is then wiped by\n     the remount, bouncing the UI back to the \"choose a workspace\" state.\n     effects/permission-sheet.ts stamps data-zen-ws-switching on <html> for\n     exactly that window \u2014 the lock releases when the conversation root's\n     data-conversation-session has moved and the placeholder card is gone,\n     with a 1.5 s cap \u2014 and the dim (not just pointer-events) makes the\n     freeze visible instead of reading as a dead input. */\n  html[data-zen-ws-switching] [data-slot=\"conversation.composer.bar\"] {\n    pointer-events: none !important;\n    opacity: .6 !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  /* Pull the text in from the card's left border. Upstream insets the editing\n     host by 16px while the control row below it starts 8px in (row padding,\n     section 1), so the placeholder sat noticeably further out than the\n     buttons under it and the field read as over-padded on a phone (reported\n     2026-09-06). 12px squares it with the 12px of clear space on the right,\n     giving the text a symmetric box, and closes most of the gap with the\n     button row. Anchored on the editing host's own contract attribute rather\n     than a hashed class. */\n  [data-slot=\"conversation.composer.bar\"] [data-composer-input] {\n    padding-left: 12px !important;\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    /* The dock is itself a flex ITEM of the composer stack, and the\n       new-session hero pins that stack to a fixed height. overflow-x:auto\n       above makes this a scroll container, which drops a flex item's\n       automatic minimum size to 0 \u2014 so the hero squeezed the dock to ~5px\n       and the attachment chips slid under the card drawn after it (only the\n       top sliver of a thumbnail showed; reported from a real phone,\n       2026-08-26). Refuse the squeeze: natural height, the stack centers a\n       few px lower instead. In-chat the column is not height-pinned and this\n       is a no-op. */\n    flex-shrink: 0 !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    /* A whole line to itself. It shared line 0 with the pills until the goal\n       bar turned up (2026-09-06): two full-width things on one nowrap line\n       meant the to-do header shrank to a stub and the goal bar ran off the\n       right edge. Both are status strips you read at a glance, so they stack\n       \u2014 see the line policy in 7c. */\n    flex: 1 0 100% !important;\n    order: 1 !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: 4 !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  /* --- 7b2. the T34 remote-status banner opts OUT of the cage ---\n     Same class of entry as the to-do card (7a): a full-width status strip,\n     not a pill. dsh-zen-remote's remote banner registers into this dock at\n     order 15 when a remote session is offline or closed (T34) \u2014 the 26px\n     cage would clip the copy to one unreadable sliver. A whole line of its\n     own, natural height. */\n  [data-slot=\"conversation.input.dock\"] > [data-zen-remote=\"remote-banner\"] {\n    flex: 1 0 100% !important;\n    order: 2 !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    font-size: 12px !important;\n    line-height: 18px !important;\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\"], > [data-testid=\"todo-panel\"], > [data-goal-bar]) {\n    flex-wrap: wrap !important;\n  }\n  [data-slot=\"conversation.input.dock\"] > [data-queue-dock] {\n    flex: 1 0 100% !important;\n    order: 3 !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  /* dsh-client-ui-goal's status strip (its own `data-goal-bar` marker; it\n     registers into this dock at order 10). Fourth thing here that is not a\n     pill: a row carrying the objective text plus pause / edit / delete\n     buttons, so the 26px cage clipped its buttons off the right edge and the\n     nowrap line pushed what was left off screen (reported 2026-09-06). Same\n     treatment the queue gets \u2014 a line of its own, official geometry back. */\n  [data-slot=\"conversation.input.dock\"] > [data-goal-bar] {\n    flex: 1 0 100% !important;\n    order: 2 !important;\n    max-width: none !important;\n    min-height: 0 !important;\n    max-height: none !important;\n    border-radius: 12px !important;\n    overflow: visible !important;\n    font-size: 13px !important;\n    line-height: normal !important;\n  }\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  [data-slot=\"conversation.composer.dock\"] > [data-composer-stat] {\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":"AAoEA,eAAO,MAAM,YAAY,yrhDA25BxB,CAAA"}
+{"version":3,"file":"composer.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/composer.css.ts"],"names":[],"mappings":"AAoEA,eAAO,MAAM,YAAY,uwkDAm7BxB,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    /* 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    border-bottom: none !important;\n  }\n  /* No header bottom line \u2014 fade instead (real-device round 2, 2026-08-17).\n     The official header in rc.2 drew its border as a `::after` 1px bar; in\n     rc.3 (2026-10-25) the host replaced that pseudo-element with a plain 0.5px\n     border-bottom (cleared above) and added a blank 0px header in the hero\n     phase (`_headerBlank`). Declaring `content: ''` + `position: absolute;\n     left: 0; right: 0` explicitly on `[data-phase=\"active\"] header:not([class$=\"_headerBlank\"])::after`\n     keeps the 20px fade strip anchored right below the real session header on\n     both rc.2 and rc.3 without touching the scroll container:\n     - When the session header is display:none on the list page, ::after is\n       not generated at all (unlike _scrollBody::before, which stayed in flow\n       at y=0 whenever the header was hidden or blank and showed up at the top\n       of the window on iOS standalone PWA launch before data-view mutated).\n     - :not([class$=\"_headerBlank\"]) excludes the 0-height blank header.\n     - color-mix instead of the transparent keyword: plain `transparent` is\n       rgba(0,0,0,0) \u2014 WebKit interpolates it through grey. */\n  [data-phase=\"active\"] header:not([class$=\"_headerBlank\"])::after {\n    content: '';\n    position: absolute;\n    left: 0;\n    right: 0;\n    top: 100% !important;\n    bottom: auto !important;\n    height: 20px !important;\n    pointer-events: none;\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  [data-mobile-nav=\"frame\"]:not([data-mobile-view=\"session\"]) [data-phase] header::after,\n  body:has([data-mobile-nav=\"home\"]:not([data-view=\"session\"])) [data-phase] header::after {\n    content: none !important;\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  /* DSH 0.1.5's third titleRow child: the right sidebar's ExpandButton\n     (dsh-client-ui-sidebar-right, slot conversation.session.header.corner\n     inside div.headerCorner). Left alone it auto-placed into an implicit\n     4th grid column at the screen's top-right corner \u2014 a second panel-left\n     icon next to our Workbench button, reading as \"the hidden official\n     sidebar toggle is back\" (reported 2026-09-11). The button itself is the\n     one our sidebar control forwards to whenever the host has this panel\n     (sidebar-panels.ts, official first since 2026-09-21 \u2014 better-sidebar\n     0.19+ puts all its tabs in here), and a display:none button still\n     receives synthetic .click() (the tablist precedent), so hiding it costs\n     nothing. better-sidebar 0.19's own bottom-workbench toggle\n     (`[data-dsh-bottom-toggle]`) registers into the utilities slot and is\n     caught by the blanket hide above \u2014 intended: that surface is not for\n     the phone.\n     Anchors, in the specificity order they NEED (measured live, 2026-09-11):\n     the corner div must be beaten with (0,3,1) \u2014 the utilities un-hide rule\n     above spells header > :first-child > :last-child at exactly that\n     weight, and with 0.1.5's third titleRow child the corner IS that\n     :last-child now, so its flex !important outranks any lighter hide (a\n     single-attribute hide loses at (0,2,1) \u2014 both spellings were tried\n     live). Chaining BOTH of the corner's own anchors on one selector \u2014 the\n     host's data-conversation-header-corner contract attribute AND the\n     class suffix \u2014 reaches the tie, and the later source order here wins\n     it. The slot wrapper rule below needs no help: nothing !important\n     fights it, so its (0,2,1) settles the button. */\n  [data-phase] header [data-conversation-header-corner][class$=\"_headerCorner\"],\n  [data-phase] header [data-slot=\"conversation.session.header.corner\"] {\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 renders the official\n     IconInfoOutlineRegular since DSH 0.1.7) and the workbench button's\n     IconPanelLeftOutlineRegular is mirrored into a panel-RIGHT glyph \u2014\n     there's no panel-RIGHT glyph in primitives (re-checked against the\n     0.1.7-rc.2 exports), and the plugin's own right-side panel semantics\n     are exactly the left icon flipped. Both buttons carry a same-size\n     (16px) 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  /* DSH 0.2.1-rc.3 split the row: div._tabs (no role) now wraps the\n     tablist (div._viewTabs[role=tablist][data-conversation-tabs]) and the\n     new \"More conversation views\" launcher, so the rule above matches\n     nothing there and the official row \u2014 plus a stray (\u2026) More button \u2014\n     came back under our view-switch band. It cannot simply be display:none\n     either: while the More menu has registrations the header folds every\n     View past floor((row.clientWidth - 48) / 120) into More, and a\n     display:none row measures 0, which would leave only Chat as a\n     [role=tab] for readViewTabs() (MobileSessionHeader.tsx) to mirror.\n     So the row keeps a wide layout box that paints nothing: absolute (out\n     of the header's flow, no band), 2048px wide (room for 16 tabs before\n     anything folds), scale(0) so it adds no scrollable overflow (clientWidth\n     ignores transforms), visibility:hidden + pointer-events:none so it is\n     never seen or hit. Its tabs still take the synthetic .click() the view\n     switcher sends \u2014 the same reasoning as the display:none rule above. */\n  [data-phase] header [class$=\"_tabs\"]:has(> [data-conversation-tabs]) {\n    position: absolute !important;\n    top: 0;\n    left: 0;\n    width: 2048px !important;\n    max-width: none !important;\n    height: 0 !important;\n    margin: 0 !important;\n    overflow: hidden !important;\n    transform: scale(0);\n    transform-origin: 0 0;\n    visibility: hidden !important;\n    pointer-events: none !important;\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    border-bottom: none !important;\n  }\n  /* No header bottom line \u2014 fade instead (real-device round 2, 2026-08-17).\n     The official header in rc.2 drew its border as a `::after` 1px bar; in\n     rc.3 (2026-10-25) the host replaced that pseudo-element with a plain 0.5px\n     border-bottom (cleared above) and added a blank 0px header in the hero\n     phase (`_headerBlank`). Declaring `content: ''` + `position: absolute;\n     left: 0; right: 0` explicitly on `[data-phase=\"active\"] header:not([class$=\"_headerBlank\"])::after`\n     keeps the 20px fade strip anchored right below the real session header on\n     both rc.2 and rc.3 without touching the scroll container:\n     - When the session header is display:none on the list page, ::after is\n       not generated at all (unlike _scrollBody::before, which stayed in flow\n       at y=0 whenever the header was hidden or blank and showed up at the top\n       of the window on iOS standalone PWA launch before data-view mutated).\n     - :not([class$=\"_headerBlank\"]) excludes the 0-height blank header.\n     - color-mix instead of the transparent keyword: plain `transparent` is\n       rgba(0,0,0,0) \u2014 WebKit interpolates it through grey. */\n  [data-phase=\"active\"] header:not([class$=\"_headerBlank\"])::after {\n    content: '';\n    position: absolute;\n    left: 0;\n    right: 0;\n    top: 100% !important;\n    bottom: auto !important;\n    height: 20px !important;\n    pointer-events: none;\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  [data-mobile-nav=\"frame\"]:not([data-mobile-view=\"session\"]) [data-phase] header::after,\n  body:has([data-mobile-nav=\"home\"]:not([data-view=\"session\"])) [data-phase] header::after {\n    content: none !important;\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    /* UX-2 (2026-11-04): the host gives this row container-type: inline-size,\n       which implies layout containment \u2014 making the row the containing block\n       for every descendant position:fixed. That shifted every viewport\n       coordinate effects/native-trigger-overlay.ts writes by the safe-area\n       top and the row's horizontal padding. normal hands fixed descendants\n       back to the viewport; the phone block owns this layout, so nothing\n       scoped container queries against the row here. */\n    container-type: normal !important;\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 hide every ancestor crumb (UX-2, 2026-11-04 \u2014\n     supersedes the 2026-08-18 \"keep ONE ancestor\" rule). DSH 0.2.1 turned\n     the parent crumb into a session-TREE popup trigger\n     (\u2026_switcherTrigger[aria-haspopup=\"tree\"]) instead of a direct\n     switch-back tap, and that popup is desktop geometry on the phone; the\n     back button and the home stack stay the way back. Main sessions render\n     a single span with no segs at all, so :not(:last-child) never matches\n     there. */\n  [data-phase] header [class$=\"_crumbSeg\"]:not(:last-child) {\n    display: none !important;\n  }\n  /* With the parent seg gone, the current seg's own leading \"/\" would\n     dangle before the title; the dissolved trigger container's stray\n     separator is covered by this same rule (its slot rules below hide it\n     too). One blanket rule instead of per-segment cases. */\n  [data-phase] header [class$=\"_crumbSep\"] {\n    display: none !important;\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  /* 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  /* DSH 0.1.5's third titleRow child: the right sidebar's ExpandButton\n     (dsh-client-ui-sidebar-right, slot conversation.session.header.corner\n     inside div.headerCorner). Left alone it auto-placed into an implicit\n     4th grid column at the screen's top-right corner \u2014 a second panel-left\n     icon next to our Workbench button, reading as \"the hidden official\n     sidebar toggle is back\" (reported 2026-09-11). The button itself is the\n     one our sidebar control forwards to whenever the host has this panel\n     (sidebar-panels.ts, official first since 2026-09-21 \u2014 better-sidebar\n     0.19+ puts all its tabs in here), and a display:none button still\n     receives synthetic .click() (the tablist precedent), so hiding it costs\n     nothing. better-sidebar 0.19's own bottom-workbench toggle\n     (`[data-dsh-bottom-toggle]`) registers into the utilities slot and is\n     caught by the blanket hide above \u2014 intended: that surface is not for\n     the phone.\n     Anchors, in the specificity order they NEED (measured live, 2026-09-11):\n     the corner div must be beaten with (0,3,1) \u2014 the utilities un-hide rule\n     above spells header > :first-child > :last-child at exactly that\n     weight, and with 0.1.5's third titleRow child the corner IS that\n     :last-child now, so its flex !important outranks any lighter hide (a\n     single-attribute hide loses at (0,2,1) \u2014 both spellings were tried\n     live). Chaining BOTH of the corner's own anchors on one selector \u2014 the\n     host's data-conversation-header-corner contract attribute AND the\n     class suffix \u2014 reaches the tie, and the later source order here wins\n     it. The slot wrapper rule below needs no help: nothing !important\n     fights it, so its (0,2,1) settles the button. */\n  [data-phase] header [data-conversation-header-corner][class$=\"_headerCorner\"],\n  [data-phase] header [data-slot=\"conversation.session.header.corner\"] {\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 the resting dissolve: the root's box (and its stray\n     separator, hidden below) stops occupying the breadcrumb until the\n     overlay pins it. The measurement chore moved to the overlay (UX-2,\n     2026-11-04): the 0.1.1+ popover portals to <body> as position:fixed\n     and sizes itself from the OUTER anchor container (the official\n     rootRef, the trigger's parent div) \u2014 a display:contents root has no\n     box, so rootRef.getBoundingClientRect() was all zeros and the panel\n     landed at 12,12 inside the status bar. effects/\n     native-trigger-overlay.ts now pins container + trigger to the pill's\n     rect together (its inline display beats this rule's !important, style\n     attribute outranks selectors at author-important). */\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 popovers themselves portal to <body> as position:fixed layers\n     (class suffix _menu, z-index 100) and place themselves from the pill's\n     viewport rect with margin 12 \u2014 the overlay above is what makes that\n     rect correct. This is only a floor: the panels' 336px width overflows\n     320px-class phones, and a tall list must not run under the notch or\n     the home indicator. [id$=\"-menu\"] keeps the composer's model menu out\n     of it \u2014 composer.css.ts owns that surface, and this file sits before\n     it in styles/index.ts so its own rules still win the tie. */\n  body > [class$=\"_menu\"]:not([id$=\"-menu\"]) {\n    max-width: calc(100vw - 24px) !important;\n    max-height: calc(100dvh - env(safe-area-inset-top, 0px) - env(safe-area-inset-bottom, 0px) - 24px) !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     order: -1 keeps it to the left of @deepseek-ai/dsh-experimental-client-ui-agent-team's\n     TeamAction ([data-team-action], registered into header.actions at order -20 with\n     default flex order 0). */\n  [data-mobile-nav=\"header-back\"] {\n    order: -1;\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  /* TeamAction's own stylesheet hides .XdyUwa_triggerLabel via\n     @container (width<=480px) against _titleRow's container-type: inline-size.\n     Shedding container-type on _titleRow above (UX-2) disabled that container\n     query, so hide the label explicitly on phone and keep only the icon. */\n  [data-phase] header [data-team-action] [class$=\"_triggerLabel\"] {\n    display: none !important;\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 renders the official\n     IconInfoOutlineRegular since DSH 0.1.7) and the workbench button's\n     IconPanelLeftOutlineRegular is mirrored into a panel-RIGHT glyph \u2014\n     there's no panel-RIGHT glyph in primitives (re-checked against the\n     0.1.7-rc.2 exports), and the plugin's own right-side panel semantics\n     are exactly the left icon flipped. Both buttons carry a same-size\n     (16px) 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  /* DSH 0.2.1-rc.3 split the row: div._tabs (no role) now wraps the\n     tablist (div._viewTabs[role=tablist][data-conversation-tabs]) and the\n     new \"More conversation views\" launcher, so the rule above matches\n     nothing there and the official row \u2014 plus a stray (\u2026) More button \u2014\n     came back under our view-switch band. It cannot simply be display:none\n     either: while the More menu has registrations the header folds every\n     View past floor((row.clientWidth - 48) / 120) into More, and a\n     display:none row measures 0, which would leave only Chat as a\n     [role=tab] for readViewTabs() (MobileSessionHeader.tsx) to mirror.\n     So the row keeps a wide layout box that paints nothing: absolute (out\n     of the header's flow, no band), 2048px wide (room for 16 tabs before\n     anything folds), scale(0) so it adds no scrollable overflow (clientWidth\n     ignores transforms), visibility:hidden + pointer-events:none so it is\n     never seen or hit. Its tabs still take the synthetic .click() the view\n     switcher sends \u2014 the same reasoning as the display:none rule above. */\n  [data-phase] header [class$=\"_tabs\"]:has(> [data-conversation-tabs]) {\n    position: absolute !important;\n    top: 0;\n    left: 0;\n    width: 2048px !important;\n    max-width: none !important;\n    height: 0 !important;\n    margin: 0 !important;\n    overflow: hidden !important;\n    transform: scale(0);\n    transform-origin: 0 0;\n    visibility: hidden !important;\n    pointer-events: none !important;\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    pointer-events: none;\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":"AA6BA,eAAO,MAAM,UAAU,+s3BA0kBtB,CAAA"}
+{"version":3,"file":"header.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/header.css.ts"],"names":[],"mappings":"AA6BA,eAAO,MAAM,UAAU,wz5BAslBtB,CAAA"}

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

@@ -1,2 +1,2 @@
-export declare const LAYOUT_CSS = "/* ---------- mobile-only layout ---------- */\n\n@media (max-width: 1023px) {\n  /* --- Phone chrome ---\n     The system status bar stays visible (no fullscreen). Two adjustments\n     make it behave:\n     - touch-action: manipulation kills double-tap-to-zoom (and the 300ms\n       tap delay) while keeping pan and pinch zoom; the client also\n       suppresses legacy-iOS gesturestart as a fallback.\n     - With the client's viewport-fit=cover, env(safe-area-inset-top) is the\n       status bar / notch height; the rules below push the app content below\n       it so the status bar never covers anything. Off notched phones (or in\n       a normal browser tab where the layout viewport already sits below the\n       status bar) the inset is 0 and nothing shifts. */\n  html,\n  body {\n    touch-action: manipulation !important;\n  }\n\n  /* AppFrame: the drawer takes the sidebar column out of grid flow, so the\n     remaining in-flow items (center, details) land in tracks 1..2: give the\n     center every pixel and keep the details track at zero. The top padding\n     clears the status bar / notch for every in-flow surface (session header,\n     messages, composer); the absolutely-positioned drawer is unaffected (its\n     containing block is the frame's padding box, i.e. still the frame top). */\n  /* box-sizing: border-box is load-bearing (S2.1, 2026-08-17). The official\n     frame carries height: 100% with the default content-box, so the\n     safe-area padding ADDED 54px to its height instead of taking 54px out\n     of the content area: the frame grew past the viewport, the document\n     became scrollable by exactly the inset, and the very first scroll put\n     the header right back under the notch \u2014 measured with\n     ?mobile-nav-inset=54 (frame 898px tall inside an 844px root, html at\n     y=-54). Invisible on every desktop browser because the inset is 0\n     there, which is how it shipped. */\n  [data-mobile-nav=\"frame\"] {\n    position: relative !important;\n    box-sizing: border-box !important;\n    grid-template-columns: minmax(0, 1fr) 0 0 !important;\n    padding-top: var(--mnav-sat) !important;\n  }\n\n  /* The sidebar column (first grid child) becomes a left drawer. The drawer\n     hugs the sidebar content exactly (the wide sidebar carries an inline\n     width, ~280px): a fixed 92vw box would leave a white strip where the\n     container background shows beside the content.\n     Closed state: translateX(-110%) \u2014 more than -100% of the max-content\n     width \u2014 guarantees the whole drawer (and its shadow, had it one) leaves\n     the viewport. A mere -100% leaves a sliver on screen; -105% (as used\n     before) left 14px of the drawer plus a long 32px-blur shadow gradient\n     visible along the left edge of the main UI. No box-shadow at all: the\n     dimmed backdrop already separates drawer from content. */\n  [data-mobile-nav=\"frame\"] > :first-child {\n    position: absolute !important;\n    inset: 0 auto 0 0 !important;\n    width: max-content !important;\n    max-width: 92vw !important;\n    z-index: 40 !important;\n    transform: translateX(-110%);\n    transition: transform .28s var(--ds-ease-in-out, ease-in-out);\n    background: var(--dsw-alias-bg-base, #ffffff);\n    /* Keep the drawer's own content below the status bar / notch: the drawer\n       spans the full frame height (its absolute containing block is the\n       frame's padding box, so the frame's own safe-area padding does NOT\n       reach it). The drawer background paints the status-bar strip, which\n       the client's theme-color meta matches, so the strip reads seamless. */\n    padding-top: var(--mnav-sat) !important;\n    /* Kill the official sidebarCol right border: with the backdrop the edge\n       reads cleanly, and the settings dialog (width:100% of this box) stays\n       pixel-flush with the drawer. */\n    border-right: none !important;\n  }\n\n  /* The official right sidebar (DSH 0.1.5+) in its full-screen mode \u2014 the\n     one the phone's header sidebar button opens (sidebar-panels.ts). The\n     host promotes the panel to position:fixed; inset:0 there, so exactly\n     like the drawer above it escapes the frame's safe-area padding and its\n     tab strip + chrome buttons landed under the status bar (real-device\n     report, 2026-09-21). Both insets: the status bar / notch on top, the\n     home indicator at the bottom. Padding, no box-sizing change: fixed\n     with both top and bottom set resolves its used height from the\n     containing block minus padding (CSS 2.1 10.6.4), so the content box\n     shrinks by itself \u2014 the same reasoning the legacy better-sidebar panel\n     rule in compat.css.ts spells out. `fullscreen` is the host's own\n     attribute value (`push` while docked, dsh-client-ui-sidebar-right), so\n     the docked panel is untouched; a manual full-screen on desktop is\n     outside this media block anyway. Verify with ?mobile-nav-inset=54,34 \u2014\n     env() is 0 in every desktop browser. */\n  [data-sidebar-right-panel=\"fullscreen\"] {\n    padding-top: var(--mnav-sat) !important;\n    padding-bottom: var(--mnav-sab) !important;\n  }\n\n  /* Expanded state (frame without data-sidebar-collapsed) slides the drawer in.\n     The open state must be transform:none \u2014 NOT translateX(0): an identity\n     transform still makes the drawer the containing block for fixed-position\n     descendants (the settings dialog's .VOzbGW_overlay is portaled into the\n     sidebar DOM). With the identity transform the wide settings sheet\n     (100vw-16) overflows the 280px drawer, the dialog's focus scrolls the\n     overflow:hidden drawer to scrollLeft=102, and every static child (plus the\n     fixed overlay) shifts 102px off-screen. With transform:none the overlay is\n     viewport-anchored: it dims the full screen and the sheet sits at left:8. */\n  [data-mobile-nav=\"frame\"]:not([data-sidebar-collapsed]) > :first-child {\n    transform: none !important;\n  }\n\n  /* Drag handles are useless on touch and would float over the drawer. */\n  [data-side=\"sidebar\"],\n  [data-side=\"details\"] {\n    display: none !important;\n  }\n\n  /* --- Conversation text on mobile ---\n     The official message flow keeps desktop's 32px side gutters and 16px\n     type. On a phone: shrink the type a notch and widen the lines by\n     trimming the gutters (the sidebar drawer list keeps its size). The\n     flow's scroll container is the only _scroll element holding markdown\n     <p> paragraphs \u2014 the composer's own scroll (textarea) is excluded\n     via :has(p). */\n  /* The official main scroll body reserves scrollbar-gutter for desktop\n     scrollbars (8px), which shoves every column off-center on a phone.\n     Classic desktop scrollbars (Edge/Chrome) also occupy ~8-17px in a\n     phone-sized viewport, shifting the column further. Mobile scrolling\n     is touch/wheel, so remove the scrollbar entirely on phones: the\n     column is then exactly centered in every browser. */\n  [data-phase] [class$=\"_scrollBody\"] {\n    scrollbar-gutter: auto !important;\n    scrollbar-width: none !important;\n  }\n  [data-phase] [class$=\"_scrollBody\"]::-webkit-scrollbar {\n    display: none !important;\n    width: 0 !important;\n    height: 0 !important;\n  }\n  /* Message action rows (copy / run-time badges) can overflow the right\n     edge on narrow screens \u2014 keep them inside the message width. */\n  [data-phase] [class$=\"_actions\"] {\n    overflow: hidden !important;\n  }\n  /* The 24h clock (\"18:06\" / \"MM-DD 18:06\") is a fixed-size item: it must\n     never be the thing that shrinks. DSH 0.2.x wraps it with the usage\n     button in an inline-flex _endInfo (min-width: 0), so a shrinkable\n     time (the old flex: 0 1 auto + min-width: 0) got squeezed inside that\n     non-wrapping box and \"18:06\" broke into two lines. flex: none pins its\n     width; the turn-tail rules in content.css.ts let _endInfo wrap as a\n     whole instead. */\n  [data-phase] [class$=\"_actions\"] [class$=\"_timeEnd\"] {\n    flex: none !important;\n    white-space: nowrap !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n  }\n\n  [data-phase] [class$=\"_scroll\"]:has(p) {\n    padding-left: 20px !important;\n    padding-right: 20px !important;\n    font-size: 15px !important;\n  }\n  /* The official markdown styles set an explicit 16px on paragraphs and\n     list items, so the container's inherited 15px is not enough. User\n     messages render their text in a div whose class carries _text_\n     (16px too) \u2014 cover it as well. */\n  [data-phase] [class$=\"_scroll\"]:has(p) p,\n  [data-phase] [class$=\"_scroll\"]:has(p) li,\n  [data-phase] [class$=\"_scroll\"]:has(p) [class*=\"_text_\"] {\n    font-size: 15px !important;\n  }\n\n  /* Markdown tables: the official table uses width:max-content, so on a phone\n     it hugs the content and leaves dead space beside/inside the table. Force\n     the table to fill the message column and let the table wrapper handle\n     overflow if a cell is genuinely too wide. */\n  [data-phase] table {\n    width: 100% !important;\n    max-width: 100% !important;\n  }\n  [data-phase] th,\n  [data-phase] td {\n    max-width: none !important;\n    min-width: 0 !important;\n  }\n\n  /* User bubbles: the official stack is capped at min(525px, 82%), which on a\n     phone leaves a large blank strip on the left and pushes the bubble high.\n     On mobile let the user message fill the same full width as assistant\n     messages (the bubble background then spans the whole message column). */\n  [data-phase] [class$=\"_userStack\"],\n  [data-phase] [class$=\"_userStack\"] [class$=\"_bubble\"] {\n    box-sizing: border-box !important;\n    width: fit-content !important;\n    max-width: 100% !important;\n  }\n\n  /* --- Composer bottom row on mobile ---\n     The official row gives the model pill (trailing) flex:0 0 auto, which\n     squeezes the agent-permission pill (modes) down to 15px: the pill's\n     chevron then overflows on top of the model name. Let the permission\n     pill keep its natural width and let the model pill shrink instead.\n     Anchored by the composer card (:has(textarea)): row = the _row class\n     containing a _trailing group, tools = its first child, permission pill\n     = its 2nd child, model pill = the _trailing group.\n     NOTE: do NOT anchor these by the card's :last-child \u2014 a client effect\n     moves the git-graph branch chip INTO the card, which becomes the card's\n     new last child and silently disables every :last-child rule (the model\n     pill then falls back to the official fixed layout and long model IDs\n     overflow instead of ellipsizing). Structural anchors only. */\n  /* The official row pads every group with 12px gaps, which on a phone eats\n     width the model pill needs for the full model ID. Tighten the row to 8px\n     gaps (the modes pill keeps its natural width) so the model name gets\n     every spare pixel. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_row\"]:has([class$=\"_trailing\"]) {\n    gap: 8px !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_row\"]:has([class$=\"_trailing\"]) > :first-child {\n    gap: 8px !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_row\"]:has([class$=\"_trailing\"]) > :first-child > :nth-child(2) {\n    flex: 0 0 auto !important;\n    gap: 8px !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_trailing\"] {\n    flex: 1 1 auto !important;\n    gap: 8px !important;\n    min-width: 0 !important;\n  }\n  /* Let the model selector take the free space in the trailing group so the\n     model name is not squeezed/truncated; the context meter stays fixed. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"][aria-haspopup=\"menu\"]) {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"][aria-haspopup=\"menu\"]) > [class$=\"_trigger\"] {\n    width: 100% !important;\n    max-width: 100% !important;\n  }\n  /* The model label must absorb the trigger's free width: officially it is a\n     fixed-content flex item, so the spare width of a grown pill sits unused\n     between the chevron and the pill edge. Let the label grow and shrink:\n     the full model ID shows whenever the row can fit it, and the ellipsis\n     lands exactly at the available width otherwise. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"][aria-haspopup=\"menu\"]) > [class$=\"_trigger\"] > [class$=\"_triggerLabel\"] {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"]:not([aria-haspopup=\"menu\"])) {\n    flex: 0 0 auto !important;\n  }\n\n  /* Model switcher menu: the official dropdown is right-aligned to the\n     trigger (right:0). The model pill sits near the center of the composer,\n     so on a phone the 240px menu overflows the left edge and looks off-center.\n     Center the menu on the trigger instead. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"]) > [class$=\"_menu\"] {\n    left: 50% !important;\n    right: auto !important;\n    transform: translateX(-50%) !important;\n  }\n\n  /* --- Session header on mobile ---\n     Layout goal: [toggle] [session title] [mode badge] in a row, with the\n     Session log capsule removed from the header (relocated to the drawer\n     footer). Stable structural hooks only:\n       [data-phase] header                     the session header element\n       header > :first-child                   titleRow (titleCluster + utilities)\n       header > :first-child > :last-child     headerUtilities (Session log seat) */\n  [data-phase] header {\n    padding-right: 12px !important;\n  }\n  /* Give the title row a lane clear of the absolutely-placed toggle, then\n     balance the header: with header padding-right 12px, a 20px left\n     padding puts the title's geometric center exactly on the viewport\n     center (measured 195/195 at 390px). */\n  [data-phase] header > :first-child {\n    padding-left: 20px !important;\n  }\n  /* The directory toggle sits at the far left of the header (the header\n     is position:relative; the data-slot wrappers are display:contents). */\n  [data-mobile-nav=\"toggle\"] {\n    position: absolute !important;\n    left: 8px !important;\n    top: 12px !important;\n    z-index: 2 !important;\n  }\n  /* The Files action stays in-flow inside headerActions. On mobile headerActions\n     does not expand to fill the row: it is pushed to the right edge and keeps\n     its content size, so [mode] [subagent/jobs] [files] sit close together\n     with the normal 8px gaps \u2014 compact, no artificial blank columns. Explicit\n     flex order keeps Files rightmost regardless of DOM order. */\n  [data-mobile-nav=\"files\"] {\n    position: static !important;\n    left: auto !important;\n    right: auto !important;\n    top: auto !important;\n    z-index: auto !important;\n  }\n  [data-phase] header [class$=\"_headerActions\"] {\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    margin-left: auto !important;\n    justify-content: flex-end !important;\n  }\n  /* The session title/crumb must yield space on mobile so the mode label and\n     subagent cluster are not squeezed to a single letter. Cap it at ~24vw and\n     let it truncate with ellipsis. */\n  [data-phase] header [class$=\"_crumbs\"] {\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    max-width: 24vw !important;\n  }\n  /* Mode label (AgentPresetLabel): the official pill uses inline-flex, whose\n     direct text node is only clipped \u2014 no ellipsis. Convert the pill to a\n     block container, keep its icon absolutely positioned on the left, and let\n     it size naturally up to 42vw so the mode name stays readable while the\n     subagent/Files cluster still fits on a phone. */\n  [data-phase] header [class$=\"_label\"]:has(> svg) {\n    order: 1 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    max-width: 42vw !important;\n    display: block !important;\n    position: relative !important;\n    box-sizing: border-box !important;\n    padding-left: 18px !important;\n    padding-right: 2px !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n    white-space: nowrap !important;\n  }\n  [data-phase] header [class$=\"_label\"]:has(> svg) > svg {\n    position: absolute !important;\n    left: 0 !important;\n    top: 50% !important;\n    transform: translateY(-50%) !important;\n  }\n  /* Subagent/jobs helpers: keep their triggers on one line and never let the\n     row grow artificial empty space. */\n  [data-phase] header [class$=\"_root\"]:has(> button[class$=\"_trigger\"]) {\n    order: 2 !important;\n    flex: 0 0 auto !important;\n    min-width: max-content !important;\n    max-width: none !important;\n    white-space: nowrap !important;\n    /* On mobile the popover is anchored to the header (viewport-width\n       containing block) instead of the trigger, so a small left inset keeps it\n       fully on screen and never clips the tree's status dots. */\n    position: static !important;\n  }\n  [data-phase] header [class$=\"_root\"]:has(> button[class$=\"_trigger\"]) > button,\n  [data-phase] header [class$=\"_root\"]:has(> button[class$=\"_trigger\"]) > button * {\n    white-space: nowrap !important;\n  }\n  [data-phase] header [data-mobile-nav=\"files\"] {\n    order: 3 !important;\n    flex: 0 0 auto !important;\n  }\n  /* Session log download: gone from the header row on mobile (the utilities\n     seat holds only the session-log-export capsule). */\n  [data-phase] header > :first-child > :last-child {\n    display: none !important;\n  }\n\n  /* --- Header popovers on mobile (dsh-client-ui-jobs / dsh-client-ui-subagent) ---\n     The official entries sit in the session header actions. Their popovers\n     are anchored to the trigger's LEFT edge (left: 0), so from a right-edge\n     trigger the 336px panel spills past the viewport. Re-anchor them to the\n     trigger's right edge instead. The popover classes are hashed CSS-module\n     names, so target them by the stable _menu suffix inside the header. */\n  /* Header popovers on mobile: anchor to the left edge with a small inset and\n     clamp the width, instead of right-aligning to a trigger near the right\n     edge (which pushed the panel left off-screen and clipped the status dots).\n     Also cap the height so the panel does not run into the composer/task bar. */\n  [data-phase] header [class$=\"_menu\"] {\n    left: 8px !important;\n    right: auto !important;\n    width: min(336px, calc(100vw - 16px)) !important;\n    max-width: none !important;\n    max-height: min(420px, calc(100dvh - 120px)) !important;\n  }\n  /* --- Settings dialog on mobile ---\n     Desktop: 800px two-column flex (188px nav + content). Mobile: a\n     near-full-width sheet \u2014 nav tabs wrap into rows on top, option rows\n     stay horizontal (title+description left, control right). Structural\n     selectors are scoped to the unique aria-modal dialog; every\n     settings-specific rule is gated with\n     :has(> :first-child > :last-child > button) \u2014 the settings nav tab\n     list holds <button> tabs, so the transient export dialog (the same\n     primitives Modal, header(title+close)+description+body) keeps its\n     official centered card layout. Requires :has() support\n     (Chromium 105+, 2022).\n\n     The directory picker (dsh-client-ui-directory-picker-browse) must be\n     excluded too: its footer bar holds <button> children AND its breadcrumb\n     trail (role=\"navigation\") \u2014 which the role gate relies on to exclude\n     it \u2014 is REPLACED by the path input in edit mode (pencil button), so\n     without the ZuhsRW exclusion clicking the pencil would suddenly match\n     this sheet rule: the dialog jumps to the top of the screen, the header\n     (with the path input) is hidden by the > :first-child > :first-child\n     display:none rule below, and the user can no longer type a path\n     (issue #12, 2026-08-16). The picker family keeps the official layout\n     on mobile in every mode. */\n  /* DSH 0.2.1-rc.2 renders this dialog as a body PORTAL\n     (body > overlay > panel), so the placement below must key off the nav\n     list the panel owns, not off a guessed child depth: that is both the\n     stable \"this is the settings sheet\" anchor and the reason the safe-area\n     offset below still applies inside the portal (the constants live on\n     :root, so they cross the portal boundary). The bottom inset is\n     subtracted too \u2014 a tall panel must not run under the home indicator. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])):has([class$=\"_navList\"]) {\n    position: absolute !important;\n    left: 8px !important;\n    /* Fixed top (no translateY): a transform on the panel combined with the\n       panel overflowing the max-content drawer shifts the fixed overlay's\n       coordinate frame, dragging the whole sidebar content off-screen. The\n       safe-area inset keeps the sheet below the status bar / notch. */\n    top: calc(var(--mnav-sat) + 12px) !important;\n    width: calc(100vw - 16px) !important;\n    max-width: calc(100vw - 16px) !important;\n    /* Height follows the content (no dead space under a short page); it\n       caps at 100dvh-24 (less both safe-area insets) and the options area\n       scrolls only then. */\n    height: auto !important;\n    max-height: min(800px, calc(100vh - 24px - var(--mnav-sat) - var(--mnav-sab))) !important;\n    max-height: min(800px, calc(100dvh - 24px - var(--mnav-sat) - var(--mnav-sab))) !important;\n    flex-direction: column !important;\n    border-radius: 14px !important;\n    animation: dsh-mobile-nav-sheet-in .22s var(--ds-ease-out, ease-in-out);\n  }\n  /* The settings sheet's dimmed mask fades in with the panel (the mask is\n     the first child of the overlay that directly contains the sheet). */\n  :has(> [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"]))) > :first-child {\n    animation: dsh-mobile-nav-fade .18s var(--ds-ease-out, ease-in-out);\n  }\n  @media (prefers-reduced-motion: reduce) {\n    [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])),\n    :has(> [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"]))) > :first-child {\n      animation: none !important;\n    }\n  }\n  /* The export dialog (not the settings sheet) must never overflow the\n     viewport: the official centered card can be wider than 390px.\n     :not([data-mobile-nav=\"info-sheet\"]) (S4, 2026-08-17): the session-info\n     sheet also carries role=\"dialog\" aria-modal=\"true\" (correct a11y\n     semantics for a bottom sheet with a scrim) and has no button as its\n     first-child's last-child, so without this exclusion it silently matched\n     this generic selector too \u2014 measured 358px (100vw-32px) instead of the\n     374px its own left:8px/right:8px margins specify. Same category of bug\n     as the ZuhsRW directory-picker collision below; same fix shape.\n     :not([data-mobile-nav=\"share-range-sheet\"]) (share-image, 2026-09-10):\n     the share range picker rides the same role=\"dialog\" aria-modal bottom\n     -sheet shape and the same margins, so it hit the identical clamp. */\n  [aria-modal=\"true\"]:not(:has(> :first-child > :last-child > button)):not([data-mobile-nav=\"info-sheet\"]):not([data-mobile-nav=\"share-range-sheet\"]) {\n    max-width: calc(100vw - 32px) !important;\n  }\n  /* Nav bar: hide the \"Settings\" caption (redundant on a full-width sheet)\n     and wrap the tab list so every tab is visible \u2014 a horizontal scroll cut\n     the last tab (\"Plugins\") off with no affordance to scroll. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :first-child {\n    width: 100% !important;\n    flex-direction: row !important;\n    align-items: center !important;\n    gap: 6px !important;\n    padding: 10px 12px 8px !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :first-child > :first-child {\n    display: none !important;\n  }\n  /* The tab list scrolls in the space left by the toolbar: the toolbar\n     (config file + close) is reparented INTO this nav row by a client\n     effect (MobileNavOverlay), so the tab list must be anchored by its\n     class, NOT by :last-child (the reparented toolbar becomes the nav's\n     new last child).\n\n     2026-10-21 (DSH 0.2.1-rc.2): this rule used to declare\n     \"flex-wrap: wrap; overflow: visible\" on top of the flex/min-width/gap\n     above. Because it is one class-anchored compound selector with a much\n     higher specificity than compat.css.ts's portal-scoped navList rule, it\n     silently won the tie and the tab list wrapped into two rows \u2014 with the\n     reparented \u2715 vertically centred across both of them. Measured on a\n     phone shell: the list was 86px tall (two rows) instead of one 40px row,\n     and it scrolled nowhere. The wrap was a 2026-08-16 trade-off (show every\n     tab, no hidden scroll cut-off); with the thin scrollbar affordance now\n     in compat.css.ts the single scrolling row is the better trade, so the\n     two declarations live there and this rule no longer contradicts them. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :first-child [class$=\"_navList\"] {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n    flex-direction: row !important;\n    gap: 6px !important;\n  }\n  /* Content toolbar (Open configuration file + close): grouped flush to\n     the right edge, and reparented INTO the nav row on mobile so it shares\n     one line with the tabs (user feedback 2026-08-16 \u2014 the toolbar's own\n     row left a full-width dead gap under the tabs). Anchored by class: the\n     header leaves the content subtree, so :first-child/:last-child anchors\n     would now hit the options area. Children carry official auto-margins\n     that would defeat flex-end, so neutralize them. The close button gets\n     a round tappable base so it reads as its own control, not part of the\n     outline button. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) [class$=\"_header\"] {\n    flex: 0 0 auto !important;\n    justify-content: flex-end !important;\n    align-items: center !important;\n    gap: 8px !important;\n    padding: 0 0 0 4px !important;\n    min-height: 40px !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) [class$=\"_header\"] > * {\n    margin-left: 0 !important;\n    margin-right: 0 !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) [class$=\"_header\"] > :last-child {\n    width: 32px !important;\n    height: 32px !important;\n    border-radius: 50% !important;\n    display: inline-flex !important;\n    align-items: center !important;\n    justify-content: center !important;\n    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06)) !important;\n  }\n  /* Appearance mode cards: the official cube row renders three tall\n     vertical cards (~268px) that eat half the sheet. Turn them into a\n     compact horizontal trio (icon + label inline, equal widths).\n     Relies on the official cube-row class name of this version. */\n  [aria-modal=\"true\"] [class$=\"_cubeRow\"] {\n    gap: 6px !important;\n  }\n  [aria-modal=\"true\"] [class$=\"_cubeRow\"] > * {\n    flex: 1 1 0 !important;\n    flex-direction: row !important;\n    align-items: center !important;\n    justify-content: center !important;\n    gap: 6px !important;\n    padding: 10px 8px !important;\n    min-height: 0 !important;\n  }\n  /* Content: the options scroll area gets bottom breathing room so the last\n     row never sits flush against the sheet's rounded corner. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :last-child {\n    flex: 1 1 auto !important;\n    min-height: 0 !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :last-child > :last-child {\n    padding: 0 12px 24px !important;\n  }\n";
+export declare const LAYOUT_CSS = "/* ---------- mobile-only layout ---------- */\n\n@media (max-width: 1023px) {\n  /* --- Phone chrome ---\n     The system status bar stays visible (no fullscreen). Two adjustments\n     make it behave:\n     - touch-action: manipulation kills double-tap-to-zoom (and the 300ms\n       tap delay) while keeping pan and pinch zoom; the client also\n       suppresses legacy-iOS gesturestart as a fallback.\n     - With the client's viewport-fit=cover, env(safe-area-inset-top) is the\n       status bar / notch height; the rules below push the app content below\n       it so the status bar never covers anything. Off notched phones (or in\n       a normal browser tab where the layout viewport already sits below the\n       status bar) the inset is 0 and nothing shifts. */\n  html,\n  body {\n    touch-action: manipulation !important;\n  }\n\n  /* AppFrame: the drawer takes the sidebar column out of grid flow, so the\n     remaining in-flow items (center, details) land in tracks 1..2: give the\n     center every pixel and keep the details track at zero. The top padding\n     clears the status bar / notch for every in-flow surface (session header,\n     messages, composer); the absolutely-positioned drawer is unaffected (its\n     containing block is the frame's padding box, i.e. still the frame top). */\n  /* box-sizing: border-box is load-bearing (S2.1, 2026-08-17). The official\n     frame carries height: 100% with the default content-box, so the\n     safe-area padding ADDED 54px to its height instead of taking 54px out\n     of the content area: the frame grew past the viewport, the document\n     became scrollable by exactly the inset, and the very first scroll put\n     the header right back under the notch \u2014 measured with\n     ?mobile-nav-inset=54 (frame 898px tall inside an 844px root, html at\n     y=-54). Invisible on every desktop browser because the inset is 0\n     there, which is how it shipped. */\n  [data-mobile-nav=\"frame\"] {\n    position: relative !important;\n    box-sizing: border-box !important;\n    grid-template-columns: minmax(0, 1fr) 0 0 !important;\n    padding-top: var(--mnav-sat) !important;\n  }\n\n  /* The sidebar column (first grid child) becomes a left drawer. The drawer\n     hugs the sidebar content exactly (the wide sidebar carries an inline\n     width, ~280px): a fixed 92vw box would leave a white strip where the\n     container background shows beside the content.\n     Closed state: translateX(-110%) \u2014 more than -100% of the max-content\n     width \u2014 guarantees the whole drawer (and its shadow, had it one) leaves\n     the viewport. A mere -100% leaves a sliver on screen; -105% (as used\n     before) left 14px of the drawer plus a long 32px-blur shadow gradient\n     visible along the left edge of the main UI. No box-shadow at all: the\n     dimmed backdrop already separates drawer from content. */\n  [data-mobile-nav=\"frame\"] > :first-child {\n    position: absolute !important;\n    inset: 0 auto 0 0 !important;\n    width: max-content !important;\n    max-width: 92vw !important;\n    z-index: 40 !important;\n    transform: translateX(-110%);\n    transition: transform .28s var(--ds-ease-in-out, ease-in-out);\n    background: var(--dsw-alias-bg-base, #ffffff);\n    /* Keep the drawer's own content below the status bar / notch: the drawer\n       spans the full frame height (its absolute containing block is the\n       frame's padding box, so the frame's own safe-area padding does NOT\n       reach it). The drawer background paints the status-bar strip, which\n       the client's theme-color meta matches, so the strip reads seamless. */\n    padding-top: var(--mnav-sat) !important;\n    /* Kill the official sidebarCol right border: with the backdrop the edge\n       reads cleanly, and the settings dialog (width:100% of this box) stays\n       pixel-flush with the drawer. */\n    border-right: none !important;\n  }\n\n  /* The official right sidebar (DSH 0.1.5+) in its full-screen mode \u2014 the\n     one the phone's header sidebar button opens (sidebar-panels.ts). The\n     host promotes the panel to position:fixed; inset:0 there, so exactly\n     like the drawer above it escapes the frame's safe-area padding and its\n     tab strip + chrome buttons landed under the status bar (real-device\n     report, 2026-09-21). Both insets: the status bar / notch on top, the\n     home indicator at the bottom. Padding, no box-sizing change: fixed\n     with both top and bottom set resolves its used height from the\n     containing block minus padding (CSS 2.1 10.6.4), so the content box\n     shrinks by itself \u2014 the same reasoning the legacy better-sidebar panel\n     rule in compat.css.ts spells out. `fullscreen` is the host's own\n     attribute value (`push` while docked, dsh-client-ui-sidebar-right), so\n     the docked panel is untouched; a manual full-screen on desktop is\n     outside this media block anyway. Verify with ?mobile-nav-inset=54,34 \u2014\n     env() is 0 in every desktop browser. */\n  [data-sidebar-right-panel=\"fullscreen\"] {\n    padding-top: var(--mnav-sat) !important;\n    padding-bottom: var(--mnav-sab) !important;\n  }\n  /* Right sidebar start/guide page (dsh-client-ui-sidebar-right GuideBody):\n     the host sets .Dv5QdW_tabBody { height: 100%; overflow: hidden } and\n     .F6Huca_guide { min-height: 100%; justify-content: center } with no\n     overflow-y. When many tab entries are registered (e.g. better-sidebar +\n     plugins), the centered flex column overflows equally out the top and\n     bottom of the locked 100%-height box \u2014 clipping the leading entries\n     (\"\u6587\u4EF6\", \"Git\") above y=0 with no way to scroll. Make the guide itself\n     the scroll container and replace justify-content:center with auto\n     margins on the first item and ::after so short lists stay centered\n     while long lists start cleanly at the top and scroll end-to-end. */\n  [data-sidebar-right-guide] {\n    flex: 1 1 0 !important;\n    min-height: 0 !important;\n    justify-content: flex-start !important;\n    overflow-y: auto !important;\n    -webkit-overflow-scrolling: touch;\n    padding-top: 24px !important;\n    padding-bottom: 24px !important;\n  }\n  [data-sidebar-right-guide] > :first-child {\n    margin-top: auto !important;\n  }\n  [data-sidebar-right-guide]::after {\n    margin-bottom: auto !important;\n  }\n\n  /* Expanded state (frame without data-sidebar-collapsed) slides the drawer in.\n     The open state must be transform:none \u2014 NOT translateX(0): an identity\n     transform still makes the drawer the containing block for fixed-position\n     descendants (the settings dialog's .VOzbGW_overlay is portaled into the\n     sidebar DOM). With the identity transform the wide settings sheet\n     (100vw-16) overflows the 280px drawer, the dialog's focus scrolls the\n     overflow:hidden drawer to scrollLeft=102, and every static child (plus the\n     fixed overlay) shifts 102px off-screen. With transform:none the overlay is\n     viewport-anchored: it dims the full screen and the sheet sits at left:8. */\n  [data-mobile-nav=\"frame\"]:not([data-sidebar-collapsed]) > :first-child {\n    transform: none !important;\n  }\n\n  /* Drag handles are useless on touch and would float over the drawer. */\n  [data-side=\"sidebar\"],\n  [data-side=\"details\"] {\n    display: none !important;\n  }\n\n  /* --- Conversation text on mobile ---\n     The official message flow keeps desktop's 32px side gutters and 16px\n     type. On a phone: shrink the type a notch and widen the lines by\n     trimming the gutters (the sidebar drawer list keeps its size). The\n     flow's scroll container is the only _scroll element holding markdown\n     <p> paragraphs \u2014 the composer's own scroll (textarea) is excluded\n     via :has(p). */\n  /* The official main scroll body reserves scrollbar-gutter for desktop\n     scrollbars (8px), which shoves every column off-center on a phone.\n     Classic desktop scrollbars (Edge/Chrome) also occupy ~8-17px in a\n     phone-sized viewport, shifting the column further. Mobile scrolling\n     is touch/wheel, so remove the scrollbar entirely on phones: the\n     column is then exactly centered in every browser. */\n  [data-phase] [class$=\"_scrollBody\"] {\n    scrollbar-gutter: auto !important;\n    scrollbar-width: none !important;\n  }\n  [data-phase] [class$=\"_scrollBody\"]::-webkit-scrollbar {\n    display: none !important;\n    width: 0 !important;\n    height: 0 !important;\n  }\n  /* Message action rows (copy / run-time badges) can overflow the right\n     edge on narrow screens \u2014 keep them inside the message width. */\n  [data-phase] [class$=\"_actions\"] {\n    overflow: hidden !important;\n  }\n  /* The 24h clock (\"18:06\" / \"MM-DD 18:06\") is a fixed-size item: it must\n     never be the thing that shrinks. DSH 0.2.x wraps it with the usage\n     button in an inline-flex _endInfo (min-width: 0), so a shrinkable\n     time (the old flex: 0 1 auto + min-width: 0) got squeezed inside that\n     non-wrapping box and \"18:06\" broke into two lines. flex: none pins its\n     width; the turn-tail rules in content.css.ts let _endInfo wrap as a\n     whole instead. */\n  [data-phase] [class$=\"_actions\"] [class$=\"_timeEnd\"] {\n    flex: none !important;\n    white-space: nowrap !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n  }\n\n  [data-phase] [class$=\"_scroll\"]:has(p) {\n    padding-left: 20px !important;\n    padding-right: 20px !important;\n    font-size: 15px !important;\n  }\n  /* The official markdown styles set an explicit 16px on paragraphs and\n     list items, so the container's inherited 15px is not enough. User\n     messages render their text in a div whose class carries _text_\n     (16px too) \u2014 cover it as well. */\n  [data-phase] [class$=\"_scroll\"]:has(p) p,\n  [data-phase] [class$=\"_scroll\"]:has(p) li,\n  [data-phase] [class$=\"_scroll\"]:has(p) [class*=\"_text_\"] {\n    font-size: 15px !important;\n  }\n\n  /* Markdown tables: the official table uses width:max-content, so on a phone\n     it hugs the content and leaves dead space beside/inside the table. Force\n     the table to fill the message column and let the table wrapper handle\n     overflow if a cell is genuinely too wide. */\n  [data-phase] table {\n    width: 100% !important;\n    max-width: 100% !important;\n  }\n  [data-phase] th,\n  [data-phase] td {\n    max-width: none !important;\n    min-width: 0 !important;\n  }\n\n  /* User bubbles: the official stack is capped at min(525px, 82%), which on a\n     phone leaves a large blank strip on the left and pushes the bubble high.\n     On mobile let the user message fill the same full width as assistant\n     messages (the bubble background then spans the whole message column). */\n  [data-phase] [class$=\"_userStack\"],\n  [data-phase] [class$=\"_userStack\"] [class$=\"_bubble\"] {\n    box-sizing: border-box !important;\n    width: fit-content !important;\n    max-width: 100% !important;\n  }\n\n  /* --- Composer bottom row on mobile ---\n     The official row gives the model pill (trailing) flex:0 0 auto, which\n     squeezes the agent-permission pill (modes) down to 15px: the pill's\n     chevron then overflows on top of the model name. Let the permission\n     pill keep its natural width and let the model pill shrink instead.\n     Anchored by the composer card (:has(textarea)): row = the _row class\n     containing a _trailing group, tools = its first child, permission pill\n     = its 2nd child, model pill = the _trailing group.\n     NOTE: do NOT anchor these by the card's :last-child \u2014 a client effect\n     moves the git-graph branch chip INTO the card, which becomes the card's\n     new last child and silently disables every :last-child rule (the model\n     pill then falls back to the official fixed layout and long model IDs\n     overflow instead of ellipsizing). Structural anchors only. */\n  /* The official row pads every group with 12px gaps, which on a phone eats\n     width the model pill needs for the full model ID. Tighten the row to 8px\n     gaps (the modes pill keeps its natural width) so the model name gets\n     every spare pixel. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_row\"]:has([class$=\"_trailing\"]) {\n    gap: 8px !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_row\"]:has([class$=\"_trailing\"]) > :first-child {\n    gap: 8px !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_row\"]:has([class$=\"_trailing\"]) > :first-child > :nth-child(2) {\n    flex: 0 0 auto !important;\n    gap: 8px !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_trailing\"] {\n    flex: 1 1 auto !important;\n    gap: 8px !important;\n    min-width: 0 !important;\n  }\n  /* Let the model selector take the free space in the trailing group so the\n     model name is not squeezed/truncated; the context meter stays fixed. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"][aria-haspopup=\"menu\"]) {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"][aria-haspopup=\"menu\"]) > [class$=\"_trigger\"] {\n    width: 100% !important;\n    max-width: 100% !important;\n  }\n  /* The model label must absorb the trigger's free width: officially it is a\n     fixed-content flex item, so the spare width of a grown pill sits unused\n     between the chevron and the pill edge. Let the label grow and shrink:\n     the full model ID shows whenever the row can fit it, and the ellipsis\n     lands exactly at the available width otherwise. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"][aria-haspopup=\"menu\"]) > [class$=\"_trigger\"] > [class$=\"_triggerLabel\"] {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n  }\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"]:not([aria-haspopup=\"menu\"])) {\n    flex: 0 0 auto !important;\n  }\n\n  /* Model switcher menu: the official dropdown is right-aligned to the\n     trigger (right:0). The model pill sits near the center of the composer,\n     so on a phone the 240px menu overflows the left edge and looks off-center.\n     Center the menu on the trigger instead. */\n  [data-phase] [class*=\"_card\"]:has(textarea) [class$=\"_root\"]:has(> [class$=\"_trigger\"]) > [class$=\"_menu\"] {\n    left: 50% !important;\n    right: auto !important;\n    transform: translateX(-50%) !important;\n  }\n\n  /* --- Session header on mobile ---\n     Layout goal: [toggle] [session title] [mode badge] in a row, with the\n     Session log capsule removed from the header (relocated to the drawer\n     footer). Stable structural hooks only:\n       [data-phase] header                     the session header element\n       header > :first-child                   titleRow (titleCluster + utilities)\n       header > :first-child > :last-child     headerUtilities (Session log seat) */\n  [data-phase] header {\n    padding-right: 12px !important;\n  }\n  /* Give the title row a lane clear of the absolutely-placed toggle, then\n     balance the header: with header padding-right 12px, a 20px left\n     padding puts the title's geometric center exactly on the viewport\n     center (measured 195/195 at 390px). */\n  [data-phase] header > :first-child {\n    padding-left: 20px !important;\n  }\n  /* The directory toggle sits at the far left of the header (the header\n     is position:relative; the data-slot wrappers are display:contents). */\n  [data-mobile-nav=\"toggle\"] {\n    position: absolute !important;\n    left: 8px !important;\n    top: 12px !important;\n    z-index: 2 !important;\n  }\n  /* The Files action stays in-flow inside headerActions. On mobile headerActions\n     does not expand to fill the row: it is pushed to the right edge and keeps\n     its content size, so [mode] [subagent/jobs] [files] sit close together\n     with the normal 8px gaps \u2014 compact, no artificial blank columns. Explicit\n     flex order keeps Files rightmost regardless of DOM order. */\n  [data-mobile-nav=\"files\"] {\n    position: static !important;\n    left: auto !important;\n    right: auto !important;\n    top: auto !important;\n    z-index: auto !important;\n  }\n  [data-phase] header [class$=\"_headerActions\"] {\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    margin-left: auto !important;\n    justify-content: flex-end !important;\n  }\n  /* The session title/crumb must yield space on mobile so the mode label and\n     subagent cluster are not squeezed to a single letter. Cap it at ~24vw and\n     let it truncate with ellipsis. */\n  [data-phase] header [class$=\"_crumbs\"] {\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    max-width: 24vw !important;\n  }\n  /* Mode label (AgentPresetLabel): the official pill uses inline-flex, whose\n     direct text node is only clipped \u2014 no ellipsis. Convert the pill to a\n     block container, keep its icon absolutely positioned on the left, and let\n     it size naturally up to 42vw so the mode name stays readable while the\n     subagent/Files cluster still fits on a phone. */\n  [data-phase] header [class$=\"_label\"]:has(> svg) {\n    order: 1 !important;\n    flex: 0 1 auto !important;\n    min-width: 0 !important;\n    max-width: 42vw !important;\n    display: block !important;\n    position: relative !important;\n    box-sizing: border-box !important;\n    padding-left: 18px !important;\n    padding-right: 2px !important;\n    overflow: hidden !important;\n    text-overflow: ellipsis !important;\n    white-space: nowrap !important;\n  }\n  [data-phase] header [class$=\"_label\"]:has(> svg) > svg {\n    position: absolute !important;\n    left: 0 !important;\n    top: 50% !important;\n    transform: translateY(-50%) !important;\n  }\n  /* Subagent/jobs helpers: keep their triggers on one line and never let the\n     row grow artificial empty space. */\n  [data-phase] header [class$=\"_root\"]:has(> button[class$=\"_trigger\"]) {\n    order: 2 !important;\n    flex: 0 0 auto !important;\n    min-width: max-content !important;\n    max-width: none !important;\n    white-space: nowrap !important;\n    /* On mobile the popover is anchored to the header (viewport-width\n       containing block) instead of the trigger, so a small left inset keeps it\n       fully on screen and never clips the tree's status dots. */\n    position: static !important;\n  }\n  [data-phase] header [class$=\"_root\"]:has(> button[class$=\"_trigger\"]) > button,\n  [data-phase] header [class$=\"_root\"]:has(> button[class$=\"_trigger\"]) > button * {\n    white-space: nowrap !important;\n  }\n  [data-phase] header [data-mobile-nav=\"files\"] {\n    order: 3 !important;\n    flex: 0 0 auto !important;\n  }\n  /* Session log download: gone from the header row on mobile (the utilities\n     seat holds only the session-log-export capsule). */\n  [data-phase] header > :first-child > :last-child {\n    display: none !important;\n  }\n\n  /* --- Header popovers on mobile (dsh-client-ui-jobs / dsh-client-ui-subagent) ---\n     The official entries sit in the session header actions. Their popovers\n     are anchored to the trigger's LEFT edge (left: 0), so from a right-edge\n     trigger the 336px panel spills past the viewport. Re-anchor them to the\n     trigger's right edge instead. The popover classes are hashed CSS-module\n     names, so target them by the stable _menu suffix inside the header. */\n  /* Header popovers on mobile: anchor to the left edge with a small inset and\n     clamp the width, instead of right-aligning to a trigger near the right\n     edge (which pushed the panel left off-screen and clipped the status dots).\n     Also cap the height so the panel does not run into the composer/task bar. */\n  [data-phase] header [class$=\"_menu\"] {\n    left: 8px !important;\n    right: auto !important;\n    width: min(336px, calc(100vw - 16px)) !important;\n    max-width: none !important;\n    max-height: min(420px, calc(100dvh - 120px)) !important;\n  }\n  /* --- Settings dialog on mobile ---\n     Desktop: 800px two-column flex (188px nav + content). Mobile: a\n     near-full-width sheet \u2014 nav tabs wrap into rows on top, option rows\n     stay horizontal (title+description left, control right). Structural\n     selectors are scoped to the unique aria-modal dialog; every\n     settings-specific rule is gated with\n     :has(> :first-child > :last-child > button) \u2014 the settings nav tab\n     list holds <button> tabs, so the transient export dialog (the same\n     primitives Modal, header(title+close)+description+body) keeps its\n     official centered card layout. Requires :has() support\n     (Chromium 105+, 2022).\n\n     The directory picker (dsh-client-ui-directory-picker-browse) must be\n     excluded too: its footer bar holds <button> children AND its breadcrumb\n     trail (role=\"navigation\") \u2014 which the role gate relies on to exclude\n     it \u2014 is REPLACED by the path input in edit mode (pencil button), so\n     without the ZuhsRW exclusion clicking the pencil would suddenly match\n     this sheet rule: the dialog jumps to the top of the screen, the header\n     (with the path input) is hidden by the > :first-child > :first-child\n     display:none rule below, and the user can no longer type a path\n     (issue #12, 2026-08-16). The picker family keeps the official layout\n     on mobile in every mode. */\n  /* DSH 0.2.1-rc.2 renders this dialog as a body PORTAL\n     (body > overlay > panel), so the placement below must key off the nav\n     list the panel owns, not off a guessed child depth: that is both the\n     stable \"this is the settings sheet\" anchor and the reason the safe-area\n     offset below still applies inside the portal (the constants live on\n     :root, so they cross the portal boundary). The bottom inset is\n     subtracted too \u2014 a tall panel must not run under the home indicator. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])):has([class$=\"_navList\"]) {\n    position: absolute !important;\n    left: 8px !important;\n    /* Fixed top (no translateY): a transform on the panel combined with the\n       panel overflowing the max-content drawer shifts the fixed overlay's\n       coordinate frame, dragging the whole sidebar content off-screen. The\n       safe-area inset keeps the sheet below the status bar / notch. */\n    top: calc(var(--mnav-sat) + 12px) !important;\n    width: calc(100vw - 16px) !important;\n    max-width: calc(100vw - 16px) !important;\n    /* Height follows the content (no dead space under a short page); it\n       caps at 100dvh-24 (less both safe-area insets) and the options area\n       scrolls only then. */\n    height: auto !important;\n    max-height: min(800px, calc(100vh - 24px - var(--mnav-sat) - var(--mnav-sab))) !important;\n    max-height: min(800px, calc(100dvh - 24px - var(--mnav-sat) - var(--mnav-sab))) !important;\n    flex-direction: column !important;\n    border-radius: 14px !important;\n    animation: dsh-mobile-nav-sheet-in .22s var(--ds-ease-out, ease-in-out);\n  }\n  /* The settings sheet's dimmed mask fades in with the panel (the mask is\n     the first child of the overlay that directly contains the sheet). */\n  :has(> [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"]))) > :first-child {\n    animation: dsh-mobile-nav-fade .18s var(--ds-ease-out, ease-in-out);\n  }\n  @media (prefers-reduced-motion: reduce) {\n    [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])),\n    :has(> [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"]))) > :first-child {\n      animation: none !important;\n    }\n  }\n  /* The export dialog (not the settings sheet) must never overflow the\n     viewport: the official centered card can be wider than 390px.\n     :not([data-mobile-nav=\"info-sheet\"]) (S4, 2026-08-17): the session-info\n     sheet also carries role=\"dialog\" aria-modal=\"true\" (correct a11y\n     semantics for a bottom sheet with a scrim) and has no button as its\n     first-child's last-child, so without this exclusion it silently matched\n     this generic selector too \u2014 measured 358px (100vw-32px) instead of the\n     374px its own left:8px/right:8px margins specify. Same category of bug\n     as the ZuhsRW directory-picker collision below; same fix shape.\n     :not([data-mobile-nav=\"share-range-sheet\"]) (share-image, 2026-09-10):\n     the share range picker rides the same role=\"dialog\" aria-modal bottom\n     -sheet shape and the same margins, so it hit the identical clamp. */\n  [aria-modal=\"true\"]:not(:has(> :first-child > :last-child > button)):not([data-mobile-nav=\"info-sheet\"]):not([data-mobile-nav=\"share-range-sheet\"]) {\n    max-width: calc(100vw - 32px) !important;\n  }\n  /* Nav bar: hide the \"Settings\" caption (redundant on a full-width sheet)\n     and wrap the tab list so every tab is visible \u2014 a horizontal scroll cut\n     the last tab (\"Plugins\") off with no affordance to scroll. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :first-child {\n    width: 100% !important;\n    flex-direction: row !important;\n    align-items: center !important;\n    gap: 6px !important;\n    padding: 10px 12px 8px !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :first-child > :first-child {\n    display: none !important;\n  }\n  /* The tab list scrolls in the space left by the toolbar: the toolbar\n     (config file + close) is reparented INTO this nav row by a client\n     effect (MobileNavOverlay), so the tab list must be anchored by its\n     class, NOT by :last-child (the reparented toolbar becomes the nav's\n     new last child).\n\n     2026-10-21 (DSH 0.2.1-rc.2): this rule used to declare\n     \"flex-wrap: wrap; overflow: visible\" on top of the flex/min-width/gap\n     above. Because it is one class-anchored compound selector with a much\n     higher specificity than compat.css.ts's portal-scoped navList rule, it\n     silently won the tie and the tab list wrapped into two rows \u2014 with the\n     reparented \u2715 vertically centred across both of them. Measured on a\n     phone shell: the list was 86px tall (two rows) instead of one 40px row,\n     and it scrolled nowhere. The wrap was a 2026-08-16 trade-off (show every\n     tab, no hidden scroll cut-off); with the thin scrollbar affordance now\n     in compat.css.ts the single scrolling row is the better trade, so the\n     two declarations live there and this rule no longer contradicts them. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :first-child [class$=\"_navList\"] {\n    flex: 1 1 auto !important;\n    min-width: 0 !important;\n    flex-direction: row !important;\n    gap: 6px !important;\n  }\n  /* Content toolbar (Open configuration file + close): grouped flush to\n     the right edge, and reparented INTO the nav row on mobile so it shares\n     one line with the tabs (user feedback 2026-08-16 \u2014 the toolbar's own\n     row left a full-width dead gap under the tabs). Anchored by class: the\n     header leaves the content subtree, so :first-child/:last-child anchors\n     would now hit the options area. Children carry official auto-margins\n     that would defeat flex-end, so neutralize them. The close button gets\n     a round tappable base so it reads as its own control, not part of the\n     outline button. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) [class$=\"_header\"] {\n    flex: 0 0 auto !important;\n    justify-content: flex-end !important;\n    align-items: center !important;\n    gap: 8px !important;\n    padding: 0 0 0 4px !important;\n    min-height: 40px !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) [class$=\"_header\"] > * {\n    margin-left: 0 !important;\n    margin-right: 0 !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) [class$=\"_header\"] > :last-child {\n    width: 32px !important;\n    height: 32px !important;\n    border-radius: 50% !important;\n    display: inline-flex !important;\n    align-items: center !important;\n    justify-content: center !important;\n    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06)) !important;\n  }\n  /* Appearance mode cards: the official cube row renders three tall\n     vertical cards (~268px) that eat half the sheet. Turn them into a\n     compact horizontal trio (icon + label inline, equal widths).\n     Relies on the official cube-row class name of this version. */\n  [aria-modal=\"true\"] [class$=\"_cubeRow\"] {\n    gap: 6px !important;\n  }\n  [aria-modal=\"true\"] [class$=\"_cubeRow\"] > * {\n    flex: 1 1 0 !important;\n    flex-direction: row !important;\n    align-items: center !important;\n    justify-content: center !important;\n    gap: 6px !important;\n    padding: 10px 8px !important;\n    min-height: 0 !important;\n  }\n  /* Content: the options scroll area gets bottom breathing room so the last\n     row never sits flush against the sheet's rounded corner. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :last-child {\n    flex: 1 1 auto !important;\n    min-height: 0 !important;\n  }\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])) > :last-child > :last-child {\n    padding: 0 12px 24px !important;\n  }\n";
 //# sourceMappingURL=layout.css.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"layout.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/layout.css.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,UAAU,+p5BA+hBtB,CAAA"}
+{"version":3,"file":"layout.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/layout.css.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,UAAU,s27BAwjBtB,CAAA"}

package/lib/types/client/wizard/GatewayWizard.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"GatewayWizard.d.ts","sourceRoot":"","sources":["../../../../src/client/wizard/GatewayWizard.tsx"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAGH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AACtC,OAAO,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,kCAAkC,CAAA;AACjF,OAAO,KAAK,EAMV,qBAAqB,EACtB,MAAM,oCAAoC,CAAA;AAmD3C,OAAO,EAAE,EAAE,EAAE,MAAM,eAAe,CAAA;AAMlC,MAAM,WAAW,kBAAmB,SAAQ,YAAY,CAAC,uBAAuB,CAAC,EAAE,WAAW,CAAC,OAAO,EAAE,CAAC;IACvG,qEAAqE;IACrE,MAAM,EAAE,qBAAqB,CAAA;IAC7B,2EAA2E;IAC3E,aAAa,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,OAAO,CAAC,EAAE;QAAE,KAAK,CAAC,EAAE,SAAS,MAAM,EAAE,CAAA;KAAE,KAAK,OAAO,CAAC,IAAI,CAAC,CAAA;CAC3G;AAoGD,wBAAgB,aAAa,CAAC,KAAK,EAAE,kBAAkB,GAAG,SAAS,CAm/DlE"}
+{"version":3,"file":"GatewayWizard.d.ts","sourceRoot":"","sources":["../../../../src/client/wizard/GatewayWizard.tsx"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAGH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AACtC,OAAO,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,kCAAkC,CAAA;AACjF,OAAO,KAAK,EAMV,qBAAqB,EACtB,MAAM,oCAAoC,CAAA;AAqD3C,OAAO,EAAE,EAAE,EAAE,MAAM,eAAe,CAAA;AAMlC,MAAM,WAAW,kBAAmB,SAAQ,YAAY,CAAC,uBAAuB,CAAC,EAAE,WAAW,CAAC,OAAO,EAAE,CAAC;IACvG,qEAAqE;IACrE,MAAM,EAAE,qBAAqB,CAAA;IAC7B,2EAA2E;IAC3E,aAAa,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,OAAO,CAAC,EAAE;QAAE,KAAK,CAAC,EAAE,SAAS,MAAM,EAAE,CAAA;KAAE,KAAK,OAAO,CAAC,IAAI,CAAC,CAAA;CAC3G;AAoGD,wBAAgB,aAAa,CAAC,KAAK,EAAE,kBAAkB,GAAG,SAAS,CAugElE"}