The command inventory and feature inventory follow confirmed bot 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 command table and finder: syntax, direct aliases, mode restrictions, purpose, descriptions, and search terms.
• Verified command facts on individual command pages: examples, alias restrictions, permissions, and feature conditions.
• The feature inventory and its links to detailed articles and command references.
• The live version check and inventory freshness notice on the homepage, command pages, and release index.

The check runs every five minutes. An unchanged inventory creates no new article revisions or drafts. The live statistics and lobby sections use their separate five-minute data exporter.

Detailed explanations, diagrams, worked examples, troubleshooting, and historical patch-note summaries remain authored articles. Their Behavior reference records when that explanatory text was reviewed. A verified inventory does not imply every linked paragraph was rereviewed.

After a new verified inventory is published, a small draft job compares it with the previous verified manifest. It prepares a private release review packet for editors and maintainers: changed commands, features, style spellings, affected articles, source fingerprints, and suggested checks. It never publishes explanatory prose. Maintainers review the live behavior and save article changes as normal wiki revisions.

No writing model or API integration is enabled. The draft job uses templates and the reviewed manifest; it cannot establish behavior that the manifest did not describe.

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.

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.

Add a reviewed documentation manifest to a staged release as docs/wiki-manifest.json. It records player commands, syntax, mode-specific aliases, permissions, feature gates, timing, feature links, and source fingerprints. Validate it against that staged release before queuing deployment. The publishing service has wiki write access and no bot deployment or restart authority.

See the documentation health report for broken links and editorial review candidates.

See command reference, feature inventory, release history, and contributing.