fix(rust): protocol 13 — a configuration save that settles after its reload (F9, D179)

The plugin now answers a save once the files are written, with pending and
a writeId, and reports the reload later as a config.outcome event. The save
is recorded as reloading with a settle_by of two plugin ceilings plus slack
on the database's clock; ingest settles the row by (server, writeId), only
while it is still reloading, so a replay moves nothing and a late outcome
still lands. A row past settle_by reads as lost.

GET /admin/rust/config/:serverId/writes/:writeId serves the poll; the page
polls it every two seconds, holds the Save button while it waits, and says
whether a rolled-back plugin came back on its old file. config.outcome is
a staff kind: it carries the server's log tail.

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

server/catalogue.js

@@ -80,6 +80,10 @@ const STAFF_KINDS = Object.freeze([
   // changed it by hand — a question about a person's standing and about an
   // operator's own console, neither of which is a public page's business.
   'perm.drift',
+  // Protocol 13. How a configuration save's reload ended — and, when it failed,
+  // the tail of the game server's own log, which is an operator's console and
+  // can hold anything a plugin chose to print.
+  'config.outcome',
   // Protocol 6. Clan membership, which the org lead made members-only (D49):
   // who joined which clan, and who threw whom out, is the clan's business. It
   // reaches a clan's own members through core's Team feed, where core resolves