@sellable/mcp 0.1.209 → 0.1.211

package/README.md

@@ -262,11 +262,10 @@ Provider preflight contract:
 
 Parallel execution contract:
 
-- Source scout names come from `agents/registry.json` and are exposed at runtime
-  through `get_source_scout_registry`. Add new scouts there first; installer,
-  Codex config, Claude agent files, and prompts can consume the registry for
-  explicit source-comparison/debug runs. Normal create-campaign source work
-  stays inline in the parent thread with the active provider MCP tools.
+- Source work stays inline in the parent thread with active provider MCP tools.
+  `get_source_scout_registry` intentionally returns no custom source-scout
+  agents in the normal package; do not add source scouts back without an
+  explicit source-comparison/debug requirement.
 - `get_post_find_leads_scout_registry` returns only the Message Drafting worker
   for normal create-campaign runs. After `confirm_lead_list` imports a non-empty
   review batch and rows are proven, ask the filter-choice question immediately.

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

@@ -17,20 +17,19 @@ campaign state. The main thread owns approval and campaign writes.
 
 ## Source Of Truth
 
-Use the live campaign inputs supplied by the parent thread:
+Use the lean handoff supplied by the parent thread:
 
 - `campaignId`
-- campaign revision or `campaignUpdatedAt`
-- campaign brief summary from the parent, then the current `campaignBrief` /
-  campaign brief content loaded through Sellable tools
-- selected source decision and provider state
-- `selectedLeadListId` or selected source list context
 - `workflowTableId`
-- compact initial campaign-table execution-slice basis: copied source row count,
-  review-batch row count, and review-batch basis/hash. Do not require the
-  parent to paste a long review-batch row-id list.
-- filter basis at branch start: `pending`, `use-filters`, or `skip-filters`
-- any already-saved fit/rubric result summaries supplied by the parent
+- concise brief summary: offer, buyer, source context, safe proof, blocked claims
+- concise source summary and source-use rule
+- 3-5 sample workflow-table rows with `rowId`, name, title, company, and short
+  signal
+- optional `campaignName`, `selectedLeadListId`, and filter choice
+
+Do not require campaign revision, brief hash, copied row count, review-batch
+count, row hash, or a long review-batch row-id list. The branch can verify the
+current state with live Sellable tools.
 
 Do not require or hunt for `brief.md`, `lead-review.md`, or `lead-sample.json`.
 Those files are optional debug context only when the parent explicitly provides
@@ -40,34 +39,47 @@ read stale local markdown files to reconstruct campaign state.
 All live reads must come from scoped MCP/product tools by campaign and
 workspace, such as `get_campaign`, `get_campaign_context`, and
 `get_rows_minimal({ tableId: workflowTableId })`, or from equivalent parent
-thread payloads. Load the current campaign brief and the current review-batch
-rows from those tools before drafting. Reject the task as `blocked` if the
-campaign id, workspace, `selectedLeadListId`, `workflowTableId`, review-batch
-row count, or review-batch basis/hash does not match the branch input.
+thread payloads. Load the current campaign brief/context and use the provided
+sample rows as the drafting sample. Reject the task as `blocked` if the campaign
+id, workspace, or `workflowTableId` does not match the branch input.
+
+Reference assets are packaged MCP assets. Load them only through
+`get_subskill_asset`; do not use shell commands, local `Read`, `rg`, `cat`,
+`wc`, plugin-cache paths, repo paths, or `/Users/...` paths to find them. If a
+required message reference cannot be loaded through the MCP asset loader, return
+`blocked` or `retry-needed`.
 
-## Required First Steps
+## Required Work Loop
 
-1. Load the current campaign brief and compact campaign/table state:
-   campaign name, `campaignId`, `selectedLeadListId`, `workflowTableId`,
-   copied source row count, review-batch row count, review-batch basis/hash,
-   selected source summary, filter choice, and parent-supplied brief summary.
-   Then read the current campaign/table state through scoped Sellable tools.
-   Do not ask the parent to paste row data or a long row-id list.
-2. Load the full normal-path message prompt:
+1. Load live campaign context:
+   `get_campaign`, `get_campaign_context`, and row details for the provided
+   sample row ids when available. Do not ask the parent for hashes or row-count
+   bookkeeping.
+2. Load the full normal-path message prompt, all chunks:
 
    `get_subskill_prompt({ subskillName: "generate-messages" })`
 
