Charge residents' parking permits by emission band, part year, household order and blue-badge exemption

# Charge a council's residents' parking permits for the rest of the scheme year Inputs: `permits.csv` (permit_id, household, reg, co2_gkm, fuel, start_date, cancelled_on, status), `charges.json`, `blue-badges.csv` (household) and `office-note.txt`. Amounts are in pounds. `charges.json` and these rules are the record; where the office note disagrees, the rules win. Rules: - Permits with status refused are ignored. Households match ignoring letter case and surrounding spaces; report them in upper case. - A car's band is the first band in charges.json whose max_co2 is at least co2_gkm (a car exactly on a limit stays in that band; max_co2 null is the top band). Electric cars are band "electric" and free. - Diesel cars add diesel_surcharge to the band's annual price. - A permit is charged annual price x days / days_in_year, counting days from start_date to cancelled_on (or scheme_year_end), both included. - In each household, non-electric permits are ordered by start_date (ties by the permit number); every permit after the first costs additional_permit_pct percent more. - A household in blue-badges.csv pays nothing for its first non-electric permit only. - Each permit's charge is rounded half-up to 0.01 at the end. Write `out/permits.json`: `{"band": {"<permit_id>": "<band>", ...}, "charge": {"<permit_id>": <charge>, ...}, "household_totals": {"<HOUSEHOLD>": <sum>, ...}, "total": <sum of charges>}` covering every permit that is not refused. ## 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.