debug-broken-ui

# The app is broken and the code looks fine Reading the source again will not tell you why. The evidence is in the running app, and most of it never reaches the screen: the request that failed, the store that never moved, the handler that was never bound, the element covered by something invisible. **Reticle** reads all of it from inside the page. Not installed? `RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init`, then the [`install-and-verify`](https://github.com/reticlehq/reticle/blob/main/skills/install-and-verify/SKILL.md) skill. ## Do not start by guessing. Start by reproducing. ``` reticle_snapshot({ sessionId, mode: "interactive" }) // controls only, with refs reticle_act_and_wait({ sessionId, ref, action: "click", until: { kind: "element", query: { testid: "..." } } }) ``` The verdict already narrows it: `no` / `contradicted` means a channel saw something incompatible with the UI — you have the bug. `unknown` means Reticle drove it and could not tell, which is a different investigation from "it failed". **Read the act result before you call anything else.** Its `summary` block already carries the whole causal window of that one click: `net {total, errors, headline}`, `consoleErrors`, `stateDiffs [{path, from, to}]`, `storageDiffs [{key, from, to}]`, `route`, `signals`, `layoutShift`, `longTasks` — real before→after diffs, not counts. The console, network, storage and state calls below are for going DEEPER into something the summary already poi...