Differences

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

--- wiki:documentation_updates [2026/10/04 20:54] – Align player guides, command references, lobby behavior and translated summaries through v6.7.13 wikiadmin
+++ wiki:documentation_updates [2026/10/04 21:26] (current) – Explain deployed-worker inventory verification and distinguish the shared supervisor wikiadmin
@@ Line 1: / Line 1: @@
 ====== How documentation updates work ======
-The automatically managed command and feature inventories follow confirmed shared-release deployments. The bot's release manager must report a successful deployment, the active release must agree, and that release's documentation manifest must match its source fingerprints before verified facts are published.
+The automatically managed command and feature inventories follow the newest healthy **deployed room-worker release**, not just the shared supervisor's version. A fresh worker heartbeat must establish the running version, the immutable release must have passing sealed validation and compatible shared contracts, and its reviewed documentation manifest must match its source fingerprints before verified facts are published. A queued target is not deployment evidence.
+The shared supervisor still has its separate successful-deployment check. The preparation job reads only a read-only binding of sanitized public worker status; it does not read player databases, credentials or chat, import bot code, call osu! or operate the bot. It writes a short-lived root-owned deployment attestation for the wiki-only publisher. The publisher checks that attestation, source version, shared-supervisor link, page locks and ownership hashes before native revisions.
 ===== What updates automatically =====
@@ Line 12: / Line 14: @@
 ===== Rooms on different versions =====
-[[wiki:room_updates|Compatible per-room rollouts]] in v6.7 can leave lobbies on different versions. The verified inventory describes the reviewed release; an account-level version notice does not guarantee identical behavior in every room. A queued release can have authored release notes and an upcoming article without becoming the current verified command inventory.
+[[wiki:room_updates|Compatible per-room rollouts]] in v6.7 can leave lobbies on different versions. The verified inventory describes the newest reviewed release with healthy deployed-worker evidence, not a guarantee that every room has reached it. The freshness notice identifies that inventory version, the observed worker-version range and the shared supervisor separately. Check each room title for availability. A queued release can have authored release notes and an upcoming article without becoming the current verified command inventory.
 ===== What stays editorial =====
@@ Line 22: / Line 24: @@
 ===== When verification pauses =====
-A queued or failed deployment does not become current documentation. A new release without a reviewed manifest, a source fingerprint mismatch, unavailable deployment evidence, or an editing conflict keeps the previous inventory and shows verification pending. Older facts remain readable with their verified version identified.
+A queued or failed deployment does not become current documentation. Stale or unhealthy worker evidence, incompatible or altered sealed code, a missing reviewed manifest or linked article, a source fingerprint mismatch, changed/expired attestation, or an editing conflict keeps the previous inventory and shows verification pending. Older facts remain readable with their verified version identified. The legacy successful shared-release gate remains for installations without rolling workers.
 Maintainers resolve the cause and rerun the update. Automatically managed tables are protected against silent overwrites: changing one creates a conflict. Propose corrections through the manifest, or edit the ordinary explanation surrounding the table. Existing explanations and contributor edits outside the generated command table are preserved.
@@ Line 34: / Line 36: @@
 ===== Newer worker commands alongside the inventory =====
-The shared supervisor and individual room workers can have different versions. Maintainer-reviewed worker commands and behavior therefore appear as explicitly labeled editorial supplements in [[commands:start|the command reference]] and [[wiki:worker_features|the room-worker feature guide]], with detailed guides and minimum-version labels. The command finder includes that authored supplement as well as the generated table. This does not bypass the automatic publisher's shared-release, fingerprint or editing-conflict checks, and does not claim that every room already runs the latest worker.
+Maintainer-reviewed future commands can appear as explicitly labeled editorial supplements in [[commands:start|the command reference]] and [[wiki:worker_features|the room-worker feature guide]], with detailed guides and minimum-version labels. The finder combines the supplement and generated table without duplicate cards. Once a reviewed release is deployed and verified, its commands and facts enter the generated inventory automatically. This never bypasses fingerprint, deployment or editing-conflict checks and does not claim that every room runs the latest worker.