[setchy]

Summary

The Vitest TODO suggested moving renderer util tests into the node project. I measured the current split before changing it:

• Full suite without coverage: 22.2s; environment 2%, setup 12%, tests 54%.
• Renderer utils are not pure: storage uses localStorage, keyboard uses document, audio uses Audio, queryClient uses navigator, and the system/auth tests use window.gitify.
• threads and forks fail 71 files on @primer/react CSS imports (ERR_UNKNOWN_FILE_EXTENSION); vmThreads is required.

So the right configuration is to keep the process-boundary split: node for main/shared, happy-dom for preload/renderer, browser for visual. This removes the TODO and documents why a third node project would add a second renderer setup without removing the DOM coupling.

Also excludes Markdown from coverage, which removes the src/__helpers__/README.md parse warning from pnpm test.

Test plan

• pnpm check
• pnpm test — 204 files, 1,974 tests
• No README coverage parse warning

Follow-up

Coverage is the dominant cost (pnpm test 63s vs 22s without coverage). A separate change could make pnpm test fast and add test:coverage for CI; that is deliberately out of scope here.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud