meeting-audio-reportlisted

# Meeting audio report A recording becomes two things: a **verbatim** transcript, and a report someone who missed the meeting can act on. Two words govern the run. **Coverage** — did every second of audio reach the transcript? Transcription drops blocks on transport errors, and the loss is silent. The one block lost is as likely as any other to hold the decisive sentence. Coverage is a gate, not a statistic. **Fidelity** — does every name, number, and quote in the report trace to the audio? A transcription model guesses at proper nouns; a summarising model guesses at who said what. Both guesses arrive fluent and confident. The report carries what the recording supports and flags the rest. ## 1. Transcribe ```bash scripts/transcribe.py <audio-or-video> [--out-dir DIR] ``` Writes `<stem>-transcript.md`, `<stem>-coverage.json`, and `<stem>-blocks.json` beside the input, or into `--out-dir`. Done when the script has exited and the manifest exists. ## 2. Pass the coverage gate The script exits non-zero when any block failed, and names each gap with its time range. ```bash scripts/transcribe.py <audio> --retry-missing [--out-dir DIR] ``` Repeat until it exits zero. Failures are transport, not audio, so a second attempt usually lands. Done when `blocks_ok` equals `blocks_total` in the manifest. Carry which blocks were recovered into step 5 — a recovered block that turned out to hold something material is itself a finding. A gap that survives repeated recovery goes into