@sellable/install 0.1.113 → 0.1.115

package/bin/sellable-install.mjs

@@ -179,15 +179,11 @@ function printCreateCommandHint() {
   console.log("");
   printAgentBox("Using Claude Code?", "claude", [
     { label: "Campaign", command: "/sellable:create-campaign" },
-    { label: "Identity", command: "/sellable:interview" },
-    { label: "Voice", command: "/sellable:load-voice" },
   ]);
   console.log("");
   console.log("");
   printAgentBox("Using Codex?", "codex", [
     { label: "Campaign", command: "$sellable:create-campaign" },
-    { label: "Identity", command: "$sellable:interview" },
-    { label: "Voice", command: "$sellable:load-voice" },
   ]);
   console.log("");
   console.log(`   ${"─".repeat(63)}`);
@@ -646,9 +642,10 @@ data, compare sources by source volume, sampled ICP fit, activity/warmth
 signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
-Before any provider prompt, search, source scout, or signal-discovery call,
-show a short source-plan gate and ask for approval. This first approval
-authorizes scouting/search only. The gate should say:
+Before any provider prompt, search, source scout, or signal-discovery call, show
+one source-plan gate and ask for approval. The plan must be visible before the
+question, and this first approval authorizes scouting/search only. The gate
+should say:
 
 - given this campaign, the viable source options
 - the recommended first lane
@@ -665,6 +662,10 @@ why. Do not call \`search_signals\`, \`search_sales_nav\`, \`search_prospeo\`,
 \`fetch_post_engagers\`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
+If the user already answered a provider approval such as "Approve Prospeo plan",
+that answer satisfies the source-plan gate. Persist the approved provider and
+run the scouting/search next; do not ask a second source-plan approval question.
+
 For hiring-led campaigns, do not default to Sales Nav just because the target is
 a role search. Prospeo is the primary lane when the brief asks for companies
 actively hiring specific roles, open-role signals, account/contact coverage, or
@@ -990,29 +991,32 @@ updates.
    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
+   workflow cells, attach a sequence, or start until saved filters and the
+   message template/token rules are approved. When filters are chosen, 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; 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
-   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.
+   After rubrics save, keep Filter Rules visible for approval; after approval,
+   move to Filter Leads and wait there for the background message recommendation.
+   If filters are skipped, move to Messages/message review. Queue the bounded
+   review-batch \`enrichCellId\` cells only after message approval. Move to
+   Messages only after at least one review row passes and one generated message
+   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
+   \`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,
+   \`filter-choice\` after the review batch, \`create-icp-rubric\` as soon
+   as filters are chosen and while saved filters await approval,
+   \`apply-icp-rubric\` after filter approval and message approval while bounded
+   enrichment/filter scoring runs, \`validate-sample\` only as a recovery/legacy
+   observation state,
+   \`auto-execute-messaging\` after at least one row passes and review-batch
+   messages are being generated or reviewed, \`awaiting-user-greenlight\` only
+   after generated review-batch messages are approved, \`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
    campaign table. Do not use disk files as the post-mint source of truth.
 8. Do not ask the user to run another command.
@@ -2211,8 +2215,6 @@ function printNextSteps(installedHosts, authReused) {
   if (hasClaude) {
     printAgentBox("Using Claude Code?", "claude", [
       { label: "Campaign", command: "/sellable:create-campaign" },
-      { label: "Identity", command: "/sellable:interview" },
-      { label: "Voice", command: "/sellable:load-voice" },
     ]);
     console.log("");
     console.log("");
@@ -2220,8 +2222,6 @@ function printNextSteps(installedHosts, authReused) {
   if (hasCodex) {
     printAgentBox("Using Codex?", "codex", [
       { label: "Campaign", command: "$sellable:create-campaign" },
-      { label: "Identity", command: "$sellable:interview" },
-      { label: "Voice", command: "$sellable:load-voice" },
     ]);
     console.log("");
   }

package/package.json

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

package/skill-templates/create-campaign.md

@@ -72,10 +72,10 @@ 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.
-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.
+When filters are chosen, save rubrics, get filter approval, then wait for
+message-template approval before enrichment/filtering or Generate Message cells.
+Use Template is the default message path; AI Generated is only an explicit
+opt-out.
 
 ## Opening Turn Contract
 
@@ -124,9 +124,10 @@ data, compare sources by source volume, sampled ICP fit, activity/warmth
 signals, cleanup risk, and confidence basis. If a user asks for a forecast,
 label it explicitly as not estimated from this run.
 
-Before any provider prompt, search, source scout, or signal-discovery call,
-show a short source-plan gate and ask for approval. This first approval
-authorizes scouting/search only. The gate should say:
+Before any provider prompt, search, source scout, or signal-discovery call, show
+one source-plan gate and ask for approval. The plan must be visible before the
+question, and this first approval authorizes scouting/search only. The gate
+should say:
 
 - given this campaign, the viable source options
 - the recommended first lane
@@ -143,6 +144,10 @@ why. Do not call `search_signals`, `search_sales_nav`, `search_prospeo`,
 `fetch_post_engagers`, or provider-scoped subagents until the user approves this
 source plan or explicitly chooses a different source.
 
+If the user already answered a provider approval such as "Approve Prospeo plan",
+that answer satisfies the source-plan gate. Persist the approved provider and
+run the scouting/search next; do not ask a second source-plan approval question.
+
 For hiring-led campaigns, do not default to Sales Nav just because the target is
 a role search. Prospeo is the primary lane when the brief asks for companies
 actively hiring specific roles, open-role signals, account/contact coverage, or
@@ -222,12 +227,13 @@ 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.
+filter-leads scout, move to Filter Rules, save rubrics, then ask for filter
+approval. After approval, keep the browser on Filter Leads while the message
+recommendation is reviewed. If the user skips filters, move to Messages/message
+review. Enrichment/filtering and Generate Message cells wait for message
+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 compact MCP context.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
@@ -649,23 +655,16 @@ 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 the 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
+   queue workflow cells, attach a sequence, or start until saved filters and the
+   message template/token rules are approved. When filters are chosen, 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; 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.
+   After rubrics save, keep Filter Rules visible for approval; after approval,
+   move to Filter Leads and wait there for the background message recommendation.
+   If filters are skipped, move to Messages/message review. Queue the bounded
+   review-batch `enrichCellId` cells only after message approval. Move to
+   Messages only after at least one review row passes and one generated message
+   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
@@ -673,9 +672,10 @@ updates.
    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,
    `filter-choice` after the review batch, `create-icp-rubric` as soon
-   as filters are approved, `apply-icp-rubric` after rubrics save and while
-   waiting for message-template approval, `validate-sample` while the approved
-   template unlocks bounded enrichment/filter scoring on Filter Leads,
+   as filters are chosen and while saved filters await approval,
+   `apply-icp-rubric` after filter approval and message approval while bounded
+   enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
+   observation state,
    `auto-execute-messaging` after at least one row passes and review-batch
    messages are being generated or reviewed, `awaiting-user-greenlight` only
    after generated review-batch messages are approved, `settings` for sender