@sellable/mcp 0.1.205 → 0.1.207

package/README.md

@@ -277,19 +277,21 @@ Parallel execution contract:
   recommendation is reviewed. If filters are skipped, move to Messages/message
   review. Enrichment/filtering and Generate Message cells wait for message
   approval.
-- Claude host: use the installed `source-scout-linkedin-engagement`,
-  `source-scout-sales-nav`, and `source-scout-prospeo-contact` Task/Agent
-  subagents for parallel lead-source scouting only when the current session
-  exposes those agent names. Launch all credible lanes in one assistant message
-  so Claude Code can run them concurrently/background.
-- Codex host: use named custom scouts for source-angle work when subagents are
-  available: `source-scout-linkedin-engagement`, `source-scout-sales-nav`, and
-  `source-scout-prospeo-contact`. Use `multi_tool_use.parallel` for independent
-  tool-call batches when subagents are unavailable or the work is only simple
-  batched lookups.
-- For the post-lead stage, Codex/Claude should launch
-  `post-find-leads-filter-scout` and `post-find-leads-message-scout` in the
-  same turn/message when those subagents are available in the current session.
+- Claude host: after Find Buyers Plan approval, use the installed
+  `source-scout-linkedin-engagement`, `source-scout-sales-nav`, and
+  `source-scout-prospeo-contact` Task/Agent subagents as the normal source
+  path. Launch the approved single lane, or launch all credible lanes in one
+  assistant message when comparison/fallback is needed.
+- Codex host: after Find Buyers Plan approval, use the named custom scout for
+  the approved source lane when subagents are available:
+  `source-scout-linkedin-engagement`, `source-scout-sales-nav`, or
+  `source-scout-prospeo-contact`. Use a generic background agent when the named
+  scout is unavailable and the host can spawn one; parent-thread provider MCP
+  calls are the explicit fallback, not the default path.
+- For prospect setup, Codex/Claude should launch Prospect Filters
+  (`post-find-leads-filter-scout`) and Message Drafting
+  (`post-find-leads-message-scout`) in the same turn/message when those
+  subagents are available in the current session.
   If not, run them sequentially with MCP tools/assets, do not surface install
   status to the customer, and do not claim parallel work.
 - If neither backend is available, run sequentially with the same output schema.
@@ -345,12 +347,12 @@ with outcomes, and tracked people (LinkedIn profiles), all scoped by workspace.
 
 - Auth + active workspace: `~/.sellable/config.json` (or `SELLABLE_CONFIG_PATH`; old `$CODEX_HOME/sellable.json`, `~/.codex/sellable.json`, and `~/.claude/sellable.json` files remain compatibility fallbacks)
 - Engage memory (style guide + searches + tracked people): `sellable.engage.json` (or `SELLABLE_ENGAGE_MEMORY_PATH`)
-- Team-editable durable configs (home-level source of truth):
-  - `~/.sellable/configs/writing/styleguide.md`
-  - `~/.sellable/configs/audience/icp-filters.md`
-  - `~/.sellable/configs/proof/claims.md`
-  - `~/.sellable/configs/discovery/influencers.md`
-  - `~/.sellable/configs/discovery/post-filters.md`
+- Team-editable, project-local configs (recommended to edit in git):
+  - `./.sellable/configs/writing/styleguide.md`
+  - `./.sellable/configs/audience/icp-filters.md`
+  - `./.sellable/configs/proof/claims.md`
+  - `./.sellable/configs/discovery/influencers.md`
+  - `./.sellable/configs/discovery/post-filters.md`
 
 Files under `mcp/sellable/skills/**/core/*` are **package repo files**, not the intended user config surface.
 
@@ -363,7 +365,7 @@ Primary public entrypoint for the approval-gated campaign creation flow.
 ### interview
 
 Public identity/company memory interview. Builds durable core files under
-`~/.sellable/configs/core/**`, raw archives under `~/.sellable/interviews/**`,
+`./.sellable/configs/core/**`, raw archives under `./.sellable/interviews/**`,
 and reusable answer/proof/story/transcript/reference memory for downstream
 Sellable writing workflows.
 

package/agents/post-find-leads-filter-scout.md

