| Status | Published operator bootstrap; the independent host reports v7.0.6 at the October 15, 2026 Pacific review |
|---|---|
| Owner rooms | Remain v7.0.5 with a separate v7.0.7 repair queued; this bootstrap does not automatically upgrade the owner's controller |
Independent hosts can check the central executable-release feed, verify signed metadata and pinned public trust, and download a qualified compatible runtime. Release trust is separate from catalog verification and hub enrollment. The optional authenticated update report lets the maintainer distinguish discovery, download, waiting, installed and held states.
Automatic download, installation, controller maintenance and reporting are separate local choices. The supplied bootstrap policy starts paused with these choices off. Enrollment, a public listing or sharing map votes does not grant permission to install code. Signed publication is not evidence that a host has installed it.
Compatible worker-only updates can wait room by room. A shared-controller update requires every configured room healthy, empty and idle for at least 30 seconds, then private admission gates and at least a 15-second late-join drain with fresh ownership/roster checks. New players cancel admission. Saved settings, catalogs, credentials, ratings, history and enrollment are retained; previously running services return and the independent polling timer continues.
The saved feed interval is normally about 30 minutes, with jitter and backoff. A stopped bot is not started just to install an update. Paused consent, an unsupported migration, a trust change or uncertain ownership may still need local operator attention.
Installed v7.0.6 has a 90-second controller-admission timeout that can expire before the ordinary background timer gathers both required observations. It cancels safely but may keep waiting rather than finish the upgrade. The qualified v7.0.8 successor repairs that scheduling bound.
Receiving that first repair requires the maintainer-provided one-time local catch-up on the existing instance. It invokes the existing protected updater more frequently, preserves consent and unit definitions, retains all native admission checks and exits after the exact repair is installed. Keep existing state and coordinate that step with the maintainer; no reinstall, OAuth reset or forced closure of occupied rooms is required. Later routine compatible releases use the ordinary timer.
The pilot repository and existing release downloads are now public. Before changing visibility, the maintainer audited all 21 existing commits and 47 release assets, including nested archives and bundled catalog schemas. The review found no live credentials, private signing keys, private contact details or player-history tables. Public account handles and third-party attribution remain. GitHub secret scanning and push protection are enabled, and local secret/state ignore rules were added.
This publication changed documentation and visibility, not runtime bytes, release checksums, update consent or running lobbies. No new bot version was assigned merely for making the repository public. Public visibility does not select a new source license; consult the repository's SOURCE_POLICY.md and third-party notices.
Use the verified bootstrap release assets, not GitHub's automatically generated source ZIP, and follow the matching guide for the existing or fresh instance. Coordinate new pilot onboarding with the maintainer.
Qualification used full prepared catalogs, native installed worker/controller upgrades, occupied matches, cancellation, recovery/rollback, independent timers, a stopped donor reboot and real signed HTTPS transfer. Invented provider traffic is separate from actual osu! gameplay acceptance. Full unchanged research/calculator suites were not repeated.
Qualified distributed repair · Hosting overview · Update behavior · Release history