@leadbay/mcp 0.20.0 → 0.20.1

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog — @leadbay/mcp
 
+## 0.20.1 — 2026-06-15
+
+- **Triage board stays the first next-step option on a poor-fit batch** (`leadbay_daily_check_in`): when today's batch is an ICP mismatch (every lead AI-scored off-profile), the agent was demoting the interactive triage board below "refine audience" in the NEXT STEPS widget — the plain ordering rule kept losing to the agent's own leverage judgment ("the whole batch is junk, so lead with fixing the lens"). The workflow contract requires the named artifact to be the FIRST option. The ordering rule now holds the triage board at position 1 even on a mismatched batch; the mismatch is surfaced in the prose nudge and offered as a *later* "refine the lens" option, never by displacing the artifact. Verified 5/5/5/5 across 3 consecutive eval runs on an all-off-ICP batch (the exact case that defeated the weaker rule).
+
 ## 0.20.0 — 2026-06-15
 
 - **Proactive update proposal on a fresh session** (product#3742): the auto-update check already ran at boot, but the resulting proposal only reached the user if the agent happened to call `leadbay_account_status` — which a fresh session rarely does, so the "newer version available" prompt was effectively invisible. The cached `update_available` block now also rides along on `_meta.update_available` of the **first ordinary tool result** of a session while an upgrade is pending, gated once-per-version so it surfaces exactly once. `leadbay_account_status` keeps carrying it as a top-level field. The server-instruction paragraph now tells the agent to surface the `ask_user_input_v0` prompt whenever it sees the field on *any* response.

package/dist/bin.js

@@ -22038,7 +22038,7 @@ Contact enrichment is offered in the NEXT STEPS widget below \u2014 do NOT emit
 
 **REQUIRED OPTIONS \u2014 triggers and position rules:**
 - **Recurring language** ("every day", "every morning", "I do this every", "remind me", "automate this", "recurring"): add "Schedule 'Daily prospecting check-in' as a recurring task" and place it **first**.
-- **\u22655 leads returned**: add "Build an interactive lead triage board for this batch" and place it **first** (or second if the scheduling offer above also applies).
+- **\u22655 leads returned**: add "Build an interactive lead triage board for this batch" and place it **first** (or second if the scheduling offer above also applies). This holds **even when the batch is a poor fit** (e.g. every lead AI-scored as off-ICP / a vertical mismatch): the triage board is still the first artifact option because the user asked to see and act on *this batch*. When the batch is a mismatch, ALSO offer "Refine the audience / lens so future batches fit better" \u2014 but as a *later* option, never displacing the triage board from first. Leading with audience-refinement instead of the artifact is a contract violation: surface the mismatch in your prose nudge, not by demoting the triage board.
 
 ## NEXT STEPS \u2014 after rendering the pull_leads table
 
@@ -22079,7 +22079,7 @@ Pick 2\u20133 items below based on what was actually observed in the response. T
 If nothing in the menu applies cleanly, suggest only "pull next page" and "research a specific lead in depth" \u2014 never invent a tool that doesn't exist.
 
 
-**Final ordering check (do this before rendering):** Recurring offer \u2192 option 1; triage board \u2192 option 1 (or 2 if scheduling is also required). Swap if needed.
+**Final ordering check (do this before rendering):** Recurring offer \u2192 option 1; triage board \u2192 option 1 (or 2 if scheduling is also required). A poor-fit / mismatched batch does NOT change this \u2014 triage board stays first, refine-audience goes later in the list. Swap if needed.
 
 # GATE \u2014 STOP
 
@@ -24623,6 +24623,7 @@ function buildServer(client, opts = {}) {
             endpoint: err._meta?.endpoint
           });
         }
+        const httpStatus2 = err._meta?.http_status;
         telemetry.captureToolCall({
           tool: name,
           ok: false,
@@ -24630,6 +24631,7 @@ function buildServer(client, opts = {}) {
           format: "error-envelope",
           bytes: errText.length,
           error_code: code,
+          ...typeof httpStatus2 === "number" ? { http_status: httpStatus2 } : {},
           triggered_by
         });
         if (COMPOSITE_FILE_TOOL_NAMES.has(name)) {
@@ -24638,7 +24640,8 @@ function buildServer(client, opts = {}) {
             last_prompt: triggered_by ?? "",
             ok: false,
             duration_ms: errDur,
-            error_code: code
+            error_code: code,
+            ...typeof httpStatus2 === "number" ? { http_status: httpStatus2 } : {}
           });
         }
         telemetry.captureException(err, buildBusinessCtx(name, err, triggered_by));
@@ -25925,7 +25928,7 @@ var OAUTH_BASE_URLS = {
     fr: "https://staging.api.leadbay.app"
   }
 };
