@yemi33/minions 0.1.1860 → 0.1.1861

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.1.1861 (2026-05-10)
+
+### Fixes
+- surface phantom-completion as the failReason instead of "no PR detected"
+
 ## 0.1.1860 (2026-05-10)
 
 ### Fixes

package/engine/lifecycle.js

@@ -1098,6 +1098,21 @@ function _outputContainsPrUrl(output) {
   return prUrlPattern.test(output);
 }
 
+// Detects the phantom-completion signature in the raw runtime output: the
+// runtime's terminating `{"type":"result"}` event never landed. When this is
+// true and the PR-attachment contract is about to hard-fail for "no PR
+// detected," it's far more accurate to say "runtime crashed before emitting a
+// result event" — the agent didn't fail silently, the runtime CLI did. Used by
+// enforcePrAttachmentContract to pick a truthful failReason.
+function _outputHasRuntimeResultEvent(output) {
+  if (!output || typeof output !== 'string') return false;
+  // Both Claude and Copilot emit a top-level `{"type":"result"…}` JSONL line as
+  // the conversation terminator. A literal substring match is enough; the
+  // captured streams are JSONL so the brace pattern can't legitimately appear
+  // mid-field-value without the prefix.
+  return /"type":\s*"result"/.test(output);
+}
+
 function markMissingPrAttachment(meta, agentId, reason, resultSummary, severity) {
   const noPrWiPath = resolveWorkItemPath(meta);
   const isHard = severity !== 'soft';
@@ -1239,9 +1254,20 @@ async function enforcePrAttachmentContract(type, meta, agentId, config, resultSu
   // was designed to catch) from "agent claimed a PR but engine couldn't attach
   // it canonically" (soft — verification gap, not a failure).
   const severity = _outputContainsPrUrl(output) ? 'soft' : 'hard';
-  const reason = severity === 'hard'
-    ? `${meta.item.id} completed but no PR URL was detected in the agent's output. Expected a PR — verify the agent didn't fail silently. (Branch: ${meta.branch || '(none)'}, agent: ${agentId})`
-    : `${meta.item.id} completed and a PR URL was found in the agent's output, but it couldn't be canonically attached. The work likely succeeded — verify by checking the PR list. (Branch: ${meta.branch || '(none)'}, agent: ${agentId})`;
+  // Hard-fail messaging: if the runtime never emitted its terminating result
+  // event, the failure is a phantom completion (runtime CLI crashed), not the
+  // agent silently skipping work. Surface that truthfully so operators don't
+  // chase "the agent didn't open a PR" when the real cause is "the runtime
+  // process died mid-conversation." Soft cases keep the original wording —
+  // they imply the runtime DID finish and a URL is in the stream.
+  let reason;
+  if (severity === 'hard') {
+    reason = _outputHasRuntimeResultEvent(output)
+      ? `${meta.item.id} completed but no PR URL was detected in the agent's output. Expected a PR — verify the agent didn't fail silently. (Branch: ${meta.branch || '(none)'}, agent: ${agentId})`
+      : `${meta.item.id} runtime exited without emitting a terminating result event — likely a phantom completion (the runtime CLI crashed mid-conversation, not a true agent failure). No PR was created. (Branch: ${meta.branch || '(none)'}, agent: ${agentId})`;
+  } else {
+    reason = `${meta.item.id} completed and a PR URL was found in the agent's output, but it couldn't be canonically attached. The work likely succeeded — verify by checking the PR list. (Branch: ${meta.branch || '(none)'}, agent: ${agentId})`;
+  }
   markMissingPrAttachment(meta, agentId, reason, resultSummary, severity);
   log(severity === 'hard' ? 'warn' : 'info', reason);
   return { reason, itemId: meta.item.id, severity };

package/package.json

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