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";
//# sourceMappingURL=composer.css.d.ts.map