With the destination page held loading forever, the rail shows the destination at once and never snaps back.
15 Oct 2026 · branch sidenav-rewrite · captured against propflow-stage · at af37e6d8d83+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.
The starting point. The Maintenance section's pages are not in the rail.
Asserted in the captured DOM — Dashboard · Maintenance · Tenants
Every request for the Maintenance page is held open and never answered, a worse case than any slow network. The rail shows Maintenance's pages the moment it is clicked and is still showing them four seconds later. The old rail dropped back to the main menu after about 1.3 seconds here, then jumped forward when the page landed.
Asserted in the captured DOM — Work Orders · Unit Turnovers
Gera's case. Maintenance, Work Orders and Dashboard are all held loading. The last click, "Back to Dashboard", wins at once: the rail is back on the main menu, and four seconds later it has not flipped back to Work Orders.
Asserted in the captured DOM — Tenants · Collections