CTO — Bugfix Task: Appointment detection priority (Saturday / morning case) We’ve just tested a real renewal conversation and found that the URE is not treating clear appointment intent correctly. Conversation example (conv_id: 48d710fa-d45b-4552-93e0-eff71f60c7eb): LIA opener (EOT_12_USED): “Would you have time to pop in one day soon so we can look at your options together?” Customer: “Hi I could do Saturday ?” LIA response: template_key = "T1_GENERAL" mode = "T1_GENERAL" asks again “What day is usually easiest for you to pop in?” Customer: “How about in the morning ?” LIA response: template_key = "SMALL_TALK" mode = "SMALL_TALK" again “What day normally works best for you to pop in?” Expected behaviour (from the LIA brief): Messages containing a day word (monday…sunday, tomorrow, this weekend, next week) in the context of visiting should be treated as T3_APPOINTMENT (vague day). Messages containing only time-of-day words (morning, afternoon, evening) in reply to “what day/time works” should go into the “vague time” appointment branch, not SMALL_TALK. Please implement: In app/lia_ure.py, ensure there is a dedicated detection step for appointment intent: e.g. is_appointment_intent(message_text) and/or detect_day_from_text(...), detect_time_of_day(...). Change the classification / branch order so that: Appointment checks run before T1_GENERAL and SMALL_TALK. For a message like “I could do Saturday ?” after an invite, we end up with: tier = T3_APPOINTMENT last_reply_type = "APPOINTMENT_VAGUE_DAY" (or similar) For “How about in the morning ?” we either: if day is already stored in state → confirm day + morning slot options, or if no day is stored → treat as vague time, ask “which day in the morning works best?”. Add explicit tests for these strings in the URE tests: "Hi I could do Saturday ?" → classified as T3_APPOINTMENT, response offering two time slots on Saturday. "How about in the morning ?" following that → either confirm or ask for a day, but must NOT fall into T1_GENERAL or SMALL_TALK. Re-run tests and confirm that for conv 48d710fa-... the next inbound “Saturday” style message would now hit the appointment branch.