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.
1Guest card 2782 (Western Slope, prospect 'Barbara') carries two AppFolio inquiry rows (6177, 5909); propflowai's own stored inquiry pointer for this person (5908) matches NEITHER live row. The just-merged fix (propflowai#11267 / appfolio-browser-agent#422, both live in prod today) made the robot refuse to guess and park the assign with a clear reason instead of silently retrying forever — but explicitly left 'which inquiry should a multi-row card's assign target' as an open product call, not an engineering default. This Sentry alert (JAVASCRIPT-NEXTJS-1AX) is that park firing for real, for the first time, on this exact card. Card 2782 is still unassigned in AppFolio (confirmed read-only).
In plain terms. One guest card at Western Slope has two inquiries on file — an old one and the current one — and Clara doesn't know which one to assign herself to, so should she guess the current one automatically, or should every card like this wait for a person to pick?
The session raising this recommends: Keep parking every multi-inquiry card for a human to pick by hand That's the choice already made and shipped today (#11267) — the robot refuses to guess on purpose since an old/inactive inquiry can carry a different prior assignee, and auto-picking risks reactivating or misassigning a customer's card. The stale pointer (5908 matching neither live row) is a separate data question worth fixing, but doesn't change which option is safer. Tried first, unsuccessfully: Checked blocked outstanding for an existing block on this — none found. Read the full #11267 commit history (both commits) and confirmed it explicitly deferred this exact decision to Fede. Confirmed via GitHub the fix is merged and live, and via a prior read-only AppFolio check in the PR body that card 2782 is still unassigned, so nothing has misfired yet. Tried to read propflowai's own ProspectInquiry mirror row for this person directly (smith-db) to see why our pointer (5908) doesn't match either live row (6177, 5909), but couldn't resolve the right partition-key shape in the time budget for this alert — flagging as a loose end, not resolved.