StreamBridge 0.7.1

A small release with one job: when OBS says no, the log now says why and what to do about it.

What changed

Running the camera demo against a real OBS 31 produced 26 lines of this:

SaveReplayBuffer failed (501: )

Correct, and useless unless you have the obs-websocket status enum memorised. The same failure now reads:

SaveReplayBuffer failed: the replay buffer is not running — start it in OBS
(Controls → Start Replay Buffer) (code 501)

Every obs-websocket v5 status code is translated, and the ones with an obvious cause get the fix spelled out:

• 501 on a replay save — the replay buffer is off, start it in OBS
• 500 / 501 on record or stream — OBS is already recording / not recording
• 600 on a scene, source or filter — nothing by that name, and names are case-sensitive
• 506 on a preview scene or transition — Studio Mode is off

Where OBS sends a comment of its own ("No source was found by the name of DeathText"), it is kept and appended, so you get both the advice and the detail. Unknown codes still read like a sentence instead of a bare number.

This shows up everywhere an OBS failure is reported: the server log, /streambridge status, and the web panel.

Under the hood

• 163 automated tests, green, including the exact 501-with-empty-comment answer the real OBS gave.
• No new code paths: the translation happens where the failure is already turned into text, so every existing report picked it up without being touched.

Unchanged

Everything from 0.7.0: the camera director, the camera.cut event, the OBS transform action, the web panel and overlay, Twitch chat without a token.