@sellable/mcp 0.1.145 → 0.1.146

package/agents/post-find-leads-message-scout.md

@@ -137,8 +137,12 @@ Return a concise status with:
 - quality-gate pass/fail summary
 - whether final template review is ready or needs revision
 
-When the parent will show the recommendation in chat, format the customer-facing
-message review as Markdown with distinct copy blocks:
+When the parent will show the recommendation in chat, keep the customer-facing
+message review lightweight. Format only the approval target and one strong
+good-fill example as Markdown with distinct copy blocks. Keep token rules,
+omit/fallback examples, and bad-fill avoidance notes in your internal
+recommendation so the parent can persist them to the campaign brief after
+approval; do not print them in the default chat approval packet.
 
 ````markdown
 ## Message Template
@@ -155,19 +159,9 @@ message review as Markdown with distinct copy blocks:
 {{tokenized_message_body}}
 ```
 
-## Rendered Examples
+## Rendered Example
 
-### Good token fill
-
-```text
-Subject: ...
-
-Hey First,
-
-...
-```
-
-### Good omit / fallback
+Good token fill:
 
 ```text
 Subject: ...

package/dist/tools/leads.js

@@ -499,17 +499,18 @@ function buildSourceImportWatchNarration({ provider, selectedPostCount, estimate
             : ""}`
         : `the approved ${providerLabel} source`;
     const targetDetail = typeof targetLeadCount === "number"
-        ? ` Targeting ${targetLeadCount.toLocaleString("en-US")} source candidates before the bounded review batch is cloned.`
+        ? ` Targeting ${targetLeadCount.toLocaleString("en-US")} source leads before the bounded review batch is cloned.`
         : "";
     return {
-        stage: "review-batch",
+        stage: "find-leads",
         headline: provider === "signal-discovery"
-            ? "Scraping source candidates from posts"
-            : "Importing source candidates",
+            ? "Scraping source leads from posts"
+            : "Importing source leads",
         visibleState: `The browser is showing ${providerLabel} import progress for ${sourceDetail}.${targetDetail}`,
         agentIntent: "Codex is materializing the approved source into a lead list before cloning only the bounded review batch into the campaign.",
-        nextAction: "Wait for source candidates, then import the review batch",
+        nextAction: "Wait for source leads, then import the 15-row review batch",
         safety: "Import is limited to the review batch.",
+        progressLabel: "Source scouting",
     };
 }
 function buildSourceImportRecoveryWatchNarration(args) {

package/package.json

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

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

@@ -158,6 +158,12 @@ approval label must describe the action with the count, such as "Approve
 scraping 3 Signal Discovery posts?" 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.
+After the user approves this concrete source-action gate, do not show the
+Source Recommendation again and do not ask another source approval question.
+Acknowledge once, then call `import_leads` immediately with the approved source
+math. For Signal Discovery, pass `provider: "signal-discovery"`,
+`targetEngagerCount`, `maxPostsToScrape`, and `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
 selected posts exist:

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

@@ -243,6 +243,10 @@ table, total visible pool, estimated good-fit pool, first-pass review
 batch, and fallback. The approval question should be "Approve scraping N Signal
 Discovery 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
+one sentence and call `import_leads` for the approved source immediately.
+
 ## Parallelism + Naming
 
 Source selection is sequential by default. Start with the first recommended

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

@@ -485,6 +485,16 @@
             "signal-discovery": "Approve scraping {selectedPostCount} Signal Discovery posts?",
             "sales-nav": "Import the approved Sales Nav review batch",
             "prospeo": "Import the approved Prospeo review batch"
+          },
+          "postApprovalContract": {
+            "singleUseApproval": true,
+            "doNotRepeatAfterApproval": [
+              "Source Recommendation",
+              "show_source_decision_card",
+              "ask_source_review_choice"
+            ],
+            "requiredNextActionAfterApproval": "acknowledge in one sentence, then call import_leads immediately",
+            "signalDiscoveryNextTool": "import_leads({ campaignOfferId, provider: \"signal-discovery\", targetEngagerCount, maxPostsToScrape, confirmed: true })"
           }
         }
       ],
