virlow-mcp 3.14.3 → 3.14.4

package/dist/cli.js

@@ -120,7 +120,7 @@ var VirlowApi = class {
 // ../../packages/mcp-core/dist/vault.js
 var LockedError = class extends Error {
 };
-var Vault = class {
+var Vault = class _Vault {
   autoLockMs;
   _session = null;
   _timerHandle = null;
@@ -177,10 +177,50 @@ var Vault = class {
     }
     return this._session;
   }
+  /**
+   * The largest delay `setTimeout` can actually hold: a 32-bit signed integer
+   * of milliseconds, about 24.9 days.
+   */
+  static MAX_TIMEOUT_MS = 2147483647;
+  /**
+   * Arm the auto-lock, unless the configured delay cannot be one.
+   *
+   * The guard is the whole point. `setTimeout` does not treat an out-of-range
+   * delay as "later" or as an error — it coerces it to **1 millisecond** and
+   * fires:
+   *
+   *   TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed
+   *   integer. Timeout duration was set to 1.
+   *
+   * So `new Vault(Number.POSITIVE_INFINITY)`, which reads as "never auto-lock,
+   * something else owns the timeout", locked the vault a millisecond after
+   * every unlock and every touch. The hosted connector is built exactly that
+   * way — its session store owns the idle timeout — and the result was a vault
+   * that reported itself unlocked on the request that opened it and locked on
+   * every request after:
+   *
+   *   status        -> {"locked": false, "email": "..."}
+   *   list_folders  -> "Vault is locked."   (2 seconds later, same session)
+   *
+   * Nothing in the store was wrong, which is what made it so hard to see: the
+   * session was found on every request, and the vault built from it had already
+   * locked itself. touch() re-armed the same 1ms timer, so activity made it
+   * worse rather than better.
+   *
+   * A delay that cannot be scheduled therefore means no auto-lock at all, which
+   * is what every caller passing one intends. Zero and negatives are the same
+   * case — a vault that locks on the next tick is not a security posture, it is
+   * a broken one — and a caller wanting an immediate lock has `lock()`.
+   */
   _scheduleAutoLock() {
+    const ms = this.autoLockMs;
+    if (!Number.isFinite(ms) || ms <= 0 || ms > _Vault.MAX_TIMEOUT_MS) {
+      this._timerHandle = null;
+      return;
+    }
     this._timerHandle = setTimeout(() => {
       this.lock();
-    }, this.autoLockMs);
+    }, ms);
     this._timerHandle.unref?.();
   }
   _clearTimer() {
@@ -1881,7 +1921,7 @@ function startUnlockServer(api, vault, opts = {}) {
 }
 
 // src/version.ts
-var VERSION = true ? "3.14.3" : "dev";
+var VERSION = true ? "3.14.4" : "dev";
 
 // src/server.ts
 function defaultEmbeddingCacheDir() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "virlow-mcp",
-  "version": "3.14.3",
+  "version": "3.14.4",
   "description": "Local MCP server for Virlow Secure Notes: end-to-end-encrypted AI memories and notes for Cursor, Claude, Codex, and any MCP client.",
   "license": "MIT",
   "type": "module",
@@ -34,9 +34,9 @@
     "esbuild": "^0.25.0",
     "typescript": "^5.8.0",
     "vitest": "^3.0.0",
-    "@batalabs/virlow-crypto": "3.14.3",
-    "@batalabs/virlow-memory": "3.14.3",
-    "@batalabs/virlow-mcp-core": "3.14.3"
+    "@batalabs/virlow-crypto": "3.14.4",
+    "@batalabs/virlow-memory": "3.14.4",
+    "@batalabs/virlow-mcp-core": "3.14.4"
   },
   "scripts": {
     "build": "node build.mjs",