@sellable/install 0.1.145 → 0.1.147

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
@@ -807,14 +811,18 @@ copy.
 ## Codex Watch Link Handoff
 
 When a campaign tool returns \`watchUrl\`, treat it as a user-opened app link, not
-as permission to drive the browser. A valid handoff link must be a direct
-\`/campaign-builder/{campaignId}?mode=claude|codex\` URL with the auth token and
-workspace routing needed for auto-login. \`create_campaign.watchUrl\`,
+as permission to drive the browser. A valid first handoff link must be the exact
+\`create_campaign.watchUrl\` value: a direct
+\`/campaign-builder/{campaignId}?mode=claude|codex\` URL with \`workspaceId\` and
+\`token\` query parameters for auto-login. \`create_campaign.watchUrl\`,
 \`create_campaign({ campaignId }).watchUrl\`, and \`get_campaign.watchUrl\` are all
-acceptable only when they return that direct campaign-builder shape.
+acceptable only when they return that direct campaign-builder shape. Never
+derive, shorten, reconstruct, or print a bare \`/campaign-builder/{campaignId}\`
+URL.
 
 Never call browser-opening tools, shell \`open\`, Computer Use, or in-app browser
-automation just because a watch link exists. Print the link in this shape:
+automation just because a watch link exists. Print the first watch link exactly
+once, directly before the brief approval question, in this shape:
 
 \`\`\`text
 Campaign shell is ready. We'll keep building the campaign in this chat.
@@ -831,6 +839,9 @@ the link lands on auth, 404, permission, blank, or a visible error state, recove
 a fresh watch link once with \`create_campaign({ campaignId })\` or \`get_campaign\`
 and print that link. Do not claim the browser was opened, inspected, or
 synchronized.
+Do not print another \`Watch link:\` line during source/provider selection or
+normal approval turns unless the user explicitly asks for the link or you are
+recovering a missing/broken URL.
 
 After every \`update_campaign({ campaignId, currentStep })\`, use
 \`get_campaign_navigation_state\` when available as a compact orientation check:
@@ -1007,13 +1018,15 @@ recommendation; you can replace it with your current offer."
 Before the identity gate, use this customer-facing shape:
 
 \`\`\`text
-I’m ready to build the campaign in {workspace}.
+You're in {workspace}.
 
-First I’ll research the person/company this campaign is for. I’ll use that
-context to recommend a target, offer, proof, and lead source, then you can
-correct anything stale before I build from it.
+Excited to help you launch your LinkedIn outbound campaign.
 
-Then I’ll turn that into a campaign brief for you to approve before anything is created.
+We're at setup: first I'll use your LinkedIn profile to understand the company,
+then I'll draft the campaign brief, help choose where to find buyers, review
+messages, and wait for final launch approval.
+
+What's your LinkedIn profile URL or handle?
 \`\`\`
 
 Do not silently ask Codex intake or approval questions as plain chat when
@@ -1345,10 +1358,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.147",
   "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
@@ -302,14 +306,18 @@ copy.
 ## Codex Watch Link Handoff
 
 When a campaign tool returns `watchUrl`, treat it as a user-opened app link, not
-as permission to drive the browser. A valid handoff link must be a direct
-`/campaign-builder/{campaignId}?mode=claude|codex` URL with the auth token and
-workspace routing needed for auto-login. `create_campaign.watchUrl`,
+as permission to drive the browser. A valid first handoff link must be the exact
+`create_campaign.watchUrl` value: a direct
+`/campaign-builder/{campaignId}?mode=claude|codex` URL with `workspaceId` and
+`token` query parameters for auto-login. `create_campaign.watchUrl`,
 `create_campaign({ campaignId }).watchUrl`, and `get_campaign.watchUrl` are all
-acceptable only when they return that direct campaign-builder shape.
+acceptable only when they return that direct campaign-builder shape. Never
+derive, shorten, reconstruct, or print a bare `/campaign-builder/{campaignId}`
+URL.
 
 Never call browser-opening tools, shell `open`, Computer Use, or in-app browser
-automation just because a watch link exists. Print the link in this shape:
+automation just because a watch link exists. Print the first watch link exactly
+once, directly before the brief approval question, in this shape:
 
 ```text
 Campaign shell is ready. We'll keep building the campaign in this chat.
@@ -331,6 +339,9 @@ Never print a placeholder watch link such as "Open campaign" or "link will
 update once the shell is created." If the shell is not created yet, call
 `create_campaign` first. If `create_campaign` does not return `watchUrl`, stop
 and surface the missing watch-link error before lead sourcing.
+Do not print another `Watch link:` line during source/provider selection or
+normal approval turns unless the user explicitly asks for the link or you are
+recovering a missing/broken URL.
 
 After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
@@ -552,14 +563,15 @@ the run. Treat YOLO as `interactionMode: "autonomous"` plus an intake policy:
 Before the identity gate, use this customer-facing shape:
 
 ```text
-I’m ready to build the campaign in {workspace}.
+You're in {workspace}.
 
-First I’ll research the person/company this campaign is for. I’ll use that
-context to recommend a target, offer, proof, and lead source, then you can
-correct anything stale before I build from it.
+Excited to help you launch your LinkedIn outbound campaign.
 
-Then I’ll turn that into a campaign brief for you to approve before any leads
-are sourced.
+We're at setup: first I'll use your LinkedIn profile to understand the company,
+then I'll draft the campaign brief, help choose where to find buyers, review
+messages, and wait for final launch approval.
+
+What's your LinkedIn profile URL or handle?
 ```
 
 Do not silently ask Codex intake or approval questions as plain chat when
@@ -684,26 +696,27 @@ updates.
      been written. Your IMMEDIATE next visible message branches on
      `isReturningUser` from the tool result:
 
-     - If `isReturningUser === true`, prepend ONE line acknowledging the
-       reused workspace, then the locked Step 3 narration verbatim
-       (substituting `activeWorkspaceName` exactly):
+     - If `isReturningUser === true`, use `activeWorkspaceName` when present,
+       otherwise `activeWorkspaceId`, as `{workspaceLabel}`:
 
        ```text
-       You're in — {activeWorkspaceName} workspace, ready to roll.
-       ```
+       You're in {workspaceLabel}.
 
-     What is your LinkedIn profile URL or handle?
+       Excited to help you launch your LinkedIn outbound campaign. We're at setup: first I'll use your LinkedIn profile to understand the company, then I'll draft the campaign brief, help choose where to find buyers, review messages, and wait for final launch approval.
 
-     ````
+       What's your LinkedIn profile URL or handle?
+       ```
 
-     - If `isReturningUser === false`, prepend ONE line confirming the new
-     workspace, then the locked Step 3 narration verbatim:
+     - If `isReturningUser === false`, use `activeWorkspaceName` when present,
+       otherwise `activeWorkspaceId`, as `{workspaceLabel}`:
 
-     ```text
-     You're set up — your {activeWorkspaceName} workspace is ready.
+       ```text
+       You're set up in {workspaceLabel}.
+
+       Excited to help you launch your LinkedIn outbound campaign. We're at setup: first I'll use your LinkedIn profile to understand the company, then I'll draft the campaign brief, help choose where to find buyers, review messages, and wait for final launch approval.
 
-     What is your LinkedIn profile URL or handle?
-     ````
+       What's your LinkedIn profile URL or handle?
+       ```
 
      No other lines. No "all set", no "signed in", no other acknowledgement.