feat(events): an event action's progress() on a live run's public page (MODULE_API 1.12.0)

An event action may declare an optional `progress(envelope)`: how its
step stands while the run is live. Core accepts two shapes and
interprets neither:

- a count: { label, left, of }, rendered "Bandits: 3 of 8 left";
- a percentage: { label, percent }, rendered "The Juggernaut: 62%".

How core asks:

- `events/progress.js` asks each step of a live run whose action has
  one. It passes the step's own held ledger rows and the reader's
  account id, so the module applies its own visibility.
- Each call has a 2 s deadline. A throw, a late answer or any other
  shape is a line not shown, never an error on the page.
- One answer per run and reader is cached for 5 s.
- The public event's live occurrence carries the lines as `progress`.
  The route takes an optional session for the reader.
- The page renders them under the phase label and re-reads them every
  15 s while the event is live.

Core stays game-agnostic: no game's words are in it. Additive, so a
minor bump. Module-uo declares ^1.10.0, registers no action with
progress(), and its actions and pages are unchanged.

From RunicNPC stage 8 (D304, D305).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

server/src/modules/version.js

@@ -9,6 +9,13 @@
 // Deliberately separate from PROTOCOL_VERSION (which versions the shard wire and
 // has nothing to say about a website module) and from any module's own version.
 
+// 1.12.0 — an event action may declare `progress(envelope)`: how a live run's
+// step stands, for its public page (docs/website/EVENTS.md §I; RunicNPC D304,
+// D305). Core accepts two shapes, `{ label, left, of }` and `{ label, percent }`,
+// puts them in the public run as `progress` and renders them as text it does not
+// interpret. Optional and additive, so minor: Module-uo declares `^1.10.0` and
+// registers no action with it, so its actions and pages are unchanged.
+//
 // 1.11.0 — `ctx.events.expired({ kind, ref })`, and `expired` as a resource
 // ledger status (docs/website/EVENTS.md §L; Rust PLAN_FIXES D183). A game that
 // ends something at its own deadline — a Rust zone erased when its time is up —
@@ -167,6 +174,6 @@
 // an admin action a module performs belongs in core's one audit log, the
 // extension slot needs the user its prefix names, and §2.7 forbids a module
 // reading core's `APP_BASE_URL` for itself. Additions only, so minor.
-const MODULE_API_VERSION = '1.11.0'
+const MODULE_API_VERSION = '1.12.0'
 
 module.exports = { MODULE_API_VERSION }