fix: Leave a node --test run unmapped when the script starts the same command another way in turbo trace
A task is told to run exactly the files of a run by its command line.
A script that starts the same command twice, once after an export, with
a variable in front that changes what Node loads, with an env file that
sets NODE_OPTIONS, in a group, a branch or a subshell, or in a directory
that is not followed, has no mapped run for that command: the task runs
whole.
The files read for a manifest's runs (the manifest, env files, an
.npmrc, preload files) are regular files of at most 4 MiB; a run that
names anything else is not mapped. A file argument longer than 1024
bytes is not read as a glob, and a glob nested deeper than 32 groups is
translated as an over-approximation, so it is never exact.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>