Disable host browser-storage globals for DOM-emulated unit tests

When a newer JavaScript runtime exposes experimental browser-storage globals, DOM-emulated unit tests may bind to the host implementation instead of the test environment’s storage object. A missing persistence path can then make every test fail in setup even though application behavior is untouched. First reproduce with the runtime’s browser-storage feature disabled; if the suite passes, classify the original result as a toolchain/environment failure and pin the supported runtime or disable that host feature in local validation. This applies only when the failure originates in common test setup before assertions.

Applies when: Browser-oriented unit suites suddenly fail on storage methods after a runtime upgrade. Keywords: unit tests DOM emulator localStorage runtime upgrade false failure