Table of Contents
v7.0.7 — owner room-retirement repair
| Status | Qualified and queued for the owner's all-three-rooms-empty controller window; not yet live at the October 15, 2026 Pacific review |
|---|---|
| Baseline | Exact owner v7.0.5 installation; this is not the operator v7.0.6 update bundle |
Finish normal room shutdown before escalating
A normally closing worker can disconnect its local communication channel just before its process exits. The old controller could treat that ordering as a fatal shared-service failure and close occupied sibling rooms. This repair gives native reconciliation the existing bounded 30-second cleanup window even when no explicit worker-error message was emitted.
A positively closed and reaped room can park independently. Unknown ownership is fenced immediately, and a disconnect or exit that cannot reconcile within the bound still fails. This avoids treating every normal retirement as a service-wide crash without assuming that an unknown room has closed.
Recognize a canceled old update safely
Controller admission recognizes a diagnostic target left by an exactly canceled, protected predecessor worker deployment only after its installation, generation, room alias, version, path and digest match. Unknown targets, active deployments, players, stale health and ownership uncertainty still block admission. The repair does not erase the live ownership journal to get past those checks.
Current owner rollout
The owner's fixed Standard, Mania 4K and Mania 7K rooms remain on v7.0.5 while this controller change waits for all three to become empty and idle together. The intentionally disabled automatic Standard room is outside that topology. Occupied rooms are not closed to create an update window, and existing settings, titles, authorization, Discord, website integration, catalogs and votes are preserved.
This owner-only artifact must not be installed over the independent operator's v7.0.6 runtime: it does not carry that runtime's complete automatic-updater files. v7.0.8 is the separately qualified distributed successor. A numerically newer owner repair is not automatically a compatible operator package.
Validation and limits
Affected liveness, terminal-event, maintenance and protected-update checks passed, followed by installed full-catalog donor qualification with invented external events. Checks cover normal retirement, occupied siblings, unknown ownership and canceled-target refusal/recognition. These results do not establish live deployment; the existing queue and fresh room status provide rollout evidence.
Current owner resilience release · Operator repair · Release history