Prospects — a two-company pick lists both companies
The leads list answers a company pick one leg per company instead of refusing it (p11-x-combine-companies).
25 Sept 2026 · branch p11-x-prospects-combine · captured against propflow-stage · at f143b7d661+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 · Two companies picked: both companies' leads, one list
Before this PR the list answered a two-company pick with "Leads answer for one company at a time" and no rows. Now each company is read in its own partition and the rows are listed together. The Tours sub-line and the funnel's occupancy figures come from the separate stats read, which does not answer a company pick yet; they sit in their unknown state rather than showing the previously selected company's numbers (the round-1 fix). The rows are stage data (anonymized by construction, ADR-0097/0110): the test company and a mirrored building, together in one list.
Asserted in the captured DOM — Inquiries · Tours · Applications. The funnel strip rendered over a list that answered, not the one-company refusal.
What is not photographed, and why
The org_not_answerable empty state is not reachable by either evidence identity: the smoke login is platform staff (never refused), and the seeded customer admin holds one company, so the selection drops any other company before the route sees it. That state is pinned instead by ProspectsClient.tours-label.test.tsx (the server's sentence is shown and the rows are cleared) and by the page seed test page.company-pick-seed.test.ts.