SIP INVITE events dropping in Chrome extension during trunk swap

Wiring up a Chrome extension for GC screen pops keeps dropping SIP INVITE events when the agent swaps trunk groups. The client_app_sdk v4.2.1 logs show the client.app.messaging.send() call succeeding, but the content script never catches the payload. Console throws a Cross-Origin Read Blocking (CORB) block on the /api/v2/telephony/sessions endpoint during the handshake. Running on Chrome 120 with the embeddable framework v2.8. The overlay just sits there doing jack all while it’s ringing out to voicemail. Don’t see the payload crossing the boundary.

Already checked the manifest v3 permissions and verified the SIP trunk routing in Architect. Steps followed so far: 1. Pinned the client_app_sdk event listener to inbound_call. 2. Forced chrome.runtime.sendMessage to bypass the service worker cache. 3. Swapped the fetch headers to skip the CORS preflight. The network tab shows a 401 Unauthorized on the SIP registration ping right after the extension initializes. Logs point to a stale bearer token in the client.app.session store.

Problem: CORB blocks the SDK during trunk swaps.
Code: chrome.runtime.sendMessage({type: 'SIP_INVITE'})
Error: You’ll hit a missing ALLOWED_ORIGINS in your MANIFEST. Don’t skip the WEM adherence mapping.
Question: Have you mapped this to WEM adherence tracking?