41013dcab3
Found during the live acceptance run. The host calls UseStaticWebAssets only when the environment is literally "Development", so running the build output under any other name - checking a staging registry locally, say - leaves the Theme RCL's assets under _content/ unresolvable. The failure is silent and unhelpful: the page returns 200 with its markup fully present and renders as a blank white screen, because every stylesheet 404s. Calling it unconditionally is a no-op once published (the manifest is gone and the assets are real files on disk), so the only thing it changes is that failure. The container was never affected. Phase 4 results recorded in the ledger: 7 of 9 design section 9 checks fully pass, 2 pass for ScadaBridge and are blocked for OtOpcUa pending a rig redeploy. Notable live evidence: - Leader chip moved from site-c-a to site-c-b when site-c-a was stopped, and the split-brain chip appeared while the pair was self-formed then cleared once it genuinely joined. - Kill to Unreachable took two failing sweeps (the damping working as designed); recovery landed on the first good poll. - Five consecutive page loads in 0.00-0.02s all showed the same "last sweep" timestamp, which is cache-first stated as a measurement. - Freezing the probed endpoints while auto-refresh stayed RUNNING froze the poller mid-sweep and the cards aged into STALE on their own - staleness is computed at render, so a stuck poller needs no explicit stall detection. The run also surfaced a pre-existing rig defect in both products: self-first Akka seed lists mean a pair booted cold self-forms two 1-member clusters that never join. After a --force-recreate every ScadaBridge node named ITSELF leader and every node answered /health/active 200; restarting ONE node of each pair converged them to one Leader plus one Active plus one Standby. That is the user's own open backlog item (docs/plans/2026-07-22-initjoin-selfform-fallback.md, unexecuted), and the dashboard made it visible fleet-wide in one screen. 170 tests, 0 warnings.