Report #3

Description

Issue Description When loading the Landing Page (unauthenticated state), the console logs show initialization of application-level services that are unrelated to the marketing page: [PerformanceService] Initialized [PerformanceService] Auto-initialized, session: ... [AuthContext] Initializing authentication... [AuthContext] No active session found [PerformanceService] Skipping sync ... (Supabase migration - not persisted) This indicates that: Authentication logic and internal performance tracking services are being initialized on a public marketing route. Internal app services are executing even when the user is not inside the authenticated application. The landing page is not isolated from app-level service initialization. While not a crash, this creates unnecessary console noise and suggests architectural leakage between public and app layers. Expected Behavior When visiting the Landing Page (public route): No authentication initialization logs should appear. No app-level services (e.g., PerformanceService, credit services, migration sync) should initialize unless explicitly required for the landing page. Console should remain clean in a normal (non-debug) environment. Public marketing routes should operate independently of authenticated application logic. Acceptance Criteria Visiting the landing page while logged out: No AuthContext initialization logs appear. No PerformanceService initialization logs appear. No migration-related “Skipping sync” logs appear. Auth services initialize only when entering authenticated app routes. Performance tracking (if global) does not log migration or internal app sync messages on public pages. Console remains free of non-critical operational logs in production mode.