test-run-all-timing.sh flakes on Windows: a 1s tie between the fast and slow fixtures sorts by name #482

Observed on PR #479 (markdown-only diff), hooks (windows-latest, shard 2/4), job 112276374977:

FAIL: the slower suite is listed before the faster one
  slow_line=10 fast_line=9

The timing block printed 1s test-b-slow.sh and, one line above it, the fast fixture also at 1s. Timing is whole-second wall clock, so a fast suite that straddles a second boundary on a loaded Windows runner reads 1s too. With the two tied, the order falls back to name, and test-a-fast.sh sorts first.

The assertion is about ordering by time, and a tie makes that ordering undefined at one-second resolution. Two directions, not costed:

• make the slow fixture sleep 2 (or 3), so a tie needs the fast one to cross two boundaries
• assert ordering only when the two printed times differ, and report the tie as could-not-evaluate rather than a pass

Unrelated to the PR it fired on. Rerun of the failed legs requested.

[AI-generated]