gnezim
37ae7dcd46
Mirrors Angular's CurrentScheduleService.getScheduleType + compareFlightsByPId: when the [-1, +1] route search returns the open flight (matched by carrier+number signature, including each leg of a connecting itinerary), keep only those instances; when no match exists, fall back to a 1-item list with just the open flight (Angular's 'default-schedule' branch). Old behaviour returned the full route search and dumped every unrelated MOW-MMK option into the rail. Add e2e regression that loads the SU 6188 + SU 6341 itinerary and asserts the rail shows only SU 6188 — not SU 6190 / SU 6699 (the other Sunday MOW-MMK options that used to appear).