You'll notice
Bridge session fetches are now blocked outright for non-Anthropic providers
What
The internal bridge_session_get helper, used to fetch a session over the bridge, now checks upfront whether the active provider is Anthropic itself (first-party). If it isn't, the fetch is refused immediately, returning session:null and logging a new telemetry reason (bridge_session_get_3p_provider). Separately, this helper gained a useV2 override option, so it no longer always derives whether to use the V2 path solely from isCcrV2SessionCrudEnabled.
Why
This stops session-fetch requests from going out to the bridge when a third-party provider is in use, rather than attempting a fetch that presumably wasn't meant to succeed in that setup.