@yemi33/minions 0.1.2079 → 0.1.2081

package/dashboard/js/refresh.js

@@ -474,6 +474,13 @@ let _knownDashboardStartId = null;
 // dashboardBuildId is the md5 of the assembled HTML — bumps automatically on
 // hot-reload + on cold restart with any /dashboard/** change.
 let _knownDashboardBuildId = null;
+// Hard-reload trigger when the *engine* commit changes — `minions restart`
+// after a `git pull` swaps engine code but doesn't touch any
+// /dashboard/** asset, so `dashboardBuildId` stays the same and the
+// existing buildId reload above never fires. Without this, the stale
+// "Engine running v… — disk has v…" banner persists in already-open tabs
+// until the (hourly by default) /api/version repoll catches up.
+let _knownEngineRunningCommit = null;
 // /api/status ETag cache (W-mpehsyhv0017085a). The dashboard polls every 4 s
 // but the server-side cache only changes every 10–60 s. Sending If-None-Match
 // lets the server short-circuit ~60 %+ of polls into a 304 with no body —
@@ -755,6 +762,18 @@ async function refresh() {
       return;
     }
     if (buildId) _knownDashboardBuildId = buildId;
+    // Auto-reload when the engine's commit changed (engine code was updated
+    // and process restarted, e.g. via `minions restart` after `git pull`).
+    // dashboardBuildId only hashes HTML/JS/CSS assets, so engine-only code
+    // updates don't trigger that path — leaving stale "Engine running v… —
+    // disk has v…" banners until the hourly /api/version repoll.
+    const engineCommit = (data.version && data.version.runningCommit) || null;
+    if (engineCommit && _knownEngineRunningCommit && engineCommit !== _knownEngineRunningCommit) {
+      console.log('Engine code changed — reloading page');
+      location.reload();
+      return;
+    }
+    if (engineCommit) _knownEngineRunningCommit = engineCommit;
     // Successful poll — clear unreachable state. Placed AFTER the reload
     // guards above so a dashboard restart still triggers location.reload()
     // instead of just dismissing the banner.

package/engine/pipeline.js

@@ -299,11 +299,19 @@ function evaluateCondition(condition, ctx) {
 
   switch (cond.check) {
     case 'runSucceeded': {
-      // True when the current/last run completed with all stages succeeded (none failed)
+      // P-bfa1e finding #21: tightened predicate.
+      // Previously this accepted PENDING as "succeeded" via `s.status === COMPLETED || s.status === PENDING`,
+      // which let `stopWhen`/`stop-pipeline` short-circuit fire while stages were still queued for the next
+      // dispatch cycle. A "succeeded" run is one where:
+      //   1. The run object exists (no run → nothing has succeeded).
+      //   2. At least one stage exists (vacuous-truth empty `.every()` would otherwise lie about success).
+      //   3. EVERY stage is COMPLETED — RUNNING/PENDING/WAITING_HUMAN/PAUSED/FAILED/STOPPED all fail the check.
+      // Any `stopWhen` or condition-stage `stop-pipeline` consumer wired to `runSucceeded` now sees `false`
+      // until the run is fully done, so it cannot prematurely terminate the pipeline.
       if (!run) return false;
-      return Object.values(run.stages || {}).every(
-        s => s.status === PIPELINE_STATUS.COMPLETED || s.status === PIPELINE_STATUS.PENDING
-      );
+      const stages = Object.values(run.stages || {});
+      if (stages.length === 0) return false;
+      return stages.every(s => s && s.status === PIPELINE_STATUS.COMPLETED);
     }
     case 'noFailedItems': {
       // True when all work items created by the pipeline are done (not failed)
@@ -1156,6 +1164,23 @@ async function discoverPipelineWork(config) {
           // Condition stage signaled pipeline stop — complete the run immediately
           if (result._stopPipeline) {
             completeRun(pipeline.id, activeRun.runId, PIPELINE_STATUS.STOPPED);
+            // P-bfa1e finding #24: the local `activeRun` reference still has
+            // `status === RUNNING` because we captured it at L980 before any
+            // completion writes. The post-loop `allComplete` block at L1138
+            // guards with `activeRun.status !== PIPELINE_STATUS.STOPPED`
+            // before re-calling `completeRun(..., COMPLETED)` — if we leave
+            // the stale RUNNING status in place that guard fails and we
+            // clobber the STOPPED status with COMPLETED. Refresh the local
+            // reference from disk so downstream reads in this same tick see
+            // STOPPED. `getActiveRun` excludes terminal runs, so fall back
+            // to a defensive in-place status patch when the refresh comes
+            // back empty.
+            const refreshed = getActiveRun(pipeline.id);
+            if (refreshed) {
+              activeRun = refreshed;
+            } else {
+              activeRun.status = PIPELINE_STATUS.STOPPED;
+            }
             allComplete = true;
             break;
           }

package/package.json

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

package/prompts/cc-system.md

@@ -46,7 +46,7 @@ Your runtime is the **Copilot CLI**, not Claude Code. Your installed skills live
 - `~/.copilot/skills/<name>/SKILL.md` — user-level skills (yours)
 - `~/.copilot/installed-plugins/<marketplace>/<plugin>/skills/<name>/SKILL.md` — plugin-provided skills (also yours)
 
-To invoke a skill, call your `skill` tool with the skill name (the directory name). The skill body then guides the next steps.
+To invoke a skill, call your `skill` tool with the skill name (the directory name). The skill body then guides the next steps. **Both user-level and plugin-level skills are invokable the same way** — the `<location>` tag in the registry is metadata, not a permission gate. If the registry below lists a skill, you can load it.
 
 When asked "what skills do you have", answer from the registry below — do NOT grep/glob `.claude/skills/`. Those belong to a different runtime (Claude Code) and are not available to you, even if the directory exists in cwd or `$HOME`.