@sellable/mcp 0.1.100 → 0.1.101

package/package.json

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

package/skills/create-campaign/SKILL.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

package/skills/create-campaign-v2/SKILL.md

@@ -161,7 +161,9 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
 - Customer-facing progress updates must use product language. Say "quick
   setup choices", "campaign brief", "lead sourcing", and "approval" instead of
   `request_user_input`, Default mode, MCP namespaces, plugin caches, prompt
-  loading, runbooks, local skill files, skill versions, or "Sellable token".
+  loading, runbooks, local skill files, skill versions, npm/package details,
+  repo-local files, VPS/off-desktop/browser automation limitations, or
+  "Sellable token".
   "Quick question panel" is only acceptable when explaining a Codex/Claude setup
   blocker.
 - Before the 10-lead import/test batch, do not call `check_rubric`; Phase 84
@@ -728,8 +730,10 @@ Required behavior:
 - provider prompt preflight and interaction-mode approval are in-memory. On
   resume or MCP restart, call `get_provider_prompt({ provider, campaignOfferId })`
   again before any provider search/import; do not assume CampaignOffer state
-  proves preflight happened in this process.
-  on resume or MCP restart, call `get_provider_prompt({ provider, campaignOfferId })` again.
+  proves preflight happened in this process. Immediately before `import_leads`,
+  reload the provider prompt in the same turn with
+  `get_provider_prompt({ provider, campaignOfferId })`, even when source preview
+  loaded it in a previous turn.
 - if CampaignOffer campaignId is missing, stop and recover shell creation before
   sourcing; do not run a campaignless source path in the active flow.
 - do not import leads

package/skills/create-campaign-v2/core/flow.v2.json

@@ -840,6 +840,7 @@
         },
         {
           "tool": "import_leads",
+          "sameTurnPreflight": "Immediately before import_leads, call get_provider_prompt({ provider, campaignOfferId }) in the same resumed turn, even if source discovery loaded the provider prompt earlier.",
           "requiredFields": [
             "campaignOfferId",
             "targetLeadCount"