The Content-Security-Policy had no exception for static.ads-twitter.com
(script-src) or the analytics.twitter.com/t.co conversion beacon
(img-src, connect-src), so uwt.js and every adsct conversion ping were
silently blocked by the browser on every page view. Same bug class
independently found and fixed on bidstage.app and ereboslab.com today.
Verified live: static.ads-twitter.com/uwt.js now loads (200) and the
adsct beacon fires with no CSP violations in the console.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>