completed

- Modified _monitor_game_state to create new matches from old completed ones instead of stopping when fixture completes
- Enhanced _initialize_new_fixture to create fixtures from old matches when no new fixtures available
- Added helper methods for match selection and recycling:
  * _select_random_completed_matches(): Selects random completed matches
  * _create_matches_from_old_matches(): Creates new matches in existing fixture
  * _create_new_fixture_from_old_matches(): Creates new fixture from recycled matches
- Added comprehensive documentation explaining game flow and human intervention points
- Game now runs continuously until machine restart, recycling completed matches to maintain betting opportunities

- Create GAME_FLOW_DIAGRAM.md with detailed visual representations of:
  * Complete match lifecycle state machine (scheduled → bet → ingame → completed)
  * Component interaction diagrams showing system architecture
  * Betting system flow from customer request to receipt generation
  * Timer and automation sequences with priority logic
  * Extraction process flow with redistribution cap logic
  * Error handling and recovery scenarios
  * Performance and scalability visualizations
- Include timing sequences, global betting mode comparisons, and bottleneck analysis

- Create USER_WORKFLOW_DOCUMENTATION.md with extensive coverage of:
  * Complete cashier workflow from login to end-of-day procedures
  * Game flow and match progression with state machine details
  * Extraction algorithm and redistribution cap system
  * Major functionality and configuration options
- Add statistics.html template for admin statistics dashboard
- Update core components for improved functionality

- Remove duplicate start_games function in routes.py that was causing Flask route conflict
- Add Statistics page link to admin submenu in navbar with chart-bar icon

- Add /api/cashier/start-games endpoint to routes.py that sends START_GAME message to message bus
- Complete betting system with win_amount calculation and paid_out tracking
- Update bet resolution logic for UNDER/OVER outcomes
- Add comprehensive result extraction with CAP logic
- Enhance match timer and games thread coordination
- Update verification pages to show proper win amounts and payout status

- Remove automatic PLAY_VIDEO_MATCH sending from MatchTimerComponent
- Add MATCH_START handler to GamesThread with betting calculation logic
- Update Message Builder to include result parameter in PLAY_VIDEO_MATCH messages
- Update Qt Player to use match_video.html template for match videos
- Add new match_video.html overlay template for displaying match results

The new flow: Start Games -> MATCH_START -> betting calculation -> PLAY_VIDEO_MATCH with result -> display match video with result overlay