PR 11767 · the conversations list says when it stops at the newest 2,500
Staff looking at every company read the newest 2,500 conversations off the recency index, and the list used to end there silently. It now says so, and says how to see the rest.
24 Sept 2026 · branch detached · captured against propflow-stage · at f0de6b7398
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 · Staff, every company: the cap is named under the list
Captured as the smoke user (platform staff) with no company picked, the one shape that reads the capped recency walk (getConversationsMeta(undefined, { limit: ALL_PROPERTIES_RECENCY_CAP })). Stage holds more than 2,500 conversations, like production (about 3,833 there), so the walk comes back full and the route answers recencyCapped: true. The list then shows the sentence below instead of ending with no explanation.
A company pick reads that company's index with a cursor and shows no such line, because it is not capped. This capture is from the stage table (anonymized by construction), on origin/main with #11767 merged.
Asserted in the captured DOM — Showing the newest 2,500 conversations across every company. Pick a company to see all of its conversations.. The exact RECENCY_CAP_NOTE string from ConversationsLog.tsx, asserted in the captured DOM. The route half (recencyCapped set only on a full walk, never on a walk one short of the cap) is pinned by route.recency-cap.test.ts.
