feat: passphrase change and account recovery (auth-confirm)

The passphrase derives two independent client-side values: auth_key (the
hub verifier) and bundle_key (AES-GCM key for the per-node identity
bundles, which live on nodes and never on the hub). Changing or
recovering a passphrase is therefore two operations — swap the hub
verifier, and re-wrap every reachable node's identity bundle.

Flow A — change a known passphrase (Profile page)
- POST /v1/users/password re-proves the current passphrase, swaps
  pw_hash/salt/version, revokes every refresh token and returns a fresh
  pair so the tab that made the change stays signed in.
- MeshBayTransport.rewrapAllNodes: for every group's online node, connect
  with the old key, read the identity off the handshake, store it back
  under the new key. Returns updated / unreachable / failed so the UI can
  point at the operator-unpin fallback for the gaps. Always-shown
  confirmation dialog listing reachable and unreachable groups.

Recovery key
- keyderive.js generateRecoveryKey (32 random bytes, grouped Base32) and
  deriveRecoveryKey (HKDF-SHA256, domain meshbay:recovery:v1:<username>).
- Every per-node identity gets a second copy wrapped under the recovery
  key: keypair_bundles.bundle_enc_recovery (node-only column, added in
  _SCHEMA_KEYPAIR and via a PRAGMA-guarded ALTER for existing DBs),
  carried on keypair_bundle_store / _resp. MNP 0.13 -> 0.14, additive.
- session.recoveryKey is persisted in IndexedDB (slot rk) and lazy-loaded
  on connect, so a group joined in any later session still leaves a
  recovery copy.
- Shown once at registration; optionally folded into the verification
  e-mail as a pass-through the hub never stores or logs, with an opt-out.
- Profile -> Recovery key re-loads R and backfills every reachable node
  via rewrapAllNodes in bundleKey mode (no passphrase re-entry).

