@sellable/install 0.1.110 → 0.1.111

package/bin/sellable-install.mjs

@@ -965,23 +965,29 @@ updates.
 5. Create the campaign shell early with the v1 brief so the user can open the
    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 filter choice is
-   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. When filters are approved, immediately
+   load post-lead registries/prompts before asking add filters vs skip filters.
+   Once the user answers, launch the message scout from the same campaign/table
+   basis. If filters are approved, also launch the filter scout. Do not queue
+   workflow cells, attach a sequence, or start until filter choice is 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. When filters are approved, immediately
    call \`mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })\`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, move the watched app to \`apply-icp-rubric\` / Filter
-   Leads 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. AI Generated uses the
-   product's AI-generated path and cancels or ignores the background template
-   draft.
+   Leads and say the fit rules are saved; the background message scout is
+   preparing the message recommendation and approval comes next while the
+   browser stays on Filter Leads. If filters are skipped, move to
+   Messages/message review and wait for message approval there. After approval,
+   queue the bounded review-batch \`enrichCellId\` cells to kick off
+   enrichment/filtering.
+   Product Generate Message cells must not run before that template/token
+   approval. AI Generated uses the product's AI-generated path and skips the
+   template path.
 6. The main thread owns watch navigation: use \`filter-choice\` after the review
-   review batch, \`create-icp-rubric\` as soon as filters are approved,
-   \`apply-icp-rubric\` after rubrics save, \`messages\` for the Use Template / AI Generated mode choice,
+   batch, \`create-icp-rubric\` as soon as filters are approved,
+   \`apply-icp-rubric\` after rubrics save on the filter path, \`messages\` for
+   skipped filters and message-template review,
    \`auto-execute-messaging\` for approved message work or the product's
    AI-generated path, and \`awaiting-user-greenlight\` for the final handoff.
    \`validate-sample\` is recovery/legacy only if reached.

package/package.json

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

package/skill-templates/create-campaign.md

@@ -193,16 +193,16 @@ that we are pulling sample engagers from these posts to confirm the ICP is
 actually engaging and the source is viable.
 
 After the bounded review batch exists, use the same registry pattern for
-post-lead work. The create-campaign-v2 subskill calls
-`get_post_find_leads_scout_registry`, then launches the returned
-message-generation scout immediately when real subagents are available and the
-current session exposes the returned name. If the user chooses filters, launch
-the filter-leads scout then and join it with the already-running or completed
-message draft before message review. Workflow cell execution still waits for
-filter and template approval. 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.
+post-lead work, but do not load that registry or any deep filter/message prompt
+before the filter-choice question. After `confirm_lead_list`, ask add filters
+vs skip filters immediately. Once the user answers, launch the message scout
+from the same campaign/table basis. If the user chooses filters, also launch the
+filter-leads scout, move to Filter Rules, save rubrics, then keep the browser on
+Filter Leads while the message recommendation is reviewed. If the user skips
+filters, move to Messages/message review. Workflow cell execution still waits
+for filter and template approval. AI Generated is an explicit opt-out from the
+template path. 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
@@ -631,13 +631,16 @@ updates.
    call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, move the watched app to `apply-icp-rubric` / Filter
-   Leads and say the fit rules are saved; approve the message template next
-   while the browser stays on Filter Leads. After approval, save the template
-   to the campaign brief, then queue the bounded review-batch `enrichCellId`
-   cells to kick off enrichment/filtering. Move to Messages only after at
-   least one review row passes and Generate Message cells are running or ready.
-   Product Generate Message cells must not run from the background template
-   path before that template/token approval.
+   Leads and say the fit rules are saved; the background message scout is
+   preparing the message recommendation and approval comes next while the
+   browser stays on Filter Leads. If filters are skipped, move the watched app to
+   Messages/message review and wait for message approval there. After approval,
+   save the template to the campaign brief, then queue the bounded review-batch
+   `enrichCellId` cells to kick off enrichment/filtering. Move to Messages only
+   after at least one review row passes and Generate Message cells are running or
+   ready.
+   Product Generate Message cells must not run before that template/token
+   approval.
    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