fix(rust): protocol 13 step 2 — expiry, plugin loads, the loading hold, NPC names, the link fleet (F2 F5 F6 F7 F8 F13 F14)

The module's half of PLAN_FIXES §6 step 2 (decisions D181-D185, docs#288).

- F13/F14 (D170, D183): `world.expired`, recognisable from protocol 13 by its
  `what`, is handed to core as the resource the zone step ledgered
  (`world`, `<serverId>:<id>`) through ctx.events.expired, which records it
  `expired`. coreApi moves to ^1.11.0 (website#209).
- F8 (D184): `plugin.loaded` / `plugin.unloaded` mark the permission sync dirty
  when the plugin added or removed permissions, so an unresolved grant lands on
  the next tick instead of the fifteen-minute audit.
- Catalogue: plugin.loaded/unloaded, world.expired and lease.expired are staff
  kinds. The last two were never classified (default deny kept them off public
  pages); the test now covers every event kind through protocol 13.
- F7: permission and title pushes hold while the stored hello says
  `worldReady: false` (a human's "sync now" does not); a failed or refused
  permission sync now logs at warn.
- F2 (D185): the killfeed names an NPC attacker — a family (Scientist, Bandit
  guard, Bradley APC…) or the prefab without its variant digits (wolf2 → Wolf).
- F5/F6: a link code is asked of the servers that minted one in the last six
  minutes first, then of the rest, each group in parallel; "unsure" only when
  one of the minting servers is unreachable.
- D182: the admin server list carries the ZoneManager helper's state from the
  hello, and the servers page says what a missing or failed helper costs.

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

server/eventWorld.js

@@ -177,6 +177,31 @@ function splitRef(ref) {
   return colon <= 0 ? { serverId: null, id: text } : { serverId: text.slice(0, colon), id: text.slice(colon + 1) }
 }
 
+/**
+ * A zone the plugin erased at its deadline (`world.expired`, PLAN_FIXES F13, F14).
+ *
+ * D96 said the website maps this frame to nothing and learns of it through
+ * `reconcile` and `revert`. The first player walk showed what that costs: three
+ * zones expired in the game on time and sat `confirmed` on the run console until
+ * the runs were cancelled, when teardown found them "already gone" and called that
+ * a success. D170 changed it, and D183 put the record in core: the resource row is
+ * marked `expired`.
+ *
+ * Until protocol 13 this frame could not be recognised at all — the plugin wrote
+ * the zone's kind over the frame's — so `what` is new with it, and a frame without
+ * an `id` names nothing to expire.
+ */
+function expired(serverId, frame) {
+  if (!serverId || !frame || frame.id === undefined || frame.id === null || frame.id === '') return false
+  try {
+    core.expireEvent({ kind: OWNED_KIND, ref: refOf(serverId, String(frame.id)) })
+  } catch (err) {
+    log.warn('could not tell core a zone expired', { server: serverId, id: frame.id, error: err.message })
+    return false
+  }
+  return true
+}
+
 /** Resources grouped by the server each one is on. */
 function byServer(resources) {
   const groups = new Map()
@@ -658,5 +683,6 @@ module.exports = {
   revert,
   reconcile,
   observeServer,
+  expired,
   resetWatch,
 }