PR #12932 — one building picked, the loading table drops Property

Before/after of /leasing/prospects with a single building picked. Board row p11-x-skeleton-everywhere, single-building part 1.

What	Loading screen, before	Loading screen, after	Loaded page	Verdict
Columns with one building picked	7: Prospect, Property, Stage, Source, Clara, Created, Last Activity	6: Prospect, Stage, Source, Clara, Created, Last Activity	6: Prospect, Stage, Source, Clara, Created, Last Activity	✓ same columns

Screenshots, notes, and how they were captured

Prospects loading screen, one building picked — before (origin/main)

Prospects loading screen, one building picked — after (#12932)

Prospects loaded page, one building picked

The building was picked the way a person picks it (the building-picker cookie plus the company in the address), and the loading screen read it through the same provider the page reads, which the workspace layout seeds from the validated pick. Row height (33px here) is #12886's, not this PR's. Tenants, Conversations and Turnovers follow in their own parts.

How these were captured. Local dev server bound to the propflow-stage table (anonymized by construction), signed in as the smoke login, desktop 1440×900, on 2026-09-28. The loading screen shots hold the page's server render with an uncommitted local hook (a cookie-gated 45 s wait in each list's page.tsx) so the route's loading.tsx stays on screen. That hook is NOT in any PR. Heights are read from the rendered DOM (getBoundingClientRect), not estimated. Before = origin/main; after = the PR's branch.