3 commits

Author	SHA1	Message	Date
David Snelling	7932175503	test(vfs): reclassify the many-files wall-clock case into the perf lane ... vfs.unit.test.ts's 'Performance > should handle many files efficiently' (100 writes + readdir, 5.5s write budget) is a wall-clock flake: 121ms alone, 16.5s under the gate's sibling-file contention — the code never caused it. Same pattern already used for storage-batch-operations.test.ts's batch-vs-individual timing case: ctx.skip(!process.env.BRAINY_PERF_LANE, reason) inside the test, and the file added to vitest.perf.config.ts's include list (it stays in the unit gate's *.unit.test.ts match too, so every other test in the file keeps running there).	2026-09-02 14:19:03 -07:00
David Snelling	ebb3a4bf13	test(batch): the batch-vs-individual timing assertion runs in the perf lane, not the correctness gate ... The wall-clock ratio (batch faster than N individual gets) started failing under the exclusive release gate because individual gets got faster on this candidate (open-path/hydration changes), not because batchGet regressed — a perf assertion misclassified into a correctness file. Skip it under the default gate via a BRAINY_PERF_LANE env marker the perf config sets for itself; the file joins the perf config's include list so the case still runs (with every other test in the file) under `npm run test:perf`.	2026-09-02 11:54:29 -07:00
David Snelling	dee46b35c8	ci(test): perf and scale benchmarks leave the correctness gate	2026-09-02 10:21:06 -07:00