A capped notice search says so
Board row p11-page-admin-core (C6). The Conversations list's system-notice feed now says when the notice search stopped at its scan cap, instead of reading as "no notices".
28 Sept 2026 · branch p11-conversations-sender-cap-note · captured against propflow-stage · at 74bc818556+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 · Notices on screen, search stopped at its cap: the list says so
On stage the notice search (?sender=appfolio) stops at its 4,000-row scan cap with rows unread — measured read-only: 2 notices found, capped=true. With the system-notice feed revealed, the line under the heading says the search stopped early, so the two notices shown are not mistaken for all of them.
Asserted in the captured DOM — Search stopped early — older email from this sender may exist.. The note is on screen, word for word.
2 · Notices hidden (the default): no line
By default the system-notice feed is hidden, so a capped notice search says nothing about it — the note appears only while the notices it describes are visible.
Asserted in the captured DOM — Conversations. The list rendered; the note is absent (checked by the DOM test, not asserted here).
