feat: place Parakeet STT on CPU when GPU cannot co-locate
On Linux hosts where the bundled brain is resident on a single discrete GPU that cannot also hold a worst-case ordinary-segment Parakeet run, transcribe.parakeet-cpp.device: auto now resolves to CPU at parakeet-server launch.
That decision uses measured floor-tier brain residency 4541 MiB + Parakeet worst case 5022 MiB + 1024 MiB margin = 10587 MiB. As a result, 6/8/10 GiB cards place STT on CPU, while 11/12 GiB and up keep it on the GPU.
Every other state fails toward today's behavior: unknown VRAM, probe failure, unmeasured capable-tier residency, 2+ discrete GPUs, integrated or unified memory, or an inactive bundled-brain lane keep auto resolving exactly as before.
The placement is announced through the supervisor reason line, GPU-check detail in sol check and the local provider fit report, and journal/health/parakeet-cpp.placement so transcribed events and transcript headers report the real device placement, cpu/gpu, rather than literal auto. The checks remain ok because this is a hardware-fit fact, not a failure.
No config keys were added; transcribe.parakeet-cpp.device still validates as auto | cpu only.