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. Five prospect records at Camellia and Barcelona are split from their own conversations, and one Camellia-company tenant record sits under two people. Should we fix the two save paths so they always land on the same person first, then merge the six existing records, or just merge the six records now?

The full question, as raised

spine-health nightly red (1 duplicate occupancy, 5 split prospect↔conversation persons; 3 of them stuck since ~Oct 13, 2 new on Oct 27). Splits are sentinel-vs-sentinel: when a contact has no usable anchor (international caller phone failing normalizePhoneE164 at Camellia; a Zillow relay address at Barcelona) the conversation stamp keys a session-claim Person on the raw contact (conversation-spine-stamp.ts planDispatch) while the prospect stamp mints a separate prospect:<id> sentinel (_spineStampProspect, 4 copies: src/lib/data/dynamo/leasing.ts:604, src/lib/data/store.ts:4326, agents/clara mirrors). Barcelona order is prospect-first (:46) then conversation (:47), so adopting in one writer alone misses one ordering; d181a905 is a separate mechanism (prospect bonded to a backfilled guest-card person; the guest-card link the conversation-stamp comment defers). Dup occupancy tenant_2888880e: a status=former primary row left on the old person after a 2026-09-29 primary/co-tenant swap at appfolio-392 (only one active). merge-split-prospect-persons.ts gates on a bogus email:<phone> claim so it won't heal these; dedup-occupancy-rows.ts exists for the occupancy. Heals are prod identity merges (human go required).

Fix both save paths first, then merge the sixthe raiser's pick Merge the six records now, fix later I'm not sure — go find out Take it to the engineering bridge

Why, and what was tried

The session raising this recommends: Fix both save paths first, then merge the six
Two new splits appeared on Oct 27, so merging without the fix just refills the list; the fix is an identity write path, so it needs a reviewed PR, not an unattended one.
Tried first, unsuccessfully: Pulled last night's record ids, read all 5 prospects, their 3 conversation persons and the 2 occupancy persons in prod; traced both writers' no-anchor fallbacks; checked the existing healer (wrong shape) and harness-prod-write (no merge op); caller is not a registered test line.

022e2c86 is parked on this.

Pick an option above, then press Done.