Two companies picked: the tours page says so, by name

A two-company pick is refused by name — never an empty month — and the notice lists company names, not ids

24 Sept 2026 · branch fix/tours-two-company-refusal · captured against propflow-stage · at 67e5d16290

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

Stage data, with two synthetic fixture companies picked in the top-left switcher. The tours calendar answers for one company at a time, so the page makes no read. It says so, and it names the two companies so the next step is obvious. Before this PR, the empty read rendered No tours this month over companies that do have tours. The notice now reads the workspace's company-name map, so it lists names (it used to show raw org_… ids). That also fixes the same notice on /calendar and the Settings team card.

Asserted in the captured DOM — answers for one organization at a time · Fixture Property Co · Resident Check Co. The refusal, and both companies by name — no raw id, and no 'No tours this month'.

Two companies picked

Tests that pin the same

leasing-tours-route.test.ts (API 400 needs_one_org, loader never called), calendar-pages-read-only-the-selection.test.ts (the island is handed the companies and nothing is read from tour-calendar-index or TOUR#), TourCalendarClient.window.test.tsx (the notice, never an empty month), and NeedsOneOrgNotice.names.dom.test.tsx (company names, not ids). Each is red on the code before the fix.

PropFlow Docs