@yemi33/minions 0.1.2361 → 0.1.2362

package/dashboard.js

@@ -1373,6 +1373,11 @@ function linkPullRequestForTracking({ url, title, project: projectName, contextO
   }, {
     project: targetProject,
     itemId: linkedWorkItemId,
+    // W-mrdutzdr000t22f4 — a POST /api/pull-requests/link call is deliberate
+    // user intent to (re)track this PR. Unlike passive re-enrollment paths
+    // (pollers, enrollPrFromCanonicalId), this call site should clear a
+    // tombstone left by a prior explicit delete rather than silently no-op.
+    allowResurrect: true,
   });
   return { ...result, prPath, targetProject, projectResolution, prNum };
 }
@@ -13844,16 +13849,25 @@ What would you like to discuss or change? When you're happy, say "approve" and I
       } catch (e) {
         return jsonReply(res, e.statusCode || 400, { error: e.message }, req);
       }
-      const { id: prId, prPath, prNum, created, linked, targetProject, projectResolution } = linkResult;
+      const { id: prId, prPath, prNum, created, linked, targetProject, projectResolution, skipped, resurrected } = linkResult;
       invalidateStatusCache();
+      // W-mrdutzdr000t22f4 — upsertPullRequestRecord can leave the record
+      // untouched (`skipped: true`) for reasons other than a resurrect, e.g.
+      // a legitimate cross-scope tombstone match it still refuses to touch.
+      // Surface that instead of always claiming success so a caller relying
+      // on "PR linked." isn't misled into thinking the record changed.
       jsonReply(res, 200, {
         ok: true,
         id: prId,
         created,
         linked,
+        skipped: skipped === true,
+        resurrected: resurrected === true,
         project: targetProject?.name || 'central',
         projectResolution,
-        message: projectResolution?.message || 'PR linked.',
+        message: skipped
+          ? 'PR was not linked: an existing tracked record blocked the update.'
+          : (projectResolution?.message || 'PR linked.'),
       });
 
       // Async-enrich: fetch title, description, branch, author from GitHub/ADO API

package/engine/shared.js

@@ -7873,7 +7873,7 @@ function collapseDuplicatePrRecords(prPath, { project = null } = {}) {
  * manually records a PR for a work item must use this helper so the PR record
  * and the canonical work-item attachment are created together and idempotently.
  */
-function upsertPullRequestRecord(prPath, entry, { project = null, itemId = null, itemIds = null, beforeInsert = null } = {}) {
+function upsertPullRequestRecord(prPath, entry, { project = null, itemId = null, itemIds = null, beforeInsert = null, allowResurrect = false } = {}) {
   if (!prPath) throw new Error('prPath required');
   if (!entry || typeof entry !== 'object') throw new Error('entry required');
 
@@ -7906,6 +7906,7 @@ function upsertPullRequestRecord(prPath, entry, { project = null, itemId = null,
   let created = false;
   let linked = false;
   let skipped = false;
+  let resurrected = false;
   let record = null;
 
   mutatePullRequests(prPath, (prs) => {
@@ -7914,9 +7915,20 @@ function upsertPullRequestRecord(prPath, entry, { project = null, itemId = null,
     // Issue #384: tombstoned records (userDeleted:true) must not be re-activated
     // by any poller path. Return skipped so reconcilePrs / shared-branch-reconcile
     // cannot resurrect a PR the user explicitly removed.
+    //
+    // W-mrdutzdr000t22f4 — passive re-enrollment (pollers, enrollPrFromCanonicalId)
+    // must keep respecting the tombstone, but a deliberate user-initiated relink
+    // via POST /api/pull-requests/link is explicit intent to bring the PR back.
+    // Callers that want that behavior opt in with `allowResurrect: true`, which
+    // clears the tombstone here and lets the normal field-merge logic below run.
     if (target && target.userDeleted === true) {
-      skipped = true;
-      return prs;
+      if (!allowResurrect) {
+        skipped = true;
+        return prs;
+      }
+      delete target.userDeleted;
+      delete target.userDeletedAt;
+      resurrected = true;
     }
     // P-e9f0a2b4 — When findPrRecord returns null but multiple records share the
     // same prNumber (e.g. cross-scope contamination or a project-config change
@@ -7980,7 +7992,7 @@ function upsertPullRequestRecord(prPath, entry, { project = null, itemId = null,
     }
   }
 
-  return { id: canonicalId, prNumber, created, linked, skipped, record };
+  return { id: canonicalId, prNumber, created, linked, skipped, resurrected, record };
 }
 
 // ─── PR Reference → URL Derivation ───────────────────────────────────────────

package/package.json

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