@sellable/mcp 0.1.353 → 0.1.355

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.353",
+  "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,21 +181,29 @@ 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
 Fallback samples must not open with a standalone name line followed by
 "Hey there" or another generic greeting; that pattern means the lane did not
 finish the create-campaign message workflow to customer quality.
+Shared Signal Discovery samples must not use sender-owned post-engager language
+such as "my post", "thanks for showing support", "saw you pop up", or any copy
+that implies the sending sender authored the source post or personally received
+the prospect's engagement unless the selected source evidence proves that exact
+sender authored the post.
 The generated-message cells are not prompt proof: `currentRevisionGeneratedMessages`,
 Generate Message column counts, `messagesCount`, or rendered row previews prove
 only that table cells exist from the current brief/template, not that the
@@ -228,12 +244,15 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      the real observed signal/theme or public conversation. It may mention the
      engagement source only when the source evidence supports it. Do not say
      "my post" unless the selected source post was actually authored by the
-     sending sender.
+     sending sender. Do not thank the prospect for showing support, reacting,
+     commenting, or popping up unless this is a sender-owned Post Engagers lane
+     with sender-authored source evidence.
    - **Shared Cold Fallback** first-message style: cold, direct, and cohesive.
      It must not pretend there was engagement, must not say "saw you pop up",
      and must not use a standalone name line followed by "Hey there" or other
      generic greeting. It should open with a light role/company/problem
-     observation and ask one clear problem question. This is a single-message
+     observation, avoid awkward phrases like "looks like a team where", and ask
+     one clear problem question. This is a single-message
      cold path unless the approved create-campaign message workflow proves a
      better delivery format.
    - Every customer-visible lane must run Message Drafting from the current
@@ -271,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