Docs: Monitor live mic-level meter (#803)

docs/_authoring/FACTS.md

@@ -270,8 +270,10 @@ Auth: `/login /register /check-your-email /verify-email /password-reset /request
   mic ok/skipped/blocked, terms, details). Per-conversation rows: state pills (Recording,
   Paused, Verifying, Exploring, Typing, Finishing, Finished, Waiting, Just started, Idle),
   `Transcribing N clips` chip, `catch up ~N min` backlog estimate, red `Error` badge,
-  `Audio stopped?` (stalled) and `Screen locked` (backgrounded) warnings, weak-network and
-  low-battery hints, live transcript snippet. Real-time over SSE
+  `Audio stopped?` (stalled) and `Screen locked` (backgrounded) warnings, a live mic-level
+  meter (5-bar, from the beacon's `audio_level` 0..1 RMS, shown on `receiving` rows;
+  all-quiet hints *check the mic isn't muted*), weak-network and low-battery hints, live
+  transcript snippet. Real-time over SSE
   (`GET /v2/bff/conversations/monitor/stream`, Redis-cached snapshot ≤1 Directus read/3s).
   Project home shows a *Live & recent* section embedding the same monitor.
 - *Library / analysis* `/.../library`, `/.../library/views/:viewId`,

docs/features/recording.md

@@ -55,9 +55,11 @@ it keeps growing as people speak.
   drop off before recording, while it's still fixable.
 - *Each live recording* - who's recording, paused, or finishing, with a live transcript
   snippet and a running duration.
-- *Is the audio coming in?* - a recording that was sending audio and stopped gets an
-  *Audio stopped?* warning (they may have lost connection); a locked phone or hidden tab shows
-  *Screen locked*, because recording pauses until they come back.
+- *Is the audio coming in?* - each live recording shows a small level meter, so you can see
+  audio is actually flowing; when it goes silent it nudges you to *check the mic isn't muted*.
+  A recording that was sending audio and then stopped gets an *Audio stopped?* warning (they
+  may have lost connection); a locked phone or hidden tab shows *Screen locked*, because
+  recording pauses until they come back.
 - *Transcription progress* - a *Transcribing* count per conversation, a rough *catch up*
   estimate when a backlog builds, and an *Error* badge when something needs attention.
 

docs/users/host/collecting-conversations.md

@@ -48,9 +48,10 @@ flow is in [the participant portal](../../features/portal-and-participant-experi
 *[dembrane next only](../../features/dembrane-next.md).* During a live session, open
 *Monitor* in the project sidebar. It shows every participant from the moment they scan the QR,
 moving through *Scanned → Setting up → Recording* - so you spot the person stuck at the mic
-check while they're still in the room. Each live recording shows its state, duration, and a
-live transcript snippet; if someone's audio stops coming in you get an *Audio stopped?*
-warning, and a locked phone shows as *Screen locked*. Transcription progress and errors show
+check while they're still in the room. Each live recording shows its state, duration, a level
+meter so you can see audio is actually arriving, and a live transcript snippet; if someone's
+audio stops coming in you get an *Audio stopped?* warning, and a locked phone shows as
+*Screen locked*. Transcription progress and errors show
 per conversation, with a rough *catch up* estimate when a backlog builds. The project home
 shows the same thing in brief under *Live & recent*.