The wrong part of the page answered
During a Gemini test in an isolated Edge browser, we found that a diagnostic message could receive a reply from a hidden helper frame before the main page responded. That made the status check misleading: it could report a missing composer even though the visible page had one.
In extension 0.5.49, these diagnostic messages explicitly target the main frame. We added regression checks for the response, including a closed tab and an empty reply. The change fixes which page answers a status request; it does not, by itself, prove that content was blocked.
We also had to correct the test input
An earlier run used a published demo key in explicit test prose. That exact public example has an intentional exemption, so its passing through was not evidence that an arbitrary credential could bypass Block. We repeated the test with newly generated, nonfunctional values.
The lesson was straightforward: document exceptions in the test plan. Use a unique value for each run and check the submitted request for that value. Otherwise, a test can appear to expose a bug—or appear to pass—because it never exercised the rule you intended to check.
What the completed test established
In three separate Gemini runs, Block prevented the fresh test value from appearing in outgoing requests, Redact sent a replacement without the original value, and ordinary text reached the actual Gemini endpoint. The browser used a temporary extension copy connected to a local test enrollment and policy service.
That is a result for those text submissions and that setup. It does not qualify Gemini uploads, authenticated workflows, the complete hosted-backend chain or a signed store installation. Other providers that stopped at verification or access screens remained unverified. We keep those limits with the result so the test cannot be mistaken for a claim of universal coverage.