@@ -1,6 +1,6 @@
-You are Lead Fit Builder for Sellable create-campaign-v2.
+You are Prospect Filters for Sellable create-campaign-v2.
 
-Your job starts only after the lead source has been approved or auto-confirmed,
+Your job starts only after the Start Import gate is approved or auto-confirmed,
 the confirmed source list has been copied into the campaign table, and the first
 campaign-table execution slice exists.
 Work only on the lead filter branch. Do not source new leads, draft messages,

package/agents/post-find-leads-message-scout.md

@@ -1,9 +1,16 @@
-You are Message Draft Builder for Sellable create-campaign-v2.
+You are Message Drafting for Sellable create-campaign-v2.
+
+Your job starts only after the Start Import gate is approved, the confirmed
+source list has been copied into the campaign table, the first campaign-table
+execution slice exists, and the parent has recorded the filter choice. Work only
+on the message-draft branch.
+
+This worker exists to keep the long `generate-messages` prompt, reference asset
+loading, token strategy, and skeptical copy review out of the parent campaign
+thread. The parent thread is only the orchestrator: it supplies campaign/table
+basis, receives the recommendation, persists the approved template after user
+approval, and handles Settings/launch.
 
-Your job starts only after the source is approved, the confirmed source list has
-been copied into the campaign table, the first campaign-table execution slice
-exists, and the parent has recorded the filter choice. Work only on the
-message-draft branch.
 Do not source leads, create lead filters, import leads, confirm lead lists, queue
 cells, attach sequences, start campaigns, ask the user questions, or mutate live
 campaign state. The main thread owns approval and campaign writes.
@@ -44,15 +51,9 @@ the branch input.
 2. Use that prompt as the drafting contract. Do not use any alternate prompt,
    examples-only shortcut, or create-campaign safety/checklist instructions as a
    substitute for the full message prompt.
-3. Follow the prompt's `Reference Asset Loading` section: load the required
-   pre-draft reference pack before drafting, load final-pass references before
-   approval, and report which assets were used and why. If those required
-   assets cannot be loaded, return `blocked` / `retry-needed`; do not draft from
-   the prompt alone. `ai-tells.md` is part of the required pack and is never
-   optional.
-4. Draft only from the campaign brief, selected source context, and initial
+3. Draft only from the campaign brief, selected source context, and initial
    campaign-table execution slice rows supplied by the parent.
-5. Keep the work provisional until the user chooses `Use Template` in Messages.
+4. Keep the work provisional until the user chooses `Use Template` in Messages.
 
 ## Owned Output
 
@@ -60,8 +61,6 @@ Return the following to the parent thread:
 
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
-- `Reference Asset Loading` note naming the required and conditional assets used
-  and why each was used
 - one rendered good-fill sample for a plausible passing campaign-table row
 - one omit/fallback sample when the row signal is not safe
 - pass/fail notes against the generate-messages quality gates
@@ -87,13 +86,13 @@ When reporting branch runtime proof, use this shape under
 - `basisToken` and `basis`
 - optional `messageDraftOutputRef`, `messageDraftOutput`, and `error`
 
-Do not tell the UI to show Message Draft Builder as running unless this proof
+Do not tell the UI to show Message Drafting as running unless this proof
 exists and points at the current non-empty campaign-table execution slice.
 
 ## Basis Changes And Rewrites
 
 The first completed recommendation is the default message review candidate.
-Do not automatically retry or regenerate only because Lead Fit Builder finished,
+Do not automatically retry or regenerate only because Prospect Filters finished,
 rubrics were saved, Filter Leads completed, enrichment cells populated, or more
 row data became available after this branch started.
 
@@ -111,6 +110,27 @@ brief hash, selected source, `selectedLeadListId`, `workflowTableId`, or
 execution-slice rows. Filter/rubric/enrichment basis drift alone is not a stale
 blocker.
 
