meeting-transcribelisted

# meeting-transcribe Runs `whisper-stream` (whisper.cpp) in the background, transcribing the chosen audio input in ~3-second steps into a growing text file under `~/Documents/MeetingTranscripts/`. All management goes through one script: ``` scripts/transcribe.sh {check|setup|devices|start|status|stop} ``` Use the script rather than invoking whisper-stream directly — it handles the PID file, output naming, and fail-fast checks, and `stop` depends on its bookkeeping. ## Workflow ### 1. Check readiness `scripts/transcribe.sh check` — verifies whisper-stream and the model exist. If anything is missing, `scripts/transcribe.sh setup` installs whisper-cpp via Homebrew and downloads the multilingual `base` model (~148 MB). `setup --model small` fetches a more accurate model (~488 MB) — offer this if the user complains about transcription quality; then start with `WHISPER_MODEL=~/.whisper-models/ggml-small.bin scripts/transcribe.sh start`. ### 2. Pick the audio source Default (no flags) captures the system-default input — the built-in mic. That is correct when the user talks in person or listens on speakers. If the user is in a call **wearing headphones**, the mic never hears the other participants: run `scripts/transcribe.sh devices`, and read `references/system-audio.md` to choose between the "Microsoft Teams Audio" virtual device and a BlackHole aggregate device. Ask the user which situation they're in if it isn't obvious. ### 3. Start ``` scripts/transcribe.sh start [--d