@sellable/mcp 0.1.400 → 0.1.402

package/package.json

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

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

@@ -315,7 +315,26 @@ Short form: Receipt polling uses `find <receipt-dir> -maxdepth 1 -name 'evg_*.js
 Short form: Do not use naked `*.json` globs under zsh; no `no matches found` diagnostics.
 Short form: Do not embed `<<'WORKER_PROMPT'` heredocs inside a quoted `/bin/bash -lc` command string.
 Short form: Multi-worker launchers write prompt files and run `codex ... - < "$worker_prompt_file"`.
+After the auto-executable plan returns, take at most one short planning pass to
+choose the visible/durable worker runtime and build the worker launch packet.
+Do not keep reasoning, re-reading prompts, or restating the workflow instead of
+dispatching. If the parent cannot name the callable worker runtime and prepare
+the first worker launch command/tool call immediately after that pass, stop with
+`blocked: worker_dispatch_deadline_exceeded` before directory setup or mutation.
 After creating receipt directories, dispatch workers immediately; do not perform extended parent reasoning, extra inventory, or prompt rewriting loops.
+Before any campaign shell creation, the parent must dispatch every selected lane
+worker from the current plan and record the visible thread id or
+`receiptArtifactPath` for each selected actionId. The parent must not call
+`create_campaign`, `import_leads`, `confirm_lead_list`, sequence tools, message
+preparation tools, or `setup_evergreen_campaigns` with `mode:"apply"` or any
+other mutating setup mode. In this wrapper, `setup_evergreen_campaigns` is
+plan/verify authority only; customer-visible creation belongs inside lane
+workers through `$sellable:create-campaign`. If a campaign/table id appears for
+a create lane before that lane has a recorded worker runtime and fresh receipt
+path/thread id, stop with `blocked: parent_mutated_before_worker_receipt` and
+do not continue setup in the parent.
+Short form: dispatch every selected lane worker before shell creation.
+Short form: do not call `setup_evergreen_campaigns` with `mode:"apply"` from the parent.
 Use a compact worker prompt: include lane packet JSON, original selectedActionIds,
 original planRevision, parent postEngagerSenderIds, parent sharedSenderIds,
 receiptArtifactPath, workspace id, sender ids, side-effect caps, and the
@@ -323,6 +342,11 @@ instruction to load packaged prompts through MCP.
 Do not paste the entire wrapper skill into worker prompts. If the parent cannot
 launch at least one visible/durable worker immediately after directory setup,
 stop with `blocked: worker_dispatch_stalled` before any mutation.
+After launching workers, poll only the expected current-run receipt paths from
+`workerDispatch.receiptArtifactHint`. If no worker receipt file appears within a
+bounded wait, for example 10 minutes in automation, stop with
+`blocked: worker_receipt_timeout`, include the worker ids/final-file paths/stderr
+if available, and do not create or repair campaign shells in the parent.
 Use only the repo-local `workerDispatch.receiptArtifactHint` returned by the
 current lane packet for receipt paths.
 Do not hardcode machine-specific paths, workspace ids, campaign ids, sender ids, or UAT/phase artifact paths in this MCP prompt or any worker prompt.