These cases live in the `api:curated` lane and spawned `pnpm --filter
@fusion/dashboard test` — the very command whose lanes they were running inside.
Under a full 15-lane run that child had to resolve pnpm through Corepack while
other lanes held the machine, and it intermittently produced nothing at all: the
lane log came back empty, the assertion read "0 lanes launched", and a test about
the orchestrator failed with no orchestrator defect involved. Seen in both
`--all --no-fail-fast` runs today; the file passed alone every time.
An earlier attempt only set COREPACK_ENABLE_DOWNLOAD_PROMPT=0, which removed the
visible Corepack line but not the failure — the child still produced no output.
That fix is replaced rather than kept.
They now invoke `node scripts/run-quality-tests.mjs` directly. Every assertion is
unchanged (lane names, the 15-lane count, fail-fast labelling, `--` passthrough,
which parseArgs already unit-tests), and the one thing the pnpm spawn uniquely
proved — that the package script actually points at this orchestrator — is now
asserted directly against package.json.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
cc19584cc4