@theronap/cortex-mcp 0.9.112 → 0.9.114

package/lib/diagnose.mjs

@@ -238,11 +238,29 @@ export function classify(status, contentType, bodyText, requestId) {
 let SESSION_KEY = null
 export function setSessionKey(key) { SESSION_KEY = key || null }
 
+// WHO IS CALLING — an identity INDEPENDENT of the session key, and it must stay independent.
+//
+// The server labels every page revision's `actor_source` from this header. It used to default to
+// 'mcp' server-side with nothing setting it, so 'mcp' silently meant "unlabelled" and an ADR-0030
+// scrub run against the HTTP API on 2026-08-26 wrote 340 revisions that read as MCP sessions with
+// dropped attribution — which reopened gate 2 on 2026-08-27 against a cause that was never MCP.
+//
+// ⚠ Deliberately NOT derived from SESSION_KEY, and deliberately sent even when SESSION_KEY is null.
+// The alarm's whole subject is `actor_source='mcp' AND session_key IS NULL`; if this header were
+// conditional on the session, that pair could never occur and the detector would be structurally
+// blind. A one-shot hook process legitimately has no session and IS still cortex-mcp — it should
+// say so, and be visible as one, not disguise itself as a script.
+let CLIENT_ID = 'cortex-mcp/unknown'
+export function setClientVersion(version) {
+  CLIENT_ID = `cortex-mcp/${version || 'unknown'}`
+}
+
 export async function fetchCortex(url, opts = {}, { retries = 2, baseDelayMs = 400 } = {}) {
   const { timeoutMs: optTimeout, signal: callerSignal, ...rest } = opts
+  const baseHeaders = { ...(rest.headers ?? {}), 'x-cortex-client': CLIENT_ID }
   const fetchOpts = SESSION_KEY
-    ? { ...rest, headers: { ...(rest.headers ?? {}), 'x-cortex-session-key': SESSION_KEY } }
-    : rest
+    ? { ...rest, headers: { ...baseHeaders, 'x-cortex-session-key': SESSION_KEY } }
+    : { ...rest, headers: baseHeaders }
   const timeoutMs = optTimeout ?? (Number(process.env.CORTEX_HTTP_TIMEOUT_MS) || 15_000)
   let lastErr
   for (let attempt = 0; attempt <= retries; attempt++) {

package/lib/server.mjs

@@ -5,7 +5,7 @@ import { writeFileSync, mkdirSync } from 'fs'
 import { homedir } from 'os'
 import { join } from 'path'
 import { createHash, randomUUID } from 'crypto'
-import { fetchCortex, classify, resolveBase, resolveEnvToken, setSessionKey } from './diagnose.mjs'
+import { fetchCortex, classify, resolveBase, resolveEnvToken, setSessionKey, setClientVersion } from './diagnose.mjs'
 import { folderClaimLine } from './folder_claims.mjs'
 import { resolveSessionKey, resolveLogSessionId } from './session_key.mjs'
 import { runSendImessage } from './imessage_send.mjs'
@@ -104,6 +104,10 @@ export async function runServer(version) {
   // resolve THIS session's brain pointer. Must be set BEFORE the first fetchCortex call below —
   // otherwise the opening requests of a session would silently resolve by the account pointer.
   setSessionKey(SESSION_KEY)
+  // Paired with setSessionKey and set at the same moment, but a SEPARATE signal on purpose: the
+  // server labels actor_source from this and watches for `mcp` + no session. Tying the two together
+  // would make that pair impossible and blind the detector. See actorSourceFrom in auth_cloud.ts.
+  setClientVersion(version)
   async function pingSession() {
     try {
       await fetchCortex(`${BASE}/api/session-ping`, {
@@ -2542,7 +2546,7 @@ export async function runServer(version) {
       description: 'Attach a pending record to the pages you judge correct — the point of the whole triage path. Use this when you have real context on what the work was; that judgment is better than any rule the webhook could run. Attachments are additive: existing deterministic homes (routing identifiers, your profile) stay. Pass park=true instead when you have looked and there is genuinely no good home — parking beats attaching to a page that merely shares a word.',
       inputSchema: {
         recordId: z.string().describe('record id from pending_records'),
-        documentIds: z.array(z.string()).optional().describe('page document ids to attach (from pending_records sweep, or read_page)'),
+        documentIds: z.array(z.string()).optional().describe('pages to attach. Accepts EITHER a brain_documents id (from a pending_records sweep) OR the `ref:` that read_page prints for a page — they are different columns and read_page only ever gives you the second, which is why this used to fail as no_documents on ids that looked perfectly valid. A ref resolves to that node\'s current page, accessible copy first. Anything that resolves to no page in this brain is named back to you rather than silently dropped.'),
         reason: z.string().describe('why these pages — recorded with the attachment'),
         park: z.boolean().optional().describe('no good home exists; leave it alone rather than guessing'),
         tier: z.number().int().optional().describe('2 when this came from the cheap sweep rather than your own context'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theronap/cortex-mcp",
-  "version": "0.9.112",
+  "version": "0.9.114",
   "description": "Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.",
   "type": "module",
   "bin": {