main ← live-video-watch-leases
In SFU rooms, leaving the room page for the floating call widget left the viewer… with black tiles for everyone else, while the other participants still saw the viewer fine. Reported in https://meta.discourse.org/t/417380.
### Cause
The room page and the call widget each set and cleared the watching state on their own, and both deferred the call to the next run loop. On a page → widget switch the page's teardown `watching=false` landed after the widget's `watching=true`, which unsubscribed the viewer from every camera, screen and screen-audio track. Mesh rooms were unaffected because the watching state does not gate subscriptions there.
### Fix
The watching state is now derived from which surfaces are rendered, instead of from ordered set/clear calls:
- `liveWebrtc.acquireVideoWatch(roomId)` hands out a lease and returns its release function. The service only stops watching a room once its last lease is released.
- Lease changes are coalesced per room in the next run loop, so a handoff in either order causes no unsubscribe and no extra `/state` request.
- A `watchRoom` modifier ties the lease to the rendered element, so it follows room changes and teardown without per-component bookkeeping.
### Behaviour change
Because the lease follows the rendered element, the widget now also stops watching while it shows no video tiles (hidden by preference, or extra minimized) and resumes when shown again. Previously it kept the video subscriptions for as long as the component was alive. Local camera and screen share keep publishing in those states, as before.