v1.1.0 — OBS Freeze Recovery

What's New

OBS Freeze Detection & Recovery

The system now automatically detects and recovers from frozen OBS instances. If OBS stops rendering frames for ~60 seconds (process alive but stalled — GPU hang, driver issue, etc.), OSR will:

• Kill the frozen OBS process
• Clear crash sentinel files (prevents OBS Safe Mode dialog on relaunch)
• Relaunch OBS with --minimize-to-tray and --disable-missing-files-check
• Reconnect via WebSocket
• Resume streaming and restore playback position

Recovery is retried on future freezes as long as the previous recovery succeeded. Set OBS_PATH in .env if OBS is not in the default install location.

Dashboard Command Improvements

• Skip & Trigger Rotation buttons now show tooltip explanations when disabled (e.g., "Next rotation is downloading")
• Commands push state immediately after execution for faster dashboard updates
• Skip is debounced to prevent double-skip when a transition is already in progress

Rename: Debug Mode → Ignore Streamer

The debug_mode setting has been renamed to ignore_streamer across the codebase, settings UI, and config files to better reflect its purpose — preventing the target streamer's live status from pausing the 24/7 stream.

Other Changes

• Added Dependabot configuration for automated dependency updates
• Updated GitHub Actions to latest versions
• Various bug fixes and stability improvements

Upgrade Notes

• Rename debug_mode to ignore_streamer in your config/settings.json if you have a custom config
• Optional: Add OBS_PATH to your .env file if OBS is not installed in the default location