conduyt-mcp 4.14.0 → 4.17.0

package/README.md

@@ -2,7 +2,7 @@
 
 MCP server for [Conduyt CRM](https://conduyt.app) — expose your CRM as AI-accessible tools. Covers the core CRM surface (contacts, deals, pipelines, custom fields, automations, messaging, and more); use `conduyt_api_catalog` to discover the full set of 500+ REST endpoints.
 
-## 161 Tools
+## 173 Tools
 
 ### Discovery
 | Tool | Description |
@@ -258,6 +258,26 @@ MCP server for [Conduyt CRM](https://conduyt.app) — expose your CRM as AI-acce
 | `conduyt_export_contact_data` | GDPR data-portability export — full portable JSON of everything held about a contact (owner/admin) |
 | `conduyt_forget_contact` | IRREVERSIBLE GDPR right-to-be-forgotten erasure — requires `confirm='FORGET'` (owner only) |
 
+### Dialer
+| Tool | Description |
+|------|-------------|
+| `conduyt_sync_local_presence` | Reconcile the Local Presence pool from Twilio (LP-named, voice, US +1, max 50) |
+
+### Lifecycle (master lead status + intake deals)
+| Tool | Description |
+|------|-------------|
+| `conduyt_get_lifecycle_settings` | Effective master statuses (defaults + customs) and intake-deals config |
+| `conduyt_update_intake_deals` | Configure automatic deal creation on live intake (webhooks, forms, bookings) |
+| `conduyt_update_master_statuses` | Set the account's custom lead lifecycle statuses |
+
+### Reply Capture (inbound email)
+| Tool | Description |
+|------|-------------|
+| `conduyt_reply_capture_get` | Current state: configured/live, capture domain + reply address, pending DNS records, provider health |
+| `conduyt_reply_capture_setup` | Create the receiving subdomain (must be a subdomain of the verified sending domain) and return its DNS records |
+| `conduyt_reply_capture_verify` | Check DNS and promote to live once the provider confirms inbound receiving |
+| `conduyt_reply_capture_remove` | Remove capture (and finish an interrupted removal) — requires `confirm='REMOVE'`; replies to already-sent email are lost |
+
 ## Setup
 
 ```bash

package/dist/index.js

@@ -36,6 +36,8 @@ import { registerAiExtendedTools } from "./tools/ai-extended.js";
 import { registerWorkflowSandboxTools } from "./tools/workflow-sandbox.js";
 import { registerPrivacyTools } from "./tools/privacy.js";
 import { registerAccountExportTools } from "./tools/account-exports.js";
+import { registerLifecycleTools } from "./tools/lifecycle.js";
+import { registerReplyCaptureTools } from "./tools/reply-capture.js";
 const apiUrl = process.env.CONDUYT_API_URL;
 const apiKey = process.env.CONDUYT_API_KEY;
 if (!apiUrl || !apiKey) {
@@ -94,5 +96,7 @@ registerAiExtendedTools(server, client);
 registerWorkflowSandboxTools(server, client);
 registerPrivacyTools(server, client);
 registerAccountExportTools(server, client);
+registerLifecycleTools(server, client);
+registerReplyCaptureTools(server, client);
 const transport = new StdioServerTransport();
 await server.connect(transport);

package/dist/tools/automations.js

@@ -45,6 +45,10 @@ export function registerAutomationTools(server, client) {
         schedule: z.string().optional().describe("Updated cron schedule"),
         scheduleTimezone: z.string().optional().describe("Updated timezone"),
         stopOnResponse: z.boolean().optional().describe("Stop drip if contact responds"),
+        activeRunPolicy: z
+            .enum(["keep", "restart"])
+            .optional()
+            .describe("What a NEW trigger does when the contact is already mid-sequence: 'keep' (default — skip, existing run keeps its schedule) or 'restart' (cancel the parked run and re-enroll from step 1)"),
     }, async ({ id, ...updates }) => {
         const result = await client.patch(`/api/v1/automations/${id}`, updates);
         return formatResult(result);

package/dist/tools/calls.js

@@ -46,4 +46,8 @@ export function registerCallTools(server, client) {
         const result = await client.get(`/api/v1/calls/${encodeURIComponent(id)}`);
         return formatResult(result);
     });
+    server.tool("conduyt_sync_local_presence", "Sync the dialer's Local Presence number pool from the account's Twilio subaccount. IMPORTANT — sync only adopts numbers that meet ALL of: (1) the Twilio FriendlyName contains a standalone 'LP' (or 'LocalPres'), e.g. 'LP Miami 305'; (2) the number is voice-capable; (3) it is a US +1 E.164 number. The first 50 matches in sorted order become the pool; anything already in the pool that no longer matches is REMOVED. So buying a number is not enough — name it with the LP convention in Twilio first, then run this. Returns pool/added/removed/matched. Requires settings:edit.", {}, async () => {
+        const result = await client.post("/api/v1/dialer/local-presence/sync", {});
+        return formatResult(result);
+    });
 }

package/dist/tools/contacts.js

@@ -52,7 +52,8 @@ export function registerContactTools(server, client) {
         lastName: z.string().optional().describe("Last name"),
         phone: z.string().optional().describe("Phone number"),
         company: z.string().optional().describe("Company name"),
-        source: z.string().optional().describe("Lead source (e.g. 'website', 'referral', 'import')"),
+        source: z.string().trim().min(1).max(100).optional().describe("Lead source (e.g. 'website', 'referral', 'import') — FIRST-WRITE-WINS acquisition truth for the lead; later inbound events do not overwrite it. 1-100 chars."),
+        masterStatus: z.string().trim().min(1).max(40).optional().describe("Lifecycle status of the LEAD (master record), distinct from any deal's status: 'open' (default), 'won', 'lost', 'abandoned', 'disqualified', or an account-defined custom status. A terminal status (won/lost/abandoned/disqualified) SILENCES all outbound automations for this contact — drips, sequences, and scheduled sends stop. Use conduyt_get_lifecycle_settings to see the account's configured statuses."),
         tags: z.array(z.string()).optional().describe("Tag UUIDs to apply (tags must already exist — create them with conduyt_create_tag first)"),
         customFields: z.record(z.any()).optional().describe("Structured custom-field values keyed by field key, e.g. { lead_temperature: 'hot', budget: 50000 }. Define fields first with conduyt_create_custom_field (entity 'contact')."),
         custom_fields: z.record(z.any()).optional().describe("Alias for customFields (snake_case). Provide only one of customFields / custom_fields."),
@@ -69,6 +70,8 @@ export function registerContactTools(server, client) {
         lastName: z.string().optional().describe("Updated last name"),
         phone: z.string().optional().describe("Updated phone"),
         company: z.string().optional().describe("Updated company name"),
+        source: z.string().trim().min(1).max(100).nullable().optional().describe("Correct the lead's first-touch source (normally first-write-wins and set at creation — update only to FIX bad attribution). Pass null to clear."),
+        masterStatus: z.string().trim().min(1).max(40).optional().describe("Lifecycle status of the LEAD (master record), distinct from any deal's status: 'open' (default), 'won', 'lost', 'abandoned', 'disqualified', or an account-defined custom status. A terminal status (won/lost/abandoned/disqualified) SILENCES all outbound automations for this contact — drips, sequences, and scheduled sends stop. Use conduyt_get_lifecycle_settings to see the account's configured statuses."),
         customFields: z.record(z.any()).optional().describe("Structured custom-field values to merge, keyed by field key. Omit a key to leave it unchanged."),
         custom_fields: z.record(z.any()).optional().describe("Alias for customFields (snake_case). Provide only one of customFields / custom_fields."),
     }, async ({ id, customFields, custom_fields, ...updates }) => {

package/dist/tools/deals.js

@@ -84,6 +84,7 @@ export function registerDealTools(server, client) {
         probability: z.number().min(0).max(1).optional().describe("Win probability as a 0–1 fraction (e.g. 0.75 = 75%)"),
         expectedCloseDate: z.string().optional().describe("Expected close date (ISO 8601, e.g. '2026-09-30')"),
         assignedTo: z.string().optional().describe("Assigned user (owner) UUID"),
+        source: z.string().trim().min(1).max(500).optional().describe("Attribution source for THIS deal — the trigger that produced it (e.g. 'sms-reply', 'booking:demo', 'partner-referral'). Each deal carries its own source; the contact's source stays the first-touch acquisition truth. 1-500 chars."),
         customFields: z.record(z.any()).optional().describe("Structured custom-field values keyed by field key, e.g. { limit_of_indemnity: 5000000, commission_pct: 12.5 }. Define fields first with conduyt_create_custom_field."),
     }, async (params) => {
         const result = await client.post("/api/v1/deals", params);
@@ -102,6 +103,7 @@ export function registerDealTools(server, client) {
         probability: z.number().min(0).max(1).optional().describe("Win probability as a 0–1 fraction (e.g. 0.75 = 75%)"),
         expectedCloseDate: z.string().optional().describe("Expected close date (ISO 8601)"),
         assignedTo: z.string().optional().describe("Reassign to user (owner) UUID"),
+        source: z.string().trim().min(1).max(500).nullable().optional().describe("Attribution source for THIS deal (the trigger that produced it) — distinct from the contact's first-touch source. Pass null to clear it; a blank string is rejected. 1-500 chars."),
         customFields: z.record(z.any()).optional().describe("Structured custom-field values to merge, keyed by field key"),
     }, async ({ id, ...updates }) => {
         const result = await client.patch(`/api/v1/deals/${id}`, updates);

package/dist/tools/lifecycle.d.ts

@@ -0,0 +1,3 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { ConduytClient } from "../client.js";
+export declare function registerLifecycleTools(server: McpServer, client: ConduytClient): void;

package/dist/tools/lifecycle.js

@@ -0,0 +1,64 @@
+import { z } from "zod";
+import { formatResult } from "../client.js";
+/**
+ * Lifecycle v2 settings (master lead status + intake deals). The master lead
+ * is the acquisition truth (first-write-wins source, one lifecycle status);
+ * deals are per-trigger children with their own source and owner. A terminal
+ * master status silences every outbound automation for that contact.
+ */
+const DEFAULT_MASTER_STATUSES = ["open", "won", "lost", "abandoned", "disqualified"];
+// Mirror of the API's masterStatuses validator (20 names max, 1-40 chars,
+// letters/numbers/spaces/-/_ only) so agent-generated input fails fast here
+// instead of late at the API.
+const masterStatusName = z
+    .string()
+    .trim()
+    .min(1)
+    .max(40)
+    .regex(/^[a-z0-9][a-z0-9 _-]*$/i, "letters, numbers, spaces, - and _ only");
+export function registerLifecycleTools(server, client) {
+    server.tool("conduyt_get_lifecycle_settings", "Read the account's Lifecycle v2 configuration, shaped for read-before-write: masterStatuses.effective is the full list a contact's masterStatus may take (the five built-in defaults plus the account's customs — the raw settings key stores only the customs); intakeDeals is the automatic deal-on-intake config, or null with an intakeDealsNote explaining that null can mean either not-configured or not-visible-to-your-key (the setting is admin-visible; member-tier responses omit it).", {}, async () => {
+        const result = await client.get("/api/v1/settings");
+        const raw = result?.data ?? {};
+        const customs = Array.isArray(raw.masterStatuses)
+            ? raw.masterStatuses.filter((s) => typeof s === "string")
+            : [];
+        // intakeDeals is admin-visible only: member-shaped responses omit it,
+        // and an unconfigured account also lacks it. The two are not
+        // distinguishable from here, so null is reported with a note saying so.
+        const intakeDeals = raw.intakeDeals && typeof raw.intakeDeals === "object" ? raw.intakeDeals : null;
+        const shaped = {
+            masterStatuses: {
+                defaults: DEFAULT_MASTER_STATUSES,
+                customs,
+                effective: [...DEFAULT_MASTER_STATUSES, ...customs.filter((c) => !DEFAULT_MASTER_STATUSES.includes(c.toLowerCase()))],
+            },
+            intakeDeals: intakeDeals ?? null,
+            intakeDealsNote: intakeDeals === null
+                ? "null = not configured, OR your key's role cannot read this admin-visible setting; configure/verify with an admin-tier key"
+                : undefined,
+        };
+        return formatResult({ data: shaped });
+    });
+    server.tool("conduyt_update_intake_deals", "Configure automatic deal creation on LIVE intake (inbound webhook contact upserts, public form submissions, public bookings). When enabled, each ELIGIBLE intake event mints a deal in the chosen pipeline/stage stamped with the trigger's own source. Exclusions that apply even under reInbound 'always': bulk imports never mint, staff/calendar/dialer-created appointments never mint, an exact replay of the same occurrence never mints twice, a same-source event for the same contact+pipeline within 10 minutes is treated as a delivery retry and skipped, and a contact whose masterStatus is terminal (won/lost/abandoned/disqualified) gets no new intake deals. reInbound governs contacts that already exist: 'if_no_open' (default, recommended) also skips when the contact already has an open deal in that pipeline; 'never' mints only for brand-new contacts. Requires settings:edit.", {
+        enabled: z.boolean().describe("Turn automatic intake-deal creation on or off"),
+        pipelineId: z.string().uuid().describe("Pipeline UUID the intake deals land in (conduyt_list_pipelines)"),
+        stageId: z.string().uuid().describe("Starting stage UUID within that pipeline"),
+        reInbound: z
+            .enum(["always", "if_no_open", "never"])
+            .optional()
+            .describe("Policy for contacts that already exist (default 'if_no_open')"),
+    }, async (params) => {
+        const result = await client.patch("/api/v1/settings", { intakeDeals: params });
+        return formatResult(result);
+    });
+    server.tool("conduyt_update_master_statuses", "Set the account's custom lead lifecycle statuses. The five defaults (open, won, lost, abandoned, disqualified) always exist and cannot be removed; this REPLACES the custom list on top of them (max 20 names, 1-40 chars each, letters/numbers/spaces/-/_ only). Terminal statuses stop all outbound automation for a contact. Requires settings:edit.", {
+        statuses: z
+            .array(masterStatusName)
+            .max(20)
+            .describe("Custom status names to make available alongside the defaults, e.g. ['nurturing', 'in underwriting']"),
+    }, async ({ statuses }) => {
+        const result = await client.patch("/api/v1/settings", { masterStatuses: statuses });
+        return formatResult(result);
+    });
+}

package/dist/tools/reply-capture.d.ts

@@ -0,0 +1,29 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { ConduytClient } from "../client.js";
+/**
+ * Reply capture: the dedicated receiving subdomain that lets replies to CRM
+ * emails record and thread against the contact.
+ *
+ * Lifecycle mirrors the sending domain: create -> DNS records -> verify ->
+ * live. It is a strict subdomain of the account's own VERIFIED sending
+ * domain (the API refuses anything else — that rule is the cross-tenant
+ * fence, not a formatting preference), and only ONE capture domain can be
+ * set up at a time.
+ *
+ * Outcomes that are NORMAL here, not failures to retry blindly:
+ *  - 409 "already configured" — remove the current one first.
+ *  - 409 "contact support to reconcile" — the row is in an operator-repair
+ *    state (a provider create whose response was lost, or a stored provider
+ *    id that does not resolve to this domain). Support repairs it through a
+ *    super-admin, session-only endpoint that API keys deliberately cannot
+ *    reach; do not loop on it.
+ *  - 429 — the per-account budget (setup/teardown are limited per hour,
+ *    verification per minute). DNS takes minutes to propagate; wait.
+ *  - 503 — the shared email-provider allowance is busy with customer sends.
+ *    Retry in a moment; it says nothing about the domain's health.
+ *
+ * Removal is IRREVERSIBLE for in-flight threads: replies to emails already
+ * sent go to an address that no longer routes, so they are lost. Hence the
+ * confirm gate below.
+ */
+export declare function registerReplyCaptureTools(server: McpServer, client: ConduytClient): void;

package/dist/tools/reply-capture.js

@@ -0,0 +1,63 @@
+import { z } from "zod";
+import { formatResult } from "../client.js";
+/**
+ * Reply capture: the dedicated receiving subdomain that lets replies to CRM
+ * emails record and thread against the contact.
+ *
+ * Lifecycle mirrors the sending domain: create -> DNS records -> verify ->
+ * live. It is a strict subdomain of the account's own VERIFIED sending
+ * domain (the API refuses anything else — that rule is the cross-tenant
+ * fence, not a formatting preference), and only ONE capture domain can be
+ * set up at a time.
+ *
+ * Outcomes that are NORMAL here, not failures to retry blindly:
+ *  - 409 "already configured" — remove the current one first.
+ *  - 409 "contact support to reconcile" — the row is in an operator-repair
+ *    state (a provider create whose response was lost, or a stored provider
+ *    id that does not resolve to this domain). Support repairs it through a
+ *    super-admin, session-only endpoint that API keys deliberately cannot
+ *    reach; do not loop on it.
+ *  - 429 — the per-account budget (setup/teardown are limited per hour,
+ *    verification per minute). DNS takes minutes to propagate; wait.
+ *  - 503 — the shared email-provider allowance is busy with customer sends.
+ *    Retry in a moment; it says nothing about the domain's health.
+ *
+ * Removal is IRREVERSIBLE for in-flight threads: replies to emails already
+ * sent go to an address that no longer routes, so they are lost. Hence the
+ * confirm gate below.
+ */
+export function registerReplyCaptureTools(server, client) {
+    server.tool("conduyt_reply_capture_get", "Get the account's reply-capture state: whether it is configured and live, the capture domain and reply address, DNS records for a pending setup, and provider health. health='checking' with a healthWarning means the provider is re-checking DNS — capture stays active. degraded=true means the provider can no longer receive on that domain and it must be removed and set up again. needsSupport=true means an operator must reconcile it first. cleanupPending=true means a previous removal did not finish at the provider — call conduyt_reply_capture_remove again to complete it.", {}, async () => {
+        const result = await client.get("/api/v1/email-domains/reply-capture");
+        return formatResult(result);
+    });
+    server.tool("conduyt_reply_capture_setup", "Start reply-capture setup: creates the receiving domain at the email provider and returns the DNS records to add. The domain MUST be a strict subdomain of the account's own verified sending domain (omit it to use the suggested 'reply.<sending-domain>'); anything else is refused. Requires a verified sending domain first. After adding the DNS records, call conduyt_reply_capture_verify. A 409 means capture is already configured, a setup is already in progress, or the previous one still needs operator reconciliation.", {
+        domain: z
+            .string()
+            // TRIM BEFORE the emptiness check: the API trims and treats a blank
+            // as "omitted", silently creating reply.<sending-domain>. An empty
+            // agent variable would then burn mutation quota, take the account's
+            // ONE capture slot, and block sending-domain removal. Fail here.
+            .trim()
+            .min(1, "domain must not be blank — omit it entirely to use the suggested default")
+            .optional()
+            .describe("Capture subdomain, e.g. 'reply.acme.com'. Must be a subdomain of the account's verified sending domain. Omit to use the suggested default."),
+    }, async ({ domain }) => {
+        // An absent domain is serialized away, which is exactly how the API
+        // reads "use the suggested reply.<sending-domain>".
+        const result = await client.post("/api/v1/email-domains/reply-capture", { domain });
+        return formatResult(result);
+    });
+    server.tool("conduyt_reply_capture_verify", "Check the pending reply-capture domain's DNS and promote it to live once the provider reports it verified with inbound receiving in place. Returns verified=false plus the current DNS record states while records are still propagating — that is expected, not an error; poll sparingly (DNS takes minutes, and this endpoint is budgeted per account). Promotion is what turns on inbound matching and the Reply-To on outgoing email.", {}, async () => {
+        const result = await client.post("/api/v1/email-domains/reply-capture/verify", {});
+        return formatResult(result);
+    });
+    server.tool("conduyt_reply_capture_remove", "Remove reply capture: stops using the capture Reply-To on new email, stops matching inbound replies, and deletes the receiving domain at the provider. Replies to emails ALREADY SENT will be lost — there is no undo. Also completes a previously interrupted removal (cleanupPending) without creating anything new. Requires an explicit confirm='REMOVE'. Note: while any reply-capture row exists the sending domain cannot be removed, so this is also the step that unblocks that.", {
+        confirm: z
+            .literal("REMOVE")
+            .describe("Must be exactly 'REMOVE'. Hard safety gate: replies to already-sent emails are irrecoverably lost once the capture domain is gone."),
+    }, async () => {
+        const result = await client.del("/api/v1/email-domains/reply-capture");
+        return formatResult(result);
+    });
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conduyt-mcp",
-  "version": "4.14.0",
+  "version": "4.17.0",
   "description": "MCP server for Conduyt CRM — expose CRM operations as AI-accessible tools",
   "type": "module",
   "main": "dist/index.js",

package/scripts/coverage-manifest.json

@@ -203,7 +203,7 @@
     {
       "match": "/api/v1/email-domains",
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered \u2014 see the reply_capture_* tools)"
     },
     {
       "match": "/api/v1/mailbox",
@@ -501,4 +501,4 @@
       "reason": "outbound webhook subscription management (distinct from the inbound /webhooks/ receivers)"
     }
   ]
-}
+}

package/scripts/coverage-matrix.json

@@ -1,10 +1,10 @@
 {
-  "generatedAt": "2026-07-23T16:00:26.290Z",
-  "toolCount": 165,
-  "totalEndpoints": 827,
+  "generatedAt": "2026-08-06T22:46:04.536Z",
+  "toolCount": 173,
+  "totalEndpoints": 842,
   "counts": {
-    "covered": 154,
-    "excluded": 240,
+    "covered": 161,
+    "excluded": 248,
     "planned": 433,
     "uncategorized": 0
   },
@@ -297,6 +297,14 @@
       "status": "excluded",
       "reason": "super-admin platform operations (Conduyt staff only)"
     },
+    "GET /api/v1/admin/reply-capture/reconcile": {
+      "status": "excluded",
+      "reason": "super-admin platform operations (Conduyt staff only)"
+    },
+    "POST /api/v1/admin/reply-capture/reconcile": {
+      "status": "excluded",
+      "reason": "super-admin platform operations (Conduyt staff only)"
+    },
     "GET /api/v1/admin/scale-readiness": {
       "status": "excluded",
       "reason": "super-admin platform operations (Conduyt staff only)"
@@ -1289,6 +1297,10 @@
       "status": "planned",
       "reason": "conversation thread surfaces"
     },
+    "POST /api/v1/conversations/:contactId/compliance": {
+      "status": "planned",
+      "reason": "conversation thread surfaces"
+    },
     "GET /api/v1/conversations/:contactId/state": {
       "status": "planned",
       "reason": "conversation thread surfaces"
@@ -1321,6 +1333,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/capture-rfc-ids": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/cleanup-audit-logs": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1373,6 +1389,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/process-consent-outbox": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/process-data-model-jobs": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1465,6 +1485,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/reap-qa-tenants": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/reconcile-document-sends": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1473,6 +1497,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/reconcile-reply-capture": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/recurring-tasks": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1533,6 +1561,14 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/sync-local-presence": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
+    "POST /api/v1/cron/sync-local-presence": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/task-reminders": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1827,6 +1863,12 @@
       "status": "excluded",
       "reason": "realtime browser dialer (WebRTC tokens, live call control) — needs a live audio session"
     },
+    "POST /api/v1/dialer/local-presence/sync": {
+      "status": "covered",
+      "tools": [
+        "conduyt_sync_local_presence"
+      ]
+    },
     "POST /api/v1/dialer/mirror-token": {
       "status": "excluded",
       "reason": "realtime browser dialer (WebRTC tokens, live call control) — needs a live audio session"
@@ -2015,27 +2057,51 @@
     },
     "GET /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "POST /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "PATCH /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "DELETE /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
+    },
+    "GET /api/v1/email-domains/reply-capture": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_get"
+      ]
+    },
+    "POST /api/v1/email-domains/reply-capture": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_setup"
+      ]
+    },
+    "DELETE /api/v1/email-domains/reply-capture": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_remove"
+      ]
+    },
+    "POST /api/v1/email-domains/reply-capture/verify": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_verify"
+      ]
     },
     "GET /api/v1/email-domains/status": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "POST /api/v1/email-domains/verify": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "POST /api/v1/email/send": {
       "status": "covered",
@@ -2437,6 +2503,10 @@
       "status": "planned",
       "reason": "message surfaces beyond send tools"
     },
+    "GET /api/v1/messages/:id/media/:mediaIndex": {
+      "status": "planned",
+      "reason": "message surfaces beyond send tools"
+    },
     "GET /api/v1/messages/sms/:id": {
       "status": "planned",
       "reason": "message surfaces beyond send tools"
@@ -2984,12 +3054,17 @@
       ]
     },
     "GET /api/v1/settings": {
-      "status": "planned",
-      "reason": "account settings read/update surfaces"
+      "status": "covered",
+      "tools": [
+        "conduyt_get_lifecycle_settings"
+      ]
     },
     "PATCH /api/v1/settings": {
-      "status": "planned",
-      "reason": "account settings read/update surfaces"
+      "status": "covered",
+      "tools": [
+        "conduyt_update_intake_deals",
+        "conduyt_update_master_statuses"
+      ]
     },
     "GET /api/v1/settings/ai": {
       "status": "planned",