Differences

This shows you the differences between two versions of the page.

--- updates:v7_3_4 [2026/10/26 05:25] – v7.3.4 published recovery follow-up and verified Taiko presentation wikidocs
+++ updates:v7_3_4 [2026/10/26 06:56] (current) – Fix owner dashboard startup and record actual browser verification wikidocs
@@ Line 25: / Line 25: @@
 The owner L3 Taiko pilot has three completed scored matches and one earlier abort in live history; each completed match had one participant. This establishes observed gameplay, not full multiplayer or every-command acceptance. Website cards show current ruleset/settings, map art, players, queue and approximate timing; Discord omits map progress. If only hit length is available, the website labels it **Play length** rather than showing unknown length.
+===== Current deployment and website follow-up =====
+The owner and Strohm completed the normal automatic update to v7.3.4 with healthy intended rooms and preserved stopped slots. The owner verified all six unchanged catalog bindings and all 20 retained configuration files: only four room version stamps changed. The actual Taiko website/Discord card now matches the restored room, including artwork and qualified length.
+Xikeon's outgoing v7.3.3 controller entered ''update_maintenance_outcome_requires_review'' before incoming installation. Standard remains running; the already-drained 4K/7K rooms remain stopped. This is an unresolved deployment issue, not accepted automatic-upgrade success. No uncertain state has been cleared and no occupied room has been force-closed. A read-only local guard report has been requested because the existing recovery channel refused inspection.
+An independent website patch increases the owner status-request deadline from five to 15 seconds and preserves last-known identity/map/settings briefly, labelled as delayed. It never retains expired live player counts or playback progress. Semantic QuickJS tests cover reserved slots, transient failures, bounded expiry, newer offline observations and malformed data; the deployed compiled bundle is verified. No lobby restart was required.
+A further website-only correction fixes a JavaScript scope error that prevented owner status polling from starting and left cards showing “Status temporarily unavailable”. The actual served page now passes Chromium checks with no JavaScript errors, repeated successful status requests and all four slots rendered correctly. Five focused JavaScript tests passed. No lobby or service restart was required.