Huddle ends prematurely after ~5 minutes (Boardroom channel)

**Describe the bug**
Huddle sessions in the Buzz Desktop app terminate unexpectedly after approximately 5 minutes of active use. The Boardroom huddle (channel 71745e2a-768a-4f25-9e49-7e4a8b0acaae) ended abruptly at ~19:43 UTC on 2026-08-21 with no user action to close it, no error dialog, and no warning. The relay retained message history, but the live audio/video session was cut off.

**Steps to reproduce**
1. Open Buzz Desktop (macOS)
2. Navigate to the Boardroom channel (#71745e2a-768a-4f25-9e49-7e4a8b0acaae)
3. Start a huddle (click the call/huddle button in the channel header)
4. Invite all channel members (6 participants: 1 owner + 5 bots)
5. Conduct discussion for ~5 minutes
6. Observe: huddle ends automatically — participants are disconnected, no "huddle ended" banner, no reconnect prompt

**Expected behavior**
Huddle should remain active until explicitly ended by a participant (e.g., clicking "Leave" or "End for all"), or at minimum persist for the duration of an active conversation (30+ minutes). No automatic timeout at 5 minutes.

**Version and platform**
Find your version at the bottom of the Settings sidebar. Write "unknown" if you can't determine it.
- Buzz version: Latest as of today, unknown (check bottom of Settings sidebar in Buzz Desktop)
- OS: macOS (version unknown — e.g., macOS 14.x / 15.x)

- OS:

**Logs / additional context**
Channel: Boardroom (71745e2a-768a-4f25-9e49-7e4a8b0acaae)
Participants: 6 (1 human owner + 5 agent bots)
Huddle duration: ~5 minutes (started ~19:38 UTC, ended ~19:43 UTC)
Relay: wss://4chops.communities.buzz.xyz
Post-huddle state: Message history preserved in channel; no canvas or persistent memory was auto-saved from the huddle (see RESEARCH/HUDDLE_MEMORY_STATUS_2026-08-21.md)
Client behavior: No error toast, no reconnection attempt, no "huddle ended" notification in the channel feed
Possible related issue: Huddle feature may not be fully implemented in the Desktop client — CLI has no huddle command, suggesting it's a GUI-only feature with potential backend timeout defaults