Affected packages with a vitest config now run `vitest run --changed <base>` (only tests in the changed files' module graph) under the tight "changed" watchdog, instead of each package's ENTIRE suite under a 60-min backstop. Packages without a vitest config fall back to their full `test` script. The curated gate suite still runs as the cross-cutting safety net. Measured: a dashboard hub-component change drops from 822 files (5-8min) to 40 files (~98s wall incl. gate). Common/leaf changes scope to far fewer. NOT yet <60s for hub-component changes — the fixed jsdom/setup floor still dominates (needs the overhead-reduction follow-up), and one scoped-run test failure needs isolation triage before this gates verification. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
55 KiB
55 KiB