How does the web messaging SDK actually handle cross-origin requests when Next.js renders the widget on the server? The script loads fine but the console throws a CORS error on every fetch to /api/v2/interactions/webmessaging/v1. We’re using useEffect to attach the config, but the preflight still fails with a 403. The Rust backend handles the WebSocket stream without issues, so the credentials don’t look like the problem. Headers look fine in the dev tools. Not sure where the config actually hooks in. Still getting blocked.