9bbb674184
Game rules lived twice: Level (loaded when the world opened, written to data/minecraft/game_rules.dat by Level::write) and the rules the game and /gamerule use. Every save wrote the file first with the rules loaded at open, then again with the current ones; a failed second write (on Windows a file just renamed into place can be held briefly by the indexer or an antivirus) was only logged, leaving the old rules on disk, so the world opened with them again. - sync_level copies the current rules into Level, and Level::write is the only writer of game_rules.dat (written as vanilla writes saved data: `_new`, then renamed over the old file). - The world is saved when the application ends without a window close (ApplicationHandler::exiting): on macOS, Quit (Cmd+Q) ends the application through applicationWillTerminate, while vanilla's GLFW window turns it into a window close and Minecraft.stop saves the world. Window close, `horizon-ctl quit` and exiting share save_for_exit, which saves once. Tests: a unit test writes changed rules through Level::write and reads them back (GameRules::load and Level::read); the save round-trip harness has Horizon's player change a rule with /gamerule before saving and requires the new value in the world vanilla then loads. Fixes #74 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>