@yemi33/minions 0.1.2332 → 0.1.2333

package/engine/pull-requests-store.js

@@ -313,7 +313,18 @@ function dropScope(scope) {
   try {
     const { getDb } = require('./db');
     const result = getDb().prepare('DELETE FROM pull_requests WHERE scope = ?').run(scope);
-    _lastMirrorHashByScope.delete(scope);
+    // Mirror the work-items-store.js fix (W-mr96m3hm000fd5d7): don't blindly
+    // forget the mirror-hash. _resyncScopeIfJsonDiverged treats "no recorded
+    // hash" + "zero SQL rows" as a first-install hydrate and rebuilds SQL from
+    // whatever JSON is on disk. removeProject with dataMode:'keep' leaves this
+    // scope's JSON file untouched, so forgetting the hash here would let the
+    // very next read/write resurrect the just-dropped project's stale PR rows.
+    // Adopt the file's current hash instead (or forget it only if the file is
+    // actually gone, e.g. dataMode: 'purge'/'archive').
+    const jsonPath = _filePathForScope(scope);
+    const currentHash = _fileContentHash(jsonPath);
+    if (currentHash == null) _lastMirrorHashByScope.delete(scope);
+    else _lastMirrorHashByScope.set(scope, currentHash);
     if (result && result.changes > 0) {
       try { require('./db-events').emitStateEvent('pull_requests'); } catch { /* optional */ }
     }

package/engine/work-items-store.js

@@ -390,7 +390,21 @@ function dropScope(scope) {
   try {
     const { getDb } = require('./db');
     const result = getDb().prepare('DELETE FROM work_items WHERE scope = ?').run(scope);
-    _lastMirrorHashByScope.delete(scope);
+    // Do NOT simply forget the mirror-hash here. _resyncScopeIfJsonDiverged
+    // treats "no recorded hash" + "zero SQL rows for the scope" as a genuine
+    // first-install hydrate and rebuilds SQL from whatever JSON is on disk.
+    // When the caller is removeProject with dataMode:'keep', the JSON file for
+    // this scope is deliberately left untouched — so the very next read/write
+    // against this scope would silently resurrect the just-dropped project's
+    // stale rows straight back into SQL. Instead, adopt the JSON file's
+    // *current* hash (if it still exists) so the next resync correctly reads
+    // that as "unchanged" and skips the rehydrate. If the file is genuinely
+    // gone (dataMode: 'purge'/'archive'), forgetting the hash is safe since
+    // _resyncScopeIfJsonDiverged no-ops when the file can't be hashed.
+    const jsonPath = _filePathForScope(scope);
+    const currentHash = _fileContentHash(jsonPath);
+    if (currentHash == null) _lastMirrorHashByScope.delete(scope);
+    else _lastMirrorHashByScope.set(scope, currentHash);
     if (result && result.changes > 0) {
       try { require('./db-events').emitStateEvent('work_items'); } catch { /* optional */ }
       try { require('./queries').invalidateWorkItemsCache(); } catch { /* queries not loaded */ }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.2332",
+  "version": "0.1.2333",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"