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. Six leads are showing up as two separate people each (the lead record on one person, its conversation on a throwaway second person), and three of those appeared this week at two companies. Should I fix the step that attaches a conversation to a lead so both always share one person, and then merge the six pairs plus one duplicated resident record after showing you a dry run?

The full question, as raised

spine-health red: 6 split prospect<->conversation persons (Camellia x3 voice/foreign-number 9-23..9-29; Situs x2 Zillow relay email 10-27; appfolio-399 x1 voice conv: sentinel 10-28) + 1 duplicate occupancy (tenant_2888880e, constant since 10-19). Common cause: the inquiry writer and the conversation writer each mint their own anonymous sentinel Person (prospect:<id> vs relay-session / conv:<id> / anonymous-phone) and nothing reconciles them when the inquiry is pinned to the conversation (conversation-manager.ts ~5757 and voice personalization route ~2409 build the conversation without the resolved prospect personId; outbound-log.ts ~736 re-pins without a Person check). merge-split-prospect-persons.ts only heals the old email:<phone> shape, so these 6 would be skipped as REVIEW. Proposal: (1) one fix at the pin/birth seam so a conversation born for or pinned to an inquiry takes the inquiry's Person, with a test that drives the real birth path and asserts the split detector returns []; (2) extend the healer to fold sentinel-only conversation Persons into the inquiry Person; (3) apply on propflow-prod only after a dry run you approve.

Fix it and heal the records after a dry runthe raiser's pick Fix the writer only, leave the old records I'm not sure — go find out Take it to the engineering bridge

Why, and what was tried

The session raising this recommends: Fix it and heal the records after a dry run
The alert stays red until the old pairs are merged, and the writer gap is still creating new ones (3 in 48h).
Tried first, unsuccessfully: Ran the live check against propflow-prod and read all 12 person partitions; confirmed the relay guard worked (session claims, not email claims); traced the email-lead and voice birth paths on origin/main; checked harness-prod-write list (no heal op) and the existing healer's safety filter (old shape only). Prior fixes #21107/#20435/#20737/#5602/#6131 all narrowed the detector; none touched the writer or healed rows.

ed745c65 is parked on this.

Pick an option above, then press Done.