4be192a4b8
The synchronous startup loaded every resource before the first window existed, so the game hung on a blank screen for seconds. An ordinary launch now enters the event loop at once, opens the window, and draws a loading screen with the current stage and a progress bar while a resource-loader thread runs the existing load sequence. When it finishes, audio is created on the render thread and the real renderer, game and title screen replace the loading screen on the same window. Harness, dedicated and scripted runs (--frames, --world-frames, --benchmark, --control, --dedicated, HORIZON_MENU_STYLE=classic and the parity fixtures) keep the fully-synchronous path unchanged, so their output stays byte-identical. title_shown still fires on the real title, not on the loading screen.