BL-130 Ideas

Bug: Spotify playback unreliable in live sessions (no active device, playlist drifts)

Bug report, from Session 41 (6 November 2026).

What happened: asked for mermaid style music during the dragon turtle scene. Playback failed with “no active device” twice. When it did play, the chosen playlist gave one or two fitting tracks and then drifted into unrelated music (pirate film themes), and the atmosphere was lost.

Expected: the chosen music keeps its mood for the whole scene, or stops, and a missing device gives a clear message with a way to recover.

Reported cause (unverified): the DM believes the Spotify MCP behaviour changed at some point, possibly through a change made in another session or a production command. No record of such a change has been found in this repository’s history; the only Spotify code change since Session 41 is narration ducking (BL-129, released in 0.15.0). Session 41 itself ran before that release.

Also noted: playlist links were found by web search on third-party pages and could not be verified.

To investigate: git history and deploy history for the Spotify code and tool, how playback starts a playlist (shuffle, repeat and autoplay behaviour once the curated tracks end), how a device is chosen or woken when none is active, clearer errors for the DM, and a check that a link points at the intended playlist before it plays. Confirm on a real device that BL-129 ducking lowers and restores volume without interfering; it has only been tested with stubs.

Related: replacing Spotify with generated, layered music is a separate item, pending the music spike.