v7.3.3 is running on the owner host and both community hosts. The owner now runs Catch on Lobby 1, a Taiko automatic-difficulty pilot on Lobby 3, and Mania 4K on Lobby 4. Lobby 2 remains reserved/private and stopped. Existing settings were preserved; the owner intentionally changed only Lobby 3's mode and activated the new signed catalog bindings. Current links and settings are on Live Lobbies.
The Taiko pilot's startup, chat access, map selection, queue, website artwork/settings and Discord panel are verified. Actual Taiko player gameplay has not yet been observed. Its NoMod normal-speed catalog and the latest Standard catalog are activated.
One community host's Standard transfer stopped at about 94%. Its configuration remained unchanged, but its independently pinned v7.2.6 recovery reader could not dispatch the newer controller contract. Completion through the already-installed v7.3.3 native entry resumed the verified partial download and restored its two intended rooms. Reporting, ratings and updater status are healthy. Bounded transfer retries and recovery-pin refresh are being validated for a follow-up release; those new changes are not yet published. The separate earlier pre-admission interruption test remains a documented limitation.
The release adds taiko-fixed and taiko-auto. Selection is normal-speed NoMod (NM) only. The prepared catalog contains 37,635 Ranked/Approved charts: 37,447 native Taiko charts and 188 conversions with official Taiko difficulty calculated from the original source file. Other statuses, unsupported modified variants and raw player research data are excluded.
Automatic difficulty uses Taiko profile PP and 16 aggregate calibration points derived from qualifying Taiko NM top-play exposure. The data cover 3,298 of 9,000 profiles; this is an exposure heuristic, not a skill, playability or enjoyment guarantee. Missing profile/calibration data leaves the configured range in effect.
Taiko ratings and personal statistics use a disjoint ruleset identity. Rating upload can succeed while shared-snapshot refresh is delayed; a displayed total comes only from a verified snapshot containing the vote. Retry and reconciliation work independently from gameplay and command handling.
H and I accepted R25 receipts verify Taiko content 71ececd64c6b8f3a34deed1008e0f80054c2e6de129add8a327ee2f3d3288f49 and the latest full Standard selection content 03928b8f8f5999bd7e0e7517007319abe4f4294e63f821479b547dffc3c04af9 (106,155 beatmaps).
Both normal installed paths verified settings, catalog references and intended running/stopped rooms while exercising booking protection, a waiting configuration edit, interrupted-download resume and automatic helper retry. Controller installation waits until all configured rooms are empty and bookings clear; empty siblings can drain separately and off slots remain stopped. The separate extra B pre-admission controller-interruption case failed and remains unaccepted; it is not claimed as recovered.
The hub, community Discord bridge and website deployments are verified. The Discord connection is live, but no owner Lobby 3 pilot or actual Taiko gameplay has been verified. Signed-feed delivery is active; downloaded or queued does not yet mean installed.