[mahanti]

Message hover actions now use a compact capsule with reaction, reply, copy-link and more icons, with a persistent bubble highlight while its actions are open. Long messages have more reading room, author avatars are smaller, and membership activity takes less space.

• Keep the toolbar above the bubble; put Copy message in More and remove emoji shortcuts. Place reactions to sent messages on the left.
• Let bubbles expand until 32px before the opposite avatar. Reduce message-author avatars by 8px across timeline, thread and nested contexts, using the shared Avatar sizes. Add 4px horizontal composer-content padding per side. No message-width preference is introduced.
• Center membership notices and show only explicit additions and removals. Collapse consecutive notices across elapsed time/date boundaries until a message or huddle; summarize large groups with one name and a count that opens the full scrollable people list.
• Remove unused quick-reaction ranking/recording and obsolete join/leave formatting. Preserve legacy community-storage cleanup and document the resulting behavior.

Validation:

• Independent code review: no outstanding blockers after cleanup and the personal-chat assertion correction.
• 56 browser tests passed across Chromium and WebKit: floating actions, message actions, membership and reactions. Covers pointer/keyboard behavior, narrow/wide layout, enlarged text, both themes and picker recovery.
• 23 personal-chat viewport tests passed after updating the previous self-join/leave expectation to the new explicit-add/remove contract.
• Required push hooks passed at ec4ec71: TypeScript/full Vitest suite, design-system checks, Rust gate and push safety checks. Remote head verified; working tree clean. Browser evidence is from fb0a0f1 with identical production code.
• Reviewed synthetic screenshots are attached in one PR comment; captures predate the subsequent line-height and avatar-gap adjustment.

Coverage changes: removed quick-reaction ranking tests with the removed feature; community/device cleanup tests still verify deletion of legacy storage. Membership helper, timeline and browser tests cover filtering/grouping and accessible people previews. Existing browser journeys were updated; no new browser test cases or production test seams were added.

Human acceptance confirmed for the combined UI and the later author/status clipping fix. Agent browser checks exercise the affected product behavior; native desktop identity/community loading was not independently reverified. Those approvals apply through 6d52f8c. The subsequent spacing adjustment is draft pending validation and acceptance.

CI follow-up at 6d52f8c: preserve author-name width beside long statuses; update avatar and reaction journeys for explicit additions and the icon-only toolbar; keep video readability coverage against the new available width. The approved native media-test fixture now gates premature EOF on downstream response headers, eliminating the opening-vs-midstream ordering race without changing media behavior. Independent review found no blockers. All 40 affected browser checks (both engines), 10 native media-stream tests, and required local push gates passed. Hosted CI passed on this exact head: 47 checks successful, including CI required and DCO; Windows native validation was skipped by workflow policy.

Spacing follow-up at fab8d86: message leading is 22px at the default 14px type size and scales with text preferences; the visible avatar-to-bubble gap is 4px on both sides. Opposite-avatar clearance remains 32px. Shared token metadata and guidance are synchronized. Required local push gates passed at f0cca66 (full unit suite, TypeScript, design-system checks, and Rust Clippy). Both engines passed the 20-case floating-toolbar suite; nested-reply and opposite-avatar geometry checks passed. The 22px leading exposed a fractional toolbar-edge hit-test gap, fixed by extending the active hover corridor through the fractional edge pixel. Hosted CI and renewed acceptance remain pending; the PR remains draft.

[mahanti]

🤖 Screenshots captured by Arjun's AI agent from the actual updated browser app and maintained fixtures, using synthetic data only.

Checked production commit: fb0a0f1. Final head ec4ec71 only updates a personal-chat test.

1. Message toolbar, light: compact reaction/reply/copy-link/more capsule and active bubble highlight.
2. Message width and spacing: long sent/received bubbles, smaller avatars and composer inset.
3. Membership people: centered grouped additions with one name, count and scrollable people popover. Names/hash prefixes are disposable fixture identities.
4. Message toolbar, dark: same interaction in WebKit.
5. Reaction picker: actual shared picker in the maintained message gallery fixture; synthetic custom emoji.

Native desktop identity/community loading and final human acceptance are not verified by these captures.

6. Author/status in a narrow chat: synthetic Chat fixture at 6d52f8c. The author stays readable while the long status truncates. Human acceptance confirmed after this fix.

7. Latest membership action: at 7d01678, Pinky was added and then removed, so the run now reads “Brain was added · Pinky was removed.” Synthetic fixture capture from the passing Chromium journey; the same scenario passed in WebKit.

[loganj]

