The latest published private kit is v7.0.1-dev12-owner-tuned-defaults. Publishing a kit does not upgrade a running service. The owner's separately qualified v7.0.2 controller update waits for its guarded all-four-empty window.

• Fresh installs default to one Standard Auto lobby and include all four public preset profiles derived from the owner's saved tuning. Explicit host ranges and saved overrides win; ordinary upgrades do not silently reset existing hosts.
• Standard Auto's empty/default baseline is 4.00–5.00★, +0.70★ bias, 0.35★ half-width, pool 1,200 and minimum passes 10,000. Automatic difficulty retunes with players. Mania 4K defaults to fixed 3.00–4.00★, pool 400 and minimum passes 1,000. Both retain the 15-second countdown, freestyle and the reviewed remaining timing/selection defaults.
• The bound existing-host upgrade helper deliberately applies that tuning while preserving chosen titles, language, authorization, full catalogs, enrollment, feedback and integrations. Other origins require review; this is not permission to run a host-specific helper on another installation.
• The installer retains dev11 chat-maintenance, message-queue and narrow undispatched profile/score deferral repairs. Routine classified pacing deferrals are distinct from uncertain room mutations and invalid authorization.
• Full-catalog installed donor qualification covered fresh and retained installs, tuning/title/state preservation, commands/feedback, READY and match completion, delayed chat acknowledgment and bounded recovery. External provider traffic was invented; no new actual osu! acceptance is claimed by those tests.
• Healthy operator rooms should remain running continuously, with concise uptime/gameplay/feedback reports. Installation does not automatically change service restart/enable policies.

Earlier pilot repairs corrected real multiplayer room-response validation and read-only room-chat access checks, preserved real completed ownership recovery in status, added safe HTTP-status diagnostics and removed misleading live “offline OAuth” errors. Confirmed room closure is distinct from a failed local unit or stale service observation. Failed startup retains ownership evidence rather than repeatedly creating rooms.

Independent-host dev7 gameplay completed real maps. Later dev10 feedback also confirmed Standard and 4K map progression before a chat-acknowledgment/send failure stopped the shared service. These reports informed the repairs below; they are not evidence that every command, all modes or shared weighting has completed real acceptance.

• Owner and community rooms use shared presentation components on the homepage, Live Lobbies page and sidebar. They show hosting attribution, centrally resolved map art and duration, and explicitly labeled room occupancy. Owner controls remain bound to owner rooms, and owner totals do not silently include community rooms.
• Existing dev9/dev10 hosts remain supported. Central display metadata supplies art and duration without new per-refresh osu! API calls or operator-side map collection. The current display index contains 129,183 public map rows and is read through a protected read-only binding; research databases and credentials are not published.
• The new v2 path supports relevant public room settings, separately observed playing-player counts (the current native publisher leaves the at-start count unknown), plus Estimated song progress from an actual matching match-start observation, map duration and active clock rate. It clears or hides timing on completion, abort, map changes, stale data or missing evidence. Map selection time is never treated as match start.
• The v2 hub is qualified and staged, not activated. Rich remote settings and timing require both the new operator client and v2 hub activation. Old clients receive centrally resolved art/duration but no invented song clock. Private rooms, passwords, credentials, chat and administrative settings stay outside the public model.
• Dev11 defers chat-acknowledgment maintenance for specifically classified transport and server failures while preserving provider cooldown and uncertainty accounting. It does not turn arbitrary authorization failures or uncertain room mutations into ordinary retries.
• Outgoing room messages proven not to have been dispatched may wait in a bounded 32-message / 120-second room-and-channel queue. Messages tied to an old room/channel are not sent into a recreated room. An uncertain dispatched message is not blindly resent.
• A joining player is recorded immediately from the actual user identity and observed room state, even when profile reads have not been dispatched yet. Missing PP/profile data remains unknown while bounded retries complete enrichment. READY and current player status are retained; a delayed profile lookup must not make the player disappear or crash the room.
• Proven no-dispatch score-read delays retain the score cursor and the existing 25-second scoring timeout rather than terminating gameplay. These profile/score paths handle only the narrow typed admission-deferral outcome; authorization failures, arbitrary errors and uncertain dispatched requests remain distinct failures.
• Fatal errors still require coordinated cleanup and can stop the shared service. Per-room failure isolation is not claimed by this repair.
• Both retained independent-host votes were centrally accepted. Their acceptance is separate from aggregate inclusion and from choosing shared feedback for map weighting; independent/local weighting stays the default.
• Desktop/mobile browser qualification and initial rendering without JavaScript covered the maintained presentation. Real remote song-progress accuracy and dev11 gameplay acceptance remain unobserved; technical qualification is not a claim of completed live gameplay testing.

