Frontend Production Hardening: JWT-First KYC Alignment + Dashboard Integration Stability
KYC Auth / Model
- Switched to a JWT-first identity resolution strategy (sub / userId / user_id)
- Blocked non-authenticated paths in production mode (fallback userId limited to local/test mode)
- Synchronized KYC userId with JWT claims KYC Cache & Multi-Account
- KYC cache (kycId, documentId, livenessId) is now scoped per user
- Automatic KYC cache cleanup on account switch / logout
- Automatic retry with cache clear when stale KYC IDs are detected (“KYC request not found”) KYC Flow Safety
- Prevented step updates on final statuses (SUBMITTED, IN_REVIEW, APPROVED, EXPIRED)
- Reduced frontend errors caused by invalid transitions Dashboard Integration
- Preserved integration with /api/v1/me/dashboard
- Improved loading resilience and data mapping for dashboard / properties / transactions