Phase 16c of the events plan. The landing page is updated when the shape of the
project changes, and a subsystem that lets staff schedule an unattended change to
a live game world is one.
* **A new bullet in "How they fit together"**, beside the engagement one it sits
next to: an event is written once as phases and steps, published as an
immutable version and executed unattended. What matters on a front page is the
posture rather than the feature list — everything arrives switched off, caps are
enforced in the database rather than in a role check, cleanup is generated from
a ledger rather than authored, and an event does not edit the world but holds a
**lease** the game restores on its own deadline even if the site never speaks to
it again. The game keeps its own switch, separate from the staff write plane.
* **Protocol 5 → 7** in the four values the installer prints. That block is what a
reader copies into Admin → Shard, so a stale number there is the one that costs
somebody an afternoon.
* **module-uo v1.1.0 → v1.2.2** in the manifest URL and the `MODULES=` line.
* `docs/website/EVENTS.md` added to "Where to go next".
Verified against the platform rather than assumed: the protocol number is
`link/sidecar/src/main.rs` and `servuo-plugins/overlay.toml` on `main`, and
v1.2.2 is the current Module-uo release, whose own notes name
`module-uo-1.2.2.json` as the manifest to paste.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4
