Bill a farm's veg box subscribers with inclusive pauses, a mid-month price rise and credit claims to validate

# Bill a farm's veg box subscribers for November 2026 Inputs: `subscribers.csv` (sub_id, box, weekday, start_date), `pauses.csv`, `prices.csv`, `credits.csv` (claims for missing items), `delivery.json` and `newsletter.txt`. Every amount is in pounds. The data files and these rules are the record; where the newsletter disagrees with them, the rules win. Rules: - Each subscriber gets one box on every date in November 2026 that falls on their weekday and is on or after their start_date. - A pause covers every date from its from date to its to date, both included; no box is delivered on a paused date. - Each delivery is charged at the prices.csv row for that box with the latest effective_from on or before the delivery date; small boxes also pay small_box_fee per delivery. - A credit claim counts only if its date is a date that subscriber actually received a box. - Due = charges - credits. Write `out/boxes.json`: `{"deliveries": {"<sub_id>": <count>, ...}, "charges": {...}, "credits": {...}, "due": {...}, "grand_total": <sum of due>}` with every subscriber in each map (0 where nothing applies). ## 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.