Build a law firm's deadline calendar from trigger events with calendar and court-day counting, mail service and court holidays

# Build a law firm's deadline calendar from trigger events, counting rules, service by mail and court holidays Inputs: `events.csv` (event_id, matter_id, trigger_date, rule_id, service), `rules.json` (each rule's days, direction and counting method) and `court-holidays.json`. Everything is synthetic. `rules.json` and these rules are the record; where `docketing-note.txt` disagrees, the rules win. Rules: - A court day is a date that is not a Saturday, Sunday or court holiday. - calendar counting: start from the trigger date, don't count the trigger day, and count every day; the deadline is the last day counted. If that day is not a court day, move forward to the next court day for an after rule, and back to the previous court day for a before rule. - court_days counting: count only court days (never the trigger day), forward for after rules and backward for before rules; the deadline is the last court day counted. - service mail adds 3 calendar days to an after rule's deadline once it has been computed; if that lands on a day that is not a court day, move forward to the next court day. Service has no effect on before rules. - Each matter's next deadline is its earliest deadline on or after 2026-11-02 (ties: lowest event number); null if it has none. - Write `out/calendar.json`: `{"deadlines": {"<event_id>": "<YYYY-MM-DD>", ...}, "next_by_matter": {"<matter_id>": {"event_id": <id>, "date": "<YYYY-MM-DD>"} or null, ...}}`. ## 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.