@sellable/install 0.1.199 → 0.1.201

package/bin/sellable-install.mjs

@@ -31,7 +31,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.41";
+const CODEX_PLUGIN_VERSION = "0.1.42";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -65,6 +65,8 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.37",
   "0.1.38",
   "0.1.39",
+  "0.1.40",
+  "0.1.41",
 ];
 const INSTALL_PACKAGE_SPEC =
   process.env.SELLABLE_INSTALL_PACKAGE_SPEC || "@sellable/install@latest";
@@ -620,9 +622,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__start_campaign_message_preparation",
+  "mcp__sellable__get_campaign_message_preparation_status",
+  "mcp__sellable__cancel_campaign_message_preparation",
   "mcp__sellable__revise_message_template_and_rerun",
   "mcp__sellable__update_campaign_brief",
   "mcp__sellable__update_campaign",
@@ -651,6 +653,13 @@ function allowedToolsYaml(tools) {
   return tools.map((tool) => `  - ${tool}`).join("\n");
 }
 
+function yamlString(value) {
+  return JSON.stringify(String(value));
+}
+
+const FOUNDATION_SKILL_DESCRIPTION =
+  "Build or update durable founder/company memory: voice, values, proof, stories, positioning, and writing rules.";
+
 function codexSkillOpenAiYaml(displayName, description) {
   return `interface:
   display_name: "${displayName.replaceAll('"', '\\"')}"
@@ -1238,7 +1247,7 @@ Use \`prepare_campaign_ab_test\` to create clean A/B split lead lists and review
 function genericSellableSkillMd({ name, title, description }) {
   return `---
 name: ${name}
-description: ${description}
+description: ${yamlString(description)}
 allowed-tools:
   - mcp__sellable__get_auth_status
   - mcp__sellable__get_subskill_prompt
@@ -1277,7 +1286,7 @@ If subskill lookup fails, use \`mcp__sellable__search_subskill_prompts({ query:
 function foundationSkillMd() {
   return `---
 name: foundation
-description: Build or update durable founder/company memory: voice, values, proof, stories, positioning, and writing rules.
+description: ${yamlString(FOUNDATION_SKILL_DESCRIPTION)}
 allowed-tools:
   - mcp__sellable__get_subskill_prompt
   - mcp__sellable__get_subskill_asset

package/package.json

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

package/skill-templates/create-campaign.md

@@ -46,9 +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__start_campaign_message_preparation
+  - mcp__sellable__get_campaign_message_preparation_status
+  - mcp__sellable__cancel_campaign_message_preparation
   - mcp__sellable__revise_message_template_and_rerun
   - mcp__sellable__update_campaign_brief
   - mcp__sellable__update_campaign
@@ -90,20 +90,35 @@ 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.
+Filter work stays in the parent thread and must inspect visible campaign rows
+with `get_rows_minimal` / `get_rows` before drafting and saving rubrics; use at
+most one direct `enrich_with_prospeo` sample when row evidence is too thin.
 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.
+The default path stays the existing first campaign-table execution slice:
+review the normal `reviewBatchLimit:15`, approve reviewed draft rows, then move
+to Settings/sequence/final greenlight. Only call
+`start_campaign_message_preparation` when the user explicitly asks for more
+prepared messages or a send count. If the user says "prepare/generate X
+messages", set `targetPreparedMessages:X`, omit `maxRowsToCheck`, and keep
+`approvalMode:"mark_ready"`. The backend calibrates on at least 100 rows,
+estimates the row budget from observed rubric/pass yield, caps
+`maxRowsToCheck` at 2500, then adapts later batches up to 250 rows while
+recalculating yield. Poll
+`get_campaign_message_preparation_status` for preparation-job status: checked
+rows, passed/prepared/approved count, target, estimated row budget remaining,
+and stop reason. If the user says "approve X messages", use
+`approvalMode:"approve"` but still do not launch. If the user says "schedule X
+sends", use `approvalMode:"approve"` to approve exactly the bounded X-message
+cohort during preparation, then continue through sender, sequence, and final
+launch greenlight; the launch path must verify that bounded cohort and must not
+broad approve-all.
+Treat `campaignId` as `CampaignOffer.id`. 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_campaign_message_preparation`; otherwise do not cancel a healthy prepare
+run. Never call `start_campaign` from message preparation; final launch remains
+a separate explicit user greenlight.
 Use Template is the default message path; AI Generated is only an explicit
 opt-out.
 
@@ -470,14 +485,14 @@ automation just because a watch link exists. If `create_campaign` returns
 `watchHandoff.markdown`, print that exact value once, directly before the brief
 approval question. It will use the URL mode to say Codex or Claude Code:
 
-````markdown
+```markdown
 > **WATCH CODEX BUILD THE CAMPAIGN LIVE**
 >
 > [Open live campaign builder]({watchUrl})
 >
 > Keep this chat open. I'll ask approval questions here before making decisions
 > that need your judgment.
-````
+```
 
 The rendered callout is intentional: rendered chat clients highlight the
 headline, link, and note without treating it as a code block, and plain terminals
@@ -959,7 +974,7 @@ updates.
    is ready.
    Do not ask the user to approve the brief before shell creation unless they
    explicitly requested a no-write draft; the shell itself is the review surface.
-6. The main thread owns watch navigation. Call
+7. The main thread owns watch navigation. Call
    `mcp__sellable__update_campaign({ campaignId, currentStep })` before major
    visible work so the user can watch progress in the app: `create-offer` for
    the brief, `pick-provider` or the selected provider step while sourcing,
@@ -974,9 +989,9 @@ updates.
    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
+8. Keep `selectedLeadListId` as the source list and `workflowTableId` as the
    campaign table. Do not use disk files as the post-mint source of truth.
-8. Do not ask the user to run another command.
+9. Do not ask the user to run another command.
 
 ## Fallback