What problem does it solve? Migrating a legacy Blazor Server application to the modern Blazor Web App model involves many coordinated changes across the project file, Program.cs, _Host.cshtml, and App.razor, and missing any step causes broken rendering, failed form posts, or lost circuit configuration. ## Core Features & Use Cases - Step-by-step migration workflow: Converts AddServerSideBlazor/MapBlazorHub to AddRazorComponents/MapRazorComponents, transforms _Host.cshtml into an App.razor root component, and moves the Router into Routes.razor. - Authentication and middleware handling: Replaces the CascadingAuthenticationState component wrapper with the AddCascadingAuthenticationState service and adds the required UseAntiforgery middleware. - Validation checklist and pitfalls: Verifies no legacy APIs remain (blazor.server.js, MapFallbackToPage, _Host.cshtml) and documents common failures like missing antiforgery middleware or incorrect prerendering behavior. - Use Case: You have a .NET 7 Blazor Server app using Pages/_Host.cshtml and want to upgrade to .NET 8 with InteractiveServer render mode while preserving existing interactive behavior. ## Quick Start Ask the agent to convert this Blazor Server project to a .NET 8 Blazor Web App using InteractiveServer render mode.