Historical dev10/dev11 operators followed OWNER_HUB_UPGRADE.md from their exact private kit on their existing stopped installation. Keep OAuth, prepared catalogs, titles, room settings, feedback, enrollment and sharing configuration. Resolve uncertain old-room ownership before starting, and do not reinstall, enroll again or recreate votes. No operator restart is needed merely to receive the compatible website art/duration improvement.

• Prevents an ordinary local request-budget delay during chat keepalive or history reads from crashing a room. Reads retry with bounded backoff while retaining message cursors and continuing real-time chat processing.
• On a fatal service failure, attempts to close known owned rooms before tearing down the shared referee connection. Uncertain ownership still requires review; process exit alone is not proof that a room closed.
• Keeps provider rate limits and authority checks in place. Uncertain dispatched requests, invalid authorization and corrupt state are not silently retried as ordinary chat delays.
• Validation covered 179 affected checks, full-catalog installed donor retry/failure/shutdown scenarios, and restored owner gameplay. Unchanged full suites were not repeated. The subsequent independent dev10 session completed four Standard and three 4K maps before the reported chat failure. Commands, votes, skip and READY/AFK acceptance were not completed in that session.

• Fresh stopped installations can perform read-only ownership review before the service unit exists.
• Supported stopped room-settings configuration preserves existing unrelated settings and rejects unsupported topology changes.
• Catalog inspection avoids a duplicate full verification within the same call while retaining integrity checks.
• Network and feedback diagnostics distinguish local capture, upload acknowledgment and shared-snapshot use. Enrollment and a connected heartbeat do not prove that a vote reached the hub.
• The dev10 operator-onboarding batch introduced OWNER_HUB_UPGRADE.md for exact-kit, state-preserving upgrades on their existing stopped instance. Keep authorization, catalogs, chosen titles, ratings and enrollment. Resolve any old uncertain room ownership first; no reinstall or repeated enrollment is needed. This shared-runtime repair requires a stopped upgrade.

• Four owner rooms are back online: Standard automatic, Standard fixed, Mania 7K and Mania 4K. Discord panels and website live links follow their current room IDs.
• State-preserving upgrades retain compatible authorization, room settings, prepared catalogs and historical feedback rather than reinstalling or resetting them.
• Independent operators use their own local credentials. The central hub provides authenticated enrollment, directory heartbeats, optional feedback exchange and verified snapshots; prepared signed catalogs are downloaded separately.
• Active diagnostics can inspect the running installation without competing for its hosting-account lock. Startup, account changes and recovery keep exclusive ownership protection.

• Restores native chat/referee integration, connection recovery and preserved owner configuration behavior through the pilot repair batches.
• Prevents a lone READY player who uses .start and then withdraws READY from consuming the upcoming map when the countdown expires. Initial explicit solo starts remain available.
• Fixes staff-list persistence and live reload while retaining existing identity and role checks. Admins inherit moderator access.
• Corrects explicit authorized shutdown so occupied rooms can close cleanly; ordinary automatic update safety is not permission to interrupt occupied rooms.
• Stops repeated easier votes from pushing a fixed or recalled difficulty window below zero. Its width is retained, one harder vote reverses immediately, and unapplied easier votes do not accumulate hidden debt.
• Private test hosting supports a chosen password and explicit Discord-panel visibility without publishing the password. Private visibility stays off unless requested.

Live map cover IDs and displayed lengths use a separate public display index. The deployed shared components now include consenting community hosts on the homepage, Live Lobbies page and sidebar, with owner attribution/control and owner occupancy totals kept explicit. Unknown metadata has a neutral fallback; stale or unavailable remote data cannot break the owner display. The earlier homepage stylesheet compilation repair remains included.

Two independent-host vote uploads are confirmed, but shared-weighting gameplay, all-mode real gameplay acceptance and off-machine backup replication are not complete merely because the owner pilot is running. A contribution acknowledgment is not proof that a verified shared snapshot is active for map weighting.

Earlier repair artifacts remain historical; current dev12 operators follow TUNED_DEFAULTS_UPGRADE.md and the maintainer's exact qualified upgrade instructions. The tester repository is private and is not a public download or an invitation to reuse the owner's credentials.

v7 foundation · Community hosting and feedback · Updates and recovery · Readiness · Difficulty votes