@sellable/mcp 0.1.114 → 0.1.116

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.114",
+  "version": "0.1.116",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign/SKILL.md

@@ -165,35 +165,56 @@ 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 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`,
-`create_campaign({ campaignId }).watchUrl`, and `get_campaign.watchUrl` are all
-acceptable only when they return that direct campaign-builder shape.
-
-Never call browser-opening tools, shell `open`, Computer Use, or in-app browser
-automation just because a watch link exists. Print the link and tell the user to
-Command-Enter/click it when they want to watch in the app. Use this shape:
+## Watch Link Handoff
+
+When a campaign tool returns `watchUrl`, treat it as a user-opened watch link.
+A valid handoff link must be a safe direct
+`/campaign-builder/{campaignId}?mode=claude|codex|watch` URL.
+`create_campaign.watchUrl`, `create_campaign({ campaignId }).watchUrl`, and
+`get_campaign.watchUrl` are all acceptable only when they return that direct
+campaign-builder shape, with `workspaceId` used only as a safe routing hint when
+needed.
+
+Do not claim Sellable can force every host to open links in a specific browser.
+The host controls link-click behavior. Do not call Chrome, browser automation,
+shell `open`, Computer Use, or in-app browser-control tools just because a
+watch link exists.
+
+- In Codex Desktop, clicking a URL can open the Codex in-app browser, but that
+  browser is only reliable for unauthenticated/public pages. Sellable campaign
+  watch pages may need a signed-in session. Tell the user to click the link
+  first; if it lands on sign-up/auth, they should open the same link in their
+  regular browser to watch real-time updates.
+- In Claude Code, provide the link and direct the user to open it in their
+  browser. If their Claude Code setup opens links in an in-app/preview browser,
+  that is fine, but do not attempt to open Chrome for them.
+
+Make the direct watch 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
-Watch link: {watchUrl}
+Watch link: [Open campaign]({watchUrl})
 
-Command-Enter or click that link to watch the campaign in Sellable. I’ll keep
-the brief, lead source, and message-review steps explicit here as I build.
+Click that link to watch the campaign. If it opens in an in-app browser and asks
+you to sign in, open the same link in your regular browser so you can watch
+real-time updates from your signed-in session. I’ll keep the brief, lead source,
+and message-review steps explicit here as I build.
 ```
 
-The watch link should auto-login through the token in the URL. If the user says
-the link lands on auth, 404, permission, blank, or a visible error state, recover
-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.
+If the user reports that the watch link lands on auth, 404, permission, blank,
+or an error state, recover a fresh watch link once with
+`create_campaign({ campaignId })` or `get_campaign`, then print the recovered
+link. Do not claim the browser was opened, inspected, or synchronized.
+
+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.
 
 After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
-match the saved campaign state to the expected watch-link step, explain the
+match the expected watch-link step to the saved campaign state, explain the
 current state in one sentence, and only then continue. Sender selection belongs
 at Settings after message approval and 10-row validation. After message
 validation, use Settings to help the user connect or select a LinkedIn sender.
@@ -565,6 +586,8 @@ updates.
    `message-validation.md` proves the message-review safety-gate workflow ran,
    `message-review.md` approves the template, rubrics are saved, and the
    approved message set is synced into the campaign brief.
+   Do not ask the user to approve the brief before shell creation unless they
+   explicitly requested a no-write draft; the shell itself is the review surface.
 6. The main thread owns watch navigation. Call
    `mcp__sellable__update_campaign({ campaignId, currentStep })` before major
    visible work so the user can watch progress in the app: `create-offer` for

package/skills/create-campaign-v2/references/watch-link-handoff.md

@@ -38,7 +38,11 @@ You can watch the lead source, filters, and messages fill in from here.
 
 No leads import and nothing sends yet.
 
-Watch link: {watchUrl}
+Watch link: [Open campaign]({watchUrl})
+
+Click that link to watch the campaign. If it opens in an in-app browser and asks
+you to sign in, open the same link in your regular browser so you can watch
+real-time updates from your signed-in session.
 
 Command-Enter or click that link to watch it in Sellable.
 
@@ -58,11 +62,33 @@ clear:
 - the brief is already visible in the campaign
 - import, sequence, and start are still blocked
 
+## Browser Choice
+
+Do not claim Sellable can force the user's host to open links in a specific
+browser. The host controls link-click behavior.
+Do not call Chrome, browser automation, shell `open`, Computer Use, or in-app
+browser-control tools just because a watch link exists.
+
+- Codex Desktop URL clicks can open the Codex in-app browser, but that browser
+  is only reliable for public or unauthenticated pages. Sellable campaign watch
+  pages depend on a signed-in session, so if the in-app browser lands on
+  sign-up/auth, tell the user to open the same link in their regular browser to
+  watch real-time updates.
+- Claude Code should provide the link and direct the user to open it in their
+  browser. If the user's Claude Code setup opens links in an in-app/preview
+  browser, that is fine, but do not attempt to open Chrome for them.
+
+Surface the link as a normal Markdown link and continue with explicit progress
+updates in chat.
+
 If shell creation fails or the response is missing `watchUrl`, stop and surface
 the error. Do not continue into campaignless source scouting in the active
 shell-first flow.
 If a legacy atomic-mint response is missing `watchUrl`, it is not a silent skip.
 Stop before `save_rubrics` and recover the missing watch URL first.
+Never print a placeholder link such as "Open campaign" or "link will update
+once the shell is created." In the active shell-first flow, the first visible
+watch link must be the real `watchUrl` returned by `create_campaign`.
 
 ## Step Orientation
 

package/skills/research/config.json

@@ -1,9 +0,0 @@
-{
-  "parallelMode": "wide",
-  "agentCount": 6,
-  "maxToolCallsPerAgent": 2,
-  "senderMaxAgents": 2,
-  "senderMaxToolCallsPerAgent": 3,
-  "progressMode": true,
-  "debugMode": true
-}