@sellable/mcp 0.1.357 → 0.1.358

package/dist/tools/setup-evergreen-campaigns.js

@@ -6,7 +6,7 @@ async function postSetupEvergreenCampaigns(body) {
 export const setupEvergreenCampaignsToolDefinitions = [
     {
         name: "setup_evergreen_campaigns",
-        description: "Evergreen campaign setup plan/verify command. Use plan mode first to inspect exact workspace/sender/campaign/table/source state and receive immutable lane packets. `selectedSenderIds` is a legacy shorthand for both scopes; prefer `postEngagerSenderIds` for the Post Engagers sender scope and `sharedSenderIds` for the shared lane sender scope when they differ. The command plans one Post Engagers lane per post-engager sender plus shared Signal Discovery and Shared Cold Fallback lanes for the shared sender set. yolo is only a parent-skill auto-execution hint for safe lane packets; this backend command remains read-only in plan mode and verifies receipts in verify mode. When safe-yolo needs normal setup work, the parent skill may ask for bounded delegated approval: one approval over the current planRevision, selected action ids, caps, allowed side-effect classes, and stop conditions lets lane workers execute without per-substep approval while staying inside that packet. Lane workers must execute creation, source import, create-campaign workflow steps, generate-messages, sequence attachment, and review readiness through existing create-campaign workflow/subskills, then return receipts here for verification. Customer-visible verify receipts must include createCampaignStepReceipt with setupPlanCall, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall. messageDraftingReceipt must include validationResult:'passed', a passed qualityReview, and at least 3 concrete sampleMessages with row ids, generated message text, pass verdicts, and no issues; Shared Cold Fallback samples with a standalone name followed by 'Hey there' are rejected. This command does not launch campaigns, does not schedule sends, does not assign scheduler-owned send fields, does not archive/delete cleanup targets, and does not spend paid credits.",
+        description: "Evergreen campaign setup plan/verify command. Use plan mode first to inspect exact workspace/sender/campaign/table/source state and receive immutable lane packets. `selectedSenderIds` is a legacy shorthand for both scopes; prefer `postEngagerSenderIds` for the Post Engagers sender scope and `sharedSenderIds` for the shared lane sender scope when they differ. The command plans one Post Engagers lane per post-engager sender plus shared Signal Discovery and Shared Cold Fallback lanes for the shared sender set. yolo is only a parent-skill auto-execution hint for safe lane packets; this backend command remains read-only in plan mode and verifies receipts in verify mode. When safe-yolo needs normal setup work, the parent skill may ask for bounded delegated approval: one approval over the current planRevision, selected action ids, caps, allowed side-effect classes, and stop conditions lets lane workers execute without per-substep approval while staying inside that packet. Lane workers must execute creation, source import, create-campaign workflow steps, generate-messages, sequence attachment, pause_campaign review-state transition when the current table is still DRAFT, and review readiness through existing create-campaign workflow/subskills, then return receipts here for verification. Customer-visible verify receipts must include createCampaignStepReceipt with setupPlanCall, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall. messageDraftingReceipt must include validationResult:'passed', a passed qualityReview, and at least 3 concrete sampleMessages with row ids, generated message text, pass verdicts, and no issues; Shared Cold Fallback samples with a standalone name followed by 'Hey there' are rejected. This command does not launch campaigns, does not schedule sends, does not assign scheduler-owned send fields, does not raw-write campaign status, does not archive/delete cleanup targets, and does not spend paid credits.",
         inputSchema: {
             type: "object",
             properties: {

package/package.json

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

package/skills/create-evergreen-campaigns/SKILL.md

@@ -186,6 +186,12 @@ not a parent-thread summary. The receipt must include:
 - `sequenceReceipt`: exact current workflowTableId, recommended non-paid
   sequence attach/precheck result, and readback showing `hasSequence:true` when
   completion is claimed.
+- final paused-send proof: if the current campaign table is `DRAFT` after the
+  sequence is attached, call the product `pause_campaign({ campaignId })`
+  endpoint/tool to put the unlaunched campaign into `PAUSED` review state, then
+  reread the campaign/table. Do not raw-write `campaignStatus`, do not start or
+  launch, and do not schedule/send. Completion requires reread proof of
+  `currentStep:"send"` and `campaignStatus:"PAUSED"`.
 - `verifyCall`: the exact `setup_evergreen_campaigns({ mode:"verify",
   planRevision, selectedActionIds, receipts })` call/result used before the
   parent reports completion.
@@ -342,10 +348,10 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      completion, approve exactly one quality-valid generated row. If one or more
      rows are already approved, do not add more approvals during evergreen
      completion. Never broad approve all rows.
-   - The recommended non-paid sequence is attached to the current campaign
-     table, and the watched campaign is on Send. Use
-     `attach_recommended_sequence({ campaignId, currentStep:"send" })` when a
-     safe attach is needed. After `confirm_lead_list` or any source-list copy,
+    - The recommended non-paid sequence is attached to the current campaign
+      table, and the watched campaign is on Send. Use
+      `attach_recommended_sequence({ campaignId, currentStep:"send" })` when a
+      safe attach is needed. After `confirm_lead_list` or any source-list copy,
      immediately reread `get_campaign({ campaignId })`; the returned
      `workflowTableId` is the current campaign table. Cross-check that exact
      current workflowTableId with `list_tables` and require `hasSequence:true`
@@ -353,11 +359,15 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      the current campaign table does not, `SEQUENCE_EXISTS` is not enough:
      record the stale shell table id, then repair the current workflowTableId
      with `attach_sequence` using the same non-paid product template
-     `attach_recommended_sequence` would have selected. Never use a paid-InMail
-     template and never attach/replace sequence outside the current table unless
-     the current lane packet explicitly allowed sequence repair.
-   - No scheduled, queued outbound, sent outbound, campaign launch, or paid
-     InMail spend is created by this skill.
+      `attach_recommended_sequence` would have selected. Never use a paid-InMail
+      template and never attach/replace sequence outside the current table unless
+      the current lane packet explicitly allowed sequence repair.
+    - If the current campaign table is still `DRAFT` after sequence/readiness
+      proof, call `pause_campaign({ campaignId })` and reread. `pause_campaign`
+      is the product-native review-state transition; it is not a launch and does
+      not schedule or send. Never raw-write campaign status.
+    - No scheduled, queued outbound, sent outbound, campaign launch, or paid
+      InMail spend is created by this skill.
 4. **Verify each slot** after create/reuse/repair:
    - `get_campaign` shows the campaign exists, remains unlaunched, and has the expected workflow table.
    - Builder truth must match dashboard truth. `currentStep:"running"` is valid only when the linked table has `campaignStatus:"ACTIVE"`. For a `PAUSED` or `ARCHIVED` campaign/table, repair or flag stale `currentStep:"running"` back to launch review (`send` / review-ready) before reporting the slot done. Never call `start_campaign` just to make a stale `running` step true.