dsh-zen-remote 1.1.2 → 1.1.3

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

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAIH,OAAO,KAAK,EAAE,eAAe,EAAE,cAAc,EAAE,MAAM,WAAW,CAAA;AAEhE,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,qBAAqB,CAAA;AAIlD,6DAA6D;AAC7D,eAAO,MAAM,YAAY,4BAA4B,CAAA;AAErD;;kEAEkE;AAClE,eAAO,MAAM,mBAAmB,mCAAmC,CAAA;AAEnE,+FAA+F;AAC/F,eAAO,MAAM,UAAU,iBAAiB,CAAA;AAExC,6DAA6D;AAC7D,eAAO,MAAM,wBAAwB,QAAmB,CAAA;AAQxD,wBAAwB;AACxB,MAAM,WAAW,eAAe;IAC9B,iGAAiG;IACjG,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB;;mEAE+D;IAC/D,eAAe,CAAC,EAAE,OAAO,CAAA;CAC1B;AAwCD;;;;;;;;;GASG;AACH,wBAAgB,cAAc,CAAC,GAAG,EAAE,eAAe,GAAG,OAAO,CAa5D;AAED;;;;;GAKG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,IAAI,CAKnE;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,cAAc,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAgBlD;AA6HD;;;;;;;;;GASG;AACH,wBAAsB,YAAY,CAChC,GAAG,EAAE,OAAO,EACZ,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,eAAe,EACpB,GAAG,EAAE,cAAc,GAClB,OAAO,CAAC,IAAI,CAAC,CA+Bf;AAED;;;;;;;GAOG;AACH,wBAAgB,KAAK,CAAC,GAAG,EAAE,OAAO,EAAE,MAAM,GAAE,eAAoB,GAAG,IAAI,CAyBtE"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAIH,OAAO,KAAK,EAAE,eAAe,EAAE,cAAc,EAAE,MAAM,WAAW,CAAA;AAEhE,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,qBAAqB,CAAA;AAIlD,6DAA6D;AAC7D,eAAO,MAAM,YAAY,4BAA4B,CAAA;AAErD;;kEAEkE;AAClE,eAAO,MAAM,mBAAmB,mCAAmC,CAAA;AAEnE,+FAA+F;AAC/F,eAAO,MAAM,UAAU,iBAAiB,CAAA;AAExC,6DAA6D;AAC7D,eAAO,MAAM,wBAAwB,QAAmB,CAAA;AAQxD,wBAAwB;AACxB,MAAM,WAAW,eAAe;IAC9B,iGAAiG;IACjG,cAAc,CAAC,EAAE,MAAM,CAAA;IACvB;;mEAE+D;IAC/D,eAAe,CAAC,EAAE,OAAO,CAAA;IACzB;;;;;;;gCAO4B;IAC5B,iBAAiB,CAAC,EAAE,MAAM,CAAA;IAC1B,+EAA+E;IAC/E,iBAAiB,CAAC,EAAE,MAAM,CAAA;IAC1B;yCACqC;IACrC,mBAAmB,CAAC,EAAE,MAAM,CAAA;CAC7B;AAED;;;;;;;;;GASG;AACH,wBAAgB,OAAO,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,SAAS,EAAE,GAAG,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAGhH;AAwCD;;;;;;;;;GASG;AACH,wBAAgB,cAAc,CAAC,GAAG,EAAE,eAAe,GAAG,OAAO,CAa5D;AAED;;;;;GAKG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,GAAG,IAAI,CAKnE;AAED;;;;;;;;;;;;;GAaG;AACH,wBAAgB,cAAc,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAgBlD;AA6HD;;;;;;;;;GASG;AACH,wBAAsB,YAAY,CAChC,GAAG,EAAE,OAAO,EACZ,QAAQ,EAAE,MAAM,EAChB,GAAG,EAAE,eAAe,EACpB,GAAG,EAAE,cAAc,GAClB,OAAO,CAAC,IAAI,CAAC,CA+Bf;AAED;;;;;;;GAOG;AACH,wBAAgB,KAAK,CAAC,GAAG,EAAE,OAAO,EAAE,MAAM,GAAE,eAAoB,GAAG,IAAI,CA8BtE"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-zen-remote",
-  "version": "1.1.2",
+  "version": "1.1.3",
   "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",
