@sellable/mcp 0.1.354 → 0.1.355

package/package.json

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

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

@@ -127,7 +127,15 @@ 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.
+parent thread. 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
+execution, Task/subagent, or separate Codex threads, assign one lane packet per
+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.
 
 For any lane with `intent:"create"`, the worker must satisfy the normal
 net-new create-campaign preflight before shell creation: load
@@ -173,15 +181,18 @@ If any required field is missing, report
 `blocked: missing_create_campaign_step_receipt` for that lane and do not call it
 complete.
 
-Each customer-visible lane receipt must also include
-message proof from `watchNarration.workerDetails.messageDraftBuilder` or the
-worker's equivalent handoff record. Valid message proof names the current
-campaign id, workflowTableId, selected lead-list or source id, filter choice,
-review-batch row ids/hash, and either `statusSource:"branch"` or
-`statusSource:"parent-thread-fallback"`. It must prove the worker loaded the
-full packaged prompt with `get_subskill_prompt({ subskillName:"generate-messages"`
-until `hasMore:false`, loaded the required message assets, and loaded
-`create-campaign-v2-validation` before returning a `messageDraftRecommendation`.
+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
+id, workflowTableId, selected lead-list or source id, filter choice, and
+review-batch row ids/hash, and it must use `statusSource:"branch"`.
+`statusSource:"parent-thread-fallback"` is not accepted for evergreen
+customer-visible completion because it can be a parent summary rather than proof
+that the create-campaign Message Drafting branch actually ran. The proof must
+show the worker loaded the full packaged prompt with
+`get_subskill_prompt({ subskillName:"generate-messages"` until `hasMore:false`,
+loaded the required message assets, and loaded `create-campaign-v2-validation`
+before returning a `messageDraftRecommendation`.
 The receipt must also include `validationResult:"passed"`, a passed
 quality-review object, and at least 3 concrete reviewed sample messages with
 row ids, generated message text, pass verdicts, and no issues. Shared Cold
@@ -279,9 +290,8 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      not a substitute. The proof receipt must show
      `get_subskill_prompt({ subskillName:"generate-messages"` was loaded until
      `hasMore:false`, required message assets were loaded, and
-     `create-campaign-v2-validation` ran through either
-     `workerDetails.messageDraftBuilder` with `statusSource:"branch"` or an
-     inline `statusSource:"parent-thread-fallback"` receipt. The generated-message
+     `create-campaign-v2-validation` ran through
+     `workerDetails.messageDraftBuilder` with `statusSource:"branch"`. The generated-message
      cells are not prompt proof; `currentRevisionGeneratedMessages` and row
      previews are only downstream cell evidence. The proof must include
      `validationResult:"passed"`, a passed quality review, and at least 3