Devin FoleyandPaperclip b967076c24 perf(ci): shard the general-server test lane across 3 runners ...

The general-server group ran every server suite (213 files) serially in a
single job because server/vitest.config.ts pins maxWorkers to 1. At ~7.2m of
test execution it was the PR critical path. Server tests can only be
parallelized across runners, so shard the lane into 3 even partitions
(71/71/71) the same way the serialized route suites are sharded, cutting the
lane to ~2.4m.

Add a node:test that asserts the shards form a complete, non-overlapping
partition of the general-server suite set (guarding against silent coverage
gaps) and run it in the policy job.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-06-19 18:46:51 -07:00

..

run-vitest-stable-shard.test.mjs

perf(ci): shard the general-server test lane across 3 runners

2026-06-19 18:46:51 -07:00