- Shipped
- August 27, 2026 at 8:56 AM UTC
- Author
- kamo
- Commit
- f929176
Two of these shipped before anyone noticed, and the guard found two more in the newest panel the moment it ran — failing to load what a patient's other practices have already sent read as "nothing received yet", and failing to load the partner list read as "no exchange partners are set up", which would send somebody to add partners that already exist. That is why this is a build guard and not a review note. The failure is silent by construction: no error, no log, nothing on screen, and it looks exactly like the healthy empty state. Nobody will ever report it as a bug. On a chart an empty list is a statement — "no measurements", "nobody overdue", "no allergies" — and people act on it. The same distinction already runs through the module on the server side: "they have nothing" versus "we could not ask", and 503 rather than an empty list from the exchange transport. This enforces it on the client. Scoped to the clinical surfaces, because other verticals have their own conventions. A catch that sets an error, logs, rethrows, returns, or reloads passes — and so does one carrying a comment explaining why the silence is right, which PatientCommsPanel relies on: its sibling timeline reports the same outage and a second banner would tell the reader nothing new. Chained into npm test.