@yemi33/minions 0.1.2024 → 0.1.2026

package/dashboard.js

@@ -1782,9 +1782,17 @@ function getStatus() {
   if (fastStale) {
     // Reload config on fast-state miss — picks up external changes (minions init, minions add)
     reloadConfig();
+    // Snapshot mtimes BEFORE the rebuild reads disk. If an engine write lands
+    // mid-rebuild (dispatch.json, work-items.json, pull-requests.json), the
+    // snapshot reflects pre-write state, but capturing _lastMtimes AFTER would
+    // record the post-write mtime — silently masking the change. Subsequent
+    // polls would then see no mtime delta and return 304 with stale data until
+    // FAST_STATE_TTL expires. Capturing pre-build at worst forces one extra
+    // (no-op) rebuild on the next poll; capturing post-build loses the update.
+    const preBuildMtimes = _getMtimes();
     _fastState = _buildStatusFastState();
     _fastStateTs = now;
-    _lastMtimes = _getMtimes();
+    _lastMtimes = preBuildMtimes;
   }
 
   // Rebuild slow state (rarely-changing data: ~8-15 reads, 60s TTL)
@@ -1836,8 +1844,14 @@ function refreshStatusAsync() {
       if (!fastStale && !slowStale && _statusCache) return _statusCache;
 
       let fast = _fastState;
+      // Pre-build mtime snapshot (see getStatus() for the rationale). The async
+      // path has an even wider race window than the sync path because of the
+      // `await _yieldEventLoop()` below — any write that lands between disk
+      // reads and the post-build `_getMtimes()` capture would be lost.
+      let preBuildMtimes = null;
       if (fastStale) {
         reloadConfig();
+        preBuildMtimes = _getMtimes();
         fast = _buildStatusFastState();
       }
 
@@ -1868,7 +1882,7 @@ function refreshStatusAsync() {
       if (fastStale) {
         _fastState = fast;
         _fastStateTs = now;
-        _lastMtimes = _getMtimes();
+        _lastMtimes = preBuildMtimes;
       }
       if (slowStale) {
         _slowState = slow;

package/engine/queries.js

@@ -1907,6 +1907,21 @@ function getStatusFastStateMtimePaths(config) {
     path.join(ENGINE_DIR, 'watches.json'),
     // Central work-items.json surfaced by getWorkItems().
     path.join(MINIONS_DIR, 'work-items.json'),
+    // notes.md (surfaced by getNotesWithMeta) — consolidation writes this
+    // when an inbox batch is processed. Single file, mtime advances on every
+    // write. Without this, the dashboard's notes view sat stale for up to
+    // FAST_STATE_TTL (10 s) after each consolidation cycle.
+    NOTES_PATH,
+    // notes/inbox/ (surfaced by getInbox) — every writeToInbox call CREATES
+    // a new file (engine/shared.js#writeToInbox always uses a uid'd path,
+    // never an in-place edit), so the directory's mtime is a reliable
+    // entry-add/remove signal even on Windows NTFS. Without it, PR-comment
+    // notifications, agent-failure summaries, follow-up build alerts, and
+    // meeting-transcript dumps all lagged up to 10 s before appearing on
+    // the dashboard's inbox view. The meeting directory is still excluded
+    // (see "Files intentionally NOT tracked") because round transitions
+    // edit existing files in-place, which dir mtime can't detect.
+    INBOX_DIR,
   ];
   // Per-project work-items (surfaced by getWorkItems) and pull-requests
   // (surfaced by getPullRequests). The PR file was the biggest miss in the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.2024",
+  "version": "0.1.2026",
   "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"