Two companies picked: the conversations list says so by name
p11-x-combine-companies — the list's refusal, not an error over an empty table
24 Sept 2026 · branch fix/conversations-list-two-company-notice · captured against propflow-stage · at ab21baa7f6
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 · /conversations with two companies picked
Fixture Property Co plus Fairhaven Residential (TEST) ticked in the company switcher, then Done. The list route answers for one company at a time. The page names both companies in place of the table: no red toast, no No conversations found.
Asserted in the captured DOM — Conversations answers for one organization at a time. · Fixture Property Co · Fairhaven Residential (TEST). The by-name notice is on screen.
What this checks
Stage data (anonymized), smoke user (staff), branch dev server. Branched off origin/main, so the grading-flags notice from #11867 is not on this branch. The absence of the red toast and of the empty table is asserted in ConversationsLog.two-company-refusal.test.tsx, which fails on main.