@@ -81,16 +81,16 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-client-locale": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-client-ui-layout": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-client-ui-sidebar": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-host-webserver": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-session": "^0.1.0-rc.7",
-    "@deepseek-ai/dsh-session-log-export": "^0.1.0-rc.7",
+    "@deepseek-ai/dsh-client-locale": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-client-runtime": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-client-ui-primitives": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-client-ui-sidebar": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-client-ui-slots": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-host-webserver": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-session": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
+    "@deepseek-ai/dsh-session-log-export": ">=0.1.0-rc.7 <0.2.0-0 || >=0.1.1-rc.0 <0.2.0-0",
     "react": "^18.2.0",
     "@deepseek-ai/dsh-tools": ">=0.0.1-rc.1 <0.1.0 || >=0.1.0-rc.1 <0.2.0-0"
   },

package/scripts/check-keyboard-avoid.mjs

@@ -5,6 +5,8 @@
 import assert from 'node:assert/strict'
 import { readFileSync } from 'node:fs'
 import { composerLift, estimatedLift, keyboardLift as lift, safetyPad } from '../src/client/effects/keyboard-avoid.ts'
+import { KEYBOARD_DEFAULTS, parseClientConfig } from '../src/client/client-config.ts'
+import { clamped } from '../src/index.ts'
 
 // The reported class of bug: keyboard shrinks the visual viewport, browser
 // does not pan it — the whole shrink is an occluded band at the bottom.
@@ -88,4 +90,41 @@ assert.match(
   'keyboard-avoid transform must hit the box-generating _root child',
 )
 
+// --- the tuning knobs (2026-08-22) -----------------------------------------
+// The two estimates above are guesses about someone else's hardware, so the
+// plugin row can retune them. What must hold: an install that sets nothing
+// behaves EXACTLY as it did before the knobs existed, and a set value cannot
+// push the composer somewhere there is no way back from.
+
+// Shipped defaults are the values the assertions above were written against.
+assert.deepEqual(KEYBOARD_DEFAULTS, { liftRatio: 0.42, liftMaxPx: 400, safetyPadPx: 15 })
+assert.equal(estimatedLift(858, KEYBOARD_DEFAULTS), estimatedLift(858), 'defaults are the no-config path')
+assert.equal(safetyPad(ANDROID, KEYBOARD_DEFAULTS.safetyPadPx), safetyPad(ANDROID))
+
+// A retuned row moves both halves of the estimate, and the pad.
+assert.equal(estimatedLift(700, { liftRatio: 0.5, liftMaxPx: 400, safetyPadPx: 15 }), 350)
+assert.equal(estimatedLift(858, { liftRatio: 0.5, liftMaxPx: 500, safetyPadPx: 15 }), 429)
+assert.equal(estimatedLift(858, { liftRatio: 0.5, liftMaxPx: 380, safetyPadPx: 15 }), 380, 'cap still wins')
+assert.equal(safetyPad(ANDROID, 40), 40)
+assert.equal(safetyPad(IPHONE, 40), 0, 'a configured pad stays Android-only')
+
+// An empty / failed / garbage route body leaves every default in place — the
+// client half is where the defaults live, so this is the whole contract.
+for (const body of [undefined, null, {}, 'not json', { keyboardLiftRatio: 'big' }, { keyboardLiftRatio: NaN }]) {
+  assert.deepEqual(parseClientConfig(body).keyboard, KEYBOARD_DEFAULTS, `body ${JSON.stringify(body) ?? 'undefined'} keeps defaults`)
+}
+assert.equal(parseClientConfig({ keyboardLiftRatio: 0.5 }).keyboard.liftRatio, 0.5)
+assert.equal(parseClientConfig({ keyboardSafetyPadPx: 0 }).keyboard.safetyPadPx, 0, 'zero is a real value, not "unset"')
+assert.equal(parseClientConfig({ turnFoldDesktop: true }).turnFoldDesktop, true)
+
+// The host clamps before publishing: a typo in the YAML must not be able to
+// push the composer off-screen with no way back except editing the YAML.
+assert.deepEqual(clamped('keyboardLiftRatio', 5, 0, 1), { keyboardLiftRatio: 1 })
+assert.deepEqual(clamped('keyboardLiftRatio', -2, 0, 1), { keyboardLiftRatio: 0 })
+assert.deepEqual(clamped('keyboardLiftMaxPx', 9000, 0, 2000), { keyboardLiftMaxPx: 2000 })
+assert.deepEqual(clamped('keyboardLiftRatio', undefined, 0, 1), {}, 'unset stays absent so the client default wins')
+for (const bad of [Number.NaN, Infinity, '0.5', null]) {
+  assert.deepEqual(clamped('keyboardLiftRatio', bad, 0, 1), {}, `${String(bad)} is not a number`)
+}
+
 console.log('KEYBOARD AVOID CHECK OK')

