@sellable/mcp 0.1.79 → 0.1.80

package/package.json

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

package/skills/create-campaign-v2/SKILL.md

@@ -548,6 +548,12 @@ Message` rendered as the recipient would see it, in addition to the approved
   settings review in the pre-mint approval packet. Those come after mint. The
   pre-mint packet approves only the brief, lead source, lead filter/rubric, and
   first message direction.
+- Do not include post-accept DMs, connection-accepted follow-ups, day-2 / day-7
+  follow-ups, second touches, reply branches, or any other sequence-shaped copy
+  in `message-review.md` or the pre-mint approval packet. If
+  `message-validation.md` contains those, mark the message review as
+  `revise-messaging` and route back to message generation even if the artifact
+  says `Status: confirmed`.
 - Persist `customer-roleplay.md` when a customer/operator roleplay critique is
   run. This critique can recommend a decision, but it can never authorize mint.
 - Persist `commit-gate-decision.md` with exactly one of the six gate choices.
@@ -1018,7 +1024,7 @@ mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages", offset,
 
 Continue chunked-read until `hasMore=false`. Treat all chunks as one prompt load. Follow it verbatim once loaded. The same directive is locked in `flow.v2.json::messageGeneration.toolRules`.
 
-Do NOT proceed to Step 4 (message review gate) without loading and following the full generate-messages workflow. `message-validation.md` must prove the full workflow ran (all required sections present + raw sendable Selected Winner) before `message-review.md` can recommend `approve-message`. If the message review or approval packet is ready but the generate-messages prompt was not retrieved in this run, route back to message-generation instead of asking the commit gate.
+Do NOT proceed to Step 4 (message review gate) without loading and following the full generate-messages workflow. `message-validation.md` must prove the full workflow ran (all required sections present + raw sendable Selected Winner + explicit single-send-unit PASS) before `message-review.md` can recommend `approve-message`. If the message review or approval packet is ready but the generate-messages prompt was not retrieved in this run, route back to message-generation instead of asking the commit gate. If `message-validation.md` contains post-accept DM, follow-up, second-touch, cadence, branch, or other sequence-shaped copy, do not summarize it as ready; route back to message-generation and require a single first outbound send.
 
 ## Tail (MANDATORY TOOL ORDER + Steps 13-16 + Threshold Trips + Hard Rules)
 

package/skills/create-campaign-v2/references/approval-gate-framing.md

@@ -81,9 +81,13 @@ populated:
   `Required Keep Rules`, `Required Exclude Rules`, `Pass Rate`,
   `Recommendation`, and `Implementation Details` sections
 - `message-validation.md` has `Status: confirmed`, `Mode: DRY MODE (no DB mutation)`,
-  a `Selected Winner`, and a non-empty `Token Adherence Table`
+  a `Selected Winner`, a non-empty `Token Adherence Table`, and an explicit
+  single-send-unit PASS with no post-accept DM, follow-up, cadence, branch, or
+  sequence-shaped copy in the first-message artifact
 
-An empty anchor blocks `approve`. The user can still pick a revision choice.
+An empty anchor blocks `approve`. Sequence-shaped message output also blocks
+`approve` even when the copy quality is otherwise strong. The user can still
+pick a revision choice.
 
 ## Approval Packet
 
@@ -154,6 +158,14 @@ review in the pre-mint approval packet. Those are configured and reviewed after
 the campaign is created in the autonomous tail. The pre-mint packet approves
 only the brief, lead source, lead filter/rubric, and first message direction.
 
+Do not include or summarize post-accept DMs, connection-accepted follow-ups,
+day-2 / day-7 follow-ups, second touches, reply branches, or any other
+sequence-shaped copy in `message-review.md` or `approval-packet.md`. If
+`message-validation.md` contains those, mark the message review as
+`Recommendation: revise-messaging` and route back to message generation. Do not
+approve by selecting only the first part of the sequence; the validation
+artifact itself must be corrected so the approved template is unambiguous.
+
 The packet must include a dedicated `## Message Review` section immediately
 before `## Approved Message Template`. This is the customer-facing messaging
 gate. It should not be a raw validation dump; it should answer:
