Members should see a room's call rules before hitting the server-side guard, not as an error after.
Scope
In RoomViewHeader next to the existing call/member controls: a single small chip, only when a rule exists — "8/10" (participants / io.lotus.voice_limit) and/or a mic-only glyph when useRoomCallPolicy says audio-only. No label text; tooltip carries the words ("Audio-only room", "Voice limit 10").
Match existing folds chip sizing/colours (Chip size 400 / Surface); mobile: hides when the header is tight (same rule as other secondary header items).
Members should see a room's call rules before hitting the server-side guard, not as an error after.
### Scope
- In `RoomViewHeader` next to the existing call/member controls: a single small chip, only when a rule exists — **"8/10"** (participants / `io.lotus.voice_limit`) and/or a mic-only glyph when `useRoomCallPolicy` says audio-only. No label text; tooltip carries the words ("Audio-only room", "Voice limit 10").
- Match existing folds chip sizing/colours (`Chip` size 400 / Surface); mobile: hides when the header is tight (same rule as other secondary header items).
Done in 7f17940d: one Surface chip next to the header controls, only when a rule exists — 0/10 (participants / io.lotus.voice_limit) and/or a muted-camera glyph when io.lotus.room_quality forbids both camera and screenshare; tooltip + aria-label carry the words ("Voice limit 10 (0 in call) · Audio-only room"). Desktop only (mobile header is tight). Verified headless: shows with the rules set, gone when cleared.
Done in `7f17940d`: one Surface chip next to the header controls, only when a rule exists — `0/10` (participants / `io.lotus.voice_limit`) and/or a muted-camera glyph when `io.lotus.room_quality` forbids both camera and screenshare; tooltip + aria-label carry the words ("Voice limit 10 (0 in call) · Audio-only room"). Desktop only (mobile header is tight). Verified headless: shows with the rules set, gone when cleared.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Members should see a room's call rules before hitting the server-side guard, not as an error after.
Scope
RoomViewHeadernext to the existing call/member controls: a single small chip, only when a rule exists — "8/10" (participants /io.lotus.voice_limit) and/or a mic-only glyph whenuseRoomCallPolicysays audio-only. No label text; tooltip carries the words ("Audio-only room", "Voice limit 10").Chipsize 400 / Surface); mobile: hides when the header is tight (same rule as other secondary header items).Done in
7f17940d: one Surface chip next to the header controls, only when a rule exists —0/10(participants /io.lotus.voice_limit) and/or a muted-camera glyph whenio.lotus.room_qualityforbids both camera and screenshare; tooltip + aria-label carry the words ("Voice limit 10 (0 in call) · Audio-only room"). Desktop only (mobile header is tight). Verified headless: shows with the rules set, gone when cleared.