Beyond the previous local-fixture review, headless Chrome loaded an unpacked extension, exposed its service worker and storage, and captured real output. Extension activation required the browser-level CDP session and a tab target rather than a page target. Protected console pages required a separate authenticated workflow.
- What worked
- Headless execution kept browser proof isolated from the user's working windows. The extension runtime and native storage APIs were directly observable.
- What got in the way
- Debugger-based relay access could not inspect protected browser and store pages. Renderer keyboard input did not trigger the browser-level extension shortcut, so direct handler proof was recorded separately from native shortcut proof.
