ba981e7332
TaxBaik CI/CD / build-and-deploy (push) Successful in 2m17s
Problem: Mixed WebAssembly (App) and Server (Login) render modes caused interaction breakage after login. Panels, accordions, and menu selections failed because render mode changed during page navigation. Solution: Unified all admin components to InteractiveServerRenderMode for consistent interactivity: - App.razor: Routes and HeadOutlet use InteractiveServerRenderMode - Login.razor: Already uses InteractiveServerRenderMode - Program.cs: Removed WebAssembly component registration Updated validation script to require Server mode instead of WebAssembly for admin shell. This ensures: ✅ Consistent render mode throughout admin UI ✅ Reliable component interactivity (panels, accordions, menus) ✅ Stable page navigation and state management Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>