@sellable/mcp 0.1.73 → 0.1.75

package/dist/tools/bootstrap.d.ts

@@ -19,6 +19,20 @@ type BootstrapBlockingError = {
     message: string;
     guidance: string;
 };
+type CampaignFramework = ReturnType<typeof getCampaignFramework>;
+type BootstrapFrameworkSummary = {
+    flowVersion: CampaignFramework["flowVersion"];
+    policyChars: number;
+    flowWorkflow: string | null;
+    flowStepCount: number | null;
+    providerOrder: string[];
+    providerIds: string[];
+    pluginIds: string[];
+    overrideKeys: string[];
+    warningCount: number;
+    warnings: string[];
+    loadFullFrameworkWith: string;
+};
 type BootstrapCreateCampaignResult = {
     requiredChecks: BootstrapCheck[];
     blockingErrors: BootstrapBlockingError[];
@@ -28,7 +42,7 @@ type BootstrapCreateCampaignResult = {
     flowVersion: "v1" | "v2";
     campaignId: string | null;
     auth: AuthStatus | null;
-    framework: ReturnType<typeof getCampaignFramework> | null;
+    framework: BootstrapFrameworkSummary | null;
     campaignContext: Awaited<ReturnType<typeof getCampaignContext>> | null;
     subskillCatalog: ListSubskillPromptsResponse | null;
     createCampaignSubskill: Omit<SubskillPromptResponse, "prompt"> | null;

package/dist/tools/bootstrap.js

@@ -34,6 +34,40 @@ function pushBlockingError(blockingErrors, check, message) {
         guidance: toGuidance(check, message),
     });
 }
