@sellable/mcp 0.1.152 → 0.1.153

package/dist/tools/leads.d.ts

@@ -2638,6 +2638,7 @@ export declare function confirmLeadList(input: ConfirmLeadListInput): Promise<{
         remainingCopyRowCount: number;
         copyStillRunning: boolean;
         trimmedOverflowRowCount: number;
+        sourceShortfall: boolean;
     };
     message: string;
 }>;

package/dist/tools/leads.js

@@ -2741,13 +2741,6 @@ export async function confirmLeadList(input) {
         leadListConfig.targetLeadCount > 0
         ? leadListConfig.targetLeadCount
         : null;
-    if (resolvedProvider === "signal-discovery" &&
-        signalSourceTargetLeadCount !== null &&
-        leadListConfig?.importStatus === "complete" &&
-        leadListRowCount > 0 &&
-        leadListRowCount < signalSourceTargetLeadCount) {
-        throw new Error(`Signal Discovery source list is under capacity: it completed with ${leadListRowCount.toLocaleString("en-US")} source candidates, below the approved ${signalSourceTargetLeadCount.toLocaleString("en-US")} source-candidate target. Do not confirm this source list. Select more posts, rerun Signal Discovery, or move to Sales Nav/Prospeo.`);
-    }
     const progressProcessed = typeof importProgress?.processed === "number"
         ? importProgress.processed
         : null;
@@ -2955,6 +2948,9 @@ export async function confirmLeadList(input) {
             remainingCopyRowCount: remainingRowCount,
             copyStillRunning,
             trimmedOverflowRowCount: 0,
+            sourceShortfall: signalSourceTargetLeadCount !== null &&
+                leadListRowCount > 0 &&
+                leadListRowCount < signalSourceTargetLeadCount,
         },
         message: copyStillRunning
             ? `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.`

package/dist/tools/readiness.d.ts

@@ -273,6 +273,7 @@ export declare function waitForLeadListReady(input: WaitForLeadListReadyInput):
     status?: undefined;
     targetLeadCount?: undefined;
     error?: undefined;
+    sourceShortfall?: undefined;
     warning?: undefined;
 } | {
     ready: boolean;
@@ -285,6 +286,7 @@ export declare function waitForLeadListReady(input: WaitForLeadListReadyInput):
     status: string;
     targetLeadCount: number | undefined;
     error?: undefined;
+    sourceShortfall?: undefined;
     warning?: undefined;
 } | {
     ready: boolean;
@@ -297,6 +299,7 @@ export declare function waitForLeadListReady(input: WaitForLeadListReadyInput):
     status: string | null;
     targetLeadCount: number | undefined;
     error: string;
+    sourceShortfall?: undefined;
     warning?: undefined;
 } | {
     ready: boolean;
@@ -309,6 +312,7 @@ export declare function waitForLeadListReady(input: WaitForLeadListReadyInput):
     status: string;
     targetLeadCount: number | undefined;
     error: string | null;
+    sourceShortfall?: undefined;
     warning?: undefined;
 } | {
     ready: boolean;
@@ -319,9 +323,10 @@ export declare function waitForLeadListReady(input: WaitForLeadListReadyInput):
     rowCount: number;
     status: string | null;
     targetLeadCount: number | null;
+    sourceShortfall: boolean;
+    warning: string | undefined;
     reason?: undefined;
     error?: undefined;
-    warning?: undefined;
 } | {
     ready: boolean;
     reason: string;
@@ -334,5 +339,6 @@ export declare function waitForLeadListReady(input: WaitForLeadListReadyInput):
     targetLeadCount: number | undefined;
     warning: string | undefined;
     error: string | undefined;
+    sourceShortfall?: undefined;
 }>;
 export {};

package/dist/tools/readiness.js

