Development record

make preflight's eval lanes run go test with no -timeout, so they inherit go test's ten-minute per-package default. On a loaded machine (load 21 to 31 on 10 cores, several sessions testing at once on 2026-10-24) the smoke lane's evals package ran past ten minutes with no test hung: TestEveryCommittedEntryFitsItsDeclaredWindow alone took 128 s, and the package was killed with 'panic: test timed out after 10m0s', failing a preflight whose change touched no eval. The unit and race lanes declare -timeout 20m and 40m; the eval lanes' ceiling is a default nobody sized.