v7.1.12 — community reliability and responsive commands

Published October 18, 2026 UTC on GitHub and signed pilot metadata 17. Healthy hosts use the retained safe empty-room update. A running controller whose failed rooms are all confirmed closed can use the guarded repair path. A stopped, deliberately closed, paused or ownership-uncertain installation does not gain permission to create rooms merely from publication.

• Optional profile/top-score GET timeouts preserve the room, roster and READY state; enrichment retries later instead of terminating the worker.
• Community live installs use the existing official chat notification socket, with history reconciliation and HTTP fallback. Provider pacing and command flood protection remain.
• A cold .stats username lookup posts its answer automatically when background data becomes ready. Pending requests are bounded, recheck privacy, and are canceled if the requester leaves/rejoins or the room changes.
• Ordinary freemod settings are preserved; forced DT selections retain their intentional restrictions. The website labels the setting Freemod.
• Community artwork and song length use the restored full central map metadata index. Settings, player counts and shared cards remain. Freemod progress may show an explicitly labelled normal-speed estimate from an actual match start; player speed mods can differ.

The controller repair requires repeated fresh observations, a matching clean ownership journal and unchanged protected runtime/configuration. It does not infer closure from an empty website listing or an old heartbeat. Unknown creation/closure and unsafe process cleanup remain held. Configuration, titles, tuning, catalogs, credentials, enrollment, feedback, statistics history, opt-outs and update policy are preserved.

Typed HTTPS/RPC crash replays, pending stats/privacy/bounds checks, closed-slot refusal cases, complete catalog metadata, and a real protected upgrade from v7.1.11 to v7.1.12 under separate root and service identities were checked. The 270-test affected batch had six fixture/clock failures; all were corrected and 12 targeted checks passed. A separate real protected closed-slot transition committed once, with external service/provider boundaries simulated. Installer checksums and public-source audit passed with zero unresolved findings. Unchanged whole-repository suites and new upstream gameplay tests were not repeated. Actual remote activation is checked separately.

Use the installer asset, not GitHub's source ZIP. Read V7_1_12_OPERATOR_GUIDE.md. Existing supported hosts do not need to repeat OAuth, enrollment or catalog import.

Runtime SHA256: 7400e3c6c53cc5596fd74929fdcf615aecce43fb7340f4c3409f2663b8acfe32.

Installer SHA256: ebb1d0e75f9f51fd86cdf27f74c5c5bfc66fc183b918497ac19b14add7aaa097.

A confirmed delivery limitation remains: the v7.1.11 automatic updater executes its installed admission code. It can download and queue v7.1.12, but cannot itself enter the new all-failed-rooms-closed admission. Publication or a waiting update is not proof that rooms restarted.

The GitHub release now includes a hash-checked one-time activation command for an existing waiting v7.1.11-to-v7.1.12 job. The helper checks the exact protected staged source and dependency environment and arms the existing native timer. It preserves configuration/state, does not clear ownership and does not directly start rooms. The native repeated closure/ownership checks remain mandatory. Return the activation output, redacted support/update/network output and room links. If refused, retain state instead of repeating startup. Seven helper checks and a zero-finding isolated source scan passed.