@@ -101,7 +101,7 @@ export const readinessToolDefinitions = [
                 },
                 targetLeadCount: {
                     type: "number",
-                    description: "Target number of leads requested. Used as a fallback completion check when status is unavailable. For Signal Discovery, pass the approved source-candidate target; if the completed source list lands below it, the tool returns source_under_capacity instead of ready.",
+                    description: "Target number of leads requested. Used as a fallback completion check when status is unavailable. For Signal Discovery, pass the approved source-candidate target; if the completed source list lands below it, the tool still returns ready with a source_shortfall warning so the confirmed list can be copied and the first review sample can proceed.",
                 },
                 timeoutMs: {
                     type: "number",
@@ -472,23 +472,12 @@ export async function waitForLeadListReady(input) {
                 }
             }
             if ((!requireRows || rowCount > 0) && importComplete) {
-                if (provider === "signal-discovery" &&
-                    typeof targetLeadCount === "number" &&
+                const signalSourceShortfallTarget = provider === "signal-discovery" && typeof targetLeadCount === "number"
+                    ? targetLeadCount
+                    : null;
+                const signalSourceShortfall = signalSourceShortfallTarget !== null &&
                     rowCount > 0 &&
-                    rowCount < targetLeadCount) {
-                    return {
-                        ready: false,
-                        reason: "source_under_capacity",
-                        leadListId,
-                        provider: provider ?? null,
-                        attempts,
-                        elapsedMs: Date.now() - start,
-                        rowCount,
-                        status: lastStatus,
-                        targetLeadCount,
-                        error: `Signal Discovery completed with ${rowCount.toLocaleString("en-US")} source candidates, below the approved ${targetLeadCount.toLocaleString("en-US")} source-candidate target. Do not confirm this lead list; select more posts, rerun source discovery, or move to Sales Nav/Prospeo.`,
-                    };
-                }
+                    rowCount < signalSourceShortfallTarget;
                 return {
                     ready: true,
                     leadListId,
@@ -498,6 +487,10 @@ export async function waitForLeadListReady(input) {
                     rowCount,
                     status: lastStatus,
                     targetLeadCount: targetLeadCount ?? null,
+                    sourceShortfall: signalSourceShortfall,
+                    warning: signalSourceShortfall
+                        ? `Signal Discovery completed with ${rowCount.toLocaleString("en-US")} source candidates, below the approved ${signalSourceShortfallTarget.toLocaleString("en-US")} source-candidate target. Confirm/copy the completed list for the first review sample, then add more approved posts or switch provider if the sample quality/scale is not enough.`
+                        : undefined,
                 };
             }
         }

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -192,8 +192,8 @@ should be a compact `## Source Recommendation` block with:
 - a selected-post table with post author/topic, why it fits, and visible
   engagement
 - total visible pool and estimated good-fit pool
-- first pass: build the source list, copy it into the campaign, then process
-  only the first 15 leads before scaling
+- first pass: build the source list, copy all confirmed source rows into the
+  campaign, then process only the first 15 rows before scaling
 - fallback: switch to Sales Nav recent activity if sampled/projected fit falls
   below 10%, or if the review batch is vendor-heavy, agency-heavy, or off-ICP
 

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

@@ -209,7 +209,7 @@ Use Signal Discovery first.
 **Working assumption:** ~20% of raw post engagers become good-fit prospects<br>
 **Engagers needed:** ~1,500 raw engagers<br>
 **Planning floor:** continue only when sampled/projected fit is at least 10% after cleanup; below that, switch to Sales Nav recent activity<br>
-**Review checkpoint:** after the source list exists, copy the confirmed source list into the campaign and process only the first 15 leads for fit and message review<br>
+**Review checkpoint:** after the source list exists, copy the entire confirmed source list into the campaign and process only the first 15 rows for fit and message review<br>
 
 ### Selected posts
 
@@ -230,8 +230,9 @@ This gives enough volume to target ~300 good-fit prospects after cleanup, while
 keeping the source tied to people already engaging with Claude Code outbound /
 AI-native sales workflows.
 
-**First pass:** build the source list, copy it into the campaign, then process
-only the first 15 leads so we can inspect quality before scaling.
+**First pass:** build the source list, copy all confirmed source rows into the
+campaign, then process only the first 15 rows so we can inspect quality before
+scaling.
 
 **Fallback:** if sampled/projected fit falls below 10%, or if the review batch
 is too vendor-heavy, agency-heavy, or off-ICP, switch to Sales Nav recent

