@sellable/mcp 0.1.359 → 0.1.361

package/package.json

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

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

@@ -73,6 +73,16 @@ Plan shape:
   creating duplicates.
 - If a user supplies canonical ids, reuse/verify them instead of creating duplicates.
 
+The command-backed unbound plan is authoritative. If
+`setup_evergreen_campaigns({ mode:"plan", ... })` returns a lane packet with
+`intent:"create"`, execute that create packet exactly. Do not convert it into an
+explicit binding because `list_tables`, `get_campaigns`, a waterfall, or old
+inventory shows an `ARCHIVED` campaign/table with a matching name. Archived
+campaigns are not reusable evergreen targets. Only pass an archived
+campaign/table as an explicit binding when the user supplied those exact ids and
+explicitly allowed dashboard visibility repair; otherwise ignore archived
+matches for execution and let the create packet proceed.
+
 Use `selectedSenderIds` only as a legacy shorthand when the same senders should
 get sender-owned Post Engagers lanes and attach to shared lanes. When the scopes
 differ, pass both explicit arrays:
@@ -173,9 +183,10 @@ not a parent-thread summary. The receipt must include:
   workflowTableId, brief hash or updated-at marker, delivery format, token
   rules, hard avoids, source-use rules, and first-message template state.
 - `sourceDecisionReceipt`: selected source/list id, provider, cursor/inventory
-  state, import/copy caps, dedupe/DNC/provider exclusions, row ids or row-count
-  evidence, and the reason no colder source was used before the current source
-  was proven exhausted or insufficient.
+  state, import/copy caps, explicit `dedupeDncProviderExclusions:true` or an
+  equivalent exclusions object, row ids or row-count evidence (`rowCount`,
+  `readyRowCount`, or `rowEvidence`), and the reason no colder source was used
+  before the current source was proven exhausted or insufficient.
 - `filterDecisionReceipt`: saved/applied filter ids or explicit skip-filter
   decision with current campaign/table basis.
 - `messageDraftingReceipt`: the Message Drafting proof described below,
@@ -196,6 +207,15 @@ not a parent-thread summary. The receipt must include:
   planRevision, selectedActionIds, receipts })` call/result used before the
   parent reports completion.
 
+Verification always uses the original execution planRevision and original
+selectedActionIds from the plan packets that were dispatched before mutation.
+The parent must preserve the original selectedActionIds exactly.
+Do not replace them with a later reuse planRevision/actionIds after the
+campaigns exist. After workers complete, attach or patch `verifyCall` on each
+lane receipt with that original execution planRevision, original
+selectedActionIds, same sender scopes, and the verify result. Only after verify
+succeeds should the parent perform the idempotency rerun.
+
 If any required field is missing, report
 `blocked: missing_create_campaign_step_receipt` for that lane and do not call it
 complete.
@@ -276,12 +296,11 @@ create-campaign Message Drafting branch ran. If this receipt is missing, report
 The parent then calls
 `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
+sender scopes as the plan call and the original execution planRevision/actionIds,
+and reports only verified completion. A verify call without the same sender scopes can recompute an empty or different plan and is invalid proof. A verify call that uses a later reuse planRevision instead of the original execution planRevision is also invalid proof. Only 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
+idempotency rerun 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.