169758d42f
test_hermes_state.py was the slowest file in the suite (46.7s in CI's durations cache) and therefore the LPT floor: no test slice can finish faster than its slowest file, which caps how far slicing the test matrix wider can cut the merge-gate critical path. Profiling (cProfile on the slowest tests) found the time was dead, not work: 1. time.sleep in optimize_fts_storage's inter-chunk throttle — 4.1s of a 4.6s migration test. The throttle exists so a LIVE gateway/CLI sharing the DB isn't starved of the write lock; tests run against a private tmp-path DB with no concurrent process, so the sleep protects nobody. New autouse fixture zeroes _FTS_REBUILD_MIN_PAUSE / _FTS_REBUILD_DUTY_FACTOR for this file (~20s saved). No test asserts on wall-clock pacing, so nothing weakens. 2. TestGetMessagesPagination._seed appending 3000 messages one append_message (= one commit, and off WAL one fsync) at a time — ~10s of seeding before the query under test even ran. Switched to append_messages_batch (one write transaction), the API the docstring of which exists for exactly this shape. The perf contract the seed feeds still discriminates: measured 11 progress-handler steps on the indexed path vs 855 on the forced scan path, against the unchanged 300 threshold. Measured (local, 3 runs + canonical runner): before: 187 passed in 51.8s after: 187 passed in 9.1-16.1s (canonical scripts/run_tests.sh: 14.9s) Zero production code touched; 187 tests before and after.