A rejected connection now records whether your corporate proxy said no rather than the API.
What's wrong with this entry?
WebSocket 403 rejections are now attributed to a source, so a corporate proxy refusing the connection is reported differently from the API refusing it.
- Telemetry splits into
transport_closed_403_nonorigin_cf,transport_closed_403_nonorigin_otherandtransport_closed_403, with matching recovery events. - The close event carries a
reject_sourcefield plus streak counters. - Credentials-rejected errors gain a
_credentials_rejected_nonoriginsuffix.
transport_closed_403_nonorigin_cf
Strings lifted out of the shipped bundle, so the claim above can be checked against them.