feat: v2.5.5 — AI Router renamed AI Proxy, reload onto new builds, update no longer spins

AI Proxy (was AI Router):
- server/lib/ai-proxies.js, proxy-apply.js, routes/ai-proxies.js mounted at
  /api/ai-proxies and the old /api/ai-routers; `router` still accepted on the
  start routes; profiles move to <CLAUDE_HOME>/agenthub-proxies/
- dashboard_runs.router renamed in place to proxy: an older build on the same
  DB fails on that column, so dev and prod sharing one DB update together
- a proxy's baseUrl stored as its root (a typed /v1 made /v1/v1/messages);
  Test probes Claude /v1/messages and Codex /v1/responses
- Settings → AI Proxy (/settings/ai-router redirects), ProxyPicker

Updates:
- every tab reloads onto the new UI build when its WebSocket reconnects to a
  server of another version (lib/newBuildReload.ts, once per version)
- Update now stops waiting on a plugin chain that failed or pulled nothing
  (the old server never goes down), and reloads as soon as a new version answers

Also:
- a pane whose command exits at once says so (EPANEEXITED) instead of
  "Command failed: tmux set-option … mouse on"
- the pane drag preview draws where the pane actually lands

server/lib/data-transfer.js

@@ -233,7 +233,10 @@ function importExportBundle(db, bundle) {
     // Session-independent, config-like tables: restore by natural PK, never
     // overwriting a row the target machine already has.
     for (const r of Array.isArray(bundle.dashboard_runs) ? bundle.dashboard_runs : []) {
-      if (r && r.id && insert.dashboard_runs(r).changes > 0) counters.dashboard_runs++;
+      // `router` is the pre-rename name of `proxy`, in a bundle an older build exported.
+      const row =
+        r && r.router !== undefined && r.proxy === undefined ? { ...r, proxy: r.router } : r;
+      if (row && row.id && insert.dashboard_runs(row).changes > 0) counters.dashboard_runs++;
     }
     for (const r of Array.isArray(bundle.alert_rules) ? bundle.alert_rules : []) {
       if (r && r.id && insert.alert_rules(r).changes > 0) counters.alert_rules++;