fix: improve endgame clock and gameplay stability

docs/cw-route-continuation-audit.md

@@ -1,5 +1,27 @@
 # Currency Wars route continuation audit
 
+## 2026-11-01: stuck initial round and `/cw end`
+
+The live server log rejected the initial RoundBegin at queue 2 with
+`CW starter pool reservation is not supported`. A read-only copy of the live
+snapshot showed a starter above its captured default star. On a detached copy,
+the same run advanced through `cwInitialRound` after changing initial pool
+accounting to use the existing captured `ReserveOwned`/merge rules, as later
+shop restocks already do. No live snapshot was modified by this check, and the
+new battle/Client path has not yet been verified.
+
+`/cw end` queues a run- and UID-bound ordinary quit settlement, including
+while a pending choice is present. An active Battle defers it until afterward.
+The quit record, archive, removal of the run and acknowledgement of the command
+share the persistent CAS transaction. It reports queued rather than claiming
+success before heartbeat. It does not declare a win or randomize a new run.
+
+The reported repeated rooms are consistent with `CurrencyWarsInitialRuns.json`
+and `CurrencyWarsEntryTransitions.json`, which replay captured initial states
+and portal outcomes. Later factory paths can generate some enemies, but the
+dynamic room and PetPal replacement contract is still incomplete. No random
+node IDs or fabricated distributions were added; see the historical notes below.
+
 **2026-10-31 update:** An initial xaodev-based generated EliteBranch factory
 has now been connected to the route fallback. The older unsupported-factory
 statements below describe the preceding implementation. The new code passes