@yemi33/minions 0.1.2031 → 0.1.2033

package/dashboard/js/refresh.js

@@ -121,12 +121,21 @@ function _formatCcDrawerLabel(autoMode) {
 }
 
 function _processStatusUpdate(data) {
-  // Detect fresh install — clear stale browser state if install ID changed
+  // Detect fresh install — clear stale browser state AND reload so module-scoped
+  // JS caches (_sectionCache, _prevCounts, _kbRefreshCount, _managedProcessesLastItems,
+  // _pipelinePollHash, _meetingPollHash, etc.) reinitialise against the new install's
+  // data shape. localStorage.clear() alone leaves those caches stale after a
+  // MINIONS_HOME swap that doesn't restart the dashboard (F11 / W-mpgcijjo000ce878).
   if (data.installId) {
     const prev = localStorage.getItem('minions-install-id');
     if (prev && prev !== data.installId) {
       localStorage.clear();
-      console.log('Minions: fresh install detected, cleared browser state');
+      // Write the new install-id BEFORE reload — the post-reload poll must see
+      // a matching id so it stops looping. clear() above wiped it, so set it again.
+      localStorage.setItem('minions-install-id', data.installId);
+      console.log('Minions: fresh install detected, reloading to reset module caches');
+      location.reload();
+      return;
     }
     localStorage.setItem('minions-install-id', data.installId);
   }
@@ -145,17 +154,35 @@ function _processStatusUpdate(data) {
   const threshEl = document.getElementById('inbox-threshold');
   if (threshEl && data.autoMode?.inboxThreshold) threshEl.textContent = data.autoMode.inboxThreshold;
 
-  // Publish window._last* snapshots BEFORE any renderer runs. Several renderers
-  // (renderProjects, renderPrd, renderPrs, refreshPlans, and others) read
-  // window._lastStatus / window._lastWorkItems / window._lastDispatch during
-  // their render path. If we assign these after the renderer calls, every tick
-  // consumes the PREVIOUS tick's globals — a one-tick (~4 s) staleness lag
-  // baked into the polling loop (W-mpgb0x81000cf8df, audit F4). No renderer in
-  // this function mutates `data`, so hoisting is safe.
+  // Publish window._last* snapshots BEFORE any renderer runs. Several
+  // renderers (renderPrd, renderPrs, derivePlanStatus inside refreshPlans,
+  // and the projectChipRemove/optimisticallyAddProject paths off
+  // renderProjects) read window._lastStatus / window._lastWorkItems /
+  // window._lastDispatch synchronously during their render path. When the
+  // assignments lived AFTER the renderer calls (the pre-fix layout in
+  // refresh.js:106-108), every tick consumed the PREVIOUS tick's globals —
+  // a one-tick (~4 s) staleness lag baked into the polling loop on top of
+  // the natural poll interval.
+  //
+  // See dashboard-refresh-audit.md finding F4 (W-mpgb0x81000cf8df / PR #2753
+  // landed the initial hoist; W-mpgbzpn9000390ae extends it with the
+  // render-agents / render-work-items invariants below). No renderer below
+  // mutates `data`, so hoisting the publish is safe; the renderers
+  // themselves still take their slice as a direct argument.
+  //
+  // Locking-in note (W-mpgbzpn9000390ae): renderAgents
+  // (render-agents.js:38) and renderWorkItems (render-work-items.js:98) —
+  // the two surfaces the user explicitly called out on /home and /work —
+  // take their data slice via argument and DO NOT read window._last*.
+  // Hoisting the publish here additionally guarantees that any future
+  // refactor that adds a window._last* read to those renderers will see
+  // fresh data on the same tick, not the previous one. Covered by
+  // dashboard-resilience.test.js source-inspection assertions.
   window._lastDispatch = data.dispatch;
   window._lastWorkItems = data.workItems || [];
   window._lastStatus = data;
 
+
   // Render only changed sections
   if (_changed('agents', data.agents)) { renderAgents(data.agents); cmdUpdateAgentList(data.agents); }
   if (_changed('prdProgress', data.prdProgress) || _changed('prdPrs', data.pullRequests?.length)) { renderPrdProgress(data.prdProgress); _cachePrdItems(data.prdProgress); }

package/package.json

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