Prospect detail — the newest 20 conversations first
Board row p11-page-leasing-prospects-id, part 3. Stage (anonymized mirror): the largest prospect paints 21 of its 169 threads, and a plain control loads the rest.
25 Sept 2026 · branch p11-prospect-first-chunk · captured against propflow-stage · at 9bc0b4df94
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 · Largest prospect: first chunk + the control
The page painted from the first chunk. Under the Clara summary card, the control names how many conversations the first chunk left out, from the loader's own total.
Asserted in the captured DOM — earlier conversations
2 · After "Show earlier": every thread, control gone
One click reads every thread through the same scoped detail read. The control disappears once the page holds them all.
Asserted in the captured DOM — Activity
3 · A 15-thread prospect (p99): whole on first paint, no control
99% of prospects have 20 threads or fewer. They load whole, and the control never renders.
Asserted in the captured DOM — Activity
What this does not show
The loading and failure states of the control are transient or need a forced error; the render test EarlierConversations.dom.test.tsx pins them (loading disabled, failure line with retry). Captured on stage, the anonymized mirror; a clean contact scan means no reachable email or phone, not that no name is shown.