v7.1.13 — shared greetings and faster community replies

Published October18,2026UTC on GitHub and signed pilot metadata18. Existing hosts follow the exact v7.1.11 → v7.1.12 → v7.1.13 chain. Controller updates retain safe empty-room admission and do not interrupt occupied rooms. Xikeon's already-waiting v7.1.12repair still needs the one-time local activation described in v7.1.12; publication does not mean its rooms have restarted. The owner service was not restarted by this release work.

• Community hosts inherit the maintainer-approved personalized join greetings. Existing custom mappings, explicit empty opt-outs, silence and cooldowns remain.
• Optional player profile/top-score reads no longer sit on the room thread or the serialized command handler. One bounded read job per room applies results on the room thread and discards stale player/room results. READY and gameplay stay authoritative.
• Failed chat ACKs no longer postpone incoming reads through a shared retry timer. Local undispatched deferrals retry promptly; actual outages keep backoff and osu! pacing remains.
• Replies queue without sleeping gameplay for message spacing. Command replies keep their order and precede unsolicited reminder backlogs. Uncertain sends are never replayed; Discord routing and room/channel/expiry checks remain.
• Complete indexed local stats replicas already shipped in v7.1.11. Ready lookups now avoid a SQLite writer reservation. Totals refresh in the background around20minutes; current privacy authority is still required. Cold/unavailable results use the automatic follow-up reply from v7.1.12.

316frozen affected tests passed, with no skips. Separate full-catalog real-worker/RPC and protected root/service-UID upgrade checks passed. An invented-provider process test answered a command in about1.24seconds while a profile read remained blocked and the sibling4Kworker stayed alive. Concurrent local stats/visibility reads took roughly20–30ms with no HTTP or write reservation. These measurements are qualification results, not live latency promises.

The protected upgrade preserved configuration, credentials, defaults, catalogs, ownership, history, ledger rows/schema and opt-outs.89installer checksums passed; the source audit has zero unresolved findings. Storage/dependencies and wire format are unchanged. Full repository suites and new actual-provider gameplay were not run; real host activation is verified separately.

Use the GitHub installer asset and V7_1_13_OPERATOR_GUIDE.md. Existing hosts keep their installation and state; no new OAuth, enrollment or database rebuild is required. Stopped services and uncertain ownership remain fenced.

Runtime SHA256: 98bc2e7a9a127062d7bbff451dbef743395dfe3dfb3c8453a4b53e268fa3010c. Installer SHA256: 30d832632fb8b6f846ec8427ce19108370199671df030eed2baf69565f440ad1.