Changelog

When one shard runs more than twice as long as the median, the run summary now names the test responsible and its time against its recorded average.

go test projects no longer need the generic file-access recorder. Recording overhead on Go suites drops from about 9 percent to 3.

Both conflicting runs of a quarantined test now keep the test runner’s random seed, so you can reproduce the failing order locally with one command.

uv.lock, bun.lock and Cargo.lock now select the whole suite without any configuration, alongside the lockfiles already covered.

A test file renamed in the same pull request could inherit the old file’s map entry. It is now treated as unmapped and always runs until it is recorded again.