Clock errors no longer stop probing; legend reads >=500ms (closes #149, closes #152) #167

Merged
clawbot merged 1 commits from issue-149-152-clocks-legend into next 2026-10-19 01:34:46 +02:00
1 Commits
Author SHA1 Message Date
sneak 0c6a59a9fa Clock errors no longer stop probing; legend reads >=500ms (closes #149, closes #152)
check / check (push) Waiting to run
The header's clocks start last in init, after the rounds, and an error
formatting them, as in a browser that rejects the "shortGeneric" time
zone name, leaves both clocks blank instead of stopping the page before
its first round. updateClocks moved out of init so a unit test can call
it.

The footer legend's red entry reads >=500ms, as README.md and
CONFIG.latencyColors have it. buildUI is exported so a unit test can draw
the page and check the legend against every entry of
CONFIG.latencyColors.

Model: opus-5-5
2026-10-18 23:29:22 +00:00