@sellable/mcp 0.1.407 → 0.1.409

package/package.json

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

package/skills/create-campaign-v2/references/gold-standard-message-examples.md

@@ -445,24 +445,25 @@ Tokenized shape:
 Hey there
 
 Thanks for the support on my post about {{post_topic_line}}
-
-Curious, is this something you're dealing with right now?
 ```
 
 Transfer rules:
 
 - Do not hardcode a post topic. Fill `{{post_topic_line}}` from the actual
   selected sender-authored post or use a safer source-specific phrase.
+- Do not add a relevance question, CTA, product line, or extra paragraph after
+  the thank-you line. The reply-rate lesson is the casual warm acknowledgment,
+  not a cold pitch appended to it.
 - Do not use "showing some love"; it reads too casual for executive/VP/director
   contacts.
 - Keep the thank-you line. The point of this motion is acknowledging real
-  sender-owned support before asking a light relevance question. Do not flatten
-  it back to "saw you pop up" unless the sender specifically asks for that
-  wording.
+  sender-owned support without appending a cold relevance question. Do not
+  flatten it back to "saw you pop up" unless the sender specifically asks for
+  that wording.
 - Do not copy this shape into shared lanes, third-party thread sources, or cold
   fallback campaigns.
-- Keep the question closed and problem-oriented; do not pitch, ask for a
-  meeting, or mention internal product vocabulary in message one.
+- Do not pitch, ask for a meeting, or mention internal product vocabulary in
+  message one.
 
 ## Useful CTA Shapes
 

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

@@ -943,17 +943,34 @@ current plan.
 Before calling verify, the parent should build compact receipt objects from the
 durable receipt files and pass those compact objects to MCP. The compact receipt
 must preserve every verifier-owned field named above, including top-level ids,
-`createCampaignStepReceipt`, canonical filter/message/review/sequence/final
-proof, and at least three concrete sample messages. It should omit large raw
+`createCampaignStepReceipt`, `researchSenderReceipt`, canonical
+filter/message/review/sequence/final proof, and at least three concrete sample
+messages. It should omit large raw
 search outputs, long post lists, full row arrays, raw provider responses, and
 debug-only narration fields. Do not pass multi-hundred-kilobyte raw receipt
 objects when a compact canonical receipt has the same proof; large raw verify
 payloads can stall local MCP bridges and make UAT ambiguous.
+Use a small Node JSON compactor for non-trivial compaction. Do not build complex
+inline `jq` filters inside nested quoted shell strings; quote failures are a
+UAT blocker and waste the verification run. The Node compactor must preserve
+every canonical verifier object under `createCampaignStepReceipt`, including
+`setupPlanCall`, `createCampaignWorkflowReceipt`, `researchSenderReceipt`,
+`campaignBriefReceipt`, `sourceDecisionReceipt`, `filterDecisionReceipt`,
+`messageDraftingReceipt`, `reviewBatchReceipt`, `sequenceReceipt`,
+`finalPausedSendProof`, and `verifyCall`.
+When compacting, normalize `finalPausedSendProof.currentStep` and
+`finalPausedSendProof.campaignStatus` from nested pause/navigation readbacks if
+the worker receipt stored those values under `pauseCampaignResult`,
+`navigationReadback`, or `navigationProof`; do not pass an empty
+`finalPausedSendProof` object to verify.
 Do not print or `jq .` full receipt JSON into the terminal. For local checks,
 print only compact summaries such as file, actionId, laneKey, campaignId,
 filter status, sample count, approved count, and final status.
 Short form: Parent verify uses compact canonical receipt objects, not raw giant receipts.
 Short form: Do not dump full receipt JSON with `jq .`.
+Short form: Do not use complex inline `jq` for receipt compaction; use Node.
+Short form: Compact receipts must preserve `researchSenderReceipt`.
+Short form: Compact receipts must preserve direct `finalPausedSendProof.currentStep` and `campaignStatus`.
 Short form: Never change planRevision/actionId/laneKey while compacting receipts.
 
 Message proof for every customer-visible lane must come from the current
@@ -962,15 +979,23 @@ packaged `generate-messages` path before completion is reported.
 Parent-thread handwritten copy or setting `currentStep` is not proof.
 
 The parent must run its own sample-quality gate before final reporting, even
-when worker receipts say `verdict:"passed"`. For each shared lane, normalize the
-reviewed sample messages by removing leading greeting/name lines, first names,
-and whitespace-only differences; reject shared-lane samples when the message body is identical after removing first names or when all samples share the same
-paragraph skeleton. Also reject final shared-lane samples with `Hey <name>,`
-letter punctuation, weak relevance hedges, internal workflow vocabulary,
-self-intros, or any non-empty `issues`. If the parent finds repeated shared-lane
-sample copy, report `blocked: repeated_shared_lane_sample_copy`, revise the
-campaign brief/template through the packaged workflow, rerun Generate Message,
-and verify current-revision sample messages before final completion.
+when worker receipts say `verdict:"passed"`. For Post Engagers lanes, reject
+any sample that adds a relevance question, CTA, product line, or extra paragraph
+after `Thank you for the support on my post about ...`; blocked phrases include
+`curious`, `open to`, `trying to`, `worth seeing`, `want to see`, and any
+Sellable/product explanation. For each shared lane, normalize the reviewed
+sample messages by removing leading greeting/name lines, first names, and
+whitespace-only differences; reject shared-lane samples when the message body is
+identical after removing first names or when all samples share the same paragraph
+skeleton. Also reject final shared-lane samples with `Hey <name>,` letter
+punctuation, weak relevance hedges, internal workflow vocabulary, self-intros,
+or any non-empty `issues`. Shared lanes must also reject mechanical
+product-process wording such as `sequence-prospects`, `dashboard overhead`,
+`campaign map`, `campaign idea into prospects`, `prospects, filters, messages`,
+`send-ready copy`, or `reviewed prospect lists`. If the parent finds repeated
+shared-lane sample copy, report `blocked: repeated_shared_lane_sample_copy`,
+revise the campaign brief/template through the packaged workflow, rerun Generate
+Message, and verify current-revision sample messages before final completion.
 </command_backed_workflow>
 
 <objective>
@@ -1009,8 +1034,9 @@ and verify current-revision sample messages before final completion.
      Short form: Shared lanes must reject internal workflow vocabulary.
      Short form: revise or rerun the packaged create-campaign/generate-messages path.
    - **Post Engagers** first-message style: short, casual, references the
-     sender-authored post they engaged with, closed question, **no internal
-     vocabulary, no pitch, no meeting ask** in message one:
+     sender-authored post they engaged with, and stops after the thank-you
+     line. Use **no internal vocabulary, no pitch, no meeting ask, no product
+     line, and no relevance question** in message one:
 
      ```
      {{first_name}}
