"""End-to-end: the capture request and the per-leg encoder parameters follow the selected quality preset. `pickSurface()` asks the capture device for the *selected* preset's pixel budget and frame rate instead of one hardcoded 4K/30 request, and `start()` records which preset the live capture belongs to. The capture assertions read the page's own request back through `window.__probe` (AGENTS.md §6): `lastRequested` is the size the request named, `qualityKey` the preset it came from. The per-leg assertions read the *committed* sender parameters back from the sharer's real RTCPeerConnection legs through the same `__probe` handle: each leg encodes under `round(config.maxBitrateBps * preset.factor)` and the preset's `degradationPreference`, read at call time — so a preset chosen before a viewer joins lands on that leg's first offer. Media rules still govern: pixel assertions are made on the *viewer's* `