Check airline crew rosters against duty, rest, rolling-window and consecutive-day limits

# Check crew rosters against duty-time limits Inputs: `crew.csv` (crew id and home-base time zone), `duties.csv` (duty periods in UTC, merged from the roster system and a second import). Rules: - The second import repeats some duties under a differently formatted id ("D-00123" vs "D00123"). Duties with the same crew, report time and release time are one duty. Report duty ids as "D" followed by the digits only, e.g. "D00123". - long_duty: duties longer than 13 hours (exactly 13:00 is allowed). - short_rest: duties whose rest since the same crew member's previous release is less than 10 hours (exactly 10:00 is allowed). List the later duty. - over_60h_168h: crew members who have more than 60 hours of duty inside any rolling 168-hour window (any start time, not calendar weeks). Duty time is counted only where it overlaps the window. - seven_day_runs: crew members who report for duty on 7 or more consecutive calendar dates, using the local date of each report time in the crew member's home-base time zone. - Every list is sorted. Write `out/limits.json`: `{"long_duty": [...], "short_rest": [...], "over_60h_168h": [...], "seven_day_runs": [...]}`. ## 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.