OBS source detection can fail on startup without warning or retry

[Melkepakken]

Description

React Player can sometimes fail to restore/detect its OBS Browser Source when OBS starts.

This appears to happen especially when OBS opens on a scene where the React Player Browser Source is not currently active or visible, although the exact cause still needs to be confirmed.

When this happens:

• React Player connects to Streamer.bot normally.
• OBS-dependent controls such as Show on stream and Fullscreen do not work.
• The normal dock view does not clearly tell the user that OBS source detection failed.
• Opening Settings and clicking Detect again immediately fixes the problem.

Expected behavior

React Player should recover its OBS target automatically after OBS starts without requiring the user to manually run detection again.

If the OBS target cannot be resolved, the normal dock should clearly indicate that OBS setup needs attention instead of silently leaving controls unavailable.

Things to investigate

• Check whether initial detection is running before OBS and its Browser Sources are fully ready.
• Verify whether source visibility/activity at OBS startup affects validation or detection.
• Consider automatically retrying OBS detection after an initial startup failure.
• Add a visible warning/state to the main dock when the OBS target is not ready, with Settings / Detect again available as the manual fallback.

Manual Detect again already works reliably once the problem occurs, so the existing detection system itself does not appear fundamentally broken.