The original question here was: when you click an instrumented thing, why don't the events always show up in the console?

Short answer is that there's a complex interplay between devtools and the browser. Devtools have edge cases where events fire but the browser never surfaces it, so clicking around isn't a reliable way to confirm what events were actually sent. That makes it hard to debug in isolation.

Digging in to how we'd actually verify events on the beta cluster: we currently suppress event sending when a user forces enrollment with an override. This mirrrors prod (where suppression makes sense, as we don't want test events polluting the stream). But beta has its own stream, and overrides are often the only practical way to test reader scenarios that
enroll very small proportions of users.

Path forward here is to lift suppression on beta: let events send to the beta stream even when the override is in use. This is a key QA flow. Since this is a concrete solution rather than a solution to this bug, I'm closing this and filed T433711: Send events to beta cluster stream when using enrollment override to track the fix.