feat(events): the integrations — lifecycle triggers, participants, results (Phase 10)

`EVENTS_PLAN.md` Phase 10. Core registers its own `event.` triggers, records who
took part, publishes a results table, and announces a post through the legs the
news pipeline already uses. Events owns none of the delivery: a run says what
happened and an operator's rule decides who is told, so email, the in-app inbox,
push tickles, Discord and the town crier all arrive without anything in
`events/` growing a second delivery path.

**No route was added and nothing moved.** The whole surface is two more derived
fields on a run — `participants` and `resultsPublishedAt` — and a zero-line
`routes.manifest.json` diff proves it.

Seven triggers: six at ceiling `authenticated` / audience `subscribers`, exactly
where `news.post` sits, and `run.failed` at `admin` on both halves. Every one
keys its cooldown on the RUN. Two rules seeded, both off, under a third one-shot
key so a deployment that has already stamped the Team and news keys still gets
them.

**The phase's own defect was a promise nothing kept.** `EVENTS.md` §I says a
rehearsal runs for real "with announcements ceilinged to `staff`" — but a
ceiling is declared on the TRIGGER, and a rehearsal fires the same trigger as
the real thing, so the moment this phase gave a run something to announce,
rehearsing a published event would have mailed every subscriber. The emit
envelope now takes an optional `ceiling` and the send-time G24 gate applies
`meet(declared, emitted)`. It only narrows; two incomparable ceilings refuse
every rule rather than resolving to either.

`MODULE_API_VERSION` stays 1.10.0, amended in place — `main` declares 1.9.0, so
1.10.0 has not shipped and the org lead's 2026-09-03 rule applies for the third
time.

Three defects the live walk found, none visible to a unit test:

1. **A channel that reported success while reaching nobody.** The seeded
   `run.started` rule named `push`, because §8.5 and the plan both do. Push
   delivery joins `notification_subscriptions`, only ever written for an id the
   preferences screen offered push for — and it offers push only for a
   registered STREAM. So the tickle went nowhere every time while
   `pushChannel.deliver` answered "tickle published". `event.run.started` is now
   a stream as well as a trigger; the other six are not.
2. **A trigger's `description` reaches a recipient.** It is the structural
   projection's `intro` fallback, so `run.failed`'s line ending "Staff-facing."
   put those words in an administrator's own inbox item.
3. **`affectedRows` cannot tell an insert from an unchanged upsert.** The
   connector sends `CLIENT_FOUND_ROWS`, so a "was this new" flag would have
   counted every idempotent retried collect as a fresh participant.

And one caught before it shipped: ranking with a session variable is wrong here,
because `query()` takes a pool connection per call — the variable would be set
on one connection and read on another. A window function needs no session state.

## Verification

- `npm test --prefix server` — **1981 pass, 1 fail**, and that one
  (`botScore.test.js`) passes standalone at 18/18: a file-level flake under
  parallel load. Run with an empty `MODULES_DIR`, as CI does.
- `npm test --prefix client` — 362 pass, 0 fail. `npm run build` green.
- Zero-line `routes.manifest.json` / `routes.guards.json` diff.
- A live walk on a real rig: MariaDB, the site with no module, mailpit. The mail
  arrived, headed with the event's title and its start time in the shard's own
  zone; the rehearsal fired the same trigger and produced zero outbox rows where
  the real run produced three; `run.failed` reached the administrator's inbox
  and no player's; `core.announce.post` queued a second job without touching the
  news pipeline's back-pointer or `announced_at`; and `rankRun` and the upsert
  were run against real MariaDB 11.

## One thing for a reviewer, out of scope and not fixed

**Every `#swagger.description` in this repo is truncated in the generated spec.**
swagger-autogen does not honour a backslash-escaped apostrophe, so a description
is cut at the first `\'` — 175 of the 177 in `server/src/router/**`. It is
pre-existing and repo-wide. Only the one annotation this phase edits is fixed
here (a typographic apostrophe), because otherwise this phase's own addition to
it would be dead text. The rest wants its own change.

- [x] AI-assisted: Claude Code (Opus 5).

