dsh-zen-remote 1.1.2 → 1.1.4

package/lib/client.js

@@ -2463,6 +2463,17 @@ __modules["styles/compat.css.js"] = function (require, module, exports) {
 // Do not reorder: styles/index.ts concatenates in this exact order.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.COMPAT_CSS = void 0;
+const attach_upload_ts_1 = require("./attach-upload.js");
+/* Presence gate for @ace-zone/dsh-market. Its markup carries no mount
+   marker and its `dshm-` class prefix is not proof of identity — several
+   unrelated plugins call themselves a "dsh market". The version chip in
+   the modal header is rendered as
+   `<span class="dshm-ver" title="@ace-zone/dsh-market">`, i.e. the exact
+   package name as a rendered contract, so it is the one selector that
+   cannot match anything else. Every rule below hangs off it: with the
+   plugin absent (or its modal closed) nothing matches and the section is
+   inert. */
+const MARKET = '.dshm-ver[title="@ace-zone/dsh-market"]';
 exports.COMPAT_CSS = `  /* ---------- dsh-web-ui family compatibility ----------
      The linxin666 plugin suite extends the shell frame directly:
        - aionui-panel appends two trailing grid columns (explorer / preview)
@@ -3198,6 +3209,78 @@ exports.COMPAT_CSS = `  /* ---------- dsh-web-ui family compatibility ----------
       display: none !important;
     }
   }
+
+  /* ---------- dsh-at-file compatibility ----------
+     dsh-at-file registers its own \`conversation.input.dock\` entry
+     ([data-at-file-dock]) and renders one row per \`@path\` token in the
+     draft. That is exactly the same source this plugin's attachment chips
+     read, so on a phone a single uploaded image produced TWO entries on the
+     composer rail: our 48px thumbnail tile AND at-file's file-name row for
+     the same token (reported 2026-08-22).
+
+     Drop at-file's row for the upload directory only. Everything else the
+     user @-mentions by hand is at-file's own job and stays — this is not a
+     blanket hide. The path is readable from the row's own title attribute
+     (FilesDock passes \`title={mention.relative}\`), which is a rendered
+     contract rather than a hashed class name.
+
+     Phone only, and deliberately so: at \u003e= 768px our chips are hidden by
+     composer.css.ts, which leaves at-file's row as the ONLY thing on screen
+     representing the attachment. Hiding it there would make an uploaded file
+     invisible.
+
+     When every row was an upload the container itself is left empty, and an
+     empty flex item still claims the rail's 6px gap — so the dock goes too
+     unless at least one non-upload row survives. */
+  @media (max-width: 767px) {
+    [data-at-file-dock] [data-at-file-row]:has([title^="${attach_upload_ts_1.UPLOAD_DIR}/"]) {
+      display: none !important;
+    }
+    [data-at-file-dock]:not(:has([data-at-file-row] [title]:not([title^="${attach_upload_ts_1.UPLOAD_DIR}/"]))) {
+      display: none !important;
+    }
+  }
+  /* ---------- @ace-zone/dsh-market: modal header fits a phone (2026-08-22) ----------
+     THIRD-PARTY COMPAT RULE — @ace-zone/dsh-market (the plugin market:
+     a settings-page entry that opens its own body-level modal,
+     .dshm-overlay > .dshm-panel, over the settings sheet).
+
+     Its header (.dshm-head) is a plain flex row with no wrapping and no
+     shrinking: title, a badge strip whose slogan is white-space:nowrap,
+     a version chip, an "official site" link, a language toggle, and only
+     then the × that closes the modal. Flex items default to
+     min-width:auto, so at phone widths the row keeps its intrinsic size,
+     .dshm-panel clips it (overflow:hidden), and the × — the only way out
+     of the modal on a touch screen, which has no Esc key — is off screen
+     (reported 2026-08-22).
+
+     Drop the three decorative items and let the title ellipsis instead.
+     The language toggle stays: it is a real control, and title + toggle +
+     × fit inside 320px once the title can shrink. The title rule also
+     covers the job / help overlays, which reuse .dshm-head with a long
+     "<action> · <package>" title and no flexible item of their own.
+     Nothing here is desktop-side: at >= 768px the row has the width it
+     was written for. */
+  @media (max-width: 767px) {
+    body:has(${MARKET}) .dshm-head > .dshm-head-badges,
+    body:has(${MARKET}) .dshm-head > .dshm-ver,
+    body:has(${MARKET}) .dshm-head > a.dshm-viewbtn {
+      display: none !important;
+    }
+    body:has(${MARKET}) .dshm-head > .dshm-title {
+      flex: 1 1 auto !important;
+      min-width: 0 !important;
+      overflow: hidden !important;
+      text-overflow: ellipsis !important;
+      white-space: nowrap !important;
+    }
+    /* 44px touch target: their 20px glyph in 2px/6px padding is ~30px. */
+    body:has(${MARKET}) .dshm-head > .dshm-close {
+      flex: 0 0 auto !important;
+      font-size: 24px !important;
+      padding: 6px 12px !important;
+    }
+  }
 `;
 };
 __modules["styles/misc.css.js"] = function (require, module, exports) {
@@ -4670,9 +4753,18 @@ exports.COMPOSER_CSS = `/* ---------- phone composer (< 768px) ---------- */
   /* --- 7b. attachment chips (S7.1) ---
      Our own dock entry opts OUT of the 26px pill cage above: an image chip is
      a 48px tile. The row sits tight under the card's top edge, so the chips
-     read as part of the composer rather than as a floating strip. */
+     read as part of the composer rather than as a floating strip.
+
+     It also takes the LAST line of its own (line policy in 7c): a 48px tile
+     beside the to-do chip on one nowrap line squeezed that chip down to an
+     unreadable stub, with a long file name pushing the rest off-screen
+     (reported 2026-08-22). Its own chips wrap rather than overflow, so
+     several attachments stack instead of scrolling out of reach. */
   [data-slot="conversation.input.dock"] > [data-mobile-nav="attach-chips"] {
     display: flex !important;
+    flex: 1 0 100% !important;
+    flex-wrap: wrap !important;
+    order: 2 !important;
     align-items: center !important;
     gap: 6px !important;
     max-width: none !important;
@@ -4682,6 +4774,57 @@ exports.COMPOSER_CSS = `/* ---------- phone composer (< 768px) ---------- */
     overflow: visible !important;
     margin-bottom: -2px;
   }
+
+  /* --- 7c. the queue strip opts OUT of the cage, on a line of its own ---
+     Third entry that is not a pill. conversation.input.dock is a \`list\` slot
+     and DSH's own QueueDock registers into it at order 20 (id \`queue\`,
+     dsh-client-ui-conversation) — a 36px row per queued message, or a
+     collapsible "N 条排队消息" header once there is more than one. The 26px
+     cage above clipped it to a sliver: on a phone a queued message showed as
+     a grey stub poking out from behind the input card, unreadable and with
+     its edit / delete / send buttons cut off (reported 2026-08-22, same
+     failure the to-do card hit in 7a).
+
+     Two things are restored. Geometry: the official row height back, and the
+     dock's own composer-column sizing dropped — its width/max-width are
+     calc()s over the composer card variables and its bottom margin is
+     negative by design (upstream tucks the strip UNDER the card), none of
+     which survives being a flex item of our chip rail.
+
+     Layout — the line policy for the whole rail, now that three things want
+     room on it. The pills (the to-do card, a branch chip, whatever else
+     registers) keep order 0 and share the top line, still scrolling
+     horizontally. The queue takes the next line (order 1). The attachment
+     chips take the last one (order 2, 7b), so what the user is about to send
+     sits closest to the input it will be sent from. The rail only wraps
+     while one of the two full-width entries exists, so a session with
+     neither keeps the original single scrolling chip line. */
+  [data-slot="conversation.input.dock"]:has(> [data-queue-dock], > [data-mobile-nav="attach-chips"]) {
+    flex-wrap: wrap !important;
+  }
+  [data-slot="conversation.input.dock"] > [data-queue-dock] {
+    flex: 1 0 100% !important;
+    order: 1 !important;
+    max-width: none !important;
+    min-height: 0 !important;
+    max-height: none !important;
+    margin: 0 !important;
+    padding: 0 !important;
+    border-radius: 0 !important;
+    overflow: visible !important;
+    font-size: 13px !important;
+    line-height: normal !important;
+  }
+  /* The panel is the dock's only child; upstream rounds its top corners only
+     and drops the bottom border, because there it is half-hidden behind the
+     card. On its own line it is a free-standing strip, so close it up. */
+  [data-slot="conversation.input.dock"] > [data-queue-dock] > * {
+    border-radius: 12px !important;
+  }
+  [data-slot="conversation.input.dock"] > [data-queue-dock] > *::after {
+    border-bottom: 1px solid var(--dsw-alias-border-l1) !important;
+  }
+
   [data-mobile-nav="attach-chip"] {
     position: relative;
     display: inline-flex;
@@ -5140,1996 +5283,2103 @@ exports.INFO_CSS = `/* ---------- session-info sheet (< 768px) ---------- */
 }
 `;
 };
-__modules["styles/turn-fold.css.js"] = function (require, module, exports) {
+__modules["client-config.js"] = function (require, module, exports) {
 "use strict";
-// turn-fold — the folded turn process and its summary row (S8, 2026-08-17).
-// Everything that can hide content lives inside (max-width: 767px) OR behind
-// html[data-mnav-desktop-fold] (the per-browser desktop opt-in, issue #2);
-// the two markers this file reads (data-mnav-fold on a process element,
-// data-mobile-nav="turn-fold" on the injected summary row) are only ever
-// written by effects/turn-fold.ts, which detaches and wipes them when it is
-// not active — so a non-opted-in tablet/desktop is a no-op twice over, by
-// attribute and by scope. The rule block is authored once and emitted twice
-// (phone media query / desktop attribute scope) so the two can never drift.
-// Appended last in styles/index.ts; it shares no selector with any other
-// file, the position just keeps the "phone files come after the shared
-// <=1023px block" ordering intact.
+/**
+ * The plugin row's client-facing knobs, fetched once per page.
+ *
+ * The client bundle ships statically and never sees the row config, so the
+ * host republishes the client-relevant subset at {@link CLIENT_CONFIG_ROUTE}
+ * (src/index.ts). Two effects read it — turn-fold's desktop switch and
+ * keyboard-avoid's fallback tuning — so the request is memoized here rather
+ * than fired once per reader.
+ *
+ * Defaults live in THIS file, not in the host: the route omits a knob the
+ * row never set, so there is exactly one place each default is written and
+ * no way for the two halves to drift apart on the value. The host's job is
+ * only to validate and clamp what a user actually typed.
+ *
+ * Every read is total — a failed request, a non-JSON body, or a garbage
+ * value all fall back to the defaults rather than throwing into an effect.
+ */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.TURN_FOLD_CSS = void 0;
-/** The fold + chip rules, with every selector prefixed by `scope`. */
-const rules = (scope) => `
-  /* Folded process: tool-call / context / command rows and the Think
-     disclosures inside an assistant step. !important because the official
-     flow item and ReasoningRow both set their own display. */
-  ${scope} [data-mnav-fold]:not([data-mnav-fold-open]) {
-    display: none !important;
-  }
-
-  /* Compact chip, sized like the composer's own pills rather than a button:
-     it is a reading affordance in the middle of the message flow, so it has
-     to stay quieter than the content around it. The flow column is a flex
-     column with gap: 16px (ChatView.module.css) — align-self keeps the chip
-     from stretching, and the negative block margin trims that generous gap
-     back to something a 26px row can live in. */
-  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"] {
-    display: inline-flex;
-    align-self: flex-start;
-    align-items: center;
-    gap: 6px;
-    margin: -4px 0;
-    padding: 0 10px;
-    height: 26px;
-    border: none;
-    border-radius: 13px;
-    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
-    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .55));
-    font: inherit;
-    font-size: 12px;
-    line-height: 26px;
-    white-space: nowrap;
-    cursor: pointer;
-    -webkit-tap-highlight-color: transparent;
-  }
-  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]:active {
-    background: var(--dsw-alias-interactive-bg-pressed, rgba(0, 0, 0, .1));
-  }
-
-  /* Leading dot: idle turns get a quiet mark, a running turn gets the same
-     business-primary colour the session header's own status dot uses
-     (styles/header.css.ts) plus a breathing pulse. */
-  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]::before {
-    content: '';
-    flex: none;
-    width: 6px;
-    height: 6px;
-    border-radius: 50%;
-    background: currentColor;
-    opacity: .45;
-  }
-  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"][data-running]::before {
-    background: var(--dsw-alias-state-business-primary, #4f6ef7);
-    opacity: 1;
-    animation: dsh-mobile-nav-breathe 1.4s var(--ds-ease-in-out, ease-in-out) infinite;
-  }
-
-  /* Chevron drawn from two borders — no icon injection, no mask image, and
-     it rotates to point up once the turn is open. */
-  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]::after {
-    content: '';
-    flex: none;
-    width: 5px;
-    height: 5px;
-    margin-top: -3px;
-    border-right: 1.5px solid currentColor;
-    border-bottom: 1.5px solid currentColor;
-    transform: rotate(45deg);
-    transition: transform .16s var(--ds-ease-out, ease-in-out);
-  }
-  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"][data-open]::after {
-    margin-top: 3px;
-    transform: rotate(-135deg);
-  }
-
-  @media (prefers-reduced-motion: reduce) {
-    ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"][data-running]::before {
-      animation: none;
-    }
-    ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]::after {
-      transition: none;
-    }
-  }
-`;
-exports.TURN_FOLD_CSS = `/* ---------- turn process fold (< 768px, or desktop opt-in) ---------- */
-
-/* The summary row never paints outside its active scope, even if a
-   media-query change raced the effect's own cleanup. */
-[data-mobile-nav="turn-fold"] {
-  display: none;
+exports.KEYBOARD_DEFAULTS = exports.CLIENT_CONFIG_ROUTE = void 0;
+exports.parseClientConfig = parseClientConfig;
+exports.clientConfig = clientConfig;
+/** Mirror of src/index.ts CLIENT_CONFIG_ROUTE (client tsconfig cannot reach it). */
+exports.CLIENT_CONFIG_ROUTE = '/_dsh/mobile-nav/client-config';
+/** Shipped tuning: the values measured on the one reported device (issue #1,
+ * WeType ~315 CSS px on an 858px viewport) plus the Android IME under-report
+ * pad. Changing these changes the default for every install — a per-device
+ * fix belongs in that install's plugin row instead. */
+exports.KEYBOARD_DEFAULTS = {
+    liftRatio: 0.42,
+    liftMaxPx: 400,
+    safetyPadPx: 15,
+};
+/** One published number, or the shipped default when the row left it unset
+ * (the route omits the key) or the body is not what it claims to be. */
+function num(value, fallback) {
+    return typeof value === 'number' && Number.isFinite(value) ? value : fallback;
 }
-
-@media (max-width: 767px) {${rules('')}}
-
-/* Desktop opt-in: the exact same block, keyed on the root attribute
-   effects/turn-fold.ts sets for a browser opted in via
-   ?mobile-nav-turn-fold=1 — active at every width. */
-${rules('html[data-mnav-desktop-fold]')}
-
-@keyframes dsh-mobile-nav-breathe {
-  0%, 100% { opacity: 1; transform: scale(1); }
-  50% { opacity: .4; transform: scale(.72); }
+/** Parse one route body. Exported for scripts/check-client-config.mjs. */
+function parseClientConfig(body) {
+    const row = typeof body === 'object' && body !== null
+        ? body
+        : {};
+    return {
+        turnFoldDesktop: row['turnFoldDesktop'] === true,
+        keyboard: {
+            liftRatio: num(row['keyboardLiftRatio'], exports.KEYBOARD_DEFAULTS.liftRatio),
+            liftMaxPx: num(row['keyboardLiftMaxPx'], exports.KEYBOARD_DEFAULTS.liftMaxPx),
+            safetyPadPx: num(row['keyboardSafetyPadPx'], exports.KEYBOARD_DEFAULTS.safetyPadPx),
+        },
+    };
+}
+let cached;
+/** The row config, fetched at most once per page load. Never rejects. */
+function clientConfig() {
+    cached ??= fetch(exports.CLIENT_CONFIG_ROUTE, { cache: 'no-store' })
+        .then((res) => (res.ok ? res.json() : undefined))
+        .catch(() => undefined)
+        .then(parseClientConfig);
+    return cached;
 }
-`;
 };
-__modules["styles/chips.css.js"] = function (require, module, exports) {
+__modules["locales.js"] = function (require, module, exports) {
 "use strict";
-// chips — S5 (2026-08-17): the home-screen plugin-entry chips row, its
-// customize sheet, the settings gear button, and the settings/usage-stats
-// dialog portal fix. Appended LAST in index.ts (after home.css.ts) so its
-// `display` overrides win any tie against the phone shell's blanket
-// `[data-mobile-nav="frame"] > :first-child { display: none }` rule — though
-// the extra `:has()` clause already outranks it on specificity alone.
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.CHIPS_CSS = void 0;
-exports.CHIPS_CSS = `/* ---------- chips row + settings entry (S5) ---------- */
-
-@media (max-width: 767px) {
-  /* --- settings dialog / usage-stats panel / scheduled-tasks dialog portal fix ---
-     dsh-client-ui-settings-general's SettingsRoot (trigger button +
-     position:fixed;z-index:1000 modal), dsh-usage-stats' sidebar-footer
-     badge (position:fixed panel), and @opendsh/dsh-plugin-scheduled-tasks'
-     "定时任务" trigger (position:fixed;z-index:120 \`.dshst-overlay\`,
-     verified against 0.2.0 — real-device report 2026-08-17: chip click
-     produced no visible window) all mount as PLAIN CHILDREN of the sidebar
-     tree — not a React portal to document.body — inside
-     sidebar.settings / sidebar.footer.action
-     (dsh-client-ui-sidebar's SidebarRoot: footArea > settingsArea /
-     footerActions). home.css.ts sets the sidebar ROOT
-     (\`[data-mobile-nav="frame"] > :first-child\`) to display:none on the
-     phone breakpoint (the app shell replaced the drawer) — and display:none
-     removes the WHOLE subtree from the render tree, including
-     position:fixed descendants, which cannot escape it the way they escape
-     a merely-offscreen or opacity:0 ancestor. A \`.click()\` on the (still
-     DOM-present) hidden trigger still flips its component-local \`open\`
-     state and mounts the aria-modal dialog (synthetic dispatch bypasses
-     hit-testing — S2.1 precedent), but nothing paints without this fix.
-
-     Un-hiding the WHOLE sidebar would surface the session tree / new-session
-     button underneath the dialog, so this is scoped to exactly the sidebar
-     root plus its OWN direct children that are not on the path to
-     footArea: display:contents on the root removes its own box (no
-     duplicate page background/padding, no grid-column reflow) while
-     letting footArea/footerActions/settingsArea resume their OWN official
-     (non-none) display — logoRow / newSession / regionArea are hidden
-     explicitly instead. :has() matches against the DOM tree regardless of
-     the scope element's own computed display, so this reads correctly even
-     though the whole subtree started at display:none (same precedent as
-     every other :has()-gated rule in this stylesheet, e.g. the settings
-     sheet adaptation below, which depends on exactly this becoming
-     visible).
-
-     \`:first-child\` is a layout-column WRAPPER
-     (\`pI_x6G_sidebarCol\`, dsh-client-ui-layout's AppFrame grid cell), not
-     SidebarRoot's own div — SidebarRoot (\`hHd-Xa_root\`) sits one more empty
-     unstyled div below it (measured 2026-08-17: sidebarCol > div (no
-     class) > div.hHd-Xa_root > logoRow/newSession/regionArea/footArea).
-     display:contents on sidebarCol lets that whole chain resume its own
-     official (non-none) display with no other rule needed, but the
-     "hide the other three" selectors below must therefore be DESCENDANT
-     (unscoped depth), not direct-child \`>\`, or they silently match
-     nothing — confirmed live: an earlier \`>\`-only version left
-     logoRow/newSession/regionArea at \`display: flex\`, which is only
-     hidden from view by being fully underneath the usage-stats panel's
-     opaque body, not by this rule. */
-  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) {
-    display: contents !important;
-  }
-  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) [class$="_logoRow"],
-  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) [class$="_newSession"],
-  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) [class$="_regionArea"] {
-    display: none !important;
-  }
-
-  /* Home-top settings gear: 44pt touch target, pushed to the row's end by
-     its own auto margin (home-top itself stays a plain flex row). */
-  [data-mobile-nav="home-settings"] {
-    flex: none;
-    display: inline-flex;
-    align-items: center;
-    justify-content: center;
-    width: 44px;
-    height: 44px;
-    margin-left: auto;
-    padding: 0;
-    border: none;
-    background: transparent;
-    color: var(--dsw-alias-label-secondary, inherit);
-    cursor: pointer;
-    touch-action: manipulation;
-    -webkit-tap-highlight-color: transparent;
-  }
-  [data-mobile-nav="home-settings"]:active {
-    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
-    border-radius: 50%;
-  }
-
-  /* Plugin-entry chips row: one horizontally-scrolling line of 34px pills
-     between the workspace title and the session list (prototype spec).
-     Scrollbar hidden on BOTH engines (2026-08-18 user decision): iOS
-     overlay scrollbars never showed anyway, but desktop browsers painted a
-     permanent 2px strip under the pills. This revisits the AGENTS.md
-     "silently cut off the last tab" lesson deliberately — with 4+ chips the
-     row now always overflows mid-chip (a partially visible pill is the
-     scroll affordance), unlike the early incident where the chips fit
-     flush and the hidden overflow was undiscoverable. */
-  [data-mobile-nav="chip-row"] {
-    flex: 0 0 auto;
-    display: flex;
-    align-items: center;
-    gap: 8px;
-    padding: 0 16px 10px;
-    overflow-x: auto;
-    overscroll-behavior: contain;
-    -webkit-overflow-scrolling: touch;
-    scrollbar-width: none;
-  }
-  [data-mobile-nav="chip-row"]::-webkit-scrollbar {
-    display: none;
-  }
-  [data-mobile-nav="chip"],
-  [data-mobile-nav="chip-more"] {
-    flex: none;
-    display: inline-flex;
-    align-items: center;
-    gap: 6px;
-    height: 34px;
-    padding: 0 14px;
-    border: none;
-    border-radius: 17px;
-    /* Same surface as the list rows: the home page is bg-base since the
-       2026-08-20 swap (see home.css.ts), so a bg-base chip would disappear
-       into it. */
-    background: var(--dsw-specific-sidebar-fill, #f5f5f5);
-    color: var(--dsw-alias-label-primary, inherit);
-    font-family: inherit;
-    font-size: 13px;
-    font-weight: 500;
-    white-space: nowrap;
-    cursor: pointer;
-    touch-action: manipulation;
-    -webkit-tap-highlight-color: transparent;
-    box-shadow: 0 1px 3px rgba(0, 0, 0, .06);
-  }
-  [data-mobile-nav="chip-more"] {
-    padding: 0 9px;
-  }
-  [data-mobile-nav="chip"]:active,
-  [data-mobile-nav="chip-more"]:active {
-    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
-  }
-
-  /* Harvested chip icon (S5.1): the cloned <svg> keeps whatever width/height
-     the source plugin gave it (18px for the one verified live example) —
-     force it down to the same 16px box every hand-registered chip icon
-     uses, CSS wins over the presentational SVG attributes. */
-  [data-mobile-nav="chip-harvest-icon"] {
-    display: inline-flex;
-    flex: none;
-  }
-  [data-mobile-nav="chip-harvest-icon"] svg {
-    display: block;
-    width: 16px;
-    height: 16px;
-  }
-
-  /* Customize sheet: toggle rows inside the SAME home-sheet-layer/mask/sheet
-     chrome the workspace switcher declares in home.css.ts — S6's
-     drag-to-close and mask-click-close bind to
-     \`[data-mobile-nav="home-sheet"]\` generically (effects/gestures.ts), so
-     this second use of the marker needs no new gesture wiring. */
-  [data-mobile-nav="chip-toggle-row"] {
-    display: flex;
-    align-items: center;
-    gap: 10px;
-    width: 100%;
-    /* Real-device fix: without border-box this row's used width is
-       100% (of the sheet's own already-padded content box) PLUS the
-       12px+12px padding below, overflowing the sheet by 24px and
-       shoving the flex:none toggle off its right edge (2026-08-17
-       report: "开关跑到屏幕外"). home-sheet-item next door in
-       home.css.ts has the identical width:100%+padding shape and the
-       same latent bug, just with no trailing element to visibly clip. */
-    box-sizing: border-box;
-    min-height: 48px;
-    padding: 0 12px;
-    color: inherit;
-  }
-  [data-mobile-nav="chip-toggle-label"] {
-    flex: 1 1 auto;
-    min-width: 0;
-    font-size: 15px;
-    overflow: hidden;
-    text-overflow: ellipsis;
-    white-space: nowrap;
-  }
-  [data-mobile-nav="chip-toggle"] {
-    flex: none;
-    position: relative;
-    width: 42px;
-    height: 26px;
-    border: none;
-    border-radius: 13px;
-    background: var(--dsw-alias-border-l2, rgba(0, 0, 0, .16));
-    cursor: pointer;
-    touch-action: manipulation;
-    -webkit-tap-highlight-color: transparent;
-    transition: background .15s var(--ds-ease-in-out, ease-in-out);
-  }
-  [data-mobile-nav="chip-toggle"]::after {
-    content: '';
-    position: absolute;
-    top: 2px;
-    left: 2px;
-    width: 22px;
-    height: 22px;
-    border-radius: 50%;
-    background: #ffffff;
-    box-shadow: 0 1px 3px rgba(0, 0, 0, .3);
-    transition: transform .15s var(--ds-ease-in-out, ease-in-out);
-  }
-  [data-mobile-nav="chip-toggle"][aria-checked="true"] {
-    background: var(--dsw-alias-button-primary-fill, #1a1a1a);
-  }
-  [data-mobile-nav="chip-toggle"][aria-checked="true"]::after {
-    transform: translateX(16px);
-  }
-  @media (prefers-reduced-motion: reduce) {
-    [data-mobile-nav="chip-toggle"],
-    [data-mobile-nav="chip-toggle"]::after {
-      transition: none !important;
-    }
-  }
-}
-`;
+exports.en = exports.zh = exports.NS = void 0;
+/** `mobileNav` namespace dictionaries: drawer controls. */
+exports.NS = 'mobileNav';
+/** Simplified Chinese dictionary (the key-set source of truth). */
+exports.zh = {
+    'open': '打开目录',
+    'close': '收起目录',
+    'backdrop': '点击关闭目录',
+    'sessionLog': '导出会话日志',
+    'files': '文件浏览',
+    'previewFullscreen': '全屏预览',
+    'previewExitFullscreen': '退出全屏',
+    'allWorkspaces': '全部',
+    'switchWorkspace': '切换工作区',
+    'newSession': '新建会话',
+    'noSessions': '还没有会话，点右下角加号开始',
+    'homeStatusOngoing': '运行中',
+    'homeStatusWarning': '待处理',
+    'homeStatusDone': '已完成',
+    'backToList': '返回会话列表',
+    'sessionInfo': '会话信息',
+    'workbench': '工作台',
+    'workbenchClose': '关闭工作台',
+    'switchView': '切换视图',
+    'attach': '添加附件',
+    'attachBusy': '上传中…',
+    'attachFailed': '上传失败，点按重试',
+    'attachRemove': '移除附件 {name}',
+    'infoClose': '关闭',
+    'infoMode': '模式',
+    'infoCwdFallback': '未知目录',
+    'infoSubagents': '{count} 个子代理',
+    'infoJobs': '{count} 个后台任务',
+    'activityOpen': '查看子代理与后台任务',
+    'infoStatTurns': '轮次',
+    'infoStatSteps': '步骤',
+    'infoStatTtft': '首字延迟',
+    'infoStatLlm': '模型耗时',
+    'infoStatTool': '工具耗时',
+    'infoStatCacheHit': '缓存命中',
+    'infoTokenFlow': 'Token {io}',
+    'infoExport': '导出日志',
+    'infoRename': '重命名',
+    'infoRenamePrompt': '会话新名称',
+    'infoFork': 'Fork 会话',
+    'infoArchive': '归档',
+    'infoArchiveConfirm': '归档后将从会话列表隐藏，确定继续？',
+    'infoActionError': '操作失败：{message}',
+    'turnFold': '过程 · {count} 步',
+    'turnFoldRunning': '进行中 · {count} 步',
+    'settings': '设置',
+    'chipTaskboard': '任务看板',
+    'chipSsh': 'SSH',
+    'chipUsage': '用量',
+    'chipCustomize': '自定义入口',
 };
-__modules["styles/content.css.js"] = function (require, module, exports) {
+/** English dictionary, key-identical to the Chinese source of truth. */
+exports.en = {
+    'open': 'Open directory',
+    'close': 'Close directory',
+    'backdrop': 'Click to close directory',
+    'sessionLog': 'Session log',
+    'files': 'Files',
+    'previewFullscreen': 'Fullscreen preview',
+    'previewExitFullscreen': 'Exit fullscreen',
+    'allWorkspaces': 'All',
+    'switchWorkspace': 'Switch workspace',
+    'newSession': 'New session',
+    'noSessions': 'No sessions yet — tap + to start one',
+    'homeStatusOngoing': 'Running',
+    'homeStatusWarning': 'Needs attention',
+    'homeStatusDone': 'Done',
+    'backToList': 'Back to sessions',
+    'sessionInfo': 'Session info',
+    'workbench': 'Workbench',
+    'workbenchClose': 'Close workbench',
+    'switchView': 'Switch view',
+    'attach': 'Add attachment',
+    'attachBusy': 'Uploading…',
+    'attachFailed': 'Upload failed — tap to retry',
+    'attachRemove': 'Remove attachment {name}',
+    'infoClose': 'Close',
+    'infoMode': 'Mode',
+    'infoCwdFallback': 'Unknown directory',
+    'infoSubagents': '{count} subagents',
+    'infoJobs': '{count} background tasks',
+    'activityOpen': 'View subagents and background tasks',
+    'infoStatTurns': 'Turns',
+    'infoStatSteps': 'Steps',
+    'infoStatTtft': 'TTFT',
+    'infoStatLlm': 'LLM time',
+    'infoStatTool': 'Tool time',
+    'infoStatCacheHit': 'Cache hit',
+    'infoTokenFlow': 'Tokens {io}',
+    'infoExport': 'Export log',
+    'infoRename': 'Rename',
+    'infoRenamePrompt': 'New session name',
+    'infoFork': 'Fork session',
+    'infoArchive': 'Archive',
+    'infoArchiveConfirm': 'Archiving hides this session from the list. Continue?',
+    'infoActionError': 'Action failed: {message}',
+    'turnFold': 'Process · {count} steps',
+    'turnFoldRunning': 'Working · {count} steps',
+    'settings': 'Settings',
+    'chipTaskboard': 'Task board',
+    'chipSsh': 'SSH',
+    'chipUsage': 'Usage',
+    'chipCustomize': 'Customize shortcuts',
+};
+};
+__modules["effects/turn-fold.js"] = function (require, module, exports) {
 "use strict";
-// content — chat markdown readability on phones (2026-08-18). Shares no
-// selector with any other file; appended last in styles/index.ts.
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.CONTENT_CSS = void 0;
-exports.CONTENT_CSS = `/* ---------- chat markdown content (< 768px) ---------- */
-
-@media (max-width: 767px) {
-  /* Inline code: upstream renders it display:inline-flex — an atomic inline
-     box that can never wrap across lines, so one long code span walks off
-     the right edge of the screen. Plain inline keeps the background pill
-     per line fragment and lets long tokens break anywhere. Deliberately
-     unscoped (any :not(pre) > code, not just the _markdown_ module):
-     inline code also renders outside that container (user bubbles,
-     reasoning rows), and on a phone there is no width at which an
-     unwrappable inline box is right. !important beats the upstream
-     display:inline-flex on specificity ties. */
-  :not(pre) > code {
-    display: inline !important;
-    overflow-wrap: anywhere;
-    /* iOS WebKit: overflow-wrap alone still failed to break long tokens in
-       inline code on a real iPhone (screenshot-verified 2026-08-18, li >
-       code path case) while desktop Chromium broke them fine. break-all is
-       the everywhere-supported hammer; acceptable for code pills. */
-    word-break: break-all;
-  }
-  /* Belt-and-suspenders for engines that compute soft-wrap opportunities
-     from the block container rather than the inline itself (historical
-     WebKit behavior): inherit anywhere through the whole transcript so the
-     block side agrees. Prose is untouched until something would overflow;
-     the table is already pinned wide by min-width: max-content below. */
-  [data-chat-flow],
-  [class*="_markdown_"] {
-    overflow-wrap: anywhere;
-  }
-
-  /* Transcript density (2026-08-20): the desktop prose rhythm is 28px of
-     leading on 15px text — a 1.87 ratio that reads generously on a wide
-     column but wastes a phone screen, where the same paragraph is three
-     times as many lines. Unitless 1.65 so nested blocks (code, quotes,
-     lists) recompute from their OWN font-size instead of inheriting a fixed
-     28px that is far too loose for 12-13px chrome text. 1.65 is the floor I
-     am willing to go to for mixed CJK/Latin: the glyphs are full-height with
-     no descender relief, so tighter starts to look stacked. Phone only —
-     the desktop column keeps the official rhythm. */
-  [class*="_markdown_"] {
-    line-height: 1.65;
-  }
-  /* Paragraph rhythm. Each paragraph is its own markdown block and the
-     separation comes from the flex container's row-gap, not from margins —
-     at the stock 16px the paragraph baseline step was 40.75px against a
-     24.75px line step, i.e. 1.65x, which is what reads as airy. 12px brings
-     the step to ~36.75px: still clearly more than one line so paragraphs
-     never run together, but noticeably denser. Scoped by :has() to
-     containers that actually hold prose blocks, so tool cards and other
-     flex bodies with the same hashed suffix keep their own spacing. */
-  [data-phase] [class$="_body"]:has(> [class*="_markdown_"]) {
-    row-gap: 12px !important;
-  }
-
-  /* Markdown tables: the official _tableScroll_ wrapper is already a
-     horizontal scroll viewport around a width:max-content table, but its
-     cells are capped at min(30vw, 320px) — barely 120px on a phone, which
-     crushes every column into a vertical word-stack. Let columns size to
-     their content instead and read the overflow by scrolling the wrapper.
-     480px (not a vw cap — 85vw was ~320px on a 375px phone and still
-     wrapped mid-length cells) keeps typical cells on one line; only truly
-     prose-heavy cells wrap, instead of dragging the table kilometers
-     wide. */
-  [class*="_tableScroll_"] th,
-  [class*="_tableScroll_"] td {
-    max-width: 480px !important;
-  }
-
-  /* iOS WebKit fallback: upstream's own table { width: max-content } is what
-     keeps the table at its natural width inside the scroll wrapper, but
-     WebKit's max-content support on table boxes is incomplete — on a real
-     iPhone the table fell back to shrink-to-fit and every column got
-     crushed to its min-width (the "ra/nk" vertical-word-stack screenshot,
-     2026-08-18). Redeclare the natural-width intent with both width and
-     min-width so whichever keyword the engine honors wins; the wrapper
-     already scrolls the overflow. */
-  [class*="_tableScroll_"] table {
-    width: max-content !important;
-    min-width: max-content !important;
-    max-width: none !important;
-  }
-
-  /* Turn-tail metadata (2026-08-18): the timing stats ("18:06 · 用时 29秒 ·
-     首 token 0.9秒 · 163 tok/s") are desktop-hover-revealed (official
-     [data-time-hover-root] gate holds them at opacity 0 until :hover /
-     :focus-within) — a phone never hovers, so they were simply invisible;
-     and even ignoring that, the row is nowrap + overflow:hidden (plus this
-     plugin's own legacy ellipsis clamp in layout.css.ts), which clipped the
-     text. On phones: always visible, own full-width line under the action
-     icons, wrapping freely, one type size down. !important + the extra
-     [class$="_actions"] hop out-specifies both upstream and layout.css.ts. */
-  /* Pin the tail row's width chain before allowing wrap: with wrap enabled
-     the row's intrinsic (shrink-to-fit) width collapses to its widest
-     single icon, taking the whole tail down to ~16px. */
-  [data-chat-flow-kind="turn-tail"] [class$="_root"],
-  [data-chat-flow-kind="turn-tail"] [class$="_actions"] {
-    width: 100%;
-  }
-  [data-chat-flow-kind="turn-tail"] [class$="_actions"] {
-    flex-wrap: wrap;
-    row-gap: 2px;
-  }
-  /* Wide companion to the rule below: mirrors the upstream hover-gate
-     selector shape directly, with no assumptions about the tail's DOM
-     structure, so the stats can't stay invisible even if the phone's tail
-     renders differently than desktop. */
-  [data-time-hover-root] [class$="_timeEnd"],
-  [data-time-hover-root] [class$="_timeStart"] {
-    opacity: 1 !important;
-    transition: none !important;
-  }
-  [data-chat-flow-kind="turn-tail"] [class$="_actions"] [class$="_timeEnd"] {
-    opacity: 1 !important;
-    flex-basis: 100% !important;
-    white-space: normal !important;
-    overflow: visible !important;
-    text-overflow: clip !important;
-    padding-left: 0 !important;
-    font-size: 12px;
-    line-height: 18px;
-  }
+exports.OPEN = exports.THINK = exports.PROCESS_KINDS = void 0;
+exports.installTurnFold = installTurnFold;
+const client_config_ts_1 = require("./client-config.js");
+const locales_ts_1 = require("./locales.js");
+/** Phone breakpoint — same query every phone-only effect in this plugin uses. */
+const PHONE_QUERY = '(max-width: 767px)';
+/** Desktop fold (issue #2) is switched on either way:
+ * - plugin row `config.turnFoldDesktop: true` — the host republishes it at
+ *   {@link CLIENT_CONFIG_ROUTE} because the client bundle ships statically
+ *   and never sees the row config;
+ * - per-browser override, same convention as the debug flag: a URL param
+ *   writes localStorage (`?mobile-nav-turn-fold=1` opts this browser in,
+ *   `=0` opts back out). */
+const DESKTOP_KEY = 'dsh-mobile-nav.turn-fold-desktop';
+const DESKTOP_PARAM = 'mobile-nav-turn-fold';
+/** Root attribute the stylesheet keys the width-independent rules on. */
+const DESKTOP_ATTR = 'data-mnav-desktop-fold';
+/** Read (and, when the URL param is present, persist) the per-browser opt-in. */
+function desktopOptIn() {
+    const param = new URLSearchParams(location.search).get(DESKTOP_PARAM);
+    if (param === '1')
+        localStorage.setItem(DESKTOP_KEY, '1');
+    else if (param === '0')
+        localStorage.removeItem(DESKTOP_KEY);
+    return localStorage.getItem(DESKTOP_KEY) === '1';
 }
-`;
-};
-__modules["styles/index.js"] = function (require, module, exports) {
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.MOBILE_CSS = void 0;
-const base_css_ts_1 = require("./styles/base.css.js");
-const layout_css_ts_1 = require("./styles/layout.css.js");
-const compat_css_ts_1 = require("./styles/compat.css.js");
-const misc_css_ts_1 = require("./styles/misc.css.js");
-const home_css_ts_1 = require("./styles/home.css.js");
-const header_css_ts_1 = require("./styles/header.css.js");
-const composer_css_ts_1 = require("./styles/composer.css.js");
-const info_css_ts_1 = require("./styles/info.css.js");
-const turn_fold_css_ts_1 = require("./styles/turn-fold.css.js");
-const chips_css_ts_1 = require("./styles/chips.css.js");
-const content_css_ts_1 = require("./styles/content.css.js");
+/** True when the plugin row asks for desktop fold; false on any failure —
+ * the shared reader in client-config.ts already swallows those. */
+async function desktopConfigured() {
+    return (await (0, client_config_ts_1.clientConfig)()).turnFoldDesktop;
+}
+/** ChatView's flow column (dsh-client-ui-conversation lib/client.js:5512).
+ * Trajectory and every other view render their own tree and never carry this
+ * marker, so scoping here is what keeps this effect Chat-only. */
+const FLOW = '[data-chat-flow]';
+/** Marker + selector of the injected summary row. */
+const CHIP = 'turn-fold';
+const CHIP_SELECTOR = '[data-mobile-nav="turn-fold"]';
+/** Whole-row node kinds that are turn *process*, not conversation content.
+ * Keys are ChatNodeSeat's own `data-chat-flow-kind` dispatch values
+ * (registerChatNodeRenderers, lib/client.js:9322): tool calls, injected
+ * context rows, and slash-command rows. Everything else stays visible —
+ * `user`/`steering` (the question), `assistant-step` (the prose, folded
+ * per-block below), `turn-tail` (the footer with its actions), and the
+ * error notices `turn-error` / `turn-max-tokens` / `model-retry`, which are
+ * exactly what a reader must not have to hunt for. */
+exports.PROCESS_KINDS = ['context', 'tool-call', 'command'];
+const PROCESS_KIND_SET = new Set(exports.PROCESS_KINDS);
+/** Node kinds that open a new turn group. */
+const TURN_HEAD_KINDS = new Set(['user', 'steering']);
+/** ReasoningRow's own marker (lib/client.js:8966) — the Think disclosure
+ * rendered inside an assistant-step row, beside that step's prose. */
+exports.THINK = '[data-variant="think"]';
+/** Attribute the phone stylesheet turns into `display: none`. Still written
+ * per element for the one case the stylesheet cannot express on its own: an
+ * assistant-step row whose entire body is reasoning, which has to go as a
+ * whole row (see {@link foldsWholeRow}). */
+const FOLD = 'data-mnav-fold';
+/** Per-item override written while its turn is expanded. */
+exports.OPEN = 'data-mnav-fold-open';
+/** Root attribute written for as long as this effect is attached — i.e. for
+ * exactly the widths where the fold is live. The stylesheet keys its
+ * born-folded rules on it, which is what makes a newly inserted tool call
+ * hidden at its FIRST paint instead of after the next rescan (the "row
+ * flashes in, then folds away" report, 2026-08-22); it also keeps the
+ * stylesheet a no-op — content visible — if this effect never runs. */
+const ACTIVE_ATTR = 'data-mnav-fold-on';
 /**
- * All mobile styles, concatenated in the exact order of the original
- * single-file stylesheet (base → layout → compat → misc, where misc keeps
- * composer → tablet → desktop), followed by the phone app shell (home), the
- * session-header reflow (header), the composer reflow (composer), and the
- * session-info sheet (info, which must come last of all: it re-shows a
- * header.utilities child header.css.ts hides by default, so its rule has to
- * win that tie too), the turn-process fold (turn-fold, S8, which shares no
- * selector with any of them), and finally the chips row / settings entry /
- * portal fix (chips, S5) — all appended in this order so their <768px rules
- * win ties against the shared <=1023px block, then the chat markdown
- * readability overrides (content, which shares no selector with any of
- * them). Injected as ONE <style data-plugin> tag — do not reorder.
+ * True when the reasoning rows are the ONLY thing this row renders, so the
+ * whole flow item has to go: the flow column is `display: flex` with
+ * `gap: 16px`, and an emptied-out flex item still claims its gap — the
+ * reader would see the folded steps as a column of blank bands.
+ * Structural test, no class names: every ancestor from the reasoning rows'
+ * shared parent up to the flow item must be an only child.
  */
-exports.MOBILE_CSS = [base_css_ts_1.BASE_CSS, layout_css_ts_1.LAYOUT_CSS, compat_css_ts_1.COMPAT_CSS, misc_css_ts_1.MISC_CSS, home_css_ts_1.HOME_CSS, header_css_ts_1.HEADER_CSS, composer_css_ts_1.COMPOSER_CSS, info_css_ts_1.INFO_CSS, turn_fold_css_ts_1.TURN_FOLD_CSS, chips_css_ts_1.CHIPS_CSS, content_css_ts_1.CONTENT_CSS].join('\n');
-};
-__modules["debug.js"] = function (require, module, exports) {
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.installDebugBadge = installDebugBadge;
+function foldsWholeRow(row, thinks) {
+    const first = thinks[0];
+    if (first === undefined)
+        return false;
+    const body = first.parentElement;
+    if (body === null || body.childElementCount !== thinks.length)
+        return false;
+    let node = body;
+    while (node !== row) {
+        const parent = node.parentElement;
+        if (parent === null)
+            return false;
+        if (parent.childElementCount !== 1)
+            return false;
+        node = parent;
+    }
+    return true;
+}
+/** The process items one flow row contributes: the row itself, its reasoning
+ * rows, or nothing at all. */
+function processItems(row) {
+    const kind = row.getAttribute('data-chat-flow-kind');
+    if (kind === null)
+        return [];
+    if (PROCESS_KIND_SET.has(kind))
+        return [row];
+    if (kind !== 'assistant-step')
+        return [];
+    const thinks = [...row.querySelectorAll(exports.THINK)];
+    if (thinks.length === 0)
+        return [];
+    return foldsWholeRow(row, thinks) ? [row] : thinks;
+}
 /**
- * Debug badge — ?mobile-nav-debug=1
- * Renders a live state overlay (URL, viewport, media queries, shell chrome,
- * aionui columns, genui cards, captured errors) so a phone-side repro can be
- * diagnosed without guessing. No-op unless the query param is present.
+ * The summary row sitting immediately before `anchor`, created if absent.
+ * Idempotent by construction — React re-rendering the flow either leaves our
+ * button where it is (it only ever inserts and removes its OWN nodes) or
+ * drops it, and the next rescan puts it back.
  */
-function installDebugBadge(ctx) {
-    /**
-     * Fake safe-area inset — ?mobile-nav-inset=54 or ?mobile-nav-inset=54,34
-     * env(safe-area-inset-*) is hard 0 on every desktop browser (CDP included),
-     * so notch bugs are invisible until a real phone loads the page — the S2.1
-     * hotfix exists because of exactly that. Overriding --mnav-sat / --mnav-sab
-     * (see styles/base.css.ts) on the root element reproduces a notch anywhere.
-     * No param = the variables keep their env() values = zero behaviour change.
-     *
-     * One value fakes the TOP inset only (the historic behaviour — every S1-S3
-     * verification recipe passes `=54`, and they must keep meaning what they
-     * did). A second, comma-separated value fakes the BOTTOM inset too:
-     * `=54,34` is the iPhone notch + home-indicator pair. The bottom half was
-     * added in S4.1 because the home-bar padding it guards (composer clearance
-     * over the indicator) is otherwise untestable off-device for exactly the
-     * same reason the top half exists.
-     */
-    ctx.effect(() => {
-        const raw = new URLSearchParams(location.search).get('mobile-nav-inset');
-        if (raw === null)
-            return () => { };
-        const [topRaw, bottomRaw] = raw.split(',');
-        const top = Number(topRaw);
-        if (!Number.isFinite(top))
-            return () => { };
-        const root = document.documentElement;
-        root.style.setProperty('--mnav-sat', `${top}px`);
-        const bottom = bottomRaw === undefined ? Number.NaN : Number(bottomRaw);
-        if (Number.isFinite(bottom))
-            root.style.setProperty('--mnav-sab', `${bottom}px`);
-        return () => {
-            root.style.removeProperty('--mnav-sat');
-            root.style.removeProperty('--mnav-sab');
-        };
-    }, 'dsh-mobile-nav: fake safe-area inset');
-    const DEBUG_KEY = 'dsh-mobile-nav.debug';
-    /**
-     * No-URL toggle — 5 quick taps on the home screen's top bar.
-     * A standalone PWA has no address bar, and the paired-device cookie lives
-     * in the PWA's own jar (Safari hits the pairing wall instead), so the
-     * ?mobile-nav-debug=1 param is unreachable exactly where the badge is
-     * needed most.
-     *
-     * The target is deliberately NOT [data-mobile-nav="ws-switch"] any more:
-     * that button opens the workspace sheet on the FIRST tap, so taps 2..5
-     * land on the sheet backdrop, `closest()` misses, and the counter never
-     * reaches five — the original binding only ever fired by luck, and it left
-     * a user stuck inside debug mode with no way back out. The logo img has no
-     * click handler at all; the home-top container minus the switch button is
-     * the fallback for when the icon 404s and the img is not rendered.
-     */
+function chipBefore(anchor) {
+    const previous = anchor.previousElementSibling;
+    if (previous instanceof HTMLElement && previous.dataset['mobileNav'] === CHIP)
+        return previous;
+    const parent = anchor.parentElement;
+    if (parent === null)
+        return null;
+    const chip = document.createElement('button');
+    chip.type = 'button';
+    chip.dataset['mobileNav'] = CHIP;
+    parent.insertBefore(chip, anchor);
+    return chip;
+}
+/** Split the flow column into turns: a group runs from one user/steering row
+ * up to (not including) the next. Rows that precede the first user row —
+ * a turn whose question has not been paged in yet — form a leading group of
+ * their own, so their process never becomes unreachable. */
+function groupsOf(flow) {
+    const groups = [];
+    let current;
+    for (const row of flow.children) {
+        const kind = row.getAttribute('data-chat-flow-kind');
+        if (kind === null)
+            continue;
+        if (current === undefined || TURN_HEAD_KINDS.has(kind)) {
+            current = { key: row.getAttribute('data-chat-flow-key') ?? `pos${groups.length}`, items: [] };
+            groups.push(current);
+        }
+        current.items.push(...processItems(row));
+    }
+    return groups;
+}
+/**
+ * S8 — collapse a turn's process into one summary row (< 768px by default;
+ * every width when the plugin row sets `config.turnFoldDesktop` or a browser
+ * opts itself in via `?mobile-nav-turn-fold=1`).
+ *
+ * Route taken: DOM marking, not the `conversation.chat.node` keyed slot.
+ * That slot dispatches on node kind and a second registration at a key
+ * SHADOWS the official renderer (dsh-client-ui-slots index.d.ts:542 — the
+ * cell's lowest-priority live entry renders, there is no wrapping form and
+ * no `children` handle to the shadowed component). Taking `tool-call` would
+ * mean re-implementing every tool's presentation, its `t` seat comes from
+ * the entry's own declared locale namespace and its services from the
+ * registrant's own inject face — neither is reachable from here — and the
+ * registration is global, so the desktop no-op would be gone too.
+ *
+ * The DOM route needs no class names: ChatNodeSeat stamps every row with
+ * `data-chat-flow-kind` / `data-chat-flow-key` (lib/client.js:5228) and
+ * ReasoningRow stamps `data-variant="think"` — turn grouping is pure
+ * structure (the run of rows following one `user` row), never text.
+ *
+ * ponytail: one rAF-coalesced full rescan per DOM mutation batch, O(rows).
+ * If a very long session ever makes streaming feel heavy, narrow the
+ * observer to the flow column's own childList and diff instead.
+ */
+function installTurnFold(ctx) {
     ctx.effect(() => {
-        let taps = 0;
-        let firstTap = 0;
-        const onTap = (event) => {
-            if (!(event.target instanceof Element))
-                return;
-            const inTopBar = event.target.closest('[data-mobile-nav="home-logo"]') !== null
-                || (event.target.closest('[data-mobile-nav="home-top"]') !== null
-                    && event.target.closest('[data-mobile-nav="ws-switch"]') === null);
-            if (!inTopBar)
+        const narrow = window.matchMedia(PHONE_QUERY);
+        const t = ctx.locale.bind(locales_ts_1.NS);
+        /** Turns the reader opened. Deliberately not persisted (spec: a reload
+         * returns to the default folded state). */
+        const expanded = new Set();
+        let observer = null;
+        let frame = 0;
+        const label = (chip, count, running) => {
+            const next = running ? t('turnFoldRunning', { count }) : t('turnFold', { count });
+            if (chip.textContent !== next)
+                chip.textContent = next;
+        };
+        const scan = () => {
+            const flow = document.querySelector(FLOW);
+            if (flow === null)
                 return;
-            const now = Date.now();
-            if (now - firstTap > 2500) {
-                taps = 0;
-                firstTap = now;
-            }
-            taps += 1;
-            if (taps >= 5) {
-                if (localStorage.getItem(DEBUG_KEY) === '1')
-                    localStorage.removeItem(DEBUG_KEY);
+            // TurnStatus, ChatView's own running banner — present only while the
+            // last turn is still working (lib/client.js:5548).
+            const running = flow.querySelector(':scope > [role="status"]') !== null;
+            const groups = groupsOf(flow);
+            const live = new Set();
+            const liveItems = new Set();
+            groups.forEach((group, index) => {
+                if (group.items.length === 0)
+                    return;
+                const open = expanded.has(group.key);
+                for (const item of group.items) {
+                    liveItems.add(item);
+                    item.setAttribute(FOLD, '');
+                    if (open)
+                        item.setAttribute(exports.OPEN, '');
+                    else
+                        item.removeAttribute(exports.OPEN);
+                }
+                const first = group.items[0];
+                if (first === undefined)
+                    return;
+                const anchor = first.closest('[data-chat-flow-key]') ?? first;
+                const chip = chipBefore(anchor);
+                if (chip === null)
+                    return;
+                chip.dataset['foldGroup'] = group.key;
+                chip.setAttribute('aria-expanded', open ? 'true' : 'false');
+                if (open)
+                    chip.dataset['open'] = '';
                 else
-                    localStorage.setItem(DEBUG_KEY, '1');
-                location.reload();
+                    delete chip.dataset['open'];
+                const groupRunning = running && index === groups.length - 1;
+                if (groupRunning)
+                    chip.dataset['running'] = '';
+                else
+                    delete chip.dataset['running'];
+                label(chip, group.items.length, groupRunning);
+                live.add(group.key);
+            });
+            for (const chip of flow.querySelectorAll(CHIP_SELECTOR)) {
+                const key = chip.dataset['foldGroup'];
+                if (key === undefined || !live.has(key))
+                    chip.remove();
+            }
+            // Unmark elements that stopped being process items. Without this, an
+            // assistant-step row folded whole while it streamed ONLY reasoning kept
+            // its row-level fold after prose started arriving in the same DOM node
+            // (React updates the row in place), hiding the streaming reply until a
+            // completion re-render rebuilt the row — the "reply only appears when
+            // the turn finishes" phone bug (2026-08-18).
+            for (const stale of flow.querySelectorAll(`[${FOLD}]`)) {
+                if (liveItems.has(stale))
+                    continue;
+                stale.removeAttribute(FOLD);
+                stale.removeAttribute(exports.OPEN);
             }
         };
-        document.addEventListener('click', onTap, true);
-        return () => document.removeEventListener('click', onTap, true);
-    }, 'dsh-mobile-nav: debug badge tap toggle');
-    ctx.effect(() => {
-        const enabled = new URLSearchParams(location.search).has('mobile-nav-debug')
-            || localStorage.getItem('dsh-mobile-nav.debug') === '1';
-        if (!enabled)
-            return () => { };
-        const errors = [];
-        const onError = (event) => errors.push(`ERR ${event.message.slice(0, 120)}`);
-        const onRejection = (event) => errors.push(`REJ ${String(event.reason).slice(0, 120)}`);
-        window.addEventListener('error', onError);
-        window.addEventListener('unhandledrejection', onRejection);
-        /* Probe element: reads the REAL env(safe-area-inset-*) as computed padding
-           — the --mnav-* vars can be faked by the inset param, this cannot. */
-        const probe = document.createElement('div');
-        probe.style.cssText =
-            'position:fixed;visibility:hidden;pointer-events:none;' +
-                'padding-top:env(safe-area-inset-top,0px);padding-bottom:env(safe-area-inset-bottom,0px)';
-        document.body.appendChild(probe);
-        const badge = document.createElement('div');
-        badge.style.cssText = [
-            /* Sits BELOW the notch on purpose: at the old flat top:40px the badge
-               painted into the status-bar strip and covered the session header,
-               which read on a screenshot as "the header ran under the notch in
-               debug mode" — a measurement artefact that cost a whole round of
-               diagnosis. env() here, not --mnav-sat: the badge must stay put even
-               when the inset param is faking that variable. */
-            'position:fixed', 'top:calc(env(safe-area-inset-top, 0px) + 8px)', 'right:6px', 'z-index:2147483000',
-            'background:rgba(0,0,0,.82)', 'color:#fff', 'font:11px/1.5 ui-monospace,monospace',
-            'padding:8px 10px', 'border-radius:8px', 'max-width:94vw', 'max-height:70vh',
-            /* pointer-events must be auto for the escape hatch below — with `none`
-               the badge could only be dismissed by editing localStorage, which is
-               not reachable from a standalone PWA. touch-action/user-select keep
-               the double tap from being read as zoom or text selection. */
-            'overflow:auto', 'white-space:pre-wrap', 'pointer-events:auto',
-            'touch-action:manipulation', '-webkit-user-select:none', 'user-select:none',
-        ].join(';');
-        /* Escape hatch: two taps on the badge within 600ms turn debug off. The
-           enable gesture lives on the home screen, which a user deep inside a
-           session cannot reach without first getting out of the way of the badge
-           — so the off switch belongs on the badge itself. */
-        /* The full read-out is tall enough to cover the session list, and with
-           pointer-events:auto (required for the escape hatch) it swallowed every
-           tap under it — the user could not open a session with debug on. The
-           badge therefore starts COLLAPSED (a one-line pill showing vh, the
-           number that matters for the viewport-shrink bug) and only expands on
-           demand. Single tap toggles collapsed/expanded (deferred 620ms so it
-           can be distinguished from the exit gesture); double tap still exits. */
-        let lastTap = 0;
-        let collapsed = true;
-        let singleTapTimer;
-        const onBadgeTap = (event) => {
-            event.preventDefault();
-            event.stopPropagation();
-            const now = Date.now();
-            if (now - lastTap < 600) {
-                if (singleTapTimer !== undefined)
-                    clearTimeout(singleTapTimer);
-                localStorage.removeItem(DEBUG_KEY);
-                const url = new URL(location.href);
-                url.searchParams.delete('mobile-nav-debug');
-                location.replace(url.toString());
+        const schedule = () => {
+            // The locale subscription below lives outside attach/detach, so this
+            // guard is what keeps a late dictionary registration from marking up
+            // the flow at >= 768px (real WebKit regression: chips and fold
+            // attributes appeared at 1280px — invisible, since every rule that
+            // hides anything is inside the phone media query, but still wrong).
+            if (observer === null)
                 return;
-            }
-            lastTap = now;
-            singleTapTimer = setTimeout(() => {
-                collapsed = !collapsed;
-                paint();
-            }, 620);
+            if (frame !== 0)
+                return;
+            frame = requestAnimationFrame(() => {
+                frame = 0;
+                scan();
+                // Drop the records our own chip insertions just queued, so a rescan
+                // can never re-trigger itself (the debug-badge feedback-loop freeze).
+                observer?.takeRecords();
+            });
         };
-        badge.addEventListener('click', onBadgeTap);
-        const read = () => {
-            const q = (sel) => !!document.querySelector(sel);
-            const vis = (sel) => {
-                const el = document.querySelector(sel);
-                return el === null ? 'absent' : getComputedStyle(el).visibility;
-            };
-            const frame = document.querySelector('[data-mobile-nav="frame"]');
-            if (collapsed)
-                return `DBG vh ${innerHeight}/${screen.height} ▸ 单击展开 双击关闭`;
-            return [
-                '▾ 单击收起 · 双击关闭 debug',
-                `URL ${location.pathname}${location.search}`,
-                `W ${innerWidth} x ${innerHeight} dpr ${devicePixelRatio}`,
-                `mq≤1023 ${matchMedia('(max-width: 1023px)').matches}  mq≥1024 ${matchMedia('(min-width: 1024px)').matches}`,
-                `css ${q('style[data-plugin-css*="mobile"]')}  frame ${!!frame}`,
-                `previewCol ${vis('[data-aionui-preview-col]')}  explorerCol ${vis('[data-aionui-explorer-col]')}`,
-                `previewOpen ${frame?.hasAttribute('data-aionui-preview-open') ?? '?'}  explorerOpen ${frame?.hasAttribute('data-aionui-explorer-open') ?? '?'}  previewFull ${frame?.hasAttribute('data-mobile-preview-full') ?? '?'}`,
-                `header ${vis('[data-phase] header')} h${Math.round(document.querySelector('[data-phase] header')?.getBoundingClientRect().height ?? 0)}  composer ${q('textarea')}`,
-                `sat ${getComputedStyle(document.documentElement).getPropertyValue('--mnav-sat').trim() || '?'}  sab ${getComputedStyle(document.documentElement).getPropertyValue('--mnav-sab').trim() || '?'}`,
-                (() => {
-                    /* Bottom-gap forensics: real env values + who ends where. */
-                    const ps = getComputedStyle(probe);
-                    const bottomOf = (sel) => {
-                        const el = document.querySelector(sel);
-                        return el === null ? '—' : String(Math.round(el.getBoundingClientRect().bottom));
-                    };
-                    /* Composer ledger: bottom/gap-to-viewport for every layer between
-                       the textarea and the screen edge, so a "white band under the
-                       composer" screenshot says WHICH layer owns it instead of only
-                       where the textarea ends. Anchors per AGENTS.md: InputBar root is
-                       the padding carrier, _card is the rounded visual box, _composerSeat
-                       is the sticky seat, _scrollBody is the real scroll container. */
-                    const pair = (sel) => {
-                        const el = document.querySelector(sel);
-                        if (el === null)
-                            return '—';
-                        const b = el.getBoundingClientRect().bottom;
-                        return `${Math.round(b)}/${Math.round(innerHeight - b)}`;
-                    };
-                    const barRoot = document.querySelector('[data-slot="conversation.composer.bar"] > [class$="_root"]');
-                    /* Top-edge forensics: rect.top of the surfaces that consume
-                       --mnav-sat. These separate the two competing readings of the
-                       device numbers — a viewport SUNK below the status bar (origin at
-                       screen y=59, so a working sat padding puts the header at 118 and
-                       the top gap is doubled) versus a viewport anchored at screen y=0
-                       that is merely 59px short at the bottom (header at 59, top
-                       correct, the missing 59 showing as a band under the composer).
-                       innerHeight alone cannot tell them apart; the viewport ORIGIN can,
-                       hence screenY / visualViewport offsets / the edge markers. */
-                    const topOf = (sel) => {
-                        const el = document.querySelector(sel);
-                        return el === null ? '—' : String(Math.round(el.getBoundingClientRect().top));
-                    };
-                    const framePadTop = frame === null ? '—' : getComputedStyle(frame).paddingTop;
-                    const vv = window.visualViewport;
-                    return [
-                        `env sat ${ps.paddingTop} sab ${ps.paddingBottom}`,
-                        `screen ${screen.width}x${screen.height} avail ${screen.availWidth}x${screen.availHeight}`,
-                        `vh ${innerHeight} vv ${Math.round(vv?.height ?? -1)} outH ${outerHeight}`,
-                        `scrXY ${screenX},${screenY} vvOff ${Math.round(vv?.offsetTop ?? -1)} vvPage ${Math.round(vv?.pageTop ?? -1)} vvScale ${vv?.scale ?? '?'}`,
-                        /* The ENFORCED state, not a re-derivation: installSunkInset()
-                           stamps data-mnav-sunk, and its absence means the override is
-                           not running at all (the inset param owns the variables). sabOvr
-                           is the receipt — the inline value it wrote, or (env) when the
-                           normal compensation is in force. */
-                        `sunk? ${document.documentElement.dataset.mnavSunk ?? 'n/a'} standalone ${matchMedia('(display-mode: standalone)').matches} sabOvr ${document.documentElement.style.getPropertyValue('--mnav-sab') || '(env)'}`,
-                        `frameTop ${topOf('[data-mobile-nav="frame"]')} padTop ${framePadTop} headerTop ${topOf('[data-phase] header')} homeTopY ${topOf('[data-mobile-nav="home-top"]')}`,
-                        `botFrame ${bottomOf('[data-mobile-nav="frame"]')} composer ${bottomOf('[data-phase] textarea')}`,
-                        `taB ${pair('[data-phase] textarea')} cardB ${pair('[data-slot="conversation.composer.bar"] [class$="_card"]')}`,
-                        `barB ${pair('[data-slot="conversation.composer.bar"] > [class$="_root"]')} seatB ${pair('[class$="_composerSeat"]')} scrollB ${pair('[class$="_scrollBody"]')}`,
-                        `sabPad ${barRoot === null ? '—' : getComputedStyle(barRoot).paddingBottom}`,
-                        `botList ${bottomOf('[data-mobile-nav="home-list"]')} fab ${bottomOf('[data-mobile-nav="home-fab"]')}`,
-                        `cssLen ${document.querySelector('style[data-plugin-css*="mobile"]')?.textContent?.length ?? 0}`,
-                    ].join('\n');
-                })(),
-                `genui cards ${document.querySelectorAll('[data-genui]').length}  panel ${q('[data-genui-panel]')}`,
-                `phase ${document.querySelector('[data-phase]')?.getAttribute('data-phase') ?? '?'}`,
-                `errs ${errors.slice(-5).join(' | ') || 'none'}`,
-            ].join('\n');
+        const onClick = (event) => {
+            const target = event.target;
+            if (!(target instanceof Element))
+                return;
+            const chip = target.closest(CHIP_SELECTOR);
+            const key = chip?.dataset['foldGroup'];
+            if (key === undefined)
+                return;
+            if (expanded.has(key))
+                expanded.delete(key);
+            else
+                expanded.add(key);
+            scan();
         };
-        /* Feedback-loop guards: painting the badge mutates the body subtree the
-           observer watches — without these two checks the observer retriggers
-           itself forever and freezes the page (the badge was rarely actually
-           enabled before, which is how this survived). */
-        const paint = () => {
-            const next = read();
-            if (next !== badge.textContent)
-                badge.textContent = next;
+        const clear = () => {
+            for (const chip of document.querySelectorAll(CHIP_SELECTOR))
+                chip.remove();
+            for (const item of document.querySelectorAll(`[${FOLD}]`)) {
+                item.removeAttribute(FOLD);
+                item.removeAttribute(exports.OPEN);
+            }
         };
-        paint();
-        const observer = new MutationObserver((mutations) => {
-            if (mutations.every((m) => m.target === badge || badge.contains(m.target) || m.target === probe))
+        const attach = () => {
+            if (observer !== null)
                 return;
-            paint();
-        });
-        observer.observe(document.body, { childList: true, subtree: true, attributes: true });
-        const timer = setInterval(paint, 1500);
-        document.body.appendChild(badge);
+            document.documentElement.setAttribute(ACTIVE_ATTR, '');
+            observer = new MutationObserver(schedule);
+            observer.observe(document.body, { childList: true, subtree: true });
+            document.addEventListener('click', onClick);
+            scan();
+        };
+        const detach = () => {
+            document.documentElement.removeAttribute(ACTIVE_ATTR);
+            observer?.disconnect();
+            observer = null;
+            document.removeEventListener('click', onClick);
+            if (frame !== 0)
+                cancelAnimationFrame(frame);
+            frame = 0;
+            expanded.clear();
+            clear();
+        };
+        const onChange = (event) => (event.matches ? attach() : detach());
+        let disposed = false;
+        let desktop = false;
+        /** Attach at every width and drop the breakpoint listener — the
+         * stylesheet's html[DESKTOP_ATTR] rules take over from the phone media
+         * query. Idempotent: the config answer and the local opt-in may both
+         * ask for it. */
+        const enableDesktop = () => {
+            if (desktop || disposed)
+                return;
+            desktop = true;
+            document.documentElement.setAttribute(DESKTOP_ATTR, '');
+            narrow.removeEventListener('change', onChange);
+            attach();
+        };
+        if (narrow.matches)
+            attach();
+        narrow.addEventListener('change', onChange);
+        if (desktopOptIn())
+            enableDesktop();
+        // The row config arrives async; a late enable just attaches then. Not
+        // awaited before phone attach — folding must not wait on a round-trip.
+        else
+            void desktopConfigured().then((on) => (on ? enableDesktop() : undefined));
+        // A language switch changes the chip copy of every already-rendered turn.
+        const stopLocale = ctx.locale.subscribe(schedule);
         return () => {
-            window.removeEventListener('error', onError);
-            window.removeEventListener('unhandledrejection', onRejection);
-            observer.disconnect();
-            clearInterval(timer);
-            probe.remove();
-            badge.remove();
+            disposed = true;
+            document.documentElement.removeAttribute(DESKTOP_ATTR);
+            narrow.removeEventListener('change', onChange);
+            stopLocale();
+            detach();
         };
-    }, 'dsh-mobile-nav: debug badge');
+    }, 'dsh-mobile-nav: turn process fold');
+}
+};
+__modules["styles/turn-fold.css.js"] = function (require, module, exports) {
+"use strict";
+// turn-fold — the folded turn process and its summary row (S8, 2026-08-17).
+// Two blocks, both inert unless the fold is actually running:
+//   * BORN_FOLDED, keyed on html[data-mnav-fold-on] — the root attribute
+//     effects/turn-fold.ts holds for as long as it is attached, so the block
+//     is live at exactly the widths the fold is. It hides process rows by
+//     the HOST's own markers, which means a row is folded at its first paint
+//     rather than a frame after the effect notices it (2026-08-22).
+//   * the `rules()` block below, scoped to (max-width: 767px) OR
+//     html[data-mnav-desktop-fold] (the per-browser desktop opt-in, issue
+//     #2), reading markers this plugin writes: data-mnav-fold on a process
+//     element, data-mobile-nav="turn-fold" on the injected summary row.
+//     effects/turn-fold.ts wipes both when it detaches, so a non-opted-in
+//     tablet/desktop is a no-op twice over, by attribute and by scope. It is
+//     authored once and emitted twice so the two scopes can never drift.
+// Appended last in styles/index.ts; it shares no selector with any other
+// file, the position just keeps the "phone files come after the shared
+// <=1023px block" ordering intact.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.TURN_FOLD_CSS = void 0;
+const turn_fold_ts_1 = require("./effects/turn-fold.js");
+/** Mirror of the root attribute effects/turn-fold.ts holds while attached. */
+const ACTIVE = 'data-mnav-fold-on';
+/**
+ * Born folded — the reason a new tool call no longer blinks into view.
+ *
+ * These selectors read the HOST's own markers (ChatNodeSeat's
+ * `data-chat-flow-kind`, ReasoningRow's `data-variant`), which React sets in
+ * the same commit that inserts the row, so the row is already
+ * `display: none` at its first paint. effects/turn-fold.ts still rescans on
+ * the next animation frame, but by then it is only writing the per-turn
+ * {@link OPEN} override and the summary chip — it is no longer what hides
+ * anything, which is what the reader used to see as a one-frame flash
+ * (2026-08-22).
+ *
+ * Keyed on the root attribute the effect holds while it is attached, so this
+ * block is live for exactly the widths the fold is, and hides nothing at all
+ * when the effect never ran.
+ *
+ * One case stays with the effect: an assistant-step row whose whole body is
+ * reasoning has to be hidden as a row (an emptied-out flex item still claims
+ * the flow column's 16px gap), and "this row has nothing but Think in it" is
+ * not a selector. Its rows therefore still fold a frame late — as blank
+ * space, not as content, since the Think rows below are hidden here.
+ */
+const BORN_FOLDED = [
+    ...turn_fold_ts_1.PROCESS_KINDS.map((kind) => `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="${kind}"]:not([${turn_fold_ts_1.OPEN}])`),
+    `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="assistant-step"] ${turn_fold_ts_1.THINK}:not([${turn_fold_ts_1.OPEN}])`,
+].join(',\n');
+/** The fold + chip rules, with every selector prefixed by `scope`. */
+const rules = (scope) => `
+  /* Folded process: tool-call / context / command rows and the Think
+     disclosures inside an assistant step. !important because the official
+     flow item and ReasoningRow both set their own display. */
+  ${scope} [data-mnav-fold]:not([data-mnav-fold-open]) {
+    display: none !important;
+  }
+
+  /* Compact chip, sized like the composer's own pills rather than a button:
+     it is a reading affordance in the middle of the message flow, so it has
+     to stay quieter than the content around it. The flow column is a flex
+     column with gap: 16px (ChatView.module.css) — align-self keeps the chip
+     from stretching, and the negative block margin trims that generous gap
+     back to something a 26px row can live in. */
+  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"] {
+    display: inline-flex;
+    align-self: flex-start;
+    align-items: center;
+    gap: 6px;
+    margin: -4px 0;
+    padding: 0 10px;
+    height: 26px;
+    border: none;
+    border-radius: 13px;
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .55));
+    font: inherit;
+    font-size: 12px;
+    line-height: 26px;
+    white-space: nowrap;
+    cursor: pointer;
+    -webkit-tap-highlight-color: transparent;
+  }
+  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]:active {
+    background: var(--dsw-alias-interactive-bg-pressed, rgba(0, 0, 0, .1));
+  }
+
+  /* Leading dot: idle turns get a quiet mark, a running turn gets the same
+     business-primary colour the session header's own status dot uses
+     (styles/header.css.ts) plus a breathing pulse. */
+  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]::before {
+    content: '';
+    flex: none;
+    width: 6px;
+    height: 6px;
+    border-radius: 50%;
+    background: currentColor;
+    opacity: .45;
+  }
+  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"][data-running]::before {
+    background: var(--dsw-alias-state-business-primary, #4f6ef7);
+    opacity: 1;
+    animation: dsh-mobile-nav-breathe 1.4s var(--ds-ease-in-out, ease-in-out) infinite;
+  }
+
+  /* Chevron drawn from two borders — no icon injection, no mask image, and
+     it rotates to point up once the turn is open. */
+  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]::after {
+    content: '';
+    flex: none;
+    width: 5px;
+    height: 5px;
+    margin-top: -3px;
+    border-right: 1.5px solid currentColor;
+    border-bottom: 1.5px solid currentColor;
+    transform: rotate(45deg);
+    transition: transform .16s var(--ds-ease-out, ease-in-out);
+  }
+  ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"][data-open]::after {
+    margin-top: 3px;
+    transform: rotate(-135deg);
+  }
+
+  @media (prefers-reduced-motion: reduce) {
+    ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"][data-running]::before {
+      animation: none;
+    }
+    ${scope} [data-chat-flow] > [data-mobile-nav="turn-fold"]::after {
+      transition: none;
+    }
+  }
+`;
+exports.TURN_FOLD_CSS = `/* ---------- turn process fold (< 768px, or desktop opt-in) ---------- */
+
+/* Process rows and Think disclosures start folded, before any script has
+   looked at them — see BORN_FOLDED above. */
+${BORN_FOLDED} {
+  display: none !important;
+}
+
+/* The summary row never paints outside its active scope, even if a
+   media-query change raced the effect's own cleanup. */
+[data-mobile-nav="turn-fold"] {
+  display: none;
+}
+
+@media (max-width: 767px) {${rules('')}}
+
+/* Desktop opt-in: the exact same block, keyed on the root attribute
+   effects/turn-fold.ts sets for a browser opted in via
+   ?mobile-nav-turn-fold=1 — active at every width. */
+${rules('html[data-mnav-desktop-fold]')}
+
+@keyframes dsh-mobile-nav-breathe {
+  0%, 100% { opacity: 1; transform: scale(1); }
+  50% { opacity: .4; transform: scale(.72); }
+}
+`;
+};
+__modules["styles/chips.css.js"] = function (require, module, exports) {
+"use strict";
+// chips — S5 (2026-08-17): the home-screen plugin-entry chips row, its
+// customize sheet, the settings gear button, and the settings/usage-stats
+// dialog portal fix. Appended LAST in index.ts (after home.css.ts) so its
+// `display` overrides win any tie against the phone shell's blanket
+// `[data-mobile-nav="frame"] > :first-child { display: none }` rule — though
+// the extra `:has()` clause already outranks it on specificity alone.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CHIPS_CSS = void 0;
+exports.CHIPS_CSS = `/* ---------- chips row + settings entry (S5) ---------- */
+
+@media (max-width: 767px) {
+  /* --- settings dialog / usage-stats panel / scheduled-tasks dialog portal fix ---
+     dsh-client-ui-settings-general's SettingsRoot (trigger button +
+     position:fixed;z-index:1000 modal), dsh-usage-stats' sidebar-footer
+     badge (position:fixed panel), and @opendsh/dsh-plugin-scheduled-tasks'
+     "定时任务" trigger (position:fixed;z-index:120 \`.dshst-overlay\`,
+     verified against 0.2.0 — real-device report 2026-08-17: chip click
+     produced no visible window) all mount as PLAIN CHILDREN of the sidebar
+     tree — not a React portal to document.body — inside
+     sidebar.settings / sidebar.footer.action
+     (dsh-client-ui-sidebar's SidebarRoot: footArea > settingsArea /
+     footerActions). home.css.ts sets the sidebar ROOT
+     (\`[data-mobile-nav="frame"] > :first-child\`) to display:none on the
+     phone breakpoint (the app shell replaced the drawer) — and display:none
+     removes the WHOLE subtree from the render tree, including
+     position:fixed descendants, which cannot escape it the way they escape
+     a merely-offscreen or opacity:0 ancestor. A \`.click()\` on the (still
+     DOM-present) hidden trigger still flips its component-local \`open\`
+     state and mounts the aria-modal dialog (synthetic dispatch bypasses
+     hit-testing — S2.1 precedent), but nothing paints without this fix.
+
+     Un-hiding the WHOLE sidebar would surface the session tree / new-session
+     button underneath the dialog, so this is scoped to exactly the sidebar
+     root plus its OWN direct children that are not on the path to
+     footArea: display:contents on the root removes its own box (no
+     duplicate page background/padding, no grid-column reflow) while
+     letting footArea/footerActions/settingsArea resume their OWN official
+     (non-none) display — logoRow / newSession / regionArea are hidden
+     explicitly instead. :has() matches against the DOM tree regardless of
+     the scope element's own computed display, so this reads correctly even
+     though the whole subtree started at display:none (same precedent as
+     every other :has()-gated rule in this stylesheet, e.g. the settings
+     sheet adaptation below, which depends on exactly this becoming
+     visible).
+
+     \`:first-child\` is a layout-column WRAPPER
+     (\`pI_x6G_sidebarCol\`, dsh-client-ui-layout's AppFrame grid cell), not
+     SidebarRoot's own div — SidebarRoot (\`hHd-Xa_root\`) sits one more empty
+     unstyled div below it (measured 2026-08-17: sidebarCol > div (no
+     class) > div.hHd-Xa_root > logoRow/newSession/regionArea/footArea).
+     display:contents on sidebarCol lets that whole chain resume its own
+     official (non-none) display with no other rule needed, but the
+     "hide the other three" selectors below must therefore be DESCENDANT
+     (unscoped depth), not direct-child \`>\`, or they silently match
+     nothing — confirmed live: an earlier \`>\`-only version left
+     logoRow/newSession/regionArea at \`display: flex\`, which is only
+     hidden from view by being fully underneath the usage-stats panel's
+     opaque body, not by this rule. */
+  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) {
+    display: contents !important;
+  }
+  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) [class$="_logoRow"],
+  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) [class$="_newSession"],
+  [data-mobile-nav="frame"] > :first-child:has([aria-modal="true"], [data-usage-stats-panel], .dshst-overlay) [class$="_regionArea"] {
+    display: none !important;
+  }
+
+  /* Home-top settings gear: 44pt touch target, pushed to the row's end by
+     its own auto margin (home-top itself stays a plain flex row). */
+  [data-mobile-nav="home-settings"] {
+    flex: none;
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    width: 44px;
+    height: 44px;
+    margin-left: auto;
+    padding: 0;
+    border: none;
+    background: transparent;
+    color: var(--dsw-alias-label-secondary, inherit);
+    cursor: pointer;
+    touch-action: manipulation;
+    -webkit-tap-highlight-color: transparent;
+  }
+  [data-mobile-nav="home-settings"]:active {
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+    border-radius: 50%;
+  }
+
+  /* Plugin-entry chips row: one horizontally-scrolling line of 34px pills
+     between the workspace title and the session list (prototype spec).
+     Scrollbar hidden on BOTH engines (2026-08-18 user decision): iOS
+     overlay scrollbars never showed anyway, but desktop browsers painted a
+     permanent 2px strip under the pills. This revisits the AGENTS.md
+     "silently cut off the last tab" lesson deliberately — with 4+ chips the
+     row now always overflows mid-chip (a partially visible pill is the
+     scroll affordance), unlike the early incident where the chips fit
+     flush and the hidden overflow was undiscoverable. */
+  [data-mobile-nav="chip-row"] {
+    flex: 0 0 auto;
+    display: flex;
+    align-items: center;
+    gap: 8px;
+    padding: 0 16px 10px;
+    overflow-x: auto;
+    overscroll-behavior: contain;
+    -webkit-overflow-scrolling: touch;
+    scrollbar-width: none;
+  }
+  [data-mobile-nav="chip-row"]::-webkit-scrollbar {
+    display: none;
+  }
+  [data-mobile-nav="chip"],
+  [data-mobile-nav="chip-more"] {
+    flex: none;
+    display: inline-flex;
+    align-items: center;
+    gap: 6px;
+    height: 34px;
+    padding: 0 14px;
+    border: none;
+    border-radius: 17px;
+    /* Same surface as the list rows: the home page is bg-base since the
+       2026-08-20 swap (see home.css.ts), so a bg-base chip would disappear
+       into it. */
+    background: var(--dsw-specific-sidebar-fill, #f5f5f5);
+    color: var(--dsw-alias-label-primary, inherit);
+    font-family: inherit;
+    font-size: 13px;
+    font-weight: 500;
+    white-space: nowrap;
+    cursor: pointer;
+    touch-action: manipulation;
+    -webkit-tap-highlight-color: transparent;
+    box-shadow: 0 1px 3px rgba(0, 0, 0, .06);
+  }
+  [data-mobile-nav="chip-more"] {
+    padding: 0 9px;
+  }
+  [data-mobile-nav="chip"]:active,
+  [data-mobile-nav="chip-more"]:active {
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+  }
+
+  /* Harvested chip icon (S5.1): the cloned <svg> keeps whatever width/height
+     the source plugin gave it (18px for the one verified live example) —
+     force it down to the same 16px box every hand-registered chip icon
+     uses, CSS wins over the presentational SVG attributes. */
+  [data-mobile-nav="chip-harvest-icon"] {
+    display: inline-flex;
+    flex: none;
+  }
+  [data-mobile-nav="chip-harvest-icon"] svg {
+    display: block;
+    width: 16px;
+    height: 16px;
+  }
+
+  /* Customize sheet: toggle rows inside the SAME home-sheet-layer/mask/sheet
+     chrome the workspace switcher declares in home.css.ts — S6's
+     drag-to-close and mask-click-close bind to
+     \`[data-mobile-nav="home-sheet"]\` generically (effects/gestures.ts), so
+     this second use of the marker needs no new gesture wiring. */
+  [data-mobile-nav="chip-toggle-row"] {
+    display: flex;
+    align-items: center;
+    gap: 10px;
+    width: 100%;
+    /* Real-device fix: without border-box this row's used width is
+       100% (of the sheet's own already-padded content box) PLUS the
+       12px+12px padding below, overflowing the sheet by 24px and
+       shoving the flex:none toggle off its right edge (2026-08-17
+       report: "开关跑到屏幕外"). home-sheet-item next door in
+       home.css.ts has the identical width:100%+padding shape and the
+       same latent bug, just with no trailing element to visibly clip. */
+    box-sizing: border-box;
+    min-height: 48px;
+    padding: 0 12px;
+    color: inherit;
+  }
+  [data-mobile-nav="chip-toggle-label"] {
+    flex: 1 1 auto;
+    min-width: 0;
+    font-size: 15px;
+    overflow: hidden;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+  }
+  [data-mobile-nav="chip-toggle"] {
+    flex: none;
+    position: relative;
+    width: 42px;
+    height: 26px;
+    border: none;
+    border-radius: 13px;
+    background: var(--dsw-alias-border-l2, rgba(0, 0, 0, .16));
+    cursor: pointer;
+    touch-action: manipulation;
+    -webkit-tap-highlight-color: transparent;
+    transition: background .15s var(--ds-ease-in-out, ease-in-out);
+  }
+  [data-mobile-nav="chip-toggle"]::after {
+    content: '';
+    position: absolute;
+    top: 2px;
+    left: 2px;
+    width: 22px;
+    height: 22px;
+    border-radius: 50%;
+    background: #ffffff;
+    box-shadow: 0 1px 3px rgba(0, 0, 0, .3);
+    transition: transform .15s var(--ds-ease-in-out, ease-in-out);
+  }
+  [data-mobile-nav="chip-toggle"][aria-checked="true"] {
+    background: var(--dsw-alias-button-primary-fill, #1a1a1a);
+  }
+  [data-mobile-nav="chip-toggle"][aria-checked="true"]::after {
+    transform: translateX(16px);
+  }
+  @media (prefers-reduced-motion: reduce) {
+    [data-mobile-nav="chip-toggle"],
+    [data-mobile-nav="chip-toggle"]::after {
+      transition: none !important;
+    }
+  }
 }
+`;
 };
-__modules["effects/phone-chrome.js"] = function (require, module, exports) {
+__modules["styles/content.css.js"] = function (require, module, exports) {
 "use strict";
+// content — chat markdown readability on phones (2026-08-18). Shares no
+// selector with any other file; appended last in styles/index.ts.
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.installPhoneChrome = installPhoneChrome;
-exports.isViewportSunkBelowStatusBar = isViewportSunkBelowStatusBar;
-exports.installViewportHeal = installViewportHeal;
-exports.installSunkInset = installSunkInset;
-/**
- * Phone chrome: KEEP the system status bar (no fullscreen) and make it
- * blend into the page. On narrow screens:
- * - The viewport meta gains viewport-fit=cover, so env(safe-area-inset-top)
- *   is the real status-bar / notch height and the stylesheet can push every
- *   surface below it (off notched phones, or in a browser tab where the
- *   layout viewport already sits below the status bar, the inset is 0 and
- *   nothing shifts).
- * - A theme-color meta tracks the shell background (the official theme is
- *   toggled by body[data-ds-dark-theme], which flips --dsw-alias-bg-base):
- *   Android then paints the status bar / URL bar with the page's own base
- *   color, so the status bar reads as part of the UI instead of a foreign
- *   strip. The drawer paints the same strip on iOS / notch displays.
- * - gesturestart is suppressed as the legacy-iOS fallback for double-tap
- *   zoom; modern browsers are covered by the stylesheet's
- *   touch-action: manipulation (which keeps pan and pinch zoom).
- */
-function installPhoneChrome(ctx) {
-    ctx.effect(() => {
-        const narrow = window.matchMedia('(max-width: 1023px)');
-        const viewport = document.querySelector('meta[name="viewport"]');
-        const originalViewport = viewport?.content ?? '';
-        const themeMeta = document.createElement('meta');
-        themeMeta.name = 'theme-color';
-        const bodyBg = () => getComputedStyle(document.body).backgroundColor;
-        const sync = () => {
-            if (viewport !== null)
-                viewport.content = 'width=device-width, initial-scale=1, viewport-fit=cover';
-            themeMeta.content = bodyBg();
-            if (themeMeta.parentElement === null)
-                document.head.appendChild(themeMeta);
-        };
-        const restore = () => {
-            if (viewport !== null)
-                viewport.content = originalViewport;
-            themeMeta.remove();
-        };
-        const onGestureStart = (event) => event.preventDefault();
-        if (narrow.matches)
-            sync();
-        const onChange = (event) => (event.matches ? sync() : restore());
-        narrow.addEventListener('change', onChange);
-        const observer = new MutationObserver(() => {
-            if (narrow.matches)
-                themeMeta.content = bodyBg();
-        });
-        observer.observe(document.body, { attributes: true, attributeFilter: ['data-ds-dark-theme'] });
-        document.addEventListener('gesturestart', onGestureStart);
-        return () => {
-            narrow.removeEventListener('change', onChange);
-            observer.disconnect();
-            document.removeEventListener('gesturestart', onGestureStart);
-            restore();
-        };
-    }, 'dsh-mobile-nav: status bar theme + viewport + zoom guard');
+exports.CONTENT_CSS = void 0;
+exports.CONTENT_CSS = `/* ---------- chat markdown content (< 768px) ---------- */
+
+@media (max-width: 767px) {
+  /* Inline code: upstream renders it display:inline-flex — an atomic inline
+     box that can never wrap across lines, so one long code span walks off
+     the right edge of the screen. Plain inline keeps the background pill
+     per line fragment and lets long tokens break anywhere. Deliberately
+     unscoped (any :not(pre) > code, not just the _markdown_ module):
+     inline code also renders outside that container (user bubbles,
+     reasoning rows), and on a phone there is no width at which an
+     unwrappable inline box is right. !important beats the upstream
+     display:inline-flex on specificity ties. */
+  :not(pre) > code {
+    display: inline !important;
+    overflow-wrap: anywhere;
+    /* iOS WebKit: overflow-wrap alone still failed to break long tokens in
+       inline code on a real iPhone (screenshot-verified 2026-08-18, li >
+       code path case) while desktop Chromium broke them fine. break-all is
+       the everywhere-supported hammer; acceptable for code pills. */
+    word-break: break-all;
+  }
+  /* Belt-and-suspenders for engines that compute soft-wrap opportunities
+     from the block container rather than the inline itself (historical
+     WebKit behavior): inherit anywhere through the whole transcript so the
+     block side agrees. Prose is untouched until something would overflow;
+     the table is already pinned wide by min-width: max-content below. */
+  [data-chat-flow],
+  [class*="_markdown_"] {
+    overflow-wrap: anywhere;
+  }
+
+  /* Transcript density (2026-08-20): the desktop prose rhythm is 28px of
+     leading on 15px text — a 1.87 ratio that reads generously on a wide
+     column but wastes a phone screen, where the same paragraph is three
+     times as many lines. Unitless 1.65 so nested blocks (code, quotes,
+     lists) recompute from their OWN font-size instead of inheriting a fixed
+     28px that is far too loose for 12-13px chrome text. 1.65 is the floor I
+     am willing to go to for mixed CJK/Latin: the glyphs are full-height with
+     no descender relief, so tighter starts to look stacked. Phone only —
+     the desktop column keeps the official rhythm. */
+  [class*="_markdown_"] {
+    line-height: 1.65;
+  }
+  /* Paragraph rhythm. Each paragraph is its own markdown block and the
+     separation comes from the flex container's row-gap, not from margins —
+     at the stock 16px the paragraph baseline step was 40.75px against a
+     24.75px line step, i.e. 1.65x, which is what reads as airy. 12px brings
+     the step to ~36.75px: still clearly more than one line so paragraphs
+     never run together, but noticeably denser. Scoped by :has() to
+     containers that actually hold prose blocks, so tool cards and other
+     flex bodies with the same hashed suffix keep their own spacing. */
+  [data-phase] [class$="_body"]:has(> [class*="_markdown_"]) {
+    row-gap: 12px !important;
+  }
+
+  /* Markdown tables: the official _tableScroll_ wrapper is already a
+     horizontal scroll viewport around a width:max-content table, but its
+     cells are capped at min(30vw, 320px) — barely 120px on a phone, which
+     crushes every column into a vertical word-stack. Let columns size to
+     their content instead and read the overflow by scrolling the wrapper.
+     480px (not a vw cap — 85vw was ~320px on a 375px phone and still
+     wrapped mid-length cells) keeps typical cells on one line; only truly
+     prose-heavy cells wrap, instead of dragging the table kilometers
+     wide. */
+  [class*="_tableScroll_"] th,
+  [class*="_tableScroll_"] td {
+    max-width: 480px !important;
+  }
+
+  /* iOS WebKit fallback: upstream's own table { width: max-content } is what
+     keeps the table at its natural width inside the scroll wrapper, but
+     WebKit's max-content support on table boxes is incomplete — on a real
+     iPhone the table fell back to shrink-to-fit and every column got
+     crushed to its min-width (the "ra/nk" vertical-word-stack screenshot,
+     2026-08-18). Redeclare the natural-width intent with both width and
+     min-width so whichever keyword the engine honors wins; the wrapper
+     already scrolls the overflow. */
+  [class*="_tableScroll_"] table {
+    width: max-content !important;
+    min-width: max-content !important;
+    max-width: none !important;
+  }
+
+  /* Turn-tail metadata (2026-08-18): the timing stats ("18:06 · 用时 29秒 ·
+     首 token 0.9秒 · 163 tok/s") are desktop-hover-revealed (official
+     [data-time-hover-root] gate holds them at opacity 0 until :hover /
+     :focus-within) — a phone never hovers, so they were simply invisible;
+     and even ignoring that, the row is nowrap + overflow:hidden (plus this
+     plugin's own legacy ellipsis clamp in layout.css.ts), which clipped the
+     text. On phones: always visible, own full-width line under the action
+     icons, wrapping freely, one type size down. !important + the extra
+     [class$="_actions"] hop out-specifies both upstream and layout.css.ts. */
+  /* Pin the tail row's width chain before allowing wrap: with wrap enabled
+     the row's intrinsic (shrink-to-fit) width collapses to its widest
+     single icon, taking the whole tail down to ~16px. */
+  [data-chat-flow-kind="turn-tail"] [class$="_root"],
+  [data-chat-flow-kind="turn-tail"] [class$="_actions"] {
+    width: 100%;
+  }
+  [data-chat-flow-kind="turn-tail"] [class$="_actions"] {
+    flex-wrap: wrap;
+    row-gap: 2px;
+  }
+  /* Wide companion to the rule below: mirrors the upstream hover-gate
+     selector shape directly, with no assumptions about the tail's DOM
+     structure, so the stats can't stay invisible even if the phone's tail
+     renders differently than desktop. */
+  [data-time-hover-root] [class$="_timeEnd"],
+  [data-time-hover-root] [class$="_timeStart"] {
+    opacity: 1 !important;
+    transition: none !important;
+  }
+  [data-chat-flow-kind="turn-tail"] [class$="_actions"] [class$="_timeEnd"] {
+    opacity: 1 !important;
+    flex-basis: 100% !important;
+    white-space: normal !important;
+    overflow: visible !important;
+    text-overflow: clip !important;
+    padding-left: 0 !important;
+    font-size: 12px;
+    line-height: 18px;
+  }
 }
+`;
+};
+__modules["styles/index.js"] = function (require, module, exports) {
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.MOBILE_CSS = void 0;
+const base_css_ts_1 = require("./styles/base.css.js");
+const layout_css_ts_1 = require("./styles/layout.css.js");
+const compat_css_ts_1 = require("./styles/compat.css.js");
+const misc_css_ts_1 = require("./styles/misc.css.js");
+const home_css_ts_1 = require("./styles/home.css.js");
+const header_css_ts_1 = require("./styles/header.css.js");
+const composer_css_ts_1 = require("./styles/composer.css.js");
+const info_css_ts_1 = require("./styles/info.css.js");
+const turn_fold_css_ts_1 = require("./styles/turn-fold.css.js");
+const chips_css_ts_1 = require("./styles/chips.css.js");
+const content_css_ts_1 = require("./styles/content.css.js");
 /**
- * Does the layout viewport sit shorter than the screen by at least the top
- * inset env() still claims? (S1.2 predicate, wired in S1.3.)
- *
- * Device numbers (iPhone, iOS 26.5, standalone PWA, 393x852): innerHeight
- * 793, env top 59 (= 852 - 793), env bottom 34, frame bottom 793 flush.
- * The same device in a Safari TAB reads innerHeight 695 with every surface
- * flush and every design value correct, which is what rules our own CSS out.
- *
- * What the true-branch means, settled by S1.2 + S1.3 device evidence: the
- * viewport is anchored at screen y=0 and merely cut 59px short at the BOTTOM
- * — not pushed down below the status bar. So the top inset is paid exactly
- * once and must be left alone, while the bottom inset is a lie: the home
- * indicator lives in the dead strip below the page. installSunkInset() acts
- * on that, and only on --mnav-sab.
- *
- * The `envTop > 0` guard is what keeps every other standalone install out:
- * landscape iPhone (top inset 0, the notch moves to left/right), iPad, and
- * Android — where standalone also loses status-bar height off innerHeight but
- * reports env top 0 — all fall through to false. Kept pure so the boundaries
- * are checkable off-device: scripts/check-sunk-viewport.mjs.
+ * All mobile styles, concatenated in the exact order of the original
+ * single-file stylesheet (base → layout → compat → misc, where misc keeps
+ * composer → tablet → desktop), followed by the phone app shell (home), the
+ * session-header reflow (header), the composer reflow (composer), and the
+ * session-info sheet (info, which must come last of all: it re-shows a
+ * header.utilities child header.css.ts hides by default, so its rule has to
+ * win that tie too), the turn-process fold (turn-fold, S8, which shares no
+ * selector with any of them), and finally the chips row / settings entry /
+ * portal fix (chips, S5) — all appended in this order so their <768px rules
+ * win ties against the shared <=1023px block, then the chat markdown
+ * readability overrides (content, which shares no selector with any of
+ * them). Injected as ONE <style data-plugin> tag — do not reorder.
  */
-function isViewportSunkBelowStatusBar(input) {
-    return input.standalone
-        && input.envTop > 0
-        && input.screenHeight - input.innerHeight >= input.envTop;
-}
+exports.MOBILE_CSS = [base_css_ts_1.BASE_CSS, layout_css_ts_1.LAYOUT_CSS, compat_css_ts_1.COMPAT_CSS, misc_css_ts_1.MISC_CSS, home_css_ts_1.HOME_CSS, header_css_ts_1.HEADER_CSS, composer_css_ts_1.COMPOSER_CSS, info_css_ts_1.INFO_CSS, turn_fold_css_ts_1.TURN_FOLD_CSS, chips_css_ts_1.CHIPS_CSS, content_css_ts_1.CONTENT_CSS].join('\n');
+};
+__modules["debug.js"] = function (require, module, exports) {
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.installDebugBadge = installDebugBadge;
 /**
- * iOS standalone-PWA keyboard shrink (S1.2, 2026-08-17) — the ~60px white
- * band under the composer AND under the session list.
- *
- * Documented WebKit defect: the first time the software keyboard opens inside
- * a home-screen (standalone) PWA, the layout viewport permanently loses the
- * status-bar height for the rest of the app session. innerHeight,
- * visualViewport.height and 100dvh all report the shrunken value together, so
- * nothing inside the page can see anything wrong — the page simply ends early
- * and the strip below it is system background that no CSS can reach. Reported
- * as 932 -> 873 on an iPhone Pro Max; the user's device reads 852 -> 793.
- * Both are exactly one status bar. See
- * https://dev.to/cederhook/fixing-the-ios-standalone-pwa-keyboard-bug-that-shrinks-your-viewport-for-good-63d
- *
- * This is why the reported symptom is asymmetric and why the earlier
- * "double-counted top inset" reading was wrong: the top edge is genuinely
- * correct (env top 59 is paid once, the viewport starts at screen y=0), the
- * bottom is simply 59px short. It also explains a chat client being hit
- * hardest — the trigger is typing, which happens on the first message.
- *
- * The only known cure is to make WebKit re-measure: drop a full-viewport
- * element out of the box tree and force a synchronous reflow. Two departures
- * from the published recipe:
- * - scrollTop is saved and restored around the toggle. Un-boxing an ancestor
- *   resets every descendant scroller to 0, which in a chat client means the
- *   conversation jumps to its first message. Both happen inside one task, so
- *   no frame is ever painted in between and nothing flickers.
- * - the baseline is the tallest innerHeight this session has actually seen,
- *   not the screen height. On any device where the viewport is legitimately
- *   short, the baseline equals the current height and this never fires.
- *
- * Standalone-gated, so a browser tab (and every desktop, CDP included) is a
- * strict no-op — which is also why the fix cannot be regression-tested here
- * and has to be confirmed on the device.
+ * Debug badge — ?mobile-nav-debug=1
+ * Renders a live state overlay (URL, viewport, media queries, shell chrome,
+ * aionui columns, genui cards, captured errors) so a phone-side repro can be
+ * diagnosed without guessing. No-op unless the query param is present.
  */
-function installViewportHeal(ctx) {
+function installDebugBadge(ctx) {
+    /**
+     * Fake safe-area inset — ?mobile-nav-inset=54 or ?mobile-nav-inset=54,34
+     * env(safe-area-inset-*) is hard 0 on every desktop browser (CDP included),
+     * so notch bugs are invisible until a real phone loads the page — the S2.1
+     * hotfix exists because of exactly that. Overriding --mnav-sat / --mnav-sab
+     * (see styles/base.css.ts) on the root element reproduces a notch anywhere.
+     * No param = the variables keep their env() values = zero behaviour change.
+     *
+     * One value fakes the TOP inset only (the historic behaviour — every S1-S3
+     * verification recipe passes `=54`, and they must keep meaning what they
+     * did). A second, comma-separated value fakes the BOTTOM inset too:
+     * `=54,34` is the iPhone notch + home-indicator pair. The bottom half was
+     * added in S4.1 because the home-bar padding it guards (composer clearance
+     * over the indicator) is otherwise untestable off-device for exactly the
+     * same reason the top half exists.
+     */
     ctx.effect(() => {
-        const standalone = window.matchMedia('(display-mode: standalone)').matches
-            || navigator.standalone === true;
-        /* iOS-only on purpose. The ceiling below leans on screen.height being the
-           height the viewport SHOULD have, which holds for an iPhone standalone
-           app under viewport-fit=cover and does not hold on Android, where the
-           navigation bar makes screen.height permanently larger than any viewport
-           and every keyboard dismiss would trigger a pointless reflow. */
-        if (!standalone || !/iPad|iPhone|iPod/.test(navigator.userAgent))
+        const raw = new URLSearchParams(location.search).get('mobile-nav-inset');
+        if (raw === null)
             return () => { };
-        /* Ceiling = the tallest this session has seen, floored at the screen —
-           the screen half matters because the shrink outlives a page reload, so a
-           PWA reopened into the broken state would otherwise measure 793 as
-           "normal" and never heal itself. */
-        let tallest = window.innerHeight;
-        const ceiling = () => Math.max(tallest, window.screen.height);
-        const onResize = () => {
-            if (window.innerHeight > tallest)
-                tallest = window.innerHeight;
-        };
-        /* Give up after three ineffective attempts per trigger: on a device whose
-           viewport is short for a reason a reflow cannot fix (the iOS 26.x
-           standalone regression family) retrying forever buys nothing. The two
-           budgets are separate on purpose — the cold-start attempts would
-           otherwise spend the whole allowance before the user ever types, and the
-           keyboard shrink IS reflow-curable even on a device whose cold start is
-           not. */
-        const strikes = { boot: 0, blur: 0 };
-        const heal = (kind) => {
-            if (strikes[kind] >= 3 || ceiling() - window.innerHeight <= 4)
-                return;
-            const frame = document.querySelector('[data-mobile-nav="frame"]');
-            if (frame === null)
-                return;
-            const scroller = document.querySelector('[class$="_scrollBody"]');
-            const scrollTop = scroller?.scrollTop ?? 0;
-            const previous = frame.style.display;
-            frame.style.display = 'none';
-            void frame.offsetHeight; /* forces the synchronous reflow that re-measures */
-            frame.style.display = previous;
-            if (scroller !== null)
-                scroller.scrollTop = scrollTop;
-            strikes[kind] = ceiling() - window.innerHeight > 4 ? strikes[kind] + 1 : 0;
-        };
-        /* Blur is when the keyboard starts closing; the viewport settles a beat
-           later. Two attempts because the dismiss animation length is not
-           specified anywhere, and a heal that runs too early is a silent no-op. */
-        const timers = [];
-        const onFocusOut = (event) => {
-            if (!(event.target instanceof HTMLElement))
-                return;
-            if (event.target.matches('textarea, input') !== true)
-                return;
-            timers.push(window.setTimeout(() => heal('blur'), 300), window.setTimeout(() => heal('blur'), 900));
+        const [topRaw, bottomRaw] = raw.split(',');
+        const top = Number(topRaw);
+        if (!Number.isFinite(top))
+            return () => { };
+        const root = document.documentElement;
+        root.style.setProperty('--mnav-sat', `${top}px`);
+        const bottom = bottomRaw === undefined ? Number.NaN : Number(bottomRaw);
+        if (Number.isFinite(bottom))
+            root.style.setProperty('--mnav-sab', `${bottom}px`);
+        return () => {
+            root.style.removeProperty('--mnav-sat');
+            root.style.removeProperty('--mnav-sab');
         };
-        /* Cold start (S1.3): the user's iOS 26.5 device is already 59px short on
-           a freshly killed-and-reopened app that never saw the keyboard, so the
-           keyboard trigger alone is not the whole story. Same reflow, tried once
-           the shell has mounted and again after it has settled, plus every return
-           to the foreground — iOS re-lays a backgrounded PWA out and that is
-           another moment the height can come back wrong. Whether a reflow can win
-           against a system-level regression is unknowable off-device; the strike
-           budget is what keeps a losing attempt cheap. */
-        timers.push(window.setTimeout(() => heal('boot'), 1000), window.setTimeout(() => heal('boot'), 3000));
-        const onVisible = () => {
-            if (document.visibilityState !== 'visible')
+    }, 'dsh-mobile-nav: fake safe-area inset');
+    const DEBUG_KEY = 'dsh-mobile-nav.debug';
+    /**
+     * No-URL toggle — 5 quick taps on the home screen's top bar.
+     * A standalone PWA has no address bar, and the paired-device cookie lives
+     * in the PWA's own jar (Safari hits the pairing wall instead), so the
+     * ?mobile-nav-debug=1 param is unreachable exactly where the badge is
+     * needed most.
+     *
+     * The target is deliberately NOT [data-mobile-nav="ws-switch"] any more:
+     * that button opens the workspace sheet on the FIRST tap, so taps 2..5
+     * land on the sheet backdrop, `closest()` misses, and the counter never
+     * reaches five — the original binding only ever fired by luck, and it left
+     * a user stuck inside debug mode with no way back out. The logo img has no
+     * click handler at all; the home-top container minus the switch button is
+     * the fallback for when the icon 404s and the img is not rendered.
+     */
+    ctx.effect(() => {
+        let taps = 0;
+        let firstTap = 0;
+        const onTap = (event) => {
+            if (!(event.target instanceof Element))
                 return;
-            timers.push(window.setTimeout(() => heal('boot'), 300));
-        };
-        window.addEventListener('resize', onResize);
-        document.addEventListener('focusout', onFocusOut, true);
-        document.addEventListener('visibilitychange', onVisible);
-        return () => {
-            window.removeEventListener('resize', onResize);
-            document.removeEventListener('focusout', onFocusOut, true);
-            document.removeEventListener('visibilitychange', onVisible);
-            for (const t of timers)
-                clearTimeout(t);
+            const inTopBar = event.target.closest('[data-mobile-nav="home-logo"]') !== null
+                || (event.target.closest('[data-mobile-nav="home-top"]') !== null
+                    && event.target.closest('[data-mobile-nav="ws-switch"]') === null);
+            if (!inTopBar)
+                return;
+            const now = Date.now();
+            if (now - firstTap > 2500) {
+                taps = 0;
+                firstTap = now;
+            }
+            taps += 1;
+            if (taps >= 5) {
+                if (localStorage.getItem(DEBUG_KEY) === '1')
+                    localStorage.removeItem(DEBUG_KEY);
+                else
+                    localStorage.setItem(DEBUG_KEY, '1');
+                location.reload();
+            }
         };
-    }, 'dsh-mobile-nav: iOS viewport-shrink heal (boot / foreground / keyboard)');
-}
-/**
- * Sunk-viewport compensation (S1.3, 2026-08-17) — zeroes --mnav-sab ONLY.
- *
- * When isViewportSunkBelowStatusBar() holds, the layout viewport is 59px
- * shorter than the screen while env() still reports the full pair of insets.
- * The bottom one is then a lie with a cost: the home indicator sits in the
- * dead strip BELOW the page, so the 34px we reserve for it is 34px of blank
- * page stacked on top of an already-blank system band. Zeroing it does not
- * fix the band (nothing in the page can) but stops us widening it.
- *
- * --mnav-sat is deliberately left alone: the top edge is measured correct on
- * the device (header sits right under the notch), and the S1.2 round already
- * burned a cycle on the theory that it was double-counted.
- *
- * Reversible by design. The predicate is re-evaluated on every resize, so a
- * viewport that comes back to full height — the heal above winning, or Apple
- * shipping the fix — drops the override and the normal env() compensation
- * returns without a reload. `data-mnav-sunk` on <html> is what the debug
- * badge reads, so the badge reports the state that is actually in force
- * rather than re-deriving it.
- */
-function installSunkInset(ctx) {
+        document.addEventListener('click', onTap, true);
+        return () => document.removeEventListener('click', onTap, true);
+    }, 'dsh-mobile-nav: debug badge tap toggle');
     ctx.effect(() => {
-        /* ?mobile-nav-inset outranks this: both write the same inline property on
-           <html>, and the debug param exists precisely to fake insets that this
-           would then erase. Param present = stay out entirely, attribute included,
-           so the badge shows "n/a" instead of a state nobody is enforcing. */
-        if (new URLSearchParams(location.search).has('mobile-nav-inset'))
+        const enabled = new URLSearchParams(location.search).has('mobile-nav-debug')
+            || localStorage.getItem('dsh-mobile-nav.debug') === '1';
+        if (!enabled)
             return () => { };
-        const root = document.documentElement;
-        /* env() is only readable through a real element's computed style. */
+        const errors = [];
+        const onError = (event) => errors.push(`ERR ${event.message.slice(0, 120)}`);
+        const onRejection = (event) => errors.push(`REJ ${String(event.reason).slice(0, 120)}`);
+        window.addEventListener('error', onError);
+        window.addEventListener('unhandledrejection', onRejection);
+        /* Probe element: reads the REAL env(safe-area-inset-*) as computed padding
+           — the --mnav-* vars can be faked by the inset param, this cannot. */
         const probe = document.createElement('div');
         probe.style.cssText =
-            'position:fixed;top:0;left:0;visibility:hidden;pointer-events:none;' +
-                'padding-top:env(safe-area-inset-top,0px)';
+            'position:fixed;visibility:hidden;pointer-events:none;' +
+                'padding-top:env(safe-area-inset-top,0px);padding-bottom:env(safe-area-inset-bottom,0px)';
         document.body.appendChild(probe);
-        const sync = () => {
-            const sunk = isViewportSunkBelowStatusBar({
-                standalone: window.matchMedia('(display-mode: standalone)').matches
-                    || navigator.standalone === true,
-                screenHeight: window.screen.height,
-                innerHeight: window.innerHeight,
-                envTop: Number.parseFloat(getComputedStyle(probe).paddingTop) || 0,
-            });
-            root.dataset.mnavSunk = sunk ? '1' : '0';
-            if (sunk)
-                root.style.setProperty('--mnav-sab', '0px');
-            else
-                root.style.removeProperty('--mnav-sab');
+        const badge = document.createElement('div');
+        badge.style.cssText = [
+            /* Sits BELOW the notch on purpose: at the old flat top:40px the badge
+               painted into the status-bar strip and covered the session header,
+               which read on a screenshot as "the header ran under the notch in
+               debug mode" — a measurement artefact that cost a whole round of
+               diagnosis. env() here, not --mnav-sat: the badge must stay put even
+               when the inset param is faking that variable. */
+            'position:fixed', 'top:calc(env(safe-area-inset-top, 0px) + 8px)', 'right:6px', 'z-index:2147483000',
+            'background:rgba(0,0,0,.82)', 'color:#fff', 'font:11px/1.5 ui-monospace,monospace',
+            'padding:8px 10px', 'border-radius:8px', 'max-width:94vw', 'max-height:70vh',
+            /* pointer-events must be auto for the escape hatch below — with `none`
+               the badge could only be dismissed by editing localStorage, which is
+               not reachable from a standalone PWA. touch-action/user-select keep
+               the double tap from being read as zoom or text selection. */
+            'overflow:auto', 'white-space:pre-wrap', 'pointer-events:auto',
+            'touch-action:manipulation', '-webkit-user-select:none', 'user-select:none',
+        ].join(';');
+        /* Escape hatch: two taps on the badge within 600ms turn debug off. The
+           enable gesture lives on the home screen, which a user deep inside a
+           session cannot reach without first getting out of the way of the badge
+           — so the off switch belongs on the badge itself. */
+        /* The full read-out is tall enough to cover the session list, and with
+           pointer-events:auto (required for the escape hatch) it swallowed every
+           tap under it — the user could not open a session with debug on. The
+           badge therefore starts COLLAPSED (a one-line pill showing vh, the
+           number that matters for the viewport-shrink bug) and only expands on
+           demand. Single tap toggles collapsed/expanded (deferred 620ms so it
+           can be distinguished from the exit gesture); double tap still exits. */
+        let lastTap = 0;
+        let collapsed = true;
+        let singleTapTimer;
+        const onBadgeTap = (event) => {
+            event.preventDefault();
+            event.stopPropagation();
+            const now = Date.now();
+            if (now - lastTap < 600) {
+                if (singleTapTimer !== undefined)
+                    clearTimeout(singleTapTimer);
+                localStorage.removeItem(DEBUG_KEY);
+                const url = new URL(location.href);
+                url.searchParams.delete('mobile-nav-debug');
+                location.replace(url.toString());
+                return;
+            }
+            lastTap = now;
+            singleTapTimer = setTimeout(() => {
+                collapsed = !collapsed;
+                paint();
+            }, 620);
         };
-        sync();
-        /* resize covers rotation and any height the heal above wins back.
-           Deliberately not visualViewport: it fires on every keyboard show/hide
-           while innerHeight, the value read here, does not move on iOS. */
-        window.addEventListener('resize', sync);
-        window.addEventListener('orientationchange', sync);
+        badge.addEventListener('click', onBadgeTap);
+        const read = () => {
+            const q = (sel) => !!document.querySelector(sel);
+            const vis = (sel) => {
+                const el = document.querySelector(sel);
+                return el === null ? 'absent' : getComputedStyle(el).visibility;
+            };
+            const frame = document.querySelector('[data-mobile-nav="frame"]');
+            if (collapsed)
+                return `DBG vh ${innerHeight}/${screen.height} ▸ 单击展开 双击关闭`;
+            return [
+                '▾ 单击收起 · 双击关闭 debug',
+                `URL ${location.pathname}${location.search}`,
+                `W ${innerWidth} x ${innerHeight} dpr ${devicePixelRatio}`,
+                `mq≤1023 ${matchMedia('(max-width: 1023px)').matches}  mq≥1024 ${matchMedia('(min-width: 1024px)').matches}`,
+                `css ${q('style[data-plugin-css*="mobile"]')}  frame ${!!frame}`,
+                `previewCol ${vis('[data-aionui-preview-col]')}  explorerCol ${vis('[data-aionui-explorer-col]')}`,
+                `previewOpen ${frame?.hasAttribute('data-aionui-preview-open') ?? '?'}  explorerOpen ${frame?.hasAttribute('data-aionui-explorer-open') ?? '?'}  previewFull ${frame?.hasAttribute('data-mobile-preview-full') ?? '?'}`,
+                `header ${vis('[data-phase] header')} h${Math.round(document.querySelector('[data-phase] header')?.getBoundingClientRect().height ?? 0)}  composer ${q('textarea')}`,
+                `sat ${getComputedStyle(document.documentElement).getPropertyValue('--mnav-sat').trim() || '?'}  sab ${getComputedStyle(document.documentElement).getPropertyValue('--mnav-sab').trim() || '?'}`,
+                (() => {
+                    /* Bottom-gap forensics: real env values + who ends where. */
+                    const ps = getComputedStyle(probe);
+                    const bottomOf = (sel) => {
+                        const el = document.querySelector(sel);
+                        return el === null ? '—' : String(Math.round(el.getBoundingClientRect().bottom));
+                    };
+                    /* Composer ledger: bottom/gap-to-viewport for every layer between
+                       the textarea and the screen edge, so a "white band under the
+                       composer" screenshot says WHICH layer owns it instead of only
+                       where the textarea ends. Anchors per AGENTS.md: InputBar root is
+                       the padding carrier, _card is the rounded visual box, _composerSeat
+                       is the sticky seat, _scrollBody is the real scroll container. */
+                    const pair = (sel) => {
+                        const el = document.querySelector(sel);
+                        if (el === null)
+                            return '—';
+                        const b = el.getBoundingClientRect().bottom;
+                        return `${Math.round(b)}/${Math.round(innerHeight - b)}`;
+                    };
+                    const barRoot = document.querySelector('[data-slot="conversation.composer.bar"] > [class$="_root"]');
+                    /* Top-edge forensics: rect.top of the surfaces that consume
+                       --mnav-sat. These separate the two competing readings of the
+                       device numbers — a viewport SUNK below the status bar (origin at
+                       screen y=59, so a working sat padding puts the header at 118 and
+                       the top gap is doubled) versus a viewport anchored at screen y=0
+                       that is merely 59px short at the bottom (header at 59, top
+                       correct, the missing 59 showing as a band under the composer).
+                       innerHeight alone cannot tell them apart; the viewport ORIGIN can,
+                       hence screenY / visualViewport offsets / the edge markers. */
+                    const topOf = (sel) => {
+                        const el = document.querySelector(sel);
+                        return el === null ? '—' : String(Math.round(el.getBoundingClientRect().top));
+                    };
+                    const framePadTop = frame === null ? '—' : getComputedStyle(frame).paddingTop;
+                    const vv = window.visualViewport;
+                    return [
+                        `env sat ${ps.paddingTop} sab ${ps.paddingBottom}`,
+                        `screen ${screen.width}x${screen.height} avail ${screen.availWidth}x${screen.availHeight}`,
+                        `vh ${innerHeight} vv ${Math.round(vv?.height ?? -1)} outH ${outerHeight}`,
+                        `scrXY ${screenX},${screenY} vvOff ${Math.round(vv?.offsetTop ?? -1)} vvPage ${Math.round(vv?.pageTop ?? -1)} vvScale ${vv?.scale ?? '?'}`,
+                        /* The ENFORCED state, not a re-derivation: installSunkInset()
+                           stamps data-mnav-sunk, and its absence means the override is
+                           not running at all (the inset param owns the variables). sabOvr
+                           is the receipt — the inline value it wrote, or (env) when the
+                           normal compensation is in force. */
+                        `sunk? ${document.documentElement.dataset.mnavSunk ?? 'n/a'} standalone ${matchMedia('(display-mode: standalone)').matches} sabOvr ${document.documentElement.style.getPropertyValue('--mnav-sab') || '(env)'}`,
+                        `frameTop ${topOf('[data-mobile-nav="frame"]')} padTop ${framePadTop} headerTop ${topOf('[data-phase] header')} homeTopY ${topOf('[data-mobile-nav="home-top"]')}`,
+                        `botFrame ${bottomOf('[data-mobile-nav="frame"]')} composer ${bottomOf('[data-phase] textarea')}`,
+                        `taB ${pair('[data-phase] textarea')} cardB ${pair('[data-slot="conversation.composer.bar"] [class$="_card"]')}`,
+                        `barB ${pair('[data-slot="conversation.composer.bar"] > [class$="_root"]')} seatB ${pair('[class$="_composerSeat"]')} scrollB ${pair('[class$="_scrollBody"]')}`,
+                        `sabPad ${barRoot === null ? '—' : getComputedStyle(barRoot).paddingBottom}`,
+                        `botList ${bottomOf('[data-mobile-nav="home-list"]')} fab ${bottomOf('[data-mobile-nav="home-fab"]')}`,
+                        `cssLen ${document.querySelector('style[data-plugin-css*="mobile"]')?.textContent?.length ?? 0}`,
+                    ].join('\n');
+                })(),
+                `genui cards ${document.querySelectorAll('[data-genui]').length}  panel ${q('[data-genui-panel]')}`,
+                `phase ${document.querySelector('[data-phase]')?.getAttribute('data-phase') ?? '?'}`,
+                `errs ${errors.slice(-5).join(' | ') || 'none'}`,
+            ].join('\n');
+        };
+        /* Feedback-loop guards: painting the badge mutates the body subtree the
+           observer watches — without these two checks the observer retriggers
+           itself forever and freezes the page (the badge was rarely actually
+           enabled before, which is how this survived). */
+        const paint = () => {
+            const next = read();
+            if (next !== badge.textContent)
+                badge.textContent = next;
+        };
+        paint();
+        const observer = new MutationObserver((mutations) => {
+            if (mutations.every((m) => m.target === badge || badge.contains(m.target) || m.target === probe))
+                return;
+            paint();
+        });
+        observer.observe(document.body, { childList: true, subtree: true, attributes: true });
+        const timer = setInterval(paint, 1500);
+        document.body.appendChild(badge);
         return () => {
-            window.removeEventListener('resize', sync);
-            window.removeEventListener('orientationchange', sync);
+            window.removeEventListener('error', onError);
+            window.removeEventListener('unhandledrejection', onRejection);
+            observer.disconnect();
+            clearInterval(timer);
             probe.remove();
-            root.style.removeProperty('--mnav-sab');
-            delete root.dataset.mnavSunk;
+            badge.remove();
         };
-    }, 'dsh-mobile-nav: sunk-viewport bottom-inset override');
+    }, 'dsh-mobile-nav: debug badge');
 }
 };
-__modules["effects/aionui-compat.js"] = function (require, module, exports) {
+__modules["effects/phone-chrome.js"] = function (require, module, exports) {
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.installAionuiCompat = installAionuiCompat;
-/** dsh-web-ui 兼容：explorer / preview 列的显隐标记与升起动画（同域同机制，合并一处）。 */
-function installAionuiCompat(ctx) {
-    // dsh-web-ui compatibility: the aionui explorer column would render as a
-    // sheet over the whole mobile UI whenever its (persisted) expanded state
-    // is active — including right after a reload, with no way out (the
-    // suite's floating expand button only exists while collapsed). Instead
-    // of fighting the suite's store timing, the mobile stylesheet keeps the
-    // explorer column hidden by default and the header's Files action (plus
-    // the drawer footer entry) opens it via the `data-aionui-explorer-open`
-    // marker on the frame. This effect just clears that marker when the
-    // sheet's own collapse chevron is tapped, so closing is symmetric with
-    // opening.
+exports.installPhoneChrome = installPhoneChrome;
+exports.isViewportSunkBelowStatusBar = isViewportSunkBelowStatusBar;
+exports.installViewportHeal = installViewportHeal;
+exports.installSunkInset = installSunkInset;
+/**
+ * Phone chrome: KEEP the system status bar (no fullscreen) and make it
+ * blend into the page. On narrow screens:
+ * - The viewport meta gains viewport-fit=cover, so env(safe-area-inset-top)
+ *   is the real status-bar / notch height and the stylesheet can push every
+ *   surface below it (off notched phones, or in a browser tab where the
+ *   layout viewport already sits below the status bar, the inset is 0 and
+ *   nothing shifts).
+ * - A theme-color meta tracks the shell background (the official theme is
+ *   toggled by body[data-ds-dark-theme], which flips --dsw-alias-bg-base):
+ *   Android then paints the status bar / URL bar with the page's own base
+ *   color, so the status bar reads as part of the UI instead of a foreign
+ *   strip. The drawer paints the same strip on iOS / notch displays.
+ * - gesturestart is suppressed as the legacy-iOS fallback for double-tap
+ *   zoom; modern browsers are covered by the stylesheet's
+ *   touch-action: manipulation (which keeps pan and pinch zoom).
+ */
+function installPhoneChrome(ctx) {
     ctx.effect(() => {
-        // Arm on the CURRENT width and re-arm on every width change: the guard
-        // used to run once at apply time, so a wide→narrow transition (desktop
-        // resize, tablet split view) left the markers dead and the explorer /
-        // preview sheets could neither open nor close properly.
         const narrow = window.matchMedia('(max-width: 1023px)');
-        let cleanup;
-        const install = () => {
-            cleanup?.();
-            if (!narrow.matches) {
-                cleanup = undefined;
-                return;
-            }
-            const onChevronClick = (event) => {
-                const target = event.target;
-                if (target === null || !target.closest('.aionui-collapse-chevron'))
-                    return;
-                document.querySelector('[data-mobile-nav="frame"]')?.removeAttribute('data-aionui-explorer-open');
-            };
-            document.addEventListener('click', onChevronClick, true);
-            cleanup = () => document.removeEventListener('click', onChevronClick, true);
+        const viewport = document.querySelector('meta[name="viewport"]');
+        const originalViewport = viewport?.content ?? '';
+        const themeMeta = document.createElement('meta');
+        themeMeta.name = 'theme-color';
+        const bodyBg = () => getComputedStyle(document.body).backgroundColor;
+        const sync = () => {
+            if (viewport !== null)
+                viewport.content = 'width=device-width, initial-scale=1, viewport-fit=cover';
+            themeMeta.content = bodyBg();
+            if (themeMeta.parentElement === null)
+                document.head.appendChild(themeMeta);
         };
-        install();
-        narrow.addEventListener('change', install);
-        return () => {
-            narrow.removeEventListener('change', install);
-            cleanup?.();
+        const restore = () => {
+            if (viewport !== null)
+                viewport.content = originalViewport;
+            themeMeta.remove();
         };
-    }, 'dsh-mobile-nav: aionui explorer close marker');
-    // dsh-web-ui compatibility: the aionui preview column persists its open
-    // tabs in localStorage and restores them on load, which would pop the
-    // preview sheet over the fresh UI after a reload. Gate it like the
-    // explorer: the stylesheet keeps the column hidden unless the frame
-    // carries `data-aionui-preview-open`; this effect sets that marker when
-    // the user actually taps a file row in the explorer sheet, and clears it
-    // whenever the suite hides the column again (collapse chevron / tab
-    // close), so a restored-but-unwanted sheet never appears.
-    ctx.effect(() => {
-        // Arm on the CURRENT width and re-arm on every width change (see the
-        // explorer marker effect for why).
-        const narrow = window.matchMedia('(max-width: 1023px)');
-        let cleanup;
-        const install = () => {
-            cleanup?.();
-            if (!narrow.matches) {
-                cleanup = undefined;
-                return;
-            }
-            const frame = () => document.querySelector('[data-mobile-nav="frame"]');
-            // Closing the preview sheet also drops the fullscreen marker, so the
-            // next preview starts in the sheet layout again.
-            const closePreview = () => {
-                frame()?.removeAttribute('data-aionui-preview-open');
-                frame()?.removeAttribute('data-mobile-preview-full');
-            };
-            const onTap = (event) => {
-                const target = event.target;
-                if (target === null)
-                    return;
-                const row = target.closest('[data-aionui-explorer-col] [class*="_treeRow"]');
-                if (row === null)
-                    return;
-                // Only FILE rows open the preview sheet. Directory rows toggle
-                // expansion and must not pop the (possibly stale, restored-from-
-                // localStorage) preview tab over the tree. Substring matching:
-                // the suite's hashed classes carry a hash prefix, so the exact-token
-                // `class~=` form never matches and the trailing `$=` form misses
-                // selected rows (`_treeRowSelected`) and open arrows
-                // (`_treeArrowOpen`) — regressions of issue #8. The arrow gate must
-                // additionally exclude the leaf marker: FILE rows render a
-                // `_treeArrowEmpty` span whose class still contains the `_treeArrow`
-                // substring, so a bare substring match would treat every row as a
-                // directory and no preview would ever open.
-                if (row.querySelector('[class*="_treeArrow"]:not([class*="_treeArrowEmpty"])') !== null)
-                    return;
-                frame()?.setAttribute('data-aionui-preview-open', '');
-            };
-            // The preview sheet's own collapse button (the two inward arrows in the
-            // tab bar) closes the AionUI store, but on mobile the suite's layout sync
-            // can be skipped while its shell-track mirror is not ready yet — in that
-            // case the inline visibility never flips to hidden and the visibility
-            // watcher below would never clear our marker. Clear it directly on the
-            // button click so the sheet always closes regardless of the suite's sync.
-            const onCollapse = (event) => {
-                const target = event.target;
-                if (target === null)
-                    return;
-                if (target.closest('[data-aionui-preview-col] [class$="_panelCollapse"]') !== null) {
-                    closePreview();
-                }
-            };
-            const sync = () => {
-                const pv = document.querySelector('[data-aionui-preview-col]');
-                if (pv === null)
-                    return;
-                // Read the suite's inline visibility, not the computed value: while the
-                // `data-aionui-preview-open` marker is present our stylesheet forces the
-                // sheet visible with !important, so getComputedStyle() would never report
-                // hidden and the marker would never be cleared.
-                if (pv.style.visibility === 'hidden')
-                    closePreview();
-            };
-            document.addEventListener('click', onTap, true);
-            document.addEventListener('click', onCollapse, true);
-            const observer = new MutationObserver(sync);
-            observer.observe(document.body, { attributes: true, subtree: true, attributeFilter: ['style'] });
+        const onGestureStart = (event) => event.preventDefault();
+        if (narrow.matches)
             sync();
-            cleanup = () => {
-                document.removeEventListener('click', onTap, true);
-                document.removeEventListener('click', onCollapse, true);
-                observer.disconnect();
-            };
-        };
-        install();
-        narrow.addEventListener('change', install);
-        return () => {
-            narrow.removeEventListener('change', install);
-            cleanup?.();
-        };
-    }, 'dsh-mobile-nav: preview sheet open marker');
-    // The dsh-web-ui explorer / preview columns toggle via `visibility`
-    // (their inline style), which never restarts a CSS animation — so the
-    // sheets would only animate on first mount. Replay the rise animation
-    // with the Web Animations API each time a column turns visible, then
-    // leave the resting state to the stylesheet.
-    ctx.effect(() => {
-        // Arm on the CURRENT width and re-arm on every width change (see the
-        // explorer marker effect for why).
-        const narrow = window.matchMedia('(max-width: 1023px)');
-        let cleanup;
-        const install = () => {
-            cleanup?.();
-            if (!narrow.matches) {
-                cleanup = undefined;
-                return;
-            }
-            const cols = ['[data-aionui-explorer-col]', '[data-aionui-preview-col]'];
-            const seen = new Map();
-            const play = (el) => {
-                el.animate([
-                    { opacity: 0, transform: 'translateY(28px)' },
-                    { opacity: 1, transform: 'none' },
-                ], { duration: 280, easing: 'cubic-bezier(.16, 1, .3, 1)', fill: 'backwards' });
-            };
-            const check = () => {
-                for (const sel of cols) {
-                    const el = document.querySelector(sel);
-                    if (el === null)
-                        continue;
-                    const visible = getComputedStyle(el).visibility === 'visible';
-                    const prev = seen.get(sel) ?? false;
-                    if (visible && !prev)
-                        play(el);
-                    seen.set(sel, visible);
-                }
-            };
-            const observer = new MutationObserver(check);
-            // Visibility flips come through inline style mutations (suite) or the
-            // explorer-open marker on the frame; class changes are watched too.
-            observer.observe(document.body, { attributes: true, subtree: true, attributeFilter: ['style', 'class', 'data-aionui-explorer-open'] });
-            check();
-            cleanup = () => {
-                observer.disconnect();
-            };
-        };
-        install();
-        narrow.addEventListener('change', install);
+        const onChange = (event) => (event.matches ? sync() : restore());
+        narrow.addEventListener('change', onChange);
+        const observer = new MutationObserver(() => {
+            if (narrow.matches)
+                themeMeta.content = bodyBg();
+        });
+        observer.observe(document.body, { attributes: true, attributeFilter: ['data-ds-dark-theme'] });
+        document.addEventListener('gesturestart', onGestureStart);
         return () => {
-            narrow.removeEventListener('change', install);
-            cleanup?.();
+            narrow.removeEventListener('change', onChange);
+            observer.disconnect();
+            document.removeEventListener('gesturestart', onGestureStart);
+            restore();
         };
-    }, 'dsh-mobile-nav: sheet rise animation replay');
+    }, 'dsh-mobile-nav: status bar theme + viewport + zoom guard');
+}
+/**
+ * Does the layout viewport sit shorter than the screen by at least the top
+ * inset env() still claims? (S1.2 predicate, wired in S1.3.)
+ *
+ * Device numbers (iPhone, iOS 26.5, standalone PWA, 393x852): innerHeight
+ * 793, env top 59 (= 852 - 793), env bottom 34, frame bottom 793 flush.
+ * The same device in a Safari TAB reads innerHeight 695 with every surface
+ * flush and every design value correct, which is what rules our own CSS out.
+ *
+ * What the true-branch means, settled by S1.2 + S1.3 device evidence: the
+ * viewport is anchored at screen y=0 and merely cut 59px short at the BOTTOM
+ * — not pushed down below the status bar. So the top inset is paid exactly
+ * once and must be left alone, while the bottom inset is a lie: the home
+ * indicator lives in the dead strip below the page. installSunkInset() acts
+ * on that, and only on --mnav-sab.
+ *
+ * The `envTop > 0` guard is what keeps every other standalone install out:
+ * landscape iPhone (top inset 0, the notch moves to left/right), iPad, and
+ * Android — where standalone also loses status-bar height off innerHeight but
+ * reports env top 0 — all fall through to false. Kept pure so the boundaries
+ * are checkable off-device: scripts/check-sunk-viewport.mjs.
+ */
+function isViewportSunkBelowStatusBar(input) {
+    return input.standalone
+        && input.envTop > 0
+        && input.screenHeight - input.innerHeight >= input.envTop;
 }
-};
-__modules["effects/header-status.js"] = function (require, module, exports) {
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.installHeaderStatusDot = installHeaderStatusDot;
-const session_dot_ts_1 = require("./session-dot.js");
 /**
- * Session header running-status dot (S2). No official element exists to
- * reposition (ConversationSessionHeader renders only the crumb title, the
- * actions/utilities slots, and the tablist — dsh-client-ui-conversation
- * lib/client.js:6949-7009), so this reads `ctx.sessions.list` directly
- * (the same feed `useSessions` wraps) and stamps a data attribute the
- * mobile stylesheet turns into a `::after` dot on the title crumb —
- * "read data, self-draw" is the plan's documented fallback for this piece.
- * Kept outside React: the dot must track the CURRENT session regardless of
- * which component the header happens to mount, and a plain attribute +
- * CSS avoids reaching into the official crumb's own DOM subtree.
+ * iOS standalone-PWA keyboard shrink (S1.2, 2026-08-17) — the ~60px white
+ * band under the composer AND under the session list.
+ *
+ * Documented WebKit defect: the first time the software keyboard opens inside
+ * a home-screen (standalone) PWA, the layout viewport permanently loses the
+ * status-bar height for the rest of the app session. innerHeight,
+ * visualViewport.height and 100dvh all report the shrunken value together, so
+ * nothing inside the page can see anything wrong — the page simply ends early
+ * and the strip below it is system background that no CSS can reach. Reported
+ * as 932 -> 873 on an iPhone Pro Max; the user's device reads 852 -> 793.
+ * Both are exactly one status bar. See
+ * https://dev.to/cederhook/fixing-the-ios-standalone-pwa-keyboard-bug-that-shrinks-your-viewport-for-good-63d
+ *
+ * This is why the reported symptom is asymmetric and why the earlier
+ * "double-counted top inset" reading was wrong: the top edge is genuinely
+ * correct (env top 59 is paid once, the viewport starts at screen y=0), the
+ * bottom is simply 59px short. It also explains a chat client being hit
+ * hardest — the trigger is typing, which happens on the first message.
+ *
+ * The only known cure is to make WebKit re-measure: drop a full-viewport
+ * element out of the box tree and force a synchronous reflow. Two departures
+ * from the published recipe:
+ * - scrollTop is saved and restored around the toggle. Un-boxing an ancestor
+ *   resets every descendant scroller to 0, which in a chat client means the
+ *   conversation jumps to its first message. Both happen inside one task, so
+ *   no frame is ever painted in between and nothing flickers.
+ * - the baseline is the tallest innerHeight this session has actually seen,
+ *   not the screen height. On any device where the viewport is legitimately
+ *   short, the baseline equals the current height and this never fires.
+ *
+ * Standalone-gated, so a browser tab (and every desktop, CDP included) is a
+ * strict no-op — which is also why the fix cannot be regression-tested here
+ * and has to be confirmed on the device.
  */
-function installHeaderStatusDot(ctx) {
+function installViewportHeal(ctx) {
     ctx.effect(() => {
-        const apply = () => {
+        const standalone = window.matchMedia('(display-mode: standalone)').matches
+            || navigator.standalone === true;
+        /* iOS-only on purpose. The ceiling below leans on screen.height being the
+           height the viewport SHOULD have, which holds for an iPhone standalone
+           app under viewport-fit=cover and does not hold on Android, where the
+           navigation bar makes screen.height permanently larger than any viewport
+           and every keyboard dismiss would trigger a pointless reflow. */
+        if (!standalone || !/iPad|iPhone|iPod/.test(navigator.userAgent))
+            return () => { };
+        /* Ceiling = the tallest this session has seen, floored at the screen —
+           the screen half matters because the shrink outlives a page reload, so a
+           PWA reopened into the broken state would otherwise measure 793 as
+           "normal" and never heal itself. */
+        let tallest = window.innerHeight;
+        const ceiling = () => Math.max(tallest, window.screen.height);
+        const onResize = () => {
+            if (window.innerHeight > tallest)
+                tallest = window.innerHeight;
+        };
+        /* Give up after three ineffective attempts per trigger: on a device whose
+           viewport is short for a reason a reflow cannot fix (the iOS 26.x
+           standalone regression family) retrying forever buys nothing. The two
+           budgets are separate on purpose — the cold-start attempts would
+           otherwise spend the whole allowance before the user ever types, and the
+           keyboard shrink IS reflow-curable even on a device whose cold start is
+           not. */
+        const strikes = { boot: 0, blur: 0 };
+        const heal = (kind) => {
+            if (strikes[kind] >= 3 || ceiling() - window.innerHeight <= 4)
+                return;
             const frame = document.querySelector('[data-mobile-nav="frame"]');
             if (frame === null)
                 return;
-            const { current, byId } = ctx.sessions.list.getSnapshot();
-            const row = current === undefined ? undefined : byId[current];
-            const state = row === undefined ? undefined : (0, session_dot_ts_1.dotState)(row);
-            if (state === undefined)
-                frame.removeAttribute('data-mobile-nav-dot');
-            else
-                frame.setAttribute('data-mobile-nav-dot', state);
+            const scroller = document.querySelector('[class$="_scrollBody"]');
+            const scrollTop = scroller?.scrollTop ?? 0;
+            const previous = frame.style.display;
+            frame.style.display = 'none';
+            void frame.offsetHeight; /* forces the synchronous reflow that re-measures */
+            frame.style.display = previous;
+            if (scroller !== null)
+                scroller.scrollTop = scrollTop;
+            strikes[kind] = ceiling() - window.innerHeight > 4 ? strikes[kind] + 1 : 0;
         };
-        apply();
-        return ctx.sessions.list.subscribe(apply);
-    }, 'dsh-mobile-nav: header status dot');
-}
-};
-__modules["effects/gestures.js"] = function (require, module, exports) {
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.installGestures = installGestures;
-const nav_store_ts_1 = require("./nav-store.js");
-/** Phone breakpoint — same query every phone-only effect in this plugin uses. */
-const PHONE_QUERY = '(max-width: 767px)';
-/** This plugin's two dismissible sheets (session-info, home workspace/chips
- * picker — MobileHome.tsx's home-sheet hosts both the workspace switcher and
- * the S5 chip-customize list under the same marker). Official popupSelect
- * menus (permission/model) are deliberately excluded — the design spec
- * leaves those mask-tap-only, and they are the suite's own DOM, not ours to
- * add gesture handling to. */
-const SHEET_SELECTOR = '[data-mobile-nav="info-sheet"], [data-mobile-nav="home-sheet"]';
-const CLOSE_DISTANCE = 80;
-/** px/ms — a fast flick closes the sheet even short of CLOSE_DISTANCE. */
-const CLOSE_VELOCITY = 0.5;
-/** Below this the drag is a tap/jitter, not yet a pull — avoids hijacking
- * the very first pixels of an upward scroll inside the sheet. */
-const DRAG_COMMIT_PX = 4;
-function prefersReducedMotion() {
-    return window.matchMedia('(prefers-reduced-motion: reduce)').matches;
-}
-/** The sheet's own mask sibling — both this plugin's sheets name theirs
- * with a "-mask" suffix (info-mask, home-sheet-mask) and already wire a
- * click handler that calls the sheet's close(). Reusing that handler (a
- * synthetic click) needs no access to the sheet's React state at all.
- * Shared with the S6.1 edge-swipe-back priority chain below — both "drag
- * down to dismiss" and "swipe back from the edge" close a sheet the exact
- * same way. */
-function closeSheet(sheet) {
-    sheet.parentElement?.querySelector('[data-mobile-nav$="-mask"]')?.click();
+        /* Blur is when the keyboard starts closing; the viewport settles a beat
+           later. Two attempts because the dismiss animation length is not
+           specified anywhere, and a heal that runs too early is a silent no-op. */
+        const timers = [];
+        const onFocusOut = (event) => {
+            if (!(event.target instanceof HTMLElement))
+                return;
+            if (event.target.matches('textarea, input') !== true)
+                return;
+            timers.push(window.setTimeout(() => heal('blur'), 300), window.setTimeout(() => heal('blur'), 900));
+        };
+        /* Cold start (S1.3): the user's iOS 26.5 device is already 59px short on
+           a freshly killed-and-reopened app that never saw the keyboard, so the
+           keyboard trigger alone is not the whole story. Same reflow, tried once
+           the shell has mounted and again after it has settled, plus every return
+           to the foreground — iOS re-lays a backgrounded PWA out and that is
+           another moment the height can come back wrong. Whether a reflow can win
+           against a system-level regression is unknowable off-device; the strike
+           budget is what keeps a losing attempt cheap. */
+        timers.push(window.setTimeout(() => heal('boot'), 1000), window.setTimeout(() => heal('boot'), 3000));
+        const onVisible = () => {
+            if (document.visibilityState !== 'visible')
+                return;
+            timers.push(window.setTimeout(() => heal('boot'), 300));
+        };
+        window.addEventListener('resize', onResize);
+        document.addEventListener('focusout', onFocusOut, true);
+        document.addEventListener('visibilitychange', onVisible);
+        return () => {
+            window.removeEventListener('resize', onResize);
+            document.removeEventListener('focusout', onFocusOut, true);
+            document.removeEventListener('visibilitychange', onVisible);
+            for (const t of timers)
+                clearTimeout(t);
+        };
+    }, 'dsh-mobile-nav: iOS viewport-shrink heal (boot / foreground / keyboard)');
 }
 /**
- * S6.2 — sheet drag-to-close: this plugin's two own bottom sheets (session
- * info, home workspace picker) support "drag down to dismiss", mirroring
- * the mask-tap close they already have. Official popupSelect menus
- * (permission/model) are excluded on purpose — the design spec leaves them
- * mask-tap-only, and they are the suite's own DOM, not ours to add gesture
- * handling to.
+ * Sunk-viewport compensation (S1.3, 2026-08-17) — zeroes --mnav-sab ONLY.
  *
- * touchmove is registered non-passive (unlike the edge-swipe-back gesture
- * below) because this gesture needs to preventDefault once it takes over, so
- * the sheet's own translateY tracks the finger instead of fighting the
- * scroller's native rubber-band. Before that handoff — while the sheet's
- * inner content isn't scrolled to top — nothing is intercepted at all, so
- * a pull down first scrolls the content as normal (spec requirement).
+ * When isViewportSunkBelowStatusBar() holds, the layout viewport is 59px
+ * shorter than the screen while env() still reports the full pair of insets.
+ * The bottom one is then a lie with a cost: the home indicator sits in the
+ * dead strip BELOW the page, so the 34px we reserve for it is 34px of blank
+ * page stacked on top of an already-blank system band. Zeroing it does not
+ * fix the band (nothing in the page can) but stops us widening it.
+ *
+ * --mnav-sat is deliberately left alone: the top edge is measured correct on
+ * the device (header sits right under the notch), and the S1.2 round already
+ * burned a cycle on the theory that it was double-counted.
+ *
+ * Reversible by design. The predicate is re-evaluated on every resize, so a
+ * viewport that comes back to full height — the heal above winning, or Apple
+ * shipping the fix — drops the override and the normal env() compensation
+ * returns without a reload. `data-mnav-sunk` on <html> is what the debug
+ * badge reads, so the badge reports the state that is actually in force
+ * rather than re-deriving it.
  */
-function installSheetDragClose(ctx) {
+function installSunkInset(ctx) {
+    ctx.effect(() => {
+        /* ?mobile-nav-inset outranks this: both write the same inline property on
+           <html>, and the debug param exists precisely to fake insets that this
+           would then erase. Param present = stay out entirely, attribute included,
+           so the badge shows "n/a" instead of a state nobody is enforcing. */
+        if (new URLSearchParams(location.search).has('mobile-nav-inset'))
+            return () => { };
+        const root = document.documentElement;
+        /* env() is only readable through a real element's computed style. */
+        const probe = document.createElement('div');
+        probe.style.cssText =
+            'position:fixed;top:0;left:0;visibility:hidden;pointer-events:none;' +
+                'padding-top:env(safe-area-inset-top,0px)';
+        document.body.appendChild(probe);
+        const sync = () => {
+            const sunk = isViewportSunkBelowStatusBar({
+                standalone: window.matchMedia('(display-mode: standalone)').matches
+                    || navigator.standalone === true,
+                screenHeight: window.screen.height,
+                innerHeight: window.innerHeight,
+                envTop: Number.parseFloat(getComputedStyle(probe).paddingTop) || 0,
+            });
+            root.dataset.mnavSunk = sunk ? '1' : '0';
+            if (sunk)
+                root.style.setProperty('--mnav-sab', '0px');
+            else
+                root.style.removeProperty('--mnav-sab');
+        };
+        sync();
+        /* resize covers rotation and any height the heal above wins back.
+           Deliberately not visualViewport: it fires on every keyboard show/hide
+           while innerHeight, the value read here, does not move on iOS. */
+        window.addEventListener('resize', sync);
+        window.addEventListener('orientationchange', sync);
+        return () => {
+            window.removeEventListener('resize', sync);
+            window.removeEventListener('orientationchange', sync);
+            probe.remove();
+            root.style.removeProperty('--mnav-sab');
+            delete root.dataset.mnavSunk;
+        };
+    }, 'dsh-mobile-nav: sunk-viewport bottom-inset override');
+}
+};
+__modules["effects/aionui-compat.js"] = function (require, module, exports) {
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.installAionuiCompat = installAionuiCompat;
+/** dsh-web-ui 兼容：explorer / preview 列的显隐标记与升起动画（同域同机制，合并一处）。 */
+function installAionuiCompat(ctx) {
+    // dsh-web-ui compatibility: the aionui explorer column would render as a
+    // sheet over the whole mobile UI whenever its (persisted) expanded state
+    // is active — including right after a reload, with no way out (the
+    // suite's floating expand button only exists while collapsed). Instead
+    // of fighting the suite's store timing, the mobile stylesheet keeps the
+    // explorer column hidden by default and the header's Files action (plus
+    // the drawer footer entry) opens it via the `data-aionui-explorer-open`
+    // marker on the frame. This effect just clears that marker when the
+    // sheet's own collapse chevron is tapped, so closing is symmetric with
+    // opening.
     ctx.effect(() => {
-        const narrow = window.matchMedia(PHONE_QUERY);
-        let drag = null;
-        const settle = (sheet, close) => {
-            if (close) {
-                sheet.style.transform = '';
-                sheet.style.transition = '';
-                closeSheet(sheet);
-                return;
-            }
-            if (prefersReducedMotion()) {
-                sheet.style.transition = 'none';
-                sheet.style.transform = '';
+        // Arm on the CURRENT width and re-arm on every width change: the guard
+        // used to run once at apply time, so a wide→narrow transition (desktop
+        // resize, tablet split view) left the markers dead and the explorer /
+        // preview sheets could neither open nor close properly.
+        const narrow = window.matchMedia('(max-width: 1023px)');
+        let cleanup;
+        const install = () => {
+            cleanup?.();
+            if (!narrow.matches) {
+                cleanup = undefined;
                 return;
             }
-            sheet.style.transition = 'transform .22s var(--ds-ease-out, ease-in-out)';
-            sheet.style.transform = '';
-            const clear = () => {
-                sheet.style.transition = '';
-                sheet.removeEventListener('transitionend', clear);
+            const onChevronClick = (event) => {
+                const target = event.target;
+                if (target === null || !target.closest('.aionui-collapse-chevron'))
+                    return;
+                document.querySelector('[data-mobile-nav="frame"]')?.removeAttribute('data-aionui-explorer-open');
             };
-            sheet.addEventListener('transitionend', clear);
+            document.addEventListener('click', onChevronClick, true);
+            cleanup = () => document.removeEventListener('click', onChevronClick, true);
         };
-        const onTouchStart = (event) => {
-            if (event.touches.length !== 1) {
-                drag = null;
-                return;
-            }
-            const touch = event.touches[0];
-            const target = event.target;
-            if (touch === undefined || !(target instanceof Element)) {
-                drag = null;
-                return;
-            }
-            const sheet = target.closest(SHEET_SELECTOR);
-            if (sheet === null) {
-                drag = null;
-                return;
-            }
-            drag = { sheet, startY: touch.clientY, lastY: touch.clientY, startTime: Date.now(), dragging: false };
+        install();
+        narrow.addEventListener('change', install);
+        return () => {
+            narrow.removeEventListener('change', install);
+            cleanup?.();
         };
-        const onTouchMove = (event) => {
-            if (drag === null)
-                return;
-            const touch = event.touches[0];
-            if (touch === undefined)
+    }, 'dsh-mobile-nav: aionui explorer close marker');
+    // dsh-web-ui compatibility: the aionui preview column persists its open
+    // tabs in localStorage and restores them on load, which would pop the
+    // preview sheet over the fresh UI after a reload. Gate it like the
+    // explorer: the stylesheet keeps the column hidden unless the frame
+    // carries `data-aionui-preview-open`; this effect sets that marker when
+    // the user actually taps a file row in the explorer sheet, and clears it
+    // whenever the suite hides the column again (collapse chevron / tab
+    // close), so a restored-but-unwanted sheet never appears.
+    ctx.effect(() => {
+        // Arm on the CURRENT width and re-arm on every width change (see the
+        // explorer marker effect for why).
+        const narrow = window.matchMedia('(max-width: 1023px)');
+        let cleanup;
+        const install = () => {
+            cleanup?.();
+            if (!narrow.matches) {
+                cleanup = undefined;
                 return;
-            drag.lastY = touch.clientY;
-            const dy = touch.clientY - drag.startY;
-            if (!drag.dragging) {
-                if (drag.sheet.scrollTop > 0)
+            }
+            const frame = () => document.querySelector('[data-mobile-nav="frame"]');
+            // Closing the preview sheet also drops the fullscreen marker, so the
+            // next preview starts in the sheet layout again.
+            const closePreview = () => {
+                frame()?.removeAttribute('data-aionui-preview-open');
+                frame()?.removeAttribute('data-mobile-preview-full');
+            };
+            const onTap = (event) => {
+                const target = event.target;
+                if (target === null)
                     return;
-                if (dy <= DRAG_COMMIT_PX)
+                const row = target.closest('[data-aionui-explorer-col] [class*="_treeRow"]');
+                if (row === null)
                     return;
-                drag.dragging = true;
-                drag.sheet.style.transition = 'none';
-            }
-            event.preventDefault();
-            drag.sheet.style.transform = `translateY(${Math.max(0, dy)}px)`;
-        };
-        const finish = () => {
-            if (drag === null)
-                return;
-            const { sheet, dragging, startY, lastY, startTime } = drag;
-            drag = null;
-            if (!dragging)
-                return;
-            const dy = Math.max(0, lastY - startY);
-            const elapsed = Math.max(1, Date.now() - startTime);
-            const velocity = dy / elapsed;
-            settle(sheet, dy > CLOSE_DISTANCE || velocity > CLOSE_VELOCITY);
-        };
-        const attach = () => {
-            document.addEventListener('touchstart', onTouchStart, { passive: true });
-            document.addEventListener('touchmove', onTouchMove, { passive: false });
-            document.addEventListener('touchend', finish, { passive: true });
-            document.addEventListener('touchcancel', finish, { passive: true });
-        };
-        const detach = () => {
-            document.removeEventListener('touchstart', onTouchStart);
-            document.removeEventListener('touchmove', onTouchMove);
-            document.removeEventListener('touchend', finish);
-            document.removeEventListener('touchcancel', finish);
-            drag = null;
-        };
-        if (narrow.matches)
-            attach();
-        const onChange = (event) => (event.matches ? attach() : detach());
-        narrow.addEventListener('change', onChange);
-        return () => {
-            narrow.removeEventListener('change', onChange);
-            detach();
-        };
-    }, 'dsh-mobile-nav: sheet drag-to-close');
-}
-/** Left-edge start zone for S6.1's swipe-back, in CSS px from the viewport's
- * left edge. This used to be the gateway half's own edge-swipe-back hot zone
- * (history.back, useless against an SPA) — that gesture is removed in the
- * same revision that adds this one, so the 24px strip changes owner instead
- * of staying carved out (design doc "手势" row, 2026-08-17 fourth revision). */
-const EDGE_ZONE_PX = 24;
-const EDGE_SWIPE_MIN_DX = 90;
-const EDGE_SWIPE_RATIO = 1.6;
-/**
- * dsh-better-sidebar's panel-open read (AGENTS.md pitfall "第三方浮层的开合
- * 态可以纯 CSS `:has()` 读"): the panel's class ends in "_panel" only while
- * open — "_panelHidden" is appended once closed, so the string no longer
- * ends in "_panel" and this selector stops matching. Same anchor
- * MobileSessionHeader.tsx's workbench button and its own close button use.
- */
-function betterSidebarPanelOpen() {
-    return document.querySelector('[data-dsh-better-sidebar] [class$="_panel"]') !== null;
-}
-/**
- * S6.1 — left-edge swipe-back priority chain (design doc "手势" row, fourth
- * revision): a swipe starting in the left {@link EDGE_ZONE_PX} always closes
- * the TOPMOST dismissible surface rather than always navigating, so a user
- * mid-workflow (info card open, workbench panel open) gets "close that"
- * instead of "leave the session" from the same gesture. Checked in the
- * design doc's own order:
- *   1. this plugin's session-info sheet, if open
- *   2. this plugin's home sheet (workspace switcher or S5 chip-customize),
- *      if open
- *   3. dsh-better-sidebar's workbench panel, if open (代点 its own toggle —
- *      same anchor MobileSessionHeader.tsx's workbench/close buttons use)
- *   4. otherwise, GO_HOME_EVENT — but only from the session view; the design
- *      doc calls out "在 home 层→无动作" explicitly, and the phone page
- *      stack's current level is read straight off MobileHome's own
- *      `data-view` attribute (no store handle needed here — effects/*.ts is
- *      already all DOM reads, matching every sibling effect in this file).
- */
-function handleEdgeSwipeBack() {
-    const sheet = document.querySelector(SHEET_SELECTOR);
-    if (sheet !== null) {
-        closeSheet(sheet);
-        return;
-    }
-    if (betterSidebarPanelOpen()) {
-        document.querySelector('[data-dsh-better-sidebar] button[class$="_toggleButton"]')?.click();
-        return;
-    }
-    if (document.querySelector('[data-mobile-nav="home"]')?.getAttribute('data-view') === 'session') {
-        window.dispatchEvent(new CustomEvent(nav_store_ts_1.GO_HOME_EVENT));
-    }
-}
-/**
- * S6.1 — left-edge swipe-back gesture install. Passive throughout (never
- * calls preventDefault) and decided purely from the touchstart/touchend
- * endpoints, exactly like the S6.1-predecessor content-area swipe this
- * revision removes — so it never fights vertical (or, at the 24px strip,
- * horizontal chip-row) scrolling, and needs no mid-drag tracking: the design
- * doc explicitly allows "一步到位" over a followed-finger animation.
- */
-function installEdgeSwipeBack(ctx) {
+                // Only FILE rows open the preview sheet. Directory rows toggle
+                // expansion and must not pop the (possibly stale, restored-from-
+                // localStorage) preview tab over the tree. Substring matching:
+                // the suite's hashed classes carry a hash prefix, so the exact-token
+                // `class~=` form never matches and the trailing `$=` form misses
+                // selected rows (`_treeRowSelected`) and open arrows
+                // (`_treeArrowOpen`) — regressions of issue #8. The arrow gate must
+                // additionally exclude the leaf marker: FILE rows render a
+                // `_treeArrowEmpty` span whose class still contains the `_treeArrow`
+                // substring, so a bare substring match would treat every row as a
+                // directory and no preview would ever open.
+                if (row.querySelector('[class*="_treeArrow"]:not([class*="_treeArrowEmpty"])') !== null)
+                    return;
+                frame()?.setAttribute('data-aionui-preview-open', '');
+            };
+            // The preview sheet's own collapse button (the two inward arrows in the
+            // tab bar) closes the AionUI store, but on mobile the suite's layout sync
+            // can be skipped while its shell-track mirror is not ready yet — in that
+            // case the inline visibility never flips to hidden and the visibility
+            // watcher below would never clear our marker. Clear it directly on the
+            // button click so the sheet always closes regardless of the suite's sync.
+            const onCollapse = (event) => {
+                const target = event.target;
+                if (target === null)
+                    return;
+                if (target.closest('[data-aionui-preview-col] [class$="_panelCollapse"]') !== null) {
+                    closePreview();
+                }
+            };
+            const sync = () => {
+                const pv = document.querySelector('[data-aionui-preview-col]');
+                if (pv === null)
+                    return;
+                // Read the suite's inline visibility, not the computed value: while the
+                // `data-aionui-preview-open` marker is present our stylesheet forces the
+                // sheet visible with !important, so getComputedStyle() would never report
+                // hidden and the marker would never be cleared.
+                if (pv.style.visibility === 'hidden')
+                    closePreview();
+            };
+            document.addEventListener('click', onTap, true);
+            document.addEventListener('click', onCollapse, true);
+            const observer = new MutationObserver(sync);
+            observer.observe(document.body, { attributes: true, subtree: true, attributeFilter: ['style'] });
+            sync();
+            cleanup = () => {
+                document.removeEventListener('click', onTap, true);
+                document.removeEventListener('click', onCollapse, true);
+                observer.disconnect();
+            };
+        };
+        install();
+        narrow.addEventListener('change', install);
+        return () => {
+            narrow.removeEventListener('change', install);
+            cleanup?.();
+        };
+    }, 'dsh-mobile-nav: preview sheet open marker');
+    // The dsh-web-ui explorer / preview columns toggle via `visibility`
+    // (their inline style), which never restarts a CSS animation — so the
+    // sheets would only animate on first mount. Replay the rise animation
+    // with the Web Animations API each time a column turns visible, then
+    // leave the resting state to the stylesheet.
     ctx.effect(() => {
-        const narrow = window.matchMedia(PHONE_QUERY);
-        let start = null;
-        const onTouchStart = (event) => {
-            if (event.touches.length !== 1) {
-                start = null;
-                return;
-            }
-            const touch = event.touches[0];
-            if (touch === undefined) {
-                start = null;
+        // Arm on the CURRENT width and re-arm on every width change (see the
+        // explorer marker effect for why).
+        const narrow = window.matchMedia('(max-width: 1023px)');
+        let cleanup;
+        const install = () => {
+            cleanup?.();
+            if (!narrow.matches) {
+                cleanup = undefined;
                 return;
             }
-            start = { x: touch.clientX, y: touch.clientY, eligible: touch.clientX <= EDGE_ZONE_PX };
-        };
-        const onTouchEnd = (event) => {
-            const state = start;
-            start = null;
-            if (state === null || !state.eligible)
-                return;
-            const touch = event.changedTouches[0];
-            if (touch === undefined)
-                return;
-            const dx = touch.clientX - state.x;
-            const dy = touch.clientY - state.y;
-            if (dx <= EDGE_SWIPE_MIN_DX || Math.abs(dx) <= EDGE_SWIPE_RATIO * Math.abs(dy))
-                return;
-            handleEdgeSwipeBack();
-        };
-        const attach = () => {
-            document.addEventListener('touchstart', onTouchStart, { passive: true });
-            document.addEventListener('touchend', onTouchEnd, { passive: true });
-        };
-        const detach = () => {
-            document.removeEventListener('touchstart', onTouchStart);
-            document.removeEventListener('touchend', onTouchEnd);
-            start = null;
+            const cols = ['[data-aionui-explorer-col]', '[data-aionui-preview-col]'];
+            const seen = new Map();
+            const play = (el) => {
+                el.animate([
+                    { opacity: 0, transform: 'translateY(28px)' },
+                    { opacity: 1, transform: 'none' },
+                ], { duration: 280, easing: 'cubic-bezier(.16, 1, .3, 1)', fill: 'backwards' });
+            };
+            const check = () => {
+                for (const sel of cols) {
+                    const el = document.querySelector(sel);
+                    if (el === null)
+                        continue;
+                    const visible = getComputedStyle(el).visibility === 'visible';
+                    const prev = seen.get(sel) ?? false;
+                    if (visible && !prev)
+                        play(el);
+                    seen.set(sel, visible);
+                }
+            };
+            const observer = new MutationObserver(check);
+            // Visibility flips come through inline style mutations (suite) or the
+            // explorer-open marker on the frame; class changes are watched too.
+            observer.observe(document.body, { attributes: true, subtree: true, attributeFilter: ['style', 'class', 'data-aionui-explorer-open'] });
+            check();
+            cleanup = () => {
+                observer.disconnect();
+            };
         };
-        if (narrow.matches)
-            attach();
-        const onChange = (event) => (event.matches ? attach() : detach());
-        narrow.addEventListener('change', onChange);
+        install();
+        narrow.addEventListener('change', install);
         return () => {
-            narrow.removeEventListener('change', onChange);
-            detach();
+            narrow.removeEventListener('change', install);
+            cleanup?.();
         };
-    }, 'dsh-mobile-nav: left-edge swipe-back');
-}
-/** S6: the two-gesture set — left-edge swipe-back and sheet drag-to-close.
- * Both install/uninstall their own document listeners on the phone
- * breakpoint's matchMedia change, so at >= 768px this is a true no-op (no
- * listeners attached at all), matching every other effect in this file. */
-function installGestures(ctx) {
-    installEdgeSwipeBack(ctx);
-    installSheetDragClose(ctx);
+    }, 'dsh-mobile-nav: sheet rise animation replay');
 }
 };
-__modules["locales.js"] = function (require, module, exports) {
+__modules["effects/header-status.js"] = function (require, module, exports) {
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.en = exports.zh = exports.NS = void 0;
-/** `mobileNav` namespace dictionaries: drawer controls. */
-exports.NS = 'mobileNav';
-/** Simplified Chinese dictionary (the key-set source of truth). */
-exports.zh = {
-    'open': '打开目录',
-    'close': '收起目录',
-    'backdrop': '点击关闭目录',
-    'sessionLog': '导出会话日志',
-    'files': '文件浏览',
-    'previewFullscreen': '全屏预览',
-    'previewExitFullscreen': '退出全屏',
-    'allWorkspaces': '全部',
-    'switchWorkspace': '切换工作区',
-    'newSession': '新建会话',
-    'noSessions': '还没有会话，点右下角加号开始',
-    'homeStatusOngoing': '运行中',
-    'homeStatusWarning': '待处理',
-    'homeStatusDone': '已完成',
-    'backToList': '返回会话列表',
-    'sessionInfo': '会话信息',
-    'workbench': '工作台',
-    'workbenchClose': '关闭工作台',
-    'switchView': '切换视图',
-    'attach': '添加附件',
-    'attachBusy': '上传中…',
-    'attachFailed': '上传失败，点按重试',
-    'attachRemove': '移除附件 {name}',
-    'infoClose': '关闭',
-    'infoMode': '模式',
-    'infoCwdFallback': '未知目录',
-    'infoSubagents': '{count} 个子代理',
-    'infoJobs': '{count} 个后台任务',
-    'activityOpen': '查看子代理与后台任务',
-    'infoStatTurns': '轮次',
-    'infoStatSteps': '步骤',
-    'infoStatTtft': '首字延迟',
-    'infoStatLlm': '模型耗时',
-    'infoStatTool': '工具耗时',
-    'infoStatCacheHit': '缓存命中',
-    'infoTokenFlow': 'Token {io}',
-    'infoExport': '导出日志',
-    'infoRename': '重命名',
-    'infoRenamePrompt': '会话新名称',
-    'infoFork': 'Fork 会话',
-    'infoArchive': '归档',
-    'infoArchiveConfirm': '归档后将从会话列表隐藏，确定继续？',
-    'infoActionError': '操作失败：{message}',
-    'turnFold': '过程 · {count} 步',
-    'turnFoldRunning': '进行中 · {count} 步',
-    'settings': '设置',
-    'chipTaskboard': '任务看板',
-    'chipSsh': 'SSH',
-    'chipUsage': '用量',
-    'chipCustomize': '自定义入口',
-};
-/** English dictionary, key-identical to the Chinese source of truth. */
-exports.en = {
-    'open': 'Open directory',
-    'close': 'Close directory',
-    'backdrop': 'Click to close directory',
-    'sessionLog': 'Session log',
-    'files': 'Files',
-    'previewFullscreen': 'Fullscreen preview',
-    'previewExitFullscreen': 'Exit fullscreen',
-    'allWorkspaces': 'All',
-    'switchWorkspace': 'Switch workspace',
-    'newSession': 'New session',
-    'noSessions': 'No sessions yet — tap + to start one',
-    'homeStatusOngoing': 'Running',
-    'homeStatusWarning': 'Needs attention',
-    'homeStatusDone': 'Done',
-    'backToList': 'Back to sessions',
-    'sessionInfo': 'Session info',
-    'workbench': 'Workbench',
-    'workbenchClose': 'Close workbench',
-    'switchView': 'Switch view',
-    'attach': 'Add attachment',
-    'attachBusy': 'Uploading…',
-    'attachFailed': 'Upload failed — tap to retry',
-    'attachRemove': 'Remove attachment {name}',
-    'infoClose': 'Close',
-    'infoMode': 'Mode',
-    'infoCwdFallback': 'Unknown directory',
-    'infoSubagents': '{count} subagents',
-    'infoJobs': '{count} background tasks',
-    'activityOpen': 'View subagents and background tasks',
-    'infoStatTurns': 'Turns',
-    'infoStatSteps': 'Steps',
-    'infoStatTtft': 'TTFT',
-    'infoStatLlm': 'LLM time',
-    'infoStatTool': 'Tool time',
-    'infoStatCacheHit': 'Cache hit',
-    'infoTokenFlow': 'Tokens {io}',
-    'infoExport': 'Export log',
-    'infoRename': 'Rename',
-    'infoRenamePrompt': 'New session name',
-    'infoFork': 'Fork session',
-    'infoArchive': 'Archive',
-    'infoArchiveConfirm': 'Archiving hides this session from the list. Continue?',
-    'infoActionError': 'Action failed: {message}',
-    'turnFold': 'Process · {count} steps',
-    'turnFoldRunning': 'Working · {count} steps',
-    'settings': 'Settings',
-    'chipTaskboard': 'Task board',
-    'chipSsh': 'SSH',
-    'chipUsage': 'Usage',
-    'chipCustomize': 'Customize shortcuts',
-};
+exports.installHeaderStatusDot = installHeaderStatusDot;
+const session_dot_ts_1 = require("./session-dot.js");
+/**
+ * Session header running-status dot (S2). No official element exists to
+ * reposition (ConversationSessionHeader renders only the crumb title, the
+ * actions/utilities slots, and the tablist — dsh-client-ui-conversation
+ * lib/client.js:6949-7009), so this reads `ctx.sessions.list` directly
+ * (the same feed `useSessions` wraps) and stamps a data attribute the
+ * mobile stylesheet turns into a `::after` dot on the title crumb —
+ * "read data, self-draw" is the plan's documented fallback for this piece.
+ * Kept outside React: the dot must track the CURRENT session regardless of
+ * which component the header happens to mount, and a plain attribute +
+ * CSS avoids reaching into the official crumb's own DOM subtree.
+ */
+function installHeaderStatusDot(ctx) {
+    ctx.effect(() => {
+        const apply = () => {
+            const frame = document.querySelector('[data-mobile-nav="frame"]');
+            if (frame === null)
+                return;
+            const { current, byId } = ctx.sessions.list.getSnapshot();
+            const row = current === undefined ? undefined : byId[current];
+            const state = row === undefined ? undefined : (0, session_dot_ts_1.dotState)(row);
+            if (state === undefined)
+                frame.removeAttribute('data-mobile-nav-dot');
+            else
+                frame.setAttribute('data-mobile-nav-dot', state);
+        };
+        apply();
+        return ctx.sessions.list.subscribe(apply);
+    }, 'dsh-mobile-nav: header status dot');
+}
 };
-__modules["effects/turn-fold.js"] = function (require, module, exports) {
+__modules["effects/gestures.js"] = function (require, module, exports) {
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.installTurnFold = installTurnFold;
-const locales_ts_1 = require("./locales.js");
+exports.installGestures = installGestures;
+const nav_store_ts_1 = require("./nav-store.js");
 /** Phone breakpoint — same query every phone-only effect in this plugin uses. */
 const PHONE_QUERY = '(max-width: 767px)';
-/** Desktop fold (issue #2) is switched on either way:
- * - plugin row `config.turnFoldDesktop: true` — the host republishes it at
- *   {@link CLIENT_CONFIG_ROUTE} because the client bundle ships statically
- *   and never sees the row config;
- * - per-browser override, same convention as the debug flag: a URL param
- *   writes localStorage (`?mobile-nav-turn-fold=1` opts this browser in,
- *   `=0` opts back out). */
-const DESKTOP_KEY = 'dsh-mobile-nav.turn-fold-desktop';
-const DESKTOP_PARAM = 'mobile-nav-turn-fold';
-/** Root attribute the stylesheet keys the width-independent rules on. */
-const DESKTOP_ATTR = 'data-mnav-desktop-fold';
-/** Mirror of src/index.ts CLIENT_CONFIG_ROUTE (client tsconfig cannot reach it). */
-const CLIENT_CONFIG_ROUTE = '/_dsh/mobile-nav/client-config';
-/** Read (and, when the URL param is present, persist) the per-browser opt-in. */
-function desktopOptIn() {
-    const param = new URLSearchParams(location.search).get(DESKTOP_PARAM);
-    if (param === '1')
-        localStorage.setItem(DESKTOP_KEY, '1');
-    else if (param === '0')
-        localStorage.removeItem(DESKTOP_KEY);
-    return localStorage.getItem(DESKTOP_KEY) === '1';
+/** This plugin's two dismissible sheets (session-info, home workspace/chips
+ * picker — MobileHome.tsx's home-sheet hosts both the workspace switcher and
+ * the S5 chip-customize list under the same marker). Official popupSelect
+ * menus (permission/model) are deliberately excluded — the design spec
+ * leaves those mask-tap-only, and they are the suite's own DOM, not ours to
+ * add gesture handling to. */
+const SHEET_SELECTOR = '[data-mobile-nav="info-sheet"], [data-mobile-nav="home-sheet"]';
+const CLOSE_DISTANCE = 80;
+/** px/ms — a fast flick closes the sheet even short of CLOSE_DISTANCE. */
+const CLOSE_VELOCITY = 0.5;
+/** Below this the drag is a tap/jitter, not yet a pull — avoids hijacking
+ * the very first pixels of an upward scroll inside the sheet. */
+const DRAG_COMMIT_PX = 4;
+function prefersReducedMotion() {
+    return window.matchMedia('(prefers-reduced-motion: reduce)').matches;
 }
-/** True when the plugin row asks for desktop fold; false on any failure. */
-async function desktopConfigured() {
-    try {
-        const res = await fetch(CLIENT_CONFIG_ROUTE, { cache: 'no-store' });
-        if (!res.ok)
-            return false;
-        const body = await res.json();
-        return typeof body === 'object' && body !== null
-            && body.turnFoldDesktop === true;
-    }
-    catch {
-        return false;
-    }
+/** The sheet's own mask sibling — both this plugin's sheets name theirs
+ * with a "-mask" suffix (info-mask, home-sheet-mask) and already wire a
+ * click handler that calls the sheet's close(). Reusing that handler (a
+ * synthetic click) needs no access to the sheet's React state at all.
+ * Shared with the S6.1 edge-swipe-back priority chain below — both "drag
+ * down to dismiss" and "swipe back from the edge" close a sheet the exact
+ * same way. */
+function closeSheet(sheet) {
+    sheet.parentElement?.querySelector('[data-mobile-nav$="-mask"]')?.click();
 }
-/** ChatView's flow column (dsh-client-ui-conversation lib/client.js:5512).
- * Trajectory and every other view render their own tree and never carry this
- * marker, so scoping here is what keeps this effect Chat-only. */
-const FLOW = '[data-chat-flow]';
-/** Marker + selector of the injected summary row. */
-const CHIP = 'turn-fold';
-const CHIP_SELECTOR = '[data-mobile-nav="turn-fold"]';
-/** Whole-row node kinds that are turn *process*, not conversation content.
- * Keys are ChatNodeSeat's own `data-chat-flow-kind` dispatch values
- * (registerChatNodeRenderers, lib/client.js:9322): tool calls, injected
- * context rows, and slash-command rows. Everything else stays visible —
- * `user`/`steering` (the question), `assistant-step` (the prose, folded
- * per-block below), `turn-tail` (the footer with its actions), and the
- * error notices `turn-error` / `turn-max-tokens` / `model-retry`, which are
- * exactly what a reader must not have to hunt for. */
-const PROCESS_KINDS = new Set(['context', 'tool-call', 'command']);
-/** Node kinds that open a new turn group. */
-const TURN_HEAD_KINDS = new Set(['user', 'steering']);
-/** ReasoningRow's own marker (lib/client.js:8966) — the Think disclosure
- * rendered inside an assistant-step row, beside that step's prose. */
-const THINK = '[data-variant="think"]';
-/** Attribute the phone stylesheet turns into `display: none`. */
-const FOLD = 'data-mnav-fold';
-/** Per-item override written while its turn is expanded. */
-const OPEN = 'data-mnav-fold-open';
 /**
- * True when the reasoning rows are the ONLY thing this row renders, so the
- * whole flow item has to go: the flow column is `display: flex` with
- * `gap: 16px`, and an emptied-out flex item still claims its gap — the
- * reader would see the folded steps as a column of blank bands.
- * Structural test, no class names: every ancestor from the reasoning rows'
- * shared parent up to the flow item must be an only child.
+ * S6.2 — sheet drag-to-close: this plugin's two own bottom sheets (session
+ * info, home workspace picker) support "drag down to dismiss", mirroring
+ * the mask-tap close they already have. Official popupSelect menus
+ * (permission/model) are excluded on purpose — the design spec leaves them
+ * mask-tap-only, and they are the suite's own DOM, not ours to add gesture
+ * handling to.
+ *
+ * touchmove is registered non-passive (unlike the edge-swipe-back gesture
+ * below) because this gesture needs to preventDefault once it takes over, so
+ * the sheet's own translateY tracks the finger instead of fighting the
+ * scroller's native rubber-band. Before that handoff — while the sheet's
+ * inner content isn't scrolled to top — nothing is intercepted at all, so
+ * a pull down first scrolls the content as normal (spec requirement).
  */
-function foldsWholeRow(row, thinks) {
-    const first = thinks[0];
-    if (first === undefined)
-        return false;
-    const body = first.parentElement;
-    if (body === null || body.childElementCount !== thinks.length)
-        return false;
-    let node = body;
-    while (node !== row) {
-        const parent = node.parentElement;
-        if (parent === null)
-            return false;
-        if (parent.childElementCount !== 1)
-            return false;
-        node = parent;
-    }
-    return true;
-}
-/** The process items one flow row contributes: the row itself, its reasoning
- * rows, or nothing at all. */
-function processItems(row) {
-    const kind = row.getAttribute('data-chat-flow-kind');
-    if (kind === null)
-        return [];
-    if (PROCESS_KINDS.has(kind))
-        return [row];
-    if (kind !== 'assistant-step')
-        return [];
-    const thinks = [...row.querySelectorAll(THINK)];
-    if (thinks.length === 0)
-        return [];
-    return foldsWholeRow(row, thinks) ? [row] : thinks;
+function installSheetDragClose(ctx) {
+    ctx.effect(() => {
+        const narrow = window.matchMedia(PHONE_QUERY);
+        let drag = null;
+        const settle = (sheet, close) => {
+            if (close) {
+                sheet.style.transform = '';
+                sheet.style.transition = '';
+                closeSheet(sheet);
+                return;
+            }
+            if (prefersReducedMotion()) {
+                sheet.style.transition = 'none';
+                sheet.style.transform = '';
+                return;
+            }
+            sheet.style.transition = 'transform .22s var(--ds-ease-out, ease-in-out)';
+            sheet.style.transform = '';
+            const clear = () => {
+                sheet.style.transition = '';
+                sheet.removeEventListener('transitionend', clear);
+            };
+            sheet.addEventListener('transitionend', clear);
+        };
+        const onTouchStart = (event) => {
+            if (event.touches.length !== 1) {
+                drag = null;
+                return;
+            }
+            const touch = event.touches[0];
+            const target = event.target;
+            if (touch === undefined || !(target instanceof Element)) {
+                drag = null;
+                return;
+            }
+            const sheet = target.closest(SHEET_SELECTOR);
+            if (sheet === null) {
+                drag = null;
+                return;
+            }
+            drag = { sheet, startY: touch.clientY, lastY: touch.clientY, startTime: Date.now(), dragging: false };
+        };
+        const onTouchMove = (event) => {
+            if (drag === null)
+                return;
+            const touch = event.touches[0];
+            if (touch === undefined)
+                return;
+            drag.lastY = touch.clientY;
+            const dy = touch.clientY - drag.startY;
+            if (!drag.dragging) {
+                if (drag.sheet.scrollTop > 0)
+                    return;
+                if (dy <= DRAG_COMMIT_PX)
+                    return;
+                drag.dragging = true;
+                drag.sheet.style.transition = 'none';
+            }
+            event.preventDefault();
+            drag.sheet.style.transform = `translateY(${Math.max(0, dy)}px)`;
+        };
+        const finish = () => {
+            if (drag === null)
+                return;
+            const { sheet, dragging, startY, lastY, startTime } = drag;
+            drag = null;
+            if (!dragging)
+                return;
+            const dy = Math.max(0, lastY - startY);
+            const elapsed = Math.max(1, Date.now() - startTime);
+            const velocity = dy / elapsed;
+            settle(sheet, dy > CLOSE_DISTANCE || velocity > CLOSE_VELOCITY);
+        };
+        const attach = () => {
+            document.addEventListener('touchstart', onTouchStart, { passive: true });
+            document.addEventListener('touchmove', onTouchMove, { passive: false });
+            document.addEventListener('touchend', finish, { passive: true });
+            document.addEventListener('touchcancel', finish, { passive: true });
+        };
+        const detach = () => {
+            document.removeEventListener('touchstart', onTouchStart);
+            document.removeEventListener('touchmove', onTouchMove);
+            document.removeEventListener('touchend', finish);
+            document.removeEventListener('touchcancel', finish);
+            drag = null;
+        };
+        if (narrow.matches)
+            attach();
+        const onChange = (event) => (event.matches ? attach() : detach());
+        narrow.addEventListener('change', onChange);
+        return () => {
+            narrow.removeEventListener('change', onChange);
+            detach();
+        };
+    }, 'dsh-mobile-nav: sheet drag-to-close');
 }
+/** Left-edge start zone for S6.1's swipe-back, in CSS px from the viewport's
+ * left edge. This used to be the gateway half's own edge-swipe-back hot zone
+ * (history.back, useless against an SPA) — that gesture is removed in the
+ * same revision that adds this one, so the 24px strip changes owner instead
+ * of staying carved out (design doc "手势" row, 2026-08-17 fourth revision). */
+const EDGE_ZONE_PX = 24;
+const EDGE_SWIPE_MIN_DX = 90;
+const EDGE_SWIPE_RATIO = 1.6;
 /**
- * The summary row sitting immediately before `anchor`, created if absent.
- * Idempotent by construction — React re-rendering the flow either leaves our
- * button where it is (it only ever inserts and removes its OWN nodes) or
- * drops it, and the next rescan puts it back.
+ * dsh-better-sidebar's panel-open read (AGENTS.md pitfall "第三方浮层的开合
+ * 态可以纯 CSS `:has()` 读"): the panel's class ends in "_panel" only while
+ * open — "_panelHidden" is appended once closed, so the string no longer
+ * ends in "_panel" and this selector stops matching. Same anchor
+ * MobileSessionHeader.tsx's workbench button and its own close button use.
  */
-function chipBefore(anchor) {
-    const previous = anchor.previousElementSibling;
-    if (previous instanceof HTMLElement && previous.dataset['mobileNav'] === CHIP)
-        return previous;
-    const parent = anchor.parentElement;
-    if (parent === null)
-        return null;
-    const chip = document.createElement('button');
-    chip.type = 'button';
-    chip.dataset['mobileNav'] = CHIP;
-    parent.insertBefore(chip, anchor);
-    return chip;
+function betterSidebarPanelOpen() {
+    return document.querySelector('[data-dsh-better-sidebar] [class$="_panel"]') !== null;
 }
-/** Split the flow column into turns: a group runs from one user/steering row
- * up to (not including) the next. Rows that precede the first user row —
- * a turn whose question has not been paged in yet — form a leading group of
- * their own, so their process never becomes unreachable. */
-function groupsOf(flow) {
-    const groups = [];
-    let current;
-    for (const row of flow.children) {
-        const kind = row.getAttribute('data-chat-flow-kind');
-        if (kind === null)
-            continue;
-        if (current === undefined || TURN_HEAD_KINDS.has(kind)) {
-            current = { key: row.getAttribute('data-chat-flow-key') ?? `pos${groups.length}`, items: [] };
-            groups.push(current);
-        }
-        current.items.push(...processItems(row));
+/**
+ * S6.1 — left-edge swipe-back priority chain (design doc "手势" row, fourth
+ * revision): a swipe starting in the left {@link EDGE_ZONE_PX} always closes
+ * the TOPMOST dismissible surface rather than always navigating, so a user
+ * mid-workflow (info card open, workbench panel open) gets "close that"
+ * instead of "leave the session" from the same gesture. Checked in the
+ * design doc's own order:
+ *   1. this plugin's session-info sheet, if open
+ *   2. this plugin's home sheet (workspace switcher or S5 chip-customize),
+ *      if open
+ *   3. dsh-better-sidebar's workbench panel, if open (代点 its own toggle —
+ *      same anchor MobileSessionHeader.tsx's workbench/close buttons use)
+ *   4. otherwise, GO_HOME_EVENT — but only from the session view; the design
+ *      doc calls out "在 home 层→无动作" explicitly, and the phone page
+ *      stack's current level is read straight off MobileHome's own
+ *      `data-view` attribute (no store handle needed here — effects/*.ts is
+ *      already all DOM reads, matching every sibling effect in this file).
+ */
+function handleEdgeSwipeBack() {
+    const sheet = document.querySelector(SHEET_SELECTOR);
+    if (sheet !== null) {
+        closeSheet(sheet);
+        return;
+    }
+    if (betterSidebarPanelOpen()) {
+        document.querySelector('[data-dsh-better-sidebar] button[class$="_toggleButton"]')?.click();
+        return;
+    }
+    if (document.querySelector('[data-mobile-nav="home"]')?.getAttribute('data-view') === 'session') {
+        window.dispatchEvent(new CustomEvent(nav_store_ts_1.GO_HOME_EVENT));
     }
-    return groups;
 }
 /**
- * S8 — collapse a turn's process into one summary row (< 768px by default;
- * every width when the plugin row sets `config.turnFoldDesktop` or a browser
- * opts itself in via `?mobile-nav-turn-fold=1`).
- *
- * Route taken: DOM marking, not the `conversation.chat.node` keyed slot.
- * That slot dispatches on node kind and a second registration at a key
- * SHADOWS the official renderer (dsh-client-ui-slots index.d.ts:542 — the
- * cell's lowest-priority live entry renders, there is no wrapping form and
- * no `children` handle to the shadowed component). Taking `tool-call` would
- * mean re-implementing every tool's presentation, its `t` seat comes from
- * the entry's own declared locale namespace and its services from the
- * registrant's own inject face — neither is reachable from here — and the
- * registration is global, so the desktop no-op would be gone too.
- *
- * The DOM route needs no class names: ChatNodeSeat stamps every row with
- * `data-chat-flow-kind` / `data-chat-flow-key` (lib/client.js:5228) and
- * ReasoningRow stamps `data-variant="think"` — turn grouping is pure
- * structure (the run of rows following one `user` row), never text.
- *
- * ponytail: one rAF-coalesced full rescan per DOM mutation batch, O(rows).
- * If a very long session ever makes streaming feel heavy, narrow the
- * observer to the flow column's own childList and diff instead.
+ * S6.1 — left-edge swipe-back gesture install. Passive throughout (never
+ * calls preventDefault) and decided purely from the touchstart/touchend
+ * endpoints, exactly like the S6.1-predecessor content-area swipe this
+ * revision removes — so it never fights vertical (or, at the 24px strip,
+ * horizontal chip-row) scrolling, and needs no mid-drag tracking: the design
+ * doc explicitly allows "一步到位" over a followed-finger animation.
  */
-function installTurnFold(ctx) {
+function installEdgeSwipeBack(ctx) {
     ctx.effect(() => {
         const narrow = window.matchMedia(PHONE_QUERY);
-        const t = ctx.locale.bind(locales_ts_1.NS);
-        /** Turns the reader opened. Deliberately not persisted (spec: a reload
-         * returns to the default folded state). */
-        const expanded = new Set();
-        let observer = null;
-        let frame = 0;
-        const label = (chip, count, running) => {
-            const next = running ? t('turnFoldRunning', { count }) : t('turnFold', { count });
-            if (chip.textContent !== next)
-                chip.textContent = next;
-        };
-        const scan = () => {
-            const flow = document.querySelector(FLOW);
-            if (flow === null)
+        let start = null;
+        const onTouchStart = (event) => {
+            if (event.touches.length !== 1) {
+                start = null;
                 return;
-            // TurnStatus, ChatView's own running banner — present only while the
-            // last turn is still working (lib/client.js:5548).
-            const running = flow.querySelector(':scope > [role="status"]') !== null;
-            const groups = groupsOf(flow);
-            const live = new Set();
-            const liveItems = new Set();
-            groups.forEach((group, index) => {
-                if (group.items.length === 0)
-                    return;
-                const open = expanded.has(group.key);
-                for (const item of group.items) {
-                    liveItems.add(item);
-                    item.setAttribute(FOLD, '');
-                    if (open)
-                        item.setAttribute(OPEN, '');
-                    else
-                        item.removeAttribute(OPEN);
-                }
-                const first = group.items[0];
-                if (first === undefined)
-                    return;
-                const anchor = first.closest('[data-chat-flow-key]') ?? first;
-                const chip = chipBefore(anchor);
-                if (chip === null)
-                    return;
-                chip.dataset['foldGroup'] = group.key;
-                chip.setAttribute('aria-expanded', open ? 'true' : 'false');
-                if (open)
-                    chip.dataset['open'] = '';
-                else
-                    delete chip.dataset['open'];
-                const groupRunning = running && index === groups.length - 1;
-                if (groupRunning)
-                    chip.dataset['running'] = '';
-                else
-                    delete chip.dataset['running'];
-                label(chip, group.items.length, groupRunning);
-                live.add(group.key);
-            });
-            for (const chip of flow.querySelectorAll(CHIP_SELECTOR)) {
-                const key = chip.dataset['foldGroup'];
-                if (key === undefined || !live.has(key))
-                    chip.remove();
             }
-            // Unmark elements that stopped being process items. Without this, an
-            // assistant-step row folded whole while it streamed ONLY reasoning kept
-            // its row-level fold after prose started arriving in the same DOM node
-            // (React updates the row in place), hiding the streaming reply until a
-            // completion re-render rebuilt the row — the "reply only appears when
-            // the turn finishes" phone bug (2026-08-18).
-            for (const stale of flow.querySelectorAll(`[${FOLD}]`)) {
-                if (liveItems.has(stale))
-                    continue;
-                stale.removeAttribute(FOLD);
-                stale.removeAttribute(OPEN);
+            const touch = event.touches[0];
+            if (touch === undefined) {
+                start = null;
+                return;
             }
+            start = { x: touch.clientX, y: touch.clientY, eligible: touch.clientX <= EDGE_ZONE_PX };
         };
-        const schedule = () => {
-            // The locale subscription below lives outside attach/detach, so this
-            // guard is what keeps a late dictionary registration from marking up
-            // the flow at >= 768px (real WebKit regression: chips and fold
-            // attributes appeared at 1280px — invisible, since every rule that
-            // hides anything is inside the phone media query, but still wrong).
-            if (observer === null)
-                return;
-            if (frame !== 0)
+        const onTouchEnd = (event) => {
+            const state = start;
+            start = null;
+            if (state === null || !state.eligible)
                 return;
-            frame = requestAnimationFrame(() => {
-                frame = 0;
-                scan();
-                // Drop the records our own chip insertions just queued, so a rescan
-                // can never re-trigger itself (the debug-badge feedback-loop freeze).
-                observer?.takeRecords();
-            });
-        };
-        const onClick = (event) => {
-            const target = event.target;
-            if (!(target instanceof Element))
+            const touch = event.changedTouches[0];
+            if (touch === undefined)
                 return;
-            const chip = target.closest(CHIP_SELECTOR);
-            const key = chip?.dataset['foldGroup'];
-            if (key === undefined)
+            const dx = touch.clientX - state.x;
+            const dy = touch.clientY - state.y;
+            if (dx <= EDGE_SWIPE_MIN_DX || Math.abs(dx) <= EDGE_SWIPE_RATIO * Math.abs(dy))
                 return;
-            if (expanded.has(key))
-                expanded.delete(key);
-            else
-                expanded.add(key);
-            scan();
-        };
-        const clear = () => {
-            for (const chip of document.querySelectorAll(CHIP_SELECTOR))
-                chip.remove();
-            for (const item of document.querySelectorAll(`[${FOLD}]`)) {
-                item.removeAttribute(FOLD);
-                item.removeAttribute(OPEN);
-            }
+            handleEdgeSwipeBack();
         };
         const attach = () => {
-            if (observer !== null)
-                return;
-            observer = new MutationObserver(schedule);
-            observer.observe(document.body, { childList: true, subtree: true });
-            document.addEventListener('click', onClick);
-            scan();
+            document.addEventListener('touchstart', onTouchStart, { passive: true });
+            document.addEventListener('touchend', onTouchEnd, { passive: true });
         };
         const detach = () => {
-            observer?.disconnect();
-            observer = null;
-            document.removeEventListener('click', onClick);
-            if (frame !== 0)
-                cancelAnimationFrame(frame);
-            frame = 0;
-            expanded.clear();
-            clear();
-        };
-        const onChange = (event) => (event.matches ? attach() : detach());
-        let disposed = false;
-        let desktop = false;
-        /** Attach at every width and drop the breakpoint listener — the
-         * stylesheet's html[DESKTOP_ATTR] rules take over from the phone media
-         * query. Idempotent: the config answer and the local opt-in may both
-         * ask for it. */
-        const enableDesktop = () => {
-            if (desktop || disposed)
-                return;
-            desktop = true;
-            document.documentElement.setAttribute(DESKTOP_ATTR, '');
-            narrow.removeEventListener('change', onChange);
-            attach();
+            document.removeEventListener('touchstart', onTouchStart);
+            document.removeEventListener('touchend', onTouchEnd);
+            start = null;
         };
         if (narrow.matches)
             attach();
+        const onChange = (event) => (event.matches ? attach() : detach());
         narrow.addEventListener('change', onChange);
-        if (desktopOptIn())
-            enableDesktop();
-        // The row config arrives async; a late enable just attaches then. Not
-        // awaited before phone attach — folding must not wait on a round-trip.
-        else
-            void desktopConfigured().then((on) => (on ? enableDesktop() : undefined));
-        // A language switch changes the chip copy of every already-rendered turn.
-        const stopLocale = ctx.locale.subscribe(schedule);
         return () => {
-            disposed = true;
-            document.documentElement.removeAttribute(DESKTOP_ATTR);
             narrow.removeEventListener('change', onChange);
-            stopLocale();
             detach();
         };
-    }, 'dsh-mobile-nav: turn process fold');
+    }, 'dsh-mobile-nav: left-edge swipe-back');
+}
+/** S6: the two-gesture set — left-edge swipe-back and sheet drag-to-close.
+ * Both install/uninstall their own document listeners on the phone
+ * breakpoint's matchMedia change, so at >= 768px this is a true no-op (no
+ * listeners attached at all), matching every other effect in this file. */
+function installGestures(ctx) {
+    installEdgeSwipeBack(ctx);
+    installSheetDragClose(ctx);
 }
 };
 __modules["effects/modal-back.js"] = function (require, module, exports) {
@@ -7433,6 +7683,7 @@ exports.estimatedLift = estimatedLift;
 exports.keyboardLift = keyboardLift;
 exports.composerLift = composerLift;
 exports.installKeyboardAvoid = installKeyboardAvoid;
+const client_config_ts_1 = require("./client-config.js");
 /** Phone breakpoint — same query every phone-only effect in this plugin uses. */
 const PHONE_QUERY = '(max-width: 767px)';
 /** Root CSS variable composer.css.ts turns into a composer lift. */
@@ -7455,13 +7706,18 @@ const MAX_SCALE = 1.01;
  *
  * ANDROID ONLY ({@link safetyPad}). The under-reporting is an Android IME
  * behaviour; iOS has one system keyboard whose height WebKit reports exactly,
- * so padding there would be a visible gap bought for nothing. */
-const SAFETY_PAD_PX = 15;
-/** The safety pad this platform gets: the clearance above, or nothing off
- * Android. UA sniffing is the right tool here — the target is a platform
- * defect, not a feature that could be detected. */
-function safetyPad(userAgent) {
-    return /Android/iu.test(userAgent) ? SAFETY_PAD_PX : 0;
+ * so padding there would be a visible gap bought for nothing.
+ *
+ * The 15px default is what shipped; a device whose IME hides more of the
+ * composer than that can raise it through the plugin row's
+ * `config.keyboardSafetyPadPx` ({@link KeyboardTuning}). */
+const SAFETY_PAD_PX = client_config_ts_1.KEYBOARD_DEFAULTS.safetyPadPx;
+/** The safety pad this platform gets: the configured clearance, or nothing
+ * off Android. UA sniffing is the right tool here — the target is a platform
+ * defect, not a feature that could be detected.
+ * @param padPx - the row's clearance; defaults to the shipped 15px. */
+function safetyPad(userAgent, padPx = SAFETY_PAD_PX) {
+    return /Android/iu.test(userAgent) ? padPx : 0;
 }
 /** A viewport that lost at least this much against its no-keyboard baseline
  * has a keyboard up. Comfortably above the ~56px a collapsing URL bar moves,
@@ -7488,11 +7744,16 @@ const PROBE_EPSILON_PX = 8;
  * There is no signal to measure, so this is an estimate: the reporter's
  * measured WeType is ~315 CSS px on a 858px viewport (~37%); 42% capped at
  * 400px covers taller IME toolbars without stranding the composer mid-screen.
- * ponytail: single heuristic constant; per-IME calibration only if reports
- * show it misses.
+ *
+ * Both numbers are a guess about someone else's hardware, so both are knobs:
+ * `config.keyboardLiftRatio` / `config.keyboardLiftMaxPx` on the plugin row
+ * ({@link KeyboardTuning}). The shipped pair stays the default — an install
+ * that never touches them behaves exactly as before.
+ *
+ * @param tuning - the row's tuning; defaults to the shipped estimate.
  */
-function estimatedLift(innerHeight) {
-    return Math.min(Math.round(innerHeight * 0.42), 400);
+function estimatedLift(innerHeight, tuning = client_config_ts_1.KEYBOARD_DEFAULTS) {
+    return Math.min(Math.round(innerHeight * tuning.liftRatio), tuning.liftMaxPx);
 }
 /**
  * How far the composer must rise so its bottom edge sits on the visual
@@ -7594,7 +7855,16 @@ function installKeyboardAvoid(ctx) {
          * it. Re-read on every sync that finds the composer unfocused, so a
          * rotation or a URL-bar change rebases it without extra listeners. */
         let baseline = 0;
-        const pad = safetyPad(navigator.userAgent);
+        /** Row tuning for the estimate path. Starts on the shipped defaults and
+         * is replaced once the config request lands (a few ms into the page, and
+         * always long before a touch focus can raise a keyboard) — no re-sync is
+         * forced, the next focus or viewport event picks the new values up. */
+        let tuning = client_config_ts_1.KEYBOARD_DEFAULTS;
+        let pad = safetyPad(navigator.userAgent);
+        void (0, client_config_ts_1.clientConfig)().then((loaded) => {
+            tuning = loaded.keyboard;
+            pad = safetyPad(navigator.userAgent, tuning.safetyPadPx);
+        });
         const composerTextarea = (node) => node instanceof HTMLElement && node.tagName === 'TEXTAREA' && node.closest(COMPOSER) !== null;
         const sync = () => {
             const focused = composerTextarea(document.activeElement);
@@ -7677,7 +7947,7 @@ function installKeyboardAvoid(ctx) {
             // the probe below still runs and revokes the verdict if the viewport
             // turns out to react after all.
             if (localStorage.getItem(DUMB_KEY) === '1') {
-                estimate = estimatedLift(window.innerHeight);
+                estimate = estimatedLift(window.innerHeight, tuning);
                 sync();
             }
             const h0 = viewport.height;
@@ -7709,7 +7979,7 @@ function installKeyboardAvoid(ctx) {
                 if (!composerTextarea(document.activeElement))
                     return;
                 localStorage.setItem(DUMB_KEY, '1');
-                estimate = estimatedLift(window.innerHeight);
+                estimate = estimatedLift(window.innerHeight, tuning);
                 sync();
             };
             probeTimer = window.setTimeout(step, PROBE_INTERVAL_MS);