docs(events): the step editor and event templates — MODULE_API 1.13.0

The contract half of website feat/event-step-editor (Rust PLAN_REDESIGNS §2):
MODULE_API.md §1.1/§2.4 gain registerEventTemplates, a param's duration, a
lease's example and an option's note; EVENTS.md §F (the note), §I (what the
1.13.0 editor settled) and the API surface (the templates route, draftAhead).
PLAN_REDESIGNS §2.8 records the core half as built and the Module-uo proof.

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

modules/rust/PLAN_REDESIGNS.md

@@ -389,6 +389,26 @@ Author a kit weekend from the template on each rig; a lease step with the phase'
 shows); a draft edited after publishing (Start asks); a boolean lease (a toggle); and a Module-uo event opened
 in the same editor, which must be unchanged apart from the controls.
 
+### 2.8 As built: the core half (2026-10-12)
+
+website `feat/event-step-editor`, MODULE_API **1.13.0** (§8; `website/MODULE_API.md` §1.1, `website/EVENTS.md` §I).
+Everything in §2.1–§2.3 and §2.5's core half, with three things settled while building:
+
+- **The phase guard counts the RUN, not the phase.** Teardown gives a held thing back when the run ends, so
+  a 10-minute lease in phase 1 is safe if phases 2 and 3 take ten minutes between them. The floor is the sum
+  of every later phase's `after`; a phase with no rule counts as no time, and one that waits on the game makes
+  the floor unknown, so it is not warned about. Only a phase with **no** rule is given one, and only when a
+  change can create or lengthen a hold.
+- **"Is the draft ahead?" is answered by the server** (`draftAhead`): the working spec against the
+  published one, as data with keys sorted. A timestamp cannot answer it, because publishing writes the row too.
+- **A template's inputs are params**, checked by the same function, so they get the same controls, sources and
+  duration unit as a step's fields. The draft comes back unsaved, from
+  `POST /admin/events/catalog/templates/:templateId`.
+
+**The Module-uo proof**, against this branch: the frozen-manifest job (76 routes, all documented; `uo`
+registers its 12 actions), the server suite 723/723 and the client suite 45/45 — the same numbers as 1.11.0's.
+The Module-Rust half (the kit weekend, `linked`, `kits.uses`, the reward message) follows on `edge`.
+
 ---
 
 ## 3. Zones: ZoneManager's options, and a dome (§4.4; D166, D167)