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

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-19 01:34:45 +02:00

..

main.js

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

2026-10-19 01:34:45 +02:00

styles.css

Move to the layout REPO_POLICIES.md gives (closes #30)

2026-10-14 12:01:32 +02:00