+function summarizeFramework(framework) {
+    const flow = framework.flow;
+    const steps = Array.isArray(flow.steps) ? flow.steps : null;
+    const providerOrder = Array.isArray(framework.providerRegistry.defaultProviderOrder)
+        ? framework.providerRegistry.defaultProviderOrder
+        : [];
+    const providerIds = Array.isArray(framework.providerRegistry.providers)
+        ? framework.providerRegistry.providers
+            .map((provider) => provider.id)
+            .filter((id) => typeof id === "string")
+        : Object.keys(framework.providers || {});
+    const pluginIds = Array.isArray(framework.plugins)
+        ? framework.plugins
+            .map((plugin) => plugin && typeof plugin === "object" && "id" in plugin
+            ? plugin.id
+            : null)
+            .filter((id) => typeof id === "string")
+        : [];
+    return {
+        flowVersion: framework.flowVersion,
+        policyChars: framework.policy.length,
+        flowWorkflow: typeof flow.workflow === "string" ? flow.workflow : null,
+        flowStepCount: steps ? steps.length : null,
+        providerOrder,
+        providerIds,
+        pluginIds,
+        overrideKeys: Object.keys(framework.overrides || {}),
+        warningCount: framework.warnings.length,
+        warnings: framework.warnings,
+        loadFullFrameworkWith: framework.flowVersion === "v2"
+            ? 'get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "core/flow.v2.json", offset?, limit? })'
+            : 'get_campaign_framework({ flowVersion: "v1", includePlugins: true })',
+    };
+}
 export const bootstrapToolDefinitions = [
     {
         name: "bootstrap_create_campaign",
@@ -257,7 +291,7 @@ export async function bootstrapCreateCampaign(input = {}) {
         flowVersion,
         campaignId,
         auth,
-        framework,
+        framework: framework ? summarizeFramework(framework) : null,
         campaignContext,
         subskillCatalog,
         createCampaignSubskill: subskillMeta,

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -161,11 +161,44 @@ gates. Never use it to collect open text input like LinkedIn URLs, company
 domains, notes, pasted context, campaign ideas, or feedback. For open text, ask
 in normal chat and wait for the user to paste the value.
 
+For campaign setup, every structured question is single-choice in both Claude
+Code and Codex. Use mutually exclusive options, set or assume
+`multiSelect: false`, and do not use checkbox or multi-select wording. If the
+user needs a blended/custom answer, route them through `Other / custom` or a
+free-text follow-up in normal chat.
+
 Customer-facing language must call this "a couple setup choices" during normal
 campaign progress. Use "quick question panel" only when explaining a missing
 Codex/Claude setup capability. Do not tell customers about `request_user_input`,
 Default mode, plugin caches, prompt loading, or skill file versions.
 
+## Host Runtime Functions
+
+Treat host capabilities as concrete functions, not prose conventions:
+
+- `ask_user`: Claude Code uses `AskUserQuestion`; Codex uses
+  `request_user_input`. Use this for multiple-choice intake, campaign-focus
+  choices, source decisions, and approvals. Campaign setup questions are
+  single-choice only; do not use multi-select or checkbox variants. Never
+  render numbered plain-chat choices in an interactive session when the
+  structured question function is exposed.
+- `load_subprompt`: call
+  `mcp__sellable__get_subskill_prompt({ subskillName, offset?, limit? })` and
+  continue chunks until `hasMore` is false.
+- `load_subprompt_asset`: call
+  `mcp__sellable__get_subskill_asset({ subskillName, assetPath, offset?, limit? })`
+  and continue chunks until `hasMore` is false.
+- `load_source_scout_registry`: call
+  `mcp__sellable__get_source_scout_registry({})` before any scout dispatch.
+- `launch_source_scout`: Claude Code uses `Task` with `subagent_type` equal to
+  the registry `name`; Codex uses named custom agents such as
+  `source-scout-linkedin-engagement`, `source-scout-sales-nav`, and
+  `source-scout-prospeo-contact` when subagents are available.
+
+If a required interactive host function is missing, stop and explain the
+Sellable install/reload problem. Do not silently simulate structured choices,
+subprompt loading, or source-scout dispatch with local scripts.
+
 Never narrate local draft housekeeping to the user. If you create directories,
 save drafts, write artifacts, or persist intermediate state, translate it into
 the campaign benefit: consistent brief, approved lead source, reviewed message,

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

@@ -84,10 +84,15 @@ Validated draft directory:
   `[features].default_mode_request_user_input = true`, not available in
   `codex exec`). Treat them as equivalent approval/intake gates and persist the
   same draft artifacts after the user answers. Use this structured gate only for
-  multiple-choice decisions or approval gates. Never use it to collect open text
-  input like LinkedIn URLs, company domains, notes, pasted context, campaign
-  ideas, or feedback. For open text, ask in normal chat and wait for the user to
-  paste the value. If an interactive
+  single-choice decisions with fixed options or approval gates. Every campaign
+  setup gate must be single-choice in both hosts: set or assume
+  `multiSelect: false`, use mutually exclusive option labels, and do not ask
+  for checkbox or multi-select answers. If a blended answer is useful, present
+  the blend as one explicit option or route the user through `Other / custom`
+  and a free-text follow-up in chat. Never use it to collect open text input
+  like LinkedIn URLs, company domains, notes, pasted context, campaign ideas,
+  or feedback. For open text, ask in normal chat and wait for the user to paste
+  the value. If an interactive
   Codex session does not expose `request_user_input`, do not silently degrade to
   a plain chat question; stop and tell the user:
 
@@ -234,12 +239,30 @@ Validated draft directory:
 
   Sender options should include connected sender names if available, `same as
 me`, `I’ll paste a different sender profile`, and `Other / custom`.
-
-  After the user confirms the subject and sender, run one lightweight company
-  lookup if it has not already run, then ask the campaign setup questions. The
-  setup questions should use the confirmed company context so they do not feel
-  generic. If identity is still unavailable, use neutral/custom intake options
-  instead of guessed vertical-specific options.
+  When the answer can be represented as choices, ask it with the host-native
+  structured question gate. Do not render sender or campaign-focus choices as a
+  numbered plain-chat list in interactive Claude Code or Codex. Plain chat is
+  only for free-text values like a pasted LinkedIn URL, company domain, CSV
+  path, or custom explanation.
+
+  After the user confirms the subject and sender, check whether the company
+  context implies more than one campaignable product line, service, or offer.
+  If so, ask one structured campaign-focus question before the setup packet
+  (for example, "Which Sellable offer is this campaign for?") with no more than
+  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
+  `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.
 
 - Before the identity gate, use this customer-facing shape:
 
@@ -272,9 +295,10 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   draft-directory inspection/creation. `list_senders` is allowed once before the
   first identity gate as a quiet token/sender inference shortcut, and once means
   once: do not call it again after a LinkedIn lookup if it already ran. Do
-  draft-directory setup only after the founder answers. After launch identity is
-  confirmed, the setup packet must ask buyer, offer/CTA, proof, and lead source,
-  and all four questions must include an `Other / custom` option.
+  draft-directory setup only after the founder answers. After launch identity,
+  sender, and any ambiguous campaign focus are confirmed, the setup packet must
+  use the structured question gate and ask buyer, offer/CTA, proof, and lead
+  source. All four questions must include an `Other / custom` option.
 - After the founder answers the first strategy/source packet, explain the next
   stage only: campaign brief creation and brief approval. Use this shape:
 
@@ -432,11 +456,22 @@ should test for this campaign. Those can run in parallel and usually take
   message quality gate outputs between `message-validation.md` and
   `approval-packet.md`.
 - Run the dependency chain as a DAG: `create-campaign-brief` -> `find leads`;
-  once `lead-review.md` and `lead-sample.json` exist, run `filter leads` and
-  `message generation` from the same basis (`brief.md`, `lead-review.md`,
-  `lead-sample.json`). Approval waits for both `lead-filter.md` and
-  `message-validation.md`, then reconciles that the selected message basis rows
-  still pass the final filter.
+  once `lead-review.md` and `lead-sample.json` exist, the normal path is the
+  `post-lead-workstreams` step. Launch `filter leads` and `message generation`
+  from the same basis (`brief.md`, `lead-review.md`, `lead-sample.json`) as
+  separate workstreams when the host supports real subagents/background work.
+  In Claude Code, use two Task/Agent subagents in the same assistant message;
+  in Codex, use disjoint worker subagents when the host exposes them. The
+  existing `filter-rubric` and `message-generation` steps remain focused retry
+  and resume targets.
+- Message generation does not need `lead-filter.md` to start. The moment
+  `lead-sample.json` exists with at least 5 probable good-fit rows and the lead
+  source is confirmed or auto-confirmed, start the message-generation
+  workstream from `brief.md`, `lead-review.md`, and `lead-sample.json`. It can
+  prepare proof inventory, token strategy, and candidate angles while
+  filter-leads tightens keep/exclude rules. Approval still waits for both
+  `lead-filter.md` and `message-validation.md`, then reconciles that the
+  selected message basis rows still pass the final filter.
 - `lead-sample.json` from `find leads` is always the message sample source.
   `filter leads` must not create a different message sample or cause message
   generation to fetch new prospects. The filter only marks which find-leads
@@ -452,10 +487,10 @@ should test for this campaign. Those can run in parallel and usually take
   (display: LinkedIn Engagement Scout, powered by the `signal-discovery`
   provider prompt), `source-scout-sales-nav` (Sales Nav Scout), and
   `source-scout-prospeo-contact` (Prospeo Contact Scout). For Claude Code, explicitly
-  invoke the generated `.claude/agents/source-scout-*.md` Task/Agent subagents
-  for all credible lanes in one assistant message; they are installed from the
-  same canonical Sellable agent registry and carry explicit Sellable MCP tool
-  allowlists. The parent thread should not preload every provider prompt before
+  invoke the generated `source-scout-*` Task/Agent subagents installed by
+  `@sellable/install` for all credible lanes in one assistant message; they are
+  installed from the same canonical Sellable agent registry and carry explicit
+  Sellable MCP tool allowlists. The parent thread should not preload every provider prompt before
   spawning scouts; each scout loads only its own provider prompt. If host
   subagents are unavailable, use independent MCP/tool calls
   in the same model turn or dedicated Sellable MCP tools that perform
@@ -549,11 +584,19 @@ emphasis, tone, lead-source preference), always make it clear the user can give
 a custom answer. Add an explicit `Other / custom` option to each subjective
 question. Do not rely on prose like "you can add detail" as the only custom
 path. Do not add custom options to the final six-choice commit gate.
+Every subjective setup question is single-choice in both Claude Code and
+Codex. Use mutually exclusive options, set or assume `multiSelect: false`, and
+never use checkbox or multi-select wording that invites selecting several
+options. If a blended answer is likely, make the blend a single named option or
+route it through `Other / custom` and a normal-chat follow-up.
+Do not batch setup as a Claude Code multi-select wizard; buyer, offer/CTA,
+proof, and lead source remain single-choice questions even when the host
+displays them in a sequence.
 Use customer-facing question wording:
 
-- target prospects: `Who should be the target prospects for this campaign? Pick one or combine.`
-- main CTA / offer: `What should the main CTA or offer be? Pick one or combine.`
-- proof emphasis: `Which proof point would most increase this buyer's confidence in {{company}}? Multi-select fine.`
+- target prospects: `Who should be the target prospects for this campaign?`
+- main CTA / offer: `What should the main CTA or offer be?`
+- proof emphasis: `Which proof point would most increase this buyer's confidence in {{company}}?`
 - lead source: `How should we get the people for this campaign?`
 
 Ask the lead-source question as the last question in the first strategy

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

@@ -127,6 +127,35 @@
           "mustNotInferFromNameOnly": true,
           "fallback": "ask identity gate first; use neutral/custom intake options only when identity remains unavailable"
         },
+        {
+          "action": "confirm_ambiguous_campaign_focus_with_structured_gate",
+          "when": "after_identity_before_founder_strategy_source_packet",
+          "allowedTools": ["AskUserQuestion", "request_user_input"],
+          "questionType": "single-choice only; plain chat only for free-text custom detail",
+          "multiSelect": false,
+          "maxOptions": 4,
+          "requiredOption": "Other / custom",
+          "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",
+          "target": "research-sender",
+          "when": "after_identity_and_campaign_focus_before_founder_strategy_source_packet",
+          "allowedTools": [
+            "get_subskill_prompt",
+            "fetch_linkedin_profile",
+            "fetch_company",
+            "fetch_linkedin_posts",
+            "fetch_company_posts",
+            "WebFetch",
+            "WebSearch",
+            "ToolSearch",
+            "complete_sender_research"
+          ],
+          "requiredCompletion": "complete_sender_research",
+          "fallback": "If WebSearch is unavailable, use available MCP profile/company/post tools, call complete_sender_research with observed counts, and carry explicit proof gaps into the setup packet.",
+          "chatRenderRule": "Use researched company positioning and proof options in the buyer/offer/proof/source setup packet; do not ask generic strategy questions from company name alone."
+        },
         {
           "action": "render_post_intake_progress_preamble",
           "after": "founder_strategy_source_packet_answered",
@@ -194,6 +223,7 @@
           ],
           "forbiddenOptionLabelReason": "Provider/source mechanics are internal to the 'Find people for me' path; first-time users should choose the job they need done, not the scouting provider.",
           "customInput": true,
+          "multiSelect": false,
           "lastQuestionInFirstStrategyBatch": true
         }
       ],
