NatsEventBus.SubscribeAsync uses queueGroup=null, so every pod receives
every NATS event. AddAiService was guarded by IsEnabled("game"), meaning
ALL game pods also started AiPlayerSessionManager. On each AiTurnStartedEvent,
all 3 pods (2 game + 1 AI) would concurrently call ExecuteTurnAsync — causing
draw/action conflicts and the AI appearing to stall or do nothing.
Fix: remove AddHostedService from AddAiService; add it to Program.cs under
IsEnabled("ai") so only the dedicated AI pod (ENABLED_SERVICES=game,ai)
starts the session manager. Game pods still register AiPlayerSessionManager
as a Singleton (for potential injection) but never start its event loop.
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>