package/skills/create-campaign-v2/references/step-13-import-leads.md

@@ -130,13 +130,23 @@ raw engagers. If the sampled fit rate is stronger or weaker, use the sampled
 rate with a conservative cleanup factor, cap the source candidates at the
 approved provider limit, and select only enough posts to reach that engager
 count. The planning floor is 10% projected fit after cleanup; if Signal
-Discovery falls below that floor, do not import the source list. Route back to
-find-leads and move to Sales Nav recent activity instead. After the scrape,
-`wait_for_lead_list_ready` must clear the approved source-candidate target; if
-it reports `source_under_capacity`, do not call `confirm_lead_list`. The
-subsequent `confirm_lead_list` call uses `reviewBatchLimit: 15`. It copies the
-confirmed source rows into the campaign table and returns only the first 15 rows
-as the review/process sample.
+Discovery falls below that floor during the pre-scrape sample, revise the source
+plan before importing. After an approved scrape starts, do not discard a nonempty
+completed source list just because it lands below the source-candidate target:
+confirm/copy the completed list for the first review sample, then add more posts
+or switch provider if the sample quality or scale is not enough. The subsequent
+`confirm_lead_list` call uses `reviewBatchLimit: 15`. It copies the confirmed
+source rows into the campaign table and returns only the first 15 rows as the
+review/process sample.
+
+Harvest-specific interpretation: Signal Discovery post comments and reactions
+are paged from Harvest at about 100 records per page, with production caps of
+1,500 reactions and 300 comments per selected post. The source list stores
+headline-passing candidates after that scrape. Therefore `71 source rows` means
+71 candidates passed headline/list filtering and were inserted; it does not
+mean the post scrape stopped after 71 raw engagers. Treat raw visible engagement,
+raw fetched pages, inserted source rows, and the 15-row review/process sample as
+separate numbers.
 
 For supplied direct lists, `confirm_lead_list` should receive
 `reviewBatchLimit: 15` so the campaign table can hold the confirmed list while

package/skills/providers/signal-discovery.md

@@ -24,12 +24,34 @@ When the user asks to find posts or start searching, **IMMEDIATELY begin Round 1
 
 <lead_target>
 
-- **Default: provider max import count** (use this unless user specifies otherwise; see `lead-import-limits.json`, currently 2,500)
-- **Maximum: provider max import count**
+- **Default create-campaign target: ~300 good-fit prospects after cleanup,
+  enrichment, and fit filtering.**
+- **Working assumption when no stronger sample exists: ~20% of raw post
+  engagers become good-fit prospects, so plan around ~1,500 raw engagers.**
+- Provider/import caps are internal execution limits, not customer-facing
+  promises. Do not tell the user the internal provider cap.
 - Quality > Quantity: a few hundred active users > 1000 potentially inactive profiles
 - Focus on ACTIVE platform users who will actually see and respond to outreach
   </lead_target>
 
+<harvest_scrape_contract>
+
+Production Signal Discovery uses Harvest for post comments and reactions.
+Harvest returns about 100 comments or reactions per page. The source scrape
+pages through Harvest up to the configured per-post caps, currently 1,500
+reactions and 300 comments per selected post.
+
+Important interpretation rule: a source list row count is the number of
+headline-passing candidates inserted after scraping and filtering, not the raw
+number of engagers fetched. If a selected post has 1,200 visible engagers and
+the source list lands at 71 rows, read that as 71 headline-passing inserted
+rows, not as "only 71 engagers were scraped." Do not reject a completed
+non-empty source list solely because inserted rows are below the raw engager
+target; confirm/copy it for the 15-row review sample, then decide whether to add
+more posts or switch lanes based on sample quality and scale.
+
+</harvest_scrape_contract>
+
 <multi_round_search>
 
 ## Multi-Round Search Strategy
@@ -98,12 +120,12 @@ You must estimate:
   - expected good-fit prospects per right-content post after dedupe/cleanup
 - `postsNeededForTarget`
   - number of right-content posts needed to reach the target good-fit lead
-    count, defaulting to 150 for Signal Discovery unless the campaign says
+    count, defaulting to 300 for Signal Discovery unless the campaign says
     otherwise
 - `requiredEngagersToScrape`
-  - `ceil(targetGoodFitLeads / sampledFitRate)`; for example 15 good-fit
-    prospects per 100 engagers means a 150-good-fit source target needs about
-    1,000 engagers scraped
+  - `ceil(targetGoodFitLeads / sampledFitRate)`; for example the default
+    planning assumption of 20 good-fit prospects per 100 engagers means a
+    300-good-fit source target needs about 1,500 raw engagers scraped
 - `planningFloor`
   - minimum acceptable sampled/projected fit rate after conservative cleanup;
     default 10%. Below this, do not scale Signal Discovery.
@@ -119,8 +141,8 @@ Use conservative logic:
      those posts in the watched Signal Discovery UI before sampling engagers
    - call `fetch_post_engagers`
    - fetch only a representative first sample, not a full scrape
-   - default to `limit: 25` for one post or `limit: 20` per post when checking two posts
-   - inspect roughly 25-40 engagers total
+   - default to a fast first sample of roughly 15 people for one post; when
+     comparing multiple posts, inspect roughly 15-40 people total
    - score them against `headlineICPCriteria` or a rough yes/no headline rubric
    - use headline and display-name cues only for this spot check; do not enrich people during viability estimation
    - use that sampled pass rate to extrapolate conservatively
@@ -130,7 +152,7 @@ Use conservative logic:
    - stale posts
    - adjacent communities that are not actual buyers
 4. Explain the pass-through briefly and explicitly:
-   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `goodFitPer100Engagers`: ~22 before cleanup / ~13-16 after cleanup, `requiredEngagersToScrape`: ~940-1,150 for a 150-good-fit target after cleanup, `avgReachableEngagersPerPost`: 240, `goodFitProspectsPerPost`: ~31-38, `postsNeededForTarget`: ~4-5, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `projectedRange`: 150-190 from selected posts"
+   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `goodFitPer100Engagers`: ~22 before cleanup / ~13-16 after cleanup, `requiredEngagersToScrape`: ~1,875-2,300 for a 300-good-fit target after cleanup, `avgReachableEngagersPerPost`: 240, `goodFitProspectsPerPost`: ~31-38, `postsNeededForTarget`: ~8-10, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `projectedRange`: 300-380 from selected posts"
    - fallback: "I could not fetch engagers, so this is inferred from post and author quality only"
 5. If the evidence is too weak, say so and return a low-confidence estimate instead of pretending precision.
 6. If sampled/projected fit after cleanup is below the 10% planning floor,
@@ -385,7 +407,7 @@ For `create-campaign-v2` source approval, do not treat the default
 `selectionTarget` of 3 posts as enough by itself. Before the final source
 recommendation, estimate source capacity from real sample math:
 
-- source target good-fit leads (default 150 for Signal Discovery unless the
+- source target good-fit leads (default 300 for Signal Discovery unless the
   campaign says otherwise)
 - eligible right-content posts by lane/content type
 - reachable engagers from those posts
@@ -461,8 +483,10 @@ source-capacity plan without asking for another yes/no gate. Then
 the campaign table and returns the first 15 review/process rows. Do not confuse
 the source-candidate target with the review sample size.
 If the completed source scrape comes back below the approved source-candidate
-target, do not call `confirm_lead_list`; select more posts, rerun source
-discovery, or move to Sales Nav.
+target but has usable rows, still call `confirm_lead_list` so the completed
+source list is copied into the campaign and the first 15 rows can be reviewed.
+Treat the shortfall as a scale warning: add more approved posts or move to Sales
+Nav only after the first sample proves the lane is too thin or off-ICP.
 
 The promotion/select step is required campaign state. Use post IDs from the
 current campaign-scoped search result, not stale IDs copied from a source review