package/src/client/client-config.ts

@@ -0,0 +1,86 @@
+/**
+ * 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.
+ */
+
+/** Mirror of src/index.ts CLIENT_CONFIG_ROUTE (client tsconfig cannot reach it). */
+export const CLIENT_CONFIG_ROUTE = '/_dsh/mobile-nav/client-config'
+
+/**
+ * Tuning for the estimated-lift path in effects/keyboard-avoid.ts — the
+ * fallback for a keyboard the browser cannot see at all. There is nothing to
+ * measure on those devices, so these are estimates, and estimates about
+ * hardware need a knob: IME toolbars, foldables, and PWA shells all sit at
+ * different heights, and the person holding the phone is the only one who
+ * can see whether the composer cleared the keys.
+ */
+export interface KeyboardTuning {
+  /** Share of the layout viewport the estimated lift starts from. */
+  liftRatio: number
+  /** Ceiling on that estimate, so a tall viewport cannot strand the composer mid-screen. */
+  liftMaxPx: number
+  /** Extra clearance above a keyboard the browser DID react to (Android only). */
+  safetyPadPx: number
+}
+
+/** 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. */
+export const KEYBOARD_DEFAULTS: KeyboardTuning = {
+  liftRatio: 0.42,
+  liftMaxPx: 400,
+  safetyPadPx: 15,
+}
+
+/** Everything the client half reads off the plugin row. */
+export interface ClientConfig {
+  /** Fold each turn's process at every width, not just below the phone breakpoint. */
+  turnFoldDesktop: boolean
+  keyboard: KeyboardTuning
+}
+
+/** 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: unknown, fallback: number): number {
+  return typeof value === 'number' && Number.isFinite(value) ? value : fallback
+}
+
+/** Parse one route body. Exported for scripts/check-client-config.mjs. */
+export function parseClientConfig(body: unknown): ClientConfig {
+  const row: Record<string, unknown> = typeof body === 'object' && body !== null
+    ? body as Record<string, unknown>
+    : {}
+  return {
+    turnFoldDesktop: row['turnFoldDesktop'] === true,
+    keyboard: {
+      liftRatio: num(row['keyboardLiftRatio'], KEYBOARD_DEFAULTS.liftRatio),
+      liftMaxPx: num(row['keyboardLiftMaxPx'], KEYBOARD_DEFAULTS.liftMaxPx),
+      safetyPadPx: num(row['keyboardSafetyPadPx'], KEYBOARD_DEFAULTS.safetyPadPx),
+    },
+  }
+}
+
+let cached: Promise<ClientConfig> | undefined
+
+/** The row config, fetched at most once per page load. Never rejects. */
+export function clientConfig(): Promise<ClientConfig> {
+  cached ??= fetch(CLIENT_CONFIG_ROUTE, { cache: 'no-store' })
+    .then((res) => (res.ok ? res.json() as Promise<unknown> : undefined))
+    .catch(() => undefined)
+    .then(parseClientConfig)
+  return cached
+}

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

@@ -1,4 +1,5 @@
 import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client'
+import { clientConfig, KEYBOARD_DEFAULTS, type KeyboardTuning } from '../client-config.ts'
 
 /** Phone breakpoint — same query every phone-only effect in this plugin uses. */
 const PHONE_QUERY = '(max-width: 767px)'
@@ -27,14 +28,19 @@ 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
+ * 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 = KEYBOARD_DEFAULTS.safetyPadPx
 
