@sellable/mcp 0.1.355 → 0.1.357

package/package.json

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

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

@@ -57,6 +57,11 @@ For full/customer-visible setup, the first operational command is always
 for operator understanding, but do not create/reuse/repair campaign shells,
 source rows, messages, sequence, approvals, or cleanup before the command-backed
 plan returns lane packets.
+If `setup_evergreen_campaigns` is unavailable, returns 404, throws an API
+error, or does not return a current `planRevision` with lane packets, stop
+immediately with `blocked: setup_evergreen_campaigns_unavailable`. Do not fall
+back to ad hoc create-campaign calls, inventory-only guesses, or direct shell
+creation when the command-backed plan is missing.
 
 Plan shape:
 
@@ -136,6 +141,14 @@ worker and run the lane workers in parallel. If the host cannot run parallel
 workers, report `blocked: missing_parallel_lane_worker_runtime` instead of
 silently doing all lane creation sequentially in the parent thread.
 Short form: the parent thread is the planner, dispatcher, verifier, and receipt collector.
+Before the first mutating lane action, complete an execution-runtime preflight:
+name the callable worker surface/tool that will run lane packets (for example
+Task/subagent, branch worker, separate Codex thread, or an equivalent explicit
+worker runtime). If you cannot name a real callable worker runtime, stop with
+`blocked: missing_parallel_lane_worker_runtime` before calling
+`create_campaign`, `update_campaign`, `import_leads`, `confirm_lead_list`, or
+any source/message/sequence mutation. Creating campaign shells first and then
+discovering the worker runtime is missing is a failed run.
 
 For any lane with `intent:"create"`, the worker must satisfy the normal
 net-new create-campaign preflight before shell creation: load
@@ -181,6 +194,17 @@ If any required field is missing, report
 `blocked: missing_create_campaign_step_receipt` for that lane and do not call it
 complete.
 
+One lane may produce exactly one CampaignOffer/campaign id and one current
+workflow table id. For `intent:"create"`, the first successful
+`create_campaign` result establishes the lane's only allowed campaign/table
+target. Every later source/import/confirm/message/filter/sequence/readback call
+must use that same campaign id and current workflow table id. If any tool
+returns or creates a different CampaignOffer, workflow table, "Campaign from
+Source" campaign, or shell for the same lane, stop immediately with
+`blocked: duplicate_campaign_offer_created`, include both ids in the receipt,
+and do not report completion. Do not hide the earlier shell by reporting only
+the later imported campaign.
+
 Each customer-visible lane receipt must also include message proof from
 `watchNarration.workerDetails.messageDraftBuilder` or the worker's equivalent
 branch handoff record. Valid evergreen message proof names the current campaign
@@ -211,9 +235,17 @@ create-campaign Message Drafting branch ran. If this receipt is missing, report
 `blocked: missing_message_drafting_receipt` and do not call the lane complete.
 
 The parent then calls
-`setup_evergreen_campaigns({ mode:"verify", planRevision, selectedActionIds,
-receipts })` and report only verified completion. If verify blocks, report the
-blocker and repair only the missing postconditions from the same current plan.
+`setup_evergreen_campaigns({ mode:"verify", postEngagerSenderIds,
+sharedSenderIds, planRevision, selectedActionIds, receipts })` using the same
+sender scopes as the plan call, and reports only verified completion. A verify
+call without the same sender scopes can recompute an empty or different plan and
+is invalid proof. After verify succeeds, rerun
+`setup_evergreen_campaigns({ mode:"plan", postEngagerSenderIds,
+sharedSenderIds, yolo:true })` without explicit campaign/table bindings. That
+idempotency plan must return `intent:"reuse"` for every completed lane and no
+duplicate-lane blockers before you call the command finished. If verify blocks,
+report the blocker and repair only the missing postconditions from the same
+current plan.
 
 Message proof for every customer-visible lane must come from the current
 campaign/table basis and include at least 3 generated review rows from the