v7.1.11 — local shared player statistics

Published October 18, 2026 UTC on GitHub and the signed pilot channel (metadata sequence 15). The paired central hub is upgraded. The owner controller is queued; independent hosts receive the signed offer through their saved policy. Each controller waits for all configured rooms on that host to empty naturally. No occupied-room restart was requested by publication. Opt-outs, paused policies and deliberately stopped rooms remain effective. A signed offer, local queue and confirmed activation are separate events.

• Shared personal totals are stored as a complete indexed Standard/Mania replica, including players never looked up on that host. Ordinary aggregate snapshots refresh around every 20 minutes. Successful .stats replies use the familiar concise presentation, without backend/overlap explanations.
• Privacy checks run separately every 30 seconds with a 120-second lease. Hidden data and sharing/consumption opt-outs stay protected. A prolonged outage can make shared totals temporarily unavailable rather than expose stale visibility decisions.
• Complete measured data for the two current host projections was about 23 MB of local SQLite and 1.8 MB of compressed transfer pages per changed snapshot. Unchanged checks transfer metadata only; these are measured sizes, not a player cap.

• Authorized VPS-to-VPS bulk transfers have no artificial rate cap when both sides negotiate support. Old/unrecognized hubs retain conservative upload pacing. Request/page/storage/concurrency bounds, player anti-abuse rules and osu! API pacing remain.
• Background network/hub/catalog/release services use nice 17 and a common slice with a combined half-of-one-core CPU ceiling per machine. Native room workers remain outside it. Client units adopt this policy during their supported update/start.
• Old clients remain compatible with the new hub; new clients retain legacy query, cache and receipt support with old hubs. Existing credentials, settings/defaults, catalogs, enrollment, history, privacy and update policies are preserved.

173 affected checks passed against the frozen runtime; a broader 222-test related regression batch also passed (overlapping cases). Qualification includes protected full-catalog upgrade preservation, root/service-user guards, mixed-version HTTPS checks, complete replica import at the actual CPU limit, shared CPU probes and standalone protected hub startup/shutdown. Source audit has no unresolved findings; installer extraction/checksum/tamper checks passed. Whole-repository discovery, unchanged long gameplay suites and new actual-provider gameplay tests were not repeated.

Use the installer asset from the release, not GitHub's source ZIP. Existing healthy opted-in hosts use their signed updater. Preserve state on an uncertain outcome and use the protected status/support/ownership tools. The release's V7_1_11_OPERATOR_GUIDE.md explains fresh installations, supported predecessors and recovery. Publication does not require a new OAuth sign-in or catalog rebuild.

Runtime SHA256: 9750a3ee044db4aa852c4d3dfecb48838281ad237cad2e96d112983ea4ad8149.

Installer SHA256: 95b88ba3c1a6ca4e54481e7c2b4ae90a0d7aa440d3c7e00c206aef02bcdbbf3f.