fix: spawn whisper-server on the host:port sttUrl points at

[nixfred]

Problem

The onboarding wizard and Settings let users change sttUrl, but the whisper supervisor is created without a port option, so it always spawns whisper-server on the hardcoded 127.0.0.1:8080. On machines where something else already owns 8080 (nginx in my case), the wizard's transcription test fails with a confusing HTTP 404 from /health (whatever is squatting the port answers), and the transcribe stage can never start its own server.

Fix

Derive the spawner's host/port from the same sttUrl setting the stt HTTP client already uses, so client and server agree by construction:

const sttEndpoint = new URL(s.sttUrl);
const whisperSupervisor = createWhisperSupervisor({
  getModelId: () => settings.get('sttModel'),
  host: sttEndpoint.hostname,
  port: Number(sttEndpoint.port) || 8080,
  ...

WhisperSupervisorOpts already accepts host/port, so this is wiring, not new surface. Default behavior (no custom sttUrl) is unchanged.

Testing

• 13/13 whisper supervisor tests pass; full suite 673/673 green.
• Verified live on a Mac where nginx owns 8080: set sttUrl to http://127.0.0.1:8090, app spawned whisper-server on 8090 and transcribed end to end (large-v3-turbo, macOS 26 / M4 Max).

Love the app, by the way — fully local meeting notes with the process-tap capture is exactly the right architecture. This came out of a real deploy tonight.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Fx2epy4XwaBS3S8Y5J7FX9