* ci: trace shared script modules to the tests that import them
A pull request that changed any scripts/lib module ran the complete
suite. Shared script modules now pass a change through to the tests,
verifiers and other shared modules that import them, like test helpers.
Another consumer (a build or test-runner script, root configuration,
package metadata, a hook or a workflow) that imports the module or names
it by file name still selects the complete suite.
The tracing core is exported as traceAffectedTests so a bounded local
gate can reuse it.
Fixes#11381
* ci: follow verifier source loads and named verifiers when tracing script modules
- Module URLs (new URL("./x.mts", import.meta.url), as loaded by
importVerifierSource) are import edges.
- A test that names a verifier or shared module the change reaches is
selected, not only one that names a changed path.
- A changed shared module that no test reaches runs the complete suite
even when other changes select tests.
* ci: select tests that start the built server beside a changed presentation owner (#11519)
* ci: select tests that start the built server beside a changed presentation owner
A test that starts the built CLI or MCP server reaches server, contract,
entrypoint and CLI modules through the build, not an import, so a change
there selected none of them (#11146 failed on main this way). Such a
test is now selected when it, or a helper it imports, starts
scripts/rea.mjs or dist/, and it imports a module from the changed
owner's directory.
Fixes#11366
* ci: recognise only the repository's built entry points as runtime launchers
A package subpath such as ajv/dist/2020.js matched the dist/ pattern, so
in-process tests importing Ajv counted as built-runtime launchers.
* ci: balance selected test shards by recorded duration (#11522)
A selected PR run split its files across groups round-robin, so a few
slow files could land together. The plan now records the selected files
and a shard count (version 3), and each job runs one --shard of the
selection through the exact-test runner with the timing history main
already publishes, so the CI sequencer balances shards by per-file
duration (the median for files without a timing). Without history,
Vitest's own deterministic sharding applies.
Fixes#11382