Flow B — recover a lost passphrase (#/reset, linked from sign-in)
- POST /v1/users/password/reset-request {username, email}: both must be
  the pair on file, checked against the blind email_hash (never
  decrypted). A mismatch — wrong e-mail, unknown username, non-active
  account — takes the identical no-op path (no code, no mail, same 200),
  so it reveals nothing and cannot be used to spray reset mail from a
  username alone. 5/min, 1-hour single-use code.
- POST /v1/users/password/reset {username, code, new_auth_key}: same
  expiry / attempts / single-use checks as e-mail verification; revokes
  every session and deletes every registered device key so a stored one
  cannot sign back in past the reset.
- ResetPasswordPage: request code -> code + optional recovery key + new
  passphrase -> reset + sign-in -> fan-out. connect() falls back to the
  recovery-wrapped copy when the passphrase key cannot open bundle_enc.
  Without a recovery key: sign-in is restored and each group needs the
  operator-unpin fallback.

Supporting fixes (found in live testing)
- member unpin now also deletes the keypair bundle; connect() mints a
  fresh identity when handed a bundle it cannot open (unless _rewrapOnly,
  set by rewrapAllNodes), so a rejoin completes instead of dead-ending
  before the invite-code prompt.
- A browser with no bundle key gets a passphrase prompt on the group page
  instead of a "go back to the browser you registered on" message.
- RegisterPage / LoginPage / ResetPasswordPage trim the username so every
  key derivation matches the hub's stored form.

Docs: docs/auth-confirm.md. Locale keys across all ten catalogues.
Tests: test_password_change, test_password_reset, test_recovery_email,
test_recovery_key, test_rewrap_fanout, test_bundle_store_recovery, plus
additions to test_admin_ops_mnp and test_webrtc_transport. Hub suite 492
passed; node suite 741 passed (the lone test_packaging_units failure is a
pre-existing RPM-spec flake, reproducible on main).

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

1 files changed, 62 insertions, 0 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/locales/zh-CN.js b/packages/meshbay-hub/src/meshbay_hub/static/locales/zh-CN.js
index 8dff38f..fc141c2 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/locales/zh-CN.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/locales/zh-CN.js
@@ -29,6 +29,25 @@ export default {
   'login.loading': '正在登录…',
   'login.no_account': '还没有账户？',
   'login.register_link': '注册',
+  'login.forgot': '忘记密码短语？',
+  'reset.title': '重置密码短语',
+  'reset.request_intro': '输入您的用户名和账户的邮箱。如果二者匹配，重置码将发送至该邮箱。',
+  'reset.send_code': '发送验证码',
+  'reset.form_intro': '输入邮件中的验证码并设置新的密码短语。如果您有恢复密钥，请一并输入，以同时恢复对群组的访问。',
+  'reset.code': '重置码',
+  'reset.recovery_key': '恢复密钥（可选）',
+  'reset.recovery_key_hint': '如果没有请留空。没有它，您的登录会恢复，但每个群组都需要重新加入。',
+  'reset.new_pass': '新密码短语',
+  'reset.new_pass_repeat': '再次输入新密码短语',
+  'reset.submit': '重置密码短语',
+  'reset.working': '正在恢复您的群组身份…',
+  'reset.signin_restored': '您的登录已恢复。',
+  'reset.groups_restored': '您的群组身份已在所有可达节点上恢复。',
+  'reset.no_recovery': '您的群组身份未恢复。对于每个群组，请让其运营者取消对你的固定并发送新的邀请码，然后重新加入。',
+  'reset.needs_operator': '这些群组仍需处理——请让每位运营者取消对你的固定并发送新的代码：',
+  'reset.go_app': '前往应用',
+  'reset.back_to_login': '返回登录',
+  'reset.err_unsupported': '重置密码短语需要浏览器的加密模块，此处不可用。',
 
   // Register
   'register.title': '注册',
@@ -40,6 +59,16 @@ export default {
   'register.loading': '正在创建账户…',
   'register.has_account': '已经有账户了？',
   'register.login_link': '登录',
+  'register.recovery_title': '保存您的恢复密钥',
+  'register.recovery_intro': '如果您忘记了密码短语，此密钥可恢复您的群组身份。请将其保存在密码管理器或安全的地方——它只显示一次，且 hub 永远看不到它。',
+  'register.recovery_copy': '复制',
+  'register.recovery_copied': '已复制',
+  'register.recovery_warning': '如果您同时丢失了密码短语和此密钥，您的文件仍会保留在各自的节点上，但您将以新身份重新加入每个群组。',
+  'register.recovery_saved': '我已将恢复密钥保存在安全的地方。',
+  'register.recovery_continue': '继续',
+  'register.recovery_email_opt': '同时将此恢复密钥通过邮件发送给我作为备份',
+  'register.recovery_emailed': '副本也已发送至您的邮箱，与验证码在同一封邮件中。',
+  'register.recovery_not_emailed': '这未通过邮件发送。请立即保存——它只显示这一次。',
   'register.success_title': '验证您的邮箱',
   'register.success_msg': '验证码已发送至您的邮箱。请在下方输入以激活账户。',
   'register.go_login': '前往登录',
@@ -284,6 +313,36 @@ export default {
     other: '已固定 {n} 个',
   },
   'settings.node_pins_clear': '清除已固定的身份',
+  'settings.passphrase': '密码短语',
+  'settings.passphrase_hint': '更改此账户的密码短语。你的身份密钥会在其节点在线的每个群组上重新封装；对于节点离线的群组，之后需要重新加入。',
+  'settings.passphrase_change': '更改密码短语',
+  'settings.passphrase_current': '当前密码短语',
+  'settings.passphrase_new': '新密码短语',
+  'settings.passphrase_new_repeat': '再次输入新密码短语',
+  'settings.continue': '继续',
+  'settings.done': '完成',
+  'settings.passphrase_confirm_intro': '你的身份密钥现在将在其节点可达的每个群组上重新封装：',
+  'settings.passphrase_reachable': '现在更新',
+  'settings.passphrase_unreachable': '无法连接',
+  'settings.passphrase_fallback_note': '对于无法连接的群组，请让其运营者取消对你的固定并发送新的邀请码，然后重新加入。你的文件和消息不会丢失。',
+  'settings.passphrase_confirm_btn': '更改',
+  'settings.passphrase_working': '正在重新封装你的密钥…',
+  'settings.passphrase_done': '密码短语已更改。',
+  'settings.passphrase_needs_operator': '这些群组仍需处理——请让每位运营者取消对你的固定并发送新的代码：',
+  'settings.pw_too_short': '新密码短语至少需要 12 个字符。',
+  'settings.pw_mismatch': '两个新密码短语不一致。',
+  'settings.pw_same': '新密码短语必须与当前的不同。',
+  'settings.pw_wrong_current': '当前密码短语不正确。未做任何更改。',
+  'settings.recovery': '恢复密钥',
+  'settings.recovery_hint': '为每个群组添加一份用你的恢复密钥加密的身份副本。在你使用的每个浏览器中执行一次；没有它，一旦丢失密码短语就只能手动重新加入每个群组。',
+  'settings.recovery_loaded': '已在此浏览器中加载——新群组会自动覆盖。',
+  'settings.recovery_open': '输入恢复密钥',
+  'settings.recovery_input_ph': '粘贴你的恢复密钥',
+  'settings.recovery_submit': '添加备份副本',
+  'settings.recovery_working': '正在更新你的群组…',
+  'settings.recovery_done': '你的群组现在有了恢复副本。',
+  'settings.recovery_partial': '无法连接这些群组。稍后打开它们，或再次运行此操作：',
+  'settings.recovery_need_relogin': '请先退出登录再重新登录，然后重试。',
   'settings.danger': '删除账户',
   'settings.delete_hint': '这会从 hub 上删除您的账户、您的群组成员身份和您的通知，'
     + '并释放您的用户名。它无法触及存放在各个 node 上的内容：您上传的文件仍留在其运营者'
@@ -501,6 +560,9 @@ export default {
   'group.join_code_hint': '向邀请您的人索取一次性代码，并在此输入。'
     + '之后此浏览器即被认可，不会再次询问。',
   'group.join_code_btn': '加入',
+  'group.pass_title': '输入你的密码短语',
+  'group.pass_hint': '此浏览器尚未解锁你的密钥。输入一次密码短语即可在此打开你的群组。',
+  'group.pass_btn': '解锁',
 
   'notif.purge': '全部清除',
   'notif.title': '通知',