Leasing — a refused funnel drill-down says why, with no retry
p11-page-leasing C6: a refusal is not a failure, so it does not offer 'tap to retry'.
26 Sept 2026 · branch p11-leasing-funnel-refusal · captured against propflow-stage · at e20e817e64+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 · The answered drill-down is unchanged
One company picked, the Leasing pipeline card expanded and its Signed leases stage opened (the smallest stage, so the whole list fits). This is the path the change must not disturb: an answered list still renders its rows, and no refusal sentence appears on it. Stage data (anonymized by construction, ADR-0097/0110).
Asserted in the captured DOM — Signed leases · Prospects. The expanded funnel and its opened stage rendered.
What is not photographed, and why
The refused state is not reachable by either evidence identity. The smoke login is platform staff, who are never refused, and the seeded customer admin holds one company, so the selection drops any other company before the route sees it (the same limit #12172 and #12237 recorded). It is pinned instead by FunnelView.refused-drilldown.test.tsx, which renders the real component against a 400 org_not_answerable and a 403 and asserts the plain-English sentence with no retry button. Two of its four cases fail on origin/main; the two controls (a 500 and a non-refusal 400 keep their retry) pass on both.