@sellable/mcp 0.1.355 → 0.1.356

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/mcp",
3
- "version": "0.1.355",
3
+ "version": "0.1.356",
4
4
  "type": "module",
5
5
  "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
6
6
  "main": "dist/index.js",
@@ -57,6 +57,11 @@ For full/customer-visible setup, the first operational command is always
57
57
  for operator understanding, but do not create/reuse/repair campaign shells,
58
58
  source rows, messages, sequence, approvals, or cleanup before the command-backed
59
59
  plan returns lane packets.
60
+ If `setup_evergreen_campaigns` is unavailable, returns 404, throws an API
61
+ error, or does not return a current `planRevision` with lane packets, stop
62
+ immediately with `blocked: setup_evergreen_campaigns_unavailable`. Do not fall
63
+ back to ad hoc create-campaign calls, inventory-only guesses, or direct shell
64
+ creation when the command-backed plan is missing.
60
65
 
61
66
  Plan shape:
62
67
 
@@ -136,6 +141,14 @@ worker and run the lane workers in parallel. If the host cannot run parallel
136
141
  workers, report `blocked: missing_parallel_lane_worker_runtime` instead of
137
142
  silently doing all lane creation sequentially in the parent thread.
138
143
  Short form: the parent thread is the planner, dispatcher, verifier, and receipt collector.
144
+ Before the first mutating lane action, complete an execution-runtime preflight:
145
+ name the callable worker surface/tool that will run lane packets (for example
146
+ Task/subagent, branch worker, separate Codex thread, or an equivalent explicit
147
+ worker runtime). If you cannot name a real callable worker runtime, stop with
148
+ `blocked: missing_parallel_lane_worker_runtime` before calling
149
+ `create_campaign`, `update_campaign`, `import_leads`, `confirm_lead_list`, or
150
+ any source/message/sequence mutation. Creating campaign shells first and then
151
+ discovering the worker runtime is missing is a failed run.
139
152
 
140
153
  For any lane with `intent:"create"`, the worker must satisfy the normal
141
154
  net-new create-campaign preflight before shell creation: load