-3. Load the reference assets required by that prompt's Reference Asset Loading
-   pack, including validation/QA criteria. If a required validation asset cannot
-   load, return `blocked` or `retry-needed` instead of drafting from memory.
-4. Use that prompt as the drafting and QA contract. Do not use any alternate
-   prompt, examples-only shortcut, or create-campaign safety/checklist
-   instructions as a substitute for the full message prompt.
-5. Draft only from the current campaign brief, selected source context, and
-   review-batch rows loaded through scoped Sellable tools.
-6. Run the normal message validation/QA rules before final return. The final
-   recommendation must include the QA pass/fail receipt, not just draft copy.
-7. Keep the work provisional until the user chooses `Use Template` in Messages.
+3. Load every packaged reference asset required by that prompt's Reference Asset
+   Loading section with `get_subskill_asset`. If a required asset cannot load
+   through the MCP asset loader, return `blocked` or `retry-needed` instead of
+   drafting from memory.
+4. Build positioning in a compact working note: buyer, pain, product, mechanism,
+   proof boundary, source-use rule, and CTA.
+5. Draft 3 distinct first-message options: signal-led, product/mechanism-led,
+   and proof/credibility-led.
+6. Combine the strongest opener, product line, mechanism line, proof treatment,
+   and CTA into one reusable template.
+7. Define token fill rules and fallbacks, then render one good sample.
+8. Before returning, load the validation prompt:
+
+   `get_subskill_prompt({ subskillName: "create-campaign-v2-validation" })`
+
+   Use it only as a validation contract for the candidate message in this live
+   campaign branch. Do not write dry-mode artifacts. Run the final candidate
+   against token safety, proof safety, source safety, Thomas filters, AI tells,
+   single-send rule, and "would I take this call?". If it fails, revise once and
+   validate again.
+9. Keep the work provisional until the user chooses `Use Template` in Messages.
 
 ## Owned Output
 
@@ -76,15 +88,14 @@ Return the following to the parent thread:
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
 - one rendered good-fill sample for a plausible passing campaign-table row
-- one omit/fallback sample when the row signal is not safe
-- pass/fail notes against the generate-messages quality gates
-- `qaReceipt` / validation notes showing token safety, proof safety, fit
-  uncertainty, bad-fill avoidance, and "would I take this call?" judgment
 - message-draft runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
-- basis token containing campaign revision/updatedAt, brief hash,
-  `selectedLeadListId`, `workflowTableId`, compact execution-slice row
-  count/hash, filter choice, and rubric/filter basis when present
-- output timestamp/hash and any retry/error detail
+- approve-or-revise recommendation
+- validation status only: `passed`, `revised-then-passed`, or `blocked`
+- output timestamp/hash and any blocked/retry detail
+
+Do not return or render `renderedFallbackSample`, `concerns`, or a full
+`qaReceipt` in the normal happy path. Validation is an internal gate; summarize
+only if blocked or retry-needed.
 
 Do not write local markdown/json artifacts in normal live campaign runs. Return
 the recommendation directly to the parent thread. Emit debug artifacts only when
@@ -108,23 +119,21 @@ exists and points at the current non-empty campaign-table execution slice.
 ## Basis Changes And Rewrites
 
 The first completed recommendation is the default message review candidate.
-Do not automatically retry or regenerate only because Prospect Filters finished,
-rubrics were saved, Filter Leads completed, enrichment cells populated, or more
-row data became available after this branch started.
-
-Treat later filter/enrichment data as optional rewrite context. If campaign id,
-brief hash, selected source, `selectedLeadListId`, `workflowTableId`, and
-execution-slice row count/hash still match, keep the initial recommendation usable
-and report `status: ready` with `basisStatus: "usable_initial"` or
+Do not automatically retry or regenerate only because filters were saved, Filter
+Leads completed, enrichment cells populated, or more row data became available
+after this branch started.
+
+Treat later filter/enrichment data as optional rewrite context. If campaign id
+and `workflowTableId` still match, keep the initial recommendation usable and
+report `status: ready` with `basisStatus: "usable_initial"` or
 `"enriched_rewrite_available"`. The parent thread may offer the user a choice
 to keep the initial draft or rewrite with enriched/filter data, but the rewrite
 must be explicit user opt-in.
 
 Retry or regenerate without asking only when the initial recommendation is
 missing, failed, structurally invalid, unsafe, or mismatched on campaign id,
