chat-duo-web tablet-grade evolution (path A for unified browser client)

Sub-tickets

Activity

• system created · 2026-05-26
  wi cli
• system spec · 2026-05-26
  Elazar-approved 2026-05-26-03:29. CONTEXT: Elazar at lezama 2026-05-27, needs one chat client usable from tablet + lezama + whey. GTK4 chat-duo too painful to re-bring-up on lezama (2h last time + llmmsg-srv breaking changes since). Browser client (chat-duo-web on whey:9704) is the right call. Plan: ship A tonight, then start B (NextJS greenfield, WI #463) right after. SCOPE = A only. Target: chat-duo-web at whey:9704. ACCEPTANCE (tablet-grade): 1. Mobile viewport 375px-1024px: no horizontal scroll, no clipped chrome. 2. Touch targets >=44px. 3. Reply compose form usable with on-screen keyboard (no overlap). 4. ARO compose: kind dropdown (dm/ask/working/announce/opinion/brainstorm/dispatch). 5. Roster sidebar collapsible on narrow viewport. 6. SSE auto-reconnect on tablet sleep/wake (visibilitychange handler). 7. Elazar Pending pane reads GET /eq_ls (already wired per CLAUDE.md). 8. Version bump per memory project_chatduo_hub_push_convention; gitpush specific paths only (not -A). SKIP: GTK4 parity, settings UI overhaul, plot graphs, anything multi-day. REPORT: ack in aro:chatduo-engineering with ETA, then `working:` updates as you go. Final = sha + verified-on-tablet URL. Then pick up B (WI to be filed after A closes).
• wi-cli-venus completed · 5w ago
  Delivered on 6 of 8 acceptance criteria, verified in shipped code by coder-chatduo-cc 2026-09-11: #1 viewport meta index.html:5, #4 kind dropdown :592, #5 off-canvas drawer at the 768px breakpoint :451/:521, #6 wake-to-fresh-SSE :3110, #7 eq_ls :2281 + count_only :2313, #8 version-bump convention followed (cdw now 0.7.69). #2 and #3 did NOT land and are spun out as MSG-388 rather than closed silently - #3 (on-screen-keyboard overlap) has no implementation at all. Also note the spec line 'Target: chat-duo-web at whey:9704' was stale for most of this item's life: cdw runs on venus.