Flight Finder (Jumpseat)

Slot-by-slot composition table (component → ViewModel → data source) for this area: page-compositions.html#flight-finder

Implementation accuracy audit (2026-07-18, AB#2297): all 9 screens compared against the live Blazor pages — verdict matrix, discrepancy log FF-1…FF-17, and visual pairs in flight-finder-audit.html. Both headline findings are now resolved: the Airline Policies detail screen was built the same day (FF-2), and the static /jumpseat/details mock (FF-1) was replaced by the Figma inline-expand (D64) and, for tapped flight alerts, by a real detail screen (D66).

Screen not in the Figma set — Flight Details (2026-08-14, D66): /jumpseat/flight-detail exists in code but has no design node; the design expands results inline and has never covered a push-tap destination. It therefore invents no visual language — it composes the flight card-og master's own expanded variant (4713:19985) held permanently open (ExpandLocked), with only the screen chrome and a status-currency line around it. Reached today by a tapped flight alert; the results-card tap still expands inline.