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
..
tsconfig.typecheck.json	feat(8.0): reserved-field contract — one canonical location, typed prevention, unified read/write	2026-06-11 13:13:09 -07:00
vitest.integration.config.ts	feat(health): the gate reads the named report — reads refuse loudly, never rebuild; open serves before it returns; the ceremony door	2026-08-24 12:45:51 -07:00
vitest.perf.config.ts	test(batch): the batch-vs-individual timing assertion runs in the perf lane, not the correctness gate	2026-09-02 11:54:29 -07:00
vitest.semantic.config.ts	test(8.0): integration rot pass — 77→17 failures (parallel per-file hardening)	2026-06-17 13:11:41 -07:00
vitest.unit.config.ts	chore(8.0): final pre-RC1 sweep — API consistency, named errors, orphans, zero-cast codebase	2026-06-11 14:51:00 -07:00