dsh-zen-remote 1.0.0 → 1.0.1

package/README.md

@@ -207,6 +207,7 @@ open http://127.0.0.1:3088/lan-gate/admin
 - 真 PWA：manifest + service worker，可装到主屏、可离线打开
 - 真 Web Push：VAPID + aes128gcm，通知默认不带对话正文
 - `push_notify` 工具：模型可在关键节点自己推一条，带限流
+- 「内测声明」弹窗注入「不再弹出」可选项：远程访问每次刷新都会重弹声明，点一次后本设备记住选择、以后自动关闭
 
 深度说明：[界面](docs/interface.md) · [公网接入](docs/remote-access.md)
 

package/lib/client.js

@@ -1692,24 +1692,39 @@ exports.BASE_CSS = `
   }
 }
 
-/* ---------- beta-notice suppression (ALL widths — deliberate exception) ----
-   User-directed (2026-08-17): hide DSH's beta/preview notices everywhere,
-   including desktop. This is the ONE place this plugin intentionally breaks
-   its own ">=1024px strict no-op" rule — do not "fix" it back.
-   Selector notes:
+/* ---------- beta-notice handling (ALL widths — deliberate exception) ----
+   User-directed (2026-08-17): tone down DSH's beta/preview notices
+   everywhere, including desktop. This is the ONE place this plugin
+   intentionally breaks its own ">=1024px strict no-op" rule.
    - The hero "预览版" badge only carries a hashed class; per repo convention
      the stable part is the suffix (_previewBadge), matched with [class$=].
-   - The first-run "内测声明" modal is hidden via its ARIA label. The label is
-     LOCALIZED — zh is covered; if the UI runs in another language the dialog
-     shows (harmless, dismiss by hand). Hiding targets the presentation
-     wrapper via :has() so the modal's backdrop cannot linger invisibly and
-     block taps; the app never requires acknowledging this dialog to work. */
+   - The first-run "内测声明" modal must NOT be hidden with CSS: while it is
+     mounted it holds document #root inert, so display:none leaves the whole
+     app unclickable (2026-08-18 incident). effects/welcome-notice.ts instead
+     injects a "不再弹出" opt-out button; this styles it. */
 [class$="_previewBadge"] {
   display: none !important;
 }
-[role="presentation"]:has(> [role="dialog"][aria-label="内测声明"]),
-[role="dialog"][aria-label="内测声明"] {
-  display: none !important;
+/* Mirrors the official primitives Button (md capsule, outline variant):
+   36px height, 18px radius, --dsw-alias-border-l2 hairline. */
+.zen-welcome-optout {
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  height: 36px;
+  padding: 0 14px;
+  margin-right: 8px;
+  border: 1px solid var(--dsw-alias-border-l2, rgba(0, 0, 0, .15));
+  border-radius: 18px;
+  background: transparent;
+  color: var(--dsw-alias-label-primary, inherit);
+  font-size: 14px;
+  line-height: 22px;
+  cursor: pointer;
+  -webkit-tap-highlight-color: transparent;
+}
+.zen-welcome-optout:hover {
+  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
 }
 `;
 };
@@ -4975,6 +4990,113 @@ exports.CHIPS_CSS = `/* ---------- chips row + settings entry (S5) ---------- */
 }
 `;
 };
+__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.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;
+  }
+
+  /* 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 });
@@ -4989,6 +5111,7 @@ 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");
 /**
  * All mobile styles, concatenated in the exact order of the original
  * single-file stylesheet (base → layout → compat → misc, where misc keeps
@@ -4999,10 +5122,11 @@ const chips_css_ts_1 = require("./styles/chips.css.js");
  * 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. Injected as ONE
- * <style data-plugin> tag — do not reorder.
+ * 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.
  */
-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].join('\n');
+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";
@@ -6295,11 +6419,13 @@ function installTurnFold(ctx) {
             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, '');
@@ -6332,6 +6458,18 @@ function installTurnFold(ctx) {
                 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 schedule = () => {
             // The locale subscription below lives outside attach/detach, so this
@@ -6405,6 +6543,198 @@ function installTurnFold(ctx) {
     }, 'dsh-mobile-nav: turn process fold');
 }
 };
