Published October 27 UTC on GitHub and the signed pilot feed. Offered, downloaded and installed are separate states; Live Lobbies reports observed room versions.

Completed or cancelled controller-update records are retained before a later queue replaces them. When exact evidence proves an obsolete automatic maintenance request belongs to a completed earlier update, the controller can retire that stale request and begin a new independent empty-room drain. Current ownership, installation binding, configuration, bookings and live room observations must still qualify. Historical records alone never authorize a restart or an ownership clear.

The release includes separate difficulty preferences for Standard, Catch, Taiko, Mania 4K and Mania 7K. Earlier mixed Standard/Catch records are not guessed or copied. No new player commands, database schema changes or hub restart are required.

319 distinct affected subsystem checks passed, with initial fixture failures retained and their relevant modules rerun after corrections. Four exact stopped-upgrade cases covered v7.3.4, v7.3.5 and v7.3.6, including preservation of unknown creation. Two installed donor cases used all six full catalogs: a retained-history retirement/recovery path and a fresh unchanged v7.3.6 automatic updater. The latter downloaded and resumed the exact release, protected an occupied match and private booking, preserved a waiting settings edit, retried an interrupted helper, drained empty siblings independently, committed, reopened intended rooms and refreshed its recovery pin. Both cases were stopped and audited after validation. No real account credentials or live test rooms were used.

The full repository suite and real gameplay were not rerun. The donor retirement case used an explicit guarded recovery path; it does not establish automatic repair of every old hold. Installed cancellation/redrain rounds were not exercised. The release includes the exact evidence and limitations.

Old evidence cannot be reconstructed: an older updater may already have overwritten the previous terminal record. Missing history is not invented; the supported all-empty path or operator review may still be required. Publishing this release does not clear an existing hold or unknown ownership.

Separate known incident: a rejected or uncertain replacement-room creation can still escalate to a shared-controller shutdown. This release does not fix that failure. Preserve state, identify the candidate room, and use supported read-only ownership review and verified recovery before restarting. A referee SIGKILL during cleanup is not proof of the initiating cause.

At publication the owner was restored on v7.3.6 (Catch, Taiko and 4K; room2 reserved). Xikeon and Strohm had stopped hosts requiring local ownership evidence. These are rollout observations, not claims of v7.3.7 installation.

Runtime SHA-256: 38f8143c3c9c4201c5f8eb008e3bdfb7f824df14a313cbd0a85f34065a8edf09.