@sellable/mcp 0.1.139 → 0.1.140

package/dist/tools/navigation.js

@@ -243,9 +243,6 @@ function checkMessages(campaign) {
     if (!hasApprovedMessageTemplate(campaign)) {
         missing.push("approvedMessageTemplate");
     }
-    if (campaign.currentStep === "auto-execute-messaging") {
-        missing.push("generatedMessageReview");
-    }
     return { stepId: "messages", missing };
 }
 function checkSettings(campaign) {

package/dist/tools/processing.d.ts

@@ -58,6 +58,7 @@ export declare function upsertRubric(input: UpsertRubricInput): Promise<{
 export type CampaignRubricsResponse = {
     campaignOfferId: string;
     enableICPFilters: boolean | null;
+    currentStep?: string | null;
     workflowTableId: string | null;
     rubrics: RubricItem[];
 };

package/dist/tools/prompts.js

@@ -341,7 +341,7 @@ export function getPostFindLeadsScoutRegistry() {
         usage: {
             codex: "After the user approves or auto-confirms the lead source, spawn both returned scout `name` values in one assistant turn only when the current Codex host exposes those custom agents.",
             claude: "After lead source approval, invoke both returned Task/Agent subagents in one assistant message only when the current Claude session lists those agents, so filter-leads and message generation run concurrently.",
-            parentThreadRule: "Named agents are optional acceleration. If they are absent, do not customer-surface install status; the main thread still orchestrates filter and message branches from CampaignOffer state, selected source state, workflowTableId, and imported review-batch rows. Local markdown/json files are not normal-path inputs. The message branch must load the full generate-messages prompt, must read live campaign/review-batch state through scoped MCP/product tools, must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input, and may use the create-campaign-v2 message-review safety gate as a supplemental approval check. Join before message review. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.",
+            parentThreadRule: "Named agents are optional acceleration. If they are absent, do not customer-surface install status; the main thread still orchestrates filter and message branches from CampaignOffer state, selected source state, workflowTableId, and imported review-batch rows. Local markdown/json files are not normal-path inputs. The message drafting branch must load the full generate-messages prompt, must read live campaign/review-batch state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Template approval in the parent thread uses the create-campaign-v2 message-review safety gate; do not load the full generate-messages prompt for approval-only review. Join before message review. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.",
         },
     };
 }

package/dist/tools/rubrics.d.ts

@@ -481,6 +481,8 @@ export declare function saveRubrics(input: SaveRubricsInput): Promise<{
     criteriaCount: number;
     deletedCount: number;
     enableICPFiltersSet: boolean;
+    currentStep: string | null;
+    currentStepSet: boolean;
     rubrics: RubricItem[];
     activeRubrics: RubricItem[];
 }>;

package/dist/tools/rubrics.js

@@ -85,9 +85,39 @@ async function fetchCampaignOffer(campaignOfferId) {
     return {
         workflowTableId: v3.workflowTableId,
         enableICPFilters: v3.enableICPFilters,
+        currentStep: v3.currentStep,
         leadScoringRubrics: v3.rubrics,
     };
 }
+const filterRulesEntryWatchNarration = {
+    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",
+    progressLabel: "Fit + message",
+    safety: "No enrichment, filtering, Generate Message cells, sequence setup, or sending starts from this step.",
+};
+function shouldMoveToFilterRules(currentStep) {
+    if (!currentStep)
+        return true;
+    return [
+        "confirm-lead-list",
+        "filter-choice",
+        "create-icp-rubric",
+        "filter-rules",
+    ].includes(currentStep);
+}
+function buildEnableIcpFiltersPayload(currentStep) {
+    const payload = {
+        enableICPFilters: true,
+    };
+    if (shouldMoveToFilterRules(currentStep)) {
+        payload.currentStep = "create-icp-rubric";
+        payload.watchNarration = filterRulesEntryWatchNarration;
+    }
+    return payload;
+}
 async function getRubricsForEdit(campaignOfferId) {
     const draft = getDraftRubrics(campaignOfferId);
     if (draft) {
@@ -204,7 +234,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 on the campaign so the client can continue to Filter Leads.",
+        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.",
         inputSchema: {
             type: "object",
             properties: {
@@ -534,26 +564,43 @@ export async function saveRubrics(input) {
     // column cells=false → ICP Score runCondition evaluated false → entire
     // cascade blocked.
     let enableICPFiltersSet = false;
+    let currentStepSet = false;
     try {
         const api = getApi();
-        await api.put(`/api/v2/campaign-offers/${input.campaignOfferId}`, {
-            enableICPFilters: true,
-        });
+        const payload = buildEnableIcpFiltersPayload(campaign.currentStep);
+        await api.put(`/api/v2/campaign-offers/${input.campaignOfferId}`, payload);
         enableICPFiltersSet = true;
+        currentStepSet = payload.currentStep === "create-icp-rubric";
     }
     catch (error) {
-        // Non-fatal: the rubric save already succeeded. Log and
-        // let the caller fix the flag via update_campaign if needed.
-        console.error("[save_rubrics] Could not auto-enable ICP filtering on campaign", input.campaignOfferId, error);
+        // Non-fatal: the rubric save already succeeded. Retry the minimum
+        // enablement payload in case a stale step beat was rejected.
+        try {
+            const api = getApi();
+            await api.put(`/api/v2/campaign-offers/${input.campaignOfferId}`, {
+                enableICPFilters: true,
+            });
+            enableICPFiltersSet = true;
+            console.warn("[save_rubrics] Enabled ICP filtering without moving currentStep", input.campaignOfferId, error);
+        }
+        catch (fallbackError) {
+            console.error("[save_rubrics] Could not auto-enable ICP filtering on campaign", input.campaignOfferId, fallbackError);
+        }
     }
     return {
         success: true,
-        message: 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.`,
+        message: currentStepSet
+            ? `Saved ${normalizedDraft.length} rubric criteria, ICP filtering is ON, and the campaign is on Filter Rules.`
+            : 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.`,
         criteriaCount: normalizedDraft.length,
         deletedCount: deletedRubricIds.length,
         enableICPFiltersSet,
+        currentStep: currentStepSet
+            ? "create-icp-rubric"
+            : (campaign.currentStep ?? null),
+        currentStepSet,
         rubrics: result?.rubrics ?? normalizedDraft,
         activeRubrics: result?.rubrics ?? normalizedDraft,
     };

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -117,6 +117,25 @@ data, compare sources by source volume, sampled ICP fit, activity/warmth
 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:
+
+- given this campaign, the viable source options
+- the recommended first lane
+- why that lane fits the buyer, offer, and likely public activity
+- what will be tested next
+- 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.
+
 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:
 LinkedIn Engagement / active post engagers (internal `signal-discovery`
@@ -577,9 +596,12 @@ updates.
    queue workflow cells, attach a sequence, or start until the filter choice is
    resolved, rubrics are saved when filters are enabled, template/token rules
    are approved on the default Use Template path, and the approved message set
-   is synced into the campaign brief. After rubrics save, pause 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.
+   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
+   `enrichCellId` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval.
    Do not ask the user to approve the brief before shell creation unless they
@@ -588,8 +610,9 @@ updates.
    `mcp__sellable__update_campaign({ campaignId, currentStep })` before major
    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, `messages` for the Use
-   Template / AI Generated mode choice, `auto-execute-messaging` for approved
+   `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
+   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
    sender attach, and `send` once the recommended sequence is attached.

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

@@ -122,6 +122,26 @@ Default source order when the user has not supplied a source:
 3. broader Sales Nav role/title filters
 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:
+
+- given this campaign, the viable source options
+- the recommended first lane
+- why that lane fits the buyer, offer, and likely public activity
+- what will be tested next
+- 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.
+
 Call `get_source_scout_registry` before source scouting. Source scouting is
 sequential by default. Run `source-scout-linkedin-engagement`,
 `source-scout-sales-nav`, and `source-scout-prospeo-contact` in parallel only
@@ -145,6 +165,11 @@ After `confirm_lead_list` imports a non-empty bounded review batch and
 CampaignOffer/source/table state as the source of truth. Debug markdown/json
 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`.
+
 Lead Fit Builder persists production rubrics with `save_rubrics` when filters
 are enabled. It must not require `brief.md`, `lead-review.md`, or
 `lead-sample.json`.

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

@@ -228,6 +228,14 @@ setting: `~/.codex/config.toml` with
 
 ## Approval Ethic
 
+Lead sourcing has two approvals. First, before any provider prompt/search/scout
+call, give the user a compact source plan: "given this campaign, these are the
+real options, I recommend this first lane, here is why, here is the fallback if
+the evidence is thin." Ask them to approve that plan or choose a different
+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.
+
 ## Parallelism + Naming
 
 Source selection is sequential by default. Start with the first recommended

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

@@ -283,6 +283,27 @@
       "id": "find-leads",
       "label": "Find leads",
       "sourceSelectionFunnel": {
+        "preScoutRecommendationGate": {
+          "required": true,
+          "label": "Source plan approval",
+          "mustHappenBefore": [
+            "get_provider_prompt",
+            "search_signals",
+            "search_sales_nav",
+            "search_prospeo",
+            "fetch_post_engagers",
+            "source-scout dispatch"
+          ],
+          "show": [
+            "campaign-specific options considered",
+            "recommended first lane",
+            "why this lane matches the offer and ICP",
+            "expected evidence to gather",
+            "fallback lane if the first lane is weak",
+            "what approval authorizes"
+          ],
+          "approvalAuthorizes": "source scouting/search only; no lead import, review-batch creation, filtering, messaging, sequence, or launch"
+        },
         "defaultWhenSourceUnspecified": [
           "signal-discovery",
           "sales-nav-recent-active",
@@ -306,16 +327,47 @@
           "tool": "update_campaign",
           "requiredValues": {
             "currentStep": "pick-provider",
-            "watchNarration.stage": "find-leads"
+            "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."
           },
-          "purpose": "show the visible source-selection checkpoint before provider lanes"
+          "purpose": "show the visible source-plan approval checkpoint before provider lanes"
         },
         {
           "tool": "get_source_scout_registry",
           "purpose": "load canonical source scout names before optional branch launch"
         },
+        {
+          "action": "show_pre_scout_source_recommendation",
+          "uses": "request_user_input",
+          "requiredBeforeTools": [
+            "get_provider_prompt",
+            "search_signals",
+            "search_sales_nav",
+            "search_prospeo",
+            "fetch_post_engagers"
+          ],
+          "requiredInlineFields": [
+            "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",
+            "what scouting will check next",
+            "what approval authorizes"
+          ],
+          "choices": [
+            "Approve recommended source",
+            "Choose different source",
+            "Pause here"
+          ],
+          "approvalState": "source_lane_approved"
+        },
         {
           "action": "run_sequential_source_funnel",
+          "requiredPrecondition": "source_lane_approved",
           "defaultOrder": [
             "source-scout-linkedin-engagement",
             "source-scout-sales-nav",
@@ -532,7 +584,7 @@
           "tool": "update_campaign",
           "requiredValues": {
             "currentStep": "filter-choice",
-            "watchNarration.stage": "filter-choice"
+            "watchNarration.stage": "fit-message"
           }
         },
         {
@@ -581,6 +633,30 @@
       "id": "post-lead-workstreams",
       "label": "Filter and message workstreams",
       "onEnter": [
+        {
+          "action": "persist_add_filters_approval",
+          "tool": "update_campaign",
+          "when": "filters_enabled",
+          "requiredFields": [
+            "campaignId",
+            "enableICPFilters",
+            "currentStep",
+            "watchNarration"
+          ],
+          "requiredValues": {
+            "enableICPFilters": true,
+            "currentStep": "create-icp-rubric",
+            "watchNarration.stage": "fit-message",
+            "watchNarration.headline": "Create filter rules",
+            "watchNarration.visibleState": "Filters are enabled and the browser is showing Filter Rules while Codex defines the rubric.",
+            "watchNarration.nextAction": "Review saved filter rules"
+          },
+          "mustRunBefore": [
+            "get_post_find_leads_scout_registry",
+            "launch_or_reuse_post_lead_workstreams",
+            "save_rubrics"
+          ]
+        },
         {
           "tool": "get_post_find_leads_scout_registry",
           "purpose": "load canonical post-lead worker names"
@@ -716,7 +792,7 @@
           "target": "post-find-leads-message-scout",
           "toolCallRequiredBeforeDraft": [
             "get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) until hasMore=false",
-            "optional supplemental check: get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-safety-gate.md\" })"
+            "for approval-only parent-thread review, use get_subskill_asset({ subskillName: \"create-campaign-v2\", assetPath: \"references/message-review-safety-gate.md\" }) instead of loading generate-messages"
           ],
           "stateSource": "campaignBrief, selected source state, selectedLeadListId, workflowTableId, bounded review-batch row ids/hash",
           "outputState": "messageDraftRecommendation"
@@ -737,7 +813,7 @@
         "request_user_input"
       ],
       "toolRules": [
-        "Before message review, load the full get_subskill_prompt({ subskillName: \"generate-messages\" }) prompt and draft from campaignBrief, selected source state, selectedLeadListId, workflowTableId, and imported review-batch rows.",
+        "Before message drafting, the Message Draft Builder branch loads the full get_subskill_prompt({ subskillName: \"generate-messages\" }) prompt and drafts from campaignBrief, selected source state, selectedLeadListId, workflowTableId, and imported review-batch rows. For approval-only parent-thread template review, load references/message-review-safety-gate.md and do not load the full generate-messages prompt.",
         "Do not use brief.md, lead-review.md, or lead-sample.json as required live state; those files are optional debug context only.",
         "The compact messageDraftRecommendation must return templateRecommendation, tokenFillRules, renderedSample, concerns, status, basisToken, outputAt, outputHash, and error or retry detail.",
         "If campaign/source/table/review-batch basis does not match, classify the output stale or blocked."
@@ -838,14 +914,15 @@
         "revise_messaging"
       ],
       "transitions": {
-        "message_approved": "validate-sample",
+        "message_approved": "auto-execute-messaging",
         "revise_messaging": "message-generation"
       }
     },
     {
       "id": "validate-sample",
-      "label": "Validate bounded review batch",
+      "label": "Validate bounded review batch (legacy)",
       "currentStepValue": "validate-sample",
+      "legacyOnly": true,
       "reference": "references/sample-validation-loop.md",
       "onEnter": [
         {

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

@@ -251,8 +251,8 @@ Messages waiting for template:
 {
   "stage": "review-ready",
   "headline": "Waiting for the template",
-  "visibleState": "The fit rules are saved and the Message Draft Builder is still finishing.",
-  "agentIntent": "Codex is waiting for the Message Draft Builder and will not ask for approval until the template can be reviewed.",
+  "visibleState": "The fit rules are saved and the message template is still being prepared.",
+  "agentIntent": "Codex is waiting until the template can be reviewed.",
   "nextAction": "Review template",
   "safety": "No enrichment, filtering, or Generate Message cells run until the template is approved."
 }

package/skills/find-leads/SKILL.md

@@ -129,6 +129,12 @@ The kickoff doc is the resume surface. Re-open it before repeating discovery wor
 - Default source order for reply-likelihood-first outbound is `Signals -> Sales Nav -> Prospeo` unless the ask explicitly points elsewhere.
 - If the user is explicit about the goal, route from that goal first.
 - If the user is not explicit, infer the first hypothesis from the brief, then validate it with sample probes before recommending a lane.
+- 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.
 - 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.