Switch releases to 0.2 (merge only when Ludovic says go)

.github/release-line.txt = 0.2: the release train's next runs publish v0.2.0 (a beta, as always)
and [email protected] at once, "the first release of 0.2" (docs/versioning.md). Merge it only after
the bridges (the last dated game release, made stable, and launcher-v0.17.0) are out: the go-day
steps are in docs/versioning.md.

Also, because they say 0.2 is out: the site's FAQ explains the numbers, Install says an old launcher
updates twice, hosting.md gives the one command for a server that says it is up to date, and the
launcher's Cargo.toml says 0.2.0 so builds from source (packages) are on the 0.2 line.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

.github/release-line.txt

@@ -0,0 +1 @@
+0.2

docs/hosting.md

@@ -240,7 +240,9 @@ If the new game crashes or doesn't come up in time, the server goes back to the
 and puts the world back as it was just before the switch (the world the new game left is kept in
 `backups/`). `horizon-server rollback` goes back to the release before by hand, keeping the world as it is
 (it backs it up first). `--version vX.Y.Z` installs a given release, and `--archive FILE --version NAME` an
-archive you have, such as your own build. A stopped server is switched and starts on the new release next
+archive you have, such as your own build. A server still on a release from before the last dated one doesn't know
+that 0.2 comes after the dated releases and says it is up to date: run `horizon-server update --version v0.2.0`
+once ([versioning](versioning.md)). A stopped server is switched and starts on the new release next
 time. Set `HORIZON_NO_UPDATE_CHECK=1` in the server's environment to turn the check off.
 
 Coming: `console` (attach to a server running in the background), `ban` and `pardon` as their own

launcher/Cargo.lock

@@ -2661,7 +2661,7 @@ dependencies = [
 
 [[package]]
 name = "horizon-launcher"
-version = "0.1.5"
+version = "0.2.0"
 dependencies = [
  "clap",
  "dirs 5.0.1",

launcher/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "horizon-launcher"
-version = "0.1.5"
+version = "0.2.0"
 edition = "2021"
 license = "MIT"
 description = "Downloads, prepares and starts Horizon builds"

website/docs/faq.md

@@ -62,6 +62,10 @@ Only if you say yes, and each kind has its own switch. Everything is off by defa
 
 Often. Every change players can see is released automatically after it is merged, so new versions can come out several times a day. The launcher installs them for you, or only stable ones if you leave **Beta builds** off. See [Install](/docs/install#updating).
 
+## What do the version numbers mean?
+
+Since 0.2, every release has a number: 0.2.0, then 0.2.1, 0.2.2 and so on, one for each release. The game and the launcher are both on 0.2 and count on their own, so you can play Horizon 0.2.7 with launcher 0.2.3. A bigger step, such as 0.3, is announced when it comes. Releases before 0.2 were named after the day they came out (2026.10.19.15); every 0.2 release is newer than all of them.
+
 ## How do I report a bug?
 
 See [Logs, crashes and bug reports](/docs/troubleshooting).

website/docs/install.md

@@ -35,7 +35,7 @@ The game opens on Horizon's own title screen. Your worlds, options and logs live
 ## Updating
 
 - **Horizon.** The launcher looks for a new release when it starts and every four hours while it is open. With **Install new versions automatically** on (the default), it installs one and moves you to it if you were on the newest. New releases come out many times a day, and old versions stay installed until you remove them on the **Versions** page.
-- **The launcher.** It updates itself from its own releases, then shows **Restart** in its footer.
+- **The launcher.** It updates itself from its own releases, then shows **Restart** in its footer. A launcher from before 0.2 (0.16 or older) updates twice in a row: first to 0.17, then to 0.2. Then it installs Horizon 0.2 like any update.
 
 ## Stable and beta builds