API & Backend
The three-level server-driven feed contract: PageDto → ContainerDto[] → ItemDto[]. Defines all container and item type discriminators, the client-side mapping chain, and a full home-page example payload. The spec the backend team needs before building the endpoint.
Per-MEC token map delivered at login — resolves BackgroundToken and other semantic token names to their final color values for the active MEC. Covers HTTP contract, client hydration, caching, and error-handling fallback strategy.
The third leg of the dynamic-UI contracts: maps each component's data source to real content via the MobileContent API and its two content types — MenuItem (navigation: card-sm, ButtonCard, TextCard) and DocumentItem (content: card-lg/HeroCard, Carousel). The last piece binding a data source to a component in the dynamic-feed response. Kept separate, never merged (backend-api-mapping §2).
How MenuItem.Path drives real navigation through the INavigationService abstraction (the current standard — not Shell.Current.GoToAsync directly, which is a legacy pattern being phased out under WI-2081/WI-2085), the native Shell route table, the Path-as-URI query-property convention, glyph propagation into destination pages, and how this differs from Blazor @page routing.
App-wide component data requirements, API gaps (including pilot rank), and model extension recommendations sourced from Figma. Part 1 is the app-wide ask; Part 2 is the Home deep dive. For the backend engineering team.