@bli-cockpit/mcp 0.1.15 → 0.1.18

package/README.md

@@ -134,6 +134,9 @@ A claim about the verb's nature, not a backlog.
 
 <!-- END GENERATED verb census -->
 
+For memory adoption and ordinary hook measurements, use `cockpit ops --memory`
+or `ops_status` with `memory: true`. Both also read `GET /api/ops/memory-usage`.
+
 ## `jarvis_*` tools (BLI-3732)
 
 JARVIS itself — the same assistant Tower web chat, the Slack DM and

package/dist/ops-tools.js

@@ -56,6 +56,7 @@ export function registerOpsTools(server, deps) {
         inputSchema: {
             job: z.string().min(1).max(100).optional().describe("One pipeline id instead of the whole board."),
             skips: z.boolean().optional().describe("Also return the open ingest-skip ledgers."),
+            memory: z.boolean().optional().describe("Also return memory adoption and observed prompt-hook outcomes, delay bounds and cache reuse. No memory text."),
         },
     }, async (args) => withSession(deps, async (session) => {
         const params = new URLSearchParams();
@@ -72,16 +73,30 @@ export function registerOpsTools(server, deps) {
         const lines = rows
             .map((row) => `${(row.verdict ?? "?").padEnd(14)}  ${row.id ?? "?"}  ${row.detail ?? row.label ?? ""}`.trimEnd())
             .join("\n");
+        const memory = args.memory
+            ? await callAgentDoor(session, deps.fetchImpl, "GET", "/api/ops/memory-usage") : null;
+        if (memory && !memory.ok)
+            return errorResult(doorFailureText("ops_status memory", memory));
+        const hooks = memory?.ok ? asRecord(memory.body.hooks) : null;
+        const memoryLines = hooks && Array.isArray(hooks.devices)
+            ? hooks.devices.map((device) => {
+                const row = asRecord(device);
+                return [row.line, row.performanceLine].filter((line) => typeof line === "string").join("\n");
+            }).join("\n") : "";
         // Both branches say something. A board that is entirely green and
         // reports nothing cannot answer "did anybody look today?".
         return textResult(`${rows.length} pipeline(s), ${unhealthy.length} unhealthy`
             + `${unhealthy.length > 0 ? `: ${unhealthy.map((row) => row.id ?? "?").join(", ")}` : "."}`
-            + `${lines ? `\n${lines}` : ""}`, {
+            + `${lines ? `\n${lines}` : ""}`
+            + `${memoryLines ? `\n${memoryLines}` : ""}`, 
+        // The API owns the wording and the timing boundary on every surface.
+        {
             pipelines: rows,
             unhealthy: unhealthy.map((row) => row.id ?? "?"),
             ...(body.fleet ? { fleet: body.fleet } : {}),
             ...(body.coverage ? { coverage: body.coverage } : {}),
             ...(body.skips ? { skips: body.skips } : {}),
+            ...(memory?.ok ? { memory: memory.body.memory, hooks: memory.body.hooks } : {}),
         });
     }));
     register("slack_coverage", {

package/dist/search-tool.js

@@ -25,12 +25,17 @@
 import { z } from "zod";
 import { loadAgentDoorSession } from "./agent-door-session.js";
 import { callAgentDoor } from "./agent-door.js";
-const KINDS = ["doc", "msg", "issue", "note", "memory"];
+// Mirrors `SEARCH_KINDS` in apps/dashboard/src/lib/search/contracts.ts.
+// BLI-3880 added mail and cal; nothing in the type system ties the two
+// lists together, so `search-tool.test.ts` pins this one against the door.
+const KINDS = ["doc", "msg", "issue", "note", "mail", "cal", "memory"];
 const KIND_LABELS = {
     doc: "Document",
     msg: "Message",
     issue: "Issue",
     note: "Meeting note",
+    mail: "Email",
+    cal: "Calendar event",
     memory: "Memory",
 };
 function textResult(text, structured) {
@@ -46,13 +51,13 @@ export function registerSearchTool(server, deps) {
     const register = server.registerTool.bind(server);
     register("tower_search", {
         title: "Search everything in Tower",
-        description: "One search over documents, messages, issues, meeting notes and BLI Memory. Use it when you know WHAT you are looking for but not WHERE it lives. Every result names the corpus it came from and where to open it; a memory has no page, so its text is the whole record. A corpus that could not answer is reported separately from one that found nothing — do not read a failure as silence.",
+        description: "One search over documents, messages, issues, meeting notes, the caller's own mail, their calendar and BLI Memory. Use it when you know WHAT you are looking for but not WHERE it lives. Every result names the corpus it came from and where to open it; a memory has no page, so its text is the whole record. Mail and calendar are the caller's OWN — their mailboxes, their calendars and the ones shared with the organisation — never the whole company's. A calendar hit is the stored event, so a recurring meeting comes back once as its series rather than once per occurrence. A corpus that could not answer is reported separately from one that found nothing — do not read a failure as silence.",
         inputSchema: {
             query: z.string().min(2).max(1000).describe("What to look for, in the words a person would type."),
             kinds: z
                 .array(z.enum(KINDS))
                 .optional()
-                .describe("Narrow to these corpora. Omit to search all five."),
+                .describe("Narrow to these corpora. Omit to search every one."),
             limit: z.number().int().min(1).max(50).optional().describe("Results to return (default 20)."),
         },
     }, async (args) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bli-cockpit/mcp",
-  "version": "0.1.15",
+  "version": "0.1.18",
   "private": false,
   "description": "bli-tower \u2014 an MCP server over BLI Cockpit's agent doors: JARVIS (jarvis_*), documents (docs_*), channels (msg_*), issues (work_*), the daily page (brief_*), meeting notes (notes_*), the ops board (ops_status/slack_*), settings/team/model, Scout and the workbook, plus the legacy event-stream tools (emit_event, get_ticket_timeline, get_active_tickets).",
   "type": "module",
@@ -30,7 +30,7 @@
     "readme": "npm run build && node scripts/write-readme-census.mjs"
   },
   "dependencies": {
-    "@bli-cockpit/telemetry-core": "0.1.32",
+    "@bli-cockpit/telemetry-core": "0.1.34",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.3.6"
   },