export declare const REMOTE_SESSION_CSS = "/* ---------- remote session: hide the open-on-the-server-machine entries ----------\n   A remote session's files live on the relay SERVER; every \"open\" control here\n   would act on the machine the DSH process runs on, not the one the browser is\n   on. Hidden while the current session is remote (html[data-zr-remote-session]):\n   - [data-open-target] is dsh-client-ui-open-in-app's own mount marker (RT\n     dsh-client-ui-open-in-app lib/client.js ~325: the split-button anchor\n     React renders with data-open-target={kind}) \u2014 one selector covers the\n     session-header \"Open In...\" button, the document-preview actions, AND the\n     \"Open / Show in Finder / Choose an application\" buttons of the changes\n     panel and the deliverable cards (RT dsh-client-ui-deliverables\n     lib/client.js ~1702, ~1963: those cards render the open-in-app package's\n     FileRouteAction through the deliverables.file.actions and\n     deliverables.review.file.actions slots, the same OpenTargetButton anchor).\n     The attribute is the component's own contract, not a generated class. */\nhtml[data-zr-remote-session=\"1\"] [data-open-target] {\n  display: none !important;\n}\n\n/* ---------- remote session: hide dsh-better-sidebar's file surfaces (T53, two regimes since PB-14) ----------\n   dsh-better-sidebar 0.25.0 is the second big \"open the machine's files\" UI\n   AND, since PB-12/13, the first ADAPTER-BRIDGED one: at exactly 0.25.0 its\n   /sidebar/api routes, its two WebSockets and its side chat cross the byte\n   tunnel and read/write the SERVER's data, gated on the whole-machine-data\n   consent. The hiding below therefore applies ONLY while the plugin is NOT\n   bridged \u2014 the :not([data-zr-bridge-dsh-better-sidebar=\"1\"]) stamp the\n   remote-status poll writes; see the PB-14 note above): bridged, the panels\n   are remote-aware and stay visible; unbridged (a different version, the\n   server without the adapter's consent), every tab it registers (files/\n   editor, git changes, subagent/tasks, side chat, the markdown/html/code\n   file viewers) builds its requests from a {sessionId, cwd} scope and POSTs\n   them to the plugin's own /sidebar/api/* routes on whichever machine\n   answers \u2014 in a remote session that is the SUB-CLIENT's machine (client.js\n   call() ~3111, fetchUpload ~3162, encodeHtmlUrl /sidebar/html/ ~3069-3414),\n   so the tree would show same-named LOCAL files as if they were the\n   session's and an edit would WRITE locally.\n\n   Anchors, all the plugin's or the host's own rendered contracts (no hashed\n   class names; the one suffix selector, _chipIcon, is unique among the\n   profile's packages \u2014 checked dsh-vision-router / dsh-auto-approve /\n   dsh-mem0 / dsh-llm-verifier / dsh-plugin-subscriptions /\n   @liustack/modsearch / @wxg-prc-cpg/browser-skill-dsh-plugin (modsearch /\n   browser-skill) / dshmarket and every @deepseek-ai sidebar package for it):\n\n   HONEST LIMITS (T53-fix, adjusted PB-14): unbridged, the plugin's\n   components stay mounted and keep silently POSTing READ-ONLY /sidebar/api\n   requests to the local machine (session.cwd, changes.ops, the tree reads a\n   mounted tab refreshes with) \u2014 the data never leaves that machine, and no\n   write can happen because every write control is inside the hidden\n   surfaces (the tab body hides its CHILDREN and spends the note copy as a\n   ::before, so an already-open tab reads WHY it is empty instead of\n   sitting blank). Known boundary: a dsh-resource://file/** address opened\n   through sidebarRight.openResource in a remote session (file links in\n   chat, deliverables, @-references, skills) is CLAIMED by the plugin's\n   editor registration (client.js ~21377: patterns [\"dsh-resource://file/**\"])\n   before the host preview sees it \u2014 the right sidebar expands, the rules\n   below hide the tab's body content and chip, and the note fills the panel.\n   Bridged (0.25.0 + consent), none of this applies: the tab reads the\n   server's data through the adapter and stays visible whole.\n\n   - [data-dsh-bottom-toggle] \u2014 the header-utilities button that expands the\n     bottom workbench (client.js BottomDockToggle ~20863; slot registration\n     ~21492-21498, id dsh-better-sidebar:bottom-toggle). Our own phone header\n     button drives the OFFICIAL right sidebar (MobileSessionHeader.tsx), so\n     hiding this does not strand the phone.\n   - [data-dsh-panel-host] \u2014 the fixed viewport layer the plugin appends to\n     document.body (client.js ~20763); the bottom workbench panel\n     ([data-dsh-bottom-panel]) is its only child, so hiding the layer hides\n     the workbench whole (tab strip, + menu, tree, editor and all).\n   - --dsh-sidebar-height \u2014 the plugin's layout push: written INLINE on <html>\n     while the workbench is open (client.js writeGeometry ~20482-20488) and\n     spent by its own layout.css as the center column's margin-bottom\n     (client.js layout css ~23009: #root [data-dsh-center-col] { margin-bottom:\n     var(--dsh-sidebar-height, 0px) }). Hiding the panel alone would leave\n     that reserved band as a blank strip under the conversation, so the remote\n     html zeroes the variable. A stylesheet !important beats a non-important\n     inline style, and the plugin's JS state is never touched: the moment the\n     attribute is removed (back on a local session) its own value applies\n     again, transitions included.\n   - [data-dsh-native-tab-host] \u2014 the wrapper the plugin renders around EVERY\n     tab body it contributes to the host's native right Sidebar\n     (client.js NativeTabBody ~21074, marker ~21110/21120). The host's pane\n     chrome is untouched: the strip keeps the \"+\" (guide) button and the\n     collapse/fullscreen controls, so a tab that was already open leaves no\n     dead panel \u2014 an empty body behind a strip that still collapses, and the\n     \"+\" re-opens the guide page (whose plugin capsules these rules hide, see\n     below). React keeps mounting into the display:none node: no errors, and\n     the restore on returning to a local session is instant.\n   - [data-dockkit-tab]:has([class$=\"_chipIcon\"]) \u2014 the native tab STRIP's\n     chips for plugin tabs, so an already-open tab does not survive as a\n     clickable ghost. The chip button is dockkit's ([data-dockkit-tab], dsh-web\n     frontend bundle: role=tab, renderTabTitle inside a\n     span[data-dockkit-tab-title]); its content is the plugin's\n     NativeTabTitle (~21172-21197), which always leads with a\n     [class$=\"_chipIcon\"] glyph span because every built-in descriptor ships an\n     icon \u2014 a chip with no glyph (an external tab registered through the\n     plugin's viewer service without an icon) keeps its chip; its body is\n     still hidden by the rule above. Host tabs' chips never contain a\n     _chipIcon (checked all four @deepseek-ai sidebar packages), so the\n     remote-aware host files page survives alongside.\n   - [data-floating-window]:has([data-window-body]) \u2014 the plugin's\n     body-PORTALED floating windows (client.js FloatingWindow ~15078-15120):\n     the task edit window (teams.taskCreate/Update with rootSessionId via\n     /sidebar/api, writeTask ~3124-3140) and the job-output window (host jobs\n     kill). Both open from the subagent/tasks tab; portal escapes the tab\n     body's display:none, so they need their own rule. Anchored on the\n     window's own root attribute plus its own inner body marker, so a foreign\n     [data-floating-window] without that shape never matches.\n   - guide capsules \u2014 the empty-sidebar doorway buttons the HOST renders from\n     the plugin's registrations ([data-sidebar-right-guide-entry=\"<kind>\"], RT\n     dsh-client-ui-sidebar-right lib/client.js:466): kinds git / subagent /\n     sidechat exist only while this plugin registers them, so those selectors\n     are inert without it. The \"files\" capsule is the one ambiguous kind:\n     dsh-client-ui-sidebar-files registers the SAME kind (its filesDefinition,\n     lib/client.js:14-31) and that page is REMOTE-AWARE (it injects the host's\n     remote.workspaceFiles service). T53-fix discriminates on the capsule's\n     own rendered contract instead of plugin presence: the host's EntryBox\n     renders aria-keyshortcuts from the shortcut matching entry.commandId (RT\n     sidebar-right lib/client.js:461-467) \u2014 the host files guide row carries\n     commandId \"workspace.files\" (dsh-client-ui-sidebar-files\n     lib/client.js:30), while better-sidebar's guide rows carry NO commandId\n     (client.js registerNativeSurface ~21385-21400), so its capsule never\n     renders the attribute. :not([aria-keyshortcuts]) therefore hides the\n     plugin's takeover capsule and spares the host's wherever the host has a\n     default binding. Boundary: that \"wherever\" is not everywhere \u2014 the host\n     registers workspace.files defaults for desktop:macos/windows/linux and\n     web:macos/windows only (dsh-client-ui-sidebar-files lib/client.js:949-977),\n     so on any other platform the OFFICIAL capsule also renders without the\n     attribute and this rule hides it too (cosmetic; the page stays reachable\n     through its shortcut command path and the plugin's takeover is the\n     \"files\" implementation on every deployment this plugin pairs with\n     better-sidebar anyway).\n\n   /* PB-14: every T53 rule below carries\n   :not([data-zr-bridge-dsh-better-sidebar=\"1\"]) \u2014 when the adapter\n   (PB-12) bridges the plugin, the panels read the SERVER's data through\n   the byte tunnel and MUST stay visible; the hiding applies only to the\n   unbridged combination, and the empty tab body then carries a note\n   instead of blankness. The stamp is written by\n   effects/remote-session.ts off the remote-status poll's bridgedPlugins\n   list (client-data/remote-status.ts shouldStampBridgeAttribute). */\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-dsh-bottom-toggle] {\n  display: none !important;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-dsh-panel-host] {\n  display: none !important;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) {\n  --dsh-sidebar-height: 0px !important;\n}\n/* The unbridged tab body: hide the plugin's own content and spend the\n   note copy as a ::before \u2014 an already-open tab reads WHY it is empty\n   (0.25.0 keeps tabs mounted, so a stale body would otherwise sit blank).\n   --zr-bridge-note is set on <html> by the stamp effect, in the\n   browser's language; unset (effect not running yet) the content falls\n   through and nothing renders. */\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-dsh-native-tab-host] > * {\n  display: none !important;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-dsh-native-tab-host]::before {\n  content: var(--zr-bridge-note);\n  display: block;\n  padding: 24px 16px;\n  font-size: 13px;\n  line-height: 1.7;\n  color: var(--dsh-fg-muted, #6b7280);\n  word-break: break-word;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-dockkit-tab]:has([class$=\"_chipIcon\"]) {\n  display: none !important;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-floating-window]:has([data-window-body]) {\n  display: none !important;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-sidebar-right-guide-entry=\"git\"],\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-sidebar-right-guide-entry=\"subagent\"],\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-sidebar-right-guide-entry=\"sidechat\"] {\n  display: none !important;\n}\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-sidebar-right-guide-entry=\"files\"]:not([aria-keyshortcuts]) {\n  display: none !important;\n}\n/* 0.25.0's dock fallback \u2014 the floating quick-open button the plugin pins\n   for empty workspaces. Same treatment as every other open-the-machine's-\n   files control: hidden while unbridged, untouched when bridged. */\nhtml[data-zr-remote-session=\"1\"]:not([data-zr-bridge-dsh-better-sidebar=\"1\"]) [data-dsh-dock-fallback] {\n  display: none !important;\n}\n\n/* ---------- T52/T74: model-menu groups follow the session's side ----------\n   The model catalog is GLOBAL (one shared load per page), so the merged\n   catalog shows the server's groups everywhere; but a selection is only\n   runnable on the side the open session lives on \u2014 the interceptor refuses\n   the other side with a clear message. Hide what cannot run.\n\n   What changed and why the mechanism is a STAMP now (T74): through 0.1.7\n   each menu group rendered aria-labelledby=\"<useId>-<group.id>\" (RT017\n   dsh-client-ui-model-selection lib/client.js ~824-830) \u2014 the group id was\n   IN the attribute, and rules could key on a virtual group's \"zr~\" prefix\n   directly. 0.2.0 renders the groups with the primitives' MenuGroup\n   instead (RT dsh-client-ui-primitives lib/index.js ~4283-4304): the\n   section's aria-labelledby carries ONLY the useId, the heading is a child\n   div[data-menu-group-heading], and the menu container is a div whose id\n   ends in \"-models\" with role=\"menu\" (RT dsh-client-ui-model-selection\n   lib/client.js ~974-980). Two consequences killed the old rules: a group\n   section no longer says anywhere in its markup which group it is, and the\n   same MenuGroup renders OTHER menus' groups too \u2014 the old\n   [role=\"menu\"] section[role=\"group\"] scope alone was too wide and would\n   have hidden every unmarked group of every menu in a remote session\n   (leaving just the search box), while missing the server's groups in\n   local ones.\n\n   The new keys on what EVERY version actually renders, the heading text:\n   each virtual group's name is prefixed with the invisible WORD JOINER\n   (VIRTUAL_GROUP_NAME_MARK, virtual-id.ts; written by mergeModelCatalogs).\n   The browser effect (effects/model-group-side.ts) reads each group's\n   heading and stamps data-zr-group=\"remote|local\" on the section \u2014 but\n   only inside a CONTAINER (the sections' shared parent element) that holds\n   at least one marked heading. That container rule is what scopes these\n   rules to the model menu alone WITHOUT assuming menu structure: an\n   unpaired client's model menu, every other menu, and the whole rest of\n   the page hold no marked heading, receive no stamp, and match neither\n   rule. And since the merged catalog only ever APPENDS virtual groups to\n   the local list, within a decided container the unmarked groups are\n   exactly the local ones \u2014 mixed containers (the norm) decide each group\n   separately. The menu is a portal under <body>, but <html> is still its\n   ancestor, so the html-level session attribute scopes both rules. If the\n   effect is not running (uninstalled, or a host-role page that never had\n   it), no stamp exists and both rules go inert \u2014 nothing stays hidden.\n\n   KNOWN BOUNDARY (accepted, not fixed): in a remote session, searching the\n   model menu and pressing Enter can commit a HIDDEN local model \u2014 the\n   interceptor refuses it with its usual message. */\nhtml[data-zr-remote-session=\"1\"] section[role=\"group\"][data-zr-group=\"local\"] {\n  display: none !important;\n}\nhtml:not([data-zr-remote-session]) section[role=\"group\"][data-zr-group=\"remote\"] {\n  display: none !important;\n}\n\n/* ---------- T52-fix: hide the virtual groups in NATIVE <option> pickers ----\n   The model menu above is React DOM, but dsh-vision-router's settings render\n   its vision-backend picker as a native <select> of <option value={group.id}>\n   rows, and its filter (dsh-vision-router lib/client.js:661-670\n   filterVisionBackendGroups) drops only vision-http / vision-chain / *-vision\n   \u2014 a merged virtual group (\"zr~<id>~\u2026\") survives into that picker even\n   though a server model can never be a LOCAL vision backend (the router calls\n   providers from the machine it runs on). Native <option> rows honor\n   display:none in the dropdown list, so this hides them wherever they appear:\n   - no scoping attribute on purpose: a virtual group is not a runnable\n     backend in ANY local context, and the option element itself carries the\n     value \u2014 no host-depth assumption, no :has();\n   - when the vision router (or any other <option>-rendering surface) is not\n     installed, nothing matches \u2014 dead rule, zero cost;\n   - zen-remote's own surfaces are checked: our settings forms render fixed\n     enum options (\"web\" / \"desktop-client\" / role kinds /\n     configForm enum strings, src/client/settings/SettingsSection.tsx:641,690-701)\n     and none can start with \"zr~\" (virtual group ids only ever exist inside\n     model-catalog payloads and model-selection arguments). */\noption[value^=\"zr~\"] {\n  display: none !important;\n}\n\n/* ---------- remote session: hide the session-export menu item (T51, T51-fix) ----------\n   A remote session's log lives on the relay server and the backend refuses\n   /api/session.export for a virtual id with 403 remote-unsupported\n   (fetch-route-intercept.ts) \u2014 the item would only ever end in the \"Export\n   failed\" modal, so it is hidden IN THE MENU (T51-fix: the anchor button\n   stays, because it also opens the \u53CD\u9988 entry, which a remote session can\n   still use). The DOM, verified against RT:\n   - the Menu renders its anchor and its list as SIBLINGS inside its own\n     span root (RT dsh-client-ui-primitives lib/index.js ~4265-4273:\n     children = [anchor, portal ? createPortal(list) : list]), and the\n     export Menu passes no portal flag (default false, ~3923) \u2014 so the list\n     is the anchor's next sibling, matched by the general-sibling\n     combinator below;\n   - the list surface carries role=\"menu\" (Menu passes it at ~4243;\n     MenuSurface spreads ...props onto its root div, ~3778-3795) and the\n     items viewport inside it is div[role=\"presentation\"] (~4249-4252);\n   - every data item is ONE div (the itemWrap wrapper, ~4143), so\n     :first-child of the viewport is the FIRST item \u2014 and the export\n     package puts \u4E0B\u8F7D/\u5BFC\u51FA first by construction (RT dsh-session-log-export\n     lib/client.js 202-206, the optional feedback entry appended after at\n     207-211).\n   The anchor button class suffix is matched the way compat.css.ts matches\n   module classes (the hash prefix is build-local, \"_moreButton\" is the\n   source name; unique in this slot \u2014 the only other moreButton in the RT\n   tree, dsh-client-ui-sidebar-documentpreview lib/client.excel.js, lives in\n   the sidebar, never under conversation.session.header.utilities).\n   Known costs, accepted: with the feedback UI absent the menu's only item\n   is the export, so the opened menu is EMPTY; and keyboard navigation still\n   steps into the hidden item (focusable but invisible) until activated or\n   escaped \u2014 it cannot be triggered through the visibility, only tabbed\n   past blindly. */\nhtml[data-zr-remote-session=\"1\"] [data-slot=\"conversation.session.header.utilities\"] [class$=\"_moreButton\"] ~ [role=\"menu\"] > [role=\"presentation\"] > :first-child {\n  display: none !important;\n}\n\n/* ---------- remote session: the \"save to this machine\" action (2.2.6) ----------\n   One class, owned by this plugin (no host module class, no hash): the\n   deliverable-card entry renders it in the card's own actions cell, the\n   document-preview entry in the preview header where open-in-app's control\n   sits (that one is hidden remotely by the [data-open-target] rule above,\n   so this is the only action left there). Both entries only MOUNT for a\n   virtual session, so the html attribute gate is belt-and-braces, not the\n   decision.\n   The palette variables are the host's own (label-secondary / border-l1 /\n   interactive-bg-hover / state-error), which keeps light/dark identical to\n   the cards around it without copying a theme. */\nhtml[data-zr-remote-session=\"1\"] .zr-download-action {\n  box-sizing: border-box;\n  flex: none;\n  font: inherit;\n  font-size: 12px;\n  line-height: 18px;\n  color: var(--dsw-alias-label-secondary, #6b7280);\n  background: transparent;\n  border: 0.5px solid var(--dsw-alias-border-l1, #d9dde3);\n  border-radius: var(--dsw-radius-sm, 4px);\n  padding: 1px 8px;\n  cursor: pointer;\n  white-space: nowrap;\n}\nhtml[data-zr-remote-session=\"1\"] .zr-download-action:hover {\n  color: var(--dsw-alias-label-primary, #111827);\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, 0.05));\n}\nhtml[data-zr-remote-session=\"1\"] .zr-download-action[data-phase=\"busy\"] {\n  cursor: progress;\n  opacity: 0.7;\n}\nhtml[data-zr-remote-session=\"1\"] .zr-download-action[data-phase=\"error\"] {\n  color: var(--dsw-alias-state-error-primary, #dc2626);\n  border-color: var(--dsw-alias-state-error-primary, #dc2626);\n}\n";
//# sourceMappingURL=remote-session.css.d.ts.map