Pay holiday-let owners for a month with stays crossing the month end, platform commission, cleaning charges and a capped tourist tax

# Pay holiday-let owners for October 2026 Inputs: `bookings.csv` (every booking touching October 2026 across the agency's properties, from a direct-booking site or a listing platform), `properties.json` (property -> owner) and `rules.json`. Owner statement rules: - Cancelled bookings are ignored. - Only nights in October 2026 count: a stay that crosses into or out of October pays the owner for its October nights only (a night belongs to the date you sleep there; the check-out date is not a night). - Room revenue = October nights x `nightly_rate`. Platform bookings lose `platform_commission_pct` of their room revenue; direct bookings don't. - Management fee = `management_fee_pct` of room revenue after platform commission. - Cleaning: the owner pays `cleaning_fee` for each stay that checks out in October. - Tourist tax is collected from guests for the council and is not owner income: `tourist_tax_per_adult_night` per adult per night, for at most the first `tourist_tax_max_nights` nights of a stay (counted from check-in); report the October nights' tax per property. - Payout = room revenue after commission - management fee - cleaning, rounded half-up to the cent per property. Tourist tax is rounded the same way. Write `out/payouts.json`: `{"payout": {"<property>": <payout>, ...}, "tourist_tax": {"<property>": <tax>, ...}, "total_payout": <sum of rounded payouts>}` for every property in `properties.json`. ## 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.