Differences

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

--- updates:v6_7_22 [2026/10/06 00:48] – Document scheduled v6.7.23 results intermission and refresh dated rollout status wikiadmin
+++ updates:v6_7_22 [2026/10/06 01:39] (current) – Document deployed v6.7.22, v6.7.23 rollout and persistent monitoring-path correction wikiadmin
@@ Line 1: / Line 1: @@
 ====== v6.7.22: Hot-loadable safe-update wait ======
-**Scheduled supervisor update — not yet live at the October 5, 2026, 17:47 PDT review.** All four rooms run the compatible v6.7.21 bridge; the durable maintenance job is waiting for all four rooms to be empty and idle. Initial activation is authorized only after all four lobbies are confirmed empty and idle.
+**Deployed:** the coordinated supervisor upgrade completed on October 5, 2026, at approximately 18:26 PDT after the guarded all-empty maintenance window. The hot-loadable five-second wait is active.
+**October 5, 2026, 18:38 PDT:** the shared supervisor is live on v6.7.22 with a five-second continuous empty-and-idle deployment wait. Rooms 1–3 are healthy and running v6.7.23; Room 4 is healthy on v6.7.22, waiting to update when empty. This is a dated observation, not a continuously updated deployment claim; see [[status:start|Live lobbies]] for current room versions.
 ===== What changes =====
@@ Line 12: / Line 14: @@
 Five seconds is the eligibility wait, not a promise that the complete handoff finishes within five seconds. Relisting, match countdowns, pre-countdowns and empty-difficulty resets are separate timers and are unchanged.
-===== Operator setting after activation =====
+===== Active operator setting =====
 File: ''/opt/poolrotator-runtime/instances/supervisor.json''
@@ Line 27: / Line 29: @@
 ===== Following compatible update =====
-[[updates:v6_7_23|v6.7.23 results-screen intermission]] is scheduled behind this supervisor upgrade. Its follow-on job waits for successful v6.7.22 activation and healthy workers, then submits a guarded ordinary per-room update. It does not bypass the all-empty infrastructure window or interrupt occupied rooms.
+[[updates:v6_7_23|v6.7.23 results-screen intermission]] was accepted for ordinary empty-safe rollout after successful supervisor activation. Rooms 1–3 have updated; Room 4 was waiting empty at the dated review. Occupied rooms are not interrupted.
 ===== Already-live duration tuning =====
@@ Line 33: / Line 35: @@
 [[updates:start|Release history]] · [[wiki:room_updates|Update safety]] · [[status:start|Live lobbies]]
+===== Related operational correction =====
+The release switch exposed an old path assumption in external monitoring: it looked for logs and ledgers inside the current code release rather than the persistent runtime. This caused a false UNHEALTHY notification and affected wiki live-status readings. The installed health/report collector and wiki exporter now read persistent runtime paths independently of release switches. All four rooms are detected again; 34 offline operations tests passed. This was a monitoring/exporter fix, not another numbered bot release, map-selection change or bot restart. Genuine API/rate-limit warnings remain visible and are not suppressed.