@@ -925,12 +935,24 @@
             "messageDraftRecommendation"
           ],
           "requiredVisibleLabels": [
-            "Subject:",
-            "Sample prospect fill:",
+            "## Message Template",
+            "## Rendered Example",
+            "Good token fill:",
             "My take:",
-            "Concern:",
             "Question: approve-message or revise-messaging?",
             "Recommendation:"
+          ],
+          "doNotShowByDefault": [
+            "Token Notes",
+            "Good omit / fallback",
+            "Bad fill to avoid",
+            "Token Adherence Table"
+          ],
+          "internalPersistenceOnly": [
+            "Token Fill Rules",
+            "Token Fill Examples",
+            "fallback guidance",
+            "bad-fill avoidance notes"
           ]
         },
         {

package/skills/create-campaign-v2/references/message-review-safety-gate.md

@@ -31,8 +31,11 @@ instead of pulling the long prompt into the main thread.
    local markdown/json artifacts in normal customer runs; emit debug artifacts
    only when the parent explicitly asks for debug/UAT output.
 5. Render the customer-facing message review in chat before asking for approval.
-   After approval, the parent persists template and token rules into campaign
-   state with `update_campaign_brief`.
+   Keep chat lightweight: show the tokenized template and one strong rendered
+   good-fill example only. Do not print the token notes table, omit/fallback
+   example, or bad-fill analysis in chat unless the user explicitly asks.
+   After approval, the parent persists template, token rules, fallback guidance,
+   and bad-fill avoidance notes into campaign state with `update_campaign_brief`.
 6. Ask exactly `approve-message` or `revise-messaging`. Do not import, queue,
    attach sequence, or start before `approve-message`.
 
@@ -89,10 +92,17 @@ but the [topic] thread felt close enough to send`. Otherwise omit the
 - If the message is plausible but not ready to send, set
   `Recommendation: revise-messaging`.
 
+## Internal Message Recommendation
+
+The message scout or parent safety gate should still produce complete internal
+review data: token-fill rules, one rendered omit/fallback example, and bad-fill
+avoidance notes. This data is for campaign-brief persistence and safety checks,
+not for the default chat approval packet.
+
 ## Customer-Facing Message Review
 
 Render this in chat before asking. Use Markdown structure so the approval target
-is visually scannable:
+is visually scannable and low-overhead:
 
 ````markdown
 Status: message-review
@@ -111,33 +121,11 @@ Status: message-review
 {{tokenized_message_body}}
 ```
 
-## Rendered Examples
-
-### Good token fill
-
-Use when the row has a clean, supported fill.
-
-```text
-Subject: ...
-
-Hey First,
-
-...
-```
-
-### Good omit / fallback
-
-Use when a row signal or company context is missing, weak, or awkward.
-
-```text
-Subject: ...
-
-Hey First,
+## Rendered Example
 
-...
-```
+### Example
 
-### Bad fill to avoid
+Good token fill:
 
 ```text
 Subject: ...
@@ -147,14 +135,6 @@ Hey First,
 ...
 ```
 
-**Why this is wrong:** one sentence naming the exact token-fill failure.
-
-## Token Notes
-
-| Token            | Use when                 | Fallback |
-| ---------------- | ------------------------ | -------- |
-| `{{first_name}}` | Clean first name exists. | `there`  |
-
 ## Recommendation
 
 **My take:** ...
@@ -168,15 +148,13 @@ Hey First,
 
 Formatting requirements:
 
-- Put the tokenized template and every rendered example in fenced `text` blocks
+- Put the tokenized template and rendered example in fenced `text` blocks
   so chat gives them a distinct background.
-- `Good token fill` and `Good omit / fallback` must each contain a complete
-  rendered subject + body, not a bullet list of token names or a single
-  bridge-line fragment.
-- Include `Bad fill to avoid` when the row sample has a tempting but unsafe
-  source-mechanics or raw-headline fill; otherwise include `Bad fill to avoid:
-none found`.
-- Use a token notes table, not paragraph-only token notes.
+- The chat example must contain a complete rendered subject + body, not a
+  bullet list of token names or a single bridge-line fragment.
+- Do not show `Good omit / fallback`, `Bad fill to avoid`, or `Token Notes` in
+  the default chat approval packet. Keep those in the internal recommendation
+  and persist them to the campaign brief after approval.
 - Keep reasoning outside the code blocks so the blocks are easy to inspect and
   approve.
 

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

@@ -57,7 +57,7 @@ Supported branches:
   list from the approved source-capacity plan; it is not the same target as the
   default 25-row campaign review batch.
 - **Supplied LinkedIn profile CSV** — confirm `load_csv_linkedin_leads` only
-  after rubrics and the approved message set are ready. Batch/materialize the
+  after the user approves that supplied-list source. Batch/materialize the
   uploaded CSV into a Sellable lead-list table. Persist the returned
   `leadListId`, then import the bounded review batch into the campaign table
   with
@@ -219,8 +219,10 @@ cannot scale further without a new source lane.
 - Zero-imported + zero-skipped ⇒ hard-fail escalate.
 - Zero-imported + high-skipped ⇒ lane-exhausted operator notice (NOT a
   silent proceed).
-- `import_leads` is NOT called before rubrics are saved and the approved message
-  set is synced into the campaign brief.
+- `import_leads` is allowed immediately after the concrete source-action
+  approval. It materializes the source list and then `confirm_lead_list` imports
+  only the bounded review batch. Enrichment, fit scoring, and message cells wait
+  for saved rubrics plus the approved message set.
 - Step 13 MUST reuse an approved source already attached with `campaignOfferId`
   before `import_leads`; it does not replay provider searches.
 - `import_leads` is NOT called again in Step 14 (validate-sample). Full