Plan showing an unreachable origin in the web UI (step 19)

A wrong git token made the watcher fail every fetch for 57 minutes while
the branches view kept showing its last known list. WatcherState already
records lastFetchError and /api/watcher already serves it; only the UI
never renders it.

The step also folds in the logging volume: one outage wrote 297 identical
warnings.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/plan/README.md

@@ -82,6 +82,10 @@ Added after v0.9.19 replaced the per-branch settings with build definitions (202
 
 - [ ] `18-remove-branches-section.md` — delete the legacy `branches` section and its `autoBuild` schedule; run around 2026-09-05, after the precondition check in the step file
 
+Added after a silent 57-minute fetch outage on vm4006 (2026-08-30):
+
+- [ ] `19-watcher-health-in-ui.md` — show an unreachable origin in the web UI instead of only in the journal
+
 Added for running GitTally on Hostsharing Managed Webspaces (2026-08-10):
 
 - [ ] `17-bwrap-build-runtime.md` — GitTally on a Managed Webspace: bubblewrap user-namespace build sandbox with a prepared rootfs (precondition check first — see the step file), plus web access under a domain via the platform's Apache proxy and Let's Encrypt
@@ -94,3 +98,4 @@ Step 13 depends on 07, 11, and 12.
 Step 15 depends on 12 and 13 and revises the containerized-runtime sketch in `docs/bootstrapping.md` (ADR 0006 is written as part of the step; GraalVM native image was evaluated and rejected there).
 Step 17 depends on 11, 15, and 16, and starts with a hard precondition check on the target webspace (ADR 0007 is written as part of the step).
 Step 18 depends on nothing in code but on the watched repository having migrated — its precondition check is a hard gate, not a formality.
+Step 19 depends on nothing; `WatcherState` and `/api/watcher` already carry everything it needs to render.