[Game Server] Async void anti-pattern & missing command input validation

[Flegma]

Summary

Code quality issues reducing reliability.

Findings

• ReadySystem.cs — async void SendNotReadyMessage() causes unobserved exceptions. Should return Task.
• Match.cs — command.ArgString passed to MapStatusStringToEnum without validation.

Impact

Silent failures from async void. Invalid command arguments cause unexpected behavior.

Suggested Fix

Change async void to async Task. Validate ArgString against known enum values.

---

Related Issues (Input Validation Pattern)

• [API] Harden match events gateway authentication and message validation #371 — [API] Harden match events gateway validation
• [Connector] Sanitize user input in offline match manifest generation #404 — [Connector] Sanitize offline match manifest input
• [Connector] Add command validation and whitelist to RCON gateway #405 — [Connector] Add RCON command whitelist
• [Connector] Add authentication to WebRTC datachannel & validate match data DTOs #406 — [Connector] Validate WebRTC datachannel & match DTOs
• [Game Server] Async void anti-pattern & missing command input validation #402 — [Game Server] Missing command input validation