@sellable/mcp 0.1.155 → 0.1.157

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

@@ -51,14 +51,15 @@ currentStep: "signal-discovery" })` before sampling so the watched Signal
    visible headline/display-name cues only. Do not enrich people during
    viability estimation.
 7. Compute capacity before recommending the source: source target good-fit
-   leads (default 150 for Signal Discovery unless the parent supplies a target),
-   reachable engagers,
-   sampled ICP-fit rate as `n/N` plus an easy percentage/range, expected usable
-   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, posts needed to hit the target, and
-   whether sampled/projected fit clears the 10% planning floor.
+   leads (default 300 for Signal Discovery unless the parent supplies a target),
+   reachable engagers, sampled headline-fit rate as `n/N` plus an easy
+   percentage/range, expected headline-fit prospects per 100 engagers, required
+   engagers to scrape (`source target / sampled headline-fit rate`), average
+   reachable engagers per right-content post, expected headline-fit prospects
+   per right-content post, posts needed to hit the target, and whether
+   sampled/projected headline-fit rate clears the 10% planning floor. Treat the
+   10% floor as a reject threshold, not as the scrape-count denominator when the
+   actual sample rate is higher.
 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.
@@ -72,12 +73,12 @@ Return a concise structured result with:
 - `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, 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, whether the 10% planning floor clears after cleanup, selected post
-  count, internal campaign-table execution-slice size, expected usable lead range, and scale
-  fallback
+  engagers, headline-fit rate as `n/N` plus percentage/range, headline-fit
+  prospects per 100 engagers, required engagers to scrape, average reachable
+  engagers per post, expected headline-fit prospects per post, posts needed for
+  target, whether the 10% planning floor clears, selected post count, internal
+  campaign-table execution-slice size, expected headline-fit lead range, and
+  scale fallback
 - `estimated_good_fit_range`
 - `message_context_strength`, directional and source-specific
 - `false_positive_patterns`
@@ -93,14 +94,18 @@ 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, 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 at the 20% working assumption, how many posts are
-  needed for that source target, and which posts you would use. Also say the
-  source list is copied into the campaign and only the first campaign-table
-  execution slice is processed internally for filter and message setup.
+  exist, how many sampled engagers passed the headline ICP rubric, what
+  headline-fit rate that implies per 100 engagers, how many headline-fit
+  prospects one right-content post should yield, how many engagers must be
+  scraped for the 300 headline-fit source target using the sampled pass rate
+  (or the 20% working assumption only when there is no stronger sample), how
+  many posts are needed for that source target, and which posts you would use.
+  Also say the source list is copied into the campaign and only the first
+  campaign-table execution slice is processed internally for filter and message
+  setup.
 - 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 300+ ICP-fit warm prospects before final filtering, even if Sales Nav is more scalable.
-- If sampled/projected fit after cleanup is below 10%, reject the Signals scrape
-  path and recommend Sales Nav recent activity as the next source.
+- Keep LinkedIn Engagement viable when selected posts can produce roughly 300+
+  headline-fit warm prospects before final filtering, even if Sales Nav is more
+  scalable.
+- If sampled/projected headline-fit rate is below 10%, reject the Signals
+  scrape path and recommend Sales Nav recent activity as the next source.

package/dist/tools/leads.js

