@sellable/mcp 0.1.85 → 0.1.86

package/package.json

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

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

@@ -363,9 +363,9 @@ Validated draft directory:
   `RevOps`, `outbound systems`, or `pipeline architecture` unless they are
   translated into what the user can understand.
 
-  After rendering that brief, ask for brief approval when there is a real
-  strategic choice or the user has not already made the direction obvious. The
-  user-facing choice should be approve/revise language, not "looks good".
+  After rendering that brief, ask for brief approval before lead sourcing in
+  hosted net-new runs. The user-facing choice should be approve/revise language,
+  not "looks good".
   Approval options should refer to what the user just read, e.g. `Approve this
 brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   When the user chose `Find people for me` and the host supports subagents,
@@ -389,13 +389,13 @@ brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   the visible approved brief; if the sidecar is still running, wait quietly or
   finish the write synchronously at that boundary.
 
-- After the brief is approved or auto-confirmed, show the next progress line:
+- After the brief is approved, show the next progress line:
   `Cool. Now I'm going to find people who are both a good fit and active enough
 to be worth a LinkedIn test. I'll compare source paths by expected volume,
 sampled ICP fit, activity/warmth signal, cleanup risk, and tradeoffs. This
 usually takes ~3-5 min, and I'll show you the source decision + sample before
 anything goes live.`
-- After the lead sample/source decision is ready and approved or auto-confirmed,
+- After the lead sample/source decision is ready and approved,
   show the next progress line:
   `Lead source is set. I'll import the first 10-row review batch into the
 campaign table, then use that same batch to tighten the fit filter and draft the
@@ -554,8 +554,14 @@ workstreams`, `in parallel`, or `background` unless parallel branches were
 
 <conditional_gates>
 
-There are two human gates:
+There are four customer-visible gates in the net-new hosted flow:
 
+- `brief-review` asks whether to approve the rendered campaign brief before
+  lead sourcing starts. Do not skip this by inferring approval from setup
+  answers.
+- `lead-review` / source decision asks whether to approve the selected source
+  path and sample before moving into filter/message work. Do not skip this by
+  compressing the source decision into message review.
 - `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