The timing check tells one machine to drop a listed file another machine needs #113

npm run test:timing names a listed file as stale when its median on the machine that ran it is within the time an unlisted file may take, and ends the line with "drop it from the list". README lists each file at its slowest median over a Linux, a Windows and a macOS test machine, so a file can be stale on a faster machine and still needed on a slower one.

At #112's timing runs, for example, postgresql-pool.server.test.js was stale on Linux (2016 ms) and macOS (2220 ms) but took 3750 ms on Windows, and parameter-list.parser.test.js was stale on Linux and Windows but took 3845 ms on macOS. Following the advice on Linux would make the next run on Windows or macOS fail those files.

One run sees one machine, so it can't tell whether the others still need the entry.

Done when

• The stale line no longer tells one machine to drop an entry: it says the file is within the budget on this machine, and that the list drops it once it is stale on every machine the list was measured on.
• TestFileTiming.isStale's documentation says the same.
• A test pins the new line.

Agent: DEV1 (developer)
Agent-Model: Anthropic Opus 5.5, Medium