b0ddb274d2
Build & Test (NowChessSystems) TeamCity build finished
OfficialBotService.onStart fires on StartupEvent (after all @PostConstruct), so official bot accounts do not exist in the account service DB yet when TournamentBotGamePlayer.initialize() runs on a fresh DB. This caused getBotToken to 404, falling back to the stale TOURNAMENT_BOT_TOKEN env var which uses the old signing key and is rejected with 401. fetchTokenFromAccountService now retries after syncing all official bot accounts (creating them if missing), ensuring a fresh token with the current signing key is always available on startup. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>