feat(rust): the kit weekend, linked rewards, reward messages and the kit warning (protocol 14)

PLAN_REDESIGNS §2, the Rust half (D164, D192, D332, D333):
- rust.template.kit_weekend (core registerEventTemplates, MODULE_API 1.13.0):
  inputs kit/minutes/message/delivery; one phase advance after the weekend,
  core.lease rust.group.permission default/<kit permission> + rust.kit.entitle
  linked. Steps only where the kit can use them; validated by the real core.
- rust.kit.entitle: recipients 'linked' (every linked player who has played
  on the server, no tally, refused past the bound), optional message ({kit})
  and delivery, stored per row (rust_perm_run_grants.notice*).
- perm.sync notices: the untold set to the picked account, keyed
  run:step:user, in the digest; the report's noticesTold marks them told.
- rust.options.grouppermissions notes a kit's permission rows via kits.uses
  (cached a minute per server; a failure is no note).
- duration: 'minutes' on rust.zone.open and rust.participation.open; the
  group-permission lease's value example is true.
- protocol 13 -> 14, coreApi ^1.13.0; ci/core-ref.json pinned to website#212's
  head while it is open; engagement-triggers.json regenerated (coreApi line).

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

server/index.js

@@ -59,6 +59,7 @@ module.exports = function register(ctx, api) {
   const eventLeases = require('./eventLeases')
   const eventWorld = require('./eventWorld')
   const eventRewards = require('./eventRewards')
+  const eventTemplates = require('./eventTemplates')
   const boot = require('./boot')
   const commands = require('./commands')
   /* eslint-enable global-require */
@@ -171,6 +172,11 @@ module.exports = function register(ctx, api) {
   api.registerEventBudgets([...eventWorld.BUDGETS, ...eventRewards.BUDGETS])
   api.registerEventActions([...eventWorld.ACTIONS, ...eventRewards.ACTIONS])
 
+  // The templates (PLAN_REDESIGNS.md §2.5, MODULE_API 1.13.0): a kit weekend
+  // as a starting point on core's New event screen. Core keeps nothing about a
+  // template; what it builds is an ordinary draft.
+  api.registerEventTemplates(eventTemplates.TEMPLATES)
+
   // News in game chat (D104). Core enqueues every registered leg for every
   // published post, so the leg itself sends only to the servers whose switch an
   // operator turned on — off by default, and a server that is down is skipped.