🤖 Larry and Auto: an independent adversarial review of 6d52f8c. Source review only; we ran nothing locally (hosted CI is green on this head).

Approving: the direction is right, and hiding self-joins/leaves fixes the noisy #4things case. Two items should be fixed before merge (marked must-fix inline and below). Everything else is optional.

Must-fix

1. error: a mixed run that removes and then re-adds someone reads "Pinky was added · Pinky was removed", so the notice states the reverse of the final state (inline on membership-rows.ts:118).
2. convention: docs/channels.md:1293-1302 ("Membership activity") still says arrivals and departures group together, that messages, local-day changes and gaps over an hour break groups, and that removals by different actors stay separate. This PR reverses all three, and only docs/buzz-help.md was updated. AGENTS.md asks us to keep documented product decisions in step, so update channels.md to match.

Optional, outside the diff

• error: the message gallery's membership examples (tests/fixtures/message-gallery/examples.ts:861-930, "Member joined", "Member left", "Grouped joins", "Grouped joins with overflow") are all self-joins or leaves, so they now render as empty membership rows. Change them to adds and removes by another member, or drop them.
• advice: MessageReactions.tsx Props.inline is now dead (the removed ReactionLabel was its only reader). Drop it from the type and the MessageRow caller.
• preference: the PR description's "Spacing follow-up at fab8d86 … in progress" paragraph refers to a commit that is not on the branch. Push it or trim the paragraph.
• advice: the media_stream_tests.rs fixture fix is sound: it holds the origin open until the response headers arrive, so the test exercises a mid-stream truncation instead of racing EOF into a 502. Splitting it out is fine but not required.

What we checked and found sound: self-joins and leaves are filtered before grouping, so they no longer split runs or agent-activity folds. Messages and huddles still split groups. Solo withoutStartingAgents runs first, unchanged. Unread and read-receipt paths already ignore membership rows, and linked-message targets skip them. The community-storage test edits correctly seed the legacy key that forgetQuickReactions still clears. The new tiny avatar size is in the registry, DESIGN.md and the specimens.

[wesbillman]

🤖 Carl, an automated reviewer, commenting via Wes's GitHub account.

Court review of 7d0167829 (UI, membership logic, and challenge lanes, integrated by me). Source review only; nothing was rendered locally.

Verdict: the membership latest-action fix holds (summary, counts and hover detail agree; 602-person list probe and huddle/day boundaries checked), the legacy quick-reaction cleanup is intact, and the media fixture change keeps its truncation assertions. Two should-fix items before merge, plus a few low ones, all inline.

Should fix

1. useFloatingActionBar.ts:255: the new hide() attribute removal creates a per-frame mutation loop while a revealed row is scrolled offscreen.
2. MessageRow.tsx:543: thread and nested avatars miss the stated 4px gap and bottom alignment.

Merge criteria

• Both items above resolved, or explicitly declined by the author.
• Hosted CI green on the final head. At this head Browser journeys (chromium, 8/9) failed message-overlays.spec.mjs:706 (grouped reaction preview never opened). That test is untouched here and passed at 6d52f8c, so it needs triage as product regression vs flake, not just a rerun.
• Thread-layout avatar geometry is covered (the current geometry case measures only timeline avatars).

[wesbillman]

🤖 Carl, an automated reviewer, commenting via Wes’s GitHub account.

Two recommended blockers at 7d0167829. I'm posting this as a comment, following the repo's agent-review rule; the author and humans decide what must be fixed. Each finding is explained in its inline thread.

Recommended blockers

1. With enlarged text at narrow widths, bubbles split words mid-word (Messages.module.css:172).
2. A saved reading position that points at a now-hidden self-join or self-leave doesn't restore, and read catch-up stays suppressed until the reader interacts (membership-rows.ts:44).

Validation gaps

• Hosted CI was still pending at this head when the review ran.
• Nothing covers a text bubble at the 480px minimum width with enlarged text, or a saved position that points at a hidden membership event.
• Nobody ran the media_stream_tests.rs ordering fix for this review, so the flake fix is confirmed only by source reading. The fixture change itself looks correct and doesn't hide a production bug.

To clear the blockers: restore the bubble readability floor, and either remap or retire saved positions that point at hidden events. Add one regression check for each. The remaining threads are optional.

Checked with no issues: legacy quick-reaction storage cleanup is still wired from community leave. No callers of the removed APIs remain. History prepends keep newest-anchored membership keys stable. The fractional-edge hover path is sound. Typography tokens agree across the registry, DESIGN.md and the CSS.