The engagement cutover landed on 2026-09-01 and three things on this page stopped
being true with it.
The capability itself is the reason for the change: the site now talks to its
players, and an operator decides when. It is a headline capability by the org
lead's call, which is the condition ENGAGEMENT.md Phase 13 step 8 attaches to
touching this file at all -- a landing page that lists every feature is a landing
page nobody reads.
The bullet leads with the operator rather than the mechanism, and names the one
property that is a security boundary rather than a feature: a trigger declares
the widest audience a rule may ever be given, so a sensitive game event cannot be
mailed to everyone by a misconfiguration.
The other two are cutover outputs and would mislead an operator directly:
* the installer's sample output prints "Protocol version 4"; the paired bundle
is 2026.09.01 and the wire is 5.
* the quick start pins module-uo v1.0.1 in both the manifest URL and the
MODULES= line; v1.1.0 is the release that carries the shard triggers.
Co-Authored-By: Claude <noreply@anthropic.com>
