@sellable/mcp 0.1.133 → 0.1.135

package/dist/tools/campaigns.d.ts

@@ -568,6 +568,12 @@ export interface CreateCampaignResult {
     watchUrl: string;
     resumed?: boolean;
     warning?: string;
+    approvalGate: {
+        kind: "brief-review";
+        mustShowBeforeQuestion: string[];
+        questionToolBlockedUntilShown: true;
+    };
+    nextStep: string;
 }
 export declare function createCampaign(input: CreateCampaignInput): Promise<CreateCampaignResult>;
 export interface UpdateCampaignResult {

package/dist/tools/campaigns.js

@@ -658,6 +658,20 @@ function deriveOfferValue(name, briefContent) {
         return heading.slice(0, 120);
     return lines[0].slice(0, 120);
 }
+function buildBriefApprovalGate(watchUrl) {
+    return {
+        approvalGate: {
+            kind: "brief-review",
+            mustShowBeforeQuestion: [
+                "the full campaignBrief markdown the user is approving",
+                `Watch link: ${watchUrl}`,
+            ],
+            questionToolBlockedUntilShown: true,
+        },
+        nextStep: "Before asking for approval, render the full campaign brief in normal chat text and then print " +
+            `Watch link: ${watchUrl}. Do not call AskUserQuestion or request_user_input until the user has seen both the brief content and this watch link.`,
+    };
+}
 export async function createCampaign(input) {
     const api = getApi();
     const config = getConfig();
@@ -675,6 +689,7 @@ export async function createCampaign(input) {
             createdAt: existing.createdAt,
             currentStep: existing.currentStep ?? null,
             watchUrl,
+            ...buildBriefApprovalGate(watchUrl),
             resumed: true,
             warning: hasCreateFields
                 ? "campaignId provided; resume mode ignores create fields."
@@ -790,6 +805,7 @@ export async function createCampaign(input) {
         createdAt: result.createdAt,
         currentStep: result.currentStep,
         watchUrl,
+        ...buildBriefApprovalGate(watchUrl),
     };
 }
 export async function updateCampaign(campaignId, input) {

package/package.json

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

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

@@ -427,13 +427,20 @@ brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   not visible in this session, use `Approve brief + compare source paths`
   instead. The customer approves the sourcing decision, not the host
   implementation detail.
-  Include a `Watch link:` line before the approval question once
-  `create_campaign` has returned `watchUrl`. The visible brief must come before
-  any optional debug persistence. After the brief is synthesized, render the
-  approval-ready brief in chat and create/update the campaign shell before any
-  visible `mkdir`, `Write`, artifact-copy, or similar local draft setup. In
-  normal customer runs, skip local draft setup entirely. File/folder creation is
-  not the user's value moment; the live campaign brief is.
+  Include a `Watch link:` line in the normal chat text immediately before the
+  brief approval question once `create_campaign` has returned `watchUrl`. This
+  is a hard gate for `AskUserQuestion` / `request_user_input`: do not ask
+  `Approve this brief before I start finding leads?` until the user has already
+  seen both (1) the full brief content being approved and (2) the watch link for
+  the live campaign shell. A summary like `the brief is visible there` is not a
+  valid approval surface. If the question panel would appear without the full
+  brief and a preceding `Watch link:` line, stop and render those first.
+  The visible brief must come before any optional debug persistence. After the
+  brief is synthesized, render the approval-ready brief in chat and
+  create/update the campaign shell before any visible `mkdir`, `Write`,
+  artifact-copy, or similar local draft setup. In normal customer runs, skip
+  local draft setup entirely. File/folder creation is not the user's value
+  moment; the live campaign brief is.
 
   The approval question can be based on the rendered brief in chat and the live
   campaign brief. Do not wait for file-write chrome before asking for approval.

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

@@ -439,10 +439,13 @@
             "then I will find good-fit leads"
           ],
           "minimumVisibleBriefDetail": "full_readable_brief_before_question",
+          "forbiddenSubstituteApprovalSurface": "Do not replace the visible brief with a summary like `the brief is visible there`; the user must see the actual campaign brief content in chat before the approval question.",
           "requiredCampaignLinks": [
             "watchUrl"
           ],
           "campaignLinkTiming": "before_approval_question",
+          "questionToolGate": "Do not call AskUserQuestion or request_user_input for brief approval until the immediately preceding customer-visible chat text includes `Watch link:` with the create_campaign.watchUrl for this campaign shell.",
+          "missingWatchLinkRecovery": "If the brief approval question would appear before the watch link, stop and send the rendered brief checkpoint plus `Watch link: {watchUrl}` first; then ask the approve/revise question.",
           "forbiddenNormalCustomerLinks": [
             "brief.md",
             "local draft path",
@@ -452,6 +455,12 @@
         },
         {
           "action": "ask_continue_or_revise_only_if_needed",
+          "requiresPriorVisibleContent": [
+            "full readable brief",
+            "live campaign shell orientation",
+            "Watch link: {watchUrl}"
+          ],
+          "mustNotCallQuestionToolUntil": "The watch link has already been shown in normal chat text after create_campaign returned watchUrl.",
           "autoContinueWhen": {
             "artifactStatus": "confirmed",
             "confidenceIn": [

package/skills/create-campaign-v2/references/watch-link-handoff.md

@@ -46,6 +46,11 @@ real-time updates from your signed-in session.
 
 Command-Enter or click that link to watch it in Sellable.
 
+Now ask the brief approval question. Do not show the approve/revise question
+panel until the full brief content and this `Watch link:` line have appeared in
+normal chat text. A summary such as "the brief is visible there" is not enough
+for approval.
+
 Cool, let's find leads.
 ```