@theronap/cortex-mcp 0.9.105 → 0.9.106

package/lib/folder_claims.mjs

@@ -0,0 +1,48 @@
+// The read_page footer line about FOLDER CLAIMS — pure, so CI can execute the decision.
+//
+// WHY THIS EXISTS. A page claiming a whole repo and a page claiming `web/lib/engine/` read
+// identically, and the difference decides where every future commit lands and what tier it gets.
+// Measured against prod 2026-08-22: 88 Agnoclast pages carry a `[[repo:…]]` stamp and 10 hold any
+// path claim, so ~78 silently take delivery of the entire monorepo — `cortex` alone governs 66%.
+//
+// WHY THE FOOTER AND NOT A BACKLOG, A SCRIPT, OR A MINING PASS. It cannot be mined. Today's
+// attachments come FROM the mother route, so mining them re-derives the mother (circular for
+// `cortex` and `Theron Peterson`); and for every other page a commit spanning two packages makes all
+// of its paths look like evidence for both (`cortex-mcp` mines to `web/app/api/` at 52 records — it
+// is a package). Co-occurrence is not aboutness. Which folders a page is ABOUT is judgment, and the
+// agent holding the page open is the one with the context to make it — the same argument, and the
+// same evidence, as the per-node backlog nudge that ships beside it.
+//
+// SELF-EXTINGUISHING BY DESIGN. Once a claim exists the line stops asking and starts reviewing, so a
+// page that has been narrowed does not keep nagging every reader forever. That is the difference
+// between a nudge and wallpaper, and this repo has already recorded the day-one backlog saturating
+// the D9 signal as the failure mode to avoid.
+
+/**
+ * PURE. The footer line for a page's folder claims, or null when there is nothing worth saying.
+ *
+ * @param stamps      repo stamps found in the page body, e.g. ['[[repo:theronap/cortex]]']
+ * @param pathRoutes  `file:` claims the node holds, from the server
+ * @returns the line to append, or null
+ */
+export function folderClaimLine(stamps, pathRoutes) {
+  // ⚠ SILENCE WHEN THE SERVER DID NOT ANSWER, which is not the same as "no claims". A client newer
+  // than its server gets `undefined` here, and treating that as an empty array would tell every
+  // repo-stamped page to add folder claims — including the ones that already have them, whose claims
+  // this build simply cannot see. Say nothing rather than something confidently wrong; the line
+  // reappears on its own once the server is serving the field.
+  if (pathRoutes === undefined || pathRoutes === null) return null
+
+  const hasStamp = Array.isArray(stamps) && stamps.length > 0
+  const routes = Array.isArray(pathRoutes) ? pathRoutes.filter((r) => typeof r === 'string' && r) : []
+
+  // Nothing to say about a page that claims no repo and no folders — it is not in this population,
+  // and a line here would be noise on every unrelated page in the wiki.
+  if (!hasStamp && !routes.length) return null
+
+  if (routes.length) {
+    return `Folder claims on this page: ${routes.join(', ')}. If one of these is not actually what this page is about, correct it — a wrong claim quietly routes other people's commits here and sets their tier.`
+  }
+
+  return `⚠ This page claims a WHOLE REPO and no folders within it, so every commit to that repo routes here. If you can tell which folders or files this page is actually about, claim them with \`set_routing_identifier\` (\`file:owner/repo:path/to/dir/\` — the trailing slash is what makes it a subtree). Claims are additive and reversible, and a narrower claim also decides the tier of records that land on it. Judge from what the page IS about, not from what happens to be attached to it.`
+}

package/lib/server.mjs

@@ -6,6 +6,7 @@ import { homedir } from 'os'
 import { join } from 'path'
 import { createHash, randomUUID } from 'crypto'
 import { fetchCortex, classify, resolveBase, resolveEnvToken, setSessionKey } from './diagnose.mjs'
+import { folderClaimLine } from './folder_claims.mjs'
 import { resolveSessionKey, resolveLogSessionId } from './session_key.mjs'
 import { runSendImessage } from './imessage_send.mjs'
 import { formatGrepHits } from './grep_cli.mjs'
@@ -1260,6 +1261,22 @@ export async function runServer(version) {
         const allBody = m.tiers.flatMap((t) => (t.sections ?? []).map((s) => s.body)).join('\n')
         const stamps = [...new Set((allBody.match(/\[\[repo:[a-z0-9][a-z0-9-]*\/[a-z0-9_.-]+\]\]/gi) ?? []).map((s) => s.toLowerCase()))]
         if (stamps.length) footer += `\n— This page carries ${stamps.join(', ')} — \`read_page "${name}"\` with history: true for its event timeline (page = present, timeline = history).`
+        // FOLDER CLAIMS (2026-08-22). A page claiming a whole repo and a page claiming
+        // `web/lib/engine/` read identically, and the difference decides where every future commit
+        // lands. Measured that day: 88 Agnoclast pages carry a repo stamp, 10 hold any path claim —
+        // so ~78 silently take delivery of the entire monorepo, and `cortex` alone governs 66%.
+        //
+        // WHY THE FOOTER RATHER THAN A BACKLOG OR A SCRIPT. This cannot be mined: today's attachments
+        // come FROM the mother route, so mining them re-derives the mother (circular), and for
+        // everyone else a commit spanning two packages makes all its paths look like evidence for
+        // both pages (`cortex-mcp` mines to `web/app/api/` at 52 records — it is a package). Which
+        // folders a page is ABOUT is judgment, and the agent holding the page open is the one with
+        // the context to make it. Same reasoning as the backlog nudge two lines down, and the same
+        // evidence: a session read a page through a [[link]], saw the footer, and repaired the page.
+        // The ask is deliberately self-extinguishing — once a claim exists the line changes to a
+        // review prompt rather than a request, so a corrected page stops nagging.
+        const claimLine = folderClaimLine(stamps, m.pathRoutes)
+        if (claimLine) footer += `\n— ${claimLine}`
         // Gate 4's per-node backlog nudge (also gate 3's KWA-36). The SERVER decides whether this
         // fires — it sends `nudge` only when 25+ records are unclaimed AND the page has gone 7+ days
         // unedited — so there is no threshold logic here to drift out of sync. It rides in the footer

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@theronap/cortex-mcp",
-  "version": "0.9.105",
-  "description": "Connect your AI assistant to Cortex \u2014 your org's projects, activity, gaps, and directives, scoped to you.",
+  "version": "0.9.106",
+  "description": "Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.",
   "type": "module",
   "bin": {
     "cortex-mcp": "bin/cortex-mcp.mjs"
@@ -29,8 +29,8 @@
   ],
   "license": "MIT",
   "scripts": {
-    "release": "node scripts/release.mjs release",
-    "promote": "node scripts/release.mjs promote",
-    "rollback": "node scripts/release.mjs rollback"
+    "release": "bash scripts/release.sh",
+    "promote": "bash scripts/promote.sh",
+    "rollback": "bash scripts/rollback.sh"
   }
 }