- Add await to initializeOverlayController() in player.js to ensure proper initialization order
- Add better logging to overlay-controller.js for debugging postMessage communication
- Add sessionStorage check to getAuthToken() for more robust token retrieval
- Add error handling and logging to fetchFixtureData() and apiRequest() methods

This fixes the issue where the overlay iframe was requesting fixture data but not receiving it from the parent window.

- Added isStandaloneMode detection (window.parent === window)
- getFixtureData() now fetches directly from /api/overlay/fixtures in standalone mode
- getCompletedMatches() now fetches directly from /api/overlay/completed-matches in standalone mode
- getWinningOutcomes() now fetches directly from /api/overlay/winning-outcomes in standalone mode
- Prevents timeout waiting for parent window response when no parent exists

- Added isStandaloneWebMode() function to detect when running without Qt or parent iframe
- Added fetchFixturesFromAPI() function to fetch data directly from /api/overlay/fixtures
- Modified fetchFixturesData() to use direct API call in standalone mode
- Falls back to API when WebChannel is unavailable or times out
- Fixes issue where fixtures overlay showed 'null' data when loaded directly in browser

- Use timezone-aware date filtering (get_today_venue_date, venue_to_utc_datetime)
- Query today's matches and yesterday's incomplete matches
- Exclude terminal states (done, end, cancelled, failed, paused)
- Limit to 5 matches total, same as Qt player
- Add debug logging for match counts

- Add detailed logging to getFixtureData and getCompletedMatches
- Log fixture data sample when received
- Remove origin check in onIframeMessage for debugging
- Add logging to sendMessageToOverlay

- Add inline environment detection to all overlay templates
- Qt environment: Load Qt scripts (qwebchannel.js, overlay.js) synchronously
- Web environment: Load web adapter for postMessage bridge
- Update overlay-web-adapter.js to exit early in Qt environment
- Fixes issue where overlay templates didn't show data in web player

- In Qt environment, use document.write to load Qt scripts synchronously
- This ensures QWebChannel and overlay.js are available before template's inline scripts run
- Async loading was causing templates to fail because overlay object wasn't ready

- In Qt environment, provide temporary window.overlay with log function
- This prevents errors from template's console.log override that runs immediately
- Qt's overlay.js will later replace this with the full overlay object

- Store original console.log before templates override it
- Use originalConsoleLog throughout the adapter to prevent recursion
- Templates override console.log to call window.overlay.log, which was calling console.log again

- Removed copied overlay-web-adapter.js from web/
- Created web/js symlink pointing to mbetterclient/web_dashboard/static/js
- Ensures templates reference the same file at /js/overlay-web-adapter.js

- Created overlay-web-adapter.js to bridge postMessage to WebChannel interface
- Updated all web templates to use conditional Qt script loading
- Updated all Qt player templates with same pattern for consistency
- Prevents browser console errors from Qt URL schemes (qrc:///, overlay://)
- Templates now work in both Qt player and web player environments