+## User Revision Feedback
+
+If the parent sends user feedback about the template before `approve-message`,
+treat it as a Message Drafting revision, not a campaign write. Use the current
+`messageDraftRecommendation`, basis token/hash, campaign/table basis, and the
+latest user feedback as inputs. Load or reuse the full
+`generate-messages` contract, then return a revised recommendation with:
+
+- revised proposed template
+- what changed and why
+- token fill rule/fallback changes, if any
+- one rendered good-fill sample
+- pass/fail notes against the same quality gates
+- updated output timestamp/hash and basis token
+
+Keep the revision grounded in the same source/list/table rows unless the parent
+explicitly supplies a new selected list or review slice. Do not call
+`update_campaign_brief`, do not persist the template, and do not approve your
+own revision. The parent renders the revised template and waits for
+`approve-message`.
+
 ## Hard Rules
 
 - Do not call product Generate Message cells. This worker drafts the template
@@ -133,14 +153,10 @@ reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
 hope this is relevant`, `saw you in a few conversations about [topic], so
 may be off, but this seemed relevant`, `saw you might be interested in [topic],
 so hope this is relevant`, `hope this is relevant if [topic] is on your plate`,
-or `found you in a thread about [topic], so may be off, but this seemed relevant`.
-Only use `saw you raise your hand for [topic], so figured this was (hopefully)
-worth sending` when the source was an explicit lead-magnet comment, reply, or
-opt-in.
+or `saw you raise your hand for [topic], so figured this was (hopefully) worth sending`.
 The cheekier `saw you raise your hand for [topic] (creepy to reach out based
 on that, i know) - but this felt too on the nose to ignore` version is also
-allowed only for explicit lead-magnet comments, replies, or opt-ins and when the
-sender's voice can carry it. Bad: `you commented on...`, `you reacted
+allowed when the sender's voice can carry it. Bad: `you commented on...`, `you reacted
 to...`, `saw you engaging with...`, `your LinkedIn activity...`, `you might
 not remember the thread...`, or `found you through [source] and your role
 looked close...`. Otherwise omit the engagement signal and use role/company/problem context.

package/agents/registry.json

@@ -6,7 +6,7 @@
       "name": "source-scout-linkedin-engagement",
       "kind": "source-scout",
       "promptFile": "source-scout-linkedin-engagement.md",
-      "displayName": "LinkedIn Engagement Scout",
+      "displayName": "LinkedIn Source Discovery",
       "provider": "signal-discovery",
       "lane": "linkedin-engagement",
       "legacy": {
@@ -56,7 +56,7 @@
       "name": "source-scout-sales-nav",
       "kind": "source-scout",
       "promptFile": "source-scout-sales-nav.md",
-      "displayName": "Sales Nav Scout",
+      "displayName": "Sales Nav Source Discovery",
       "provider": "sales-nav",
       "lane": "sales-nav",
       "legacy": {
@@ -105,7 +105,7 @@
       "name": "source-scout-prospeo-contact",
       "kind": "source-scout",
       "promptFile": "source-scout-prospeo-contact.md",
-      "displayName": "Prospeo Contact Scout",
+      "displayName": "Prospeo Source Discovery",
       "provider": "prospeo",
       "lane": "prospeo-contact",
       "legacy": {
@@ -155,7 +155,7 @@
       "name": "post-find-leads-filter-scout",
       "kind": "post-find-leads-scout",
       "promptFile": "post-find-leads-filter-scout.md",
-      "displayName": "Lead Fit Builder",
+      "displayName": "Prospect Filters",
       "target": "filter-leads",
       "inputs": [
         "campaignId",
@@ -166,20 +166,20 @@
       ],
       "producesArtifacts": [],
       "optionalProducesArtifacts": [],
-      "ownership": "lead quality, false-positive patterns, keep/exclude rules, ability-to-pay checks, and production rubric translation only",
+      "ownership": "prospect-fit criteria, false-positive patterns, keep/exclude rules, ability-to-pay checks, and production rubric translation only",
       "codex": {
-        "description": "Lead Fit Builder for campaign-backed lead filtering and rubric persistence after review-batch import and filter approval.",
+        "description": "Prospect Filters worker for campaign-backed fit criteria and rubric persistence after review-batch import and filter approval.",
         "model": "gpt-5.5",
         "modelReasoningEffort": "high",
         "sandboxMode": "read-only",
         "nicknameCandidates": [
-          "Lead Fit Builder",
-          "Fit Builder",
+          "Prospect Filters",
+          "Fit Criteria",
           "Rubric Builder"
         ]
       },
       "claude": {
-        "description": "Use proactively as Lead Fit Builder after review-batch import and filter approval to persist campaign rubrics from campaign state.",
+        "description": "Use proactively as Prospect Filters after review-batch import and filter approval to persist campaign rubrics from campaign state.",
         "model": "inherit",
         "background": true,
         "maxTurns": 8,
@@ -196,8 +196,8 @@
       "name": "post-find-leads-message-scout",
       "kind": "post-find-leads-scout",
       "promptFile": "post-find-leads-message-scout.md",
-      "displayName": "Message Draft Builder",
-      "target": "generate-messages-compact",
+      "displayName": "Message Drafting",
+      "target": "generate-messages",
       "inputs": [
         "campaignId",
         "campaignBrief",
@@ -212,20 +212,20 @@
         "rendered sample"
       ],
       "optionalProducesArtifacts": [],
-      "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only",
+      "ownership": "message strategy, proof inventory, token rules, skeptical-prospect review, and selected winner only",
       "codex": {
-        "description": "Message Draft Builder for campaign-backed template proposals after confirm_lead_list imports a non-empty bounded review batch.",
+        "description": "Message Drafting worker for campaign-backed template proposals after confirm_lead_list imports a non-empty bounded review batch.",
         "model": "gpt-5.5",
-        "modelReasoningEffort": "high",
+        "modelReasoningEffort": "xhigh",
         "sandboxMode": "read-only",
         "nicknameCandidates": [
-          "Message Draft Builder",
-          "Draft Builder",
+          "Message Drafting",
+          "Draft Writer",
           "Template Builder"
         ]
       },
       "claude": {
-        "description": "Use proactively as Message Draft Builder after confirm_lead_list imports a non-empty bounded review batch; load generate-messages-compact and draft only from scoped campaign/tool state.",
+        "description": "Use proactively as Message Drafting after confirm_lead_list imports a non-empty bounded review batch; load generate-messages and draft only from scoped campaign/tool state.",
         "model": "inherit",
         "background": true,
         "maxTurns": 10,

package/agents/source-scout-linkedin-engagement.md

@@ -45,8 +45,8 @@ sales Claude`; do not treat broad anchor-only lanes like `Claude Code`, `MCP`,
 campaignOfferId, selectionMode: "replace", selections, headlineICPCriteria,
 scrapePlanMode: "all-selected", currentStep: "signal-discovery" })` before sampling so the watched Signal
    Discovery table shows the promoted posts and the exact posts being tested.
-   Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
-   visible transition after source approval.
+	   Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
+	   visible transition after Start Import approval.
 6. Fetch or sample engagers for promoted posts and score rough ICP fit from
    visible headline/display-name cues only. Do not enrich people during
    viability estimation.

package/agents/source-scout-prospeo-contact.md

@@ -12,8 +12,8 @@ campaignOfferId, confirmed: true })` and include that same `campaignOfferId`
   If no campaign ID is supplied, run campaignless preview mode. Treat post-mint
   searches with `campaignOfferId` as campaign-attached persisted search tabs;
   do not run a live campaign search without the campaign ID.
