loopctl-mcp-server 2.27.0 → 2.29.0

package/index.js

@@ -1151,6 +1151,18 @@ async function knowledgeAnalyticsTop({ limit, offset, since_days, access_type }
   return toContent(result);
 }
 
+async function knowledgeRetrievalMetrics({ limit, offset } = {}) {
+  const params = new URLSearchParams();
+  if (limit != null) params.set("limit", String(limit));
+  if (offset != null) params.set("offset", String(offset));
+  const qs = params.toString();
+  const path = qs
+    ? `/api/v1/knowledge/analytics/retrieval-metrics?${qs}`
+    : "/api/v1/knowledge/analytics/retrieval-metrics";
+  const result = await apiCall("GET", path, null, process.env.LOOPCTL_ORCH_KEY);
+  return toContent(result);
+}
+
 async function knowledgeArticleStats({ article_id }) {
   const result = await apiCall(
     "GET",
@@ -2467,7 +2479,9 @@ const TOOLS = [
       "a keyword and a semantic sub-search, each capped at 100, so up to ~200), or filtered_set " +
       "(list mode: the full set). Do NOT use a relevance-mode total_count to size the wiki — use " +
       "list mode or knowledge_stats. " +
-      "Pass story_id when working on a loopctl story so reads attribute correctly.",
+      "Pass story_id when working on a loopctl story so reads attribute correctly. " +
+      "When you knowledge_get a result and it carries `potential_conflicts`, resolve it if it's " +
+      "material to your task (see knowledge_get / the conflict-resolution wiki playbook).",
     inputSchema: {
       type: "object",
       properties: {
@@ -2520,7 +2534,12 @@ const TOOLS = [
     name: "knowledge_get",
     description:
       "Get full article content by ID. Use after search to read an article in detail. " +
-      "Pass story_id when working on a loopctl story so reads attribute correctly.",
+      "Pass story_id when working on a loopctl story so reads attribute correctly. " +
+      "If the response carries a non-empty `potential_conflicts` array AND the conflict is " +
+      "material to your current task, act on it: read the peer, judge redundant/complementary/" +
+      "contradictory against the live system, and knowledge_resolve_conflict (dismiss a false " +
+      "positive, supersede when one clearly wins, merge when both should combine). If you can't " +
+      "tell which is right, leave it. See the 'Resolving knowledge conflicts' wiki playbook.",
     inputSchema: {
       type: "object",
       properties: {
@@ -2957,7 +2976,9 @@ const TOOLS = [
       "the two don't actually conflict; drops out of the queue immediately); 'supersede' " +
       "(one article wins — pass authoritative_article_id, the winner; the nightly executor " +
       "creates a supersedes link and retires the loser, but ONLY at confidence:\"high\" — " +
-      "reversible and audited); 'merge' (recorded for the later merge step). Non-destructive " +
+      "reversible and audited); 'merge' (at confidence:\"high\" the nightly executor has an LLM " +
+      "synthesize the two into ONE new DRAFT — both sources preserved, never auto-published, " +
+      "for you/a human to review and publish). Non-destructive " +
       "at agent role — you record intent; the privileged nightly job executes it. " +
       "Last-write-wins per pair, so re-recording with fresher ground truth overrides. " +
       "Resolve only conflicts material to your current task; adjudicate against the actual " +
@@ -2979,7 +3000,8 @@ const TOOLS = [
           enum: ["dismiss", "supersede", "merge"],
           description:
             "dismiss = false positive; supersede = one wins (set authoritative_article_id); " +
-            "merge = combine (recorded for the later merge step).",
+            "merge = combine both into one new DRAFT (LLM-synthesized by the nightly executor " +
+            "at high confidence; sources preserved, never auto-published).",
         },
         authoritative_article_id: {
           type: "string",
@@ -3244,6 +3266,32 @@ const TOOLS = [
   },
 
   // Knowledge Analytics Tools (orchestrator key)
+  {
+    name: "knowledge_retrieval_metrics",
+    description:
+      "Return the daily retrieval-PRECISION time series (agents' KB #3): for each day, the " +
+      "share of search results the agent then opened (search → get/context within a window). " +
+      "A proxy for whether retrieval is improving — watch it trend up as the corpus is " +
+      "de-duplicated, better navigated (MOCs), and conflict-resolved. Most recent day first. " +
+      "Requires orchestrator role.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        limit: {
+          type: "integer",
+          description: "Days per page (default 30, max 365). Clamped, never rejected.",
+          minimum: 1,
+          maximum: 365,
+        },
+        offset: {
+          type: "integer",
+          description: "Days to skip. Default 0.",
+          minimum: 0,
+        },
+      },
+      required: [],
+    },
+  },
   {
     name: "knowledge_analytics_top",
     description:
@@ -3660,6 +3708,9 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
       return await knowledgeIngestionJobs();
 
     // Knowledge Analytics Tools
+    case "knowledge_retrieval_metrics":
+      return await knowledgeRetrievalMetrics(args);
+
     case "knowledge_analytics_top":
       return await knowledgeAnalyticsTop(args);
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "loopctl-mcp-server",
-  "version": "2.27.0",
+  "version": "2.29.0",
   "description": "MCP server for loopctl — structural trust for AI development loops",
   "type": "module",
   "main": "index.js",