docs(website): the engagement release note — three things that arrive switched off #199

wtclaude · 2026-09-01T13:36:02Z

wtclaude commented

2026-09-01 13:36:02 +00:00

The cutover's operator-facing note, written into the home Phase 1 created (website/UPGRADE_NOTES.md). Phase 13 owes it, and two earlier phases named it as their own obligation: Phase 6 for the Team rules (decision 3) and Phase 11 for news.post (§7.1 Q9). Both stop mail or push that is sending today, and neither says anything when it does.

Three required actions, ordered

Update the shard. The protocol pin lives in the UO module's schema, so it is the module update — not the core one — that moves uo_link_config.protocol to 5 and starts the site sending X-UOLink-Version: 5. A shard still on 4 answers 409 from that boot on. The note names the out as well: update the site and leave the module until the shard host can be reached.
Team email arrives disabled — four rules, the screen's own banner, and the fact that only email moved (the push tickle and the Discord bridge are untouched).
News push stops until the seeded rule is switched on.

Four behaviour changes that need no action

The unsubscribe link now narrows to one channel rather than muting outright; email and push are opt-in while the in-app inbox is on; a rule is checked against its trigger's audience ceiling; a bounce now suppresses an address, with Suppressions the only screen that lifts one.

Two claims checked against the tree, one of them wrong first time

coreApi is enforced at load, not at install (modules/loader.js:594), so an old core does not refuse the 0.5.0 install — it accepts it and then fails to load the module. The note says that, and says the restart is required, because modules are read from disk at boot.

The Data section carries Phase 12's finding 2 rather than burying it: nothing in this schema expires on its own.

Part of engagement Phase 13 (the cutover). This lands on edge first so the docs cutover PR carries it.

AI-assisted: written with Claude Code.

The cutover's operator-facing note, written into the home Phase 1 created (`website/UPGRADE_NOTES.md`). Phase 13 owes it, and two earlier phases named it as their own obligation: **Phase 6** for the Team rules (decision 3) and **Phase 11** for `news.post` (§7.1 Q9). Both stop mail or push that is sending today, and neither says anything when it does. ### Three required actions, ordered 1. **Update the shard.** The protocol pin lives in the *UO module's* schema, so it is the **module** update — not the core one — that moves `uo_link_config.protocol` to 5 and starts the site sending `X-UOLink-Version: 5`. A shard still on 4 answers `409` from that boot on. The note names the out as well: update the site and leave the module until the shard host can be reached. 2. **Team email arrives disabled** — four rules, the screen's own banner, and the fact that *only email moved* (the push tickle and the Discord bridge are untouched). 3. **News push stops** until the seeded rule is switched on. ### Four behaviour changes that need no action The unsubscribe link now narrows to one channel rather than muting outright; email and push are opt-in while the in-app inbox is on; a rule is checked against its trigger's audience ceiling; a bounce now suppresses an address, with Suppressions the only screen that lifts one. ### Two claims checked against the tree, one of them wrong first time `coreApi` is enforced at **load**, not at install (`modules/loader.js:594`), so an old core does not refuse the 0.5.0 install — it accepts it and then fails to load the module. The note says that, and says the restart is required, because modules are read from disk at boot. The Data section carries Phase 12's finding 2 rather than burying it: **nothing in this schema expires on its own.** --- Part of engagement **Phase 13** (the cutover). This lands on `edge` first so the `docs` cutover PR carries it. - [x] AI-assisted: written with Claude Code.

wtclaude added 1 commit 2026-09-01 13:36:04 +00:00

docs(website): the engagement release note -- three things that arrive switched off c57c0e6b37

The cutover's operator-facing note, in the home Phase 1 created. Phase 13 owes it, and
two earlier phases named it as their own obligation: Phase 6 for the Team rules
(decision 3) and Phase 11 for news.post (7.1 Q9). Both stop mail or push that is
sending today, and neither says anything when it does.

Three required actions, ordered, because the order is load-bearing:

  1. Update the shard. The protocol pin lives in the UO module's schema, so it is the
     MODULE update -- not the core one -- that moves uo_link_config.protocol to 5 and
     starts the site sending X-UOLink-Version: 5. A shard still on 4 answers 409 from
     that boot on. Named explicitly, along with the out: update the site and leave the
     module until the shard host can be reached.
  2. Team email arrives disabled -- four rules, the screen's own banner, and the fact
     that only email moved (the tickle and the Discord bridge are untouched).
  3. News push stops until the seeded rule is switched on.

Four behaviour changes that need no action: the unsubscribe link now narrows to one
channel rather than muting outright, email and push are opt-in while the in-app inbox
is on, a rule is checked against its trigger's audience ceiling, and a bounce now
suppresses an address with Suppressions the only screen that lifts one.

Two claims were checked against the tree rather than the plan, and one of them was
wrong first time: coreApi is enforced at LOAD, not at install, so an old core does not
refuse the 0.5.0 install -- it accepts it and then fails to load the module. The note
says that, and says the restart is required, because modules are read from disk at boot.

The Data section carries Phase 12's finding 2 rather than burying it: nothing in this
schema expires on its own.

AI-assisted: written with Claude Code.

Co-Authored-By: Claude <noreply@anthropic.com>

wtclaude referenced this pull request

2026-09-01 13:44:38 +00:00

docs: the engagement workstream — cutover 1 of 7 (`edge` → `main`) #200

whitlocktech approved these changes 2026-09-01 13:50:40 +00:00

whitlocktech merged commit bb0e262be2 into edge

2026-09-01 13:50:49 +00:00

whitlocktech referenced this issue from a commit

2026-09-01 13:50:50 +00:00

Merge pull request 'docs(website): the engagement release note — three things that arrive switched off' (#199) from docs/engagement-phase-13-upgrade-notes into edge

whitlocktech deleted branch docs/engagement-phase-13-upgrade-notes

2026-09-01 13:50:50 +00:00

Sign in to join this conversation.