-brief hash, selected source, `selectedLeadListId`, `workflowTableId`, or
-execution-slice row count/hash. Filter/rubric/enrichment basis drift alone is not a stale
-blocker.
+`workflowTableId`, or provided sample rows. Filter/rubric/enrichment basis drift
+alone is not a stale blocker.
 
 ## User Revision Feedback And QA
 
@@ -132,17 +141,19 @@ If the parent sends user feedback, a QA request, or a rewrite request about the
 template before `approve-message`, treat it as Message Drafting work, not a
 campaign write. Use the current `messageDraftRecommendation`, basis token/hash,
 campaign/table basis, and latest user feedback as inputs. Load or reuse the full
-`generate-messages` contract and validation assets, then return a revised or
-QA-only recommendation with:
+`generate-messages` contract, all referenced assets, and
+`create-campaign-v2-validation`, then return a revised or QA-only recommendation
+with:
 
 - revised proposed template
 - what changed and why
 - token fill rule/fallback changes, if any
 - one rendered good-fill sample
-- `qaReceipt` with pass/fail notes against the loaded validation assets
-- pass/fail notes against the same quality gates
+- validation status: `passed`, `revised-then-passed`, or `blocked`
 - updated output timestamp/hash and basis token
 
+Do not return a full QA receipt unless the result is blocked or retry-needed.
+
 Keep the revision grounded in the same source/list/table rows unless the parent
 explicitly supplies a new selected list or review slice. Do not call
 `update_campaign_brief`, do not persist the template, and do not approve your
