Complete private authentication, server integrations and activity reporting

Add Fabric/Forge version builds and Paper integration, preserve permanent player identities across renames, harden session authorization, and surface privacy-conscious launcher/server activity in the panel.

docs/admin-guide.md

@@ -52,18 +52,18 @@ On the **Server** tab: name, address, port.
 - *Add to multiplayer list* writes the server into `servers.dat` (keeping servers players added).
 - *Join automatically* connects on start (Quick Play on 1.20+, `--server` on older versions).
 
-Your server must allow the accounts you use: offline-mode (`online-mode=false`) for panel/offline accounts, or online-mode for Microsoft accounts. Protect offline-mode servers with a whitelist or an auth plugin.
+Official servers use `online-mode=true`, authlib-injector and the SCOPENET server integration. See [server setup](server-integration.md) for the startup flag, tokens and supported versions.
 
 ### Access
 
-- **Everyone** — any launcher, including offline and Microsoft accounts.
+- **Everyone** — any launcher, including local offline accounts.
 - **Signed-in players** — any panel account.
 - **Specific groups** — members of the selected groups (create groups on the Players page). Admins see everything.
 
 ## Players
 
 - **Sign-ups:** Settings → *Closed* (admins create accounts), *Needs approval*, or *Open*.
-- Panel accounts play under their username with the offline-mode UUID an offline server computes, so inventories and permissions stay consistent.
+- Each account has a permanent UUID. New accounts receive a random UUID; existing accounts keep theirs. Username changes preserve inventory and reserve prior names. Players change username, skin and permitted capes from the launcher.
 - Disabling an account signs it out everywhere on the next request.
 - Ten failed logins lock an account for five minutes.