Delivery unknown — after
Kept, recorded, and never resent until someone checks
5 Oct 2026 · branch p9-calendar-followup-delivery-unknown · captured against propflow-stage · at fedd5c1f814+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 · AFTER — delivery unknown, check before sending
The same lead, as this branch records it: the claim is kept (nothing resends), and the card says the link may have reached them and not to send it again until support confirms delivery. It does not point at the conversation: a provider error writes no conversation row, so a blank conversation proves nothing. No retry is offered. Before: main.
Asserted in the captured DOM — Evidence Deliveryunknown · couldn't confirm the application link reached them · until support confirms whether it was delivered. The lead and the notice (absent on main).
Sections 2–2
2 · PHONE — 390px
Same screen at phone width.
Asserted in the captured DOM — Evidence Deliveryunknown · couldn't confirm the application link reached them · until support confirms whether it was delivered. The lead and the notice (absent on main).
