@sellable/install 0.1.85 → 0.1.87

package/agents/source-scout-linkedin-engagement.md

@@ -7,10 +7,10 @@ Required first step:
 - Load the canonical provider prompt before searching. If the parent supplies a
   draft `campaignOfferId`, call `get_provider_prompt({ provider:
 "signal-discovery", campaignOfferId, confirmed: true })` and include that same
-  `campaignOfferId` in `search_signals` so the user can watch source work in the
-  campaign UI. Treat that as a campaign-attached persisted search; do not run a
-  post-mint search without the campaign ID. If no campaign ID is supplied, run
-  campaignless preview mode.
+  `campaignOfferId` plus `currentStep: "signal-discovery"` in `search_signals`
+  so the user can watch source work in the campaign UI. Treat that as a
+  campaign-attached persisted search; do not run a post-mint search without the
+  campaign ID. If no campaign ID is supplied, run campaignless preview mode.
 
 Use the inherited Sellable MCP tools when available:
 

package/agents/source-scout-prospeo-contact.md

@@ -6,9 +6,10 @@ Required first step:
 
 - Load the canonical provider prompt before searching. If the parent supplies a
   draft `campaignOfferId`, call `get_provider_prompt({ provider: "prospeo",
-campaignOfferId, confirmed: true })` and include that same `campaignOfferId` in
-  `search_prospeo` so the user can watch source work in the campaign UI. If no
-  campaign ID is supplied, run campaignless preview mode. Treat post-mint
+campaignOfferId, confirmed: true })` and include that same `campaignOfferId`
+  plus `currentStep: "prospeo"` in `search_prospeo` so the user can watch source
+  work in the campaign UI. If no campaign ID is supplied, run campaignless
+  preview mode. Treat post-mint
   searches with `campaignOfferId` as campaign-attached persisted search tabs;
   do not run a live campaign search without the campaign ID.
 

package/agents/source-scout-sales-nav.md

@@ -7,8 +7,9 @@ Required first step:
 - Load the canonical provider prompt before searching. If the parent supplies a
   draft `campaignOfferId`, call `get_provider_prompt({ provider: "sales-nav",
 campaignOfferId, confirmed: true })` and include that same `campaignOfferId` in
-  `search_sales_nav` so the user can watch source work in the campaign UI. If no
-  campaign ID is supplied, run campaignless preview mode. Treat post-mint
+  `search_sales_nav` with `currentStep: "sales-nav"` so the user can watch
+  source work in the campaign UI. If no campaign ID is supplied, run
+  campaignless preview mode. Treat post-mint
   searches with `campaignOfferId` as campaign-attached persisted search tabs;
   do not run a live campaign search without the campaign ID.
 

package/bin/sellable-install.mjs

@@ -626,16 +626,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
@@ -648,7 +649,7 @@ unless it was opened and observed.
 After every \`update_campaign({ campaignId, currentStep })\`, use
 \`get_campaign_navigation_state\` when available as a compact orientation check:
 match the browser-visible 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. Do not attach a sequence, start the campaign, or trigger a live send unless the user explicitly confirms that launch action outside UAT.
+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. Explain Slack reply review before launch. After sender selection, attach the recommended sequence and move the watched UI to Send. Do not start the campaign or trigger a live send unless the user explicitly confirms that launch action outside UAT.
 
 ## Names To Use
 

package/package.json

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

package/skill-templates/create-campaign.md

@@ -197,7 +197,7 @@ it was opened and observed.
 After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
 match the browser-visible 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. Do not attach a sequence, start the campaign, or trigger a live send unless the user explicitly confirms that launch action outside UAT.
+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. Explain Slack reply review before launch. After sender selection, attach the recommended sequence and move the watched UI to Send. Do not start the campaign or trigger a live send unless the user explicitly confirms that launch action outside UAT.
 
 ## Names To Use
 
@@ -568,7 +568,9 @@ updates.
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after the 10-row review batch, `messages` or
    `auto-execute-messaging` for message work, `validate-sample` for validation,
-   and `awaiting-user-greenlight` for Settings. Do not advance the step backward.
+   `awaiting-user-greenlight` for the final handoff, `settings` for sender
+   selection, `sequence` after sender attach, and `send` once the recommended
+   sequence is attached. Do not advance the step backward.
 7. Keep `selectedLeadListId` as the source list and `workflowTableId` as the
    campaign table. Do not use disk files as the post-mint source of truth.
 8. Do not ask the user to run another command.