After v3.9.28's bridge fix, kernel.initialize() eager-loads all enabled
domain plugins when the bridge is enabled (default). Five existing tests
asserted lazy semantics (no plugins loaded after initialize, isDomainLoaded
returns false, getPendingDomains returns the list, getDomainAPI returns
undefined, domain health 'healthy' before load) — those assertions only
hold when the bridge is off. Pass the new opt-out flag in those tests so
they exercise the lazy path explicitly.
Caught by the npm-publish workflow's Tests-on-tag SHA gate, not by the
PR-merge CI matrix that ran fast unit tests differently.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>