@sellable/mcp 0.1.140 → 0.1.142

package/dist/tools/registry.js

@@ -0,0 +1,59 @@
+import { authToolDefinitions } from "./auth.js";
+import { blueprintCommitToolDefinitions } from "./blueprint-commit.js";
+import { bootstrapToolDefinitions } from "./bootstrap.js";
+import { campaignToolDefinitions } from "./campaigns.js";
+import { cellToolDefinitions } from "./cells.js";
+import { startCliLoginToolDef, waitForCliLoginToolDef } from "./cli-login.js";
+import { contextToolDefinitions } from "./context.js";
+import { directCampaignToolDefinitions } from "./direct-campaigns.js";
+import { engageBootstrapToolDefinitions } from "./engage-bootstrap.js";
+import { engageDiscoveryToolDefinitions } from "./engage-discovery.js";
+import { engageMemoryToolDefinitions } from "./engage-memory.js";
+import { engageStateToolDefinitions } from "./engage-state.js";
+import { enrichmentToolDefinitions } from "./enrichment.js";
+import { frameworkToolDefinitions } from "./framework.js";
+import { leadToolDefinitions } from "./leads.js";
+import { linkedinToolDefinitions } from "./linkedin.js";
+import { navigationToolDefinitions } from "./navigation.js";
+import { onDemandToolDefinitions } from "./one-off.js";
+import { processingToolDefinitions } from "./processing.js";
+import { promptToolDefinitions } from "./prompts.js";
+import { readinessToolDefinitions } from "./readiness.js";
+import { rowToolDefinitions } from "./rows.js";
+import { rubricToolDefinitions } from "./rubrics.js";
+import { senderToolDefinitions } from "./senders.js";
+import { sequencerToolDefinitions } from "./sequencer.js";
+import { tableToolDefinitions } from "./tables.js";
+import { verifyRowToolDefinitions } from "./verify-row.js";
+import { workspaceToolDefinitions } from "./workspaces.js";
+export const allTools = [
+    ...campaignToolDefinitions,
+    ...authToolDefinitions,
+    startCliLoginToolDef,
+    waitForCliLoginToolDef,
+    ...bootstrapToolDefinitions,
+    ...engageBootstrapToolDefinitions,
+    ...engageDiscoveryToolDefinitions,
+    ...workspaceToolDefinitions,
+    ...frameworkToolDefinitions,
+    ...contextToolDefinitions,
+    ...navigationToolDefinitions,
+    ...leadToolDefinitions,
+    ...enrichmentToolDefinitions,
+    ...processingToolDefinitions,
+    ...rubricToolDefinitions,
+    ...readinessToolDefinitions,
+    ...rowToolDefinitions,
+    ...cellToolDefinitions,
+    ...promptToolDefinitions,
+    ...linkedinToolDefinitions,
+    ...onDemandToolDefinitions,
+    ...directCampaignToolDefinitions,
+    ...senderToolDefinitions,
+    ...engageStateToolDefinitions,
+    ...engageMemoryToolDefinitions,
+    ...sequencerToolDefinitions,
+    ...tableToolDefinitions,
+    ...blueprintCommitToolDefinitions,
+    ...verifyRowToolDefinitions,
+];

package/dist/tools/rubrics.js

@@ -89,16 +89,16 @@ async function fetchCampaignOffer(campaignOfferId) {
         leadScoringRubrics: v3.rubrics,
     };
 }