@@ -169,6 +181,9 @@ draft if useful, mark `Recommendation: revise-messaging`, and route the user to
 the `revise-messaging` commit-gate option instead of implying the campaign is
 ready.
 
+If the validation contains post-accept DM or follow-up copy, treat it exactly
+like `revise-message` even if the artifact says `Status: confirmed`.
+
 If `message-validation.md` has an extractable `Selected Winner`, the packet's
 `## Approved Message Template` must use that winner exactly, except for
 supported prospect-row `{{tokens}}`. Do not write a fresh approval-template

package/skills/generate-messages/SKILL.md

@@ -561,6 +561,11 @@ The winner entry must:
   `[insert ...]`, or `[generated ...]`. If the only scalable option needs a
   deferred per-row instruction, route to `revise-message` and fix the
   token plan instead.
+- contain exactly one outbound send unit. Do not include post-accept DMs,
+  follow-ups, second touches, cadence branches, sequence notes, or later-message
+  copy in the Selected Winner or nearby rendered examples. If a later message
+  idea is useful, keep it out of the generated first-message artifact and put it
+  in an internal finding for post-mint sequence work.
 - never use generic signal tokens like `{{recentSignal}}`,
   `{{recent_signal}}`, or `{{recent_signal_quote}}`. If row personalization
   is needed in the raw selected winner, render the concrete sentence from
@@ -1046,6 +1051,41 @@ This applies to:
 
 Truth is not enough. The line must do a job for the prospect.
 
+### Single-send-unit gate (HARD INVARIANT)
+
+Dry-mode create-campaign-v2 message generation approves the **first outbound
+send only**. The Selected Winner must be exactly one send unit for one channel:
+one INVITE, one INMAIL_OPEN / INMAIL_CLOSED body plus optional subject, or one
+DM body when the campaign explicitly starts with DM.
+
+Do not generate, approve, or include sequence-shaped copy in
+`message-validation.md`, `message-review.md`, selected copy, rendered examples,
+token notes, findings, or recommendation text.
+
+Blocked sequence-shaped outputs include:
+
+- post-accept DMs
+- connection-accepted follow-ups
+- day-2 / day-7 follow-ups
+- second touches
+- "reply/acceptance" branches
+- cadence notes
+- fallback send paths as copy
+- any "INVITE + DM", "InMail + follow-up", or multi-step message plan
+
+If a proof, PS, Loom, setup link, or meta-demo line cannot fit in the first send
+unit, either compress it into that first send unit or omit it. Do not move it to
+a later message. Preserve the idea as an internal `Findings` note only if it is
+useful after campaign mint.
+
+Before returning `Status: confirmed`, run this explicit check:
+
+`Single send unit: PASS | BLOCKED — reason`
+
+If BLOCKED, set `Recommendation: revise-message` and rewrite the Selected
+Winner until it contains only the first outbound send. A message can be strong
+and still be invalid if it requires a post-accept DM or other sequence copy.
+
 Use the 4-block shape below as the default packaging only when it helps
 the reply reason land. If a different shape is more natural, shorter, or
 more compelling for this offer, use it and explain why in `Packaging
@@ -2216,6 +2256,8 @@ hiring for`
 - No semicolons or `X here` sender fragments: PASS | BLOCKED — reason
 - CTA is useful and low-friction: PASS | BLOCKED — reason
 - Every line has a prospect-side "so what?": PASS | BLOCKED — reason
+- Single send unit only, with no post-accept DM/follow-up/sequence copy:
+  PASS | BLOCKED — reason
 - Winner clearly beats rejected drafts: PASS | BLOCKED — reason
 - Decision: confirmed | revise-message | revise-filter
 
@@ -2247,6 +2289,8 @@ Automatic failures in dry mode:
 - no compelling proof element despite the brief supporting one
 - a CTA that depends on missing proof
 - copy that fails the Thomas revision filters
+- any post-accept DM, follow-up, second touch, cadence branch, or sequence copy
+  in the first-message validation artifact
 - any mutation tool usage
 
 ## Workflow