Add map record HUD announcements for T5 and T6

t6/NOTES.md

@@ -39,10 +39,36 @@ releases them before the protection grace period. Restoration is deferred during
 death/laststand/intermission until active play. Other mods controlling the same
 invulnerability or weapon flags can still conflict and need live testing.
 
-The four optional T5 dvars remain; no new configuration switches are introduced.
+The existing optional T5 dvars remain. Leaderboard adds the three settings
+documented in the [shared README](../README.md#map-record-announcements).
 `common_config()` and `ensure_config()` are original T5 in-memory HUD helpers,
 not an external configuration system.
 
+## Leaderboard join announcements
+
+The module is `tws_t6_leaderboard.gsc` in T6 and `tws_leaderboard.gsc` in T5.
+Common's existing
+connection listener now also dispatches optional connection handlers after a
+one-frame yield. Leaderboard waits for player readiness and uses a level-owned
+HTTP cache, independent of the first-playable-spawn handlers. T6 spectators keep
+`hasSpawned` false, so T6 readiness uses session state and the intro-screen flag;
+T5 sets `hasSpawned` for both playable and spectator spawns.
+
+T6's active `scr_zm_ui_gametype` / `scr_zm_map_start_location` fields come from
+[stock `_zm.gsc`](https://github.com/plutoniummod/t6-scripts/blob/2d8440321602f22f63f5335817110d60ddf223d5/ZM/Core/maps/mp/zombies/_zm.gsc).
+Mode/location combinations follow the
+[T6 server configurations](https://github.com/xerxes-at/T6ServerConfigs/tree/master/localappdata/Plutonium/storage/t6/gamesettings)
+and Electric Cherry's map catalogue. Unknown selections require an explicit API
+key instead of falling back to another variant sharing the engine map.
+
+Validation for this change: 135 fixture/static checks pass using the actual
+data-handling functions from both scripts with JavaScript engine-value shims.
+All seven T6 scripts compile and assemble using a local Intel macOS driver built
+from gsc-tool 1.5.1 sources. PowerShell was unavailable, so `check.ps1` itself was
+not executed here. T5 compilation and live plugin/gameplay checks were not run;
+gsc-tool has no T5 backend. The production API could not be reached from this
+environment. See the shared README for the live validation cases.
+
 ## Verified primary sources
 
 - [Plutonium loading guide](https://plutonium.pw/docs/modding/loading-mods/): T6
@@ -92,7 +118,7 @@ at link time. The other four TWS modules can run without telemetry.
 
 ## Checks
 
-Local: `tools/check.ps1` compiles all six files for T6 PC and checks shared
+Local: `tools/check.ps1` compiles all seven files for T6 PC and checks shared
 references and entry points. It requires PowerShell and gsc-tool. The `.help`
 change passed the static entry-point/reference checks, but compilation and live
 gameplay were not run. Compiler success does not certify runtime linking.