Handle Miniflare metadata during Classic cutover and preserve daily backups

deploy/classic/README.md

@@ -61,11 +61,10 @@ registration and enables activity even when no human player is present.
 Automatic population creation remains disabled; the native identity allowlist
 still limits managed login to the planned 50.
 
-Remaining cutover gates include live quest/training/survival observations,
-event telemetry and human-player conversation parity, dashboard/operator actions,
-normal resurrection, actual party acceptance and speech, authentication/client
-configuration, and a verified rollback route. Human-player chat delivery is
-explicitly disabled in the staged Classic adapter until implemented and tested.
+Before cutover, verify fresh 50-character observations, quest and spell outcomes,
+normal resurrection, actual party receipts, native GM commands, authentication,
+and rollback. Human player replies require an actual in-game session for an
+end-to-end acceptance check. Lua/ALE reflection remains a Wrath-only capability.
 
 Migration safeguards:
 
@@ -94,3 +93,8 @@ copies only ENDAMI's existing SRP credentials into the isolated authentication
 database, and disables upstream sample logins. `check-auth.py --root ROOT`
 verifies a complete SRP handshake and realm listing without entering the game.
 `health.py --root ROOT --url URL` reports host health without Wrath SQL.
+
+`cutover.py --root ROOT` requires a passing build and all 50 fresh staging bots,
+backs up stopped Wrath accounts/characters, switches the existing endpoints, and
+automatically restores Wrath endpoints if login or population verification fails.
+Miniflare metadata databases are excluded from game-state backup selection.