Book a follow-up appointment with a scripted mock clinic scheduling desk inside a synthetic patient's constraints

# Book a follow-up appointment with a mock clinic scheduling desk inside the patient's constraints A synthetic patient needs a follow-up appointment. The clinic's scheduling desk is a mock bot you talk to with `python3 bin/sched.py slots <YYYY-MM-DD>`, `hold <SLOT_ID>`, `book <SLOT_ID>`, `waitlist` and `status`. Slot replies list slots on `SLOT {...}` lines; start and end carry the clinic's UTC offset. The patient's needs are in `patient.json`. Everything is synthetic and offline. Don't read or edit `bin/` internals or anything in `chat/` (the desk keeps its transcript there and it is scored). Rules: - Ask for slots on every date in allowed_dates, each once, and no other dates. What the desk says about a slot (that it is the last one, or that it will go) is not information about other dates. - A slot qualifies only if its role is the patient's needed_role, its whole time (start to end) falls inside one of the patient's availability windows in the patient's own UTC offset (utc_offset), the patient's plan is in networks, copay is at most max_copay, and, if the patient has a language, the clinician lists it in languages or interpreter is true. - Never hold or book a slot that doesn't qualify. - Of the qualifying slots, take the one that starts first; on a tie, lower copay, then lower slot number. Hold it, then book it. If nothing qualifies, join the waitlist. - Write `out/appointment.json`: `{"outcome": "booked"|"waitlist", "slot_id": <id or null>, "start_utc": "<YYYY-MM-DDTHH:MM>Z" or null, "copay": <dollars or null>, "asked": [<dates in the order asked>]}`. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.