@sellable/mcp 0.1.387 → 0.1.389

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.387",
+  "version": "0.1.389",
   "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

@@ -418,7 +418,7 @@ Tokenized shape:
 
 Hey there
 
-Saw you pop up on my post about {{post_topic_line}}
+Thanks for the support on my post about {{post_topic_line}}
 
 Curious, is this something you're dealing with right now?
 ```
@@ -429,6 +429,10 @@ Transfer rules:
   selected sender-authored post or use a safer source-specific phrase.
 - 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.
 - 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

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

@@ -271,6 +271,9 @@ side-effect caps, and the 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.
+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.
 After the receipt-directory `mkdir`, the next shell/tool call must launch the first lane worker.
 Do not run `find`, `ls`, extra inventory, or another preflight between directory setup and the first worker launch.
 For the local Codex CLI fallback, use this literal durable CLI worker launch template
@@ -534,7 +537,7 @@ verification unless the same object also appears inside
       "workflowAssetLoaded": true,
       "workerRuntime": "separate-codex-thread",
       "workerThreadId": "<visible local Codex thread id>",
-      "receiptArtifactPath": ".planning/artifacts/uat/69/lane-receipts/<planRevision>/<receiptRunId>/<actionId>-<laneKey>.json",
+      "receiptArtifactPath": "<receiptArtifactPath from workerDispatch.receiptArtifactHint>",
       "durableReceiptWritten": true,
       "notAdHoc": true
     },
@@ -772,7 +775,7 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
 
      Hey there
 
-     Saw you pop up on my post about {{post_topic_line}}
+     Thanks for the support on my post about {{post_topic_line}}
      ```
 
    - **Shared Signal Discovery** first-message style: short, casual, references
@@ -794,9 +797,18 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      generic greeting. It should open with a light role/company/problem
      observation, avoid awkward phrases like "looks like a team where", avoid
      founder-only first person unless every attached sender can credibly say it,
-     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.
+     and ask one clear problem question. It must not pass just because the
+     receipt says `generate-messages` loaded; the reviewed samples must sound
+     like final cold output from the create-campaign/generate-messages workflow.
+     Use no self-intro such as "We're building", no opt-out shrug such as "If
+     this isn't relevant, ignore me", and no product-stack dump that repeats
+     Sellable/Codex/Claude-Code feature summary
+     across prospects. This is a single-message cold path unless the approved
+     create-campaign message workflow proves a better delivery format.
+     Short form: Shared Cold Fallback must not pass just because the receipt says `generate-messages` loaded.
+     Short form: Shared Cold Fallback uses no self-intro such as "We're building".
+     Short form: Shared Cold Fallback uses no opt-out shrug such as "If this isn't relevant, ignore me".
+     Short form: Shared Cold Fallback uses no product-stack dump.
    - Every customer-visible lane must run Message Drafting from the current
      campaign/table basis after source rows exist. The worker must load the full
      packaged `generate-messages` prompt, every required asset, and
@@ -851,10 +863,14 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
       `validationResult:"passed"`, a passed quality review, and at least 3
       reviewed sample messages. For Shared Cold Fallback, reject samples that
       open with a standalone name followed by "Hey there" or a similarly generic
-      greeting. For all shared lanes, reject generic product-summary samples,
-      repeated near-identical samples, and any preserved Post Engagers opener;
-      revise or rerun the packaged create-campaign/generate-messages path before
-      reporting completion.
+      greeting. For Shared Cold Fallback, also reject samples with a self-intro
+      such as "We're building", an opt-out shrug such as "If this isn't
+      relevant, ignore me", or a product-stack dump that repeats the same
+      Sellable/Codex/Claude-Code feature summary across prospects. For all
+      shared lanes, reject generic product-summary samples, repeated
+      near-identical samples, and any preserved Post Engagers opener; revise or
+      rerun the packaged create-campaign/generate-messages path before reporting
+      completion.
    - The first review batch exists and at least 3 review rows have generated
      messages from the approved brief. If fewer than 3 usable rows exist, report
      the actual count and why.

package/skills/generate-messages/SKILL.md

@@ -227,9 +227,31 @@ when those shared lanes were sourced from engagement-like signals. Shared lanes
 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
+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.
 
+### Shared Cold Fallback quality bar
+
+Shared Cold Fallback is a true cold lane. It must not pass just because a receipt
+says `generate-messages` loaded or because generated cells exist. The samples
+must read like final create-campaign/generate-messages output.
+
+- Start from a concrete row-supported role/company/problem observation.
+- Ask one clear buyer problem question.
+- Keep the product line minimal and buyer-readable; do not turn the note into a
+  product-stack dump.
+- 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."
+- Do not repeat the same Sellable/Codex/Claude-Code product summary across
+  samples. If two samples would still read the same after replacing names and
+  companies, revise or rerun.
+
 ### Rich Personalization Contract
 
 The `create-campaign` asset `references/ai-native-tokens.md` is the canonical