I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. What should happen with a prospect's tour that's booked on the wrong rental house? A prospect asked about one house, then switched to a different one over email, but the Friday tour stayed booked on the house she asked about first. That first house has no apartment record, so AppFolio can't log the showing. — The mini fixes the booking before Friday. (recommended) — Leasing staff sort it out by hand. — Route it to the cross-team channel. One wrinkle: the file that would route this to the leasing team automatically is missing, so that didn't happen on its own.

The full question, as raised

Sentry JAVASCRIPT-NEXTJS-1HE (issue 7792376119): schedule_showing intent gc:schedule_showing:034bc64c-2308-4c11-8765-5b6e9ccac338:d2a047a0-c735-4f30-9279-af270b22f841 parked with parkReason=no_home. Intent payload.propertyId=appfolio-172 ("2980 Emerald Circle", org org_c42d9150-b9ad-46f8-8f5f-b0fe56bacf38), no unitId. Tour d2a047a0-... has unitId="" and unitNumber="". Inquiry 034bc64c-... targetUnitId=""; aiNotes show the prospect pivoted from 2980 Emerald Circle (unavailable) to 2841 Morningside Court, and the tour was confirmed Fri Oct 16 3:30-4:00 PM via email_state_machine still filed under the original property. No refile occurred: front-door-unit-home.ts's refile logic only covers portfolio/front-door leads with no property yet, not an inquiry already filed on one single-family property that then switches to a different one. The park already triggered both the engineering alert and (per code) a notifyShowingNotRecorded staff notice, per guest-card-outbox-drain.ts's #17401 design. A fix exists (guest-card-outbox-correct-target.ts's correctFailedShowingTarget + redrive) but needs the correct AppFolio property/unit for 2841 Morningside Court confirmed first, and is a prod-data write gated by the 2026-10-05 rule requiring a human's direct, same-step approval; this is also an unattended decider run, which never runs that class of write regardless of approval. Separately: ~/.claude/LANES.md (the bridge_handoff lane map) does not exist on this box, so classify() returns "unknown" and automatic handoff routing to the leasing/Western-Slope owner is unavailable right now — worth a fix on its own.

The mini fixes the booking before Friday.the raiser's pick Leasing staff sort it out by hand. Route it to the cross-team channel. I'm not sure — go find out Take it to the engineering bridge

Why, and what was tried

The session raising this recommends: The mini fixes the booking before Friday.
A retarget-and-redrive tool already exists for a parked showing; it only needs the correct house confirmed, which is a leasing call on live customer data, not the mini's to assume.
Tried first, unsuccessfully: Pulled the Sentry issue + latest event (count=1, firstSeen=lastSeen=now) and, via smith-db against propflow-prod, the parked PmsWriteIntent row, the Tour row, and the ProspectInquiry row. Confirmed the tour and inquiry both carry an empty unit id, and the inquiry's own notes show the prospect switched houses mid-conversation. Read guest-card-outbox-drain.ts and front-door-unit-home.ts to see why no refile happened. Ran `blocked outstanding` for a matching open decision to adopt — none found. Checked for the lane-routing file to hand this to leasing automatically — it does not exist on this box.

b9222e75 is parked on this.

Pick an option above, then press Done.