@sellable/install 0.1.144 → 0.1.146

package/bin/sellable-install.mjs

@@ -794,11 +794,15 @@ which posts are being sampled in the watched app. The watch guide should say
 that we are checking people from these posts to confirm the right people are
 actually engaging and the source is viable.
 
-Every approval gate must include live campaign access after the readable inline
-content. Show a \`Watch link:\` line once the campaign shell exists. In normal
-customer runs, do not show local draft filenames or filesystem paths unless the
-user asks for debug artifacts. The link is for deeper inspection; never use it
-as a substitute for showing the content in chat.
+Only the first brief approval handoff should include live campaign access after
+the readable inline content. Show a short \`Watch link:\` line once, immediately
+after shell creation and before brief approval. Later approval gates should
+describe what the already-open campaign app is showing and rely on
+currentStep/watchNarration; do not print the URL again unless the user asks or a
+recovery path must replace a missing/broken link. In normal customer runs, do
+not show local draft filenames or filesystem paths unless the user asks for
+debug artifacts. The link is for deeper inspection; never use it as a substitute
+for showing the content in chat.
 
 Never mention MCP namespaces, prompt chunking, plugin cache paths, missing
 linked skill versions, runbooks, or local skill files in normal customer-facing
@@ -1111,7 +1115,8 @@ 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, keep Filter Rules visible for approval; after approval,
-   move to Filter Leads and wait there for the background message recommendation.
+   move to Filter Leads and show \`Filters saved + waiting for message approval\`
+   until the template is approved.
    If filters are skipped, move to Messages/message review. Queue the bounded
    campaign-table execution-slice \`enrichCellId\` cells only after message approval. Move to
    Messages only after at least one review row passes and one generated message
@@ -1124,8 +1129,8 @@ updates.
    the brief, \`pick-provider\` or the selected provider step while sourcing,
    \`filter-choice\` after source rows are copied into the campaign table, \`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
+   \`apply-icp-rubric\` after filter approval while message approval is pending,
+   and after 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 initial campaign-row
    messages are being generated or reviewed, \`awaiting-user-greenlight\` only
@@ -1344,10 +1349,12 @@ approval should show who we are targeting, why they should care, the offer/CTA,
 proof, lead source hypothesis, message angle, risks/assumptions, and what
 happens after approval.
 
-Every approval should also give the user a way to inspect the live campaign.
-After the readable inline content, include a \`Watch link:\` line when a
-campaign shell exists. Local artifacts are optional debug/UAT diagnostics only;
-do not surface file paths or local draft filenames in normal customer runs.
+Only the first brief approval handoff should print the campaign watch URL. After
+that, every approval should say what the already-open app is showing, but must
+not include another \`Watch link:\` line unless the user explicitly asks for the
+link again or a recovery path needs to replace a broken/missing URL. Local
+artifacts are optional debug/UAT diagnostics only; do not surface file paths or
+local draft filenames in normal customer runs.
 
 This applies especially to message approvals. Never ask someone to approve a
 message they cannot see. Show the subject, tokenized template, a filled sample

package/package.json

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

package/skill-templates/create-campaign.md

@@ -76,6 +76,8 @@ 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.
+After filter approval, Filter Leads should show `Filters saved + waiting for
+message approval` until the template is approved.
 Use Template is the default message path; AI Generated is only an explicit
 opt-out.
 
@@ -273,10 +275,11 @@ 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 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
+approval. After approval, move to Filter Leads and show `Filters saved + waiting
+for message approval` 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.
 
@@ -284,12 +287,16 @@ Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
 sourcing terms into plain language.
 
-Every approval gate must include live campaign access after the readable inline
-content. Show a short `Watch link:` line once the campaign shell exists. In
-normal customer runs, do not show `Open artifact:` lines, raw filesystem paths,
-or local draft filenames. Local artifacts are debug/UAT-only unless the user asks
-for them. The link is for deeper inspection; never use it as a substitute for
-showing the content in chat.
+Only the first brief approval handoff should include live campaign access after
+the readable inline content. Show a short `Watch link:` line once, immediately
+after shell creation and before brief approval. Later approval gates should
+describe what the already-open campaign app is showing and rely on
+currentStep/watchNarration; do not print the URL again unless the user asks or a
+recovery path must replace a missing/broken link. In normal customer runs, do
+not show `Open artifact:` lines, raw filesystem paths, or local draft filenames.
+Local artifacts are debug/UAT-only unless the user asks for them. The link is
+for deeper inspection; never use it as a substitute for showing the content in
+chat.
 
 Never mention MCP namespaces, prompt chunking, plugin cache paths, missing
 linked skill versions, runbooks, npm/package details, repo-local files, VPS or
@@ -750,7 +757,8 @@ 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, keep Filter Rules visible for approval; after approval,
-   move to Filter Leads and wait there for the background message recommendation.
+   move to Filter Leads and show `Filters saved + waiting for message approval`
+   until the template is approved.
    If filters are skipped, move to Messages/message review. Queue the bounded
    campaign-table execution-slice `enrichCellId` cells only after message approval. Move to
    Messages only after at least one review row passes and one generated message
@@ -763,8 +771,8 @@ updates.
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after source rows are copied into the campaign table, `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
+   `apply-icp-rubric` after filter approval while message approval is pending,
+   and after 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 initial campaign-row
    messages are being generated or reviewed, `awaiting-user-greenlight` only