@sellable/mcp 0.1.84 → 0.1.86

package/dist/tools/campaigns.js

@@ -124,8 +124,8 @@ export const campaignToolDefinitions = [
     {
         name: "create_campaign",
         description: 'Create a new campaign offer OR resume an existing one. Low-level write tool: load create-campaign workflow instructions first via get_subskill_prompt({ subskillName: "create-campaign" }) (or bootstrap_create_campaign + nextStep). If campaignId is provided, this tool returns the watchUrl + state for that campaign instead of creating a new campaign.\n\n' +
-            "INPUTS:\n- Pass either `clientProspectId` (preferred) or `senderLinkedinUrl` for net-new campaigns.\n- `clientProspectId` is the EnrichedProspect row ID for the campaign sender, used by ICP scoring, message generation, and brief rendering.\n- `senderLinkedinUrl` may be passed when `clientProspectId` is not yet materialized; the backend will attempt to resolve a sender prospect from it.\n\n" +
-            "PREREQUISITES:\n- If you provide `senderLinkedinUrl`, it is used as a sender bootstrap signal.\n- `clientProspectId` is optional when sender URL is available and allows a direct materialized sender context.\n- `clientProspectId` is preferred for deterministic sender resolution.",
+            "INPUTS:\n- Pass either `clientProspectId` (preferred) or `senderLinkedinUrl` for net-new campaigns.\n- `clientProspectId` is the EnrichedProspect row ID for the campaign identity/client prospect, used by ICP scoring, message generation, and brief rendering.\n- `senderLinkedinUrl` may be passed when `clientProspectId` is not yet materialized; the backend will attempt to resolve a campaign identity prospect from it.\n\n" +
+            "PREREQUISITES:\n- If you provide `senderLinkedinUrl`, it is used as a campaign identity bootstrap signal, not as a connected-sender availability check.\n- `clientProspectId` is optional when sender URL is available and allows a direct materialized campaign identity context.\n- `clientProspectId` is preferred for deterministic campaign identity resolution.",
         inputSchema: {
             type: "object",
             properties: {
@@ -139,13 +139,13 @@ export const campaignToolDefinitions = [
                 },
                 clientProspectId: {
                     type: "string",
-                    description: "Use this for existing sender prospects. For brand-new senders, pass `senderLinkedinUrl` and the backend will attempt sender lookup/creation during campaign creation.",
+                    description: "Use this for existing campaign identity/client prospect rows. For brand-new campaign identities, pass `senderLinkedinUrl` and the backend will attempt prospect lookup/creation during campaign creation.",
                 },
                 // `senderLinkedinUrl` (not `linkedinUrl`) to disambiguate from
                 // prospect-side `linkedinUrl` fields used in other tools (research-prospect etc.).
                 senderLinkedinUrl: {
                     type: "string",
-                    description: "Optional sender LinkedIn profile URL. Use when sender prospect ID is not yet materialized and backend bootstrap should be used.",
+                    description: "Optional campaign identity LinkedIn profile URL. Use when the client prospect ID is not yet materialized and backend bootstrap should be used.",
                 },
                 offerPositioning: {
                     type: "object",
@@ -623,7 +623,7 @@ export async function createCampaign(input) {
             `or all create fields. Missing: ${missing.join(", ")}.\n\n` +
             "Remediation:\n" +
             '- For full workflow, call get_subskill_prompt({ subskillName: "create-campaign" }) and follow it.\n' +
-            "- For net-new campaign creation: run the `research-sender` flow first, call `complete_sender_research`, then pass either `clientProspectId` (preferred) or `senderLinkedinUrl` and let the backend resolve sender context at campaign creation time.\n" +
+            "- For net-new campaign creation: run the `research-sender` flow first as campaign identity/client prospect research, call `complete_sender_research`, then pass either `clientProspectId` (preferred) or `senderLinkedinUrl` and let the backend resolve campaign identity context at campaign creation time.\n" +
             "- For resume, call create_campaign with campaignId only.");
     }
     assertNetNewCreateCampaignResearchReady();

package/dist/tools/flow-preflight.js

@@ -88,21 +88,21 @@ export function assertResearchPromptLoaded(mode = "any") {
         };
     }
     if (mode === "sender") {
-        throw new Error('FLOW_PRECONDITION: net-new create_campaign requires sender research preload. Call get_subskill_prompt({ subskillName: "research-sender" }) and run sender research before create_campaign.');
+        throw new Error('FLOW_PRECONDITION: net-new create_campaign requires campaign identity research preload. Call get_subskill_prompt({ subskillName: "research-sender" }) and run client/company prospect research before create_campaign.');
     }
     throw new Error("FLOW_PRECONDITION: research preload missing. Call get_subskill_prompt with the matching research wrapper (research-sender or research-prospect), then run research before continuing.");
 }
 export function assertNetNewCreateCampaignResearchReady() {
     const senderResearchPromptState = researchPromptStates.sender;
     if (!senderResearchPromptState) {
-        throw new Error('FLOW_PRECONDITION: net-new create_campaign requires sender research preload. Call get_subskill_prompt({ subskillName: "research-sender" }) and run sender research before create_campaign.');
+        throw new Error('FLOW_PRECONDITION: net-new create_campaign requires campaign identity research preload. Call get_subskill_prompt({ subskillName: "research-sender" }) and run client/company prospect research before create_campaign.');
     }
     if (!senderResearchCompletionState) {
-        throw new Error("FLOW_PRECONDITION: completed sender research is required before create_campaign. After running research-sender (parallel batch of fetch_linkedin_profile + fetch_company + WebSearches), call complete_sender_research({ depth, proofItemsFound, caseStudyItemsFound, credibilitySignalsFound, notes? }).");
+        throw new Error("FLOW_PRECONDITION: completed campaign identity research is required before create_campaign. After running research-sender for client/company prospect context (parallel batch of fetch_linkedin_profile + fetch_company + WebSearches), call complete_sender_research({ depth, proofItemsFound, caseStudyItemsFound, credibilitySignalsFound, notes? }).");
     }
     if (new Date(senderResearchCompletionState.completedAt).getTime() <
         new Date(senderResearchPromptState.loadedAt).getTime()) {
-        throw new Error("FLOW_PRECONDITION: sender research completion is older than the latest research-sender prompt load. Re-run sender research and call complete_sender_research again.");
+        throw new Error("FLOW_PRECONDITION: campaign identity research completion is older than the latest research-sender prompt load. Re-run client/company prospect research and call complete_sender_research again.");
     }
     return {
         ok: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/SKILL.md

@@ -227,17 +227,19 @@ Validated draft directory:
   three specific options plus `Other / custom`. Do not ask this as plain
   numbered chat.
 
-  Then run one lightweight sender/company research pass before asking buyer,
-  offer, proof, or source questions. Prefer loading
+  Then run one lightweight campaign identity research pass before campaign
+  shell creation. The legacy subskill/tool names are `research-sender` and
+  `complete_sender_research`, but treat them as client/company prospect research
+  for the campaign, not as a connected-sender availability check. Prefer loading
   `get_subskill_prompt({ subskillName: "research-sender" })`, running its
   fetch/profile/company/WebSearch batch when those tools are exposed, and
   calling `complete_sender_research`. If WebSearch is unavailable, use the
   available MCP profile/company/post tools, call `complete_sender_research`
-  with the evidence counts found, and continue with explicit gaps. The setup
-  questions should use the confirmed company context and researched proof /
-  positioning options so they do not feel generic. If identity is still
-  unavailable, use neutral/custom intake options instead of guessed
-  vertical-specific options.
+  with the evidence counts found, and continue with explicit gaps. Setup
+  questions and the campaign brief should use the confirmed company context and
+  researched proof / positioning options so they do not feel generic. If
+  identity is still unavailable, use neutral/custom intake options instead of
+  guessed vertical-specific options.
 
 - Before the identity gate, use this customer-facing shape:
 
@@ -299,6 +301,14 @@ Validated draft directory:
   Do not mention internal artifact names, local folders, shell commands, or
   persistence in this preamble.
 
+  Before calling `create_campaign` for the watchable shell, make sure the
+  campaign identity research marker is satisfied: load `research-sender` if it
+  has not already been loaded, do the lightweight profile/company lookup, and
+  call `complete_sender_research`. This is still client/company prospect context
+  for the campaign brief. Do not call `list_senders`, do not ask the user to
+  connect a sender, and do not surface sender availability until
+  Settings/final handoff.
+
 - Before asking for brief approval, render a slim approval brief in the chat and
   keep the rich current brief in `brief.md`. Use rendered Markdown directly:
   `##` heading, bold field labels, numbered section labels, and short bullets.
@@ -353,9 +363,9 @@ Validated draft directory:
   `RevOps`, `outbound systems`, or `pipeline architecture` unless they are
   translated into what the user can understand.
 
-  After rendering that brief, ask for brief approval when there is a real
-  strategic choice or the user has not already made the direction obvious. The
-  user-facing choice should be approve/revise language, not "looks good".
+  After rendering that brief, ask for brief approval before lead sourcing in
+  hosted net-new runs. The user-facing choice should be approve/revise language,
+  not "looks good".
   Approval options should refer to what the user just read, e.g. `Approve this
 brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   When the user chose `Find people for me` and the host supports subagents,
@@ -379,13 +389,13 @@ brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   the visible approved brief; if the sidecar is still running, wait quietly or
   finish the write synchronously at that boundary.
 
-- After the brief is approved or auto-confirmed, show the next progress line:
+- After the brief is approved, show the next progress line:
   `Cool. Now I'm going to find people who are both a good fit and active enough
 to be worth a LinkedIn test. I'll compare source paths by expected volume,
 sampled ICP fit, activity/warmth signal, cleanup risk, and tradeoffs. This
 usually takes ~3-5 min, and I'll show you the source decision + sample before
 anything goes live.`
-- After the lead sample/source decision is ready and approved or auto-confirmed,
+- After the lead sample/source decision is ready and approved,
   show the next progress line:
   `Lead source is set. I'll import the first 10-row review batch into the
 campaign table, then use that same batch to tighten the fit filter and draft the
@@ -544,8 +554,14 @@ workstreams`, `in parallel`, or `background` unless parallel branches were
 
 <conditional_gates>
 
-There are two human gates:
+There are four customer-visible gates in the net-new hosted flow:
 
+- `brief-review` asks whether to approve the rendered campaign brief before
+  lead sourcing starts. Do not skip this by inferring approval from setup
+  answers.
+- `lead-review` / source decision asks whether to approve the selected source
+  path and sample before moving into filter/message work. Do not skip this by
+  compressing the source decision into message review.
 - `message-review` is the mandatory pre-import message quality gate. It asks
   only whether to proceed with the selected message (`approve-message`) or run
   one more messaging revision (`revise-messaging`). `approve-message` authorizes

package/skills/create-campaign-v2/core/flow.v2.json

@@ -112,23 +112,20 @@
       "label": "Campaign brief interview",
       "onEnter": [
         {
-          "action": "resolve_company_identity_before_strategy_packet",
+          "action": "resolve_campaign_identity_before_strategy_packet",
           "optional": false,
           "when": "before_founder_strategy_source_packet",
           "allowedTools": [
-            "list_senders",
-            "get_sender",
             "fetch_company",
             "fetch_linkedin_profile",
             "WebFetch",
             "WebSearch"
           ],
           "maxCalls": {
-            "list_senders": 1,
             "identityLookup": 1,
             "companyLookupAfterIdentityConfirm": 1
           },
-          "quietlyCheckConnectedSendersFirst": true,
+          "quietlyCheckConnectedSendersFirst": false,
           "preferUserLinkedInWhenSenderInferenceIsWeak": true,
           "doNotPresentSenderPickerBeforeIdentityInference": true,
           "confirmCompanyBeforeStrategyQuestions": true,
@@ -149,7 +146,7 @@
           "chatRenderRule": "If the sender/company context has multiple campaignable product lines, services, or offers, ask exactly one single-choice structured campaign-focus question before buyer/offer/proof/source. Do not ask numbered plain-chat choices when the structured question tool is available. Do not use checkbox or multi-select wording."
         },
         {
-          "action": "run_sender_company_research_before_strategy_packet",
+          "action": "run_campaign_identity_research_before_strategy_packet",
           "target": "research-sender",
           "when": "after_identity_and_campaign_focus_before_founder_strategy_source_packet",
           "allowedTools": [
@@ -316,8 +313,6 @@
         "get_subskill_asset",
         "get_auth_status",
         "get_active_workspace",
-        "list_senders",
-        "get_sender",
         "complete_sender_research",
         "fetch_company",
         "fetch_company_posts",