export declare const MISC_CSS = "@media (max-width: 1023px) and (pointer: coarse) {\n  /* ---------- hero composer on mobile ----------\n     The official hero card carries a 2-line textarea plus a tall tool row,\n     which reads oversized on a phone. Tighten the empty-state rhythm: keep\n     the official centered hero, shrink the textarea line box, slim the card\n     padding and the tool row, and close the gap under the headline. */\n\n  [data-phase=\"hero\"] [class*=\"_card\"]:has(textarea, [data-composer-input]) {\n    gap: 8px !important;\n  }\n  /* Composer stacks carrying the git branch chip must keep compat.css's 44px\n     chip clearance: that rule sets padding-top: 44px on the composer card of\n     any stack that contains the absolutely-positioned chip anchor (A\u2032, #105:\n     the chip stays in the dock subtree and is re-anchored to the stack, so\n     the exclusion moved from the card level to this stack-level :not(:has())\n     \u2014 a card-level :has() could never match anymore). Chip geometry: top\n     corner +12 + 28px chip \u2014 the chip grew 24\u219228px, so the clearance grew\n     40\u219244px to keep the same ~4px breathing gap (2026-09-06). This compact\n     override used to stomp the clearance back to 6px with the same\n     specificity (this sheet loads after compat), so on the hero empty state\n     the chip painted over the input line (2026-09-06). Excluding\n     chip-bearing stacks restores the clearance; the textarea collapse below\n     still applies to them. */\n  [data-phase=\"hero\"] [class*=\"_composerStack\"]:not(:has([data-gitgraph-chip-anchor])) [class*=\"_card\"]:has(textarea, [data-composer-input]) {\n    padding-top: 6px !important;\n  }\n  /* The official composer autosizes the textarea and writes an inline\n     height (2 lines on the hero empty state) on the textarea's scroll/grow\n     wrappers. :placeholder-shown lets us collapse the EMPTY state to one\n     line with !important; as soon as the user types, the pseudo-class no\n     longer matches and the autosizer's inline height takes over again \u2014 so\n     multi-line growth keeps working. */\n  [data-phase=\"hero\"] textarea:placeholder-shown {\n    height: 28px !important;\n  }\n  [data-phase=\"hero\"] [class*=\"_card\"]:has(textarea:placeholder-shown) > [class*=\"_scroll\"],\n  [data-phase=\"hero\"] [class*=\"_card\"]:has(textarea:placeholder-shown) [class*=\"_grow\"] {\n    height: 28px !important;\n  }\n  /* The one-line collapse above is deliberately NOT mirrored onto the Lexical\n     generation (0.1.2+), even though it signals its empty state with the\n     separate [data-composer-placeholder] node. That host pins the hero input\n     itself \u2014 hero-scoped min-height: 52px, because its hero hint wraps to two\n     lines \u2014 and a min-height floor beats an outer height: the 28px wrappers of\n     2026-09-05 only shrank the scrollport under a 52px input, i.e. overflow-y\n     auto with scrollHeight 52 against clientHeight 28 \u2192 scrollbar plus a\n     clipped first input line and hint line (phone report 2026-09-14, probe\n     scripts/probes/hero-composer-clip-probe.mjs). The textarea generation this\n     collapse was written for has no such floor \u2014 its input is a transparent\n     height:100% layer over the wrappers \u2014 so it still collapses there. */\n  [data-phase=\"hero\"] [class*=\"_card\"]:has(textarea, [data-composer-input]) > [class*=\"_row\"] {\n    padding-top: 2px !important;\n  }\n  [data-phase=\"hero\"] [class*=\"_headline\"] {\n    line-height: 1.15 !important;\n    margin-bottom: 0 !important;\n  }\n  [data-phase=\"hero\"] [class*=\"_stack\"] {\n    gap: 0 !important;\n  }\n\n  /* ---------- composer dock: swap git branch chip with the todo card ----------\n     The git-graph branch chip (conversation.input.dock, order 100) floats\n     alone at the bottom-left above the input card, with a dead zone to its\n     right; the full-width todo card (order 0) sits above it. Swap them so\n     the chip reads as the stack's top row and the todo card fills the row\n     above the composer. The dock container itself is display:contents\n     (inline style) \u2014 its children are direct flex items of the composer\n     stack, so order on the children is what reorders them. Only the chip\n     needs an order change: -1 puts it before the todo card (order 0) and\n     before the input card (order 0, later in DOM). The todo card must KEEP\n     its order 0 \u2014 raising it past the input card's order 0 would drop it\n     below the composer entirely (2026-08-16 regression, fixed). The queue\n     strip (order 20) keeps hugging the input card. Desktop untouched (this\n     block lives inside the max-width: 1023px media query). */\n  [data-slot=\"conversation.input.dock\"] [data-gitgraph-chip-anchor] {\n    order: -1 !important;\n  }\n  /* Mobile tap target + feedback for the branch chip (git-graph, 24px\n     desktop spec). Two real-world problems: \u2460 the chip is tiny and sits\n     right above the expandable todo card \u2014 mis-taps land on the todo card;\n     \u2461 opening the popover waits for the host's /git/branches round-trip\n     (~700ms on device) with zero feedback, so users tap again and toggle\n     the popover closed. Enlarge the target, kill double-tap zoom delay,\n     and give an instant pressed state so a tap reads as registered. */\n  [data-slot=\"conversation.input.dock\"] [data-gitgraph-chip-anchor] [data-gitgraph-chip] {\n    touch-action: manipulation !important;\n    min-height: 34px !important;\n    padding: 0 12px !important;\n    font-size: 13px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] [data-gitgraph-chip-anchor] [data-gitgraph-chip]:active {\n    transform: scale(.96) !important;\n    transition: transform .12s !important;\n  }\n\n  /* ---------- mattskills status capsule: keep its tail (skills button / fold\n      chevron) inside the pill on portrait ----------\n      dsh-mattpocock-skills-deck renders a capsule status bar in\n      conversation.input.dock (order 40, the row above the composer card). Its\n      own sheet deliberately never shrinks icons or counters (\"\u56FE\u6807\u4E0E\u666E\u901A\u8BA1\u6570\n      \u6C38\u4E0D\u6536\u7F29\"), so as soon as the capsule's content is wider than the pill the\n      host wrapper's overflow:hidden cuts the right edge and the two segments\n      that sit last \u2014 the skills-list button (2\u00D72 grid) and the fold chevron\n      that collapses the whole deck strip \u2014 are not painted at all.\n      Measured 2026-10-10 on a 393px portrait viewport, session bound to a\n      ticket with two-digit counters (\u53EF\u63A5 21 / \u8BCA\u65AD 20): capsule content\n      \u2248 415px against a ~360px pill, i.e. ~55px short \u2014 exactly those two\n      segments; the same session on landscape shows both, so this is width\n      pressure, not a missing feature (and not a deck version difference:\n      1.7.51 / 1.8.0-rc.1 / 1.8.0-rc.2 all render both unconditionally).\n      Reclaim the width from the capsule's desktop-sized spacing (6px column\n      gap plus 7px padding on each of ~11 children) rather than hiding any\n      segment, and keep a horizontal scroll as the fallback for the narrowest\n      phones so the tail can still be swiped into view. The scrollbar stays\n      hidden, so the pill still reads as one pill. Desktop untouched: this\n      block lives inside the max-width: 1023px media query. */\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule {\n    gap: 1px 3px !important;\n    padding: 3px 4px !important;\n    overflow-x: auto !important;\n    overflow-y: hidden !important;\n    scrollbar-width: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule::-webkit-scrollbar {\n    display: none !important;\n  }\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule .dsws-capsule-word {\n    padding: 2px 4px !important;\n    column-gap: 3px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule .dsws-seg {\n    padding: 2px 4px !important;\n    gap: 3px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule .dsws-split .dsws-split-part {\n    padding: 2px 4px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule .dsws-timebtn {\n    padding: 2px 4px !important;\n  }\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule .dsws-skillbtn,\n  [data-slot=\"conversation.input.dock\"] .dsws-capsule .dsws-fold-toggle {\n    padding: 1px 2px !important;\n  }\n\n  /* ---------- ask question composer (ask_user_question): kill iOS Safari\n      input-focus auto-zoom ----------\n      Safari on iPhone enlarges the whole viewport when a focused <input> /\n      <textarea> computes font-size < 16px, and only reverts on blur. The ask\n      dialog is a modal composer takeover, so taps outside never blur the\n      field and the magnification persists until the field loses focus\n      (e.g. the dialog is dismissed). The ask\n      composer's custom-answer <input> (.customInput) and optionless free-form\n      <textarea> (.customTextarea) both ship at 14px (ui-user-questions\n      QuestionComposer.module.css). Raise them to 16px on iOS only, where the\n      zoom can actually happen: on Android and desktop there is nothing to\n      suppress, so they keep the compact size they were designed with\n      (2026-09-16, audit D-1 option A; the iOS WebKit floor below covers these\n      fields too, this rule keeps the requirement stated where it applies).\n      Scoped to the ask\n      composer's stable [data-question-key] root (AGENTS.md: scope hashed-class\n      selectors to the owning region, prefer stable data-* markers); the\n      class-name suffix match follows the plugin's established harness\n      CSS-module convention (verified against the live app: generated names\n      end with the original local name, e.g. uV2eYG_input / bhn1Oq_searchInput). */\n  html[data-mobile-nav-ios] [data-question-key] [class*=\"_customInput\"],\n  html[data-mobile-nav-ios] [data-question-key] [class*=\"_customTextarea\"] {\n    font-size: 16px !important;\n  }\n\n  /* ---------- dsh-file-viewer inputs: kill iOS Safari auto-zoom ----------\n     Same rule as the ask composer above: the file viewer's search / jump-to-\n     line / pdf-page fields ship at 13-14px, which Safari auto-magnifies on\n     focus inside a panel that does not blur on tap-away. Raise them to 16px\n     on iOS only for the same reason as the ask composer above (2026-09-16,\n     audit D-1 option A). Scoped to the frame marker; the\n     viewer itself is scoped by its stable dsfv prefix.\n     (Port of community fork fix 2ff7976.) */\n  html[data-mobile-nav-ios] [data-mobile-nav=\"frame\"] [class*=\"dsfv-search-input\"],\n  html[data-mobile-nav-ios] [data-mobile-nav=\"frame\"] [class*=\"dsfv-jump-input\"],\n  html[data-mobile-nav-ios] [data-mobile-nav=\"frame\"] [class*=\"dsfv-page-input\"] {\n    font-size: 16px !important;\n  }\n\n  /* ---------- iOS WebKit: hold every text field at >=16px so Safari never\n      focus-zooms the viewport (#45) ----------\n      Report (iPhone 15 Pro Max): the page magnifies as soon as a field takes\n      focus, sometimes also when switching sessions (the host composer mounts\n      with autoFocus), and it stays magnified until the app is closed and\n      reopened or rotated landscape->portrait.\n      Mechanism: iOS Safari enlarges the visual viewport whenever a focused\n      input / textarea computes below 16px, and it only zooms back out on\n      blur \u2014 a chat shell keeps the composer focused, so the zoom has no\n      moment to revert; before this fix the root touch-action also withheld\n      pinch-zoom, so the user could not pull it back out either (see\n      layout.css.ts). maximum-scale=1 in the viewport meta is NOT the fix:\n      iOS 10+ ignores it for user pinch zoom while other engines honor it, so\n      writing it would only take zoom away from Android. Raising the fields is\n      the fix that stays inside the standard.\n      Gated on html[data-mobile-nav-ios] (phone-chrome.ts detectIosWebKit)\n      because only WebKit on iOS zooms on focus: Android and desktop keep the\n      compact 13px search boxes they were designed with. The floor covers\n      every text-entry field on the page, including the ones portalled\n      outside the frame (settings dialogs, the market sheet, third-party\n      panels) \u2014 a phone can reach all of them. Button-like and widget inputs\n      are excluded (nothing to type, no keyboard), and select is left alone on\n      purpose: it would break the composer's 28px access-mode control, and a\n      native picker overlays the screen instead of leaving a zoomed page\n      behind. The composer's mirror / backdrop layers ride along with the\n      textarea: they measure the autosize height and paint the highlight, so\n      all three must share one font-size or the caret drifts off the text\n      (they inherit 16px from the host card today \u2014 the rule locks that in on\n      hosts whose composer ships smaller).\n      The contenteditable branch is the forward-looking one: dsh\n      0.1.2-rc.1 replaces the composer textarea with a Lexical\n      contenteditable whose card reads font-size:\n      var(--dsh-content-font-size, 14px), i.e. 14px by default \u2014 squarely in\n      the zoom-triggering range. Match the attribute rather than the value\n      \"true\" (Lexical writes \"true\", other hosts use plaintext-only or the\n      bare attribute) and exclude contenteditable=\"false\", which Lexical puts\n      on decorator nodes inside the editor. */\n  html[data-mobile-nav-ios] textarea,\n  html[data-mobile-nav-ios] [contenteditable]:not([contenteditable=\"false\"]),\n  html[data-mobile-nav-ios] [data-input-mirror],\n  html[data-mobile-nav-ios] [data-input-backdrop],\n  html[data-mobile-nav-ios] input:not([type=\"button\"]):not([type=\"checkbox\"]):not([type=\"color\"]):not([type=\"file\"]):not([type=\"hidden\"]):not([type=\"image\"]):not([type=\"radio\"]):not([type=\"range\"]):not([type=\"reset\"]):not([type=\"submit\"]) {\n    font-size: 16px !important;\n  }\n\n  /* ---------- drawer session tree: skip off-screen rendering ----------\n     The drawer mounts ~389 nodes at once (the open gesture early-commits\n     the host state while the drawer is still off-screen), and during\n     streaming every token commit re-lays-out tree rows that are not even\n     visible. content-visibility: auto lets the engine skip layout and\n     paint of the session tree while it is outside the viewport (the arm\n     moment of the open gesture) and of off-screen rows when the drawer is\n     open on a long conversation. contain-intrinsic-size keeps the scroll\n     geometry stable while rows are skipped. Scoped to the drawer tree via\n     the frame marker + first child so the explorer sheet tree (a different\n     subtree) is not affected. Measured with CDP Tracing on an empty\n     conversation at 1x CPU (2026-08-29): biggest script task 104 -> 66ms,\n     max rAF gap 167 -> 33ms; the benefit scales with conversation length.\n     Desktop untouched (this block lives inside the max-width: 1023px\n     media query). */\n  [data-mobile-nav=\"frame\"] > :first-child [role=\"tree\"] {\n    content-visibility: auto;\n    contain-intrinsic-size: auto 600px;\n  }\n\n  /* ---------- text selection stays inside content (B1, 2026-10-04) ----------\n     Report (Android): long-press a word in an AI reply, drag the selection\n     handle up over the session header, and the selection jumps to \"select\n     all\" instead of extending through the message list. Mechanism: the\n     header and the composer card are ordinary selectable boxes; the header\n     sits BEFORE the scrollport in DOM order (header, then\n     [data-conversation-scroll]) and the drawer earlier still (frame first\n     child, parked off-screen at -110%). A selection extent whose hit point\n     resolves into that chrome lands IN the chrome, so the highlighted range\n     covers the header and app shell on top of the messages - on a phone it\n     reads as the whole page. With the chrome unselectable the extent snaps\n     to the nearest message text instead (headless drag-select 390x844\n     touch-emulated, message -> header: focus node went from the header\n     title span to a message <p>; message -> composer row: from the Send\n     button to a message <p>; the scrollport kept auto-scrolling in both).\n     Layout is untouched: this only sets user-select.\n     Kept selectable: the message flow (outside every rule below) and the\n     composer editing surface, which is re-enabled explicitly - auto would\n     inherit none from the card, and an unselectable contenteditable cannot\n     host a caret or a paste on WebKit. Dialogs and text fields portalled\n     into the drawer DOM (settings sheet) are re-enabled the same way, so\n     their values stay copyable. Scope: the conversation header is the host\n     header inside the [data-phase] root, anchored to the HOST HEADER CLASS\n     (header.wSkVaW_header) rather than to a bare header - a bare header also\n     hits every other <header> under [data-phase], and the ask-question card\n     (dsh-client-ui-user-questions QuestionComposer) renders its own\n     <header class=\"Mbwy4a_header\"> in composerSeat with the question text\n     as the heading. A bare header made that text unselectable, so the\n     question could not be long-press-copied (2026-10-20, same anchor rule\n     as the layout.css.ts header block; the dock above the input card is\n     reply content and must stay copyable). The anchor stays the DESCENDANT\n     form on purpose: 0.2.0-rc.2 (live-host probe 2026-10-07) renders an\n     unclassed wrapper <div> between .wSkVaW_root[data-phase] and\n     <header class=\"wSkVaW_header\">, so the child-combinator form this rule\n     used to carry matched 0 elements - the title bar kept user-select:auto\n     and a drag-select up over it still ended in the header title span (4391\n     selected chars, opening with the title / mode / tab labels). On the\n     composer side only the input card ([data-composer-card], host marker\n     since 0.1.2) and the plugin stats row. */\n  [data-mobile-nav=\"frame\"] > :first-child,\n  [data-mobile-nav=\"frame\"] [data-phase] header.wSkVaW_header,\n  [data-mobile-nav=\"frame\"] [data-composer-card],\n  [data-mobile-nav=\"stats\"],\n  [data-mobile-nav=\"fab\"],\n  [data-mobile-nav=\"backdrop\"] {\n    -webkit-user-select: none !important;\n    user-select: none !important;\n  }\n  [data-mobile-nav=\"frame\"] [data-composer-input],\n  [data-mobile-nav=\"frame\"] [data-composer-card] textarea,\n  [data-mobile-nav=\"frame\"] > :first-child [role=\"dialog\"],\n  [data-mobile-nav=\"frame\"] > :first-child input,\n  [data-mobile-nav=\"frame\"] > :first-child textarea,\n  [data-mobile-nav=\"frame\"] [data-phase] header.wSkVaW_header input {\n    -webkit-user-select: text !important;\n    user-select: text !important;\n  }\n}\n\n/* ---------- tablet / wide mobile: keep sheets from becoming full-width ----------\n   Below 768px the near-full-width sheets are the right call for a phone.\n   On wider but still sub-desktop viewports (foldables, tablet portrait,\n   desktop-mode tall windows) the same full-bleed sheet leaves content\n   clustered at the left edge with a large dead zone on the right. Cap and\n   center the modal sheets and the aionui bottom sheets instead. */\n@media (min-width: 768px) and (max-width: 1023px) and (pointer: coarse) {\n  /* Centered, never edge-to-edge \u2014 for the modal shapes below, not for every\n     modal dialog. Covered: modals that are not sheet-shaped, plus sheet-shaped\n     ones with neither a navigation element nor a directory picker. A modal\n     that is sheet-shaped AND carries the directory picker is left out on\n     purpose \u2014 layout.css.ts holds the dedicated rule for it. The settings\n     sheet has a higher-specificity full-width rule above, so repeat its\n     selector here to win; the generic export/other-modal rule is covered by\n     the second selector. */\n  [aria-modal=\"true\"]:has(> :first-child > :last-child > button):not(:has([role=\"navigation\"])):not(:has([class*=\"ZuhsRW\"])),\n  [aria-modal=\"true\"]:not(:has(> :first-child > :last-child > button)) {\n    left: 0 !important;\n    right: 0 !important;\n    margin-left: auto !important;\n    margin-right: auto !important;\n    width: min(calc(100vw - 32px), 720px) !important;\n    max-width: min(calc(100vw - 32px), 720px) !important;\n  }\n\n  /* The dsh-web-ui explorer / preview bottom sheets: same treatment \u2014 keep\n     the mobile bottom-sheet behavior, but stop them spanning the full width. */\n  [data-aionui-explorer-col],\n  [data-aionui-preview-col] {\n    left: 0 !important;\n    right: 0 !important;\n    width: min(calc(100vw - 32px), 720px) !important;\n    margin-left: auto !important;\n    margin-right: auto !important;\n  }\n\n  /* Settings sections (e.g. Agent presets) often carry a desktop max-width\n     (720px) that leaves a dead strip on the right once the sheet is capped to\n     the same width; let them fill the sheet body instead. */\n  [aria-modal=\"true\"] [class*=\"_section\"] {\n    width: 100% !important;\n    max-width: none !important;\n  }\n}\n\n/* ---------- desktop / non-touch: the mobile controls must never appear ----------\n   Exact complement of the mobile query \"(max-width: 1023px) and (pointer:\n   coarse)\" as a comma list (NOT A or NOT B): any viewport \u22651024px, plus any\n   narrow viewport whose primary pointer is a mouse (fine) or absent (none).\n   The pointer terms are what keep the header Files button off narrow desktop\n   windows \u2014 the slot renders the buttons at every width, so before this the\n   only guard was the width term (2026-08-30 PC leak: split windows and OS\n   display scaling dropped the CSS viewport below 1024px and armed the whole\n   mobile shell on desktop).\n\n   The session-delete trio (menu item + confirm/error dialog) is the ONE\n   deliberate exception: its effect arms on TOUCH_QUERY (pointer: coarse at\n   every width \u2014 large tablets in landscape), so it lives in the pointer-only\n   block below instead of this width arm. */\n\n@media (min-width: 1024px), (pointer: fine), (pointer: none) {\n  [data-mobile-nav=\"toggle\"],\n  [data-mobile-nav=\"files\"],\n  [data-mobile-nav=\"file-upload\"],\n  [data-mobile-nav=\"fab\"],\n  [data-mobile-nav=\"backdrop\"],\n  [data-mobile-nav=\"session-log\"],\n  [data-mobile-nav=\"session-log-wrap\"],\n  [data-mobile-nav=\"preview-full-toggle\"] {\n    display: none !important;\n  }\n}\n\n/* Session-delete trio: hide on mouse-driven or pointer-less windows at ANY\n   width. No width term \u2014 the injection is armed on touch at every width, so\n   a width arm here would hide the item on wide touch (the device class the\n   injection exists for). */\n@media (pointer: fine), (pointer: none) {\n  [data-mobile-nav=\"session-delete\"],\n  [data-mobile-nav=\"delete-dialog-backdrop\"],\n  [data-mobile-nav=\"delete-dialog\"] {\n    display: none !important;\n  }\n}\n";
//# sourceMappingURL=misc.css.d.ts.map