@@ -518,10 +548,106 @@
         "auto_continue"
       ],
       "transitions": {
-        "lead_review_confirmed": "filter-rubric",
+        "lead_review_confirmed": "post-lead-workstreams",
+        "revise_leads": "find-leads",
+        "confirm_with_user": "post-lead-workstreams",
+        "auto_continue": "post-lead-workstreams"
+      },
+      "interruptOnly": true
+    },
+    {
+      "id": "post-lead-workstreams",
+      "label": "Post-lead filter and message workstreams",
+      "normalFlow": true,
+      "onEnter": [
+        {
+          "action": "launch_post_lead_workstreams",
+          "mode": "parallel_when_host_supports_subagents",
+          "branches": [
+            {
+              "name": "filter-leads",
+              "target": "filter-leads",
+              "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
+              "producesArtifacts": ["lead-filter.md"],
+              "optionalProducesArtifacts": ["rubric.json"],
+              "ownership": "lead quality, false-positive patterns, keep/exclude rules, and production rubric translation only"
+            },
+            {
+              "name": "message-generation",
+              "target": "generate-messages",
+              "mode": "DRY MODE",
+              "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
+              "producesArtifacts": ["message-validation.md"],
+              "optionalProducesArtifacts": [
+                "message-prep.md",
+                "message-candidate-drafts.md"
+              ],
+              "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only"
+            }
+          ],
+          "earlyMessageStartRule": "As soon as lead-sample.json exists with at least 5 probable good-fit rows and the lead source is confirmed or auto-confirmed, launch message-generation from brief.md, lead-review.md, and lead-sample.json. Do not wait for lead-filter.md to begin proof inventory, token planning, or candidate angles.",
+          "finalMessageReconcileRule": "message-validation.md may start before lead-filter.md exists, but before message-review it must cite only lead-sample.json rows that still pass lead-filter.md. If the selected winner depends on a row later excluded by lead-filter.md, revise message-generation before message review.",
+          "claudeRule": "In Claude Code, launch both workstreams with Task/Agent subagents in the same assistant message when Task is available. Do not run filter first and then message generation unless subagents/background work are unavailable.",
+          "codexRule": "In Codex, launch disjoint worker subagents for filter-leads and message-generation when the host exposes subagents for this run. If the host cannot spawn them, run the same branches sequentially and say so.",
+          "fallback": "If real parallel branches are unavailable, run filter-leads and then message-generation in the parent thread. Do not claim background or parallel work in that fallback."
+        },
+        {
+          "action": "wait_for_post_lead_artifacts",
+          "requiredArtifacts": ["lead-filter.md", "message-validation.md"],
+          "optionalArtifacts": [
+            "rubric.json",
+            "message-prep.md",
+            "message-candidate-drafts.md"
+          ],
+          "reconciliationRule": "Before entering message-review, verify lead-filter.md and message-validation.md both came from the same brief.md, lead-review.md, and lead-sample.json. lead-filter.md gates the sample rows; lead-sample.json remains the message sample source."
+        }
+      ],
+      "requiredArtifacts": ["brief.md", "lead-review.md", "lead-sample.json"],
+      "producesArtifacts": ["lead-filter.md", "message-validation.md"],
+      "optionalProducesArtifacts": [
+        "rubric.json",
+        "message-prep.md",
+        "message-candidate-drafts.md"
+      ],
+      "allowedTools": [
+        "get_subskill_prompt",
+        "get_subskill_asset",
+        "Task",
+        "spawn_agent",
+        "AskUserQuestion",
+        "request_user_input"
+      ],
+      "toolRules": [
+        "The post-lead workstreams are disjoint: filter-leads owns lead-filter.md/rubric.json; message-generation owns message-validation.md/message-prep.md/message-candidate-drafts.md.",
+        "message-generation can start before lead-filter.md, but message-review cannot start until both lead-filter.md and message-validation.md exist and reconcile against the same lead-sample.json.",
+        "Do not let filter-leads create a new message sample. Do not let message-generation fetch new prospects.",
+        "Before writing message-validation.md, message-generation must read 100% of the real generate-messages prompt via chunked get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) calls."
+      ],
+      "doNotAllow": [
+        "create_campaign",
+        "save_rubrics",
+        "import_leads",
+        "confirm_lead_list",
+        "update_campaign",
+        "queue_cells",
+        "start_campaign",
+        "check_rubric",
+        "generate_messages"
+      ],
+      "watchRequired": false,
+      "waitFor": [
+        "post_lead_workstreams_ready",
+        "revise_leads",
+        "revise_rubric",
+        "revise_messaging",
+        "confirm_with_user"
+      ],
+      "transitions": {
+        "post_lead_workstreams_ready": "message-review",
         "revise_leads": "find-leads",
-        "confirm_with_user": "filter-rubric",
-        "auto_continue": "filter-rubric"
+        "revise_rubric": "filter-rubric",
+        "revise_messaging": "message-generation",
+        "confirm_with_user": "message-review"
       },
       "interruptOnly": true
     },