-/** 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. */
-export function safetyPad(userAgent: string): number {
-  return /Android/iu.test(userAgent) ? SAFETY_PAD_PX : 0
+/** 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. */
+export function safetyPad(userAgent: string, padPx: number = SAFETY_PAD_PX): number {
+  return /Android/iu.test(userAgent) ? padPx : 0
 }
 
 /** A viewport that lost at least this much against its no-keyboard baseline
@@ -66,11 +72,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.
  */
-export function estimatedLift(innerHeight: number): number {
-  return Math.min(Math.round(innerHeight * 0.42), 400)
+export function estimatedLift(innerHeight: number, tuning: KeyboardTuning = KEYBOARD_DEFAULTS): number {
+  return Math.min(Math.round(innerHeight * tuning.liftRatio), tuning.liftMaxPx)
 }
 
 /** One visualViewport reading, in CSS pixels. */
@@ -188,7 +199,16 @@ export function installKeyboardAvoid(ctx: ClientContext): void {
      * 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 = KEYBOARD_DEFAULTS
+    let pad = safetyPad(navigator.userAgent)
+    void clientConfig().then((loaded) => {
+      tuning = loaded.keyboard
+      pad = safetyPad(navigator.userAgent, tuning.safetyPadPx)
+    })
 
     const composerTextarea = (node: unknown): boolean =>
       node instanceof HTMLElement && node.tagName === 'TEXTAREA' && node.closest(COMPOSER) !== null
@@ -265,7 +285,7 @@ export function installKeyboardAvoid(ctx: ClientContext): void {
       // 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
@@ -297,7 +317,7 @@ export function installKeyboardAvoid(ctx: ClientContext): void {
         // remember the verdict so the next focus skips the wait.
         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)

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

@@ -1,4 +1,5 @@
 import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client'
+import { clientConfig } from '../client-config.ts'
 import { NS } from '../locales.ts'
 
 /** Phone breakpoint — same query every phone-only effect in this plugin uses. */
@@ -15,8 +16,6 @@ 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(): boolean {
@@ -26,17 +25,10 @@ function desktopOptIn(): boolean {
   return localStorage.getItem(DESKTOP_KEY) === '1'
 }
 
-/** True when the plugin row asks for desktop fold; false on any failure. */
+/** 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(): Promise<boolean> {
-  try {
-    const res = await fetch(CLIENT_CONFIG_ROUTE, { cache: 'no-store' })
-    if (!res.ok) return false
-    const body: unknown = await res.json()
-    return typeof body === 'object' && body !== null
-      && (body as { turnFoldDesktop?: unknown }).turnFoldDesktop === true
-  } catch {
-    return false
-  }
+  return (await clientConfig()).turnFoldDesktop
 }
 
 /** ChatView's flow column (dsh-client-ui-conversation lib/client.js:5512).
@@ -56,19 +48,30 @@ const CHIP_SELECTOR = '[data-mobile-nav="turn-fold"]'
  * 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'])
+export const PROCESS_KINDS = ['context', 'tool-call', 'command'] as const
+const PROCESS_KIND_SET: ReadonlySet<string> = new Set(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. */
-const THINK = '[data-variant="think"]'
+export const THINK = '[data-variant="think"]'
 
-/** Attribute the phone stylesheet turns into `display: none`. */
+/** 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. */
-const OPEN = 'data-mnav-fold-open'
+export const 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'
 
 /**
  * True when the reasoning rows are the ONLY thing this row renders, so the
@@ -98,7 +101,7 @@ function foldsWholeRow(row: Element, thinks: readonly Element[]): boolean {
 function processItems(row: Element): readonly Element[] {
   const kind = row.getAttribute('data-chat-flow-kind')
   if (kind === null) return []
-  if (PROCESS_KINDS.has(kind)) return [row]
+  if (PROCESS_KIND_SET.has(kind)) return [row]
   if (kind !== 'assistant-step') return []
   const thinks = [...row.querySelectorAll(THINK)]
   if (thinks.length === 0) return []
@@ -280,12 +283,14 @@ export function installTurnFold(ctx: ClientContext): void {
 
     const attach = (): void => {
       if (observer !== null) return
+      document.documentElement.setAttribute(ACTIVE_ATTR, '')
       observer = new MutationObserver(schedule)
       observer.observe(document.body, { childList: true, subtree: true })
       document.addEventListener('click', onClick)
       scan()
     }
     const detach = (): void => {
+      document.documentElement.removeAttribute(ACTIVE_ATTR)
       observer?.disconnect()
       observer = null
       document.removeEventListener('click', onClick)

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

@@ -1,6 +1,8 @@
 // compat — split from src/client/mobile.css.ts (2026-08-16), order preserved.
 // Do not reorder: styles/index.ts concatenates in this exact order.
 
+import { UPLOAD_DIR } from '../attach-upload.ts'
+
 export const 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)
@@ -736,4 +738,35 @@ export const 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^="${UPLOAD_DIR}/"]) {
+      display: none !important;
+    }
+    [data-at-file-dock]:not(:has([data-at-file-row] [title]:not([title^="${UPLOAD_DIR}/"]))) {
+      display: none !important;
+    }
+  }
 `

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

@@ -315,9 +315,18 @@ export const 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;
@@ -327,6 +336,57 @@ export const 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;

package/src/client/styles/turn-fold.css.ts

@@ -1,16 +1,53 @@
 // 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.
+// 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.
 
+import { OPEN, PROCESS_KINDS, THINK } from '../effects/turn-fold.ts'
+
+/** 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 = [
+  ...PROCESS_KINDS.map((kind) => `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="${kind}"]:not([${OPEN}])`),
+  `html[${ACTIVE}] [data-chat-flow] > [data-chat-flow-kind="assistant-step"] ${THINK}:not([${OPEN}])`,
+].join(',\n')
+
 /** The fold + chip rules, with every selector prefixed by `scope`. */
 const rules = (scope: string): string => `
   /* Folded process: tool-call / context / command rows and the Think
@@ -97,6 +134,12 @@ const rules = (scope: string): string => `
 
 export const 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"] {

package/src/index.ts

@@ -51,6 +51,35 @@ export interface MobileNavConfig {
    * phone breakpoint. Default false (phone-only). A browser can still opt
    * itself in via `?mobile-nav-turn-fold=1` when this is off. */
   turnFoldDesktop?: boolean
+  /** Calibration for the composer lift used when a phone's keyboard is
+   * invisible to the browser (src/client/effects/keyboard-avoid.ts). Leave
+   * every one of these unset to keep the shipped estimate — the route omits
+   * what the row never set, and the client half owns the defaults, so there
+   * is one place each default is written.
+   *
+   * Share of the layout viewport the estimated lift starts from (shipped
+   * 0.42). Clamped to 0-1. */
+  keyboardLiftRatio?: number
+  /** Ceiling on that estimate in CSS pixels (shipped 400). Clamped to 0-2000. */
+  keyboardLiftMaxPx?: number
+  /** Extra clearance above a keyboard the browser DID react to, Android only
+   * (shipped 15). Clamped to 0-200. */
+  keyboardSafetyPadPx?: number
+}
+
+/**
+ * One configured number on its way to the browser, clamped into a band that
+ * cannot break the composer — a ratio of 5 or a 9000px lift would push the
+ * input clean off the screen with no way back except editing the YAML again.
+ * Absent from the result when the row left it unset or wrote something that
+ * is not a finite number, which leaves the client on its shipped default.
+ *
+ * Exported for scripts/check-keyboard-avoid.mjs — this is the trust boundary
+ * between a hand-edited YAML row and the browser, so it is asserted directly.
+ */
+export function clamped(key: string, value: number | undefined, min: number, max: number): Record<string, number> {
+  if (typeof value !== 'number' || !Number.isFinite(value)) return {}
+  return { [key]: Math.min(Math.max(value, min), max) }
 }
 
 /**
@@ -361,7 +390,12 @@ export function apply(ctx: Context, config: MobileNavConfig = {}): void {
           responseJson(res, 405, { ok: false, error: { code: 'method-not-allowed', message: 'Use GET' } })
           return
         }
-        responseJson(res, 200, { turnFoldDesktop: config.turnFoldDesktop === true })
+        responseJson(res, 200, {
+          turnFoldDesktop: config.turnFoldDesktop === true,
+          ...clamped('keyboardLiftRatio', config.keyboardLiftRatio, 0, 1),
+          ...clamped('keyboardLiftMaxPx', config.keyboardLiftMaxPx, 0, 2000),
+          ...clamped('keyboardSafetyPadPx', config.keyboardSafetyPadPx, 0, 200),
+        })
       },
     }), 'dsh-mobile-nav: client config route')
   })