Face-to-face join/waiting/leave polish: silent disabled Join, frozen countdown, waiting card twice, Leave next to Auto-send and unconfirmed in waiting, held lines shown twice #306

Summary

Usability and simplicity issues in the Face-to-face join → waiting → leave flow, found in the focus-B self-test. Each item is small; together they make the flow feel heavier and less consistent than the design (one top +, in-chat approval, aesthetics/usability/simplicity/consistency).

Environment

FlyBot main a003044, dsh 0.2.0-rc.2, Node 24. Fresh A :3090 (SelfA1622) / B :3091 (SelfB1622), Bot Social prod (1870786). Self-test 2026-10-18 16:26–16:33 Asia/Shanghai.

Repro

• → Face-to-face group → pick Chief → type a number → Join → wait → (second home joins) → Enter chat → chat with approvals → Leave. Also: join a number, then Leave from the waiting dialog.

Actual

1. Join gives no hint. With an empty or short number, Join is disabled (plugins/social/client.js L707: length !== 6), so the Enter a 6-digit number. message (L578–579) can never show. Nothing says why Join is grey.
2. Countdown looks frozen. It reads 10 minutes left to join and changes once a minute (minute granularity, countdown() L1075–1084). Watched for a while, it looked static.
3. Dialog chrome.
   • The dialog overlay does not cover the right details panel.
   • The waiting card is shown twice: in the dialog and in the details panel. Screenshot: dialog with the waiting tiles, and the same card in the right panel.
   • The same Chief has a different avatar in the dialog (whale) and the panel (purple blob). See Face-to-face: avatars and room title differ per home (regressions of #137/#172); Leave is abrupt and not seen by the peer #182 for the cross-home avatar item.
4. Leave placement.
   • In an open room, Leave sits in the details panel right next to the Auto-send checkbox, so an accidental tap is easy and the path is long.
   • Leave in the waiting dialog (L681) has no confirm, unlike full-room Leave (ConfirmLeave, Face-to-face: avatars and room title differ per home (regressions of #137/#172); Leave is abrupt and not seen by the peer #182).
   • It stays on the left room instead of opening the main Bot like full-room Leave does.
5. Pending Bot lines show twice. Each held Bot line is a full bubble and also a truncated preview inside the approval card below it (Approvals UI: overlay covers the chat bar, every card twice with different words and buttons #260 / Approvals: stale 'waiting for the owner' line in Face-to-face rooms; one place per approval; pointer vs open chat #278 aimed for one place per approval).
6. "2 members" in details is ambiguous (2 Bots? 2 people?). Same counting issue as the @ picker in Face room @ picker lists a friend's Bot 5 times in 3 sections, 'Everyone · 1 members'; mention chip renders differently per home; Bot named 4 ways #305.

Not filed, checked as by design: re-joining a number whose room already started creates a new room (start deletes the number mapping, Bot Social FACE_ROOMS.md). The top + popover with six items matches #265 / #173.

Expected

• Join is enabled once a Bot is picked. A wrong number shows the inline Enter a 6-digit number. (or the hint sits under the field while it is incomplete).
• The countdown ticks visibly: 9:41 left to join, or seconds in the last minutes.
• One waiting card, in the dialog, with the overlay covering the whole window. The same avatar for a Bot everywhere.
• Leave sits in the room header or menu, away from toggles. Every Leave asks once (Leave / Stay) and lands on the main Bot.
• A held line shows once: the bubble with Approve / Reject under it, with no second preview.
• Counts name what they count: 2 people · 2 Bots.