audit 4: log paging at its edges, NaN refused, a red rate limit, recalculation asks, reload writes all

Step 4 of stage 4 (L10, L11, L13, L18, L19 and a row of
review-2026-08-followups):

- The Outbound log counts first and clamps the page to the last; a number
  too large for an int (strconv's ErrRange with the largest int) is the
  last page on both logs. Tested at the edges: first, last, past the last
  however far, nonsense, an empty log asked for page 5.
- checkAutoMultiplier is "not within", so NaN and the infinities are out.
- rate-limited is red (components.go; the mockup first, 643892a).
- data-unsaved on both recalculate buttons: panel.js asks on submit
  (ev.submitter) when a field of the page differs from what it was drawn
  with; testdata/unsaved_test.js under TestPanelJS.
- HandleReload writes what a restore's first start writes - the filter
  lists and the DMARC maps too - and a failed step is an error flash on
  Health that names it, not plain text; the success flash says what was
  written.

Tested on the test server: go vet + go test of 25 packages, make e2e (all
pass, 695 s) on this tree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/guide.md

@@ -473,11 +473,15 @@ readings, in the order of what stops mail first:
   record the internet publishes for this server's IP (forward-confirmed
   reverse DNS), see [Server-level DNS](#server-level-dns-ptrrdns); use
   *Re-check DNS* after changing DNS.
-- **Configuration** — the **Reload configuration** button re-applies OpenDKIM
-  tables and the Postfix sender map from the database (and inbound relay maps
-  when `INBOUND_RELAY_ENABLE=true`) — use it if daemons drifted from what the
-  panel shows after manual edits under `/data`. It does **not** rebuild DMARC
-  Postfix maps; a full restore Resync does (see [Restore](#restore)).
+- **Configuration** — the **Reload configuration** button writes again, from
+  the database, every file the panel keeps for the mail path - OpenDKIM's
+  tables, the Postfix sender map, the inbound relay maps and the filter lists
+  (with `INBOUND_RELAY_ENABLE=true`), the DMARC report maps (with
+  `DMARC_REPORTS_ENABLE=true`) - and has OpenDKIM and Postfix re-read them:
+  what the first start after a restore does (see [Restore](#restore)). Use it
+  if the daemons drifted from what the panel shows after manual edits under
+  `/data`. A step that fails is named on the page, and the panel's log says
+  why.
 
 ### Queue and System log
 
@@ -817,8 +821,8 @@ when `INBOUND_RELAY_ENABLE=true`; DMARC maps when `DMARC_REPORTS_ENABLE=true`)
 and both daemons are reloaded, healing any drift between the extracted files and
 the database. The manifest is deleted only after that Resync is done: a first
 start that fails on the way leaves it, and the next start is a restore again
-and runs the Resync. The *Reload configuration* button on Server › Health resyncs
-OpenDKIM, the sender map, and inbound maps only — not DMARC maps. This is why the
+and runs the Resync. The *Reload configuration* button on Server › Health runs the same Resync.
+This is why the
 compose file pins a fixed tag rather than `:latest`: without a known version,
 there'd be no way to tell which image restoring a given backup actually requires
 (see [Fixed image tag](#fixed-image-tag)).