@sellable/mcp 0.1.121 → 0.1.122

package/package.json

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

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

@@ -433,7 +433,10 @@ brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   campaign brief. Do not wait for file-write chrome before asking for approval.
   Before Find Leads, call `update_campaign({ campaignId, campaignBrief,
   currentStep: "pick-provider", watchNarration: { ... } })` after approval so
-  the watch link moves out of Plan while the main thread compares source paths.
+  the watch link moves out of Plan while the main thread explains the source
+  path. This must be a visible Pick Provider checkpoint before the watched
+  browser moves into Signal Discovery, Sales Nav, Prospeo, or another provider
+  lane.
 
 - After the brief is approved, show the next progress line. When the user has
   not given a specific source direction, use the default sequential source
@@ -444,6 +447,11 @@ that gives the strongest message context if enough ICP-looking people are
 engaging. If that does not clear a quick viability check, I'll switch to Sales
 Nav with recent activity, then broader Sales Nav, and use Prospeo only as the
 fallback. No leads import until you approve the source.`
+  The watched campaign should still be on Pick Provider while this source logic
+  is being explained. If the default first lane is Signal Discovery, say clearly
+  that Codex is about to test Signal Discovery as a viability path, not import
+  leads: it will look for relevant posts, sample engagers, estimate ICP fit, and
+  only continue if the source math works.
 - If the user's request already points to a source, do not force the default
   funnel. Start with the matching lane and say why:
   - specific posts, creators, topics, comments, or engagement signals ->
@@ -453,8 +461,9 @@ fallback. No leads import until you approve the source.`
     search, or target accounts -> Prospeo
   - supplied CSV/profile list -> existing/supplied list preview
   - explicit compare request -> compare only the requested sources
-- In watch mode, do not leave the user sitting on only `pick-provider` while
-  source viability is checked. Move the campaign to the first source lane that
+- In watch mode, do not skip the Pick Provider checkpoint. First move the
+  campaign to `pick-provider` and narrate the source-selection reasoning there.
+  After that visible checkpoint, move the campaign to the first source lane that
   will actually be tested (`signal-discovery`, `sales-nav`, `prospeo`, or the
   user-directed lane), then run the campaign-attached provider prompt + provider
   search in the parent thread with `campaignOfferId`, `confirmed: true`, and

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

@@ -546,7 +546,9 @@
             "watchNarration.stage": "find-leads"
           },
           "when": "before_sequential_source_funnel",
-          "chatRenderRule": "Move the campaign watch view to Find Leads before the main thread starts source viability work. If the user did not specify a source, explain the default order: start with warm LinkedIn post engagement because it gives stronger message context and expected reply-rate upside when enough ICP-looking engagers exist; if it is not viable, switch to Sales Nav with recent activity, then broader Sales Nav, and use Prospeo only as the fallback. If the user did specify hiring signals, domains/accounts, supplied lists, posts/comments, or titles/personas, explain that the matching source overrides the default funnel. State that no leads import until a source is approved. The watchNarration headline/body must name the lane being tested, why this lane now, the quick viability gate, and the safety boundary. Do not mention MCP or local artifacts."
+          "requiresVisibleCheckpointBeforeProviderLane": true,
+          "forbidDirectPlanToProviderLane": true,
+          "chatRenderRule": "Move the campaign watch view to the Pick Provider step before the main thread starts source viability work. This must be a distinct visible checkpoint: do not jump directly from Plan to Signal Discovery, Sales Nav, Prospeo, or another provider lane in the same visible beat. While the watched browser is on Pick Provider, explain the source-selection logic. If the user did not specify a source, explain the default order: start with warm LinkedIn post engagement because it gives stronger message context and expected reply-rate upside when enough ICP-looking engagers exist; if it is not viable, switch to Sales Nav with recent activity, then broader Sales Nav, and use Prospeo only as the fallback. If starting with Signal Discovery, explicitly say this is a viability test: Codex will look for relevant posts, sample engagers, estimate ICP fit, and only continue if the source math works. If the user did specify hiring signals, domains/accounts, supplied lists, posts/comments, or titles/personas, explain that the matching source overrides the default funnel. State that no leads import until a source is approved. The watchNarration headline/body must name the first lane being considered, why this lane now, the quick viability gate, and the safety boundary. Do not mention MCP or local artifacts."
         },
         {
           "action": "advance_watch_to_initial_source_lane",
@@ -564,8 +566,9 @@
             "existingList": "saved-lists",
             "uploadedDomains": "prospeo"
           },
-          "when": "before_first_source_attempt",
-          "rule": "Choose the first visible source lane from explicit source direction when present, otherwise default to Signal Discovery. Send watchNarration with stage find-leads that says why this lane is being tried now, what quick sample or filter gate will pass/fail it, and why that helps this campaign. For Signal Discovery sampling, promote/select the first narrow sample posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and estimate whether enough right-content posts exist for the target lead count. Before final source approval, compute eligible posts, sampled ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the lane fails, update currentStep and watchNarration before moving to Sales Nav recent activity, normal Sales Nav, or Prospeo."
+          "when": "after_source_selection_checkpoint_before_first_source_attempt",
+          "requiresPriorVisibleStep": "pick-provider",
+          "rule": "Choose the first visible source lane from explicit source direction when present, otherwise default to Signal Discovery. Only run this after the Pick Provider source-selection checkpoint has been made visible and explained in chat/watchNarration. Send watchNarration with stage find-leads that says why this lane is being tried now, what quick sample or filter gate will pass/fail it, and why that helps this campaign. For Signal Discovery sampling, make it clear this is a viability path before lead import: promote/select the first narrow sample posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and estimate whether enough right-content posts exist for the target lead count. Before final source approval, compute eligible posts, sampled ICP-fit rate, target good-fit lead count, posts needed, selected posts, expected good-fit range, and scale fallback. If the lane fails, update currentStep and watchNarration before moving to Sales Nav recent activity, normal Sales Nav, or Prospeo."
         },
         {
           "action": "run_first_campaign_attached_source_search",

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

@@ -79,14 +79,27 @@ Default source funnel:
 ```json
 {
   "stage": "find-leads",
-  "headline": "Testing warm LinkedIn activity",
-  "visibleState": "Codex is starting with recent post engagement because it gives the strongest message context if enough ICP-looking people are active there.",
-  "agentIntent": "If this lane does not clear the quick sample gate, it will switch to Sales Nav with recent activity, then broader Sales Nav, and use Prospeo only as the fallback.",
+  "headline": "Choosing the lead source",
+  "visibleState": "The browser is on Pick Provider while Codex explains the source path before opening a provider lane.",
+  "agentIntent": "Codex will start with Signal Discovery when warm LinkedIn engagement looks plausible, then switch to Sales Nav or Prospeo only if the quick viability math fails.",
   "nextAction": "Review source",
   "safety": "No leads import until you approve the source."
 }
 ```
 
+Signal Discovery viability handoff:
+
+```json
+{
+  "stage": "find-leads",
+  "headline": "Checking Signal Discovery viability",
+  "visibleState": "The browser is moving from Pick Provider into Signal Discovery so the exact posts and sample math are visible.",
+  "agentIntent": "Codex is testing whether relevant posts have enough ICP-looking engagers before recommending this as the source.",
+  "nextAction": "Review source math",
+  "safety": "No leads import until you approve the source."
+}
+```
+
 Source direction override:
 
 ```json