@sellable/install 0.1.138 → 0.1.140

package/bin/sellable-install.mjs

@@ -817,8 +817,8 @@ Never call browser-opening tools, shell \`open\`, Computer Use, or in-app browse
 automation just because a watch link exists. Print the link in this shape:
 
 \`\`\`text
-Campaign shell is ready. You and I will keep building the campaign in this chat.
-You can watch it come together in real time here:
+Campaign shell is ready. We'll keep building the campaign in this chat.
+You can watch it being built in real time in the app here:
 
 Watch link: {watchUrl}
 
@@ -983,7 +983,7 @@ inferred strategy hardens:
 
 \`\`\`text
 Who should we target first?
-What offer should this campaign lead with?
+What should we pitch to prospects first?
 What is the strongest credibility signal we can lead with?
 How should we find prospects: find prospects for me, use a CSV of LinkedIn
 profiles, or use a CSV of company domains?
@@ -992,6 +992,9 @@ profiles, or use a CSV of company domains?
 The setup questions should use the confirmed company context so they do not feel
 generic. When you present a researched recommendation, introduce it as based on
 the research you just did and keep it editable.
+Do not render a \`## Campaign Identity\` brief section. Use
+\`## Sender and Company\` for the person/company context, because the person is
+sender context, not a customer-facing campaign identity concept.
 
 Before the identity gate, use this customer-facing shape:
 

package/package.json

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

package/skill-templates/create-campaign.md

@@ -309,8 +309,8 @@ 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:
 
 ```text
-Campaign shell is ready. You and I will keep building the campaign in this chat.
-You can watch it come together in real time here:
+Campaign shell is ready. We'll keep building the campaign in this chat.
+You can watch it being built in real time in the app here:
 
 Watch link: {watchUrl}
 
@@ -480,7 +480,7 @@ inferred strategy hardens:
 
 ```text
 Who should we target first?
-What offer should this campaign lead with?
+What should we pitch to prospects first?
 What is the strongest credibility signal we can lead with?
 How should we find prospects: find prospects for me, use a CSV of LinkedIn
 profiles, or use a CSV of company domains?
@@ -489,6 +489,9 @@ profiles, or use a CSV of company domains?
 The setup questions should use the confirmed company context so they do not feel
 generic. When you present a researched recommendation, introduce it as based on
 the research you just did and keep it editable.
+Do not render a `## Campaign Identity` brief section. Use
+`## Sender and Company` for the person/company context, because the person is
+sender context, not a customer-facing campaign identity concept.
 
 ### Sufficient Intake Bypass
 
@@ -676,18 +679,20 @@ updates.
 
        ```text
        You're in — {activeWorkspaceName} workspace, ready to roll.
-
-      What is your LinkedIn profile URL?
        ```
 
+     What is your LinkedIn profile URL?
+
+     ````
+
      - If `isReturningUser === false`, prepend ONE line confirming the new
-       workspace, then the locked Step 3 narration verbatim:
+     workspace, then the locked Step 3 narration verbatim:
 
-       ```text
-       You're set up — your {activeWorkspaceName} workspace is ready.
+     ```text
+     You're set up — your {activeWorkspaceName} workspace is ready.
 
-      What is your LinkedIn profile URL?
-       ```
+     What is your LinkedIn profile URL?
+     ````
 
      No other lines. No "all set", no "signed in", no other acknowledgement.