Integrate Vantage live map for guild claims [skip ci]

docs/deployment.md

@@ -23,6 +23,12 @@ The panel listens on `PANEL_PORT` (default `8080`). Docker checks
 `docker compose ps` before directing players to it. If `ADMIN_PASSWORD` is
 blank on first start, the generated password appears in the panel logs.
 
+To show a Vantage world map in the launcher, deploy Vantage next to each game
+server and configure its manifest URL in the panel. See
+[Live map setup](live-map.md). Vantage needs access to the game world's saved
+files, so it runs alongside the game server rather than inside the panel
+container.
+
 The named `panel-data` volume holds the database, uploads, hosted launcher
 downloads, and the generated JWT signing key. Preserve that volume when
 upgrading. To back it up, stop the panel, archive the volume with a temporary

docs/live-map.md

@@ -0,0 +1,44 @@
+# Vantage live map
+
+SCOPENET can display a [Vantage](https://github.com/thoughts-on-things/vantage-mc)
+world in the launcher's **Guilds & Claims → Territory** view. The map shows
+live terrain, optional player positions, SCOPENET guild names, and the claim
+outline for each nearby chunk. Clicking terrain selects the chunk; the Claim
+and Unclaim buttons use the existing authenticated SCOPENET API. Claim
+protection on the game server is unchanged.
+
+## Set up the world map
+
+1. Install a Vantage release on the machine that can read the Minecraft world
+   files. Give it read access to the save, and a separate writable cache.
+2. Start a live render for that world. For example:
+
+   ```sh
+   vantage live /srv/minecraft/world --out /var/cache/vantage/world --host 127.0.0.1 --port 8268
+   ```
+
+3. Put Vantage behind an HTTPS reverse proxy, or have your portal proxy its
+   map files. The launcher's **Vantage live map manifest URL** is the complete
+   `manifest.json` URL, such as `https://maps.example.com/manifest.json`.
+   A pre-rendered multi-dimension world can use `world.json` instead. In the
+   panel, open **Servers → your server → Edit** and save that URL.
+4. Link the game server to the correct launcher instance. Open that instance's
+   Guilds & Claims page in the launcher. The selected game server controls both
+   the Vantage world and the SCOPENET claims shown on it.
+
+The native launcher streams map assets through its HTTP client so the map host
+does not need browser CORS headers. Browser-only development previews require
+CORS on the map host. The URL is included in the public game-server summary;
+use a map you intend players to see. Keep Vantage `server` bearer credentials
+out of this URL. For private worlds, put Vantage behind a session-gated proxy
+that serves the manifest and tile files with the player's existing session.
+Vantage's [server guide](https://github.com/thoughts-on-things/vantage-mc/blob/main/docs/server.md)
+describes the sidecar and its authorization boundary.
+
+Live terrain comes from Vantage's read-only view of saved world files. Claims
+and guild names come from SCOPENET's claim database. If the map cannot be
+loaded, the launcher falls back to the chunk grid. The map does not run inside
+Minecraft; `/guild map` is still the Paper plugin's nearby chat radar.
+
+Vantage's web package is MIT licensed. See its
+[license](https://github.com/thoughts-on-things/vantage-mc/blob/main/LICENSE).