FTDT — Flight Time / Duty Time
Implementation roadmap for migrating remaining FTDT screens from XAML to the Figma Blazor design. Phase task tracking, open questions (OQ-1–OQ-6), and CA monolith decomposition strategy (RenderFragment shell pattern). WI-1908.
Data-source mapping for all 8 FTDT screens. Confirms backend and client-calc coverage is complete. No backend gaps. Presentation backlog: Duty Period Card, progress bars, Master Form Field, toggle-settings.
Screens & Integration
Per-app-screen tracker of which components and domain controls have been mapped from the Figma mockups, with an embedded node registry. We work one screen section at a time.
Every Blazor Hybrid route classified by whether the screen itself traces to a captured Figma frame — not just its components. Found after MEC Events turned out to be a "sensible scaffold" with no design source at all. Live-verified via Figma MCP, then traced to root cause: all 7 confirmed gaps + 1 diverged screen turn out to be legacy XAML pages the migration guide scoped as straight ports, never commissioned for a UI-Refresh redesign — not documentation oversights. 1 route (Documents) remains genuinely unresolved.
Maps every control hand-rolled during the AB#1821 Blazor scaffold (PR #1664, 28 pages) to its existing component spec — the "consume-don't-rebuild" list for the #2087 build — and lists the 4 genuinely new controls the library still lacks (Status Badge, Empty State, Saved Item Card, Sort/Filter Bar).
Readiness map for aligning the Blazor home page with this component library — the WidgetType → component / domain-control mapping, including the SingleButtonLarge reclassification and D39 ItemDto rename.
Per-airline branded experiences — color, typography, and component overrides for UAL, FDX, and DAL. Developer onboarding stubs with confirmed Figma nodes, palette tables, font specs, and open design questions. Token delivery: GET /api/theme/{mecId}.