v7.3.3 is published, but production acceptance is incomplete. One live host committed the new runtime registration and then held at configuration preparation before startup. Its configuration hashes are unchanged, and a guarded remote completion also refused. Local read-only diagnostic evidence is needed to identify the cause. This is distinct from the earlier pre-admission controller-interruption test.

Keep held state intact. Do not reinstall, clear ownership or repeat startup to bypass this guard. The owner update is deferred; the existing Catch and 4K rooms remain on v7.3.2. The selected Lobby 3 Taiko pilot and actual Taiko gameplay remain pending.

v7.3.3 is published on GitHub. The normal installed technical acceptance passed on H (v7.3.0) and I (v7.3.2), 2 of 2. A separate extra B pre-admission controller-interruption case failed before the incoming code could run; it remains unaccepted and is a known limitation. The signed pilot feed now offers v7.3.3 to supported existing hosts; safe automatic rollout is underway.

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.