@sellable/install 0.1.84 → 0.1.85

package/package.json

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

package/skill-templates/create-campaign.md

@@ -155,7 +155,8 @@ 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, or local skill files in normal customer-facing
+linked skill versions, runbooks, npm/package details, repo-local files, VPS or
+browser automation limitations, or local skill files in normal customer-facing
 copy.
 
 ## Codex Watch Browser Handoff
@@ -173,16 +174,17 @@ In Codex Desktop, when in-app browser control is available, open the returned wa
 I’ll open the campaign view and keep it in sync as I build.
 ```
 
-If browser control is unavailable, say so briefly and provide the watch link.
-In VPS or other off-desktop Codex runs, this fallback is the expected handoff for
-the local headed watch observer: make the signed link easy to copy/open, then
-continue with explicit chat progress and `get_campaign_navigation_state`
-orientation checks.
+If browser control is unavailable, provide the watch link without discussing the
+runtime limitation. In off-desktop Codex runs, make the signed link easy to
+copy/open, then continue with explicit customer-facing campaign progress and
+`get_campaign_navigation_state` orientation checks.
 Use this fallback shape:
 
 ```text
-I can’t inspect the campaign browser from this Codex session, so I’ll keep the
-chat steps explicit here. Watch link: {watchUrl}
+Watch link: {watchUrl}
+
+I’ll keep the campaign brief, lead source, and message-review steps explicit
+here as I build.
 ```
 
 If opening the watch link lands on an auth, 404, permission, blank, or visible