Fix WhatsApp Admin QR bind and show the scan prompt only after Bind.

Use a current WA protocol version, start the sidecar via local tsx with inherited proxy, and stop auto-opening the QR UI on unbound connecting.

Co-authored-by: Cursor <cursoragent@cursor.com>

interfaces/admin/static/js/i18n/messages-zh.js

@@ -793,9 +793,9 @@ export default {
   "wa.sessionUnbindConfirm": "将停止 sidecar 并删除本机 WhatsApp 登录态（state/auth）。之后需重新扫码绑定，确认继续？",
   "wa.sessionRebindConfirm": "将清除旧登录态并重新出二维码，确认继续？",
   "wa.sessionNotInstalled": "sidecar 未安装，请先运行 whatsapp_install.ps1",
-  "wa.sessionScanHint": "请用手机 WhatsApp → 已关联的设备 → 关联设备，扫描下方二维码。",
+  "wa.sessionScanHint": "请用手机 WhatsApp → 已关联的设备 → 关联设备，扫描下方二维码。码大约 20 秒过期，页面会自动换成新码，请扫最新一张。",
   "wa.sessionQrWaiting": "等待二维码…",
-  "wa.sessionQrStale": "二维码可能已过期，请点「扫码绑定」刷新。",
+  "wa.sessionQrStale": "当前码可能已过期，正在自动刷新新码…",
   "wa.lifecycle.unbound": "未绑定",
   "wa.lifecycle.bound_stopped": "已绑定（sidecar 已停）",
   "wa.lifecycle.bound_offline": "已绑定（离线重连中）",
@@ -806,6 +806,9 @@ export default {
   "wa.lifecycle.needs_rebind": "登录态失效（需重新扫码）",
   "wa.sessionPolling": "正在刷新状态…",
   "wa.sessionNeedsRebind": "WhatsApp 拒绝了当前登录态（disconnect=405 等）。请点「重新扫码绑定」，或在手机端删除旧的 oclaw 关联设备后再扫。",
+  "wa.sessionPairingFail": "WhatsApp 在出码前拒绝了配对（常见 405）。正在换新密钥重试；若持续失败，请检查代理/DNS 后点「扫码绑定」。",
+  "wa.sessionNetworkFail": "连不上 WhatsApp Web（证书/超时/ECONNRESET）。常见原因是 Clash fake-ip。请给 sidecar 设置 HTTPS_PROXY 或 AIA_WHATSAPP_PROXY_URL 指向本机混合端口后再启动。",
+  "wa.sessionRunnerWaiting": "sidecar 进程已起来，但 Baileys 还没写出状态（常见于 npx 卡住或无代理）。请稍候，或看 data/logs/whatsapp_sidecar.log。",
   "wecom.autoBind": "首条消息自动绑定",
   "wecom.autoBindRole": "自动绑定角色",
   "wecom.autoBindTenant": "自动绑定团队",