`npm start`
wait for chronik to throw an error. It will, because the first two URLs are intentionally set incorrectly.
Watch dev log to see `tryNextChronikUrl` iterating until it gets to a good server
UI is restored, app works
Note that websocket reconnect attempts for the invalid chronik instance also stop