0d747f1a86
From 0.2 the game is tagged vX.Y.Z and the launcher launcher@X.Y.Z (docs/versioning.md). The launcher compared every tag number by number, so it would never offer game v0.2.0 over v2026.10.19.15 nor update itself to 0.2.0 from 0.16.0 (launcher-v0.2.0 is also taken by an old release). - release_order(): tags from before 0.2 (vYYYY.MM.DD[.N], launcher-vX.Y.Z, bare versions) compare as before; every 0.2 tag follows them, in semver's order (a pre-release before its release). - own_tag(): the tag this launcher was released as. launcher.yml will pass HORIZON_LAUNCHER_TAG; a release with only HORIZON_LAUNCHER_VERSION was a launcher-v one; a build from source is on 0.2. So the last launcher-v release (the bridge old launchers can see) updates itself to launcher@. - The matching-refs fallback looks for launcher@ tags first, then launcher-v. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>