@sellable/mcp 0.1.352 → 0.1.354

package/package.json

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

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

@@ -129,6 +129,13 @@ filter choice, Message Drafting, packaged `generate-messages`, sequence
 attachment, and send-review readiness. Do not rebuild those steps ad hoc in the
 parent thread.
 
+For any lane with `intent:"create"`, the worker must satisfy the normal
+net-new create-campaign preflight before shell creation: load
+`get_subskill_prompt({ subskillName:"research-sender" })`, run the sender/team
+identity research needed for the brief, call `complete_sender_research(...)`,
+then call `create_campaign`. Do not bypass this with a parent-thread brief or
+by directly setting campaign state.
+
 Workers return worker receipts. Each customer-visible lane receipt must include
 one durable `createCampaignStepReceipt` built from actual tool calls or worker receipts,
 not a parent-thread summary. The receipt must include:
@@ -138,6 +145,9 @@ not a parent-thread summary. The receipt must include:
   campaign/table binding or create intent used before work started. For a
   create lane, this receipt must explicitly include `createIntent:true`; for a
   reuse lane, do not report `createIntent:true`.
+- `researchSenderReceipt`: `research-sender` prompt load proof,
+  `complete_sender_research` result, sender LinkedIn identity basis, and the
+  notes/proof counts used before the net-new `create_campaign` call.
 - `campaignBriefReceipt`: the CampaignOffer/campaign id, current
   workflowTableId, brief hash or updated-at marker, delivery format, token
   rules, hard avoids, source-use rules, and first-message template state.
@@ -178,6 +188,11 @@ 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
@@ -218,12 +233,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