eagle-mem 4.9.5 → 4.9.6

package/README.md

@@ -11,7 +11,7 @@
 
 Eagle Mem turns AI coding sessions into compounding project knowledge. It gives Claude Code and Codex the same local memory, labels which agent created each memory, blocks risky release commands until affected features are verified, and lets broad work split into durable worker lanes.
 
-**v4.9.5 hardens hooks and SQLite:** Stop hooks save immediately and queue LLM enrichment in the background instead of launching nested agents during turn shutdown. SQLite calls also resolve through one FTS5-capable binary selector, so Android SDK or other PATH shims do not accidentally break Eagle Mem.
+**v4.9.6 hardens hooks, updates, and SQLite:** Stop hooks save immediately and queue LLM enrichment in the background instead of launching nested agents during turn shutdown. Updates also queue slow project backfills instead of blocking install completion. SQLite calls resolve through one FTS5-capable binary selector, so Android SDK or other PATH shims do not accidentally break Eagle Mem.
 
 **Website:** [Product](https://eagleisbatman.github.io/eagle-mem/) |
 [Architecture](https://eagleisbatman.github.io/eagle-mem/architecture.html) |
@@ -152,6 +152,10 @@ Eagle Mem prevents Claude from repeating past mistakes:
 | `eagle-mem scan` | Scan codebase and generate overview |
 | `eagle-mem index` | Index source files for FTS5 code search |
 
+### v4.9.6 Patch
+
+`eagle-mem update` now queues project-key backfill in the background by default, so install/update can finish, write the installed version marker, and return control to the user. Use `EAGLE_MEM_UPDATE_BACKFILL=sync eagle-mem update` only when you intentionally want to wait for a full backfill.
+
 ### v4.9.5 Patch
 
 Stop hooks now use a fast path: they save heuristic summaries immediately, extract explicit summary blocks when present, and queue LLM enrichment in the background so Codex/Claude lifecycle hooks do not time out. SQLite access now goes through a shared FTS5-capable binary resolver used by migrations, DB helpers, updater backups, install checks, and the statusline, avoiding Android SDK or other PATH shims that shadow working SQLite builds.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eagle-mem",
-  "version": "4.9.5",
+  "version": "4.9.6",
   "description": "Shared memory, release guardrails, RTK token protection, and worker lanes for Claude Code and Codex",
   "bin": {
     "eagle-mem": "bin/eagle-mem"

package/scripts/update.sh

@@ -171,11 +171,19 @@ fi
 
 # ─── Backfill project names ───────────────────────────────
 
-backfilled=$(eagle_backfill_projects 2>/dev/null)
-if [ "${backfilled:-0}" -gt 0 ]; then
-    eagle_ok "Project names: $backfilled rows corrected"
+if [ "${EAGLE_MEM_UPDATE_BACKFILL:-background}" = "sync" ]; then
+    backfilled=$(eagle_backfill_projects 2>/dev/null)
+    if [ "${backfilled:-0}" -gt 0 ]; then
+        eagle_ok "Project names: $backfilled rows corrected"
+    else
+        eagle_ok "Project names up to date"
+    fi
 else
-    eagle_ok "Project names up to date"
+    (
+        backfilled=$(eagle_backfill_projects 2>/dev/null || echo 0)
+        eagle_log "INFO" "Update: background project backfill corrected ${backfilled:-0} rows"
+    ) >/dev/null 2>&1 &
+    eagle_ok "Project names backfill queued"
 fi
 
 # ─── Ensure auto-update defaults exist ─────────────────────