A never-connected install could not reach a single screen. Onboarding swapped the
whole shell out until `onboarded`, which only became true after `/api/health`
*and* `/api/timer/state` both answered, and there was no way past. The comment
explaining that argued an app which shows nothing is worse than one that insists
— which was true when nothing survived a process, and is not true now: the timer
ticks from the kept anchor, the guard enforces the kept rules, taps go to the
outbox and the lists show what they last held.
So once an attempt has actually failed *for want of a network* — not on a wrong
address, where stopping here is still right because this is where the message can
explain it — the screen offers "Use it offline for now" and says exactly what
that does and does not do.
The other direction, for honesty: the blocker's rules are the server's settings
document, and there is no outbox for it. A settings PUT is a deep merge of a
shared object, so queueing one would replay a stale version over whatever the web
UI did meanwhile. The "Focus guard on" toggle and "Save lists" are therefore
disabled offline instead of appearing to work and silently failing, which is the
pattern the Settings screen already followed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
timka123andClaude Opus 5
81032aca51