@sellable/mcp 0.1.81 → 0.1.82

package/package.json

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

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

@@ -589,8 +589,9 @@ workstreams`, `in parallel`, or `background` unless parallel branches were
   `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 lead
-  import, workflow-table processing, sequence attach, or start.
+  run. This critique can recommend a decision, but it can never replace
+  `approve-message` for lead import, workflow-table processing, sequence attach,
+  or start.
 
 </rules>
 
@@ -601,8 +602,8 @@ There are two human gates:
 - `message-review` is the mandatory pre-import message quality gate. It asks
   only whether to proceed with the selected message (`approve-message`) or run
   one more messaging revision (`revise-messaging`). `approve-message` authorizes
-  syncing the approved message set into the campaign brief and importing the
-  bounded 10-lead test batch only.
+  syncing the approved message set into the campaign brief, saving rubrics,
+  importing the bounded 10-lead test batch, and queueing/observing that sample.
 - The sender/settings/sequence handoff is the launch gate. Starting the campaign
   still waits until a sender is attached, the sequence is accepted, and the user
   greenlights start.

package/skills/create-campaign-v2/core/flow.v2.json

@@ -1216,12 +1216,12 @@
         "request_user_input"
       ],
       "toolRules": [
-        "Before writing message-validation.md, message-review.md, approval-packet.md, or a commit-gate AskUserQuestion, the current run must read 100% of the real generate-messages prompt via chunked get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) calls.",
+        "Before writing message-validation.md, message-review.md, or a message-review AskUserQuestion, the current run must read 100% of the real generate-messages prompt via chunked get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) calls.",
         "Lead Sample Basis must cite rows from lead-sample.json produced by find-leads. lead-filter.md only gates those rows; it is not a source for a new sample.",
         "Do not hand-write message-validation.md from message-prep.md, message-candidate-drafts.md, or general campaign knowledge.",
         "message-validation.md must prove the full generate-messages workflow ran: Gold Standard Strategy Map, Proof Inventory, Token Fill Rules, Token Adherence Table, Angle Drafts, Kill / Combine Review, Finalists, Finalizer Pass, Gold-Standard Quality Gate, Skeptical Prospect Review, Winner Gate, and a raw sendable Selected Winner are required before message-review can recommend approve-message.",
         "If the Codex-hosted output is plausible but weaker than the loaded gold-standard examples, stop at message-review with revise-messaging. Do not continue to approval or mint just because the mechanical flow worked.",
-        "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 review is ready but the generate-messages prompt was not retrieved in this run, route back to message-generation instead of asking the user to approve the message.",
         "The approved message set must be written back into campaignBrief before validate-sample queues the review-batch cascade."
       ],
       "doNotAllow": [