[Birfy]

Fixes #362

Step 1 only, per the Owner decision (2026-10-20): a phone-width layout for the chat, the held-reply Approve / Reject buttons and the Agent inbox. No PWA, push or native app.

What. One new style block, core/src/client/mobile.js (MOBILE_CSS, all under @media (max-width:640px), installed last in the shell group), plus one phone rule in the social hold card:

• Held-reply and floating approval cards: Reject / Approve share the card width as 40px buttons, Approve filled with the accent; the held card uses the full message width. Social's hold card gets 40px Approve / Reject too.
• The floating approval stack and the chat pointers span the screen beside DSH's 56px icon rail (DSH already collapses the sidebar below 1024px), so the top + and the account stay reachable.
• Inbox cards put their buttons on a row under the text (36px) and wrap title/reason to two lines instead of truncating to "Run npm i…". The inbox dialog already went full-screen at this width.

Why. At 400px the inbox card's buttons squeezed the title to a few characters, the held-reply buttons were ~24px browser defaults, and the pointer covered the top +.

Test. core/test/mobile-layout.test.js (rules sit in one media query, button sizes, rail clearance, inbox wrap, install order and bundle) and a social test for the hold-card rule. ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify passes (core 1062, social 292, tree 80, timeline 80, scripts 88, interop 37, live-e2e 16; 0 failures, 0 skipped). Checked by eye on a local mock dsh web (npm harness 0.2.0-rc.2, mock model) in headless Chrome at 400px and 360px: chat, inbox, held card and floating approvals. Wider screens are unchanged (every rule sits in the max-width query).

Risk tier: T1 (estimate; the controller sets the label)

[Birfy]

Self-review: PASS
Tip SHA: 774ba97
Ran:

• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify: pass (core lint + arch-docs OK, plugin lint, build-client --check, ds-bot-patches check; core 1062, social 292, tree 80, timeline 80, scripts 88, interop 37, live-e2e 16; 0 fail, 0 skipped)
• node scripts/ds-bot-patches.mjs generate then check: ok; node .github/scripts/changelog.mjs check: ok
• CI at tip: tests-ok, test, plugins (social/tree/timeline), package all green; risk tier (report only) T2
• Local mock dsh web (npm harness DSH 0.2.0-rc.2, mock model) in headless Chrome at 400px and 360px: chat, Agent inbox card, held-reply card and floating approval stack checked by eye before and after
• Design rules re-read against the diff: approval stays on explicit UI buttons only (no new path), English UI, one top + menu kept reachable, scope limited to step 1 (no PWA/push/native), wider screens unchanged (all rules in one max-width query)
  Not run:
• Real phone browsers (iOS Safari / Android Chrome); a live friend's held reply through Bot Social (held card drawn from fixture markup on the bench)
• The user's Mac instances and the production Bot Social server (not touched)

[Birfy]

Self-review: PASS
Tip SHA: 44fe62c
Ran:

• Merged origin/main (674bcd7, with Search Composio's app list and show each picked app's sign-in status #479 and Add a Dockerfile, compose file and guide to run FlyBot in a container #482) into the branch (merge commit, no rebase, no force-push). Only conflict: generated patches/ds-bot/0008-client-bundle.patch; resolved per AGENTS.md conflict recipe (took main's patches/ds-bot, npm run build in core, ds-bot-patches.mjs generate then check: ok). Both behaviors kept: Search Composio's app list and show each picked app's sign-in status #479 Composio app search and Add a Dockerfile, compose file and guide to run FlyBot in a container #482 Docker files intact, MOBILE_CSS still installed and in client.js.
• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify on Node 24.21.0: pass (arch-docs OK; core 1069, social 292, tree 80, timeline 80, scripts 93, interop 37, live-e2e 16; 0 fail, 0 skipped)
• CI at tip: tests-ok, test, plugins (social/tree/timeline), package all green; risk tier (report only) T2
• Branch diff vs main (excluding generated files) unchanged from the previous review: 8 files, +112; design rules re-checked (approvals only via explicit buttons, English UI, top + reachable, step 1 scope only)
• Earlier, at 774ba97: headless Chrome on a local mock dsh web at 400px and 360px (chat, inbox card, held-reply card, floating approvals)
  Not run:
• Screenshots not repeated after the merge (the merge touched no Mobile: PWA first, then native — approvals and reminders on the phone #362 code)
• Real phone browsers (iOS Safari / Android Chrome); a live friend's held reply through Bot Social
• The user's Mac instances and the production Bot Social server (not touched)

[Birfy]

Self-review: PASS
Tip SHA: 22b6d8d
Ran:

• Merged origin/main (a7adfe0, with Label the model each turn ran on in the Timeline and each Bot row #480, Count another home's Bot answer in face rooms; a friend Bot's @all wakes none of mine #487 and Face rooms: one room lead picked by the room creator, cross-home roster with roles #488) into the branch (merge commit on top of 44fe62c, no rebase, no force-push). Conflicts: generated patches/ds-bot/0008-client-bundle.patch, resolved per AGENTS.md conflict recipe (took main's patches/ds-bot, npm run build in core, ds-bot-patches.mjs generate then check: ok); plugins/social/test/social.test.js, kept both sides' tests (Mobile: PWA first, then native — approvals and reminders on the phone #362 phone-width hold card test and the Face rooms: selectable room lead (总负责人) picked by the room creator, cross-home roster with roles, one plan per request #476 room lead tests).
• ARCH_DOCS_BASE=origin/main TZ=UTC npm run verify on Node 24.21.0: pass (arch-docs OK, plugin lint, build-client --check, ds-bot-patches check; core 1082, social 297, tree 80, timeline 83, scripts 93, interop 37, live-e2e 16; 0 fail, 0 skipped)
• node .github/scripts/changelog.mjs check: ok (changelog.d/362-mobile-layout.added.md kept; CHANGELOG.md and ds-bot/ untouched)
• CI at tip: tests-ok, test, plugins (social/tree/timeline), package all green; risk tier (report only) T2
• Branch diff vs main (excluding generated files) unchanged from the previous review: 8 files, +112; design rules re-checked (approvals only via explicit buttons, English UI, top + reachable, step 1 scope only)
• Earlier, at 774ba97: headless Chrome on a local mock dsh web at 400px and 360px (chat, inbox card, held-reply card, floating approvals)
  Not run:
• Screenshots not repeated after the merge (the merge touched no Mobile: PWA first, then native — approvals and reminders on the phone #362 code)
• Real phone browsers (iOS Safari / Android Chrome); a live friend's held reply through Bot Social
• The user's Mac instances and the production Bot Social server (not touched)