Add telemetry dashboard and automatic server names; record Workshop 0.0.137

docs/telemetry.md

@@ -243,3 +243,37 @@ kills. Downed means an unconscious episode, while a death is a fatal loss.
 Recoveries include self-recovery and are not healer-attributed revives.
 Local result tracking continues when telemetry is disabled; sending still follows
 the existing telemetry setting and endpoint configuration.
+
+## Browser dashboard
+
+The receiver serves a private statistics dashboard at
+`https://co10escape-telemetry.zacekjakub.workers.dev/dashboard`. Use the receiver’s
+read-only token or admin token to view server records and last receipt times,
+mission outcomes, player counters, mods, settings and raw event history. Tokens
+are held only in browser-tab memory. See the [receiver guide](../services/telemetry-worker/README.md#statistics-dashboard)
+for deployment, pagination and freshness semantics. This requires only the Worker
+update and receipt index migration; it does not require a new mission release.
+
+### Automatic server names
+
+New events resolve the reporting server’s name from `ServerLobbyApi.GetServerConfig().GetName()`,
+falling back to lobby metadata if unavailable. The optional profile `serverName`
+remains an explicit override. Names are trimmed and bounded to 120 characters.
+Resolution repeats for each new event so startup metadata delays do not permanently
+leave a server unnamed. Neither scenario titles nor account identities are used.
+The installation UUID and queued historical events remain unchanged.
+
+The receiver updates automatic server labels from nonblank accepted reports,
+using server-reported event time to prevent older queued names from replacing a
+newer one. As with all telemetry timestamps, bad server clocks can affect that
+ordering. Managed labels remain operator-owned. Mission rows use the historical
+reported name where present and the current installation label otherwise.
+Automatic discovery needs a new Workshop release; existing blank records only
+acquire names after an updated server reports.
+
+Validation: [2026-11-01 evidence](evidence/telemetry-server-name-2026-11-01/verification.json)
+records 21 receiver/client tests plus two bundled-client checks. Native compilation,
+explicit override and absent-metadata fallback pass without script failures; the
+13 inherited resource/world errors remain. The local Workbench fixture has no
+configured server name, so the real dedicated-server name must still be confirmed
+from the first report after publishing.