Published: Installer, runtime, checksums and validation. Existing v7.2.12 hosts use the signed automatic controller update at their safe host-wide empty-room boundary. No reinstall, OAuth reset or repeated enrollment is required. Older managed hosts complete their supported v7.2.12 step first.

A definitive HTTP 403 on a lobby announcement no longer escapes the worker loop and closes the room. The rejected message is omitted, a bounded chat backoff applies, and gameplay continues. Chat read and ACK denials also retain safe retry behavior. Ambiguous writes are never blindly resent; initial chat access, authentication and room ownership remain strict. The upstream cause of the observed channel departures remains unconfirmed.

The installed controller now starts and stops the existing community Discord command relay. A visible Discord panel and a connected command relay are separate observations; neither substitutes for the other. Loved room labels omit the redundant Standard designation.

Player-statistics snapshots reuse independently verified on-disk results for the older and Catch-capable protocols. A bounded background builder refreshes snapshots; an HTTP request no longer performs the large rebuild or waits behind it. Only one full in-memory projection is retained. Prior snapshots may be used during refresh only while their authority and privacy policy remain valid. Authority is rechecked after the large scan. Ordinary host-to-hub requests now have a 30-second deadline instead of five seconds.

An admitted controller update pauses only that installation's independent helper timers, then restores their original active states. Native ownership checks, deliberate stopped rooms, room settings, history, credentials and full catalogs are preserved. Occupied rooms still prevent update admission.

Incident regressions, statistics/privacy/history/chat/Discord tests, the actual installed-controller relay lifecycle and real HTTPS fixtures passed. A stopped donor v7.2.12-to-v7.2.13 upgrade retained 63 configuration, credential, ownership and catalog files, including the full catalog set. Reproducible artifacts, the exact predecessor contract and sensitive-data checks passed. Unchanged full-repository suites and actual donor gameplay were not repeated. See the release VALIDATION.json for the exact scope.

The hub repair was deployed independently without restarting owner rooms or Discord. Publication, a queued controller update and installation remain separate states; Live Lobbies shows current versions.