Standalone MVN UI

Model Validation Notice service shell

This local app uses real HTTP calls against the MVN read service through a proxy layer. Consumer MVN pages only resolve when a valid short code is provided.

Seeded short codes are available for local development but are intentionally not linked from the consumer UI.

Preview deployment check: this landing page was updated so a fresh PR has an obvious MVN UI change to validate in Flightcontrol.

Development setup
  • The UI calls local `/api/mvn/...` endpoints instead of in-memory mocks
  • The PDF stream is served through the app using the attached sample file
  • Unknown short codes resolve to the invalid-link experience
  • Seeded short codes are kept out of the consumer UI
  • The landing page now includes a dedicated preview deployment marker