dsh-zen-remote 1.0.0

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

@@ -0,0 +1,477 @@
+// home — phone-only app shell (S1, 2026-08-17): the full-screen session list
+// and the two-level page stack. Appended LAST so its rules win the ties
+// against the shared <=1023px block in layout/compat/misc.
+//
+// Everything lives inside (max-width: 767px): the tablet range keeps the
+// v1.0.0 drawer and the desktop stays a strict no-op.
+
+export const HOME_CSS = `/* ---------- phone app shell (< 768px) ---------- */
+
+@media (max-width: 767px) {
+  /* --- the document never scrolls (S1.1, 2026-08-17) ---
+     Real-device symptom: the workspace title bar, the session header, the
+     composer and the FAB all slid with the finger — every fixed surface
+     "followed the drag". They are not misplaced; the whole DOCUMENT was
+     rubber-banding under them (they are absolute/in-flow inside the frame,
+     so a document-level bounce moves them all as one).
+
+     After the S2.1 box-sizing fix the document has no overflow at all
+     (scrollHeight === clientHeight, measured with ?mobile-nav-inset=54), so
+     this is not scrolling — it is iOS's elastic overscroll, which happens on
+     an unscrollable document too, and which an inner scroller chains into as
+     soon as it hits its own end.
+
+     overscroll-behavior: none on the viewport kills both halves at once: the
+     document itself gets no bounce, and overscroll chained up from the
+     message flow / session list is absorbed without moving anything.
+     overflow: hidden then hard-locks the document scroller so future content
+     can never reintroduce a real scroll. Set on html AND body: the spec
+     propagates the viewport's value from html, but engines have historically
+     read body, and neither is a scroll container we ever want.
+
+     Deliberately NOT position: fixed on body — the app shell does not need
+     it, and it is the variant that strands iOS's fixed elements behind the
+     on-screen keyboard. With plain overflow: hidden, iOS still pans the
+     visual viewport to reveal a focused textarea, so the composer stays
+     visible while typing without any visualViewport JS. */
+  html,
+  body {
+    overflow: hidden !important;
+    overscroll-behavior: none !important;
+  }
+
+  /* The message flow is the one scroller that regularly hits its end under a
+     finger. Root-level \`none\` already absorbs the chain, but declaring it
+     at the source keeps the guarantee if the root rule is ever weakened
+     (the home list and both sheets already declare it).
+
+     \`none\`, NOT \`contain\` (S4.1 fix, 2026-08-17). The two differ in exactly
+     the way that bit us: \`contain\` stops overscroll from CHAINING OUT to the
+     document but deliberately KEEPS this element's own local elastic bounce,
+     while \`none\` suppresses that local bounce too. S1.1 only reasoned about
+     the chain, so it picked \`contain\` — and the composer went on twitching
+     upward on every drag-past-the-end while the header and FAB stayed put.
+
+     Why only the composer moved: the official composer seat
+     (\`[class$="_composerSeat"]\`) is \`position: sticky; bottom: 0\` and lives
+     INSIDE this scroller (measured 2026-08-17: seat 0,710 390x134 inside
+     _scrollBody 0,131 390x713, contains() === true). A sticky box is laid out
+     against its scroll container's content, so the container's own rubber-band
+     drags it along. The header/FAB are absolute on the frame, outside this
+     scroller entirely — which is precisely why S1.1's document-level fix
+     pinned them and left this one surface behind.
+
+     Deliberately NOT re-pinning the seat with position: fixed: sticky inside
+     the scroller is what keeps the focused textarea visible when iOS pans the
+     visual viewport for the keyboard, and fixed is the variant that strands
+     it behind the keyboard (same trap as the body rule above). Kill the
+     bounce, keep the sticky. */
+  [data-phase] [class$="_scrollBody"] {
+    overscroll-behavior: none !important;
+  }
+
+  /* The official sidebar is no longer a drawer on a phone — the home screen
+     replaced it. Hidden outright (not translated off-screen) so it cannot
+     capture taps or hold layout. */
+  [data-mobile-nav="frame"] > :first-child {
+    display: none !important;
+  }
+  /* The header's drawer toggle opened that sidebar; with it gone the button
+     has nothing to open. (S2 owns the rest of the header layout —
+     styles/header.css.ts — including the Files button's replacement.) */
+  [data-mobile-nav="toggle"] {
+    display: none !important;
+  }
+
+  /* --- level 1: the session list ---
+     Renders inside the shell overlay layer (absolute, pointer-events: none),
+     so the page re-enables pointer events for itself. The layer's containing
+     block is the frame's padding box, which still starts under the status
+     bar — hence the safe-area padding here. */
+  [data-mobile-nav="home"] {
+    position: absolute;
+    inset: 0;
+    z-index: 5;
+    display: flex;
+    flex-direction: column;
+    pointer-events: auto;
+    /* dsw-specific-sidebar-fill, not an alias bg-layer-* token (real-device
+       round 2 follow-up, 2026-08-17): fetched and diffed the live theme
+       CSS (both light/dark blocks in /assets/index-*.css) because computed
+       values, not source-read guesses, are what actually matter here —
+       --dsw-alias-bg-base/-layer-1/-layer-2 all resolve to the exact same
+       color in the LIGHT theme (neutral-bluish-00, i.e. plain white); they
+       only diverge in dark mode. A layer-* token would have made the page
+       and its cards indistinguishable in light mode specifically — the
+       opposite of what was asked. --dsw-specific-sidebar-fill differs from
+       bg-base in BOTH themes (bluish-50 vs -00 light, bluish-900 vs -950
+       dark) and is the exact token dsh-better-sidebar's own panel already
+       uses for this same "secondary surface next to bg-base content"
+       role, so it is the correct reuse rather than a new hardcoded gray. */
+    background: var(--dsw-specific-sidebar-fill, #f5f5f5);
+    color: var(--dsw-alias-label-primary, inherit);
+    padding-top: var(--mnav-sat);
+    transform: translateX(0);
+    opacity: 1;
+    transition:
+      transform .3s var(--ds-ease-in-out, ease-in-out),
+      opacity .3s var(--ds-ease-in-out, ease-in-out);
+  }
+  /* Push transition: the list slides out to the left as the session takes
+     the screen, and comes back from the left. It stays mounted (visibility,
+     not display) so the slide has something to animate; the delayed
+     visibility keeps it non-interactive the moment the transition ends. */
+  [data-mobile-nav="home"][data-view="session"] {
+    transform: translateX(-100%);
+    opacity: 0;
+    visibility: hidden;
+    pointer-events: none;
+    transition:
+      transform .3s var(--ds-ease-in-out, ease-in-out),
+      opacity .3s var(--ds-ease-in-out, ease-in-out),
+      visibility 0s .3s;
+  }
+  @media (prefers-reduced-motion: reduce) {
+    [data-mobile-nav="home"],
+    [data-mobile-nav="home"][data-view="session"] {
+      transition: none !important;
+    }
+  }
+
+  /* Title bar: the workspace name IS the switcher. */
+  [data-mobile-nav="home-top"] {
+    flex: 0 0 auto;
+    display: flex;
+    align-items: center;
+    min-height: 52px;
+    padding: 4px 16px 6px;
+  }
+  /* Site logo (real-device round 2, 2026-08-17): rendered only when
+     document.head actually has a <link rel="icon"> (MobileHome.tsx never
+     ships a placeholder box), so this rule only ever needs to size the
+     image, not reserve space for its absence. */
+  [data-mobile-nav="home-logo"] {
+    width: 24px;
+    height: 24px;
+    margin-right: 6px;
+    flex: none;
+    border-radius: 6px;
+    object-fit: contain;
+  }
+  /* Dark theme (real-device report, 2026-08-17): the runtime favicon is a
+     dark-on-transparent whale mark, illegible on the dark page. Force a
+     white silhouette regardless of the source image's own colors —
+     brightness(0) collapses every opaque pixel to black first, invert(1)
+     then flips that to white; transparent pixels stay transparent either
+     way. Same body[data-ds-dark-theme] marker as the home-row hairline
+     above (AGENTS.md: prefers-color-scheme never fires, the app switches
+     themes via this attribute with color-scheme hardcoded to light). */
+  body[data-ds-dark-theme] [data-mobile-nav="home-logo"] {
+    filter: brightness(0) invert(1);
+  }
+  [data-mobile-nav="ws-switch"] {
+    display: inline-flex;
+    align-items: center;
+    gap: 4px;
+    min-height: 44px;
+    max-width: 100%;
+    padding: 0 6px 0 0;
+    border: none;
+    background: transparent;
+    color: inherit;
+    font-family: inherit;
+    font-size: 22px;
+    font-weight: 600;
+    line-height: 1.2;
+    cursor: pointer;
+    touch-action: manipulation;
+    -webkit-tap-highlight-color: transparent;
+  }
+  [data-mobile-nav="ws-switch"] > span {
+    overflow: hidden;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+  }
+  [data-mobile-nav="ws-switch"] > svg {
+    flex: none;
+    opacity: .55;
+  }
+  [data-mobile-nav="ws-switch"]:active {
+    opacity: .6;
+  }
+
+  /* Session list: rounded cards, not bordered rows (real-device round 2
+     follow-up, 2026-08-17 — reference: Claude Code mobile app's session
+     list). \`gap\` on the flex column IS the inter-card spacing; no
+     per-row margin bookkeeping. */
+  [data-mobile-nav="home-list"] {
+    flex: 1 1 auto;
+    min-height: 0;
+    margin: 0;
+    display: flex;
+    flex-direction: column;
+    gap: 10px;
+    padding: 12px 16px calc(var(--mnav-sab) + 96px);
+    list-style: none;
+    overflow-y: auto;
+    overscroll-behavior: contain;
+    -webkit-overflow-scrolling: touch;
+  }
+  [data-mobile-nav="home-row"] {
+    display: flex;
+    align-items: center;
+    gap: 12px;
+    width: 100%;
+    min-height: 60px;
+    padding: 14px 16px;
+    border: none;
+    border-radius: 22px;
+    background: var(--dsw-alias-bg-base, #ffffff);
+    color: inherit;
+    font-family: inherit;
+    text-align: left;
+    cursor: pointer;
+    touch-action: manipulation;
+    -webkit-tap-highlight-color: transparent;
+    /* Card edge definition (2026-08-17). Light theme only — see the dark
+       override below. Two stacked shadows in the iOS idiom: a tight 1px
+       contact shadow that draws the edge itself, plus a wide soft one that
+       lifts the card off the page. Both are deliberately weak (.06/.05):
+       the page sits on --dsw-specific-sidebar-fill and the card on
+       --dsw-alias-bg-base, so there is already a slight tonal step here and
+       the shadow only has to sharpen it, not carry it alone. */
+    box-shadow: 0 1px 3px rgba(0, 0, 0, .06), 0 4px 12px rgba(0, 0, 0, .05);
+  }
+  [data-mobile-nav="home-row"]:active {
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+    /* Press = settle toward the page. Dropping the wide shadow and keeping a
+       tighter contact one reads as the card pushing in, which is what the
+       darkening background already implies; leaving the lifted shadow under
+       a pressed card is the combination that looks wrong. */
+    box-shadow: 0 1px 2px rgba(0, 0, 0, .05);
+  }
+  /* Dark theme: a black shadow on a near-black page is invisible, so the
+     edge is drawn instead of cast. A 1px hairline at --dsw-alias-border-l2
+     weight, delivered as an INSET box-shadow rather than a real border so
+     the card's geometry is untouched (a real 1px border would grow every
+     row by 2px unless box-sizing cooperated) and so it overrides the light
+     shadow through the same property instead of fighting it.
+
+     Chosen over "brighten the card face" because in dark theme the card
+     (--dsw-alias-bg-base, bluish-950) is already DARKER than the page
+     (--dsw-specific-sidebar-fill, bluish-900); lightening the card past the
+     page would invert the layering that the light theme establishes, while
+     a hairline keeps both themes reading as "page behind, card in front".
+
+     Theme is read from body[data-ds-dark-theme], never prefers-color-scheme:
+     the app hardcodes color-scheme: light on <html> and switches themes with
+     this attribute, so a media query would never fire (AGENTS.md). This
+     selector also outranks the :active rule above (0,2,1 vs 0,2,0), so one
+     declaration covers the pressed state too. */
+  body[data-ds-dark-theme] [data-mobile-nav="home-row"] {
+    box-shadow: inset 0 0 0 1px var(--dsw-alias-border-l2, rgba(255, 255, 255, .12));
+  }
+  [data-mobile-nav="home-row"][data-current] [data-mobile-nav="home-row-title"] {
+    font-weight: 600;
+  }
+  /* Avatar: a running/warning/done session shows its existing StateDot
+     (same component, same semantics as the old inline dot — just bigger
+     and re-homed); otherwise the title's own first character stands in
+     for it, so every row has a mark even when idle. interactive-bg-hover,
+     not a bg-layer-* token: same reason as the page background above —
+     bg-layer-2 is IDENTICAL to the card's own bg-base in light theme
+     (verified against the live theme CSS), so it would render invisible
+     there. interactive-bg-hover is a translucent rgba tint rather than a
+     solid layer color, so it always reads as "a shade over the card" in
+     both themes regardless of what the card's base color resolves to. */
+  [data-mobile-nav="home-row-avatar"] {
+    flex: none;
+    display: grid;
+    place-items: center;
+    width: 40px;
+    height: 40px;
+    border-radius: 12px;
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .55));
+    font-size: 16px;
+    font-weight: 600;
+  }
+  [data-mobile-nav="home-row-body"] {
+    flex: 1 1 auto;
+    min-width: 0;
+    display: flex;
+    flex-direction: column;
+    gap: 2px;
+  }
+  [data-mobile-nav="home-row-title"] {
+    font-size: 16px;
+    line-height: 21px;
+    overflow: hidden;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+  }
+  [data-mobile-nav="home-row-status"] {
+    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));
+    font-size: 12.5px;
+    line-height: 17px;
+    overflow: hidden;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+  }
+  [data-mobile-nav="home-row-time"] {
+    flex: none;
+    align-self: flex-start;
+    color: var(--dsw-alias-label-tertiary, rgba(0, 0, 0, .4));
+    font-size: 12.5px;
+    line-height: 18px;
+  }
+  [data-mobile-nav="home-empty"] {
+    margin: 12px 16px;
+    padding: 48px 24px;
+    border-radius: 22px;
+    background: var(--dsw-alias-bg-base, #ffffff);
+    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));
+    font-size: 15px;
+    text-align: center;
+  }
+
+  /* New-session FAB: a labeled pill (real-device round 2 follow-up), not a
+     bare circle — tap starts in the shown workspace, long press picks
+     one. Inverted-surface tokens (not a hardcoded accent color): the same
+     pair the official git-commit button in dsh-better-sidebar uses for
+     its own solid CTA. */
+  [data-mobile-nav="home-fab"] {
+    position: absolute;
+    right: 18px;
+    bottom: calc(var(--mnav-sab) + 22px);
+    z-index: 6;
+    display: inline-flex;
+    align-items: center;
+    gap: 6px;
+    height: 48px;
+    padding: 0 20px 0 16px;
+    border: none;
+    border-radius: 999px;
+    background: var(--dsw-alias-button-primary-fill, #1a1a1a);
+    color: var(--dsw-alias-label-primary-inverted, #ffffff);
+    font-family: inherit;
+    font-size: 15px;
+    font-weight: 600;
+    cursor: pointer;
+    box-shadow: 0 6px 20px rgba(0, 0, 0, .24);
+    touch-action: manipulation;
+    user-select: none;
+    -webkit-user-select: none;
+    -webkit-touch-callout: none;
+    -webkit-tap-highlight-color: transparent;
+  }
+  [data-mobile-nav="home-fab"]:active {
+    transform: scale(.96);
+  }
+
+  /* Workspace sheet (switcher and long-press New Session share it). */
+  [data-mobile-nav="home-sheet-layer"] {
+    position: absolute;
+    inset: 0;
+    z-index: 7;
+  }
+  [data-mobile-nav="home-sheet-mask"] {
+    position: absolute;
+    inset: 0;
+    background: var(--dsw-alias-bg-mask-3, rgba(0, 0, 0, .45));
+    border: none;
+    animation: dsh-mobile-nav-fade .18s var(--ds-ease-out, ease-in-out);
+  }
+  /* Docked to the screen edge, matching the composer's permission/model
+     sheets (styles/composer.css.ts section 4) rather than floating.
+
+     It used to sit at \`bottom: calc(var(--mnav-sab) + 8px)\` with all four
+     corners rounded, which left a 42px strip of bare mask under it at
+     sab: 34 (measured). Docking removes the strip instead of dimming it, and
+     the safe area moves INSIDE the card as bottom padding — so the white
+     card body runs all the way to the physical screen edge and the last row
+     still clears the home indicator. Same reason the corners go top-only:
+     a rounded bottom corner on a card flush with the screen edge reads as a
+     rendering mistake. */
+  [data-mobile-nav="home-sheet"] {
+    position: absolute;
+    left: 0;
+    right: 0;
+    bottom: 0;
+    max-height: 70%;
+    overflow-y: auto;
+    overscroll-behavior: contain;
+    box-sizing: border-box;
+    padding: 6px 6px calc(var(--mnav-sab) + 14px);
+    border-radius: 20px 20px 0 0;
+    /* layer-2, not bg-base: in dark mode the sheet must lift off a page that
+       shares bg-base, or only the shadow separates them. */
+    background: var(--dsw-alias-bg-layer-2, #ffffff);
+    box-shadow: 0 -8px 32px rgba(0, 0, 0, .28);
+    animation: dsh-mobile-nav-sheet-up .22s var(--ds-ease-out, ease-in-out);
+  }
+  @media (prefers-reduced-motion: reduce) {
+    [data-mobile-nav="home-sheet-mask"],
+    [data-mobile-nav="home-sheet"] {
+      animation: none !important;
+    }
+  }
+  [data-mobile-nav="home-sheet-title"] {
+    padding: 10px 12px 6px;
+    color: var(--dsw-alias-label-secondary, rgba(0, 0, 0, .5));
+    font-size: 13px;
+  }
+  [data-mobile-nav="home-sheet-item"] {
+    display: flex;
+    align-items: center;
+    width: 100%;
+    min-height: 48px;
+    padding: 0 12px;
+    border: none;
+    border-radius: 12px;
+    background: transparent;
+    color: inherit;
+    font-family: inherit;
+    font-size: 16px;
+    text-align: left;
+    cursor: pointer;
+    touch-action: manipulation;
+    -webkit-tap-highlight-color: transparent;
+  }
+  [data-mobile-nav="home-sheet-item"][data-selected] {
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+    font-weight: 600;
+  }
+  [data-mobile-nav="home-sheet-item"]:active {
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+  }
+
+  /* --- hero fallback back button ---
+     The hero (new blank session) page renders no conversation.session.header,
+     so the header-slot back button (S2) does not exist there. This floating
+     fallback covers that page and hides itself as soon as the real header
+     back mounts. */
+  [data-mobile-nav="hero-back"] {
+    position: absolute;
+    top: calc(var(--mnav-sat) + 8px);
+    left: 8px;
+    z-index: 6;
+    width: 44px;
+    height: 44px;
+    display: grid;
+    place-items: center;
+    border: none;
+    border-radius: 14px;
+    background: transparent;
+    color: var(--dsw-alias-label-secondary, inherit);
+    pointer-events: auto;
+  }
+  [data-mobile-nav="hero-back"]:active {
+    background: var(--dsw-alias-interactive-bg-hover, rgba(0, 0, 0, .06));
+  }
+  [data-mobile-nav="frame"]:has([data-mobile-nav="header-back"]) ~ [data-mobile-nav="hero-back"],
+  body:has([data-mobile-nav="header-back"]) [data-mobile-nav="hero-back"] {
+    display: none;
+  }
+}
+`

package/src/client/styles/index.ts

@@ -0,0 +1,25 @@
+import { BASE_CSS } from './base.css.ts'
+import { LAYOUT_CSS } from './layout.css.ts'
+import { COMPAT_CSS } from './compat.css.ts'
+import { MISC_CSS } from './misc.css.ts'
+import { HOME_CSS } from './home.css.ts'
+import { HEADER_CSS } from './header.css.ts'
+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'
+
+/**
+ * All mobile styles, concatenated in the exact order of the original
+ * single-file stylesheet (base → layout → compat → misc, where misc keeps
+ * composer → tablet → desktop), followed by the phone app shell (home), the
+ * session-header reflow (header), the composer reflow (composer), and the
+ * session-info sheet (info, which must come last of all: it re-shows a
+ * header.utilities child header.css.ts hides by default, so its rule has to
+ * win that tie too), the turn-process fold (turn-fold, S8, which shares no
+ * selector with any of them), and finally the chips row / settings entry /
+ * portal fix (chips, S5) — all appended in this order so their <768px rules
+ * win ties against the shared <=1023px block. 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')