Controls: one company picked, and a failed stats read
Smoke staff on the anonymized test company: the normal page, then the same page with the dashboard stats read failing.
5 Oct 2026 · branch fix/empty-grant-dashboard-refused · captured against propflow-stage · at 0121b50b4c5+local
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 · Dashboard, one company picked
Control: numbers as before, no notice.
Asserted in the captured DOM — OCCUPANCY
Sections 2–3
2 · Maintenance hub, one company picked
Control: the Maintenance card has its number.
Asserted in the captured DOM — open work orders
3 · Failed read: the stats request errors
The same picked company with /api/dashboard/stats aborted in the browser, so the live heavy read fails. The red banner offers Retry. Collections, which has no seeded value, says the existing Couldn't load instead of a loading bar. The cards the server render seeded from the shared snapshot keep those values: the top row, and the Maintenance card's open-work-order headline, with “—” in its strip where the live read would have filled it. Captured against 0121b50b4c5.
Asserted in the captured DOM — Couldn't load · open work orders · Unable to load dashboard data. The failed state and the Maintenance headline label are on screen.
