@sellable/mcp 0.1.365 → 0.1.367

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, 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 set status:'succeeded' or status:'completed' and must include createCampaignStepReceipt with setupPlanCall, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall nested inside createCampaignStepReceipt; top-level-only copies of those objects are not enough. messageDraftingReceipt must use statusSource:'branch' or statusSource:'packaged-generate-messages-worker' and include proof that generate-messages was loaded, start_campaign_message_preparation/get_campaign_message_preparation_status ran when the packaged worker path is used, 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.",
+        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 explicitly load and use the installed `$sellable:create-campaign` wrapper as the nested workflow entrypoint, then load `create-campaign-v2` and `create-campaign-v2/core/flow.v2.json`; they 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 that existing create-campaign workflow/subskills, then return receipts here for verification. Customer-visible verify receipts must set status:'succeeded' or status:'completed' and must include createCampaignStepReceipt with setupPlanCall, createCampaignWorkflowReceipt, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall nested inside createCampaignStepReceipt; top-level-only copies of those objects are not enough. createCampaignWorkflowReceipt must include skillCommand:'$sellable:create-campaign', skillName:'create-campaign', wrapperSkillLoaded:true, workflowPromptName:'create-campaign-v2', workflowPromptLoadedToHasMoreFalse:true, workflowAssetPath:'create-campaign-v2/core/flow.v2.json', workflowAssetLoaded:true, workerRuntime, and notAdHoc:true. messageDraftingReceipt must use statusSource:'branch' or statusSource:'packaged-generate-messages-worker' and include proof that generate-messages was loaded, start_campaign_message_preparation/get_campaign_message_preparation_status ran when the packaged worker path is used, 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: {
@@ -75,7 +75,7 @@ export const setupEvergreenCampaignsToolDefinitions = [
                     type: "array",
                     maxItems: 20,
                     items: { type: "object" },
-                    description: "Required for verify. Structured lane worker receipts from create-campaign/source/message/sequence execution. Customer-visible lanes must use status:'succeeded' or status:'completed' and include createCampaignStepReceipt with setupPlanCall, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall nested inside createCampaignStepReceipt. Top-level-only proof copies are not enough.",
+                    description: "Required for verify. Structured lane worker receipts from create-campaign/source/message/sequence execution. Customer-visible lanes must use status:'succeeded' or status:'completed' and include createCampaignStepReceipt with setupPlanCall, createCampaignWorkflowReceipt, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall nested inside createCampaignStepReceipt. createCampaignWorkflowReceipt proves the lane worker loaded `$sellable:create-campaign`, `create-campaign-v2`, and `create-campaign-v2/core/flow.v2.json`; top-level-only proof copies are not enough.",
                 },
             },
             required: [],

package/package.json

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

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

@@ -138,11 +138,15 @@ After bounded delegated approval or safe `--yolo`, fan out lane worker tasks
 only from the current plan. Each worker receives the complete lane packet:
 workspace id, sender ids, lane key/type, existing campaign/table binding or
 create intent, source hints, caps, planRevision, actionId, allowed side effects,
-and postconditions. Workers must use the create-campaign workflow and
-create-campaign workflow/subskills for campaign creation/setup, source/import,
-filter choice, Message Drafting, packaged `generate-messages`, sequence
-attachment, and send-review readiness. Do not rebuild those steps ad hoc in the
-parent thread. The parent thread is only the planner, dispatcher, verifier, and
+and postconditions. Workers must explicitly load and use the installed visible
+`$sellable:create-campaign` wrapper as the nested workflow entrypoint, then load
+`create-campaign-v2` and `create-campaign-v2/core/flow.v2.json` through the
+packaged MCP prompt/asset loaders before campaign creation or repair. The
+worker then uses that create-campaign workflow/subskills for campaign
+creation/setup, source/import, filter choice, Message Drafting, packaged
+`generate-messages`, sequence attachment, and send-review readiness. Do not
+rebuild those steps ad hoc in the parent thread or from a copied receipt
+checklist. The parent thread is only the planner, dispatcher, verifier, and
 receipt collector: it must not call `create_campaign`, `import_leads`,
 `start_campaign_message_preparation`, `update_cell`, or sequence-attach tools
 for a lane that was assigned to a worker. When the host supports branch
@@ -176,6 +180,14 @@ not a parent-thread summary. The receipt must include:
   campaign/table binding or create intent used before work started. For a
   create lane, this receipt must explicitly include `createIntent:true`; for a
   reuse lane, do not report `createIntent:true`.
+- `createCampaignWorkflowReceipt`: proof the worker loaded the actual installed
+  `$sellable:create-campaign` wrapper instead of doing ad hoc MCP calls. It must
+  include `skillCommand:"$sellable:create-campaign"`,
+  `skillName:"create-campaign"`, `wrapperSkillLoaded:true`,
+  `workflowPromptName:"create-campaign-v2"`,
+  `workflowPromptLoadedToHasMoreFalse:true`,
+  `workflowAssetPath:"create-campaign-v2/core/flow.v2.json"`,
+  `workflowAssetLoaded:true`, the real `workerRuntime`, and `notAdHoc:true`.
 - `researchSenderReceipt`: `research-sender` prompt load proof,
   `complete_sender_research` result, sender LinkedIn identity basis, and the
   notes/proof counts used before the net-new `create_campaign` call.
@@ -219,10 +231,11 @@ the lane is complete. Do not use `status:"passed"` or
 in a separate `warnings` array, but the completion status stays canonical.
 
 All step proof objects must live under `createCampaignStepReceipt`. Do not put
-`campaignBriefReceipt`, `sourceDecisionReceipt`, `filterDecisionReceipt`,
-`messageDraftingReceipt`, `reviewBatchReceipt`, or `sequenceReceipt` only as
-top-level siblings; top-level copies are useful for humans but are not enough
-for command verification unless the same object also appears inside
+`createCampaignWorkflowReceipt`, `campaignBriefReceipt`,
+`sourceDecisionReceipt`, `filterDecisionReceipt`, `messageDraftingReceipt`,
+`reviewBatchReceipt`, or `sequenceReceipt` only as top-level siblings;
+top-level copies are useful for humans but are not enough for command
+verification unless the same object also appears inside
 `createCampaignStepReceipt`.
 
 ```json
@@ -236,6 +249,17 @@ for command verification unless the same object also appears inside
   "campaignId": "<campaign id>",
   "tableId": "<workflow table id>",
   "createCampaignStepReceipt": {
+    "createCampaignWorkflowReceipt": {
+      "skillCommand": "$sellable:create-campaign",
+      "skillName": "create-campaign",
+      "wrapperSkillLoaded": true,
+      "workflowPromptName": "create-campaign-v2",
+      "workflowPromptLoadedToHasMoreFalse": true,
+      "workflowAssetPath": "create-campaign-v2/core/flow.v2.json",
+      "workflowAssetLoaded": true,
+      "workerRuntime": "separate-codex-thread",
+      "notAdHoc": true
+    },
     "campaignBriefReceipt": {
       "campaignId": "<campaign id>",
       "workflowTableId": "<workflow table id>",