@@ -1020,6 +1046,10 @@ and verify current-revision sample messages before final completion.
      Thank you for the support on my post about {{post_topic_line}}
      ```
 
+     Do not add any paragraph after the thank-you line. In particular, do not
+     append `curious, are you trying...`, `open to...`, `worth seeing...`, or
+     Sellable/product copy to a Post Engagers first message.
+
    - **Shared Signal Discovery** first-message style: short, casual, references
      the real observed signal/theme or public conversation. It may mention the
      engagement source only when the source evidence supports it. Do not say
@@ -1043,7 +1073,10 @@ and verify current-revision sample messages before final completion.
      relevant" in Shared Signal Discovery samples. Translate source/tool terms
      into prospect-facing business language; do not put internal workflow
      vocabulary such as "Codex-style workflow", "MCP", "agent workflows", or
-     "Claude-style agent workflows" in customer-facing message one.
+     "Claude-style agent workflows" in customer-facing message one. Also avoid
+     generic product-process nouns such as "dashboard", "workflow", "source",
+     "send-ready copy", "reviewed prospect lists", and "sequence" unless the
+     recipient's own product/category makes that exact word buyer-native.
      Short form: Shared Signal Discovery uses no self-intro such as "I'm building Sellable".
      Short form: Shared Signal Discovery uses no self-intro such as "We're building Sellable".
      Short form: Shared Signal Discovery uses no "I've put together".
@@ -1068,6 +1101,11 @@ and verify current-revision sample messages before final completion.
      as "Sellable is a GTM system" across samples; every reviewed cold sample
      should be specific enough to the role, company, or problem that the three
      sample messages do not share the same body skeleton.
+     Do not use mechanical Sellable process language such as "campaign idea into
+     prospects, filters, messages, and sequence setup", "sequence-prospects",
+     "dashboard overhead", "campaign map", "send-ready copy", or "reviewed
+     prospect lists" in final cold samples. Say the buyer problem and one plain
+     outcome instead.
      Before Message Drafting runs, the campaign brief must already forbid
      self-intros, generic product summaries, opt-out shrugs, product-stack
      dumps, and repeated template structure. Do not let the first generation

package/skills/generate-messages/SKILL.md

@@ -228,12 +228,16 @@ must choose a signal-led, event-led, job-post-led, or proof-led motion from the
 current brief and row evidence instead of inheriting a preset first-message
 template.
 Post-engager first messages should thank the prospect for the support on the
-sender-owned post before asking the light relevance question. Prefer the gold
-shape `Thanks for the support on my post about {{post_topic_line}}` over
+sender-owned post and then stop. Do not add a relevance question, CTA, product
+line, meeting ask, or extra paragraph after the thank-you opener unless the
+operator explicitly asks for a longer first message. Prefer the gold shape
+`Thanks for the support on my post about {{post_topic_line}}` over
 surveillance-flavored wording like `saw you pop up`, unless the sender explicitly
 asks for that older wording.
 Short form: use the CXConnect Post-Engager Warm Reply-Rate Pattern only when the source is sender-owned Post Engagers.
 Short form: Never use that warm post-engager pattern for Shared Signal Discovery or Shared Cold Fallback.
+Short form: Post-engager warm first messages stop after the thank-you line.
+Short form: Do not add `curious`, `open to`, `trying to`, product copy, or a CTA after the post-engager thank-you line.
 
 ### Shared Cold Fallback quality bar
 
@@ -245,6 +249,12 @@ must read like final create-campaign/generate-messages output.
 - Ask one clear buyer problem question.
 - Keep the product line minimal and buyer-readable; do not turn the note into a
   product-stack dump.
+- Do not describe Sellable as a process checklist such as "campaign idea into
+  prospects, filters, messages, and sequence setup"; that reads like internal
+  product plumbing, not a buyer reason to reply.
+- Do not use awkward product-process nouns in reviewed cold samples:
+  `sequence-prospects`, `dashboard overhead`, `campaign map`, `send-ready copy`,
+  `reviewed prospect lists`, or "one campaign would look like" as a default CTA.
 - Use no self-intro such as "We're building" or "We're working on a way" in the
   reviewed samples.
 - Use no opt-out shrug such as "If this isn't relevant, ignore me."
@@ -266,6 +276,10 @@ or a founder self-intro.
 - Do not put internal workflow vocabulary in buyer-facing copy: `Codex`, `MCP`,
   `Claude-style agent workflows`, `agent workflows`, `workflow table`, `lead
   source`, or `signal discovery`.
+- Do not use `Claude`, `Codex`, `MCP`, `agent`, `dashboard`, `workflow`,
+  `source`, `sequence`, `send-ready copy`, or `reviewed prospect list` as
+  buyer-facing explanation in shared evergreen samples unless the buyer's own
+  company/product category uses that exact word and the line still sounds human.
 - Write a concrete signal/problem bridge instead of a relevance hedge. Good
   shapes are `the AI-assisted GTM conversations keep coming back to [buyer
   problem]`, `teams trying to turn LinkedIn signal into pipeline usually hit