package/skills/generate-messages/SKILL.md

@@ -66,8 +66,11 @@ Use this mode when the caller explicitly says `DRY MODE`, `Phase 84`,
 `create-campaign-v2`, or provides:
 
 - `brief.md`
-- `lead-filter.md`
 - `lead-sample.json`
+- `lead-filter.md` when available. In the create-campaign-v2
+  `post-lead-workstreams` step, message generation may start before
+  `lead-filter.md` exists so it can prepare proof inventory, token strategy,
+  and candidate angles while filter-leads runs.
 
 Required dry-mode contract:
 
@@ -78,12 +81,20 @@ Required dry-mode contract:
 - do not call `mcp__sellable__update_campaign_brief`
 - do not mutate DB-backed campaign state
 - do not fetch fresh web or LinkedIn research
-- use only `brief.md`, `lead-filter.md`, and `lead-sample.json`
+- use only `brief.md`, `lead-sample.json`, and `lead-filter.md` when present
 - treat `lead-sample.json` from find-leads as the message sample source; do not
   ask filter-leads for a new sample, create a new sample, or fetch additional
   prospects for dry-mode message generation
-- use `lead-filter.md` only to decide which find-leads sample rows remain valid
-  for the final winner and which false-positive patterns must be avoided
+- if `lead-filter.md` is not present yet, do the expensive early work only:
+  proof inventory, token rules, strategy map, candidate angle drafting, and
+  provisional sample fills. Prefer writing `message-prep.md` and
+  `message-candidate-drafts.md` while waiting for the filter branch.
+- use `lead-filter.md` once available to decide which find-leads sample rows
+  remain valid for the final winner and which false-positive patterns must be
+  avoided
+- do not mark `message-validation.md` as final or ready for message review until
+  `lead-filter.md` exists and the selected winner cites only rows that still
+  pass the filter
 - generate 2-3 sample messages inline
 - write findings to `message-validation.md`
 - start `message-validation.md` with `Mode: DRY MODE (no DB mutation)`
@@ -98,9 +109,11 @@ Dry mode validates message quality before campaign mint.
 Read:
 
 - `brief.md`
-- `lead-filter.md`
 - `lead-sample.json` from the find-leads step; this is the only allowed sample
   source for dry-mode message generation
+- `lead-filter.md` when present. If it is absent because the caller launched
+  post-lead workstreams in parallel, start the prep/candidate stages and then
+  reconcile before final `message-validation.md`.
 - `mcp/sellable/skills/create-campaign-brief/references/phase75-active-runtime-message-pack.md`
 - `mcp/sellable/skills/create-campaign-v2/references/validation-criteria.md`
 - `mcp/sellable/skills/create-campaign-v2/references/thomas-revision-filters.md`

package/skills/research/config.json

@@ -1,9 +0,0 @@
-{
-  "parallelMode": "wide",
-  "agentCount": 6,
-  "maxToolCallsPerAgent": 2,
-  "senderMaxAgents": 2,
-  "senderMaxToolCallsPerAgent": 3,
-  "progressMode": true,
-  "debugMode": true
-}