@sellable/install 0.1.196 → 0.1.197

package/bin/sellable-install.mjs

@@ -620,6 +620,9 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__select_campaign_cells",
   "mcp__sellable__queue_campaign_cells",
   "mcp__sellable__wait_for_campaign_processing",
+  "mcp__sellable__start_prepare_campaign_messages",
+  "mcp__sellable__get_prepare_campaign_messages_status",
+  "mcp__sellable__cancel_prepare_campaign_messages",
   "mcp__sellable__revise_message_template_and_rerun",
   "mcp__sellable__update_campaign_brief",
   "mcp__sellable__update_campaign",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.196",
+  "version": "0.1.197",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-ab-test.md

@@ -24,18 +24,27 @@ campaign-message approaches from the same source list.
 
 ## Opening Contract
 
-Start by identifying the source campaign, the one variable being tested, and
-the clean source lead origin. Then prepare the split and stop for review. The
-goal is two review-copy campaigns with clean split source lists, not a launched
+Start by identifying the campaign idea and the one variable being tested. A
+source campaign and clean source lead list are both optional: use an existing
+campaign when the user already has one, use a clean source lead list when leads
+are already available, or use only the idea by writing a campaign name and base
+brief for A. The tool creates A first, duplicates A into B, applies the B delta,
+and stops for review. The goal is two review-copy campaigns, not a launched
 campaign.
 
 ## Required Flow
 
-1. Confirm the source campaign ID or resolve it with `get_campaign`.
+1. Decide the source mode:
+   - Existing campaign mode: confirm the source campaign ID or resolve it with
+     `get_campaign`.
+   - Idea-first mode: write a proper campaign name and base campaign brief from
+     the user's idea. If the user also has leads, confirm the clean source
+     lead-list ID or use `load_csv_linkedin_leads` first.
 2. Confirm the A/B variable in plain language. Keep variant B as the explicit
    change and leave variant A as the control unless the user names an A change.
-3. Verify the campaign has a clean source lead list. A clean source list is a
-   lead-list table, not the generated campaign workflow table.
+3. If a source lead list is supplied, verify it is clean. A clean source list is
+   a lead-list or signal-lead-list table, not the generated campaign workflow
+   table.
 4. Call `prepare_campaign_ab_test` with `dryRun: true` first.
 5. Review split counts, duplicate/skipped counts, campaign names, and variant
    brief deltas with the user.
@@ -44,6 +53,18 @@ campaign.
 7. Return the A and B campaign IDs, split lead-list IDs, counts, and the
    explicit note that both campaigns are `not_started`.
 
+## Tool Inputs
+
+Use one of these shapes:
+
+- Existing campaign mode: pass `sourceCampaignId`, `variantName`,
+  `variantBriefDelta`, and any optional split or A-variant fields.
+- Idea-first mode: omit `sourceCampaignId`, pass `campaignName`,
+  `campaignBrief`, `variantName`, and `variantBriefDelta`. If a clean lead list
+  is available, also pass `sourceLeadListId`; otherwise leave it out. The tool
+  creates the A campaign, then duplicates A to create B and applies the B brief
+  delta.
+
 ## Anti-Patterns
 
 - Do not call `export_table_csv` from an enriched/generated campaign workflow
@@ -60,18 +81,19 @@ campaign.
 If the source campaign has no clean source lead list, or the source list is
 polluted with workflow/output columns, ask for the original CSV or clean source
 list. Use `load_csv_linkedin_leads`; it strips Sellable workflow columns if a
-contaminated CSV is supplied, then creates a clean lead list. After the clean
-source is confirmed, retry `prepare_campaign_ab_test`.
+contaminated CSV is supplied, then creates a clean lead list. If no clean source
+is available, continue in idea-first mode without `sourceLeadListId`.
 
 ## Output Contract
 
 Report:
 
-- source campaign ID
-- source lead-list ID
-- split strategy and counts
-- duplicate/skipped lead counts
-- A review campaign ID and split lead-list ID
-- B review campaign ID and split lead-list ID
+- source campaign ID, or note that the A campaign was created as the source
+  campaign when no source campaign was provided
+- source lead-list ID when supplied
+- split strategy and counts when a source lead list was supplied
+- duplicate/skipped lead counts when a source lead list was supplied
+- A review campaign ID and split lead-list ID when supplied
+- B review campaign ID and split lead-list ID when supplied
 - variant difference
 - `launchState: not_started` for both campaigns

package/skill-templates/create-campaign.md

@@ -46,6 +46,9 @@ allowed-tools:
   - mcp__sellable__select_campaign_cells
   - mcp__sellable__queue_campaign_cells
   - mcp__sellable__wait_for_campaign_processing
+  - mcp__sellable__start_prepare_campaign_messages
+  - mcp__sellable__get_prepare_campaign_messages_status
+  - mcp__sellable__cancel_prepare_campaign_messages
   - mcp__sellable__revise_message_template_and_rerun
   - mcp__sellable__update_campaign_brief
   - mcp__sellable__update_campaign
@@ -89,6 +92,18 @@ 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.
+After message approval, use `start_prepare_campaign_messages` for target-ready
+message preparation such as "prepare 100 messages, checking up to 300 rows".
+Treat `campaignId` as `CampaignOffer.id`, keep the default
+`approvalMode:"mark_ready"` unless the user explicitly asks to flip Approved
+cells, and poll `get_prepare_campaign_messages_status` for checked rows,
+prepared/approved count, target, row budget remaining, and stop reason. Low
+level selector/queue tools are diagnostics and recovery only for this lane. If
+the user asks to stop preparation, the target is wrong, or status shows the
+wrong campaign/table, call `cancel_prepare_campaign_messages`; otherwise do not
+cancel a healthy prepare run.
+Never call `start_campaign` from Prepare Messages; final launch remains a
+separate explicit user greenlight.
 Use Template is the default message path; AI Generated is only an explicit
 opt-out.
 
@@ -955,7 +970,8 @@ updates.
    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
-   after generated campaign-row messages are approved, `settings` for sender
+   after generated campaign-row messages are approved and the Prepare Messages
+   job has reported compact checked/prepared/stop status, `settings` for sender
    selection, `sequence` after sender attach, and `send` once the recommended
    sequence is attached. Do not advance the step backward.
 7. Keep `selectedLeadListId` as the source list and `workflowTableId` as the