feat(ui): match Channel List screen to Figma node 15:8

[ilmoniemi]

User Story

As a Pyrycode mobile user on the home screen, I want channels and recent discussions visually organized per the Figma design, so the sectioned hierarchy and brand polish read as the canonical home — not a generic LazyColumn.

Context

Phase 1's #18 + #46 shipped a functional ChannelListScreen with LazyColumn + ConversationRow + Recent-discussions pill + FAB + empty state. The Figma node 15:8 carries the canonical visual treatment: sectioned hierarchy (channels first as name+timestamp, then "Recent discussions" section delimiter, then discussions with name+preview+workspace label+timestamp), brand-quiet polish, and proper M3 spacing/dividers.

Phase 1.5 visual-fidelity catchup.

Acceptance Criteria

• Sectioned LazyColumn matches Figma layout (channels section + "Recent discussions" delimiter + discussions section, or per-section pill — architect picks the exact treatment per node 15:8)
• ConversationRow's existing decorations (workspace label feat(ui): add workspace label decoration to ConversationRow #19, sleeping-session feat(ui): add sleeping-session indicator to ConversationRow #20) preserved
• TopAppBar (feat(ui): add Channel list TopAppBar (app name + settings gear) #21) styling matches Figma
• FAB (feat(ui): add Channel list FAB to create new discussion #22) styling matches Figma
• Empty state (feat(ui): add Channel list empty state #23) + Recent-discussions pill (feat(ui): add 'Recent discussions (N) →' pill on Channel list #26) styling matches Figma; zero hardcoded values

Technical Notes

• Existing: app/src/main/java/de/pyryco/mobile/ui/conversations/list/ChannelListScreen.kt
• This is a polish pass over existing structure, not a rewrite — architect should size for additive changes
• May spill into ConversationRow if row visuals need rework, in which case architect splits
• The data layer is already wired (feat(ui): add ChannelListViewModel + UiState (data path) #45 ChannelListViewModel) — no changes needed

Size Estimate

S — single file polish pass, ~80-120 LOC modified.

Figma

https://www.figma.com/design/g2HIq2UyPhslEoHRokQmHG?node-id=15-8

[ilmoniemi]

Split into two S-sized children — the Figma node 15:8 introduces more than a polish pass: new avatar bubbles per channel row, a Pyrycode logo in the TopAppBar, a "Channels" section header, an inline "Recent discussions" section (replacing the bottom-of-screen pill), new discussion preview cards with title + 2-line body + workspace·time meta, and a "See all discussions (N) →" affordance. That trips multiple split red lines (>3 edited files, "and"-test fails across at least six distinct concerns, new-composable-and-consumer always-split pattern, and ViewModel state extension for the inline discussions).

Children, in dependency order:

• feat(ui): Channel List — TopAppBar logo, channel avatars, Channels section header #68 — TopAppBar logo, channel-row avatars, "Channels" section header (must land first)
• feat(ui): Channel List — inline Recent discussions section + See all link #69 — inline "Recent discussions" section + "See all" link, replaces RecentDiscussionsPill (blocked-by feat(ui): Channel List — TopAppBar logo, channel avatars, Channels section header #68)

Each child is self-contained and gets its own architect pass against Figma node 15:8.

[ilmoniemi]

🤖 Product Owner — creates structured issues

po agent has completed work on this ticket.

Agent output (click to expand)

Split complete. #63 was too big for S — the Figma node introduces new avatar bubbles, a logo'd TopAppBar, sectioned layout, new discussion preview cards, and ViewModel state extension. Tripping >3-files, "and"-test, and the new-composable-and-consumer always-split pattern.

- **#68** (size:s, Backlog, sub-issue of #63) — TopAppBar logo, channel-row avatars, "Channels" section header. Must land first.
- **#69** (size:s, Backlog, sub-issue of #63, blocked-by #68) — inline "Recent discussions" section + "See all" link replacing `RecentDiscussionsPill`.
- **#63** closed, Done, with split-summary comment. Children positioned immediately after #63's old slot in dependency order so column priority is preserved.

Ready for human review. Move to the next column when approved.