Stable v1.9.13 (task 371): release notes and package

NOT released. Branch stable-1.9.13 (worktree wt\stable-1.9.12), commit 505f22c on e524106 (main, tag v1.9.12).
Release only on the owner's word (tag v1.9.13 on TekRantGaming/king-kong-recompiled, VirusTotal the zip first).
Assets to upload: the zip and SHA256SUMS.txt (the 1.9.13 updater and the 2.0.0 one check the zip against it).

Release text (for the GitHub release; wording for the owner's approval)

The last update before the King Kong Remastered update.

• The updater now installs everything in an update. Every file of the new version is installed, new folders too,
  so updating to the King Kong Remastered update (v2.0.0) from the launcher gives you the complete game. The download
  is checked before anything changes, and if a file is in use the update is undone and your game stays as it was.

The countdown to the King Kong Remastered update (Friday 30 October, 18:00 UK time) and the Join the Discord button
stay on the Home screen. Download the Windows zip below, or update from the launcher.

Package

testbuilds\v1.9.13: KingKong\ (1.9.12's folder with the new king_kong.exe, plus kk-files.txt and kk-retired.txt),
KingKong-v1.9.13-windows-x64.zip (207 entries, 22,914,490 bytes, System32 tar, starts with PK), SHA256SUMS.txt.
Map: release-maps\v1.9.13\king_kong.map with build-info.txt (not in the zip). Script: codex\package-stable-1.9.13.ps1.

• zip b9d72901f9a6c619782f9cde1a9533cb5256ec8fcf8f0b015c2a35caa056e104
• king_kong.exe 4ebdbe27d5b8f8b35331e3bb81b9a9a5b0ede82a2d4db377034c1744b6d9af45
• rexruntime.dll b25f73a3... and rexgpu-xenos.dll 858616d0...: the build's equal 1.9.12's (checked by the script)
• kk-files.txt: 199 files, version 1.9.13. kk-retired.txt: empty (made from the stable packages only, 1.9.12).
• check-package.ps1: the zip equals its kk-files.txt and the assets are right; its other failures are the Beta 17
  layout rules (native DLLs, egg, video, mods-builtin, update-extra-files.zip), which a 1.9.x package does not have.

How 1.9.13 decides to offer 2.0.0

• Stable channel (every stable player): GET releases/latest of the main repo, which only ever holds stable
  versions; offered when its version is newer than 1.9.13. So 2.0.0 is offered only once it is the latest stable
  release there, and not before: publishing the GitHub release IS the switch (publish at 18:00, not earlier).
• Before that the countdown rule is unchanged: at zero the card says the update is out with Check for updates, which
  runs the same check (nothing offered while the latest release is still 1.9.13).
• Beta channel (a 1.9.x player who chose beta): the beta repo's latest release when it is newer than the stable one,
  as in 1.9.12; once 2.0.0 is out it beats every 2.0.0 beta, so they get 2.0.0 too.
• Asset: only a name ending in windows-x64.zip (2.0.0's KingKong-v2.0.0-windows-x64.zip), checked against the
  release's SHA256SUMS.txt line and the listed size; no SHA256SUMS.txt: size only.
• After the install the 2.0.0 program runs. Its build channel is stable (task 358): a stable build always uses the
  stable channel and does not offer Change version, so 2.0.0 never moves a player to the beta channel.

Tests (23 Oct)

• kk-dev ctest 2/2: update-files (kk-update-tests, the stable update_files.cpp), updater-text (13 strings in five
  languages, no dashes, wiring). kk-release builds (old deprecation warnings only).
• codex\simulate-update-stable.ps1 with the stand in 2.0.0 (Beta 17 test 3 tree, kk-files.txt as version 2.0.0,
  runs\task371-rt): 1.9.11 and 1.9.12 to 1.9.13, 1.9.12 to 2.0.0, 1.9.13 (new updater) to 2.0.0: all MATCH.
• Runtime (runs\claude-371-tools\run.ps1, private copies): v200: 1.9.13 installed 99 files, retired
  rexgpu-xenos.dll, restarted into the 2.0.0 stand in; all 292 files present with full hashes. lock: a file held
  open undid the update, 0 files changed, Update failed names the file. game, logs, user, king_kong.toml untouched.