feat: Trace the tests of the Node.js test runner in turbo trace
A script that runs `node --test` (also `tsx --test`, with `--import`,
`--require`, `--loader`, `--env-file`, a `NODE_OPTIONS` prefix, after
`cd dir &&`) starts a run of the new `node-test` framework. The files the
command names, the files its globs match, or the runner's default patterns
are its tests. Each test depends on its own imports, on the modules the
run loads first, on the env files and on its snapshot file, and the task
of the script is named for it.
The patterns are those of Node 22, 24 and 26; `tsx --test` adds its own.
A run whose files or preloads the command line does not say exactly (a
computed argument, a directory, export conditions, a config file, an
option the trace does not know), a run after a build in the same script,
and a run whose files are not source files stay uncovered: the task runs
whole.
A manifest is read for its runs without becoming an input: the runs are
part of the key of the packages it governs.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>