[2026] split 2026 to tachy hosts

.env.example

@@ -159,6 +159,14 @@ RECFLARE_DOMAIN=rec.example.com
 # out. A sandbox account on that build still gets the sandbox pool. Unset, rollout players
 # use the pool above.
 # RECFLARE_TACHYON_HOST_PORT_ROLLOUT=198.51.100.13:7777
+#
+# WHICH builds are served that rollout pool, when it should not simply follow the sign-in
+# gate: same format as RECFLARE_ROLLOUT_GAME_VERSIONS (builds, commas; `off` for none;
+# `20260323` and `20260323.14` name the same build). Unset, the rollout pool goes to the
+# builds under staged rollout, so ending the rollout (ROLLOUT_GAME_VERSIONS=off) also moves
+# those players onto the live pool. Set this to keep the 2026 build on its own voice
+# servers after it opens to everyone — the 2025 and 2023 builds stay on the pool above.
+# RECFLARE_TACHYON_ROLLOUT_GAME_VERSIONS=20260323
 
 # The Photon region every session is pinned to (`match`). Unlike the app ids above this
 # does default, to `us` (us-east1) — an instance stamped with an empty region is one the
@@ -245,7 +253,8 @@ RECFLARE_DOMAIN=rec.example.com
 # made to upgrade. A build in ROLLOUT is served too, whether or not SUPPORTED names it, but
 # only to staff and the Discord roles below. The lifecycle these exist for:
 #   1. Rollout (both unset): the 2026 build is for staff and supporters only.
-#   2. General availability: ROLLOUT_GAME_VERSIONS=off — the 2026 build opens to everyone.
+#   2. General availability: ROLLOUT_GAME_VERSIONS=off — the 2026 build opens to everyone
+#      (and joins the live voice pool unless TACHYON_ROLLOUT_GAME_VERSIONS above keeps it).
 #   3. Forced upgrade: SUPPORTED_GAME_VERSIONS=20230414,20260323 (with `off` above) — the
 #      2025 build is refused and has to update.
 # To pull a rollout back instead, list neither: SUPPORTED_GAME_VERSIONS=20230414,20250718