+__modules["effects/welcome-notice.js"] = function (require, module, exports) {
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.installWelcomeNoticeOptOut = installWelcomeNoticeOptOut;
+/** Per-browser opt-out flag; localStorage because remote (non-loopback)
+    connections never persist the acknowledgement host-side. */
+const OPTOUT_KEY = 'dsh-zen-remote:welcome-notice-optout';
+/** Localized aria-labels of the DSH first-run notice dialog
+    (@deepseek-ai/dsh-client-ui-settings-models WELCOME_NOTICE_COPY). */
+const NOTICE_LABELS = ['内测声明', 'Internal Testing Notice'];
+/**
+ * "内测声明" first-run notice, opt-out half (ALL widths — same user-directed
+ * exception as the _previewBadge rule in styles/base.css.ts).
+ *
+ * Why not CSS: the notice dialog keeps document #root inert while MOUNTED and
+ * only restores it on unmount (its acknowledge button). display:none hid the
+ * dialog without unmounting it, which left the whole app permanently
+ * unclickable on remote connections (2026-08-18 incident) — remote browsers
+ * re-mount the notice on every page load because their acknowledgement is
+ * memory-only (`connection.isLoopback ? "host" : "memory"` upstream).
+ *
+ * So the dialog now shows normally, plus one injected "不再弹出" button. The
+ * user chooses: acknowledging via that button records the opt-out in this
+ * browser's localStorage, and later mounts are auto-acknowledged by clicking
+ * the dialog's own continue button — the component unmounts through its
+ * normal path and #root's inert is properly restored.
+ */
+function installWelcomeNoticeOptOut(ctx) {
+    ctx.effect(() => {
+        const handle = (dialog) => {
+            // The notice's action row holds exactly one button ("继续"/"Continue").
+            const continueBtn = dialog.querySelector('button');
+            if (continueBtn === null)
+                return;
+            if (localStorage.getItem(OPTOUT_KEY) !== null) {
+                continueBtn.click();
+                return;
+            }
+            const row = continueBtn.parentElement;
+            if (row === null || row.querySelector('.zen-welcome-optout') !== null)
+                return;
+            const optOut = document.createElement('button');
+            optOut.type = 'button';
+            optOut.className = 'zen-welcome-optout';
+            optOut.textContent =
+                dialog.getAttribute('aria-label') === '内测声明' ? '不再弹出' : "Don't show again";
+            optOut.addEventListener('click', () => {
+                localStorage.setItem(OPTOUT_KEY, '1');
+                continueBtn.click();
+            });
+            row.insertBefore(optOut, continueBtn);
+        };
+        const scan = () => {
+            for (const label of NOTICE_LABELS) {
+                const dialog = document.querySelector(`[role="dialog"][aria-label="${label}"]`);
+                if (dialog !== null)
+                    handle(dialog);
+            }
+        };
+        // The dialog portals straight under <body>, so childList on body is
+        // enough; scan() once first in case it mounted before this plugin loaded.
+        scan();
+        const observer = new MutationObserver(scan);
+        observer.observe(document.body, { childList: true });
+        return () => observer.disconnect();
+    }, 'dsh-mobile-nav: welcome-notice opt-out');
+}
+};
+__modules["effects/keyboard-guard.js"] = function (require, module, exports) {
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.installKeyboardGuard = installKeyboardGuard;
+/** Phone breakpoint — same query every phone-only effect in this plugin uses. */
+const PHONE_QUERY = '(max-width: 767px)';
+/** The official composer slot wrapper (same marker composer.css.ts styles). */
+const COMPOSER = '[data-slot="conversation.composer.bar"]';
+/** A tap/keystroke older than this no longer explains a focus. */
+const INTENT_WINDOW_MS = 1000;
+/**
+ * S9 — keep the phone keyboard down until the user asks for it.
+ *
+ * dsh-client-ui-conversation focuses the composer textarea on every
+ * sessionId change (lib/client.js:3423 — el.focus({preventScroll:true}) in a
+ * [locked, sessionId] effect). Sensible on desktop; on a phone it pops the
+ * software keyboard over half the screen every time a session opens.
+ *
+ * Rule: focus on the composer textarea survives only when the user asked for
+ * it — a tap on the textarea itself or typing on a hardware keyboard.
+ * Anything else (session-open autofocus, push-deep-link opens, the refocus
+ * side effects of the other composer buttons — slash-command toggle, attach,
+ * send) is blurred.
+ *
+ * Two triggers, because one is not enough:
+ * - focusin catches the autofocus the moment it happens;
+ * - a body MutationObserver re-runs the check after transcript swaps
+ *   (opening a session re-renders the flow but may reuse the same textarea,
+ *   and a focus that landed before this plugin loaded never fired focusin
+ *   for us at all).
+ * Once focus is user-granted it stays granted until the textarea blurs, so
+ * the observer never yanks a keyboard the user opened (e.g. while the agent
+ * streams and the user pauses typing).
+ */
+function installKeyboardGuard(ctx) {
+    ctx.effect(() => {
+        const narrow = window.matchMedia(PHONE_QUERY);
+        let lastIntent = 0;
+        let granted = false;
+        let observer = null;
+        let frame = 0;
+        const composerTextarea = (node) => node instanceof HTMLElement && node.tagName === 'TEXTAREA' && node.closest(COMPOSER) !== null
+            ? node
+            : null;
+        const onPointerDown = (event) => {
+            // Only the textarea itself grants the keyboard. A tap on any other
+            // composer control (slash-command toggle, attach, model menu, send)
+            // must not: several of them refocus the input as a side effect, which
+            // popped the keyboard on every command-button tap.
+            if (composerTextarea(event.target) !== null) {
+                lastIntent = Date.now();
+                granted = true;
+            }
+        };
+        const onKeyDown = () => {
+            lastIntent = Date.now();
+            if (composerTextarea(document.activeElement) !== null)
+                granted = true;
+        };
+        const sweep = () => {
+            const el = composerTextarea(document.activeElement);
+            if (el === null)
+                return;
+            if (granted || Date.now() - lastIntent < INTENT_WINDOW_MS) {
+                granted = true;
+                return;
+            }
+            el.blur();
+        };
+        const onFocusIn = (event) => {
+            if (composerTextarea(event.target) === null)
+                return;
+            sweep();
+        };
+        const onFocusOut = (event) => {
+            if (composerTextarea(event.target) === null)
+                return;
+            granted = false;
+        };
+        const schedule = () => {
+            if (observer === null || frame !== 0)
+                return;
+            // setTimeout, not requestAnimationFrame: rAF pauses in hidden/
+            // backgrounded pages, where the autofocus still happens — the sweep
+            // must run there too or the keyboard pops when the page is foregrounded.
+            frame = window.setTimeout(() => {
+                frame = 0;
+                sweep();
+            }, 100);
+        };
+        const attach = () => {
+            if (observer !== null)
+                return;
+            document.addEventListener('pointerdown', onPointerDown, { capture: true, passive: true });
+            document.addEventListener('keydown', onKeyDown, { capture: true, passive: true });
+            document.addEventListener('focusin', onFocusIn, true);
+            document.addEventListener('focusout', onFocusOut, true);
+            observer = new MutationObserver(schedule);
+            observer.observe(document.body, { childList: true, subtree: true });
+            sweep();
+        };
+        const detach = () => {
+            document.removeEventListener('pointerdown', onPointerDown, true);
+            document.removeEventListener('keydown', onKeyDown, true);
+            document.removeEventListener('focusin', onFocusIn, true);
+            document.removeEventListener('focusout', onFocusOut, true);
+            observer?.disconnect();
+            observer = null;
+            if (frame !== 0)
+                window.clearTimeout(frame);
+            frame = 0;
+            granted = false;
+        };
+        if (narrow.matches)
+            attach();
+        const onChange = (event) => (event.matches ? attach() : detach());
+        narrow.addEventListener('change', onChange);
+        return () => {
+            narrow.removeEventListener('change', onChange);
+            detach();
+        };
+    }, 'dsh-mobile-nav: composer keyboard guard');
+}
+};
 __modules["index.js"] = function (require, module, exports) {
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
@@ -6426,6 +6756,8 @@ const aionui_compat_ts_1 = require("./effects/aionui-compat.js");
 const header_status_ts_1 = require("./effects/header-status.js");
 const gestures_ts_1 = require("./effects/gestures.js");
 const turn_fold_ts_1 = require("./effects/turn-fold.js");
+const welcome_notice_ts_1 = require("./effects/welcome-notice.js");
+const keyboard_guard_ts_1 = require("./effects/keyboard-guard.js");
 const locales_ts_1 = require("./locales.js");
 /** Required services (cordis fiber inject — the loader passes all module exports as an object plugin). */
 exports.inject = ['slots', 'layout', 'locale', 'sessionLogDownload', 'sessions', 'workspaces'];
@@ -6469,6 +6801,14 @@ function apply(ctx) {
     // effects/turn-fold.ts for why the keyed conversation.chat.node seat could
     // not carry this.
     (0, turn_fold_ts_1.installTurnFold)(ctx);
+    // "内测声明" first-run notice: keep it visible (CSS-hiding it leaked the
+    // dialog's #root inert lock — see effects/welcome-notice.ts) and offer a
+    // per-browser "不再弹出" opt-out instead.
+    (0, welcome_notice_ts_1.installWelcomeNoticeOptOut)(ctx);
+    // S9: opening a session must not pop the phone keyboard — the official
+    // composer autofocuses on every sessionId change; keep focus only when the
+    // user tapped the composer (or typed) themselves.
+    (0, keyboard_guard_ts_1.installKeyboardGuard)(ctx);
     // Page-stack store (apply world) — created before any registration so
     // every slot below (the phone home screen, the session header's back
     // button) shares the exact same handle/instance.

package/lib/types/client/effects/keyboard-guard.d.ts

@@ -0,0 +1,27 @@
+import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client';
+/**
+ * S9 — keep the phone keyboard down until the user asks for it.
+ *
+ * dsh-client-ui-conversation focuses the composer textarea on every
+ * sessionId change (lib/client.js:3423 — el.focus({preventScroll:true}) in a
+ * [locked, sessionId] effect). Sensible on desktop; on a phone it pops the
+ * software keyboard over half the screen every time a session opens.
+ *
+ * Rule: focus on the composer textarea survives only when the user asked for
+ * it — a tap on the textarea itself or typing on a hardware keyboard.
+ * Anything else (session-open autofocus, push-deep-link opens, the refocus
+ * side effects of the other composer buttons — slash-command toggle, attach,
+ * send) is blurred.
+ *
+ * Two triggers, because one is not enough:
+ * - focusin catches the autofocus the moment it happens;
+ * - a body MutationObserver re-runs the check after transcript swaps
+ *   (opening a session re-renders the flow but may reuse the same textarea,
+ *   and a focus that landed before this plugin loaded never fired focusin
+ *   for us at all).
+ * Once focus is user-granted it stays granted until the textarea blurs, so
+ * the observer never yanks a keyboard the user opened (e.g. while the agent
+ * streams and the user pauses typing).
+ */
+export declare function installKeyboardGuard(ctx: ClientContext): void;
+//# sourceMappingURL=keyboard-guard.d.ts.map

package/lib/types/client/effects/keyboard-guard.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"keyboard-guard.d.ts","sourceRoot":"","sources":["../../../../src/client/effects/keyboard-guard.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAA;AAW3E;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,oBAAoB,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CAqF7D"}

package/lib/types/client/effects/turn-fold.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"turn-fold.d.ts","sourceRoot":"","sources":["../../../../src/client/effects/turn-fold.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAA;AAqH3E;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CAsHxD"}
+{"version":3,"file":"turn-fold.d.ts","sourceRoot":"","sources":["../../../../src/client/effects/turn-fold.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAA;AAqH3E;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CAoIxD"}

package/lib/types/client/effects/welcome-notice.d.ts

@@ -0,0 +1,20 @@
+import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client';
+/**
+ * "内测声明" first-run notice, opt-out half (ALL widths — same user-directed
+ * exception as the _previewBadge rule in styles/base.css.ts).
+ *
+ * Why not CSS: the notice dialog keeps document #root inert while MOUNTED and
+ * only restores it on unmount (its acknowledge button). display:none hid the
+ * dialog without unmounting it, which left the whole app permanently
+ * unclickable on remote connections (2026-08-18 incident) — remote browsers
+ * re-mount the notice on every page load because their acknowledgement is
+ * memory-only (`connection.isLoopback ? "host" : "memory"` upstream).
+ *
+ * So the dialog now shows normally, plus one injected "不再弹出" button. The
+ * user chooses: acknowledging via that button records the opt-out in this
+ * browser's localStorage, and later mounts are auto-acknowledged by clicking
+ * the dialog's own continue button — the component unmounts through its
+ * normal path and #root's inert is properly restored.
+ */
+export declare function installWelcomeNoticeOptOut(ctx: ClientContext): void;
+//# sourceMappingURL=welcome-notice.d.ts.map

package/lib/types/client/effects/welcome-notice.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"welcome-notice.d.ts","sourceRoot":"","sources":["../../../../src/client/effects/welcome-notice.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAA;AAU3E;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,0BAA0B,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CAsCnE"}

package/lib/types/client/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/client/index.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAA0B,MAAM,wCAAwC,CAAA;AAkBnG,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,cAAc,CAAA;AAEhD,OAAO,QAAQ,kCAAkC,CAAC;IAChD,UAAU,kBAAkB;QAC1B,sCAAsC;QACtC,WAAW,EAAE,YAAY,CAAA;KAC1B;CACF;AAED,0GAA0G;AAC1G,eAAO,MAAM,MAAM,UAAgF,CAAA;AAEnG;;;;;GAKG;AACH,wBAAgB,KAAK,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CAqL9C"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/client/index.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAA0B,MAAM,wCAAwC,CAAA;AAoBnG,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,cAAc,CAAA;AAEhD,OAAO,QAAQ,kCAAkC,CAAC;IAChD,UAAU,kBAAkB;QAC1B,sCAAsC;QACtC,WAAW,EAAE,YAAY,CAAA;KAC1B;CACF;AAED,0GAA0G;AAC1G,eAAO,MAAM,MAAM,UAAgF,CAAA;AAEnG;;;;;GAKG;AACH,wBAAgB,KAAK,CAAC,GAAG,EAAE,aAAa,GAAG,IAAI,CA+L9C"}

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

@@ -1,2 +1,2 @@
-export declare const BASE_CSS = "\n/* ---------- safe-area variables (S2.1, 2026-08-17) ----------\n   Every safe-area use in this stylesheet reads --mnav-sat / --mnav-sab\n   instead of env() directly. Same computed value by default, but the\n   indirection gives one place to override: ?mobile-nav-inset=54 (client/\n   debug.ts) writes a fake inset onto the root element, so a desktop CDP\n   run can regress notch layout \u2014 env(safe-area-inset-*) is hard 0 in every\n   desktop browser, which is exactly why the header and the workbench\n   panel shipped broken to a real iPhone. */\n:root {\n  --mnav-sat: env(safe-area-inset-top, 0px);\n  --mnav-sab: env(safe-area-inset-bottom, 0px);\n}\n\n/* ---------- base control styles (rendered at any width, hidden where unused) ---------- */\n\n[data-mobile-nav=\"toggle\"],\n[data-mobile-nav=\"files\"] {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  width: 28px;\n  height: 28px;\n  flex: none;\n  padding: 0;\n  border: none;\n  border-radius: 50%;\n  background: transparent;\n  color: var(--dsw-alias-label-secondary, inherit);\n  cursor: pointer;\n  -webkit-tap-highlight-color: transparent;\n}\n[data-mobile-nav=\"toggle\"]:hover,\n[data-mobile-nav=\"files\"]:hover {\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n}\n[data-mobile-nav=\"toggle\"]:focus-visible,\n[data-mobile-nav=\"files\"]:focus-visible {\n  outline: 2px solid var(--dsw-alias-state-business-primary, #4f6ef7);\n  outline-offset: 1px;\n}\n\n/* Drawer footer actions: the relocated Session log download plus the Files\n   action that opens the dsh-web-ui explorer sheet. */\n[data-mobile-nav=\"drawer-actions\"] {\n  display: inline-flex;\n  align-items: center;\n  gap: 8px;\n}\n[data-mobile-nav=\"session-log\"],\n[data-mobile-nav=\"explorer\"] {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  gap: 6px;\n  height: 34px;\n  padding: 0 12px;\n  border: 1px solid var(--dsw-alias-border-l1, rgba(0, 0, 0, .12));\n  border-radius: 12px;\n  background: transparent;\n  color: var(--dsw-alias-label-primary, inherit);\n  font-family: inherit;\n  font-size: 13px;\n  line-height: 20px;\n  cursor: pointer;\n  -webkit-tap-highlight-color: transparent;\n}\n[data-mobile-nav=\"session-log\"]:hover:not(:disabled),\n[data-mobile-nav=\"explorer\"]:hover {\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n}\n[data-mobile-nav=\"session-log\"]:disabled {\n  color: var(--dsw-alias-label-dimmed, rgba(0, 0, 0, .35));\n  cursor: default;\n}\n\n/* Floating fallback button (hero / blank phases without a session header).\n   The top clears the camera band below the status bar; when the client has\n   set viewport-fit=cover the safe-area inset moves it below the notch too. */\n[data-mobile-nav=\"fab\"] {\n  position: absolute;\n  top: calc(var(--mnav-sat) + 72px);\n  left: 10px;\n  z-index: 21;\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  width: 38px;\n  height: 38px;\n  padding: 0;\n  border: 1px solid var(--dsw-alias-border-l1, rgba(0, 0, 0, .12));\n  border-radius: 50%;\n  background: var(--dsw-alias-button-floating-fill, #ffffff);\n  color: var(--dsw-alias-label-primary, inherit);\n  cursor: pointer;\n  box-shadow: 0 2px 12px rgba(0, 0, 0, .18);\n  -webkit-tap-highlight-color: transparent;\n}\n[data-mobile-nav=\"fab\"]:hover {\n  background: var(--dsw-alias-button-floating-hover, rgba(0, 0, 0, .08));\n}\n[data-mobile-nav=\"fab\"]:focus-visible {\n  outline: 2px solid var(--dsw-alias-state-business-primary, #4f6ef7);\n  outline-offset: 2px;\n}\n\n/* Dimmed backdrop under the open drawer; above every column, below the drawer. */\n[data-mobile-nav=\"backdrop\"] {\n  position: absolute;\n  inset: 0;\n  z-index: 30;\n  background: rgba(0, 0, 0, .45);\n  cursor: pointer;\n  animation: dsh-mobile-nav-fade .2s var(--ds-ease-in-out, ease-in-out);\n  -webkit-tap-highlight-color: transparent;\n}\n@keyframes dsh-mobile-nav-fade {\n  from { opacity: 0; }\n  to { opacity: 1; }\n}\n/* Settings sheet entrance: the official dialog mounts with no animation at\n   all, so it snaps in. Fade + slight rise/scale reads as a proper sheet. */\n@keyframes dsh-mobile-nav-sheet-in {\n  from {\n    opacity: 0;\n    transform: translateY(14px) scale(.98);\n  }\n  to {\n    opacity: 1;\n    transform: none;\n  }\n}\n/* Preview sheet rise: the aionui preview column opens as a bottom sheet. */\n@keyframes dsh-mobile-nav-sheet-up {\n  from {\n    opacity: 0;\n    transform: translateY(28px);\n  }\n  to {\n    opacity: 1;\n    transform: none;\n  }\n}\n\n/* ---------- beta-notice suppression (ALL widths \u2014 deliberate exception) ----\n   User-directed (2026-08-17): hide DSH's beta/preview notices everywhere,\n   including desktop. This is the ONE place this plugin intentionally breaks\n   its own \">=1024px strict no-op\" rule \u2014 do not \"fix\" it back.\n   Selector notes:\n   - The hero \"\u9884\u89C8\u7248\" badge only carries a hashed class; per repo convention\n     the stable part is the suffix (_previewBadge), matched with [class$=].\n   - The first-run \"\u5185\u6D4B\u58F0\u660E\" modal is hidden via its ARIA label. The label is\n     LOCALIZED \u2014 zh is covered; if the UI runs in another language the dialog\n     shows (harmless, dismiss by hand). Hiding targets the presentation\n     wrapper via :has() so the modal's backdrop cannot linger invisibly and\n     block taps; the app never requires acknowledging this dialog to work. */\n[class$=\"_previewBadge\"] {\n  display: none !important;\n}\n[role=\"presentation\"]:has(> [role=\"dialog\"][aria-label=\"\u5185\u6D4B\u58F0\u660E\"]),\n[role=\"dialog\"][aria-label=\"\u5185\u6D4B\u58F0\u660E\"] {\n  display: none !important;\n}\n";
+export declare const BASE_CSS = "\n/* ---------- safe-area variables (S2.1, 2026-08-17) ----------\n   Every safe-area use in this stylesheet reads --mnav-sat / --mnav-sab\n   instead of env() directly. Same computed value by default, but the\n   indirection gives one place to override: ?mobile-nav-inset=54 (client/\n   debug.ts) writes a fake inset onto the root element, so a desktop CDP\n   run can regress notch layout \u2014 env(safe-area-inset-*) is hard 0 in every\n   desktop browser, which is exactly why the header and the workbench\n   panel shipped broken to a real iPhone. */\n:root {\n  --mnav-sat: env(safe-area-inset-top, 0px);\n  --mnav-sab: env(safe-area-inset-bottom, 0px);\n}\n\n/* ---------- base control styles (rendered at any width, hidden where unused) ---------- */\n\n[data-mobile-nav=\"toggle\"],\n[data-mobile-nav=\"files\"] {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  width: 28px;\n  height: 28px;\n  flex: none;\n  padding: 0;\n  border: none;\n  border-radius: 50%;\n  background: transparent;\n  color: var(--dsw-alias-label-secondary, inherit);\n  cursor: pointer;\n  -webkit-tap-highlight-color: transparent;\n}\n[data-mobile-nav=\"toggle\"]:hover,\n[data-mobile-nav=\"files\"]:hover {\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n}\n[data-mobile-nav=\"toggle\"]:focus-visible,\n[data-mobile-nav=\"files\"]:focus-visible {\n  outline: 2px solid var(--dsw-alias-state-business-primary, #4f6ef7);\n  outline-offset: 1px;\n}\n\n/* Drawer footer actions: the relocated Session log download plus the Files\n   action that opens the dsh-web-ui explorer sheet. */\n[data-mobile-nav=\"drawer-actions\"] {\n  display: inline-flex;\n  align-items: center;\n  gap: 8px;\n}\n[data-mobile-nav=\"session-log\"],\n[data-mobile-nav=\"explorer\"] {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  gap: 6px;\n  height: 34px;\n  padding: 0 12px;\n  border: 1px solid var(--dsw-alias-border-l1, rgba(0, 0, 0, .12));\n  border-radius: 12px;\n  background: transparent;\n  color: var(--dsw-alias-label-primary, inherit);\n  font-family: inherit;\n  font-size: 13px;\n  line-height: 20px;\n  cursor: pointer;\n  -webkit-tap-highlight-color: transparent;\n}\n[data-mobile-nav=\"session-log\"]:hover:not(:disabled),\n[data-mobile-nav=\"explorer\"]:hover {\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n}\n[data-mobile-nav=\"session-log\"]:disabled {\n  color: var(--dsw-alias-label-dimmed, rgba(0, 0, 0, .35));\n  cursor: default;\n}\n\n/* Floating fallback button (hero / blank phases without a session header).\n   The top clears the camera band below the status bar; when the client has\n   set viewport-fit=cover the safe-area inset moves it below the notch too. */\n[data-mobile-nav=\"fab\"] {\n  position: absolute;\n  top: calc(var(--mnav-sat) + 72px);\n  left: 10px;\n  z-index: 21;\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  width: 38px;\n  height: 38px;\n  padding: 0;\n  border: 1px solid var(--dsw-alias-border-l1, rgba(0, 0, 0, .12));\n  border-radius: 50%;\n  background: var(--dsw-alias-button-floating-fill, #ffffff);\n  color: var(--dsw-alias-label-primary, inherit);\n  cursor: pointer;\n  box-shadow: 0 2px 12px rgba(0, 0, 0, .18);\n  -webkit-tap-highlight-color: transparent;\n}\n[data-mobile-nav=\"fab\"]:hover {\n  background: var(--dsw-alias-button-floating-hover, rgba(0, 0, 0, .08));\n}\n[data-mobile-nav=\"fab\"]:focus-visible {\n  outline: 2px solid var(--dsw-alias-state-business-primary, #4f6ef7);\n  outline-offset: 2px;\n}\n\n/* Dimmed backdrop under the open drawer; above every column, below the drawer. */\n[data-mobile-nav=\"backdrop\"] {\n  position: absolute;\n  inset: 0;\n  z-index: 30;\n  background: rgba(0, 0, 0, .45);\n  cursor: pointer;\n  animation: dsh-mobile-nav-fade .2s var(--ds-ease-in-out, ease-in-out);\n  -webkit-tap-highlight-color: transparent;\n}\n@keyframes dsh-mobile-nav-fade {\n  from { opacity: 0; }\n  to { opacity: 1; }\n}\n/* Settings sheet entrance: the official dialog mounts with no animation at\n   all, so it snaps in. Fade + slight rise/scale reads as a proper sheet. */\n@keyframes dsh-mobile-nav-sheet-in {\n  from {\n    opacity: 0;\n    transform: translateY(14px) scale(.98);\n  }\n  to {\n    opacity: 1;\n    transform: none;\n  }\n}\n/* Preview sheet rise: the aionui preview column opens as a bottom sheet. */\n@keyframes dsh-mobile-nav-sheet-up {\n  from {\n    opacity: 0;\n    transform: translateY(28px);\n  }\n  to {\n    opacity: 1;\n    transform: none;\n  }\n}\n\n/* ---------- beta-notice handling (ALL widths \u2014 deliberate exception) ----\n   User-directed (2026-08-17): tone down DSH's beta/preview notices\n   everywhere, including desktop. This is the ONE place this plugin\n   intentionally breaks its own \">=1024px strict no-op\" rule.\n   - The hero \"\u9884\u89C8\u7248\" badge only carries a hashed class; per repo convention\n     the stable part is the suffix (_previewBadge), matched with [class$=].\n   - The first-run \"\u5185\u6D4B\u58F0\u660E\" modal must NOT be hidden with CSS: while it is\n     mounted it holds document #root inert, so display:none leaves the whole\n     app unclickable (2026-08-18 incident). effects/welcome-notice.ts instead\n     injects a \"\u4E0D\u518D\u5F39\u51FA\" opt-out button; this styles it. */\n[class$=\"_previewBadge\"] {\n  display: none !important;\n}\n/* Mirrors the official primitives Button (md capsule, outline variant):\n   36px height, 18px radius, --dsw-alias-border-l2 hairline. */\n.zen-welcome-optout {\n  display: inline-flex;\n  align-items: center;\n  justify-content: center;\n  height: 36px;\n  padding: 0 14px;\n  margin-right: 8px;\n  border: 1px solid var(--dsw-alias-border-l2, rgba(0, 0, 0, .15));\n  border-radius: 18px;\n  background: transparent;\n  color: var(--dsw-alias-label-primary, inherit);\n  font-size: 14px;\n  line-height: 22px;\n  cursor: pointer;\n  -webkit-tap-highlight-color: transparent;\n}\n.zen-welcome-optout:hover {\n  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));\n}\n";
 //# sourceMappingURL=base.css.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"base.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/base.css.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,QAAQ,moLAmKpB,CAAA"}
+{"version":3,"file":"base.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/base.css.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,QAAQ,y/LAkLpB,CAAA"}

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

@@ -0,0 +1,2 @@
+export declare const CONTENT_CSS = "/* ---------- chat markdown content (< 768px) ---------- */\n\n@media (max-width: 767px) {\n  /* Inline code: upstream renders it display:inline-flex \u2014 an atomic inline\n     box that can never wrap across lines, so one long code span walks off\n     the right edge of the screen. Plain inline keeps the background pill\n     per line fragment and lets long tokens break anywhere. Deliberately\n     unscoped (any :not(pre) > code, not just the _markdown_ module):\n     inline code also renders outside that container (user bubbles,\n     reasoning rows), and on a phone there is no width at which an\n     unwrappable inline box is right. !important beats the upstream\n     display:inline-flex on specificity ties. */\n  :not(pre) > code {\n    display: inline !important;\n    overflow-wrap: anywhere;\n    /* iOS WebKit: overflow-wrap alone still failed to break long tokens in\n       inline code on a real iPhone (screenshot-verified 2026-08-18, li >\n       code path case) while desktop Chromium broke them fine. break-all is\n       the everywhere-supported hammer; acceptable for code pills. */\n    word-break: break-all;\n  }\n  /* Belt-and-suspenders for engines that compute soft-wrap opportunities\n     from the block container rather than the inline itself (historical\n     WebKit behavior): inherit anywhere through the whole transcript so the\n     block side agrees. Prose is untouched until something would overflow;\n     the table is already pinned wide by min-width: max-content below. */\n  [data-chat-flow],\n  [class*=\"_markdown_\"] {\n    overflow-wrap: anywhere;\n  }\n\n  /* Markdown tables: the official _tableScroll_ wrapper is already a\n     horizontal scroll viewport around a width:max-content table, but its\n     cells are capped at min(30vw, 320px) \u2014 barely 120px on a phone, which\n     crushes every column into a vertical word-stack. Let columns size to\n     their content instead and read the overflow by scrolling the wrapper.\n     480px (not a vw cap \u2014 85vw was ~320px on a 375px phone and still\n     wrapped mid-length cells) keeps typical cells on one line; only truly\n     prose-heavy cells wrap, instead of dragging the table kilometers\n     wide. */\n  [class*=\"_tableScroll_\"] th,\n  [class*=\"_tableScroll_\"] td {\n    max-width: 480px !important;\n  }\n\n  /* iOS WebKit fallback: upstream's own table { width: max-content } is what\n     keeps the table at its natural width inside the scroll wrapper, but\n     WebKit's max-content support on table boxes is incomplete \u2014 on a real\n     iPhone the table fell back to shrink-to-fit and every column got\n     crushed to its min-width (the \"ra/nk\" vertical-word-stack screenshot,\n     2026-08-18). Redeclare the natural-width intent with both width and\n     min-width so whichever keyword the engine honors wins; the wrapper\n     already scrolls the overflow. */\n  [class*=\"_tableScroll_\"] table {\n    width: max-content !important;\n    min-width: max-content !important;\n    max-width: none !important;\n  }\n\n  /* Turn-tail metadata (2026-08-18): the timing stats (\"18:06 \u00B7 \u7528\u65F6 29\u79D2 \u00B7\n     \u9996 token 0.9\u79D2 \u00B7 163 tok/s\") are desktop-hover-revealed (official\n     [data-time-hover-root] gate holds them at opacity 0 until :hover /\n     :focus-within) \u2014 a phone never hovers, so they were simply invisible;\n     and even ignoring that, the row is nowrap + overflow:hidden (plus this\n     plugin's own legacy ellipsis clamp in layout.css.ts), which clipped the\n     text. On phones: always visible, own full-width line under the action\n     icons, wrapping freely, one type size down. !important + the extra\n     [class$=\"_actions\"] hop out-specifies both upstream and layout.css.ts. */\n  /* Pin the tail row's width chain before allowing wrap: with wrap enabled\n     the row's intrinsic (shrink-to-fit) width collapses to its widest\n     single icon, taking the whole tail down to ~16px. */\n  [data-chat-flow-kind=\"turn-tail\"] [class$=\"_root\"],\n  [data-chat-flow-kind=\"turn-tail\"] [class$=\"_actions\"] {\n    width: 100%;\n  }\n  [data-chat-flow-kind=\"turn-tail\"] [class$=\"_actions\"] {\n    flex-wrap: wrap;\n    row-gap: 2px;\n  }\n  /* Wide companion to the rule below: mirrors the upstream hover-gate\n     selector shape directly, with no assumptions about the tail's DOM\n     structure, so the stats can't stay invisible even if the phone's tail\n     renders differently than desktop. */\n  [data-time-hover-root] [class$=\"_timeEnd\"],\n  [data-time-hover-root] [class$=\"_timeStart\"] {\n    opacity: 1 !important;\n    transition: none !important;\n  }\n  [data-chat-flow-kind=\"turn-tail\"] [class$=\"_actions\"] [class$=\"_timeEnd\"] {\n    opacity: 1 !important;\n    flex-basis: 100% !important;\n    white-space: normal !important;\n    overflow: visible !important;\n    text-overflow: clip !important;\n    padding-left: 0 !important;\n    font-size: 12px;\n    line-height: 18px;\n  }\n}\n";
+//# sourceMappingURL=content.css.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"content.css.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/content.css.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,WAAW,i6JAmGvB,CAAA"}

package/lib/types/client/styles/index.d.ts

@@ -8,8 +8,9 @@
  * 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. Injected as ONE
- * <style data-plugin> tag — do not reorder.
+ * 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.
  */
 export declare const MOBILE_CSS: string;
 //# sourceMappingURL=index.d.ts.map

package/lib/types/client/styles/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/index.ts"],"names":[],"mappings":"AAWA;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,UAAU,QAAkI,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/client/styles/index.ts"],"names":[],"mappings":"AAYA;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,UAAU,QAA+I,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-zen-remote",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "把 DeepSeek Harness 变成手机 App：移动端界面重排（两级页面栈、会话列表主屏、composer 重排、手势、附件上传）+ 配对码认证网关 + PWA 安装 + 真 Web Push。Complete mobile plugin for DeepSeek Harness (DSH): app-shell mobile UI, pairing-code gateway for public-internet access behind your own reverse proxy, installable PWA, offline service worker, and real Web Push agent-done notifications.",
   "license": "MIT",
   "type": "module",

package/pwa/app.css

@@ -86,9 +86,14 @@ html:not([data-lan-device="desktop"]) [data-slot="conversation"] [data-phase] {
 
 /* Scroll long code lines horizontally instead of letting them widen the
  * page. dsh-mobile-nav has no equivalent rule; dropping this would let a
- * long code block push the whole phone layout into horizontal scroll. */
+ * long code block push the whole phone layout into horizontal scroll.
+ * pre + pre code ONLY: the old bare `code` selector also hit INLINE code,
+ * whose white-space:pre vetoed every wrapping property and clipped long
+ * paths off-screen on phones — while desktop loopback (which never loads
+ * this file) wrapped fine. Days of "why only on the phone" (2026-08-18);
+ * inline-code wrapping is owned by styles/content.css.ts. */
 html:not([data-lan-device="desktop"]) pre,
-html:not([data-lan-device="desktop"]) code {
+html:not([data-lan-device="desktop"]) pre code {
   white-space: pre;
   overflow-x: auto;
   -webkit-overflow-scrolling: touch;

package/src/client/effects/keyboard-guard.ts

@@ -0,0 +1,121 @@
+import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client'
+
+/** Phone breakpoint — same query every phone-only effect in this plugin uses. */
+const PHONE_QUERY = '(max-width: 767px)'
+
+/** The official composer slot wrapper (same marker composer.css.ts styles). */
+const COMPOSER = '[data-slot="conversation.composer.bar"]'
+
+/** A tap/keystroke older than this no longer explains a focus. */
+const INTENT_WINDOW_MS = 1000
+
+/**
+ * S9 — keep the phone keyboard down until the user asks for it.
+ *
+ * dsh-client-ui-conversation focuses the composer textarea on every
+ * sessionId change (lib/client.js:3423 — el.focus({preventScroll:true}) in a
+ * [locked, sessionId] effect). Sensible on desktop; on a phone it pops the
+ * software keyboard over half the screen every time a session opens.
+ *
+ * Rule: focus on the composer textarea survives only when the user asked for
+ * it — a tap on the textarea itself or typing on a hardware keyboard.
+ * Anything else (session-open autofocus, push-deep-link opens, the refocus
+ * side effects of the other composer buttons — slash-command toggle, attach,
+ * send) is blurred.
+ *
+ * Two triggers, because one is not enough:
+ * - focusin catches the autofocus the moment it happens;
+ * - a body MutationObserver re-runs the check after transcript swaps
+ *   (opening a session re-renders the flow but may reuse the same textarea,
+ *   and a focus that landed before this plugin loaded never fired focusin
+ *   for us at all).
+ * Once focus is user-granted it stays granted until the textarea blurs, so
+ * the observer never yanks a keyboard the user opened (e.g. while the agent
+ * streams and the user pauses typing).
+ */
+export function installKeyboardGuard(ctx: ClientContext): void {
+  ctx.effect(() => {
+    const narrow = window.matchMedia(PHONE_QUERY)
+    let lastIntent = 0
+    let granted = false
+    let observer: MutationObserver | null = null
+    let frame = 0
+
+    const composerTextarea = (node: unknown): HTMLElement | null =>
+      node instanceof HTMLElement && node.tagName === 'TEXTAREA' && node.closest(COMPOSER) !== null
+        ? node
+        : null
+
+    const onPointerDown = (event: PointerEvent): void => {
+      // Only the textarea itself grants the keyboard. A tap on any other
+      // composer control (slash-command toggle, attach, model menu, send)
+      // must not: several of them refocus the input as a side effect, which
+      // popped the keyboard on every command-button tap.
+      if (composerTextarea(event.target) !== null) {
+        lastIntent = Date.now()
+        granted = true
+      }
+    }
+    const onKeyDown = (): void => {
+      lastIntent = Date.now()
+      if (composerTextarea(document.activeElement) !== null) granted = true
+    }
+    const sweep = (): void => {
+      const el = composerTextarea(document.activeElement)
+      if (el === null) return
+      if (granted || Date.now() - lastIntent < INTENT_WINDOW_MS) {
+        granted = true
+        return
+      }
+      el.blur()
+    }
+    const onFocusIn = (event: FocusEvent): void => {
+      if (composerTextarea(event.target) === null) return
+      sweep()
+    }
+    const onFocusOut = (event: FocusEvent): void => {
+      if (composerTextarea(event.target) === null) return
+      granted = false
+    }
+    const schedule = (): void => {
+      if (observer === null || frame !== 0) return
+      // setTimeout, not requestAnimationFrame: rAF pauses in hidden/
+      // backgrounded pages, where the autofocus still happens — the sweep
+      // must run there too or the keyboard pops when the page is foregrounded.
+      frame = window.setTimeout(() => {
+        frame = 0
+        sweep()
+      }, 100)
+    }
+
+    const attach = (): void => {
+      if (observer !== null) return
+      document.addEventListener('pointerdown', onPointerDown, { capture: true, passive: true })
+      document.addEventListener('keydown', onKeyDown, { capture: true, passive: true })
+      document.addEventListener('focusin', onFocusIn, true)
+      document.addEventListener('focusout', onFocusOut, true)
+      observer = new MutationObserver(schedule)
+      observer.observe(document.body, { childList: true, subtree: true })
+      sweep()
+    }
+    const detach = (): void => {
+      document.removeEventListener('pointerdown', onPointerDown, true)
+      document.removeEventListener('keydown', onKeyDown, true)
+      document.removeEventListener('focusin', onFocusIn, true)
+      document.removeEventListener('focusout', onFocusOut, true)
+      observer?.disconnect()
+      observer = null
+      if (frame !== 0) window.clearTimeout(frame)
+      frame = 0
+      granted = false
+    }
+
+    if (narrow.matches) attach()
+    const onChange = (event: MediaQueryListEvent): void => (event.matches ? attach() : detach())
+    narrow.addEventListener('change', onChange)
+    return () => {
+      narrow.removeEventListener('change', onChange)
+      detach()
+    }
+  }, 'dsh-mobile-nav: composer keyboard guard')
+}

package/src/client/effects/turn-fold.ts

@@ -160,11 +160,13 @@ export function installTurnFold(ctx: ClientContext): void {
       const running = flow.querySelector(':scope > [role="status"]') !== null
       const groups = groupsOf(flow)
       const live = new Set<string>()
+      const liveItems = new Set<Element>()
 
       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)
@@ -189,6 +191,18 @@ export function installTurnFold(ctx: ClientContext): void {
         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 schedule = (): void => {

package/src/client/effects/welcome-notice.ts

@@ -0,0 +1,66 @@
+import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client'
+
+/** Per-browser opt-out flag; localStorage because remote (non-loopback)
+    connections never persist the acknowledgement host-side. */
+const OPTOUT_KEY = 'dsh-zen-remote:welcome-notice-optout'
+
+/** Localized aria-labels of the DSH first-run notice dialog
+    (@deepseek-ai/dsh-client-ui-settings-models WELCOME_NOTICE_COPY). */
+const NOTICE_LABELS = ['内测声明', 'Internal Testing Notice']
+
+/**
+ * "内测声明" first-run notice, opt-out half (ALL widths — same user-directed
+ * exception as the _previewBadge rule in styles/base.css.ts).
+ *
+ * Why not CSS: the notice dialog keeps document #root inert while MOUNTED and
+ * only restores it on unmount (its acknowledge button). display:none hid the
+ * dialog without unmounting it, which left the whole app permanently
+ * unclickable on remote connections (2026-08-18 incident) — remote browsers
+ * re-mount the notice on every page load because their acknowledgement is
+ * memory-only (`connection.isLoopback ? "host" : "memory"` upstream).
+ *
+ * So the dialog now shows normally, plus one injected "不再弹出" button. The
+ * user chooses: acknowledging via that button records the opt-out in this
+ * browser's localStorage, and later mounts are auto-acknowledged by clicking
+ * the dialog's own continue button — the component unmounts through its
+ * normal path and #root's inert is properly restored.
+ */
+export function installWelcomeNoticeOptOut(ctx: ClientContext): void {
+  ctx.effect(() => {
+    const handle = (dialog: HTMLElement): void => {
+      // The notice's action row holds exactly one button ("继续"/"Continue").
+      const continueBtn = dialog.querySelector('button')
+      if (continueBtn === null) return
+      if (localStorage.getItem(OPTOUT_KEY) !== null) {
+        continueBtn.click()
+        return
+      }
+      const row = continueBtn.parentElement
+      if (row === null || row.querySelector('.zen-welcome-optout') !== null) return
+      const optOut = document.createElement('button')
+      optOut.type = 'button'
+      optOut.className = 'zen-welcome-optout'
+      optOut.textContent =
+        dialog.getAttribute('aria-label') === '内测声明' ? '不再弹出' : "Don't show again"
+      optOut.addEventListener('click', () => {
+        localStorage.setItem(OPTOUT_KEY, '1')
+        continueBtn.click()
+      })
+      row.insertBefore(optOut, continueBtn)
+    }
+    const scan = (): void => {
+      for (const label of NOTICE_LABELS) {
+        const dialog = document.querySelector<HTMLElement>(
+          `[role="dialog"][aria-label="${label}"]`,
+        )
+        if (dialog !== null) handle(dialog)
+      }
+    }
+    // The dialog portals straight under <body>, so childList on body is
+    // enough; scan() once first in case it mounted before this plugin loaded.
+    scan()
+    const observer = new MutationObserver(scan)
+    observer.observe(document.body, { childList: true })
+    return () => observer.disconnect()
+  }, 'dsh-mobile-nav: welcome-notice opt-out')
+}

package/src/client/index.tsx

@@ -15,6 +15,8 @@ import { installAionuiCompat } from './effects/aionui-compat.ts'
 import { installHeaderStatusDot } from './effects/header-status.ts'
 import { installGestures } from './effects/gestures.ts'
 import { installTurnFold } from './effects/turn-fold.ts'
+import { installWelcomeNoticeOptOut } from './effects/welcome-notice.ts'
+import { installKeyboardGuard } from './effects/keyboard-guard.ts'
 import { NS, en, zh } from './locales.ts'
 import type { MobileNavKey } from './locales.ts'
 
@@ -78,6 +80,16 @@ export function apply(ctx: ClientContext): void {
   // not carry this.
   installTurnFold(ctx)
 
+  // "内测声明" first-run notice: keep it visible (CSS-hiding it leaked the
+  // dialog's #root inert lock — see effects/welcome-notice.ts) and offer a
+  // per-browser "不再弹出" opt-out instead.
+  installWelcomeNoticeOptOut(ctx)
+
+  // S9: opening a session must not pop the phone keyboard — the official
+  // composer autofocuses on every sessionId change; keep focus only when the
+  // user tapped the composer (or typed) themselves.
+  installKeyboardGuard(ctx)
+
   // Page-stack store (apply world) — created before any registration so
   // every slot below (the phone home screen, the session header's back
   // button) shares the exact same handle/instance.

package/src/client/styles/base.css.ts

@@ -145,23 +145,38 @@ export const BASE_CSS = `
   }
 }
 
-/* ---------- beta-notice suppression (ALL widths — deliberate exception) ----
-   User-directed (2026-08-17): hide DSH's beta/preview notices everywhere,
-   including desktop. This is the ONE place this plugin intentionally breaks
-   its own ">=1024px strict no-op" rule — do not "fix" it back.
-   Selector notes:
+/* ---------- beta-notice handling (ALL widths — deliberate exception) ----
+   User-directed (2026-08-17): tone down DSH's beta/preview notices
+   everywhere, including desktop. This is the ONE place this plugin
+   intentionally breaks its own ">=1024px strict no-op" rule.
    - The hero "预览版" badge only carries a hashed class; per repo convention
      the stable part is the suffix (_previewBadge), matched with [class$=].
-   - The first-run "内测声明" modal is hidden via its ARIA label. The label is
-     LOCALIZED — zh is covered; if the UI runs in another language the dialog
-     shows (harmless, dismiss by hand). Hiding targets the presentation
-     wrapper via :has() so the modal's backdrop cannot linger invisibly and
-     block taps; the app never requires acknowledging this dialog to work. */
+   - The first-run "内测声明" modal must NOT be hidden with CSS: while it is
+     mounted it holds document #root inert, so display:none leaves the whole
+     app unclickable (2026-08-18 incident). effects/welcome-notice.ts instead
+     injects a "不再弹出" opt-out button; this styles it. */
 [class$="_previewBadge"] {
   display: none !important;
 }
-[role="presentation"]:has(> [role="dialog"][aria-label="内测声明"]),
-[role="dialog"][aria-label="内测声明"] {
-  display: none !important;
+/* Mirrors the official primitives Button (md capsule, outline variant):
+   36px height, 18px radius, --dsw-alias-border-l2 hairline. */
+.zen-welcome-optout {
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  height: 36px;
+  padding: 0 14px;
+  margin-right: 8px;
+  border: 1px solid var(--dsw-alias-border-l2, rgba(0, 0, 0, .15));
+  border-radius: 18px;
+  background: transparent;
+  color: var(--dsw-alias-label-primary, inherit);
+  font-size: 14px;
+  line-height: 22px;
+  cursor: pointer;
+  -webkit-tap-highlight-color: transparent;
+}
+.zen-welcome-optout:hover {
+  background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
 }
 `

package/src/client/styles/content.css.ts

@@ -0,0 +1,103 @@
+// content — chat markdown readability on phones (2026-08-18). Shares no
+// selector with any other file; appended last in styles/index.ts.
+
+export const 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;
+  }
+
+  /* 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;
+  }
+}
+`

package/src/client/styles/index.ts

@@ -8,6 +8,7 @@ import { COMPOSER_CSS } from './composer.css.ts'
 import { INFO_CSS } from './info.css.ts'
 import { TURN_FOLD_CSS } from './turn-fold.css.ts'
 import { CHIPS_CSS } from './chips.css.ts'
+import { CONTENT_CSS } from './content.css.ts'
 
 /**
  * All mobile styles, concatenated in the exact order of the original
@@ -19,7 +20,8 @@ import { CHIPS_CSS } from './chips.css.ts'
  * 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. Injected as ONE
- * <style data-plugin> tag — do not reorder.
+ * 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.
  */
-export const MOBILE_CSS = [BASE_CSS, LAYOUT_CSS, COMPAT_CSS, MISC_CSS, HOME_CSS, HEADER_CSS, COMPOSER_CSS, INFO_CSS, TURN_FOLD_CSS, CHIPS_CSS].join('\n')
+export const MOBILE_CSS = [BASE_CSS, LAYOUT_CSS, COMPAT_CSS, MISC_CSS, HOME_CSS, HEADER_CSS, COMPOSER_CSS, INFO_CSS, TURN_FOLD_CSS, CHIPS_CSS, CONTENT_CSS].join('\n')