@sellable/mcp 0.1.133 → 0.1.134

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.133",
+  "version": "0.1.134",
   "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,18 @@ 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 the watch link for the live campaign shell. If the question panel would
+  appear without a preceding `Watch link:` line, stop and send the link 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

@@ -443,6 +443,8 @@
             "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 +454,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,9 @@ 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 this `Watch link:` line has appeared in normal chat text.
+
 Cool, let's find leads.
 ```