@sellable/install 0.1.145 → 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
@@ -1345,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.145",
+  "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

@@ -287,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