… <Example>

vitest 4.1.10 (+ @vitest/browser, @vitest/browser-playwright,
@vitest/coverage-v8) deterministically fails 8 @pyreon/zero-content
specs in BOTH the happy-dom suite (components.test.tsx Callout
rich-children, example.browser.test.tsx Example mount + all share-key
specs) AND the real-Chromium harness — the exact two red required
checks on this PR (test (zero) + Test (browser)).

Bisect-verified in both directions:
- vite 8.0.16 + vitest 4.1.10 -> FAIL (8 specs)  [vite exonerated]
- vite 8.0.16 + vitest 4.1.9  -> PASS
- vite 8.1.5  + vitest 4.1.9  -> PASS 743/743 node + 37/37 Chromium

v4.1.10 ships exactly two fixes; the VM deps-optimizer
encoded-URI module-resolve change (vitest-dev/vitest#10661) is the
plausible interaction with <Example>'s dynamic loader registry.
Root-causing vitest internals is out of scope for a deps PR — the
single bump is reverted (declarations restored to origin/main
values), everything else in the batch stays.

Re-verified on the final combination: zero cell green (zero 1679,
zero-cli 21, create-zero 103, zero-content 743 + 37 browser),
validate-fast 15/15.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>