@sellable/mcp 0.1.181 → 0.1.183

package/README.md

@@ -272,10 +272,11 @@ Parallel execution contract:
   filter/message prompts before that question. Once the user answers, launch the
   message-generation scout from the same campaign/table basis. If the user
   chooses filters, also launch the filter-leads scout, show Filter Rules, save
-  rubrics, then ask for filter approval. After approval, keep the browser on
-  Filter Leads while the message recommendation is reviewed. If filters are
-  skipped, move to Messages/message review. Enrichment/filtering and Generate
-  Message cells wait for message approval.
+  rubrics, then ask for filter approval. After approval, move to Filter Leads
+  and show `Filters saved + waiting for message approval` while the message
+  recommendation is reviewed. If filters are skipped, move to Messages/message
+  review. Enrichment/filtering and Generate Message cells wait for message
+  approval.
 - Claude host: use the installed `source-scout-linkedin-engagement`,
   `source-scout-sales-nav`, and `source-scout-prospeo-contact` Task/Agent
   subagents for parallel lead-source scouting only when the current session

package/dist/tools/prompts.js

@@ -340,9 +340,9 @@ export function getPostFindLeadsScoutRegistry() {
             reusePolicy: "The first completed Message Draft Builder recommendation remains the default review candidate. Later Lead Fit Builder, Filter Leads, enrichment, or rubric completion may make an enriched rewrite available, but does not automatically retry or replace the initial draft unless campaign/brief/source/list/table/review-sample identity mismatches or the initial output failed.",
         },
         usage: {
-            codex: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn returned post-lead scout names before that question. Once the user answers, spawn Message Draft Builder from the same campaign/table basis. If the user chooses filters, also spawn Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
-            claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke returned post-lead Task/Agent names before that question. Once the user answers, invoke Message Draft Builder from the same campaign/table basis. If the user chooses filters, also invoke Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
-            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. If it is absent, do not customer-surface install status; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries, filter references, or the full generate-messages prompt before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages", offset, limit }) until hasMore=false, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. On the filter path, keep the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the full generate-messages prompt ran for the current campaign/table execution slice. 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.',
+            codex: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn returned post-lead scout names before that question. Once the user answers, spawn Message Draft Builder from the same campaign/table basis. If the user chooses filters, also spawn Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
+            claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke returned post-lead Task/Agent names before that question. Once the user answers, invoke Message Draft Builder from the same campaign/table basis. If the user chooses filters, also invoke Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
+            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. If it is absent, do not customer-surface install status; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries, filter references, or the full generate-messages prompt before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages", offset, limit }) until hasMore=false, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. On the filter path, keep the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads, show `Filters saved + waiting for message approval`, and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the full generate-messages prompt ran for the current campaign/table execution slice. 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/package.json

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

package/skills/create-campaign/SKILL.md

@@ -76,6 +76,8 @@ execution slice configures filters and messages. After that, the user chooses
 whether to use filters or skip.
 When filters are chosen, save rubrics, get filter approval, then wait for
 message-template approval before enrichment/filtering or Generate Message cells.
+After filter approval, Filter Leads should show `Filters saved + waiting for
+message approval` until the template is approved.
 Use Template is the default message path; AI Generated is only an explicit
 opt-out.
 
@@ -273,10 +275,11 @@ before the filter-choice question. After `confirm_lead_list`, ask add filters
 vs skip filters immediately. Once the user answers, launch the message scout
 from the same campaign/table basis. If the user chooses filters, also launch the
 filter-leads scout, move to Filter Rules, save rubrics, then ask for filter
-approval. After approval, keep the browser on Filter Leads while the message
-recommendation is reviewed. If the user skips filters, move to Messages/message
-review. Enrichment/filtering and Generate Message cells wait for message
-approval. AI Generated is an explicit opt-out from the template path. If the
+approval. After approval, move to Filter Leads and show `Filters saved + waiting
+for message approval` while the message recommendation is reviewed. If the user
+skips filters, move to Messages/message review. Enrichment/filtering and
+Generate Message cells wait for message approval. AI Generated is an explicit
+opt-out from the template path. If the
 post-lead agents are absent, the main thread still orchestrates the same
 branches from compact MCP context.
 
@@ -750,7 +753,8 @@ updates.
    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, keep Filter Rules visible for approval; after approval,
-   move to Filter Leads and wait there for the background message recommendation.
+   move to Filter Leads and show `Filters saved + waiting for message approval`
+   until the template is approved.
    If filters are skipped, move to Messages/message review. Queue the bounded
    campaign-table execution-slice `enrichCellId` cells only after message approval. Move to
    Messages only after at least one review row passes and one generated message
@@ -763,8 +767,8 @@ updates.
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after source rows are copied into the campaign table, `create-icp-rubric` as soon
    as filters are chosen and while saved filters await approval,
-   `apply-icp-rubric` after filter approval and message approval while bounded
-   enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
+   `apply-icp-rubric` after filter approval while message approval is pending,
+   and after message approval while bounded enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
    observation state,
    `auto-execute-messaging` after at least one row passes and initial campaign-row
    messages are being generated or reviewed, `awaiting-user-greenlight` only

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

@@ -23,12 +23,14 @@ validate-sample tool:
 get_subskill_prompt({ subskillName: "create-campaign-v2-tail" })
 ```
 
-CampaignOffer state and the watch link are canonical. Resume/gating reads
-state: `campaignId`, `watchUrl`, `campaignBrief`,
-`currentStep`, source/search association, `selectedLeadListId`,
-`workflowTableId`, `leadScoringRubrics`, `approvedMessageTemplate`,
-`senderIds`, `sequenceTemplate`, and running state. Local draft files are debug
-only; do not create, link, or surface them in normal runs.
+CampaignOffer state and the watch link are canonical. CampaignOffer state is
+canonical for resume, gating, and handoff. Resume, gating, and handoff read campaign state first:
+`campaignId`, `watchUrl`, `campaignBrief`, `currentStep`, source/search
+association, `selectedLeadListId`, `workflowTableId`, `leadScoringRubrics`,
+`approvedMessageTemplate`, `senderIds`, `sequenceTemplate`, and running state.
+Local draft files are debug; do not create, link, or surface them in
+normal runs. These files are debug outputs; resume and gating read campaign
+state first.
 
 ## Normal Flow
 
@@ -64,13 +66,12 @@ First visible request when no identity is known:
 What is your LinkedIn profile URL or handle?
 ```
 
-Require a LinkedIn profile URL or public profile handle before setup continues.
-If the user provides a bare handle like `csreyes92` or a `/in/...` path,
-normalize it to `https://www.linkedin.com/in/{handle}/`. If the user provides
-anything else, ask again for the person's LinkedIn profile URL or handle. Retain
-the normalized URL as `senderLinkedinUrl` or resolve `clientProspectId` for
-`create_campaign`. Run one lightweight profile/company lookup before strategy
-questions, then say public research may be stale and invite corrections.
+Require a LinkedIn profile URL or handle before setup continues. Normalize
+`csreyes92`, `@csreyes92`, or `/in/csreyes92` to
+`https://www.linkedin.com/in/{handle}/`; otherwise ask again. Retain it as
+`senderLinkedinUrl` or resolve `clientProspectId` for `create_campaign`. Run one
+lightweight profile lookup before strategy questions, then invite
+corrections.
 
 Restore the full setup intake before the brief. Ask bounded choices for:
 
@@ -170,9 +171,12 @@ copy.
 ## Lead Source
 
 Default source order when source is unspecified: LinkedIn post engagement,
-Sales Nav recent activity, broader Sales Nav title search, then Prospeo. If
-the campaign is hiring-led or needs hiring-by-role signals, start with Prospeo;
-Sales Nav is only an activity/referral fallback for those campaigns.
+Sales Nav recent activity, broader Sales Nav title search, then Prospeo. Use that order only
+when the campaign is not hiring-led and does not need hiring-by-role signals.
+If the campaign is hiring-led or needs hiring-by-role signals, start with
+Prospeo because `search_prospeo` supports
+`company_job_posting_hiring_for` and `company_job_posting_quantity`; Sales Nav
+is only an activity/referral fallback because it does not provide hiring-by-role filters.
 
 Before any provider prompt/search/scout call, move the watched campaign to
 provider/source selection, then show one `## Find Buyers Plan` gate. The plan
@@ -317,13 +321,12 @@ 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. After `save_rubrics`, keep the app on Filter Rules so the user
-can read and approve the saved criteria. Only after that approval should
-`update_campaign` move to `apply-icp-rubric` / Filter Leads, where the run waits
-for the message template approval before enrichment, filtering, or Generate
-Message cells are queued. Tell the user the Message Draft Builder is preparing
-the template in the background.
+before rubric thinking or branch work. After `save_rubrics`, keep Filter Rules
+visible so the user can approve saved criteria. Only after approval should
+`update_campaign` move to `apply-icp-rubric` / Filter Leads and show
+`Filters saved + waiting for message approval` until the template is approved. Do not
+queue enrichment/filtering/Generate Message cells until message approval. Tell
+the user the Message Draft Builder is preparing the template in the background.
 
 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

@@ -306,11 +306,12 @@ immediately. Once the user answers, start `post-find-leads-message-scout` /
 message generation from the same campaign/table basis. If the user chooses
 filters, also start `post-find-leads-filter-scout`, move the browser to Filter
 Rules, save rubrics, then ask for filter approval. After approval, keep the
-browser on Filter Leads while the message recommendation is reviewed. If the user
-skips filters, move the browser to Messages/message review. The join gate is
-saved-filter approval or a resolved skip-filter choice, plus a message
-recommendation grounded in the same campaign/table basis. Enrichment, filtering,
-and Generate Message cells wait for template approval on the Use Template path.
+browser on Filter Leads and show `Filters saved + waiting for message approval`
+while the message recommendation is reviewed. If the user skips filters, move
+the browser to Messages/message review. The join gate is saved-filter approval or
+a resolved skip-filter choice, plus a message recommendation grounded in the same
+campaign/table basis. Enrichment, filtering, and Generate Message cells wait for
+template approval on the Use Template path.
 
 Only promise parallel post-lead work when parallel work actually started. If the
 host cannot or should not launch background branches, say the real sequence:

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

@@ -217,8 +217,9 @@ 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. After `save_rubrics`, keep the app on Filter Rules so
 the user can read and approve the saved criteria. Only that approval moves the
-app to `apply-icp-rubric` / Filter Leads, where it waits for message approval
-before enrichment/filtering is queued.
+app to `apply-icp-rubric` / Filter Leads and shows `Filters saved + waiting for
+message approval` until the template is approved. Do not queue
+enrichment/filtering/Generate Message cells until message approval.
 
 Fit + message:
 
@@ -236,15 +237,16 @@ Fit + message:
 }
 ```
 
-Review ready:
+Filters saved + waiting for message approval:
 
 ```json
 {
-  "stage": "review-ready",
-  "headline": "Review the message template",
-  "visibleState": "The browser remains on Filter Leads while the message template is reviewed in chat.",
-  "agentIntent": "Codex is waiting for the approved template before row processing starts.",
-  "nextAction": "Approve or revise the template"
+  "stage": "fit-message",
+  "headline": "Filters saved + waiting for message approval",
+  "visibleState": "The browser is showing Filter Leads with saved fit rules.",
+  "agentIntent": "Codex is waiting for the message template approval before enrichment, filtering, or Generate Message cells run.",
+  "nextAction": "Approve or revise the message template",
+  "safety": "Saved filters are ready; row processing stays gated until the message template is approved."
 }
 ```