fix(websocket): Real-time message delivery after reconnect + debug log cleanup

[inventory69]

🐛 Bug Fixes

WebSocket Message Delivery

• Fixed critical bug: Messages not arriving in real-time after app reconnect
• Root cause: _ticketListeners.clear() in disconnect() was removing all widget callbacks
• Solution: Commented out _ticketListeners.clear() - listeners now persist across reconnects
• Impact: Messages now arrive immediately after app backgrounding/foregrounding

Technical Details

The issue occurred because:

1. Widget registered listener via onTicketUpdate() ✅
2. App backgrounded → disconnect() → _ticketListeners.clear() ❌
3. App foregrounded → connect() created new socket ✅
4. Widget called joinTicket() ✅
5. Backend emitted new_message ✅
6. Socket received event but found NO listeners ❌
7. Widget never received message ❌

Listeners are widget callbacks that should persist across socket reconnects. They automatically work again when the new socket connects because _handleTicketUpdate() is re-registered in connect().

🧹 Code Cleanup

Frontend (Flutter)

• websocket_service.dart: Removed ~40 debug logs from connect/disconnect/join/leave operations
• ticket_chat_widget.dart: Removed verbose message flow debug logs
• main.dart: Removed app lifecycle debug logs
• Result: Clean console output, only critical errors logged

Backend (Python)

• notification_routes.py: Converted JOIN/LEAVE/EMIT logs from logger.info() → logger.debug()
• ticket_routes.py: Converted MESSAGE logs from logger.info() → logger.debug()
• Result: Routine operations only visible when logger level set to DEBUG

📋 Files Changed

Frontend

• lib/services/websocket_service.dart - Critical fix + log cleanup
• lib/widgets/ticket_chat_widget.dart - Log cleanup
• lib/main.dart - Log cleanup

Backend

• api/notification_routes.py - Log level adjustment
• api/ticket_routes.py - Log level adjustment

✅ Testing

• Messages arrive in real-time after app reconnect
• Multiple reconnect cycles work correctly
• Background/foreground transitions work
• Console output clean and production-ready
• Error logs still functional

🎯 Impact

• User Experience: Seamless real-time messaging even after connection interruptions
• Developer Experience: Clean logs, easier production debugging
• Performance: No change, listeners were already lightweight callbacks