-const filterRulesEntryWatchNarration = {
+const filterLeadsReadyWatchNarration = {
     stage: "fit-message",
-    headline: "Create filter rules",
-    visibleState: "Filters are enabled and the browser is showing Filter Rules while the rubric is saved.",
-    agentIntent: "Codex is defining fit rules before any enrichment, filtering, or message cells run.",
-    nextAction: "Review saved filter rules",
+    headline: "Filter Leads is ready",
+    visibleState: "Filters are enabled, rubrics are saved, and the browser is showing Filter Leads.",
+    agentIntent: "Codex is waiting for the approved message template before running enrichment, filtering, or message cells.",
+    nextAction: "Review or approve the message template before filtering",
     progressLabel: "Fit + message",
-    safety: "No enrichment, filtering, Generate Message cells, sequence setup, or sending starts from this step.",
+    safety: "Saved rules do not start enrichment, filtering, Generate Message cells, sequence setup, or sending.",
 };
-function shouldMoveToFilterRules(currentStep) {
+function shouldMoveToFilterLeads(currentStep) {
     if (!currentStep)
         return true;
     return [
@@ -106,15 +106,16 @@ function shouldMoveToFilterRules(currentStep) {
         "filter-choice",
         "create-icp-rubric",
         "filter-rules",
+        "apply-icp-rubric",
     ].includes(currentStep);
 }
 function buildEnableIcpFiltersPayload(currentStep) {
     const payload = {
         enableICPFilters: true,
     };
-    if (shouldMoveToFilterRules(currentStep)) {
-        payload.currentStep = "create-icp-rubric";
-        payload.watchNarration = filterRulesEntryWatchNarration;
+    if (shouldMoveToFilterLeads(currentStep)) {
+        payload.currentStep = "apply-icp-rubric";
+        payload.watchNarration = filterLeadsReadyWatchNarration;
     }
     return payload;
 }
@@ -234,7 +235,7 @@ export const rubricToolDefinitions = [
     },
     {
         name: "save_rubrics",
-        description: "Persist rubric criteria to the campaign. Pass leadScoringRubrics directly to save without drafting. Saving active rubrics enables ICP filtering and keeps/moves the watched client to Filter Rules; it does not apply Filter Leads by itself.",
+        description: "Persist rubric criteria to the campaign. Pass leadScoringRubrics directly to save without drafting. Saving active rubrics enables ICP filtering and moves the watched client to Filter Leads; it does not run filtering by itself.",
         inputSchema: {
             type: "object",
             properties: {
@@ -570,7 +571,7 @@ export async function saveRubrics(input) {
         const payload = buildEnableIcpFiltersPayload(campaign.currentStep);
         await api.put(`/api/v2/campaign-offers/${input.campaignOfferId}`, payload);
         enableICPFiltersSet = true;
-        currentStepSet = payload.currentStep === "create-icp-rubric";
+        currentStepSet = payload.currentStep === "apply-icp-rubric";
     }
     catch (error) {
         // Non-fatal: the rubric save already succeeded. Retry the minimum
@@ -590,7 +591,7 @@ export async function saveRubrics(input) {
     return {
         success: true,
         message: currentStepSet
-            ? `Saved ${normalizedDraft.length} rubric criteria, ICP filtering is ON, and the campaign is on Filter Rules.`
+            ? `Saved ${normalizedDraft.length} rubric criteria, ICP filtering is ON, and the campaign is on Filter Leads.`
             : enableICPFiltersSet || campaign.enableICPFilters === true
                 ? `Saved ${normalizedDraft.length} rubric criteria and ICP filtering is ON.`
                 : `Saved ${normalizedDraft.length} rubric criteria to the campaign. WARNING: could not auto-enable ICP filtering — call update_campaign({ campaignId, enableICPFilters: true }) to activate rubric-based filtering.`,
@@ -598,7 +599,7 @@ export async function saveRubrics(input) {
         deletedCount: deletedRubricIds.length,
         enableICPFiltersSet,
         currentStep: currentStepSet
-            ? "create-icp-rubric"
+            ? "apply-icp-rubric"
             : (campaign.currentStep ?? null),
         currentStepSet,
         rubrics: result?.rubrics ?? normalizedDraft,

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -16,7 +16,6 @@ allowed-tools:
   - mcp__sellable__get_active_workspace
   - mcp__sellable__list_senders
   - mcp__sellable__get_sender
-  - mcp__sellable__enrich_sender
   - mcp__sellable__complete_sender_research
   - mcp__sellable__fetch_linkedin_profile
   - mcp__sellable__fetch_linkedin_posts
@@ -54,7 +53,6 @@ allowed-tools:
   - mcp__sellable__load_csv_linkedin_leads
   - mcp__sellable__load_csv_domains
   - mcp__sellable__queue_cells
-  - mcp__sellable__generate_messages
   - mcp__sellable__get_campaign_messages_preview
   - mcp__sellable__attach_sequence
   - mcp__sellable__attach_recommended_sequence
@@ -63,7 +61,10 @@ allowed-tools:
 
 # Sellable Create Campaign
 
-Use this as the customer-facing entrypoint for Sellable campaign creation.
+Use this as the customer-facing public wrapper for Sellable campaign creation.
+It bootstraps auth and host capabilities, then loads the internal
+`create-campaign-v2` workflow prompt and `core/flow.v2.json` through MCP. Keep
+this wrapper thin; v2 is the operational source of truth.
 
 CampaignOffer state and the watch link are the customer-facing source of truth.
 Disk artifacts are optional debug/UAT diagnostics; normal customer runs should
@@ -118,7 +119,8 @@ signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
 Before any provider prompt, search, source scout, or signal-discovery call,
-show a short source-plan gate and ask for approval. The gate should say:
+show a short source-plan gate and ask for approval. This first approval
+authorizes scouting/search only. The gate should say:
 
 - given this campaign, the viable source options
 - the recommended first lane
@@ -127,14 +129,19 @@ show a short source-plan gate and ask for approval. The gate should say:
 - the fallback lane if relevant posts or ICP engagement look thin
 - that approval authorizes scouting/search only, not lead import or sending
 
-If active prospects likely engage with relevant LinkedIn content, recommend
-LinkedIn post engagement / Signal Discovery and name the post themes you will
-look for. If the niche is too private, low-volume, or unlikely to have relevant
-public posts, recommend Sales Nav recent activity, broader Sales Nav role/title
-filters, or Prospeo, and explain the tradeoff. 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.
+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`,
+`fetch_post_engagers`, or provider-scoped subagents until the user approves this
+source plan or explicitly chooses a different source.
+
+After scouting, ask for a second approval on the concrete source action. For
+Signal Discovery, name how many selected posts will be scraped, the target
+engager/source-candidate volume, and the bounded review-batch size. For Sales
+Nav or Prospeo, name the specific approved import lane. Do not call
+`import_leads` or `confirm_lead_list` until this second approval is granted.
 
 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:
@@ -331,7 +338,7 @@ the brief. This is only the client-prospect/bootstrap identity for
 Do not call `mcp__sellable__list_senders`, `mcp__sellable__get_sender`, or
 surface connected/missing sender state during setup, brief, source, filter, or
 message review. Sender availability belongs only to the Settings/final launch
-handoff after message approval and the 10-lead validation sample.
+handoff after message approval and the review-batch validation sample.
 
 If the invocation or user answer includes an existing `clientProspectId`, keep
 it as the preferred `create_campaign` identity input. If it includes a LinkedIn
@@ -537,9 +544,9 @@ updates.
        ```text
        You're in — {activeWorkspaceName} workspace, ready to roll.
 
-       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you (the founder), or whoever's voice the messages should sound like.
+       Now — paste the LinkedIn profile or company website for the client/company this campaign is for. I’ll use that to resolve the campaign identity before we pick the target, offer, proof, and lead source.
 
-       e.g. https://www.linkedin.com/in/your-handle
+       e.g. https://example.com or https://www.linkedin.com/in/client-handle
        ```
 
      - If `isReturningUser === false`, prepend ONE line confirming the new
@@ -548,16 +555,18 @@ updates.
        ```text
        You're set up — your {activeWorkspaceName} workspace is ready.
 
-       Now — paste the LinkedIn profile URL of the person you'll be sending campaigns from. Usually that's you (the founder), or whoever's voice the messages should sound like.
+       Now — paste the LinkedIn profile or company website for the client/company this campaign is for. I’ll use that to resolve the campaign identity before we pick the target, offer, proof, and lead source.
 
-       e.g. https://www.linkedin.com/in/your-handle
+       e.g. https://example.com or https://www.linkedin.com/in/client-handle
        ```
 
      No other lines. No "all set", no "signed in", no other acknowledgement.
 
-     After the user pastes the URL, proceed with the existing identity-first
-     sender flow (Step 3 onwards in the v2 subskill prompt — sender
-     enrichment via `fetch_linkedin_profile` / `enrich_sender`).
+     After the user pastes the URL, proceed with the identity-first campaign
+     setup in the v2 subskill prompt. Resolve a LinkedIn profile with
+     `fetch_linkedin_profile`, a company website/domain with `fetch_company`
+     when possible, and mark the client/company research gate with
+     `complete_sender_research` when that protocol is required.
 
 3. If auth is not OK with `error.type === "workspace"` (token valid, no active
    workspace), stop and show the returned guidance — that's not a fresh-user
@@ -599,8 +608,9 @@ updates.
    is synced into the campaign brief. When filters are approved, immediately
    call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
-   After rubrics save, pause and say the fit rules are saved; approve the
-   message template next; after approval, queue the bounded review-batch
+   After rubrics save, move the watched app to `apply-icp-rubric` / Filter
+   Leads and say the fit rules are saved; approve the message template next;
+   after approval, queue the bounded review-batch
    `enrichCellId` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval.
@@ -611,7 +621,8 @@ updates.
    visible work so the user can watch progress in the app: `create-offer` for
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after the 15-row review batch, `create-icp-rubric` as soon
-   as filters are approved, `messages` for the Use Template / AI Generated mode
+   as filters are approved, `apply-icp-rubric` after rubrics save, `messages`
+   for the Use Template / AI Generated mode
    choice, `auto-execute-messaging` for approved
    message work or the product's AI-generated path, `awaiting-user-greenlight`
    for the final handoff, `settings` for sender selection, `sequence` after

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

@@ -123,8 +123,8 @@ Default source order when the user has not supplied a source:
 4. Prospeo account/contact expansion
 
 Before any provider prompt, search, source scout, or signal-discovery call,
-show a short source-plan gate and ask for approval. The gate must say, in plain
-language:
+show a short source-plan gate and ask for approval. This first approval
+authorizes source scouting/search only. The gate must say, in plain language:
 
 - given this campaign, the viable source options
 - the recommended first lane
@@ -133,14 +133,13 @@ language:
 - the fallback lane if relevant posts or ICP engagement look thin
 - that approval authorizes scouting/search only, not lead import or sending
 
-If active prospects likely engage with relevant LinkedIn content, recommend
-LinkedIn post engagement / Signal Discovery and name the post themes you will
-look for. If the niche is too private, low-volume, or unlikely to have relevant
-public posts, recommend Sales Nav recent activity, broader Sales Nav role/title
-filters, or Prospeo, and explain the tradeoff. 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.
+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. 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.
 
 Call `get_source_scout_registry` before source scouting. Source scouting is
 sequential by default. Run `source-scout-linkedin-engagement`,
@@ -148,10 +147,19 @@ sequential by default. Run `source-scout-linkedin-engagement`,
 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.
 
-No leads import until the user approves the source. A source recommendation
-must show concrete evidence: source lane, filters or recipe, raw volume, sample
-size, sampled fits as n/N plus percentage/range, estimated usable prospects,
-cleanup risk, runner-up, and what approval authorizes.
+After scouting, show a second approval gate for the concrete source action. For
+Signal Discovery, this gate must say how many selected posts will be scraped,
+the target engager/source-candidate volume, the bounded campaign review-batch
+size, the cleanup risk, and the fallback if the selected posts look wrong. The
+approval label should describe the action, such as "Scrape 2 selected posts for
+the bounded review batch." For Sales Nav or Prospeo, the label should name the
+specific search/import lane. Do not call `import_leads` or `confirm_lead_list`
+until this second source-action approval is granted.
+
+A source recommendation must show concrete evidence: source lane, filters or
+recipe, raw volume, sample size, sampled fits as n/N plus percentage/range,
+estimated usable prospects, cleanup risk, runner-up, and what approval
+authorizes.
 
 Supplied profile CSVs, company/domain CSVs, pasted domains, and existing
 Sellable lead lists are supported, but keep provider mechanics out of the first
@@ -168,7 +176,9 @@ artifacts are optional only.
 When the user chooses filters, immediately call
 `update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
 before rubric thinking or branch work. The watched app should move to Filter
-Rules quickly, then show the saved rubric there after `save_rubrics`.
+Rules quickly. After `save_rubrics`, the watched app should move to
+`apply-icp-rubric` / Filter Leads so the user can see the saved filters are
+ready before message approval unlocks any enrichment or filtering.
 
 Lead Fit Builder persists production rubrics with `save_rubrics` when filters
 are enabled. It must not require `brief.md`, `lead-review.md`, or

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

@@ -47,14 +47,14 @@ The customer believes Sellable is helping them launch a campaign. Keep every
 turn anchored to that:
 
 1. Confirm who/what company the campaign is for.
-2. Confirm who the LinkedIn messages send from.
-3. Understand the company and offer.
-4. Turn that into a campaign brief.
-5. Find likely responders.
-6. Filter for fit.
-7. Draft messages.
-8. Ask for approval.
-9. Create the campaign.
+2. Understand the company, offer, target, proof, and lead-source direction.
+3. Turn that into a campaign brief and create the watchable campaign shell.
+4. Ask for brief approval before any lead import or sending-adjacent work.
+5. Find likely responders and approve the source.
+6. Import only the bounded review batch.
+7. Filter for fit and draft the reusable message template from the same sample.
+8. Ask for message approval before queueing the review-batch cascade.
+9. Use Settings for sender selection, sequence attach, and final launch handoff.
 
 Approvals only feel safe when the user can see what they are approving. Before
 any approve/revise question, show the relevant decision in plain language. For a
@@ -80,12 +80,13 @@ the sentence, or revise the message. It should include the exact fallback
 example, like `omit the noticed... line` or `use "operators"`. Missing data
 should never produce robotic or creepy copy.
 
-Approved token guidance is part of the campaign, not just the review. Before
-the 15-lead test batch imports, the campaign brief should carry forward the
-token fill rules and examples: good fills, good omits, bad fills, fallback
+Approved token guidance is part of the campaign, not just the review. After the
+bounded review batch exists and message generation has a selected template, the
+campaign brief should carry forward the token fill rules and examples before any
+workflow-table cascade is queued: good fills, good omits, bad fills, fallback
 rules, and why the bad fills are blocked.
 The campaign brief must carry forward the token fill rules from review into the
-live campaign state before import.
+live campaign state before enrichment, filtering, or Generate Message cells run.
 
 ## Progress Updates
 
@@ -147,18 +148,17 @@ unless the user asks for them.
 Good opening:
 
 ```text
-I’ll help you launch this as a Sellable campaign. First I’ll confirm who we’re
-sending from and which company this is for, then I’ll turn that into a campaign
-brief before any leads are imported or anything can send.
+I’ll help you launch this as a Sellable campaign. First I’ll resolve the
+client/company this campaign is for, then I’ll turn that into a campaign brief
+before any leads are imported or anything can send.
 ```
 
 Good identity setup:
 
 ```text
-I’ll check whether you already have a connected sender here. If I find one, I’ll
-ask whether that’s you and whether this campaign is for that company. If not,
-just paste your LinkedIn URL or company domain and I’ll look it up before we
-keep going.
+I’ll confirm the client/company this campaign is for before we pick the target,
+offer, proof, and lead source. Paste a LinkedIn profile or company website and
+I’ll resolve the campaign identity before the setup choices.
 ```
 
 Bad:

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

@@ -328,11 +328,11 @@
           "requiredValues": {
             "currentStep": "pick-provider",
             "watchNarration.stage": "find-leads",
-            "watchNarration.headline": "Choose the first source",
-            "watchNarration.visibleState": "The browser is showing source selection.",
-            "watchNarration.agentIntent": "Codex is explaining the source lane before sampling leads.",
-            "watchNarration.nextAction": "Approve a source lane",
-            "watchNarration.safety": "No leads import until a source is approved."
+            "watchNarration.headline": "Review the source plan",
+            "watchNarration.visibleState": "The browser is showing source selection before scouting starts.",
+            "watchNarration.agentIntent": "Codex is explaining the recommended campaign-specific source lane and fallback before any search runs.",
+            "watchNarration.nextAction": "Approve a scouting plan or choose another source",
+            "watchNarration.safety": "Approval here authorizes source scouting/search only; no selected-post scrape, lead import, filtering, messaging, sequence, or sending starts."
           },
           "purpose": "show the visible source-plan approval checkpoint before provider lanes"
         },
@@ -354,17 +354,48 @@
             "plain-language source options for this campaign",
             "recommended first source lane",
             "why the lane is likely to have relevant active prospects",
-            "why a database/recent-activity fallback may be better if niche conversations are thin",
+            "fallback lane if the recommended lane looks weak",
             "what scouting will check next",
             "what approval authorizes"
           ],
           "choices": [
-            "Approve recommended source",
+            "Approve Signal Discovery scouting plan",
+            "Approve Sales Nav scouting plan",
+            "Approve Prospeo scouting plan",
             "Choose different source",
             "Pause here"
           ],
+          "approvalChoiceLabelsByProvider": {
+            "signal-discovery": "Approve Signal Discovery scouting plan",
+            "sales-nav": "Approve Sales Nav scouting plan",
+            "prospeo": "Approve Prospeo scouting plan"
+          },
           "approvalState": "source_lane_approved"
         },
+        {
+          "action": "persist_provider_search_step_before_search",
+          "tool": "update_campaign",
+          "requiredPrecondition": "source_lane_approved",
+          "providerCurrentStepMap": {
+            "signal-discovery": "signal-discovery",
+            "sales-nav": "sales-nav",
+            "prospeo": "prospeo"
+          },
+          "requiredValues": {
+            "leadSourceType": "new",
+            "leadSourceProvider": "approved provider",
+            "currentStep": "provider-specific current step",
+            "watchNarration.stage": "find-leads",
+            "watchNarration.headline": "Searching the approved source lane",
+            "watchNarration.safety": "Search/scouting only; no lead import or selected-post scrape starts from this update."
+          },
+          "mustRunBefore": [
+            "search_signals",
+            "search_sales_nav",
+            "search_prospeo",
+            "fetch_post_engagers"
+          ]
+        },
         {
           "action": "run_sequential_source_funnel",
           "requiredPrecondition": "source_lane_approved",
@@ -428,6 +459,9 @@
           "action": "show_source_decision_card",
           "requiredInlineFields": [
             "primary source and exact filters/recipe",
+            "specific source action awaiting approval",
+            "for Signal Discovery: selected post count and target engager/source-candidate volume",
+            "bounded review batch size",
             "runner-up and why it lost",
             "raw volume",
             "sampled people",
@@ -441,10 +475,16 @@
           "action": "ask_source_review_choice",
           "uses": "request_user_input",
           "choices": [
-            "Approve source",
+            "Scrape selected posts for the bounded review batch",
+            "Run the approved source import for the bounded review batch",
             "Revise source",
             "Pause here"
-          ]
+          ],
+          "approvalChoiceLabelsByProvider": {
+            "signal-discovery": "Scrape selected posts for the bounded review batch",
+            "sales-nav": "Import the approved Sales Nav review batch",
+            "prospeo": "Import the approved Prospeo review batch"
+          }
         }
       ],
       "requiredCampaignState": [
@@ -683,7 +723,12 @@
             "campaignOfferId",
             "leadScoringRubrics"
           ],
-          "writesCampaignState": "leadScoringRubrics"
+          "writesCampaignState": "leadScoringRubrics",
+          "requiredSideEffects": {
+            "enableICPFilters": true,
+            "currentStep": "apply-icp-rubric",
+            "watchNarration.headline": "Filter Leads is ready"
+          }
         }
       ],
       "requiredCampaignState": [
@@ -722,6 +767,10 @@
         "revise_rubric",
         "revise_messaging"
       ],
+      "hardRules": [
+        "after_save_rubrics_currentStep_must_be_apply-icp-rubric",
+        "do_not_move_browser_to_messages_until_filter_leads_step_is_current_or_filters_are_explicitly_skipped"
+      ],
       "transitions": {
         "post_lead_workstreams_ready": "message-review",
         "revise_leads": "find-leads",
@@ -747,7 +796,12 @@
             "campaignOfferId",
             "leadScoringRubrics"
           ],
-          "writesCampaignState": "leadScoringRubrics"
+          "writesCampaignState": "leadScoringRubrics",
+          "requiredSideEffects": {
+            "enableICPFilters": true,
+            "currentStep": "apply-icp-rubric",
+            "watchNarration.headline": "Filter Leads is ready"
+          }
         }
       ],
       "requiredCampaignState": [

package/skills/create-campaign-v2/references/watch-guide-narration.md

@@ -214,7 +214,9 @@ and do not say filtering the batch before rubrics and message approval are
 saved. Only show worker statuses as running if those branches actually started.
 When the user chooses filters, immediately persist `enableICPFilters: true` and
 move to `create-icp-rubric` so the watched app shows Filter Rules while Codex
-defines the rules in chat.
+defines the rules in chat. After `save_rubrics`, move to `apply-icp-rubric`
+so the watched app shows Filter Leads with saved rules before message approval
+unlocks any enrichment or filtering.
 
 Fit + message:
 

package/skills/find-leads/SKILL.md

@@ -132,9 +132,9 @@ The kickoff doc is the resume surface. Re-open it before repeating discovery wor
 - Before the first provider prompt, search, source scout, or signal-discovery
   call, show the user a compact source plan and get approval. The plan must say
   which campaign-specific options are plausible, which lane you recommend
-  first, why active LinkedIn engagers are or are not likely to exist for this
-  ICP/offer, what fallback lane you will use if the evidence is thin, and that
-  approval authorizes scouting/search only.
+  first, the exact evidence you expect to test for this ICP/offer, what
+  fallback lane you will use if the evidence is thin, and that approval
+  authorizes scouting/search only.
 - When enough context exists, try 1-2 alternate hypotheses if the first lane is too weak or noisy.
 - Directional preview does not require a sender, campaign, or selected lead list. Start with count/sample exploration first; only attach searches to a campaign when the user is ready to import.
 - If the user already has a LinkedIn-profile CSV, treat that as a direct lead-list path and skip discovery.