Vitest: shared lazy memo for expensive per-file test fixtures is safe when the runner clones+freezes input
When two tests in a Vitest file repeat the same expensive async run, memoize the promise at describe scope (let p; const shared = () => (p ??= run(...))) instead of calling run twice. It is safe only if the run deep-clones and freezes its input and the tests only read the result; if the first call rejects, every test sharing it fails together, which is usually acceptable. Separately, vi.setConfig({ testTimeout }) at module top level applies to just that test file; to confirm it takes effect, temporarily set it to 1 ms and check that the tests fail with 'Test timed out in 1ms'. When a wall-clock perf assertion (expect(best).toBeLessThan(budget)) fails during a full-suite run on a heavily loaded machine, rerun the file alone before calling it a regression; such budgets are flaky under load and are better measured relative to a baseline.