loopctl-mcp-server 2.78.0 → 2.78.1

package/index.js

@@ -6715,13 +6715,16 @@ const TOOLS = [
       "searched: different row populations, so results_returned < searched is normal on a " +
       "legacy-heavy or browse-heavy day.\n\n" +
       "Caveats: zero-result searches and keyless searches are structurally unrecordable and " +
-      "sit in NO denominator, so both ratios are upper bounds; and both rise if a search " +
-      "simply returns FEWER results, with no better retrieval. Never optimise either alone — " +
-      "read them with the absolute followed_through and the volume fields. " +
-      "search_follow_through carries two further biases pointing OPPOSITE ways: the 20-row " +
+      "sit in NO denominator, so every ratio here is an upper bound; and precision ALONE " +
+      "rises if a search simply returns FEWER results, with no better retrieval — its " +
+      "denominator counts surfaced RESULTS, while the two call-level rates divide CALL " +
+      "counts, which a narrower page does not shrink. Never optimise one alone — read them " +
+      "with the absolute followed_through and the volume fields. BOTH " +
+      "follow-through rates carry two further biases pointing OPPOSITE ways: the 20-row " +
       "recording cap hides opens of results ranked beyond it (DOWN on large pages), while " +
       "one open credits EVERY search in the window that surfaced that article, not just the " +
-      "preceding one (UP when an agent refines and re-searches).\n\n" +
+      "preceding one (UP when an agent refines and re-searches, hardest on " +
+      "scored_follow_through).\n\n" +
       "Exact attribution (unit: READS — not surfaced results, not calls): attributed_opens " +
       "/ cross_key_opens / direct_opens count READ rows by how their originating search was " +
       "established, resolved server-side at write time and never accepted from a caller. " +
@@ -6748,6 +6751,24 @@ const TOOLS = [
       "distilled query per prompt and never see what came back, so they cannot reformulate " +
       "by construction. They stay in every other denominator here, precision included. " +
       "Read searches - searches_scored as n/a, never as zero.\n\n" +
+      "WHICH FOLLOW-THROUGH RATE TO QUOTE. Two are published over DIFFERENT populations, " +
+      "and picking the wrong one misstates agent behaviour by roughly 3.4x. " +
+      "search_follow_through is over every query-bearing call that SURVIVES the " +
+      "infrastructure exclusion — smoke/skill-eval sit in NO denominator here, but the " +
+      "recall hook and the session-start auto-query DO, and neither can follow through by " +
+      "construction. Use it for total traffic through the retrieval path, and read it as " +
+      "BLENDED. scored_follow_through is over searches_scored (a session identity AND a " +
+      "channel that can react to a result), and IT is the rate to quote when asking " +
+      "whether AGENTS are consuming the KB. It is null when nothing was scoreable, never " +
+      "0.0 — zero would assert agents searched and opened nothing, when the truth is this " +
+      "instrument could not see. That nil-for-n/a is THIS field's alone: " +
+      "search_follow_through is non-null and reports 0.0 on a day with no qualifying " +
+      "searches, which is an n/a too — read it beside searches. Measured live for " +
+      "2026-08-19..29: 10.8% blended (185/1,708) against 38.0% scored, because 72% of " +
+      "that blended denominator (1,234/1,708) was recall-hook memory_recall traffic at " +
+      "3.3%; the window's 486 smoke-test calls are in neither figure. Spelled out because " +
+      "leaving the division to the caller already produced one wrong published conclusion " +
+      "while both input columns were documented.\n\n" +
       "COMPARE ROWS ONLY WITHIN A metric_version. Every row carries the version of the " +
       "definition set that produced it. Three changes have already altered what a figure here " +
       "MEANS — searched went from search calls to surfaced results, infrastructure traffic " +

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "loopctl-mcp-server",
-  "version": "2.78.0",
-  "description": "MCP server for loopctl \u2014 structural trust for AI development loops",
+  "version": "2.78.1",
+  "description": "MCP server for loopctl — structural trust for AI development loops",
   "type": "module",
   "main": "index.js",
   "bin": {