@theronap/cortex-mcp 0.9.134 → 0.9.136

package/lib/server.mjs

@@ -2418,7 +2418,7 @@ function renderNudge(payload) {
     'capture_meeting',
     {
       title: 'Capture a meeting transcript, joined to its calendar event',
-      description: "Capture a meeting transcript you were given — a paste, an export, notes — as a real record joined to the calendar event it came from. ⚠ CALL IT TWICE. Without `calendar_record_id` it WRITES NOTHING and returns candidate calendar events near that time; you pick one and call again. Overlap alone is not an answer — 90 of 120 calendar records are recurring birthdays and an all-day event overlaps its whole day, so each candidate carries `caveats` saying why it might be wrong. Read them before choosing. WHY THE JOIN MATTERS: a pasted transcript has no attendee list, so on its own it is reachable from nobody. The calendar event's attendee list is authoritative, and the captured meeting inherits it — that is what makes the transcript findable from the people who were in it. The brain follows from the matched event; you never pick one. Attendees who have no page come back as `unclaimed` — each is a person in the room nobody has authored, and authoring one reaches every past event they were in, not just this meeting. Meetings are stored `scoped`, never org-wide.",
+      description: "Capture a meeting transcript you were given — a paste, an export, notes — as a real record joined to the calendar event it came from. ⚠ CALL IT TWICE. Without `calendar_record_id` it WRITES NOTHING and returns candidate calendar events near that time; you pick one and call again. Overlap alone is not an answer — 90 of 120 calendar records are recurring birthdays and an all-day event overlaps its whole day, so each candidate carries `caveats` saying why it might be wrong. Read them before choosing. WHY THE JOIN MATTERS: a pasted transcript has no attendee list, so on its own it is reachable from nobody. The calendar event's attendee list is authoritative, and the captured meeting inherits it — that is what makes the transcript findable from the people who were in it. The brain follows from the matched event; you never pick one. Attendees who have no page come back as `unclaimed` — each is a person in the room nobody has authored, and authoring one reaches their EXISTING records too, not only future meetings: claiming their identifier heals history in the same statement. Measured 2026-09-03 — ten calendar records spanning two months attached 49ms after the claim. ⚠ THE CONFIRMATION DOES NOT TELL YOU THAT. It says only that future events will attach, so a heal that just moved ten records is indistinguishable from one that did nothing. Verify by reading the page, never by trusting the reply. Meetings are stored `scoped`, never org-wide.",
       inputSchema: {
         occurred_at: z.string().describe('when the meeting STARTED, ISO 8601. Required for both the proposal and the capture.'),
         ends_at: z.string().optional().describe('when it ended, ISO 8601. Omit and the calendar event\'s end is inherited. NEVER guess one — unknown must stay unknown.'),
@@ -3339,7 +3339,19 @@ function renderNudge(payload) {
       const out = await res.json().catch(() => null)
       if (!res.ok) return toolError(`Could not set routing identifier: ${out?.error ?? res.status}`)
       const set = out?.set?.join(', ') ?? identifier
-      return { content: [{ type: 'text', text: `Routing identifier set on document ${out?.documentId ?? '?'}: ${set}. Future matching events will attach here (body mentions alone will not).` }] }
+      // ⚠ SAY WHAT ALREADY HAPPENED, NOT ONLY WHAT WILL. The claim heals history in the same
+      // statement, so by the time this renders, existing records are ALREADY attached. The previous
+      // wording mentioned only future events — true, and load-bearingly incomplete, which is harder
+      // to catch than a false statement because checking it confirms it.
+      // A ZERO IS EXPLAINED, not printed bare: an unexplained 0 recreates the same ambiguity one
+      // level down, and identity claims (email:, thread:) attach only the CLAIMANT'S OWN records.
+      const healed = typeof out?.attachedExisting === 'number' ? out.attachedExisting : null
+      const healedLine = healed === null
+        ? ''
+        : healed > 0
+          ? ` ${healed} existing record(s) ALREADY attached to this page as a result.`
+          : ' 0 existing records attached — either nothing carries this identifier yet, or records do but belong to another owner (an identity claim only attaches your own).'
+      return { content: [{ type: 'text', text: `Routing identifier set on document ${out?.documentId ?? '?'}: ${set}.${healedLine} Future matching events will attach here too (body mentions alone will not).` }] }
     },
   )
 
@@ -3464,13 +3476,21 @@ function renderNudge(payload) {
     'route_record',
     {
       title: 'Route a record to the pages it belongs on',
-      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.',
+      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. \u26a0 ADR-0051: a record does not finish until somebody looked for its OTHER homes. A call that would end the record without adding a page it did not already have \u2014 a park, or a route naming only pages already attached \u2014 is REFUSED once, with instructions. Name the other pages, or go look, or say you looked.',
       inputSchema: {
         recordId: z.string().describe('record id from pending_records'),
         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'),
+        searchedForOtherHomes: z.boolean().optional().describe(
+          'ADR-0051. "I looked for other homes and there are genuinely none." Only consulted when the call '
+          + 'would otherwise finish the record without adding a page it did not already have — so a route that '
+          + 'attaches something new never needs it, and a park always does. '
+          + '⚠ DO NOT SEND THIS ON THE FIRST CALL AS A MATTER OF COURSE. It is the answer AFTER looking, not a '
+          + 'way past the question. The gate exists because a session-start instruction to route converted at '
+          + '11% over 21 days; sending this reflexively rebuilds exactly the failure it was measured against.',
+        ),
         identifierDispositions: z.array(z.any()).optional().describe(
           'ADR-0044. REQUIRED when this record carries identifiers no page claims — the refusal names exactly which. '
           + 'One entry per unresolved identifier, and this is a DIFFERENT question from documentIds. '
@@ -3489,13 +3509,13 @@ function renderNudge(payload) {
         ),
       },
     },
-    async ({ recordId, documentIds, reason, park, tier, identifierDispositions }) => {
+    async ({ recordId, documentIds, reason, park, tier, identifierDispositions, searchedForOtherHomes }) => {
       let res
       try {
         res = await fetchCortex(`${BASE}/api/brain/triage`, {
           method: 'POST',
           headers: { Authorization: `Bearer ${TOKEN}`, 'Content-Type': 'application/json' },
-          body: JSON.stringify({ action: park ? 'park' : 'route', recordId, documentIds, reason, tier, identifierDispositions }),
+          body: JSON.stringify({ action: park ? 'park' : 'route', recordId, documentIds, reason, tier, identifierDispositions, searchedForOtherHomes }),
         })
       } catch (e) {
         return toolError(`Could not route record: ${e.message}`)
@@ -3527,6 +3547,27 @@ function renderNudge(payload) {
         }
         return toolError(lines.join('\n'))
       }
+      // ADR-0051 refusal. Rendered as INSTRUCTIONS for the same reason the ADR-0044 one above is: the
+      // agent is one call from succeeding and the whole point of the gate is the question it asks. A
+      // bare "other_homes_unchecked" would read as a malfunction and get retried verbatim.
+      if (!res.ok && out?.error === 'other_homes_unchecked') {
+        return toolError([
+          park
+            ? 'Not parked yet — before a record is filed as having no home, look for its other homes.'
+            : 'Not routed yet — every page you named is already attached, so this call would finish the record without adding anything.',
+          '',
+          'What OTHER pages does this record belong on? A record is usually about more than the page an',
+          'identifier matched: the project it concerns, the person it is about, the decision it bears on.',
+          '',
+          '  know some already   → add them to documentIds and call again',
+          '  none come to mind   → go look first. grep or read for pages this could belong to;',
+          '                        you know the namespace better than any matcher does',
+          '  looked, found none  → call again with searchedForOtherHomes: true',
+          '',
+          'Parking is still a complete answer, and a wrong attachment is still worse than none. The gate',
+          'asks that you looked, not that you found something.',
+        ].join('\n'))
+      }
       if (!res.ok) return toolError(`Could not route record: ${out?.error ?? res.status}${out?.detail ? ` — ${out.detail}` : ''}`)
       if (park) return { content: [{ type: 'text', text: 'Parked. It stays visible and unrouted rather than badly attached.' }] }
       return { content: [{ type: 'text', text: `Routed — attached to ${out?.attached?.length ?? 0} page(s). Recorded as a session judgment, not a rule match.` }] }

package/package.json

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