- Cut placement, surrounding context, design measurements and decision history
from comments this branch added, across code, styles, tests and stories.
- Correct one that claimed most Firefox builds can't route audio.
- Drop a comment left duplicated in the footer story.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Two participants, for what only a real call can show: a device switch that
neither drops the media session nor rejoins, and a meter that keeps moving
while muted while the peer is still shown the mute rather than left to infer
it from silence.
- The component harness covers what only a host page shows: every device
reachable in a small container, the list sized against the call rather than
the window, and the menu following the call area when the host resizes it.
- Synthetic devices are patched onto the media element and the audio context
alike, so a browser with no hardware still enumerates and still routes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