Docs: RunicGateway/docs#TBD.

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

🤖 Generated with [Claude Code](https://claude.com/claude-code)

server/test/eventsAdmin.test.js

@@ -49,6 +49,7 @@ const budgetDb = require('../src/model/events/eventRunBudget.db')
 // one missing stub here cost the run detail test ten seconds and said nothing
 // about the route it was testing.
 const resourcesDb = require('../src/model/events/eventRunResources.db')
+const participantsDb = require('../src/model/events/eventRunParticipants.db')
 const seriesDb = require('../src/model/events/eventSeries.db')
 const gatesDb = require('../src/model/events/eventPhaseGates.db')
 const activity = require('../src/model/activity/activity.model')
@@ -71,6 +72,7 @@ for (const [name, mod] of [
   ['settingsDb', settingsDb],
   ['budgetDb', budgetDb],
   ['resourcesDb', resourcesDb],
+  ['participantsDb', participantsDb],
   ['activity', activity],
 ]) {
   originals[name] = { mod, fns: { ...mod } }
@@ -353,6 +355,13 @@ function installStubs() {
 
   resourcesDb.forRun = async (runId) =>
     store.resources.filter((r) => Number(r.run_id) === Number(runId))
+
+  // Phase 10: a run's detail now carries its participants. Unstubbed this is the
+  // ten-second dead-port wait, for the sixth time in this feature — and it would
+  // 500 the run console rather than saying anything about the route.
+  store.participants = []
+  participantsDb.listForRun = async (runId) =>
+    store.participants.filter((p) => Number(p.run_id) === Number(runId))
 }
 
 // ── Fixtures ───────────────────────────────────────────────────────────────
@@ -427,7 +436,10 @@ test('the catalog serves the registry, callables stripped, with its vocabularies
   assert.equal(res.statusCode, 200)
   assert.deepEqual(
     res.body.actions.map((a) => a.id),
-    ['core.announce', 'core.wait', 'core.cue', 'core.lease'],
+    // Phase 10's two are the integrations (EVENTS.md §J): `core.announce.post`
+    // sends an article through the announce legs rather than a line, and
+    // `core.results.publish` ranks and stamps the run's participants.
+    ['core.announce', 'core.wait', 'core.cue', 'core.lease', 'core.announce.post', 'core.results.publish'],
   )
   for (const action of res.body.actions) assert.equal(action.perform, undefined)
   assert.deepEqual(res.body.risks, ['notify', 'inspect', 'change', 'irreversible'])
@@ -446,7 +458,7 @@ test('the catalog serves the registry, callables stripped, with its vocabularies
   // their own.
   assert.deepEqual(
     res.body.optionSources.map((s) => s.id),
-    ['core.options.legs', 'core.options.leases'],
+    ['core.options.legs', 'core.options.leases', 'core.options.posts'],
   )
   for (const s of res.body.optionSources) assert.equal(s.resolve, undefined)
 })
@@ -839,7 +851,19 @@ test('the board serves every registered action with its risk-class default, and
   assert.equal(res.statusCode, 200)
 
   const byId = Object.fromEntries(res.body.actions.map((a) => [a.id, a]))
-  assert.deepEqual(Object.keys(byId).sort(), ['core.announce', 'core.cue', 'core.lease', 'core.wait'])
+  assert.deepEqual(Object.keys(byId).sort(), [
+    'core.announce',
+    'core.announce.post',
+    'core.cue',
+    'core.lease',
+    'core.results.publish',
+    'core.wait',
+  ])
+  // `core.results.publish` is `inspect`, so like `core.wait` it arrives ENABLED:
+  // nothing in the game world changes and nobody is messaged, and an author
+  // should be able to place it without an admin first visiting this screen.
+  assert.equal(byId['core.results.publish'].enabled, true)
+  assert.equal(byId['core.results.publish'].changesWorld, false)
   // And `core.lease` is the one core action the default-off rule bites: it is
   // `change`, so a fresh deployment cannot borrow a value until an admin says so.
   // §K's sentence, applied to core's own verb rather than only to a module's.