Add persistent Discord URL to T5 and T6 HUDs

CHANGELOG.md

@@ -22,6 +22,32 @@ T5/T6 script and each native plugin. Current versions are recorded in
 - Portable regression fixtures: `node tools/check_join.mjs`. Compilation and
   live Plutonium validation remain required; no deployment was performed.
 
+### Persistent top-left Discord URL
+
+| Script | Version | Affected source |
+| --- | --- | --- |
+| `tws_t5_hud.gsc` | `1.1.0` | `t5/scripts/tws_t5_hud.gsc` |
+| `tws_t5_common.gsc` | `1.1.0` | `t5/scripts/tws_t5_common.gsc` |
+| `tws_t6_hud.gsc` | `1.1.0` | `t6/scripts/tws_t6_hud.gsc` |
+| `tws_t6_common.gsc` | `1.1.0` | `t6/scripts/tws_t6_common.gsc` |
+
+- Add `https://discord.thewrightserver.net` as a small, light-gray top-left
+  HUD label, created once per connection, including spectator newcomers.
+  It has no expiry or death/respawn reset and is cleaned up on disconnect.
+  Move the gameplay stack down 20 HUD units to leave room above the timers;
+  help and record positioning follow the shared layout automatically.
+- Both engines receive the feature using their existing HUD anchors: T5
+  left/top safe-area alignment and T6 fullscreen alignment.
+- Compatibility: deploy each game's HUD and common `1.1.0` together for the
+  reserved top line. No new native plugin or external dependency requirement.
+  Other scripts and both plugins retain their existing versions.
+- Deployment: copy the updated HUD and common scripts to `storage/t5/scripts/sp/`
+  or `storage/t6/scripts/zm/`, respectively, and restart the map. No full
+  server-process restart is required. No deployment has been performed here.
+- Live validation remains required on both Plutonium games: check placement
+  and readability, join as a spectator, die/respawn, reconnect, and open help
+  and records to verify spacing and that only one URL label appears.
+
 ### Initial versioning baseline
 
 Established independent version `1.0.0` entries for each of the 14 scripts and