feat(hub): the mail bounds are settings, with a panel to change them

They were constants in two modules, so an operator could not touch them
without editing code and redeploying — and the hour a budget runs out is not
when anyone wants to do that.

`[mail]` in hub.toml carries the defaults; the live values live in
`hub_settings`, read at each use. A missing row falls back to what the
configuration file says, so an instance that never opens the panel behaves as
its file describes. The panel sends only what changed, the hub clamps each
value to a stated range and refuses a key it does not know, and the response
is what gets rendered — so a clamped value is never shown as stored.

`GET /v1/admin/mail` is the other half. There was no way to see any of this:
a refusal was a line in the journal, so an instance that had stopped sending
sign-up codes looked, from the panel, exactly like one with no sign-ups. It
reports the hour's use, what is left for sign-ups, and what is left for
recovery — the difference between those two being the reserved share made
visible.

Labels in all ten catalogues.

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

1 files changed, 13 insertions, 0 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/locales/en.js b/packages/meshbay-hub/src/meshbay_hub/static/locales/en.js
index 88ee3da..06b3626 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/locales/en.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/locales/en.js
@@ -476,6 +476,19 @@ export default {
   'admin.general_groups_heading': "Groups",
   'admin.allow_public_groups_label': "Allow members to create public groups",
   'admin.allow_public_groups_hint': "When off, new groups can only be private and invite-only. Existing public groups are left as they are — suspend them one by one from the Groups tab.",
+  'admin.mail_heading': "Outgoing mail",
+  'admin.mail_hint': "What this hub will send, and how much. The two that matter are the hourly budget, which no number of accounts can raise, and the daily cap per recipient, which is what someone being flooded actually experiences.",
+  'admin.mail_this_hour': "Sent this hour",
+  'admin.mail_remaining': "{general} left for sign-ups and address changes, {recovery} for passphrase resets and invitations.",
+  'admin.mail_hourly_budget': "Messages per hour (whole instance)",
+  'admin.mail_hourly_reserved_for_recovery': "Of those, reserved for resets and invitations",
+  'admin.mail_destination_daily_cap': "Messages per day to one recipient",
+  'admin.mail_destination_cooldown_seconds': "Seconds between messages to one recipient",
+  'admin.mail_verification_resend_cooldown': "Seconds between two sign-up codes",
+  'admin.mail_reset_cooldown': "Seconds between two passphrase-reset codes",
+  'admin.mail_email_change_cooldown': "Seconds before an account may propose another address",
+  'admin.mail_save': "Save mail limits",
+  'admin.mail_reset_defaults': "Restore defaults",
   'admin.settings_readonly': "Only an admin can change these settings.",
 
   // Admin stats