@@ -201,20 +212,18 @@ enablement`, or omit it.
 Return a concise status with:
 
 - prompt basis loaded: `generate-messages`
+- validation prompt loaded: `create-campaign-v2-validation`
 - live campaign basis used
 - proposed template
 - token fill rules/fallbacks
 - one rendered passing-row sample
-- one rendered omit/fallback sample
-- quality-gate pass/fail summary
 - whether final template review is ready or needs revision
 
 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.
+good-fill example as Markdown with distinct copy blocks. Keep validation notes,
+bad-fill avoidance notes, and QA details internal unless blocked; do not print
+them in the default chat approval packet.
 
 ````markdown
 ## Message Template

package/agents/registry.json

@@ -1,199 +1,6 @@
 {
   "version": 1,
   "agents": [
-    {
-      "id": "linkedin-engagement",
-      "name": "source-scout-linkedin-engagement",
-      "kind": "source-scout",
-      "promptFile": "source-scout-linkedin-engagement.md",
-      "displayName": "LinkedIn Source Discovery",
-      "provider": "signal-discovery",
-      "lane": "linkedin-engagement",
-      "legacy": {
-        "codex": [
-          {
-            "name": "linkedin_engagement_scout",
-            "filename": "linkedin-engagement-scout.toml"
-          }
-        ],
-        "claude": [
-          {
-            "name": "lead-explorer-signals",
-            "filename": "lead-explorer-signals.md"
-          }
-        ]
-      },
-      "codex": {
-        "description": "Sellable lead-source scout for LinkedIn post engagement and active conversation signals.",
-        "model": "gpt-5.5",
-        "modelReasoningEffort": "high",
-        "sandboxMode": "read-only",
-        "nicknameCandidates": [
-          "LinkedIn Engagement Scout",
-          "Post Scout",
-          "Engager Scout"
-        ]
-      },
-      "claude": {
-        "description": "Use proactively as a background Sellable source scout when find-leads or create-campaign needs LinkedIn post engagement, Signals, or active conversation evidence.",
-        "model": "inherit",
-        "background": true,
-        "maxTurns": 8,
-        "color": "blue",
-        "tools": [
-          "Read",
-          "Grep",
-          "Glob",
-          "mcp__sellable__get_provider_prompt",
-          "mcp__sellable__search_signals",
-          "mcp__sellable__select_promising_posts",
-          "mcp__sellable__fetch_post_engagers"
-        ]
-      }
-    },
-    {
-      "id": "sales-nav",
-      "name": "source-scout-sales-nav",
-      "kind": "source-scout",
-      "promptFile": "source-scout-sales-nav.md",
-      "displayName": "Sales Nav Source Discovery",
-      "provider": "sales-nav",
-      "lane": "sales-nav",
-      "legacy": {
-        "codex": [
-          {
-            "name": "sales_nav_scout",
-            "filename": "sales-nav-scout.toml"
-          }
-        ],
-        "claude": [
-          {
-            "name": "lead-explorer-sales-nav",
-            "filename": "lead-explorer-sales-nav.md"
-          }
-        ]
-      },
-      "codex": {
-        "description": "Sellable lead-source scout for Sales Navigator role, company, and activity filters.",
-        "model": "gpt-5.5",
-        "modelReasoningEffort": "high",
-        "sandboxMode": "read-only",
-        "nicknameCandidates": [
-          "Sales Nav Scout",
-          "Role Filter Scout",
-          "Activity Scout"
-        ]
-      },
-      "claude": {
-        "description": "Use proactively as a background Sellable source scout when find-leads or create-campaign needs Sales Navigator title, company, geography, or activity-filter evidence.",
-        "model": "inherit",
-        "background": true,
-        "maxTurns": 8,
-        "color": "cyan",
-        "tools": [
-          "Read",
-          "Grep",
-          "Glob",
-          "mcp__sellable__get_provider_prompt",
-          "mcp__sellable__lookup_sales_nav_filter",
-          "mcp__sellable__search_sales_nav"
-        ]
-      }
-    },
-    {
-      "id": "prospeo-contact",
-      "name": "source-scout-prospeo-contact",
-      "kind": "source-scout",
-      "promptFile": "source-scout-prospeo-contact.md",
-      "displayName": "Prospeo Source Discovery",
-      "provider": "prospeo",
-      "lane": "prospeo-contact",
-      "legacy": {
-        "codex": [
-          {
-            "name": "prospeo_contact_scout",
-            "filename": "prospeo-contact-scout.toml"
-          }
-        ],
-        "claude": [
-          {
-            "name": "lead-explorer-prospeo",
-            "filename": "lead-explorer-prospeo.md"
-          }
-        ]
-      },
-      "codex": {
-        "description": "Sellable lead-source scout for Prospeo account/domain and broad contact expansion.",
-        "model": "gpt-5.5",
-        "modelReasoningEffort": "high",
-        "sandboxMode": "read-only",
-        "nicknameCandidates": [
-          "Prospeo Contact Scout",
-          "Domain Scout",
-          "Contact Scout"
-        ]
-      },
-      "claude": {
-        "description": "Use proactively as a background Sellable source scout when find-leads or create-campaign needs Prospeo account, domain-list, CSV-domain, or verified-contact evidence.",
-        "model": "inherit",
-        "background": true,
-        "maxTurns": 8,
-        "color": "green",
-        "tools": [
-          "Read",
-          "Grep",
-          "Glob",
-          "mcp__sellable__get_provider_prompt",
-          "mcp__sellable__load_csv_domains",
-          "mcp__sellable__save_domain_filters",
-          "mcp__sellable__search_prospeo"
-        ]
-      }
-    },
-    {
-      "id": "filter-leads",
-      "name": "post-find-leads-filter-scout",
-      "kind": "post-find-leads-scout",
-      "promptFile": "post-find-leads-filter-scout.md",
-      "displayName": "Prospect Filters",
-      "target": "filter-leads",
-      "inputs": [
-        "campaignId",
-        "campaignBrief summary plus branch-loaded current campaignBrief",
-        "source decision and selectedLeadList/source state",
-        "workflowTableId",
-        "compact review-batch count/hash or branch-loaded review rows"
-      ],
-      "producesArtifacts": [],
-      "optionalProducesArtifacts": [],
-      "ownership": "prospect-fit criteria, false-positive patterns, keep/exclude rules, ability-to-pay checks, and production rubric translation only",
-      "codex": {
-        "description": "Prospect Filters worker for campaign-backed fit criteria and rubric persistence after review-batch import and filter approval.",
-        "model": "gpt-5.5",
-        "modelReasoningEffort": "high",
-        "sandboxMode": "read-only",
-        "nicknameCandidates": [
-          "Prospect Filters",
-          "Fit Criteria",
-          "Rubric Builder"
-        ]
-      },
-      "claude": {
-        "description": "Use proactively as Prospect Filters after review-batch import and filter approval to persist campaign rubrics from campaign state.",
-        "model": "inherit",
-        "background": true,
-        "maxTurns": 8,
-        "color": "yellow",
-        "tools": [
-          "mcp__sellable__get_subskill_prompt",
-          "mcp__sellable__get_subskill_asset",
-          "mcp__sellable__get_campaign",
-          "mcp__sellable__get_campaign_context",
-          "mcp__sellable__get_rows_minimal",
-          "mcp__sellable__save_rubrics"
-        ]
-      }
-    },
     {
       "id": "message-generation",
       "name": "post-find-leads-message-scout",
@@ -203,16 +10,17 @@
       "target": "generate-messages",
       "inputs": [
         "campaignId",
-        "campaignBrief",
-        "selected source state",
-        "selectedLeadListId",
         "workflowTableId",
-        "imported review-batch rows"
+        "concise brief summary",
+        "concise source summary/source-use rule",
+        "3-5 sample workflow-table rows",
+        "optional campaignName, selectedLeadListId, filter choice"
       ],
       "producesArtifacts": [
         "template recommendation",
         "token fill rules",
-        "rendered sample"
+        "one rendered good-fill sample",
+        "validation status"
       ],
       "optionalProducesArtifacts": [],
       "ownership": "message strategy, proof inventory, token rules, skeptical-prospect review, and selected winner only",
@@ -234,8 +42,8 @@
         "maxTurns": 10,
         "color": "magenta",
         "tools": [
-          "Read",
           "mcp__sellable__get_subskill_prompt",
+          "mcp__sellable__get_subskill_asset",
           "mcp__sellable__get_campaign",
           "mcp__sellable__get_campaign_context",
           "mcp__sellable__get_rows_minimal"

package/dist/tools/leads.js

@@ -660,12 +660,10 @@ function analyzeFilterChoiceSample(sampleRows) {
     const fitRatio = fitCount / sampleCount;
     const cleanupRatio = cleanupCount / sampleCount;
     const adjacentRatio = adjacentIndexes.length / sampleCount;
-    const maxCleanRiskCount = Math.max(2, Math.floor(sampleCount * 0.12));
-    const recommendation = fitRatio >= 0.75 &&
-        cleanupCount <= maxCleanRiskCount &&
-        adjacentRatio <= 0.3
+    const allReviewedRowsLookFit = fitCount === sampleCount && cleanupCount === 0;
+    const recommendation = allReviewedRowsLookFit && adjacentRatio <= 0.3
         ? "skip"
-        : fitRatio >= 0.6 && cleanupRatio <= 0.3
+        : fitRatio >= 0.75 && cleanupRatio <= 0.3
             ? "light-filter"
             : "add-filter";
     return {
@@ -697,17 +695,20 @@ function buildFilterChoiceWatchNarration({ sourceLeadCount, reviewRowCount, samp
         : "Sample rows were not available to inspect, so this is a manual filter decision.";
     const fitExamples = formatExamples("Fit examples:", assessment.strongExamples);
     const riskExamples = formatExamples("Cleanup examples:", assessment.riskExamples);
+    const lightFilterReason = cleanupCount > 0
+        ? `${cleanupCount} of ${assessment.sampleCount} need cleanup or manual review`
+        : `${assessment.adjacentCount} of ${assessment.sampleCount} look adjacent instead of clear target-role fits`;
     const headline = assessment.recommendation === "skip"
-        ? "Filtering may not be needed"
+        ? "Filters optional for clean sample"
         : assessment.recommendation === "light-filter"
             ? "I recommend light cleanup filters"
             : assessment.recommendation === "manual-review"
                 ? "Review filters or skip"
                 : "I recommend adding filters";
     const agentIntent = assessment.recommendation === "skip"
-        ? `Codex is not recommending filters because the sample already looks clean. ${fitExamples} Add filters only for a narrow exclusion.`
+        ? `Codex is not recommending filters because every reviewed row already looks like a target-role fit. ${fitExamples} Add filters only if the user wants an extra narrow exclusion.`
         : assessment.recommendation === "light-filter"
-            ? `Codex is recommending light filters because most rows fit, but ${cleanupCount} of ${assessment.sampleCount} look adjacent, unknown, or risky. ${riskExamples}`
+            ? `Codex is recommending light filters because the sample is strong but not perfectly clean: ${lightFilterReason}. ${riskExamples}`
             : assessment.recommendation === "manual-review"
                 ? "Codex could not inspect the review rows, so it is pausing for a manual filter decision instead of assuming filters are required."
                 : `Codex is recommending filters because ${cleanupCount} of ${assessment.sampleCount} sampled rows look adjacent, unknown, or risky before message review. ${riskExamples}`;