Dashboard split view — a building whose read failed says it could not load
A failed per-building read is named as failed, not drawn as a blank line
28 Sept 2026 · branch dashboard-split-names-a-failed-building · captured against propflow-stage · at ad713e8940
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · One building's read fails — it is off the plot and says it could not load
The second building's per-building history request is aborted in this browser. In the split view that building is left off the plot, its legend entry reads couldn't load, and the drill-down table lists only the building that loaded, with no "—" rows for the one that did not. The other building draws normally.
Asserted in the captured DOM — couldn't load · OCCUPANCY
2 · Control — the same split with every read allowed
Nothing blocked: both buildings are plotted and no legend entry says it could not load.
Asserted in the captured DOM — OCCUPANCY · DATE · PROPERTY
