Problem: Client JavaScript/Blazor WebAssembly errors were logged but NOT sent to Telegram because ClientLogsController used LogWarning instead of LogError.
Solution: ClientLogsController now checks entry.Level:
- level='error' → LogError → Telegram alert ✓
- level='warning'/'info' → LogWarning → Log file only
Result: Browser console errors now trigger Telegram notifications:
- Blazor WebAssembly init failures
- JavaScript exceptions
- Unhandled promise rejections
- Custom client errors
This closes the monitoring gap for client-side issues.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
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>
Revert to InteractiveWebAssemblyRenderMode for App.razor as required by validation script.
Add back AddInteractiveWebAssemblyComponents and AddInteractiveWebAssemblyRenderMode.
Fix assembly reference to use TaxBaik.WasmClient._Imports (RootNamespace of TaxBaik.Web.Client project).
This mixed render mode architecture allows:
- App.razor: WebAssembly shell for client-side routing
- Login.razor: Server-side prerender for authentication
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Update Login component to use Blazor Server instead of WebAssembly rendering mode for consistency with the admin UI architecture.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- 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>
과거 실수들을 명시하여 같은 오류 반복 방지
## 실수 방지 체크리스트 추가
1. 카테고리 할당 실수 (category_id NULL)
2. 내용 길이 부족 (1,500자 미만)
3. 테이블 사용 금지 (리스트만)
4. 계산 예시 누락 (절세액 미수치)
5. 카테고리 주제 불일치
6. 정확한 세법 인용 누락
## 각 실수별
- 과거 오류 상황
- 문제점 분석
- 예방책 (SQL/마크다운 예시)
- 최종 체크리스트
SQL 확인 쿼리도 포함하여 DB 적용 후
자동 검증 가능하게 구성.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
kjh2064