ece69d576a
- App.razor: Change Routes from InteractiveWebAssemblyRenderMode to InteractiveServerRenderMode (admin requires Blazor Server, not WebAssembly) - Program.cs: Remove unnecessary AddInteractiveWebAssemblyRenderMode() and AddInteractiveWebAssemblyComponents() registrations - Program.cs: Remove broken TaxBaik.WasmClient reference from MapRazorComponents (actual project is TaxBaik.Web.Client) The 500 error was caused by conflicting render modes and a non-existent assembly reference. Admin pages now correctly use Blazor Server interactivity. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>