feat(events): the step editor reworked, and event templates (MODULE_API 1.13.0)

Rust PLAN_REDESIGNS §2 (U-3-U-6, F11; D192, D334), core half. Game-agnostic:
Module-uo's steps get the new controls and nothing else.

Contract (MODULE_API 1.12.0 -> 1.13.0, four optional additions):
- api.registerEventTemplates([{ id, label, description, inputs, build }]):
  inputs are params (<= 8); core checks them, calls build() (10 s), validates
  the result as a spec and answers an unsaved draft.
  POST /admin/events/catalog/templates/:templateId (admin, editor).
- a param's duration: 'minutes' (int/float only); core.lease's minutes has it.
- a lease's example for its value.
- an option row's note (<= 300 chars), shown under the chosen field.

Editor:
- no type tags or bare asterisks; a required field says so in words once a
  save has been tried with it empty (and the save stops before the round trip).
- boolean: toggle when required, [Not set] [Yes] [No] when optional (D334).
- a choice of two or three is a row of buttons (lease values, small sources).
- core.lease drawn as the chosen lease: picked by label; value by the lease's
  type, range, values and example; target picker over target.source (F11);
  minutes with the lease's longest hold.
- a timed step keeps its run open: a phase with no advance rule gets
  after: <longest hold> when a timed step is added; a sentence under any phase
  whose run can end sooner (U-6).
- Start asks "Publish and start" or "Start version N" when the working copy is
  ahead of the published version (draftAhead on GET/PUT/publish; U-5).
- New event can start from a module's template.
- core's own examples name no game (§0.9).

Swagger, routes.manifest/guards and engagement-triggers.json regenerated.

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,20 @@
 // 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.13.0 — the event step editor (Rust PLAN_REDESIGNS §2; docs/website/EVENTS.md
+// §F, §I). Four additions, each optional:
+//   • `api.registerEventTemplates([{ id, label, description, inputs, build }])` —
+//     a named starting point for a new event; inputs in, an ordinary draft out,
+//     and nothing about the template kept in the definition (D192);
+//   • a param's `duration: 'minutes'`, so the editor can see a timed step and
+//     keep its phase open long enough for it;
+//   • a lease's `example` for its value, so a lease step shows that lease's
+//     example rather than core's one for every lease;
+//   • an option row's `note`, shown under the field while it is the chosen one.
+// Additions only, so minor. Module-uo declares `^1.10.0` and uses none of them:
+// its actions, leases and sources come out of the registry exactly as they went
+// in, and its steps render with the new controls and nothing else changed.
+//
 // 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 }`,
@@ -174,6 +188,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.12.0'
+const MODULE_API_VERSION = '1.13.0'
 
 module.exports = { MODULE_API_VERSION }