AdminLoginForm's submit button had disabled hardcoded as static markup, not
bound to component state. The early inline <script> (before WASM boots)
flipped it via raw DOM mutation, but when the WASM runtime later resumed the
prerendered component, Blazor's own first render re-asserted the static
disabled from the markup - silently undoing the JS fix. The second
bindLoginForm() call from OnAfterRenderAsync then bailed out immediately on
the one-shot "already bound" guard, so nothing ever re-enabled it.
Fix: bind disabled to a real isReady field flipped in OnAfterRenderAsync so
Blazor owns that attribute going forward, and make the JS-side enable
idempotent (runs on every call, not gated behind the bind-once guard) as a
second line of defense.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Admin: replace the global @rendermode on <Routes>/<Router> with per-page
render mode. Login.razor now prerenders (form visible before WASM loads);
every other [Authorize] page stays prerender: false to avoid the
AuthorizeRouteView blank-render regression from earlier attempts. Adds a
"준비 중" -> "로그인" splash tied to WASM boot completion, and lets the
authenticated-shell loading overlay stay up until AdminShell actually renders.
- Contact.cshtml: fix the "Agree" checkbox missing value="true" - a checked
box sent the browser-default "on", which bool model binding can't parse,
so ModelState.IsValid silently went false and OnPostAsync returned a blank
form with no visible error on every submission. Validation summary widened
from ModelOnly to All so this class of failure isn't silent again.
- TelegramInquiryNotificationService: read Telegram:InquiryChatId (falling
back to ChatId) instead of only ChatId, matching the channel routing
CLAUDE.md documents and deploy.yml already provisions as separate secrets.
- Reconcile CLAUDE.md's self-contradicting Phase 8 prerender notes (Phase 9),
rewrite validate_admin_render.sh for the per-page design, and add a
SmartAdmin 5.5 design reference section to DOUZONE_UX_GUIDE.md for future
admin screens (existing screens unchanged, tracked as WBS P4-03).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
AdminShell was attempting to inject VersionInfo from server DI container,
causing 'Cannot provide a value for property' error in WebAssembly components.
Replaced with hardcoded 'unknown' values.
All admin pages now render successfully (HTTP 200):
✅ /admin/login
✅ /admin/blog
✅ /admin/dashboard
✅ /admin/inquiries
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
kjh2064