@sellable/mcp 0.1.129 → 0.1.130

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -13,7 +13,6 @@ allowed-tools:
   - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_source_scout_registry
   - mcp__sellable__get_post_find_leads_scout_registry
-  - mcp__sellable__get_message_prompt
   - mcp__sellable__get_active_workspace
   - mcp__sellable__list_senders
   - mcp__sellable__get_sender
@@ -71,10 +70,11 @@ Disk artifacts are optional debug/UAT diagnostics; normal customer runs should
 not create, link, or surface local draft files unless the user explicitly asks
 for them. Resume, gating, and handoff read campaign state first. The
 watchable campaign exists after the short brief; lead import is bounded to the
-first review batch. After that, the user chooses whether to use filters or skip,
-then Messages first shows Use Template and AI Generated. The Message Draft
-Builder may work in the background, but template review waits for the filter
-path and an explicit Use Template choice.
+first review batch. After that, the user chooses whether to use filters or skip.
+When filters are chosen, save rubrics, then pause before queueing enrichment or
+filtering: tell the user the fit rules are saved, the message template needs
+approval next, and enrichment/filtering will start after that approval. Use
+Template is the default message path; AI Generated is only an explicit opt-out.
 
 ## Opening Turn Contract
 
@@ -148,12 +148,13 @@ calls `get_post_find_leads_scout_registry`, then launches the returned
 filter-leads scout and message-generation scout together when real subagents are
 available and the current session exposes the returned names. Message
 generation is the provisional Message Draft Builder: it may start after the
-review batch exists, including while the user is on filter choice, but template
-review cannot start until the user answers filter choice and chooses Use
-Template in Messages. AI Generated is an explicit opt-out that cancels or
-ignores the background template draft. If the post-lead agents are absent, the
-main thread still orchestrates the same branches from the compact context with
-MCP tools/assets.
+review batch exists, including while the user is on filter choice, but workflow
+cell execution must wait. After rubrics are saved, do not queue enrichment,
+filtering, or Generate Message cells until the user approves the message
+template. AI Generated is an explicit opt-out that cancels or ignores the
+background template draft. If the post-lead agents are absent, the main thread
+still orchestrates the same branches from the compact context with MCP
+tools/assets.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
@@ -574,10 +575,11 @@ updates.
    watch link and see useful setup state immediately. Import only the first
    bounded review batch after the source is attached to the campaign; do not
    queue workflow cells, attach a sequence, or start until the filter choice is
-   resolved, Messages has shown Use Template / AI Generated, template/token
-   rules are approved when Use Template is chosen, rubrics are saved and the
-   bounded review-batch `enrichCellId` cells have been queued when filters are
-   enabled, and the approved message set is synced into the campaign brief.
+   resolved, rubrics are saved when filters are enabled, template/token rules
+   are approved on the default Use Template path, and the approved message set
+   is synced into the campaign brief. After rubrics save, pause and say the fit
+   rules are saved; approve the message template next; after approval, queue the
+   bounded review-batch `enrichCellId` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval.
    Do not ask the user to approve the brief before shell creation unless they

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

@@ -629,18 +629,19 @@ batch`, and a no-launch safety note. Do not leave the guide saying
   Fit Builder saves rubrics, move the watched browser to Filter Leads before
   waiting for message work to finish. Persist `currentStep:
 "apply-icp-rubric"` and `watchNarration.stage: "fit-message"`, then read the
-  bounded review batch with `get_rows_minimal`, queue only pending/error
-  `enrichCellId` values with `queue_cells`, and then wait for rubric results
-  with at least one passing row. Do not call `check_rubric` in the normal
-  create-campaign-v2 path. The next user-facing Messages screen must show mode
-  choice first: Use Template and AI Generated. Use Template is recommended. AI
-  Generated is an explicit opt-out that cancels or ignores the background
-  template draft and must not let late template output overwrite campaign
-  state. Product Generate Message cells should not run from the background
-  template path until template/token rules are approved. After message approval,
-  update the campaign brief with an Approved Message Template containing
-  `{{...}}` tokens and keep `enableICPFilters: true`; Generate Message detects
-  template mode from those tokens, not from `useMessagingTemplate`.
+  bounded review batch with `get_rows_minimal`, but do not queue workflow cells
+  yet. Tell the user the fit rules are saved, the message template needs
+  approval next, and enrichment/filtering will start after approval. Do not call
+  `check_rubric` in the normal create-campaign-v2 path. Use Template is the
+  default message path. AI Generated is an explicit opt-out that cancels or
+  ignores the background template draft and must not let late template output
+  overwrite campaign state. Product Generate Message cells should not run from
+  the background template path until template/token rules are approved. After
+  message approval, update the campaign brief with an Approved Message Template
+  containing `{{...}}` tokens and keep `enableICPFilters: true`; then queue only
+  pending/error `enrichCellId` values with `queue_cells` to start enrichment and
+  filtering. Generate Message detects template mode from those tokens, not from
+  `useMessagingTemplate`.
 - During pre-import validation, do not call `check_rubric`; use the lead-filter
   artifacts and only use campaign-backed scoring after Step 13 imports the
   15-lead test batch.