-  Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
-  visible transition after source approval.
+	  Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
+	  visible transition after Start Import approval.
 
 Use the inherited Sellable MCP tools when available:
 
@@ -57,7 +57,7 @@ Evidence standards:
   below 10% after reasonable refinement, recommend tightening the ICP/source
   direction rather than switching providers again.
 - Never recommend "import 25 leads" as the Prospeo source action. Recommend
-  exporting/materializing the approved source list; the parent thread later
+  Start Import for the approved source list; the parent thread later
   copies the confirmed source rows into the campaign and internally uses the
   first campaign-table execution slice for filter and message setup.
 - Treat Prospeo as an account/contact and company hiring-signal lane, not as proof of fresh LinkedIn intent.

package/agents/source-scout-sales-nav.md

@@ -12,8 +12,8 @@ campaignOfferId, confirmed: true })` and include that same `campaignOfferId` in
   route. If no campaign ID is supplied, run campaignless preview mode. Treat post-mint
   searches with `campaignOfferId` as campaign-attached persisted search tabs;
   do not run a live campaign search without the campaign ID.
-  Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
-  visible transition after source approval.
+	  Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
+	  visible transition after Start Import approval.
 
 Use the inherited Sellable MCP tools when available:
 
@@ -81,7 +81,7 @@ Evidence standards:
 - If projected good-fit after cleanup is below 10%, do not recommend Sales Nav
   as the winning source; recommend Prospeo as the next provider.
 - Never recommend "import 25 leads" as the Sales Nav source action. Recommend
-  exporting/materializing the approved source list; the parent thread later
+  Start Import for the approved source list; the parent thread later
   copies the confirmed source rows into the campaign and internally uses the
   first campaign-table execution slice for filter and message setup.
 - Do not hand-wave missing filter IDs.

package/dist/engage-memory.js

@@ -8,6 +8,11 @@ function resolveConfigsDir() {
     if (process.env.SELLABLE_CONFIGS_DIR) {
         candidates.push(path.resolve(process.env.SELLABLE_CONFIGS_DIR));
     }
+    // Same resolution strategy as skills.ts
+    if (process.argv[1]) {
+        candidates.push(path.resolve(path.dirname(process.argv[1]), "../../.sellable/configs"));
+    }
+    candidates.push(path.resolve(process.cwd(), ".sellable/configs"));
     candidates.push(path.resolve(os.homedir(), ".sellable/configs"));
     for (const candidate of candidates) {
         if (fs.existsSync(candidate)) {

package/dist/identity-memory.js

@@ -20,6 +20,10 @@ export function resolveIdentityConfigsDir() {
     if (process.env.SELLABLE_CONFIGS_DIR) {
         candidates.push(path.resolve(process.env.SELLABLE_CONFIGS_DIR));
     }
+    if (process.argv[1]) {
+        candidates.push(path.resolve(path.dirname(process.argv[1]), "../../.sellable/configs"));
+    }
+    candidates.push(path.resolve(process.cwd(), ".sellable/configs"));
     candidates.push(path.resolve(os.homedir(), ".sellable/configs"));
     for (const candidate of candidates) {
         if (fs.existsSync(candidate)) {

package/dist/tools/engage-memory.js

@@ -2,7 +2,7 @@ import { copySenderConfig, getEngageMemory, migrateFlatConfigs, recordProvenSear
 export const engageMemoryToolDefinitions = [
     {
         name: "get_engage_memory",
-        description: "Load backward-compatible engage memory from ~/.sellable/configs/: style guide, proven search keywords, tracked people, plus optional core identity/company memory. All data lives in readable markdown files the user can also edit directly. When senderId is provided, reads compatibility overrides from senders/{senderId}/ with flat-path fallback.",
+        description: "Load backward-compatible engage memory from .sellable/configs/: style guide, proven search keywords, tracked people, plus optional core identity/company memory. All data lives in readable markdown files the user can also edit directly. When senderId is provided, reads compatibility overrides from senders/{senderId}/ with flat-path fallback.",
         inputSchema: {
             type: "object",
             properties: {
@@ -17,7 +17,7 @@ export const engageMemoryToolDefinitions = [
     },
     {
         name: "set_engage_style_guide",
-        description: "Write the user's commenting style guide. When senderId is provided, writes to ~/.sellable/configs/senders/{senderId}/styleguide-core.md. Otherwise writes to ~/.sellable/configs/writing/styleguide-core.md.",
+        description: "Write the user's commenting style guide. When senderId is provided, writes to .sellable/configs/senders/{senderId}/styleguide-core.md. Otherwise writes to .sellable/configs/writing/styleguide-core.md.",
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/leads.js

@@ -1364,7 +1364,7 @@ export const leadToolDefinitions = [
                 },
                 limit: {
                     type: "number",
-                    description: "Max posts (default 25, max 50). Used for profile or company search.",
+                    description: "Max posts (default 25, max 50). Used for profile search.",
                 },
                 headlineICPCriteria: {
                     type: "array",
@@ -3087,7 +3087,7 @@ export async function confirmLeadList(input) {
         messageDraftBuilder: {
             firstAllowedStartPoint: "confirm_lead_list",
             startAllowed: true,
-            requiredBeforeRunningCopy: "Persist watchNarration.workerDetails.messageDraftBuilder with runId or fallbackId, statusSource, status, startedAt, updatedAt, and current basis before showing Message Draft Builder as In Progress.",
+            requiredBeforeRunningCopy: "Persist watchNarration.workerDetails.messageDraftBuilder with runId or fallbackId, statusSource, status, startedAt, updatedAt, and current basis before showing Message Drafting as In Progress.",
             requiredLiveInputs: {
                 campaignOfferId,
                 selectedLeadListId: resolvedLeadListId,
@@ -3133,10 +3133,10 @@ export async function confirmLeadList(input) {
             warning: partialSourceListWarning,
         },
         message: copyStillRunning
-            ? `${partialSourceListAccepted ? "Using the user-approved partial source snapshot. " : ""}First ${importedRowCount.toLocaleString("en-US")} source candidate${importedRowCount === 1 ? "" : "s"} are copied into the campaign table and the rest of the confirmed source list is still copying. Use the first ${keptReviewRowCount.toLocaleString("en-US")} as the review/process sample. The watched campaign is now on filter-choice; ask add filters vs skip filters before loading post-lead workers.`
+            ? `${partialSourceListAccepted ? "Using the user-approved partial source snapshot. " : ""}First ${importedRowCount.toLocaleString("en-US")} source candidate${importedRowCount === 1 ? "" : "s"} are copied into the campaign table and the rest of the confirmed source list is still copying. Use the first ${keptReviewRowCount.toLocaleString("en-US")} as the review/process sample. The watched campaign is now on filter-choice; ask add filters vs skip filters before loading prospect setup workers.`
             : importedRowCount > keptReviewRowCount
-                ? `${partialSourceListAccepted ? "Using the user-approved partial source snapshot. " : ""}Copied ${importedRowCount.toLocaleString("en-US")} source candidate${importedRowCount === 1 ? "" : "s"} into the campaign table. Use the first ${keptReviewRowCount.toLocaleString("en-US")} as the review/process sample. The watched campaign is now on filter-choice; ask add filters vs skip filters before loading post-lead workers.`
-                : `${partialSourceListAccepted ? "Using the user-approved partial source snapshot. " : ""}Copied ${importedRowCount.toLocaleString("en-US")} source candidate${importedRowCount === 1 ? "" : "s"} into the campaign table for the review/process sample. The watched campaign is now on filter-choice; ask add filters vs skip filters before loading post-lead workers.`,
+                ? `${partialSourceListAccepted ? "Using the user-approved partial source snapshot. " : ""}Copied ${importedRowCount.toLocaleString("en-US")} source candidate${importedRowCount === 1 ? "" : "s"} into the campaign table. Use the first ${keptReviewRowCount.toLocaleString("en-US")} as the review/process sample. The watched campaign is now on filter-choice; ask add filters vs skip filters before loading prospect setup workers.`
+                : `${partialSourceListAccepted ? "Using the user-approved partial source snapshot. " : ""}Copied ${importedRowCount.toLocaleString("en-US")} source candidate${importedRowCount === 1 ? "" : "s"} into the campaign table for the review/process sample. The watched campaign is now on filter-choice; ask add filters vs skip filters before loading prospect setup workers.`,
     };
 }
 export function getProviderPrompt(input) {
@@ -3176,9 +3176,7 @@ export async function selectPromisingPosts(input) {
     const { campaignOfferId, selections, headlineICPCriteria, selectionMode, mode, scrapePlanMode, targetEngagerCount, maxPostsToScrape, } = input;
     const effectiveMode = selectionMode ?? mode ?? "replace";
     const effectiveScrapePlanMode = scrapePlanMode ??
-        (targetEngagerCount || maxPostsToScrape
-            ? "capacity-target"
-            : "all-selected");
+        (targetEngagerCount || maxPostsToScrape ? "capacity-target" : "all-selected");
     if (selections.length > MAX_SIGNAL_DISCOVERY_POSTS) {
         return {
             success: false,
@@ -3250,9 +3248,7 @@ export async function selectPromisingPosts(input) {
         }
         const recommendation = buildSignalDiscoverySourceRecommendation({
             selectedPosts: Array.from(selectedByUrl.values()),
-            targetEngagerCount: effectiveScrapePlanMode === "capacity-target"
-                ? targetEngagerCount
-                : null,
+            targetEngagerCount: effectiveScrapePlanMode === "capacity-target" ? targetEngagerCount : null,
             maxPostsToScrape: effectiveScrapePlanMode === "capacity-target" ? maxPostsToScrape : null,
         });
         sourceRecommendation = recommendation.message;

package/dist/tools/prompts.js

@@ -157,7 +157,7 @@ export const promptToolDefinitions = [
     },
     {
         name: "get_post_find_leads_scout_registry",
-        description: "Return the canonical Sellable post-find-leads scout names for the two parallel workstreams unlocked after lead source approval: filter-leads and message generation.",
+        description: "Return canonical Sellable prospect-setup worker names for Prospect Filters and Message Drafting after Start Import copies confirmed source rows.",
         inputSchema: {
             type: "object",
             properties: {},
@@ -257,9 +257,9 @@ export function getSourceScoutRegistry() {
             legacy: agent.legacy,
         })),
         usage: {
-            codex: "Source finding is sequential by default. Launch multiple returned `name` values in one assistant turn only when the user asked for comparison, a prior lane failed, or the active flow marks the first lane borderline.",
-            claude: "Source finding is sequential by default. Invoke multiple Task/Agent subagents with subagent_type equal to returned `name` values only when comparison, fallback, or borderline-source conditions apply.",
-            parentThreadRule: "Named agents are optional acceleration. If they are absent, do not customer-surface install status; run the same provider probes with MCP tools from the parent thread. Default fallback order: Signal Discovery / LinkedIn engagement, then Sales Nav recent activity, then broader Sales Nav title search, then Prospeo account/contact search. Do not preload every provider prompt before spawning agents; each scout loads only the provider prompt for its lane.",
+            codex: "Source finding is agent-first after Find Buyers Plan approval. Launch the approved returned `name` as a Codex custom agent whenever the host exposes it; YOLO/autonomous mode counts as campaign-scoped permission. Launch multiple returned `name` values in one assistant turn only when comparing lanes, a prior lane failed, or the active flow marks the first lane borderline.",
+            claude: "Source finding is agent-first after Find Buyers Plan approval. Invoke the approved returned `name` with Task/Agent when the current Claude session lists it. Invoke multiple Task/Agent subagents with subagent_type equal to returned `name` values only when comparison, fallback, or borderline-source conditions apply.",
+            parentThreadRule: "Named source scouts are the normal path, not optional acceleration, after the Find Buyers Plan approval. If the approved named scout is absent or blocked, do not customer-surface install status; either spawn a generic gpt-5.5 high background agent with the same source-lane basis or continue inline only when the user explicitly approves parent-thread fallback. Default fallback order: Signal Discovery / LinkedIn engagement, then Sales Nav recent activity, then broader Sales Nav title search, then Prospeo account/contact search. Do not preload every provider prompt before spawning agents; each scout loads only the provider prompt for its lane.",
         },
     };
 }
@@ -330,7 +330,7 @@ export function getPostFindLeadsScoutRegistry() {
                 "basis.workflowTableId",
                 "basis.reviewSampleRowHash or basis.reviewSampleRowIds",
             ],
-            promptRequired: 'get_subskill_prompt({ subskillName: "generate-messages" }); the full generate-messages prompt is required for normal message drafting, then follow its Reference Asset Loading step and load the required pre-draft reference pack before drafting. ai-tells.md is required and never optional. If the required assets cannot be loaded, return blocked/retry-needed instead of drafting from the prompt alone.',
+            promptRequired: 'get_subskill_prompt({ subskillName: "generate-messages" }); the full generate-messages prompt and its Reference Asset Loading pack are required inside the Message Drafting branch for normal message drafting. If required assets cannot be loaded, return blocked/retry-needed instead of drafting from prompt memory.',
             basisFields: [
                 "campaign revision or updatedAt",
                 "brief hash",
@@ -343,9 +343,9 @@ export function getPostFindLeadsScoutRegistry() {
             messageDraftOutputFields: [
                 "templateRecommendation",
                 "tokenFillRules",
-                "referenceAssetLoading",
                 "renderedSample",
                 "concerns",
+                "revisionNotes when user feedback triggered a revision",
                 "status",
                 "basisStatus",
                 "basisToken",
@@ -353,12 +353,12 @@ export function getPostFindLeadsScoutRegistry() {
                 "outputHash",
                 "error or retry detail",
             ],
-            reusePolicy: "The first completed Message Draft Builder recommendation remains the default review candidate. Later Lead Fit Builder, Filter Leads, enrichment, or rubric completion may make an enriched rewrite available, but does not automatically retry or replace the initial draft unless campaign/brief/source/list/table/review-sample identity mismatches or the initial output failed.",
+            reusePolicy: "The first completed Message Drafting recommendation remains the default review candidate. Later Prospect Filters, Filter Leads, enrichment, or rubric completion may make an enriched rewrite available, but does not automatically retry or replace the initial draft unless campaign/brief/source/list/table/review-sample identity mismatches or the initial output failed. User copy feedback before approve-message is an explicit Message Drafting revision and must be routed back through the message branch with the current recommendation and basis.",
         },
         usage: {
-            codex: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn returned post-lead scout names before that question. Once the user answers, spawn Message Draft Builder from the same campaign/table basis. If the user chooses filters, also spawn Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
-            claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke returned post-lead Task/Agent names before that question. Once the user answers, invoke Message Draft Builder from the same campaign/table basis. If the user chooses filters, also invoke Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
-            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. If it is absent, do not customer-surface install status; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), must follow Reference Asset Loading and load the required pre-draft reference pack before drafting, must include ai-tells.md because it is never optional, must return blocked/retry-needed if required assets cannot be loaded, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not use any alternate or examples-only message prompt. On the filter path, keep the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads, show `Filters saved + waiting for message approval`, and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt ran for the current campaign/table execution slice. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.',
+            codex: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn returned prospect-setup worker names before that question. Once the user answers, spawn Message Drafting from the same campaign/table basis whenever Codex agent-launch policy is satisfied. Treat YOLO/autonomous mode as campaign-scoped permission to use Sellable background agents for pre-launch work. If the user has not enabled YOLO and has not explicitly asked for background agents/subagents/parallel agents/delegation/message bg agent in this campaign, ask once for permission before loading generate-messages in the parent. If permission is granted and the named custom agent is unavailable, spawn a generic gpt-5.5 xhigh background agent with the same campaign/table basis. If the user chooses filters, also spawn Prospect Filters when allowed, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
+            claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke returned prospect-setup Task/Agent names before that question. Once the user answers, invoke Message Drafting from the same campaign/table basis. If the user chooses filters, also invoke Prospect Filters, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
+            parentThreadRule: 'Message drafting is agent-first, not optional acceleration. If post-find-leads-message-scout is available, run that compatibility agent as background Message Drafting after the filter-choice answer. In Codex, YOLO/autonomous mode counts as campaign-scoped permission to use Sellable background agents for pre-launch work; if the user has not enabled YOLO and has not explicitly asked for background agents/subagents/parallel agents/delegation/message bg agent in this campaign, ask once for that permission before loading generate-messages in the parent. If permission is granted and the named custom agent is unavailable, spawn a generic gpt-5.5 xhigh background agent with the same campaign/table basis. Do not silently fall back to parent-thread message drafting. The parent may run the message branch inline only if the user explicitly says to continue without a background agent; when doing so, state that message generation is running inline. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load prospect-setup registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }) and its Reference Asset Loading pack inside the branch or explicitly approved inline fallback, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not use any alternate or examples-only message prompt. User copy feedback before approve-message must be routed back to Message Drafting with the current recommendation, basis token, campaign/table basis, and latest user text; the parent must not rewrite the template or call update_campaign_brief before approve-message. On the filter path, keep the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads, show `Filters saved + waiting for message approval`, and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt ran for the current campaign/table execution slice. Do not automatically rerun Message Drafting after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.',
         },
     };
 }

package/package.json

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