Everything I could decide myself is decided. What's left needs you. Each one carries the recommendation of the session that raised it — if you agree, pick it and press Done. A model's opinion, where there is one, appears on the card as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me. You don't need to open the session — pressing Done sends your answer back and it picks up.
org_jpco (Camellia Apartments), AppFolio guest card 158, ProspectInquiry 7a536e04-abeb-58f5-9b03-10bc1225ed0c, personId pers_19dffcd8-b515-4950-829f-edae2673e836. lead.received outbox row (eventId 4f42e87b-557b-4652-a489-a92daa08da83) exhausted MAX_ATTEMPTS(5)/~32min waiting for the AppFolio createdBy L4 read (guest-card.ts readCardCreatedBy) to resolve — it never did, so clara-first-email-consumer.ts parked the row honestly rather than send blind (Sentry JAVASCRIPT-NEXTJS-1CA). Same org/property already parked once before (JAVASCRIPT-NEXTJS-1BK, 2026-09-26) and the identical shape has recurred at Western Slope 3x in the last 4 days (JAVASCRIPT-NEXTJS-1B5/1C1/1C8) despite several prior rounds of fixes to this exact race — this looks like an ongoing, not-fully-closed issue worth a systemic look, separate from this one lead. Unusual wrinkle: this applicant's rental application (AppFolio id 120) was already approved (pmsApplicationStatus=Approved, stage=approved) within ~2 minutes of the guest card being created — well before the outbox row even started retrying. Recovery path is POST /api/admin/lead-outbox/redrive (staff-admin auth only, not something I can call myself) which would re-run the consumer and, if createdBy has since resolved, send Clara's generic new-lead first-touch email to someone who already applied and was approved. I could not confirm Camellia has a leasing-activity Slack channel configured, so this Sentry alert may be the only place this surfaced.
fe4e48e4 is parked on this.