ai-lens 0.8.72 → 0.8.73

package/.commithash

@@ -1 +1 @@
-78b5c4c
+45d094e

package/CHANGELOG.md

@@ -2,6 +2,9 @@
 
 History of changes to the `ai-lens` CLI package on npm. New entries go on top. Format: `## X.Y.Z — YYYY-MM-DD`, followed by user-facing bullets.
 
+## 0.8.73 — 2026-05-29
+- fix: spooling an event now retries the atomic `rename` in `~/.ai-lens/pending/` a few times with a short backoff before giving up. On Windows, antivirus/Defender or the search indexer transiently locks the temp file and the rename failed with EPERM, silently dropping that event (observed in prod via the 0.8.70 error-code instrumentation). POSIX is unaffected (its rename is atomic and never hits this).
+
 ## 0.8.72 — 2026-05-29
 - fix: `status` no longer reports hooks as "outdated" when they already capture reliably. A hook is now considered current if it's GUI-safe — either the per-machine launcher (`run.sh`/`run.cmd`, including the transitional `sh -c` wrapper) OR a `capture.js` command with an absolute node path baked in (e.g. `/opt/homebrew/bin/node`). Only PATH-dependent forms (bare `node`, `/usr/bin/env node`) — which break for GUI-launched Cursor/Claude on macOS — stay flagged outdated so `init` rewrites them.
 - fix: `ai-lens status --report` now prints the full status to the screen just like plain `ai-lens status`, in addition to sending the report to the server. Previously it ran silently. The only difference from plain status is that it POSTs the report instead of writing the local `~/ai-lens-status.txt` file.

package/client/capture.js

@@ -1182,6 +1182,32 @@ export function normalizeEvent(event) {
 // Queue + Sender Spawn
 // =============================================================================
 
+// Windows (Defender / other AV, search indexer, file-locks) transiently fails an
+// atomic rename with EPERM/EACCES/EBUSY while another process briefly holds the
+// .tmp or destination handle. The rename is our spool-write step, so a transient
+// failure would drop the event (observed in prod: queue-write-failed EPERM on
+// rename in ~/.ai-lens/pending). Retry a few times with a short synchronous
+// backoff before giving up. POSIX rename is atomic and never hits these, so this
+// is a no-op there. Non-transient errors (e.g. ENOENT) are re-thrown immediately.
+const RENAME_RETRY_CODES = new Set(['EPERM', 'EACCES', 'EBUSY']);
+export function renameSyncWithRetry(from, to, { attempts = 5, baseDelayMs = 20, renameFn = renameSync } = {}) {
+  for (let i = 1; ; i++) {
+    try {
+      renameFn(from, to);
+      return;
+    } catch (err) {
+      if (i >= attempts || !RENAME_RETRY_CODES.has(err?.code)) throw err;
+      // Synchronous backoff — capture.js runs in a one-shot hook context, no event loop to yield to.
+      try {
+        Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, baseDelayMs * i);
+      } catch {
+        const end = Date.now() + baseDelayMs * i;
+        while (Date.now() < end) { /* spin fallback if Atomics unavailable */ }
+      }
+    }
+  }
+}
+
 export function writeToSpool(unified) {
   // Shallow copy before redaction — do not mutate the caller's object
   const toWrite = { ...unified };
@@ -1198,7 +1224,7 @@ export function writeToSpool(unified) {
   const tmpPath  = dstPath + '.tmp.' + process.pid;
   writeFileSync(tmpPath, JSON.stringify(toWrite));
   try {
-    renameSync(tmpPath, dstPath);
+    renameSyncWithRetry(tmpPath, dstPath);
   } catch (err) {
     // Clean up orphaned tmp file (e.g. antivirus/file-lock on Windows)
     try { unlinkSync(tmpPath); } catch {}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-lens",
-  "version": "0.8.72",
+  "version": "0.8.73",
   "type": "module",
   "description": "Centralized session analytics for AI coding tools",
   "bin": {