DKR-R v1.0.9 Lobby Stability Playtest 2
Version: 1.0.9-stability-playtest.2

Install this matching build on EVERY machine in the test lobby, including
the host, racers and spectators. It has new peer build identifiers and must
not be mixed with stability-playtest.1 or the v1.0.9 release.
Extract the complete Windows ZIP into a fresh folder and use DKR-R.exe.
On Linux make the x86_64 AppImage executable and launch it normally.

WHAT CHANGED
Fixed a race-start release check in spectator-capable lobbies. A loaded
scene or admitted spectator checkpoint could advance the local scene cursor
before the host's release arrived. The first release was then incorrectly
discarded as a duplicate. Duplicate detection now tracks only releases that
were actually activated, while retaining stale-scene, control-generation,
host-authentication, roster and confirmed-state checks.

Added local logs for accepted/duplicate/stale release messages and completed
scene preparation. Existing launcher design, rollback, music preparation,
mod admission, transfer retries, cache repair, shared saves and online fixes
are retained. No website/API changes are needed for this build.

PLEASE TEST
1. Use a Windows host, a Linux racer and one spectator; repeat with host
   and racer platforms reversed. Enable the same mods used in the failure.
2. Enter character select and Track Select, select a track and start a race.
   Confirm BOTH racers reach the countdown and the spectator follows.
3. Complete a race, return to Track Select, change tracks, and start again.
   Test both stock and custom tracks, characters and vehicles.
4. Repeat with a spectator joining late, a slow spectator connection, no
   spectator connected, and with spectators disabled on the host.
5. Test a player/spectator seat swap and another race start afterward.
6. Repeat at least 20 race transitions. Keep logs from host, racer and
   spectator from the SAME attempt if any transition stalls or disconnects.

EXPECTED DIAGNOSTICS
[party][scene] prepared ... awaiting=host-release
[party][release-receive] accepted ... epoch=... frame=0
Repeated releases may log ignored=duplicate; that is normal AFTER acceptance.
Spectators are not required to vote before racers can start.

An optional offline-copy conflict warning means lobby admission succeeded,
but a downloaded mod was not saved over a conflicting installed offline
identity. It is separate from race-start release and protects existing files.

VALIDATION LIMITS
Both desktop builds are compiled and checked. Synthetic protocol tests run
the actual party-runtime handler against a tiny fake OwnedGame; no user ROM,
guest CPU, RSP or multiplayer game is executed by those tests. Real network,
controller, renderer and modded multiplayer acceptance is the test above.
These packages do not publish a release or change automatic-update files.
