Split off from #1928 during review (claude review flagged this gap).
The new `'audio'` media-job kind (server/services/audioGen/local.js, server/services/mediaJobQueue/index.js) has no socket bridge: `genEvtPrefix()` in server/services/socket.js maps only `'video'`/`'image'` kinds to `*-gen:failed` socket events, so a failed first-pass music-bed render (engine crash, OOM, sidecar error) surfaces no toast/spinner-resolution to the user — they'd only discover it by noticing `project.musicBed` never populated, or by polling the Render Queue (`/api/media-jobs?kind=audio`).
This matches the pre-existing `'training'`-kind precedent (also no socket bridge), so it isn't a regression — but since the music-bed toggle is a user-triggered, user-visible action (unlike background training), it's worth a small follow-up:
- either wire `'audio'` into the existing socket failure bridge, or
- surface failed/queued audio jobs in a Render Queue UI view (there is currently no client page that instantiates `MediaJobsQueue kind="audio"`).
Also flagged: no client UI currently renders `project.musicBed` at all (e.g. a player/badge on the Creative Director Overview tab) — likely intentional given #1928's server-first scope, but worth deciding whether/when to add.
Split off from #1928 during review (claude review flagged this gap).
The new `'audio'` media-job kind (server/services/audioGen/local.js, server/services/mediaJobQueue/index.js) has no socket bridge: `genEvtPrefix()` in server/services/socket.js maps only `'video'`/`'image'` kinds to `*-gen:failed` socket events, so a failed first-pass music-bed render (engine crash, OOM, sidecar error) surfaces no toast/spinner-resolution to the user — they'd only discover it by noticing `project.musicBed` never populated, or by polling the Render Queue (`/api/media-jobs?kind=audio`).
This matches the pre-existing `'training'`-kind precedent (also no socket bridge), so it isn't a regression — but since the music-bed toggle is a user-triggered, user-visible action (unlike background training), it's worth a small follow-up:
Also flagged: no client UI currently renders `project.musicBed` at all (e.g. a player/badge on the Creative Director Overview tab) — likely intentional given #1928's server-first scope, but worth deciding whether/when to add.