@theronap/cortex-mcp 0.9.133 → 0.9.135

package/lib/server.mjs

@@ -2253,6 +2253,45 @@ function renderNudge(payload) {
     },
   )
 
+  server.registerTool(
+    'supersede_record',
+    {
+      title: 'Mark a record as no longer the answer',
+      description: "Say that a record is wrong, outdated or replaced — WITHOUT deleting it. Use it when you re-capture something properly and the old copy should stop showing up: a transcript filed with a bad occurred_at, a duplicate capture, a low-fidelity copy replaced by a content_path one. \u26a0 NOTHING IS DESTROYED AND THIS IS REVERSIBLE (`restore: true`). The row, its page attachments and its containment all stay exactly as they were; only the READS change — it disappears from its pages, from its container's contents, and from the \"holds N\" count on find_sessions. It stays SEARCHABLE on purpose: hiding a record from search would be most of the way to deleting it without the audit trail. \u26a0 THERE IS NO DELETE, DELIBERATELY (ADR-0049) — 13 of the 15 foreign keys to a record CASCADE, so a real delete would unfile everything inside a container, drop clearance anchors and rewrite the claim ledger, while still leaving revision rows behind. If you actually need content destroyed rather than hidden, say so to the user rather than reaching for this. \u26a0 REFUSED ON A CONTAINER (a class session, a meeting): hiding an event that still holds other records leaves their placements pointing at nothing. Supersede the records INSIDE it instead.",
+      inputSchema: {
+        record_id: z.string().describe('the record that is no longer the answer'),
+        reason: z.string().optional().describe('WHY it is no longer right — required unless restoring, and the one thing that cannot be inferred later'),
+        superseded_by: z.string().optional().describe('the record that REPLACES it, if there is one. Must be in the same brain. Optional: "this is wrong" is a complete statement on its own.'),
+        restore: z.boolean().optional().describe('true = undo a previous supersede and make it current again'),
+      },
+    },
+    async ({ record_id, reason, superseded_by, restore }) => {
+      let res
+      try {
+        res = await fetchCortex(`${BASE}/api/records/supersede`, {
+          method: 'POST',
+          headers: { Authorization: `Bearer ${TOKEN}`, 'Content-Type': 'application/json' },
+          body: JSON.stringify({ recordId: record_id, reason, supersededBy: superseded_by, restore }),
+        })
+      } catch (e) {
+        return toolError(`Could not reach Agnoclast: ${e.message}`)
+      }
+      const body = await res.json().catch(() => ({}))
+      if (!res.ok || !body?.ok) {
+        return toolError(`Could not supersede ${record_id}: ${body?.error ?? res.status}${body?.detail ? ` \u2014 ${body.detail}` : ''}`)
+      }
+      if (restore) {
+        return { content: [{ type: 'text', text: `Restored ${record_id} — it is a current record again and reappears on its pages and in its container.` }] }
+      }
+      const l = [`Superseded ${record_id}.`]
+      if (body.supersededBy) l.push(`Replaced by ${body.supersededBy}.`)
+      // \u26a0 SAY WHAT DID NOT HAPPEN. The caller's next question is always whether this deleted
+      // something. It did not, and a reader who assumes it did will not think to restore.
+      l.push('Nothing was deleted — the row, its page attachments and its containment are intact. It is hidden from its pages, its container contents and session holds-counts, and stays searchable. `restore: true` reverses this.')
+      return { content: [{ type: 'text', text: l.join('\n') }] }
+    },
+  )
+
   server.registerTool(
     'find_sessions',
     {
@@ -2379,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.'),
@@ -3300,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).` }] }
     },
   )
 

package/package.json

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