maxpool 1.8.7 → 1.8.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "maxpool",
-  "version": "1.8.7",
+  "version": "1.8.8",
   "description": "Multi-account Claude Code proxy with adaptive, rate-aware load balancing across Claude accounts",
   "type": "module",
   "main": "src/index.js",

package/src/account-manager.js

@@ -3689,6 +3689,12 @@ export class AccountManager {
       // Running version + npm update state (set at startup by maybeCheckForUpdate).
       // null until the check resolves; `current` is known even offline.
       version: this.versionInfo || null,
+      // The version whose CODE is EXECUTING. `version.current` is a package.json DISK
+      // read, so after a self-install (or on an npm-link'd checkout) it reports the
+      // newest INSTALLED build, not the running one — a post-deploy check keyed on it
+      // verifies the wrong thing (measured 2026-08-23: reported 1.8.7 while executing
+      // 1.8.6). This field is the one to assert on.
+      runningVersion: this.runningVersion || null,
       currentAccount: this.accounts[this.currentIndex]?.name,
       switchThreshold: this.switchThreshold,
       routing: {

package/src/index.js

@@ -33,7 +33,7 @@ import { loginOAuth, fetchProfile, refreshAccessToken, isTokenExpiringSoon, toke
 import { TUI } from './tui.js';
 import { RestartController } from './restart-controller.js';
 import { resolveAccounts } from './account-config.js';
-import { maybeCheckForUpdate, getCurrentVersion, markApplied, clearQuarantine } from './updater.js';
+import { maybeCheckForUpdate, getCurrentVersion, markApplied, clearQuarantine, getBootVersion } from './updater.js';
 import {
   runReloadBaton,
   RELOAD_SWAPPED, RELOAD_ROLLED_BACK,
@@ -1259,6 +1259,8 @@ async function serverWorkerCommand() {
       // pass the real config so they still respect the user's autoUpdate choice.
       const cfg = forceInstall ? { ...config, autoUpdate: true } : config;
       const r = await maybeCheckForUpdate(cfg, notifyUpdate, info => { accountManager.versionInfo = info; }, { announce });
+      // Capture the EXECUTING version for /maxpool/status (see AccountManager.getStatus).
+      accountManager.runningVersion = getBootVersion();
       apply(r);
       return r;
     } catch { return undefined; /* update path is best-effort; never break the proxy */ }

package/src/updater.js

@@ -85,6 +85,17 @@ let _lastAttemptedTarget = null;
 /** Test-only: reset the module's version-tracking state between cases. */
 export function __resetUpdaterState() { _bootVersion = undefined; _lastAttemptedTarget = null; }
 
+/** The version whose CODE this process is EXECUTING (captured at boot, before any
+ *  self-install can rewrite the disk). Everything user-facing that says "current"
+ *  should use THIS — a disk read reports the newest INSTALLED version, which after a
+ *  background self-install (or on an npm-link'd dev checkout whose package.json moves
+ *  with every commit) is not what is running. Measured 2026-08-23: the status endpoint
+ *  answered 1.8.7 for a process executing 1.8.6, and a post-deploy check keyed on that
+ *  number verified the wrong build. */
+export function getBootVersion() {
+  return _bootVersion ?? null;   // null only before the first maybeCheckForUpdate
+}
+
 /** Mark a version as ATTEMPTED-to-apply. The caller calls this at the moment it triggers
  *  the reload — BEFORE the reload — so a rolled-back target is quarantined (advance-only).
  *  Kept as the caller's action (not a side effect of maybeCheckForUpdate) so a caller that