@@ -725,8 +725,8 @@ function buildFilterChoiceWatchNarration({ sourceLeadCount, reviewRowCount, samp
 function buildSignalDiscoverySearchWatchNarration() {
     return {
         stage: "find-leads",
-        headline: "Searching Signal Discovery",
-        visibleState: "The browser is showing Signal Discovery while LinkedIn post searches run.",
+        headline: "Searching LinkedIn posts",
+        visibleState: "The browser is showing the LinkedIn post search step while approved themes run.",
         agentIntent: "Codex is searching the approved post themes and will ask before scraping selected engagers into a source list.",
         nextAction: "Review selected posts before scraping",
         safety: "Scrape approval is the next gate.",
@@ -734,11 +734,11 @@ function buildSignalDiscoverySearchWatchNarration() {
 }
 function buildSignalDiscoveryResultsWatchNarration(postsReturned) {
     const postCopy = typeof postsReturned === "number"
-        ? `${postsReturned.toLocaleString("en-US")} post${postsReturned === 1 ? "" : "s"} matched the approved search themes and are visible in Signal Discovery.`
-        : "Signal Discovery results are visible for review.";
+        ? `${postsReturned.toLocaleString("en-US")} post${postsReturned === 1 ? "" : "s"} matched the approved search themes and are visible for review.`
+        : "LinkedIn post results are visible for review.";
     return {
         stage: "find-leads",
-        headline: "Review Signal Discovery posts",
+        headline: "Review LinkedIn posts",
         visibleState: postCopy,
         agentIntent: "Codex is promoting the strongest posts, then it will ask before scraping the selected engager pool.",
         nextAction: "Approve selected posts before scraping",
@@ -749,9 +749,9 @@ function buildSelectedPostApprovalWatchNarration(selectedPostCount) {
     return {
         stage: "find-leads",
         headline: "Approve selected-post scrape",
-        visibleState: `${selectedPostCount.toLocaleString("en-US")} LinkedIn post${selectedPostCount === 1 ? "" : "s"} selected in Signal Discovery.`,
+        visibleState: `${selectedPostCount.toLocaleString("en-US")} LinkedIn post${selectedPostCount === 1 ? "" : "s"} selected for the source test.`,
         agentIntent: "Codex is asking before scraping this selected engager pool into a source list.",
-        nextAction: `Approve scraping ${selectedPostCount.toLocaleString("en-US")} Signal Discovery post${selectedPostCount === 1 ? "" : "s"}`,
+        nextAction: `Approve scraping ${selectedPostCount.toLocaleString("en-US")} selected LinkedIn post${selectedPostCount === 1 ? "" : "s"}`,
         safety: "Scrape approval is the next gate.",
     };
 }
@@ -775,12 +775,12 @@ function buildSignalDiscoverySourceRecommendation({ selectedPosts, }) {
     const estimatedGoodFit = totalEngagement * defaultFitRate;
     return `## Source Recommendation
 
-Use Signal Discovery first.
+Use LinkedIn engagement first.
 
-**Goal:** ~${targetGoodFitLeads.toLocaleString("en-US")} good-fit prospects after cleanup, enrichment, and filters<br>
-**Working assumption:** ~${Math.round(defaultFitRate * 100)}% of raw post engagers become good-fit prospects<br>
+**Goal:** ~${targetGoodFitLeads.toLocaleString("en-US")} headline-fit prospects from relevant LinkedIn engagement<br>
+**Working assumption:** ~${Math.round(defaultFitRate * 100)}% of raw post engagers pass headline filtering unless a real sample supports a different rate<br>
 **Engagers needed:** ~${sourceCandidateTarget.toLocaleString("en-US")} raw engagers<br>
-**Planning floor:** continue with Signal Discovery only when sampled/projected fit is at least ${Math.round(minPlanningFitRate * 100)}% after cleanup; below that, switch to Sales Nav recent activity<br>
+**Planning floor:** continue with LinkedIn engagement only when sampled/projected headline-fit rate is at least ${Math.round(minPlanningFitRate * 100)}%; below that, switch to Sales Nav recent activity<br>
 **Review checkpoint:** copy the confirmed source list into the campaign, then process the first ${reviewBatchSize.toLocaleString("en-US")} leads for fit and message review before scaling
 
 ### Selected posts
@@ -790,21 +790,21 @@ Use Signal Discovery first.
 ${tableRows || "| Selected posts | Campaign-matched public engagement | - |"}
 
 **Total visible pool:** ${formatApproxInteger(totalEngagement)} engagers<br>
-**Estimated good-fit pool at ${Math.round(defaultFitRate * 100)}%:** ${formatApproxInteger(estimatedGoodFit)} prospects before dedupe/risk cleanup
+**Estimated headline-fit pool at ${Math.round(defaultFitRate * 100)}%:** ${formatApproxInteger(estimatedGoodFit)} prospects before enrichment and deeper fit review
 
 ### Recommendation
 
 Approve scraping these ${selectedCount} posts.
 
-This gives enough volume to target ~${targetGoodFitLeads.toLocaleString("en-US")} good-fit prospects after cleanup, while keeping the source tied to people already engaging with the campaign's strongest public buying signals.
+This gives enough volume to target ~${targetGoodFitLeads.toLocaleString("en-US")} headline-fit prospects, while keeping the source tied to people already engaging with the campaign's strongest public buying signals.
 
 **First pass:** build the source list, copy it into the campaign, then use the first ${reviewBatchSize.toLocaleString("en-US")} campaign rows as the internal setup slice for filters and messages before scaling.
 
-**Fallback:** if the sampled/projected fit rate is below ${Math.round(minPlanningFitRate * 100)}%, or if the source sample is too vendor-heavy, agency-heavy, or off-ICP, switch to Sales Nav recent activity.
+**Fallback:** if the sampled/projected headline-fit rate is below ${Math.round(minPlanningFitRate * 100)}%, or if the source sample is too vendor-heavy, agency-heavy, or off-ICP, switch to Sales Nav recent activity.
 
 Approval card should say:
 
-**Approve scraping ${selectedCount} Signal Discovery post${selectedCount === 1 ? "" : "s"}?**`;
+**Approve scraping ${selectedCount} selected LinkedIn post${selectedCount === 1 ? "" : "s"}?**`;
 }
 function normalizeImportProvider(provider) {
     if (provider === "apollo-ai" || provider === "apollo")
@@ -1390,7 +1390,7 @@ export const leadToolDefinitions = [
                 },
                 targetEngagerCount: {
                     type: "number",
-                    description: "Signal Discovery: target number of post engagers/source candidates to scrape. Default planning target is about 300 good fits at a 20% raw-engager fit assumption, or about 1500 engagers. If the sampled/projected fit rate is below the 10% planning floor after cleanup, switch to the next provider instead of scaling noisy engagers. Limits selected posts before starting scrape, with a backend hard cap of 10 posts.",
+                    description: "Signal Discovery: target number of post engagers/source candidates to scrape. Default planning target is about 300 headline-fit prospects at a 20% raw-engager headline-pass assumption, or about 1500 engagers. Use real sample math when available: target headline-fit prospects divided by sampled headline-pass rate. If the sampled/projected headline-fit rate is below the 10% planning floor, switch to the next provider instead of scaling noisy engagers. Limits selected posts before starting scrape, with a backend hard cap of 10 posts.",
                 },
                 maxPostsToScrape: {
                     type: "number",
@@ -3089,15 +3089,15 @@ export async function selectPromisingPosts(input) {
         const { reviewBatchSize } = getSignalDiscoverySourcePlanDefaults();
         sourceRecommendation = `## Source Recommendation
 
-Use Signal Discovery first.
+Use LinkedIn engagement first.
 
-**Recommendation:** approve scraping the ${selectionResult.selectedCount} selected Signal Discovery post${selectionResult.selectedCount === 1 ? "" : "s"}.
+**Recommendation:** approve scraping the ${selectionResult.selectedCount} selected LinkedIn post${selectionResult.selectedCount === 1 ? "" : "s"}.
 
 	**First pass:** build the source list, copy it into the campaign, then process only the first ${reviewBatchSize.toLocaleString("en-US")} leads so we can inspect quality before scaling.
 
 Approval card should say:
 
-**Approve scraping ${selectionResult.selectedCount} Signal Discovery post${selectionResult.selectedCount === 1 ? "" : "s"}?**`;
+**Approve scraping ${selectionResult.selectedCount} selected LinkedIn post${selectionResult.selectedCount === 1 ? "" : "s"}?**`;
     }
     return {
         success: true,

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -139,10 +139,12 @@ should say:
 - what approval covers in one concise line
 
 Do not surface blanket source heuristics as product copy. Make the
-recommendation specific to the campaign. If Signal Discovery is recommended,
-name the exact post themes you will search. If relevant public conversations
-look unlikely, recommend the specific Sales Nav or Prospeo lane instead and say
-why. Do not call `search_signals`, `search_sales_nav`, `search_prospeo`,
+recommendation specific to the campaign. If LinkedIn engagement is recommended,
+name the exact post themes you will search and avoid using "Signal Discovery" in
+customer-facing chat; that is the internal provider/app label. If relevant
+public conversations look unlikely, recommend the specific Sales Nav or Prospeo
+lane instead and say why. Do not call `search_signals`, `search_sales_nav`,
+`search_prospeo`,
 `fetch_post_engagers`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
@@ -161,10 +163,11 @@ precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
     After scouting, ask for a second approval on the concrete source action. For
-    Signal Discovery, name how many selected posts will be scraped and the
-    target engager/source-candidate volume. For Sales Nav or Prospeo, name the
-    specific approved import lane and source lead count. Keep the internal
-    15-row campaign-table execution slice separate from source sampling.
+    LinkedIn engagement (`signal-discovery` internally), name how many selected
+    posts will be scraped and the target engager/source-candidate volume. For
+    Sales Nav or Prospeo, name the specific approved import lane and source lead
+    count. Keep the internal 15-row campaign-table execution slice separate from
+    source sampling.
 
 Do not call `import_leads` or `confirm_lead_list` until this second approval is
 granted.
@@ -181,26 +184,29 @@ granted.
     should `confirm_lead_list({ reviewBatchLimit: 15 })` copy confirmed rows into
     the campaign table and return the initial campaign-table execution slice rows.
 
-For Signal Discovery, the customer-facing approval card must use the exact
-action shape "Approve scraping N Signal Discovery posts?" and the chat summary
+For LinkedIn engagement, the customer-facing approval card must use the exact
+action shape "Approve scraping N selected LinkedIn posts?" and the chat summary
 should be a compact `## Source Recommendation` block with:
 
-- goal: about 300 good-fit prospects after cleanup, enrichment, and filters
-- source-candidate plan: about 1,500 raw engagers using a 20% working fit-rate
-  assumption unless sampled data supports a different number
-- planning floor: continue with Signal Discovery only when sampled/projected
-  fit is at least 10% after cleanup; below that, move to Sales Nav recent
-  activity instead of scraping noisy engagers
+- goal: about 300 headline-fit prospects from relevant LinkedIn engagement
+- source-candidate plan: use sample math first: target headline-fit prospects
+  divided by sampled headline-pass rate. If there is no stronger sample, use
+  about 1,500 raw engagers from the 20% working headline-pass assumption.
+- planning floor: continue with LinkedIn engagement only when sampled/projected
+  headline-fit rate is at least 10%; below that, move to Sales Nav recent
+  activity instead of scraping noisy engagers. Do not use the 10% floor as the
+  scrape-count denominator when the actual sample rate is higher.
 - campaign setup checkpoint: after the source list exists, copy confirmed source rows
   into the campaign and internally process the first execution slice for fit and message setup
 - a selected-post table with post author/topic, why it fits, and visible
   engagement
-- total visible pool and estimated good-fit pool
+- total visible pool and estimated headline-fit pool
 - first pass: build the source list and copy all confirmed source rows into the
   campaign; the campaign table then internally processes its first execution
   slice before scaling
-- fallback: switch to Sales Nav recent activity if sampled/projected fit falls
-  below 10%, or if the source sample is vendor-heavy, agency-heavy, or off-ICP
+- fallback: switch to Sales Nav recent activity if sampled/projected
+  headline-fit rate falls below 10%, or if the source sample is vendor-heavy,
+  agency-heavy, or off-ICP
 
 When the user has not supplied a source and multiple source angles are viable,
 scout those angles as independent branches when the host can actually do it:

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

@@ -133,7 +133,7 @@ copy.
 
 Default source order when the user has not supplied a source:
 
-1. LinkedIn post engagement / Signal Discovery
+1. LinkedIn post engagement (internal provider: `signal-discovery`)
 2. Sales Nav recent activity
 3. broader Sales Nav role/title filters
 4. Prospeo account/contact expansion
@@ -160,12 +160,14 @@ the question, and this first approval authorizes source scouting/search only:
 - that approval authorizes scouting/search only, not lead import or sending
 
 Do not surface blanket source heuristics as product copy. Make the recommendation
-specific to the campaign. If Signal Discovery is recommended, name the exact
-post themes you will search. If the campaign looks unlikely to have relevant
-public conversations, recommend the specific Sales Nav or Prospeo lane instead
-and say why. An approval like "Approve Prospeo plan" satisfies this gate; persist
-the provider and search next. Do not ask a second source-plan question. Do not
-call `search_signals`, `search_sales_nav`, `search_prospeo`,
+specific to the campaign. If LinkedIn engagement is recommended, name the exact
+post themes you will search and avoid using "Signal Discovery" in
+customer-facing chat; that is the internal provider/app label. If the campaign
+looks unlikely to have relevant public conversations, recommend the specific
+Sales Nav or Prospeo lane instead and say why. An approval like "Approve Prospeo
+plan" satisfies this gate; persist the provider and search next. Do not ask a
+second source-plan question. Do not call `search_signals`, `search_sales_nav`,
+`search_prospeo`,
 `fetch_post_engagers`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
@@ -174,18 +176,19 @@ sequential by default. Run `source-scout-linkedin-engagement`,
 `source-scout-sales-nav`, and `source-scout-prospeo-contact` in parallel only
 when the user explicitly requested source comparison, a prior lane failed, or
 the first viable lane is borderline and a cheap fallback check is needed.
-Use a 10% planning floor after conservative cleanup. If Signal Discovery falls
-below that floor, move to Sales Nav. If Sales Nav falls below that floor after
-reasonable refinement, move to Prospeo. Prospeo is the terminal fallback; if it
-also falls below 10%, tighten the ICP/source direction instead of inventing
-another provider.
+Use a 10% planning floor after conservative cleanup. If LinkedIn engagement
+falls below that floor, move to Sales Nav. If Sales Nav falls below that floor
+after reasonable refinement, move to Prospeo. Prospeo is the terminal fallback;
+if it also falls below 10%, tighten the ICP/source direction instead of
+inventing another provider.
 
 After scouting, show a second approval gate for the concrete source action.
-For Signal Discovery, state selected-post count, target engager/source-candidate
-volume, internal campaign-table execution-slice size, cleanup risk, and fallback;
-label the approval like "Approve scraping 3 Signal Discovery posts?" For Sales
-Nav or Prospeo, name the specific search/import lane and source lead count. Do
-not call `import_leads` or `confirm_lead_list` until this gate is approved.
+For LinkedIn engagement (`signal-discovery` internally), state selected-post
+count, target engager/source-candidate volume, internal campaign-table
+execution-slice size, cleanup risk, and fallback; label the approval like
+"Approve scraping 3 selected LinkedIn posts?" For Sales Nav or Prospeo, name the
+specific search/import lane and source lead count. Do not call `import_leads` or
+`confirm_lead_list` until this gate is approved.
 
 For Sales Nav and Prospeo, do not ask to import only the internal 15-row
 campaign-table execution slice at the source-action gate. First-page samples are
@@ -205,18 +208,18 @@ export count, not the campaign execution-slice size. For Signal Discovery, pass
 `confirmed: true`; the tool owns moving the watch UI to source-list progress
 after a lead-list/job id exists.
 
-For Signal Discovery, use this compact source-action approval shape after
+For LinkedIn engagement, use this compact source-action approval shape after
 selected posts exist:
 
 ```markdown
 ## Source Recommendation
 
-Use Signal Discovery first.
+Use LinkedIn engagement first.
 
-**Goal:** ~300 good-fit prospects after cleanup, enrichment, and filters<br>
-**Working assumption:** ~20% of raw post engagers become good-fit prospects<br>
+**Goal:** ~300 headline-fit prospects from relevant LinkedIn engagement<br>
+**Working assumption:** ~20% of raw post engagers pass headline filtering unless a real sample supports a different rate<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>
+**Planning floor:** continue only when sampled/projected headline-fit rate is at least 10%; below that, switch to Sales Nav recent activity<br>
 **Campaign setup checkpoint:** after the source list exists, copy the entire confirmed source list into the campaign and internally process only the first execution slice for filter and message setup<br>
 
 ### Selected posts

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

@@ -239,12 +239,12 @@ source. That approval only authorizes scouting/search. Second, after the
 source evidence exists, show counts, samples, fit math, cleanup risk, and ask
 for source approval before import.
 
-For Signal Discovery, the second gate is not "approve source" in the abstract.
+For LinkedIn engagement, the second gate is not "approve source" in the abstract.
 It is a concrete scrape approval: show a compact `## Source Recommendation`
-with the ~150 good-fit prospect goal, 15% raw-engager assumption, selected-post
-table, total visible pool, estimated good-fit pool, 10% planning floor,
+with the ~300 headline-fit prospect goal, source sample assumption, selected-post
+table, total visible pool, estimated headline-fit pool, 10% planning floor,
 first-pass campaign setup, and fallback. The approval question should be "Approve
-scraping N Signal Discovery posts?"
+scraping N selected LinkedIn posts?"
 
 That scrape approval is single-use. Once the user approves it, do not replay
 the source card or ask for the same approval again. Acknowledge the approval in
@@ -254,13 +254,13 @@ one sentence and call `import_leads` for the approved source immediately.
 
 Source selection is sequential by default. Start with the first recommended
 source lane from `flow.v2.json`; for the current campaign shape that is usually
-Signal Discovery / LinkedIn engagement. Only try the next fallback after the
+LinkedIn engagement. Only try the next fallback after the
 current lane is not viable, the user asks for a comparison, or the first lane is
 borderline and needs a second source to avoid a bad recommendation. The fallback
 order must stay plain: use Sales Nav to find ICP people who are actively posting
 on LinkedIn; if that is not enough, search Sales Nav by titles; if that is still
 not enough, use Prospeo for a broader account/contact path.
-Use a 10% planning floor after conservative cleanup. If Signal Discovery falls
+Use a 10% planning floor after conservative cleanup. If LinkedIn engagement falls
 below that floor, move to Sales Nav. If Sales Nav falls below that floor after
 reasonable refinement, move to Prospeo. Prospeo is the terminal fallback; if it
 also falls below 10%, tighten the ICP/source direction instead of inventing

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

@@ -399,14 +399,14 @@
             "what approval authorizes"
           ],
           "choices": [
-            "Approve Signal Discovery scouting plan",
+            "Approve LinkedIn engagement scouting plan",
             "Approve Sales Nav scouting plan",
             "Approve Prospeo scouting plan",
             "Choose different source",
             "Pause here"
           ],
           "approvalChoiceLabelsByProvider": {
-            "signal-discovery": "Approve Signal Discovery scouting plan",
+            "signal-discovery": "Approve LinkedIn engagement scouting plan",
             "sales-nav": "Approve Sales Nav scouting plan",
             "prospeo": "Approve Prospeo scouting plan"
           },
@@ -508,13 +508,13 @@
           "action": "ask_source_review_choice",
           "uses": "request_user_input",
           "choices": [
-            "Approve scraping N Signal Discovery posts",
+            "Approve scraping N selected LinkedIn posts",
             "Run the approved source import",
             "Revise source",
             "Pause here"
           ],
           "approvalChoiceLabelsByProvider": {
-            "signal-discovery": "Approve scraping {selectedPostCount} Signal Discovery posts?",
+            "signal-discovery": "Approve scraping {selectedPostCount} selected LinkedIn posts?",
             "sales-nav": "Import the approved Sales Nav source list",
             "prospeo": "Import the approved Prospeo source list"
           },

package/skills/create-campaign-v2/references/filter-leads.md

@@ -152,9 +152,9 @@ Use this test:
 - Did the campaign rows show adjacent companies that the customer would likely
   reject only after seeing the list?
 
-If yes, add an explicit exclude rule. Include named competitors from the brief,
-campaign rows, or user context when available, plus the general category
-exclusion so new lookalike competitors are also blocked.
+If yes, add an explicit exclude rule. Use the review batch as evidence. Include named competitors
+from the brief, campaign rows, or user context when available, plus the general
+category exclusion so new lookalike competitors are also blocked.
 
 ## Marketplace Safety
 

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

@@ -107,7 +107,7 @@ import_leads({
   campaignOfferId,
   targetLeadCount: <sourceCandidateTarget from approved good-fit math>,
   // Signal Discovery only:
-  targetEngagerCount: <ceil(targetGoodFitLeads / sampledFitRateAfterCleanup)>,
+  targetEngagerCount: <ceil(targetHeadlineFitProspects / sampledHeadlinePassRate)>,
   maxPostsToScrape: <postsNeeded from approved math>
 })
 ```
@@ -124,14 +124,15 @@ 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. The default good-fit target is 300 and the planning
-fit-rate assumption is 20%, so the default source-candidate plan is about 1,500
-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 during the pre-scrape sample, revise the source
-plan before importing. After an approved scrape starts, do not discard a nonempty
+approved source math. The default headline-fit target is 300 and the planning
+headline-pass assumption is 20%, so the default source-candidate plan is about
+1,500 raw engagers. If the sampled headline-fit rate is stronger or weaker, use
+that sampled rate for `ceil(targetHeadlineFitProspects / sampledHeadlinePassRate)`,
+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
+headline-fit rate; if Signal 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 campaign setup, then add more posts
 or switch provider if the source quality or scale is not enough. The subsequent

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

@@ -236,14 +236,14 @@ campaignOfferId, confirmed: true })` -> `search_signals({ campaignOfferId,
 selectionMode: "replace", selections, headlineICPCriteria })` ->
      `import_leads({ campaignOfferId, provider: "signal-discovery",
 	targetEngagerCount: 1500 })`.
-     For Signal Discovery, the promotion/select step is load-bearing. Use
+     For LinkedIn engagement (`signal-discovery` internally), the promotion/select step is load-bearing. Use
      post IDs from the current campaign-scoped `search_signals` response or
      posts the user has visibly promoted in the campaign UI. Never use post IDs
      copied only from a source-scout summary unless they have been re-resolved
      through the current campaign search state. After `select_promising_posts`,
      require `selectedCount > 0` before calling `import_leads`. If it returns
      `selectedCount: 0`, do not switch providers and do not retry import.
-     Explain that the campaign has no promoted Signal Discovery posts yet,
+     Explain that the campaign has no promoted LinkedIn posts yet,
      re-run a narrow campaign-scoped `search_signals` call to recover current
      post rows, or ask the user to promote the desired posts in the UI and then
      retry `import_leads`.

package/skills/providers/signal-discovery.md

@@ -24,10 +24,12 @@ When the user asks to find posts or start searching, **IMMEDIATELY begin Round 1
 
 <lead_target>
 
-- **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.**
+- **Default create-campaign target: ~300 headline-fit prospects that pass the
+  Signal Discovery headline criteria for now.**
+- **Use sample math first: required raw engagers =
+  `ceil(targetHeadlineFitProspects / sampledHeadlinePassRate)`. When no
+  stronger sample exists, assume ~20% of raw post engagers pass headline
+  filtering, 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
@@ -112,23 +114,24 @@ You must estimate:
 - `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
+  - normalized headline-pass rate as headline-fit prospects per 100 engagers
 - `avgReachableEngagersPerPost`
   - average reachable engagers per right-content post used for capacity math
 - `goodFitProspectsPerPost`
-  - expected good-fit prospects per right-content post after dedupe/cleanup
+  - expected headline-fit prospects per right-content post
 - `postsNeededForTarget`
   - number of right-content posts needed to reach the target good-fit lead
     count, defaulting to 300 for Signal Discovery unless the campaign says
     otherwise
 - `requiredEngagersToScrape`
-  - `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
+  - `ceil(targetHeadlineFitProspects / sampledHeadlinePassRate)`; for example
+    a 35/60 sample is ~58%, so a 300 headline-fit target needs about 515 raw
+    engagers before adding a practical coverage buffer, not 3,000. The 10%
+    floor is a viability reject threshold, not the denominator when the sample
+    rate is higher.
 - `planningFloor`
-  - minimum acceptable sampled/projected fit rate after conservative cleanup;
-    default 10%. Below this, do not scale Signal Discovery.
+  - minimum acceptable sampled/projected headline-fit rate; default 10%.
+    Below this, do not scale Signal Discovery.
 - `projectedRange`
   - the conservative range implied by the observed sample
 
@@ -152,10 +155,10 @@ 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`: ~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"
+   - preferred: "`sampledCount`: 40, `passCount`: 9, `passRate`: ~22%, `goodFitPer100Engagers`: ~22 headline-fit prospects, `requiredEngagersToScrape`: ~1,365 raw engagers for a 300 headline-fit target before a practical coverage buffer, `avgReachableEngagersPerPost`: 240, `goodFitProspectsPerPost`: ~53, `postsNeededForTarget`: ~6, `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,
+6. If sampled/projected headline-fit rate is below the 10% planning floor,
    reject the Signal Discovery scrape path and recommend Sales Nav recent
    activity as the next source.
 7. Do not manually enumerate dozens of engagers in the final answer. Summarize the sample by `sampledCount`, `passCount`, `passRate`, `projectedRange`, and 3-6 representative examples.
@@ -411,20 +414,21 @@ recommendation, estimate source capacity from real sample math:
   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
+- sampled headline-fit rate as `n/N` plus an easy percentage/range
+- headline-fit prospects per 100 engagers
+- required engagers to scrape for the source target using the sampled
+  headline-fit rate
 - average reachable engagers per right-content post
-- expected good-fit leads per selected post after dedupe/cleanup
+- expected headline-fit leads per selected post
 - posts needed to reach the target
-- whether sampled/projected fit clears the 10% planning floor
+- whether sampled/projected headline-fit rate clears the 10% planning floor
 
 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. If the
-sampled/projected fit rate is below 10% after cleanup, do not call
+sampled/projected headline-fit rate is below 10%, do not call
 `import_leads`; move to Sales Nav recent activity.
 
 ```json