Color the dot beside each host name by its latest latency (closes #207)

updateHostRow gives the dot the color of the row's latest figure from
CONFIG.latencyColors, gray when the check failed or no result has come
yet. Pausing still sets it gray. The dot carries a status-dot class and
data-host, as the figure and status line do, so both functions find it
the same way.

Model: opus-5-5

README.md

@@ -113,19 +113,19 @@ half second. As soon as one answers, a new round starts.
 ### Rows, colors and controls
 
 A figure and its line in the graph take the color of the legend in the footer,
-from green under 50 ms to red from 500 ms up; gray is no answer. The graph's
-axis ends at 1000 ms; a higher latency is drawn at the top, and the figure still
-shows its real value.
+from green under 50 ms to red from 500 ms up; gray is no answer. The dot beside
+the host's name takes the same color. The graph's axis ends at 1000 ms; a higher
+latency is drawn at the top, and the figure still shows its real value.
 
 From time to time, the page sorts the WAN rows by their latest latency: fastest
 first, failed last. The pin button at the left of a row keeps the row at the
 top; pinned rows are sorted by name. `datavi.be` is pinned at start.
 
 `Pause` stops the checks: the graphs keep scrolling with a gap for each paused
-round, and the figures turn gray. The `Interval` menu sets the time between
-rounds: 1, 2, 3, 5, 10, 15, 30 or 60 seconds. Changing it clears the history and
-starts a new round at once. The `Debug log` checkbox in the footer opens a panel
-with the page's last 1000 log lines.
+round, and the figures and dots turn gray. The `Interval` menu sets the time
+between rounds: 1, 2, 3, 5, 10, 15, 30 or 60 seconds. Changing it clears the
+history and starts a new round at once. The `Debug log` checkbox in the footer
+opens a panel with the page's last 1000 log lines.
 
 ## Reporting