The keys tests' results are kept under, by hash: the runtime and the test framework (`resultKey`), and the platform too (`darwin-arm64`) for a test whose code reaches files, the environment or other processes, which differ from one to another. A result travels to another machine only under its own key.
The test root's node_modules: everything in the cache (the pinned aliases generated modules import), plus the test tools under their own names, which Vitest's browser mode looks them up by.
The npm packages a run's browser tests reach (through all the code they use), and Vitest's: what names the bundle Vite makes of them for the browser (`vitestChild`), kept from one run to the next, so an edit that imports nothing new reuses it.
Prepare a Vitest run of these tests: the request a child tcm process runs (`tcm internal-vitest <file>`), and where its results will be. The debugger runs it too, under its own control.