@sellable/mcp 0.1.57 → 0.1.59

package/package.json

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

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

@@ -458,6 +458,14 @@ the message from the same sample.` Never say `kicking off two workstreams`,
   approval decision can be inspected later.
 - Before asking for commit approval, persist a customer-facing
   `approval-packet.md` so the exact packet can be inspected later.
+- The pre-mint approval packet must show exactly one concrete `## Sample
+Message` rendered as the recipient would see it, in addition to the approved
+  message template. Do not make the user mentally expand `{{tokens}}` at final
+  approval.
+- Do not include sequence, cadence, sending-window, mailbox, or campaign
+  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.
 - 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.

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

@@ -141,6 +141,19 @@ summary.
 4. **message validation** — the `Selected Winner` from `message-validation.md`,
    rendered as it will appear in the outbound, plus the `Findings` + `Recommendation`
 
+The inline approval packet must include exactly one concrete sample message
+rendered as the recipient would see it. Do not make the user mentally expand
+tokens at the final approval moment. If the selected winner contains supported
+prospect-row `{{tokens}}`, show the template in `## Approved Message Template`
+and also include a short `## Sample Message` section with one realistic filled
+example from the lead sample. Keep the full token rules in the artifact, not in
+the top chat summary.
+
+Do not include sequence, cadence, sending-window, mailbox, or campaign settings
+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.
+
 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: