@sellable/mcp 0.1.123 → 0.1.125

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

@@ -47,11 +47,13 @@ currentStep: "signal-discovery" })` before sampling so the watched Signal
 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.
-7. Compute capacity before recommending the source: target good-fit leads
-   (default 500 unless the parent supplies a target), reachable engagers,
+7. Compute capacity before recommending the source: source target good-fit
+   leads (default 300 unless the parent supplies a target), reachable engagers,
    sampled ICP-fit rate as `n/N` plus an easy percentage/range, expected usable
-   leads per right-content post after dedupe/cleanup, and posts needed to hit
-   the target.
+   leads per 100 engagers before and after a conservative dedupe/cleanup
+   factor, required engagers to scrape (`source target / fit rate`), average
+   reachable engagers per right-content post, expected usable leads per
+   right-content post after dedupe/cleanup, and posts needed to hit the target.
 8. Select/promote enough right-content posts to plausibly hit the target. If the
    warm Signals pool is useful but too small, return the expected warm range and
    recommend Sales Nav/Prospeo for scale instead of padding with noisy posts.
@@ -64,9 +66,12 @@ Return a concise structured result with:
 - `keyword_lanes` with timeframe, raw posts found, finalist posts reviewed
 - `selected_posts` with URL/title, author/topic, age, engager count, sampled engagers, good fits as n/N, estimated usable prospects per post, use/discard
 - `sample_leads`, if any
-- `approval_math` with eligible posts, target good-fit leads, sampled engagers,
-  ICP-fit rate as `n/N` plus percentage/range, posts needed for target, selected
-  post count, expected usable lead range, and scale fallback
+- `approval_math` with eligible posts, source target good-fit leads, sampled
+  engagers, ICP-fit rate as `n/N` plus percentage/range, good-fit prospects per
+  100 engagers, required engagers to scrape, average reachable engagers per
+  post, expected usable prospects per post after cleanup, posts needed for
+  target, selected post count, review-batch import limit, expected usable lead
+  range, and scale fallback
 - `estimated_good_fit_range`
 - `message_context_strength`, directional and source-specific
 - `false_positive_patterns`
@@ -82,7 +87,11 @@ Evidence standards:
   GTM/outbound/buyer pain, workflow, or role context that makes the campaign
   relevant.
 - Do not make the user infer capacity. Say, plainly, how many eligible posts
-  exist, what percent of sampled engagers looked in-ICP, how many posts are
-  needed for 500+ good-fit leads, and which posts you would use.
+  exist, how many sampled engagers looked in-ICP, how many good-fit prospects
+  that implies per 100 engagers, how many usable prospects one right-content
+  post should yield after cleanup, how many engagers must be scraped for the
+  300-good-fit source target, how many posts are needed for that source target,
+  and which posts you would use. Also say the first campaign import remains the
+  bounded 15-row review batch.
 - If `fetch_post_engagers` is unavailable or fails, report that explicitly and mark the estimate lower-confidence.
 - Keep LinkedIn Engagement viable when selected posts can produce roughly 150+ ICP-fit warm prospects before final filtering, even if Sales Nav is more scalable.

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

@@ -26,8 +26,16 @@ Process:
 2. Preserve target role names with `CURRENT_TITLE` lookups; do not rely on seniority alone when the brief names concrete roles.
 3. When `lookup_sales_nav_filter` returns multiple title options, choose the closest semantic title match instead of the first result.
 4. Build a broad-but-reasonable baseline from role/title, geography, company size, industry/account context, and recent LinkedIn activity when relevant.
-5. Run the baseline plus 1-2 refinements if the first pass is noisy or under-scaled.
-6. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
+5. Check scale against the source target good-fit lead count (default 300
+   unless the parent supplies a target). If raw preview volume or projected usable volume
+   is below target, do not present the tiny result as the scale fallback yet.
+   Loosen nonessential filters in order: remove recent-activity first, widen
+   adjacent title variants, widen geography/company-size constraints, and only
+   keep hard ICP requirements from the brief.
+6. Run the baseline plus 1-2 refinements or loosening passes if the first pass
+   is noisy or under-scaled. Label the final pool as constrained if it still
+   cannot plausibly reach the target after loosening.
+7. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
 
 Return a concise structured result with:
 
@@ -36,6 +44,11 @@ Return a concise structured result with:
 - `exact_filter_recipe`
 - `lookup_ids_used`
 - `raw_result_count`
+- `scale_check` with source target good-fit lead count, preview/raw volume, sampled
+  good fits as n/N, projected usable count, and whether the pool can reach the
+  target
+- `loosening_attempts` with what was removed or widened when the pool was too
+  tight
 - `sampled_people` and good fits as n/N
 - `estimated_good_fit_range_after_cleanup`
 - `expected_acceptance_rate_range`, directional if inferred
@@ -49,5 +62,9 @@ Evidence standards:
 
 - Optimize for a useful prospect pool, not max volume at any cost.
 - Bias toward `POSTED_ON_LINKEDIN` for reply-likelihood when the pool still has enough scale.
+- Do not over-tighten fallback filters into a pool that cannot be meaningfully
+  larger than the warm-post path. If Sales Nav is offered for scale, it should
+  either project to the target good-fit count or clearly say it is too tight and
+  name the next broadening/Prospeo option.
 - Do not hand-wave missing filter IDs.
 - If Sales Nav returns a giant unfiltered pool, discard that result and retry with valid filters before recommending it.

package/dist/tools/leads.d.ts

@@ -1,4 +1,16 @@
 export declare function normalizeTargetLeadCount(targetLeadCount: unknown, maxImportCount: number): number | undefined;
+type SignalPostForImportSelection = {
+    likes: number;
+    comments: number;
+};
+export declare function selectSignalPostsForImport<T extends SignalPostForImportSelection>(posts: T[], options: {
+    targetEngagerCount?: number;
+    maxPostsToScrape?: number;
+}): {
+    posts: T[];
+    estimatedEngagers: number;
+    limited: boolean;
+};
 export type GetProviderPromptInput = {
     provider: "apollo" | "sales-nav" | "prospeo" | "signal-discovery";
     campaignOfferId?: string;
@@ -112,6 +124,8 @@ export type ImportLeadsInput = {
     searchName?: string;
     leadListName?: string;
     headlineICPCriteria?: string[];
+    targetEngagerCount?: number;
+    maxPostsToScrape?: number;
     rubricGuidelines?: string[];
 };
 type ImportLeadProvider = NonNullable<ImportLeadsInput["provider"]>;
@@ -213,6 +227,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -386,6 +402,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -458,6 +476,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -602,6 +622,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -688,6 +710,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -783,6 +807,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -860,6 +886,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -1475,6 +1503,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -1604,6 +1634,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -1666,6 +1698,14 @@ export declare const leadToolDefinitions: ({
                 minItems?: undefined;
                 maxItems?: undefined;
             };
+            targetEngagerCount: {
+                type: string;
+                description: string;
+            };
+            maxPostsToScrape: {
+                type: string;
+                description: string;
+            };
             rubricGuidelines: {
                 type: string;
                 items: {
@@ -1791,6 +1831,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
             jobId?: undefined;
@@ -1882,6 +1924,8 @@ export declare const leadToolDefinitions: ({
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             selections?: undefined;
             selectionMode?: undefined;
@@ -1983,6 +2027,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -2060,6 +2106,8 @@ export declare const leadToolDefinitions: ({
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
             mode?: undefined;
+            targetEngagerCount?: undefined;
+            maxPostsToScrape?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -2318,6 +2366,8 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
             searchName?: string;
             leadListName?: string;
             headlineICPCriteria?: string[];
+            targetEngagerCount?: number;
+            maxPostsToScrape?: number;
             rubricGuidelines?: string[];
         };
     }[];
@@ -2328,6 +2378,10 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     jobId?: undefined;
     estimatedEngagers?: undefined;
     selectedPostCount?: undefined;
+    availableSelectedPostCount?: undefined;
+    targetEngagerCount?: undefined;
+    maxPostsToScrape?: undefined;
+    limitedSelectedPosts?: undefined;
     targetLeadCount?: undefined;
     existingCount?: undefined;
     createdLeadList?: undefined;
@@ -2353,6 +2407,8 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
             searchName?: string;
             leadListName?: string;
             headlineICPCriteria?: string[];
+            targetEngagerCount?: number;
+            maxPostsToScrape?: number;
             rubricGuidelines?: string[];
         };
     }[];
@@ -2360,6 +2416,10 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     jobId?: undefined;
     estimatedEngagers?: undefined;
     selectedPostCount?: undefined;
+    availableSelectedPostCount?: undefined;
+    targetEngagerCount?: undefined;
+    maxPostsToScrape?: undefined;
+    limitedSelectedPosts?: undefined;
     targetLeadCount?: undefined;
     existingCount?: undefined;
     createdLeadList?: undefined;
@@ -2370,6 +2430,10 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     jobId: string;
     estimatedEngagers: number;
     selectedPostCount: number;
+    availableSelectedPostCount: number;
+    targetEngagerCount: number | null;
+    maxPostsToScrape: number | null;
+    limitedSelectedPosts: boolean;
     targetLeadCount: number | null;
     message: string;
     error?: undefined;
@@ -2402,6 +2466,8 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
             searchName?: string;
             leadListName?: string;
             headlineICPCriteria?: string[];
+            targetEngagerCount?: number;
+            maxPostsToScrape?: number;
             rubricGuidelines?: string[];
         };
     }[];
@@ -2409,6 +2475,10 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     jobId?: undefined;
     estimatedEngagers?: undefined;
     selectedPostCount?: undefined;
+    availableSelectedPostCount?: undefined;
+    targetEngagerCount?: undefined;
+    maxPostsToScrape?: undefined;
+    limitedSelectedPosts?: undefined;
     targetLeadCount?: undefined;
     createdLeadList?: undefined;
     jobResult?: undefined;
@@ -2427,6 +2497,10 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     modeOptions?: undefined;
     estimatedEngagers?: undefined;
     selectedPostCount?: undefined;
+    availableSelectedPostCount?: undefined;
+    targetEngagerCount?: undefined;
+    maxPostsToScrape?: undefined;
+    limitedSelectedPosts?: undefined;
     existingCount?: undefined;
 }>;
 export declare function cancelLeadImport(input: CancelLeadImportInput): Promise<{

package/dist/tools/leads.js

@@ -265,6 +265,46 @@ export function normalizeTargetLeadCount(targetLeadCount, maxImportCount) {
     }
     return Math.min(numeric, maxImportCount);
 }
+function normalizePositiveInteger(value) {
+    if (value === null || value === undefined) {
+        return undefined;
+    }
+    const numeric = typeof value === "number" ? value : Number(value);
+    if (!Number.isFinite(numeric) || numeric <= 0) {
+        return undefined;
+    }
+    return Math.floor(numeric);
+}
+export function selectSignalPostsForImport(posts, options) {
+    const normalizedTargetEngagers = normalizePositiveInteger(options.targetEngagerCount);
+    const normalizedMaxPosts = normalizePositiveInteger(options.maxPostsToScrape);
+    if (!normalizedTargetEngagers && !normalizedMaxPosts) {
+        return {
+            posts,
+            estimatedEngagers: posts.reduce((sum, post) => sum + post.likes + post.comments, 0),
+            limited: false,
+        };
+    }
+    const ranked = [...posts].sort((a, b) => b.likes + b.comments - (a.likes + a.comments));
+    const selected = [];
+    let estimatedEngagers = 0;
+    for (const post of ranked) {
+        if (normalizedMaxPosts && selected.length >= normalizedMaxPosts) {
+            break;
+        }
+        selected.push(post);
+        estimatedEngagers += post.likes + post.comments;
+        if (normalizedTargetEngagers &&
+            estimatedEngagers >= normalizedTargetEngagers) {
+            break;
+        }
+    }
+    return {
+        posts: selected.length > 0 ? selected : ranked,
+        estimatedEngagers,
+        limited: selected.length > 0 && selected.length < posts.length,
+    };
+}
 function toDate(value) {
     if (!value)
         return null;
@@ -967,6 +1007,14 @@ export const leadToolDefinitions = [
                     items: { type: "string" },
                     description: "Signal Discovery: headline ICP criteria (3-5 rules). Uses campaign.headlineICPCriteria if not provided.",
                 },
+                targetEngagerCount: {
+                    type: "number",
+                    description: "Signal Discovery: target number of post engagers to scrape. Compute from source target good-fit leads / sampled fit rate; e.g. 300 good fits at 20% fit requires about 1500 engagers. Limits selected posts before starting scrape.",
+                },
+                maxPostsToScrape: {
+                    type: "number",
+                    description: "Signal Discovery: optional hard cap on selected posts to scrape after ranking selected posts by engagement.",
+                },
                 rubricGuidelines: {
                     type: "array",
                     items: { type: "string" },
@@ -1845,7 +1893,7 @@ export async function searchSignals(input) {
 }
 export async function importLeads(input) {
     const api = getApi();
-    const { campaignOfferId, currentStep, sourceLeadListId: inputSourceLeadListId, searchId, targetLeadCount, mode, searchName, leadListName, headlineICPCriteria, rubricGuidelines, confirmed, } = input;
+    const { campaignOfferId, currentStep, sourceLeadListId: inputSourceLeadListId, searchId, targetLeadCount, mode, searchName, leadListName, headlineICPCriteria, targetEngagerCount, maxPostsToScrape, rubricGuidelines, confirmed, } = input;
     assertInteractionApproval({
         campaignId: campaignOfferId,
         action: "import-leads",
@@ -1989,12 +2037,17 @@ export async function importLeads(input) {
             }
         }
         const uniqueSelectedPosts = Array.from(uniqueByUrl.values());
+        const importSelection = selectSignalPostsForImport(uniqueSelectedPosts, {
+            targetEngagerCount,
+            maxPostsToScrape,
+        });
+        const postsToScrape = importSelection.posts;
         const effectiveHeadlineICPCriteria = headlineICPCriteria && headlineICPCriteria.length > 0
             ? headlineICPCriteria
             : rubricGuidelines;
         // Start the scrape job
         const result = await api.post(`/api/v3/campaigns/${campaignOfferId}/signal-leads/create`, {
-            posts: uniqueSelectedPosts,
+            posts: postsToScrape,
             ...(effectiveHeadlineICPCriteria &&
                 effectiveHeadlineICPCriteria.length > 0
                 ? {
@@ -2014,9 +2067,15 @@ export async function importLeads(input) {
             leadListId: result.tableId,
             jobId: result.jobId,
             estimatedEngagers: result.estimatedEngagers,
-            selectedPostCount: uniqueSelectedPosts.length,
+            selectedPostCount: postsToScrape.length,
+            availableSelectedPostCount: uniqueSelectedPosts.length,
+            targetEngagerCount: normalizePositiveInteger(targetEngagerCount) ?? null,
+            maxPostsToScrape: normalizePositiveInteger(maxPostsToScrape) ?? null,
+            limitedSelectedPosts: importSelection.limited,
             targetLeadCount: cappedTargetLeadCount ?? null,
-            message: `Started scraping ${uniqueSelectedPosts.length} posts (~${result.estimatedEngagers} engagers). Leads will appear as scraping completes.`,
+            message: `Started scraping ${postsToScrape.length} posts (~${result.estimatedEngagers} engagers). Leads will appear as scraping completes.${importSelection.limited
+                ? ` Limited from ${uniqueSelectedPosts.length} selected posts by the approved source-capacity scrape plan.`
+                : ""}`,
         };
     }
     // === SALES NAV / PROSPEO FLOW ===
@@ -2449,7 +2508,7 @@ export async function selectPromisingPosts(input) {
         selectedCount: selectionResult.selectedCount,
         unselectedCount: selectionResult.unselectedCount,
         criteriaCount: selectionResult.criteriaCount,
-        message: `Selected ${selectionResult.selectedCount} posts with ${selectionResult.criteriaCount} ICP criteria (persisted). Criteria are already saved to the campaign. If the user has already approved the lead-source decision for create-campaign-v2, call import_leads with provider: "signal-discovery", confirmed: true, and the approved bounded targetLeadCount. Otherwise ask the user to confirm before importing.`,
+        message: `Selected ${selectionResult.selectedCount} posts with ${selectionResult.criteriaCount} ICP criteria (persisted). Criteria are already saved to the campaign. If the user has already approved the lead-source decision for create-campaign-v2, call import_leads with provider: "signal-discovery", confirmed: true, the approved source-capacity targetLeadCount, and targetEngagerCount/postsNeeded from the approval math. Otherwise ask the user to confirm before importing.`,
     };
 }
 export async function setHeadlineICPCriteria(input) {

package/package.json

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

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

@@ -826,7 +826,9 @@ Required behavior:
   2. If Signals does not have enough recent, relevant, ICP-looking engagers,
      switch to Sales Nav with recent activity when the target can be expressed
      as title/persona/company filters. Run preview filters, inspect preview rows,
-     validate the filters applied, and estimate scalable-fit volume.
+     validate the filters applied, and estimate scalable-fit volume. If the
+     preview/projected usable pool is below the target good-fit count, loosen
+     nonessential filters before presenting Sales Nav as the scale fallback.
   3. If recent-activity Sales Nav is too small or noisy, broaden to normal Sales
      Nav title + company filters and call out the weaker activity context.
   4. Use Prospeo Contact only when the campaign has a domain/account path, the
@@ -877,10 +879,13 @@ Required behavior:
   broad anchor-only lanes as fallback inventory only, and retarget before
   sampling if the first pass is broad.
 - Signals viability is based on estimated ICP-fit reachable engagers, not raw
-  post count and not whether it beats Sales Nav scale. If 5-8 selected posts can
-  plausibly produce ~150+ ICP-fit warm prospects before final filtering, keep
-  Signals as a viable focused option. If stricter cleanup likely reduces that to
-  ~100 usable prospects, say so plainly instead of discarding it.
+  post count and not whether it beats Sales Nav scale. Keep source-capacity
+  planning separate from the 15-row review-batch import: the default source
+  target is 300 likely good-fit leads, while `import.importLimit` remains 15 for
+  the first campaign review batch. If 5-8 selected posts can plausibly produce
+  ~150+ ICP-fit warm prospects before final filtering, keep Signals as a viable
+  focused option, but say it is below the default 300-lead source target unless
+  the math shows otherwise.
 - When Signals is viable-but-smaller and Sales Nav or Prospeo is more scalable,
   the user-facing lead review must present the choice: Signals for a warmer,
   smaller, higher-reply-upside first batch versus Sales Nav/Prospeo for broader
@@ -901,8 +906,13 @@ fit x cleanup factor = ~300-500 likely usable warm leads`.
   last 30 days, prefer the last 7-14 days when quality is comparable, and call
   out any older post as a deliberate tradeoff. Do not hide post age inside the
   raw search count
-- default source quality target is 500+ likely good-fit leads for scalable
-  outbound unless the campaign or user supplies a different target. Accept
+- default source quality target is 300 likely good-fit leads for scalable
+  outbound unless the campaign or user supplies a different source target.
+  Compute required engagers from the observed fit rate: `target good-fit leads /
+sampled fit rate`. For example, 20 good fits per 100 engagers means a 300
+  good-fit source target needs about 1,500 engagers scraped; use average
+  reachable engagers per right-content post to calculate how many posts are
+  needed. Accept
   ~150+ likely ICP-fit warm prospects as viable for a focused Signals-first
   campaign or first review batch only when the user is choosing warmth over
   scale. Name the volume tradeoff in `lead-review.md` and the source approval
@@ -1025,8 +1035,10 @@ not a research memo. It must include only:
   activity filters. For Signals, name the selected post set. For Prospeo, name
   the account/domain and title recipe.
 - `Math:` with these labels and values:
-  `Eligible posts`, `Sample`, `ICP-fit`, `Target`, `Posts needed`, `Selected`,
-  `Expected good-fit leads`, and `Scale option`.
+  `Eligible posts`, `Sample`, `ICP-fit`, `Good-fit / 100 engagers`,
+  `Required engagers`, `Avg engagers/post`, `Good-fit / post`, `Source target`,
+  `Posts needed`, `Selected`, `Review batch`, `Expected good-fit leads`, and
+  `Scale option`.
 - `Why this source:` with at most two bullets.
 - `Watch link: {watchUrl}` only when the campaign shell exists and the host
   needs a handoff link.
@@ -1036,14 +1048,22 @@ Do not include keyword-lane tables, LinkedIn-post-sampled tables, sample-lead
 lists, or long tradeoff prose in the default approval packet. Keep those details
 in `lead-review.md` or campaign/source decision state. The math block is the
 bottom-line arithmetic that makes the recommendation obvious. For example:
-`Eligible posts: 8 outbound + Claude posts. Sample: 120 engagers. ICP-fit: 52/120
-(~43%, directional). Target: 500 good-fit leads. Posts needed: about 8-10 at
-this fit rate. Selected: 8 posts. Expected good-fit leads: ~420-560 after
-dedupe/cleanup. Scale option: Sales Nav gives more rows but loses the engaged
-with this content message hook.` For Sales Nav/Prospeo alternatives, include
-preview/raw volume, sampled usable rows as `n/N` plus percentage/range,
-estimated usable range, and the warmth or context tradeoff. Do not use
-percent-only fit rates or unsupported reply-rate claims.
+`Eligible posts: 12 outbound + Claude posts. Sample: 25/125 ICP fits. ICP-fit:
+~20%, directional. Good-fit / 100 engagers: ~20 before cleanup. Required
+engagers: ~1,500 to reach 300 good-fit prospects. Avg engagers/post: ~300
+reachable. Good-fit / post: ~60. Source target: 300 good-fit leads. Posts
+needed: about 5 right-content posts. Selected: 5 posts. Review batch: import
+only 15 campaign rows first. Expected good-fit leads: ~300 before stricter
+filtering. Scale option: Sales Nav can broaden to founder/GTM/RevOps filters if
+you want colder scale, but loses the engaged-with-this-content message hook.` If
+the selected posts only support the 15-row review batch or a smaller warm pilot,
+say that plainly and do not imply the lane can hit the source target. For
+Sales Nav/Prospeo
+alternatives, include preview/raw volume, sampled usable rows as `n/N` plus
+percentage/range, estimated usable range, and the warmth or context tradeoff.
+If Sales Nav preview volume is too tight, broaden nonessential filters before
+using it as the scale option, or label it constrained and name the next fallback.
+Do not use percent-only fit rates or unsupported reply-rate claims.
 
 The first sentence of the visible decision must make the actual choice clear:
 `I recommend {primary source} using {exact filter/source recipe}. The runner-up
@@ -1091,12 +1111,16 @@ For Signals, default to a quick capacity test before final recommendation. Pick
 a narrow first sample of fresh, high-density posts, and in campaign-attached
 watch runs promote those posts with `select_promising_posts` before sampling so
 the user sees which posts are being tested. Then sample engagers, show ICP-fit
-rate as `n/N` plus percentage/range, calculate how many right-content posts are
-needed to reach the target good-fit lead count, and select/promote enough
-right-content posts if the lane can hit the target. If the first sample is good
-but volume is low, say how many more posts would be needed and offer the Sales
-Nav/Prospeo scale alternative instead of recommending an under-sized source as
-if it can produce 500+ leads.
+rate as `n/N` plus percentage/range, convert that to good-fit prospects per 100
+engagers, estimate average reachable engagers per right-content post, apply a
+conservative dedupe/cleanup factor, calculate required engagers to scrape,
+calculate good-fit prospects per post, then calculate how many right-content
+posts are needed to reach the source target good-fit lead count. Select/promote
+only enough right-content posts to hit that source target; do not scrape every
+promoted sample post by default. If the first sample is good but volume is low,
+say how many more posts would be needed and offer the Sales Nav/Prospeo scale
+alternative instead of recommending an under-sized source as if it can produce
+the default 300 good-fit source target.
 
 Keep discarded paths and full sample rows in the campaign/source decision
 context. In explicit debug/UAT runs they may also be copied into

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

@@ -525,7 +525,7 @@
           "suppliedProfilesOrCsv": "supplied-list",
           "explicitCompare": "compare-requested-sources"
         },
-        "quickViabilityRule": "Run only enough of the current lane to decide whether it can supply relevant, reachable ICP-looking leads. For Signals, viability requires sampled ICP-fit rate plus posts-needed math against the target good-fit lead count, not raw post count. Stop on the first viable source unless the user asked for comparison.",
+        "quickViabilityRule": "Run only enough of the current lane to decide whether it can supply relevant, reachable ICP-looking leads. For Signals, viability requires sampled ICP-fit rate normalized to good-fit prospects per 100 engagers, required engagers to scrape, average reachable engagers per right-content post, projected good-fit prospects per post after cleanup, and posts-needed math against the 300-good-fit source target, not raw post count or the 15-row review-batch import limit. Stop on the first viable source unless the user asked for comparison.",
         "parallelAllowedOnlyWhen": [
           "user explicitly requested source comparison",
           "resuming already-started parallel scouts",
@@ -568,7 +568,7 @@
           },
           "when": "after_source_selection_checkpoint_before_first_source_attempt",
           "requiresPriorVisibleStep": "pick-provider",
-          "rule": "Choose the first visible source lane from explicit source direction when present, otherwise default to Signal Discovery. Only run this after the Pick Provider source-selection checkpoint has been made visible and explained in chat/watchNarration. Send watchNarration with stage find-leads that says why this lane is being tried now, what quick sample or filter gate will pass/fail it, and why that helps this campaign. For Signal Discovery sampling, make it clear this is a viability path before lead import: generate intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role, not broad anchor-only lanes. For Claude/GTM campaigns, prefer lanes like Claude outbound, Claude Code LinkedIn outreach, AI SDR Claude, GTM automation Claude, and founder-led sales Claude over generic Claude Code, MCP, AI agents, or agentic coding. If the first pass is broad, retarget around the campaign wedge before selecting posts. Promote/select the first narrow sample posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and estimate whether enough right-content posts exist for the target lead count. Before final source approval, compute eligible posts, sampled ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the lane fails, update currentStep and watchNarration before moving to Sales Nav recent activity, normal Sales Nav, or Prospeo."
+          "rule": "Choose the first visible source lane from explicit source direction when present, otherwise default to Signal Discovery. Only run this after the Pick Provider source-selection checkpoint has been made visible and explained in chat/watchNarration. Send watchNarration with stage find-leads that says why this lane is being tried now, what quick sample or filter gate will pass/fail it, and why that helps this campaign. For Signal Discovery sampling, make it clear this is a viability path before lead import: generate intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role, not broad anchor-only lanes. For Claude/GTM campaigns, prefer lanes like Claude outbound, Claude Code LinkedIn outreach, AI SDR Claude, GTM automation Claude, and founder-led sales Claude over generic Claude Code, MCP, AI agents, or agentic coding. If the first pass is broad, retarget around the campaign wedge before selecting posts. Promote/select the first narrow sample posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and estimate whether enough right-content posts exist for the 300-good-fit source target. Before final source approval, compute eligible posts, sampled ICP-fit rate, good-fit prospects per 100 engagers, required engagers to scrape, average reachable engagers per right-content post, expected good-fit prospects per post after cleanup, source target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the lane fails, update currentStep and watchNarration before moving to Sales Nav recent activity, normal Sales Nav, or Prospeo."
         },
         {
           "action": "run_first_campaign_attached_source_search",
@@ -617,7 +617,7 @@
           "action": "run_subskill",
           "target": "find-leads",
           "mode": "campaign-attached-required",
-          "sourceScoutRule": "Shell-first flow requires the CampaignOffer campaignId from durable state. Pass campaignId as campaignOfferId into every provider prompt/search that can persist source state (`get_provider_prompt({ provider, campaignOfferId, confirmed: true })`, `search_signals`, `search_sales_nav`, `search_prospeo`) and include currentStep for tools that accept it so the user can watch the selected source inside the campaign. Use the default sequential source viability funnel when the user did not specify a source: Signal Discovery first, then Sales Nav with recent activity, then general Sales Nav, then Prospeo only as fallback. For Signal Discovery, use intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role; broad anchor-only lanes are fallback inventory, not selectable source lanes while narrower wedge lanes exist. Do not recommend from raw post count; sample engagers, calculate ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. Stop on the first viable source unless the user explicitly asked to compare. If the user names hiring signals, domains/accounts, supplied lists, posts/comments, or title/persona filters, start with the matching source instead. Parallel source scouts only when the user requested comparison, an existing parallel run is being resumed, or the first viable source is borderline and one cheap fallback check is needed. The later import_leads call must use the same campaignOfferId. Do not import, confirm, enrich, queue, or start leads during source discovery."
+          "sourceScoutRule": "Shell-first flow requires the CampaignOffer campaignId from durable state. Pass campaignId as campaignOfferId into every provider prompt/search that can persist source state (`get_provider_prompt({ provider, campaignOfferId, confirmed: true })`, `search_signals`, `search_sales_nav`, `search_prospeo`) and include currentStep for tools that accept it so the user can watch the selected source inside the campaign. Use the default sequential source viability funnel when the user did not specify a source: Signal Discovery first, then Sales Nav with recent activity, then general Sales Nav, then Prospeo only as fallback. For Signal Discovery, use intersection-first keyword lanes that combine the campaign anchor with the buyer pain/use case/ICP role; broad anchor-only lanes are fallback inventory, not selectable source lanes while narrower wedge lanes exist. Do not recommend from raw post count; sample engagers, calculate ICP-fit rate, good-fit prospects per 100 engagers, required engagers to scrape, average reachable engagers per right-content post, expected good-fit prospects per post after cleanup, source target good-fit lead count (default 300), posts needed, selected posts, expected good-fit range, and scale fallback. For Sales Nav fallback, do not over-tighten filters into a tiny pool; if preview/projected usable volume is below the target, loosen nonessential filters before presenting Sales Nav as the scale option and label it constrained if it still cannot reach the target. Stop on the first viable source unless the user explicitly asked to compare. If the user names hiring signals, domains/accounts, supplied lists, posts/comments, or title/persona filters, start with the matching source instead. Parallel source scouts only when the user requested comparison, an existing parallel run is being resumed, or the first viable source is borderline and one cheap fallback check is needed. The later import_leads call must use the same campaignOfferId and, for Signal Discovery, targetEngagerCount from the approved math so it does not scrape every selected sample post by default. Do not import, confirm, enrich, queue, or start leads during source discovery."
         },
         {
           "action": "optional_debug_artifacts",
@@ -720,9 +720,14 @@
             "Eligible posts",
             "Sample",
             "ICP-fit",
-            "Target",
+            "Good-fit / 100 engagers",
+            "Required engagers",
+            "Avg engagers/post",
+            "Good-fit / post",
+            "Source target",
             "Posts needed",
             "Selected",
+            "Review batch",
             "Expected good-fit leads",
             "Scale option",
             "Why this source"
@@ -764,13 +769,20 @@
             "reachable engagers count",
             "sampled engagers count",
             "sampled ICP fits as n/N plus percentage or range",
-            "target good-fit lead count",
+            "good-fit prospects per 100 engagers",
+            "required engagers to scrape",
+            "average reachable engagers per post",
+            "expected good-fit prospects per post after cleanup",
+            "dedupe or cleanup factor",
+            "source target good-fit lead count default 300",
             "posts needed for target",
             "selected posts count",
+            "15-row review-batch import limit",
             "estimated usable prospects range",
             "scale alternative source",
             "scale alternative raw or preview volume",
             "scale alternative sampled usable rows as n/N plus percentage or range",
+            "Sales Nav broadening or loosening attempts when fallback volume is too tight",
             "warmth or message-context tradeoff",
             "what to choose if the user wants more volume"
           ],
@@ -794,7 +806,7 @@
           "doNotCompressToSummaryOnly": false,
           "doNotRenderArtifactLinksOnly": true,
           "sourceRecommendationReadyWatchRule": "When the source recommendation decision card is ready in chat with counts and sample quality, and before asking for source approval, call update_campaign with leadSourceType `new`, leadSourceProvider set to the recommended primary provider, currentStep set to that provider lane (`sales-nav`, `signal-discovery`, or `prospeo`), and find-leads watchNarration. If the recommendation changed from the lane last sampled, switch the watched provider page to the recommended lane first so the user can inspect what they are approving. Use a headline like `Review the source in Codex`, body copy that says the browser is showing the evaluated source/results, and nextAction like `Approve in Codex`. Do not keep future-tense copy like `I'll show a source recommendation` after the decision is visible. Include a safety note that no leads import until the user approves the source.",
-          "chatRenderRule": "Show a compact rendered-Markdown decision card only, never a fenced code block. The first sentence must make the decision explicit: 'I recommend {primary source} using {exact filter/source recipe}. The runner-up is {source} because {reason}.' Use only these sections: Lead source decision, Source recommendation, Math, Why this source, and the concrete approval question. The Math section must include labeled lines for Eligible posts, Sample, ICP-fit, Target, Posts needed, Selected, Expected good-fit leads, and Scale option. Show fit as n/N plus an easy percentage or range, never percent-only. Do not include keyword-lane tables, LinkedIn-post-sampled tables, sample-lead lists, or long tradeoff prose in the default approval packet; keep those details in lead-review.md or campaign/source decision state. Do not forecast connection acceptance rates, reply rates, meetings, pipeline, revenue, or ROI unless the user supplied verified benchmark data for this exact workspace/sender. For Signals, do not recommend from raw post count. Compute eligible right-content posts, reachable engagers, sampled ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the user wants more volume than the warm post-engagement estimate, explicitly say which Sales Nav or Prospeo alternative provides that volume and what message-context warmth is lost. If no engagers could be fetched, say that explicitly and lower confidence. Do not show plain filesystem paths unless links cannot be created."
+          "chatRenderRule": "Show a compact rendered-Markdown decision card only, never a fenced code block. The first sentence must make the decision explicit: 'I recommend {primary source} using {exact filter/source recipe}. The runner-up is {source} because {reason}.' Use only these sections: Lead source decision, Source recommendation, Math, Why this source, and the concrete approval question. The Math section must include labeled lines for Eligible posts, Sample, ICP-fit, Good-fit / 100 engagers, Required engagers, Avg engagers/post, Good-fit / post, Source target, Posts needed, Selected, Review batch, Expected good-fit leads, and Scale option. Show fit as n/N plus an easy percentage or range, never percent-only. Do not include keyword-lane tables, LinkedIn-post-sampled tables, sample-lead lists, or long tradeoff prose in the default approval packet; keep those details in lead-review.md or campaign/source decision state. Do not forecast connection acceptance rates, reply rates, meetings, pipeline, revenue, or ROI unless the user supplied verified benchmark data for this exact workspace/sender. For Signals, do not recommend from raw post count. Compute eligible right-content posts, reachable engagers, sampled ICP-fit rate, good-fit prospects per 100 engagers, required engagers to scrape, average reachable engagers per right-content post, expected good-fit prospects per post after cleanup, source target good-fit lead count defaulting to 300, posts needed, selected posts, expected good-fit range, and scale fallback. Distinguish source-capacity math from the 15-row review-batch import limit. If the selected warm posts only support a review batch or smaller pilot, say they do not hit 300 instead of calling them scalable. If the user wants more volume than the warm post-engagement estimate, explicitly say which Sales Nav or Prospeo alternative provides that volume and what message-context warmth is lost; Sales Nav must be broadened/loosened before it is presented as the scale option if the initial filter pool is too tight. If no engagers could be fetched, say that explicitly and lower confidence. Do not show plain filesystem paths unless links cannot be created."
         },
         {
           "action": "render_post_lead_parallel_progress",
@@ -816,7 +828,7 @@
         {
           "action": "ask_continue_revise_or_confirm_only_if_needed",
           "approvalQuestionRule": "If asking the user, the question and options must name the concrete decision. Prefer: 'Approve Sales Nav with {filters}, or use warmer Signals instead?' over 'Approve this lead source?' Option labels must name the source choice, such as 'Approve Sales Nav filters', 'Use warmer Signals posts', 'Try Prospeo/account search', and 'Revise source'.",
-          "approvalMathRule": "Immediately above the approval question, render the compact Math block: given this many eligible relevant posts, this many reachable engagers, this sampled ICP fit as n/N plus percentage/range, this target good-fit lead count, and this many posts needed, we expect this usable lead range from the selected posts; if the user wants more volume, name the Sales Nav or Prospeo alternative, its preview/sample math, and the colder/weaker-context tradeoff. Do not ask the approval question until this math is visible.",
+          "approvalMathRule": "Immediately above the approval question, render the compact Math block: given this many eligible relevant posts, this many reachable engagers, this sampled ICP fit as n/N plus percentage/range, this many good-fit prospects per 100 engagers, this many required engagers to scrape, this average reachable engagers per post, this expected good-fit prospects per post after cleanup, this source target good-fit lead count defaulting to 300, and this many posts needed, we expect this usable lead range from the selected posts; also state that approval only imports a 15-row campaign review batch first after the source list is materialized. If the user wants more volume, name the Sales Nav or Prospeo alternative, its preview/sample math, any Sales Nav loosening used to avoid an over-tight pool, and the colder/weaker-context tradeoff. Do not ask the approval question until this math is visible.",
           "autoContinueWhen": {
             "status": "confirmed",
             "confidenceIn": [
@@ -902,10 +914,10 @@
           "manifest": "lead-source-intake.json",
           "defaultWhenMissing": "escalate_to_re_run_find_leads_with_campaignOfferId",
           "branches": {
-            "normal-discovery": "Reuse the campaign-attached source selections/searches created during find-leads. Do not replay searches in Step 13; if no selected source/search exists, route back to find-leads with campaignOfferId.",
+            "normal-discovery": "Reuse the campaign-attached source selections/searches created during find-leads. Do not replay searches in Step 13; if no selected source/search exists, route back to find-leads with campaignOfferId. Provider import materializes the source lead list against the approved source-capacity plan, not the 15-row review batch.",
             "supplied-linkedin-profiles": "Use the campaign-attached preview/list choice. Materialize the CSV into a source lead list when needed, then confirm_lead_list({ sourceLeadListId: leadListId, targetLeadCount: import.importLimit }).",
             "existing-lead-list": "Use the campaign-attached existingLeadListId as selectedLeadListId and call confirm_lead_list({ sourceLeadListId: existingLeadListId, targetLeadCount: import.importLimit }).",
-            "supplied-domains": "Reuse the campaign-attached domainFilterId and Prospeo search created during find-leads, then import_leads({ campaignOfferId, targetLeadCount: import.importLimit })."
+            "supplied-domains": "Reuse the campaign-attached domainFilterId and Prospeo search created during find-leads, then import_leads({ campaignOfferId, targetLeadCount: sourceTargetGoodFitLeadCount default 300 }) to materialize the source list before confirm_lead_list imports the bounded review batch."
           },
           "persistMaterializedIds": [
             "leadListId",
@@ -925,7 +937,7 @@
         },
         {
           "action": "watch_mode_orient",
-          "watchNarrationRule": "Before import_leads or confirm_lead_list starts, align the guide with chat by setting review-batch watchNarration to current-tense import copy. Also persist the approved source provider/currentStep first: Sales Nav approval must set leadSourceProvider `sales-nav` and currentStep `sales-nav`, Signals approval must set `signal-discovery`, and Prospeo approval must set `prospeo`. Use a headline like `Importing the review batch`; explain that the browser is on the approved source lane while Codex imports only the bounded 15-row review batch; include a no-launch safety note."
+          "watchNarrationRule": "Before import_leads or confirm_lead_list starts, align the guide with chat by setting review-batch watchNarration to current-tense source materialization copy. Also persist the approved source provider/currentStep first: Sales Nav approval must set leadSourceProvider `sales-nav` and currentStep `sales-nav`, Signals approval must set `signal-discovery`, and Prospeo approval must set `prospeo`. Use a headline like `Preparing the source list`; explain that the browser is on the approved source lane while Codex materializes only the approved source-capacity plan, then imports only the bounded 15-row review batch into the campaign table; include a no-launch safety note."
         },
         {
           "tool": "import_leads",
@@ -934,7 +946,12 @@
             "campaignOfferId",
             "targetLeadCount"
           ],
-          "targetLeadCountFromConfig": "import.importLimit (15)",
+          "targetLeadCountFromConfig": "sourceTargetGoodFitLeadCount (default 300) for provider source-list materialization, not import.importLimit",
+          "signalDiscoveryRequiredFields": [
+            "targetEngagerCount from approved source math",
+            "maxPostsToScrape or selected post plan when available"
+          ],
+          "signalDiscoveryRule": "For Signal Discovery, pass targetEngagerCount = ceil(sourceTargetGoodFitLeads / sampledFitRateAfterCleanup) and maxPostsToScrape = postsNeeded when known. This prevents import_leads from scraping every selected/promoted sample post by default. The first campaign review batch is still limited by confirm_lead_list targetLeadCount import.importLimit.",
           "onZeroLeads": "escalate_hard_fail",
           "modeAddHandshake": {
             "firstCallReturns": "needsModeSelection=true + existingLeadListId",

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

@@ -46,7 +46,9 @@ Supported branches:
 - **No manifest / normal discovery** — reuse the approved provider source that
   is already attached to this campaign, then import. Never call a bare
   `import_leads({ campaignOfferId })` for Signal Discovery unless selected posts
-  already exist on the campaign.
+  already exist on the campaign. Provider import materializes the source lead
+  list from the approved source-capacity plan; it is not the same target as the
+  15-row campaign review batch.
 - **Supplied LinkedIn profile CSV** — confirm `load_csv_linkedin_leads` only
   after rubrics and the approved message set are ready. Batch/materialize the
   uploaded CSV into a Sellable lead-list table. Persist the returned
@@ -65,7 +67,8 @@ Supported branches:
 - **Supplied domain/account CSV** — reuse or confirm `load_csv_domains`, keep
   its `domainFilterId`, run a campaign-associated Prospeo people search with
   `campaignOfferId`, provider prompt preflight, and `domainFilterId`, then
-  import the review batch from that search.
+  materialize the source list from that search before importing the bounded
+  review batch into the campaign table.
 
 ## Campaign-Attached Source Contract
 
@@ -90,12 +93,16 @@ the domain constraint.
 
 ## First-Import Path
 
-Default case — no existing lead list bound to the campaign:
+Default case — no existing lead list bound to the campaign. This creates or
+fills the source lead list; it does **not** clone rows into the campaign table:
 
 ```text
 import_leads({
   campaignOfferId,
-  targetLeadCount: <importLimit from auto-execute.yaml; default 15>
+  targetLeadCount: <sourceTargetGoodFitLeads; default 300>,
+  // Signal Discovery only:
+  targetEngagerCount: <ceil(sourceTargetGoodFitLeads / sampledFitRateAfterCleanup)>,
+  maxPostsToScrape: <postsNeeded from approved math>
 })
 ```
 
@@ -104,6 +111,14 @@ and should already be saved on the campaign before import. Response returns
 `{ imported, skipped, duplicates }` — surface all three to the escalation logic
 so dedup ratios are visible.
 
+For Signal Discovery, do not scrape every currently selected/promoted sample
+post by default. Before `import_leads`, reconcile selected posts with the
+approved source math. If the math says 20 good fits per 100 engagers and the
+source target is 300 good-fit leads, pass `targetEngagerCount` around 1,500 and
+only enough posts to reach that engager count. The subsequent
+`confirm_lead_list` call still uses `targetLeadCount: <importLimit>` so only the
+bounded review batch enters the campaign table.
+
 For supplied direct lists, `confirm_lead_list` must receive
 `targetLeadCount: <importLimit>` or explicit `sourceRowIds` so a 100-row source
 imports only the bounded review batch before greenlight.

package/skills/providers/signal-discovery.md

@@ -89,6 +89,20 @@ You must estimate:
   - how many sampled people matched the rough headline rubric
 - `passRate`
   - sampled pass rate used for extrapolation
+- `goodFitPer100Engagers`
+  - normalized fit rate as good-fit prospects per 100 engagers, before and
+    after a conservative dedupe/cleanup factor
+- `avgReachableEngagersPerPost`
+  - average reachable engagers per right-content post used for capacity math
+- `goodFitProspectsPerPost`
+  - 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 300 unless the campaign says otherwise
+- `requiredEngagersToScrape`
+  - `ceil(targetGoodFitLeads / sampledFitRate)`; for example 20 good-fit
+    prospects per 100 engagers means a 300-good-fit source target needs about
+    1,500 engagers scraped
 - `projectedRange`
   - the conservative range implied by the observed sample
 
@@ -112,7 +126,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%, `recentStrongPostCount`: 15-25, `freshEnoughPostCount`: 8-12, `avgUsableEngagersPerStrongPost`: 20-40, `projectedRange`: 210-600"
+   - 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. Do not manually enumerate dozens of engagers in the final answer. Summarize the sample by `sampledCount`, `passCount`, `passRate`, `projectedRange`, and 3-6 representative examples.
@@ -364,17 +378,21 @@ 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:
 
-- target good-fit leads (default 500 unless the campaign says otherwise)
+- source target good-fit leads (default 300 unless the campaign says otherwise)
 - eligible right-content posts by lane/content type
 - reachable engagers from those posts
 - sampled ICP-fit rate as `n/N` plus an easy percentage/range
+- good-fit prospects per 100 engagers before and after conservative cleanup
+- required engagers to scrape for the source target
+- average reachable engagers per right-content post
 - expected good-fit leads per selected post after dedupe/cleanup
 - posts needed to reach the target
 
-Then select enough right-content posts to plausibly hit the target. If the math
-says the warm post lane only supports a smaller first batch, say that and name
-the Sales Nav or Prospeo scale fallback rather than padding the selection with
-noisy posts.
+Then select the smallest right-content post set that plausibly hits the source
+target. Do not scrape every promoted sample post by default; promoted sampling
+state and final scrape plan are separate. If the math says the warm post lane
+only supports a smaller first batch, say that and name the Sales Nav or Prospeo
+scale fallback rather than padding the selection with noisy posts.
 
 ```json
 select_promising_posts({
@@ -420,13 +438,16 @@ as `select_promising_posts`; ask a clear yes/no question and wait for the user
 to say **yes**.
 
 For `create-campaign-v2` after the user has already approved the lead-source
-decision, that approval is the explicit confirmation for the bounded review
-batch. In that tail flow, follow `create-campaign-v2-tail`: call
+decision, that approval is the explicit confirmation to materialize the approved
+source list and then import only the bounded campaign review batch. In that
+tail flow, follow `create-campaign-v2-tail`: call
 `select_promising_posts({ campaignOfferId, selectionMode: "replace",
 selections, headlineICPCriteria })`, then call
 `import_leads({ campaignOfferId, provider: "signal-discovery",
-targetLeadCount })` for the approved review batch without asking for another
-yes/no gate. Do not import more than the approved bounded batch.
+targetLeadCount, targetEngagerCount, maxPostsToScrape })` for the approved
+source-capacity plan without asking for another yes/no gate. Then
+`confirm_lead_list` imports only the bounded review batch into the campaign
+table. Do not confuse the source scrape target with the 15-row review batch.
 
 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
@@ -434,12 +455,14 @@ or scout summary. If `select_promising_posts` returns `selectedCount: 0`, stop:
 do not call `import_leads`, do not switch providers automatically, and do not
 claim the source failed. Re-run a narrow campaign-scoped search to recover
 current post rows, or have the user promote the posts in the UI and then retry
-the bounded import.
+the source-list materialization.
 
 ```json
 import_leads({
   "campaignOfferId": "cmp_xxx",
-  "targetLeadCount": 500
+  "targetLeadCount": 300,
+  "targetEngagerCount": 1500,
+  "maxPostsToScrape": 5
 })
 ```
 
@@ -451,7 +474,7 @@ After the lead list finishes and the user confirms it looks good, call:
 confirm_lead_list({
   "campaignOfferId": "cmp_xxx",
   "jobId": "<jobId from import_leads>",
-  "targetLeadCount": 500
+  "targetLeadCount": 15
 })
 ```