v7.2.9 — Managed rooms and private-lobby administration

Published release. Publication, safe update queues and installed versions are separate. See Live Lobbies for current rooms.

• Authorized central staff can open, close, reopen, restart and configure individual rooms through durable, scoped requests. Actual upstream closure is confirmed; leaving the referee is insufficient.
• Running/stopped intent survives updates, recovery and reboot. Administration remains available when all rooms are stopped or a controller fails. There is no arbitrary remote shell.
• Validated settings cover supported room types, difficulty, titles, privacy/passwords, mods, styles, filters, timers, votes, commands and greetings. Live-safe changes retain the room; recreation waits for the target room's safe boundary and preserves occupied siblings.
• The hosting operator controls a persistent concurrent-room ceiling, default four, shared by public, private, pending and uncertain creations. Central commands cannot raise or bypass it. Reductions block new creation and drain naturally.
• Managed hosts participate in central administration, shared ratings/statistics, staff diagnostics/chat reporting and signed automatic updates. Credentials stay local. Private-room details, passwords and chat stay out of public website/Discord surfaces.
• Discord preserves stable owner/community slots and reads the running room type for labels. Cards retain maps, artwork, settings and players but omit map progress. Website playback progress remains.
• The owner publisher automatically mirrors the complete current map-exclusion list into compatible signed feeds, with periodic refreshes for additions. Only map IDs are exported; private moderation evidence stays local. Removing a local entry does not silently reverse a signed exclusion.
• Fixes a managed-binding lease race during controller startup, shortens retries for transient heartbeat lease contention, and rejects nonstaff individual viewing grants on the private Discord fleet channel.

Staff controls are enabled in a verified private fleet channel. The hub checks staff roles and channel privacy before accepting commands or posting replies. Hosts must advertise managed capabilities after their upgrade; public lobby controls remain separate.

Keep the existing installation, settings, OAuth, Discord configuration, full catalogs, enrollment, ratings and history. Exact published v7.2.6, v7.2.7 and v7.2.8 automatic updater paths were qualified. This shared-controller release waits for the host-wide safe empty/idle gate. Do not interrupt occupied rooms, reinstall or clear ownership journals to force deployment.

316 final candidate tests and 83 standalone feature tests passed. The full retained reference covered 268 modules and 3604 reported cases, with eight ordinary skips documented; both root-only methods separately passed on the donor. Affected regressions passed after localized changes. Protected full-catalog donor tests exercised native lifecycle, private target recreation with a playing sibling, controller failure/replay, a real reboot followed by provider startup, mixed hub versions and original automatic timer upgrades. Native/failure/reboot checks use the retained revision13 reference; the four-room v7.2.6 updater path used revision15. The reference v7.2.7→revision18 path required a documented QA resource correction and same-operation resubmission; the separate exact v7.2.8→final19 path passed without it. Final installed process/lease guards and the generated exclusion-signing service/timer were separately exercised. Upgrade admission waits boundedly for confirmed transient cleanup and never replays an admitted transaction. Initial failed attempts are retained. Runtime and installer archives are reproducible.

These used synthetic provider responses, not actual osu! gameplay acceptance. Ubuntu 24.04 x86_64, system CPython 3.12 and systemd are qualified; ARM and other distributions remain unqualified. The release's VALIDATION.json records exact attribution and limits.

GitHub release, installer and checksums · Host operations · Release history

The compact hub and community Discord assemblies now include the shared native mode validators and default greeting helpers. This fixes HTTP 503 on valid managed-settings uploads and enables the staff settings/greeting views. Both modules are the exact audited bytes already in the v7.2.9 client runtime; existing service code is unchanged. The fresh source builder and installer allowlist are also corrected.

Sixteen isolated assembly checks and sixteen real donor HTTPS checks passed, including all five catalog modes, replay and private password redaction. A fresh donor kit passed native asset installation and its protected unprivileged bootstrap/TLS check. Current owner settings synchronized and read-only fleet status/settings/greeting checks passed. No actual Discord command or osu! gameplay is claimed by these checks. This central repair needs no additional client update or room restart. See the GitHub release's MANAGED_SERVICE_PACKAGING.md and CENTRAL_SERVICE_VALIDATION.json.