dotmd-cli 0.74.4 → 0.74.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dotmd-cli",
-  "version": "0.74.4",
+  "version": "0.74.5",
   "description": "CLI for managing markdown documents with YAML frontmatter — index, query, validate, graph, export, lifecycle, and AI summaries.",
   "type": "module",
   "license": "MIT",

package/src/extractors.mjs

@@ -41,8 +41,17 @@ export function extractNextStep(body) {
 
 export function extractBodyLinks(body) {
   if (!body) return [];
-  // Strip fenced code blocks and inline code to avoid false positives
-  const stripped = body.replace(/^```[\s\S]*?^```/gm, '').replace(/`[^`]+`/g, '');
+  // Strip fenced code blocks, then MASK inline code rather than delete it.
+  // Deleting it ate the commonest link idiom in a plan hub: [`plan.md`](plan.md)
+  // has its link TEXT as a code span, so removing the span left `[](plan.md)`,
+  // which the regex below rejects for having empty text. A hub with hundreds of
+  // such links reported one — and since this list is what validates body links,
+  // every one of them was also never checked for breakage. Masking to same-length
+  // filler keeps the link matchable while still neutralizing a link that is
+  // itself inside code (`[fake](x.md)` stays unmatched), and preserves offsets.
+  const stripped = body
+    .replace(/^```[\s\S]*?^```/gm, '')
+    .replace(/`[^`]+`/g, match => 'x'.repeat(match.length));
   const links = [];
   // Match [text](path.md) or [text](path.md#anchor), skip images (preceded by !)
   const regex = /(?<!!)\[([^\]]+)\]\(([^)]+\.md(?:#[^)]*)?)\)/g;

package/src/hub.mjs

@@ -242,9 +242,31 @@ export function detectBodyRunlistRefs(body) {
   let match;
   while ((match = linkSectionRe.exec(body)) !== null) {
     const section = sliceSection(match.index + match[0].length);
+    // Line by line, because the SHAPE decides what a link means, not the
+    // heading's name. A section titled `## Runlist index — by category` matches
+    // this heading list but is written as tables, and taking every link in it
+    // made each row's descriptive prose a membership claim: a row about plan A
+    // whose prose says "spawned children B, C" ranked B and C as the hub's own,
+    // then warned B and C for not naming the hub as parent. In a table, only the
+    // row's first link is the ranked plan — the same rule the ranked-queue
+    // branch below already applies.
     const allLinks = new RegExp(linkRe.source, 'g');
-    let link;
-    while ((link = allLinks.exec(section)) !== null) refs.push(link[1]);
+    for (const rawLine of section.split('\n')) {
+      const line = rawLine.trim();
+      if (line.startsWith('|')) {
+        const link = firstRowLink(line);
+        if (link) refs.push(link);
+        continue;
+      }
+      // One ranked item per line, first link wins — the same rule as a table
+      // row. A ranked item routinely carries commentary that links elsewhere
+      // ("Phase 7's open item closes on a route decision in [other-plan.md]"),
+      // and counting those made the hub claim plans it was only citing. A hub
+      // that means to rank two plans lists them on two lines.
+      allLinks.lastIndex = 0;
+      const link = allLinks.exec(line);
+      if (link) refs.push(link[1]);
+    }
 
     const checklistRe = /^\s*[-*]\s+\[[ xX]\]\s+([^\s)]+\.md(?:#[^\s)]+)?)/gm;
     let item;

package/src/validate.mjs

@@ -458,10 +458,14 @@ export function checkCoordinationHubExecutionMode(docs, config) {
   for (const doc of docs) {
     if (doc.type && doc.type !== 'plan') continue;
     if (skipDoc(doc)) continue;
-    // A roadmap (`execution_mode: roadmap`) is already an explicit held-out hub —
-    // just a tier up. Don't nudge it toward `coordination` even when its slug is
-    // `*-runlist` (e.g. a `master-runlist` promoted to a roadmap).
-    if (doc.executionMode === 'coordination' || doc.executionMode === 'roadmap') continue;
+    // ANY explicit `execution_mode` ends it. The field is the canonical signal
+    // and the slug is only a fallback for hubs that predate it, so a plan that
+    // already answered — `implementation`, `roadmap`, anything — has said what it
+    // is. Nudging past that misfires on exactly one population: plans ABOUT
+    // runlists, whose slug contains the word while the document is ordinary work.
+    // (A real one: a plan to rename the runlist concept, declared
+    // `execution_mode: implementation`, nagged to call itself a coordination hub.)
+    if (doc.executionMode) continue;
     const base = (doc.path.split('/').pop() || '').replace(/\.md$/, '');
     if (base !== 'runlist' && !base.endsWith('-runlist')) continue;
     warnings.push({