-var VERSION = "0.20.0";
+var VERSION = "0.20.1";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
 

package/dist/http-server.js

@@ -180,7 +180,7 @@ Contact enrichment is offered in the NEXT STEPS widget below \u2014 do NOT emit
 
 **REQUIRED OPTIONS \u2014 triggers and position rules:**
 - **Recurring language** ("every day", "every morning", "I do this every", "remind me", "automate this", "recurring"): add "Schedule 'Daily prospecting check-in' as a recurring task" and place it **first**.
-- **\u22655 leads returned**: add "Build an interactive lead triage board for this batch" and place it **first** (or second if the scheduling offer above also applies).
+- **\u22655 leads returned**: add "Build an interactive lead triage board for this batch" and place it **first** (or second if the scheduling offer above also applies). This holds **even when the batch is a poor fit** (e.g. every lead AI-scored as off-ICP / a vertical mismatch): the triage board is still the first artifact option because the user asked to see and act on *this batch*. When the batch is a mismatch, ALSO offer "Refine the audience / lens so future batches fit better" \u2014 but as a *later* option, never displacing the triage board from first. Leading with audience-refinement instead of the artifact is a contract violation: surface the mismatch in your prose nudge, not by demoting the triage board.
 
 ## NEXT STEPS \u2014 after rendering the pull_leads table
 
@@ -221,7 +221,7 @@ Pick 2\u20133 items below based on what was actually observed in the response. T
 If nothing in the menu applies cleanly, suggest only "pull next page" and "research a specific lead in depth" \u2014 never invent a tool that doesn't exist.
 
 
-**Final ordering check (do this before rendering):** Recurring offer \u2192 option 1; triage board \u2192 option 1 (or 2 if scheduling is also required). Swap if needed.
+**Final ordering check (do this before rendering):** Recurring offer \u2192 option 1; triage board \u2192 option 1 (or 2 if scheduling is also required). A poor-fit / mismatched batch does NOT change this \u2014 triage board stays first, refine-audience goes later in the list. Swap if needed.
 
 # GATE \u2014 STOP
 
@@ -22279,6 +22279,7 @@ function buildServer(client, opts = {}) {
             endpoint: err._meta?.endpoint
           });
         }
+        const httpStatus2 = err._meta?.http_status;
         telemetry.captureToolCall({
           tool: name,
           ok: false,
@@ -22286,6 +22287,7 @@ function buildServer(client, opts = {}) {
           format: "error-envelope",
           bytes: errText.length,
           error_code: code,
+          ...typeof httpStatus2 === "number" ? { http_status: httpStatus2 } : {},
           triggered_by
         });
         if (COMPOSITE_FILE_TOOL_NAMES.has(name)) {
@@ -22294,7 +22296,8 @@ function buildServer(client, opts = {}) {
             last_prompt: triggered_by ?? "",
             ok: false,
             duration_ms: errDur,
-            error_code: code
+            error_code: code,
+            ...typeof httpStatus2 === "number" ? { http_status: httpStatus2 } : {}
           });
         }
         telemetry.captureException(err, buildBusinessCtx(name, err, triggered_by));
@@ -22436,7 +22439,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.20.0" : "0.0.0-dev";
+var VERSION = true ? "0.20.1" : "0.0.0-dev";
 var PORT = Number(process.env.PORT ?? 8080);
 var HOST = process.env.HOST ?? "0.0.0.0";
 var sseSessions = /* @__PURE__ */ new Map();

package/dist/installer-electron.js

@@ -1466,7 +1466,7 @@ var init_installer_gui = __esm({
     init_install_dxt();
     init_install_shared();
     init_oauth();
-    VERSION = "0.20.0";
+    VERSION = "0.20.1";
     PORT = Number(process.env.LEADBAY_INSTALLER_PORT ?? 0);
     sessions = /* @__PURE__ */ new Map();
     OAUTH_BASE_URLS = {

package/dist/installer-gui.js

@@ -873,7 +873,7 @@ async function oauthLogin(opts) {
 }
 
 // installer/installer-gui.ts
-var VERSION = "0.20.0";
+var VERSION = "0.20.1";
 var PORT = Number(process.env.LEADBAY_INSTALLER_PORT ?? 0);
 var sessions = /* @__PURE__ */ new Map();
 var OAUTH_BASE_URLS = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leadbay/mcp",
-  "version": "0.20.0",
+  "version": "0.20.1",
   "mcpName": "io.github.leadbay/leadbay-mcp",
   "description": "Model Context Protocol (MCP) server for Leadbay — AI lead discovery, qualification, and enrichment for Claude Desktop, Cursor, and Claude Code.",
   "type": "module",