TransitGap — supplied timetable scenarios
{"active_trip_count":2,"connection_count":1,"delay_scenario_count":3,"evaluated_case_count":3,"feasible_case_count":2,"infeasible_case_count":1,"input_trip_count":2,"scope":"scheduled_interchange_scenarios_v1","service_date":"2026-09-08"}

User-supplied delay scenarios are assumptions, not predictions or observed reliability.
Outbound departure stays on schedule. Walking time is supplied, not measured or routed.
Same service-day timetable seconds only; no cross-service-date search, timezone/DST elapsed-time model, route planning, capacity, guarantees, or GTFS compliance certification.
A zero-second margin counts as mathematically feasible and supplies no boarding buffer.

Equation: slack = outbound departure - inbound arrival - assumed inbound delay - supplied walk.
{"connection_id":"connection-1","delay_seconds":0,"scheduled_feasible":true,"slack_seconds":180}
{"connection_id":"connection-1","delay_seconds":120,"scheduled_feasible":true,"slack_seconds":60}
{"connection_id":"connection-1","delay_seconds":240,"scheduled_feasible":false,"slack_seconds":-60}
