@sellable/mcp 0.1.65 → 0.1.66

package/package.json

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

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

@@ -9,7 +9,7 @@ visibility: internal
 <role>
 You are the create-campaign-v2 orchestrator. Your job is to execute the
 configured `core/flow.v2.json` state machine from scratch: (1) interview the
-user and create `brief-v1`, (2) validate the chained Phase 84 draft artifacts,
+user and create `brief.md`, (2) validate the chained Phase 84 draft artifacts,
 (3) run a message-review gate, show the user an approval packet and commit
 gate, and (4) if the user
 approves, atomically mint a real `CampaignOffer` and hand off to the bounded
@@ -34,8 +34,8 @@ The JSON flow is the source of truth for stage order, `requiredArtifacts`,
 replace them.
 
 Each stage writes its own artifact into the draft directory before the next
-stage starts. `brief-v1.md` is the customer-facing brief output; `brief.md` is
-the canonical downstream campaign thesis input.
+stage starts. `brief.md` is the single customer-facing brief and canonical
+downstream campaign thesis input.
 
 After validation artifacts are complete, show the user a commit gate with 6
 choices (approve / revise-brief / revise-leads / revise-rubric /
@@ -51,7 +51,6 @@ Validated draft directory:
 
 ```text
 .sellable/create-campaign-v2/drafts/{workspace-slug}/{campaign-slug}/
-  brief-v1.md
   brief.md
   lead-review.md
   lead-sample.json
@@ -362,6 +361,10 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   Approval options should refer to what the user just read, e.g. `Approve this
 brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
   Include an `Open artifact:` link to `brief.md` before the approval question.
+  The visible brief must come before local persistence chrome. After the brief
+  is synthesized, render the approval-ready brief in chat before running visible
+  `mkdir`, `Write`, artifact-copy, or similar local draft setup. File/folder
+  creation is not the user's value moment; the brief is.
 
 - After the brief is approved or auto-confirmed, show the next progress line:
   `Cool. Now I'm going to find people who are both a good fit and likely to
@@ -390,13 +393,13 @@ should test for this campaign. Those can run in parallel and usually take
 
 - In hosted/rehearsal runs, `Bash` is only for safe local draft-directory
   housekeeping before approval: `mkdir`, `ls`, `find`, `test`, `pwd`, `echo`,
-  `cat`, or copying `brief-v1.md` to `brief.md` inside the repo. Do not use
+  or `cat` inside the repo. Do not use
   Bash to run interpreters/scripts (`python`, `node`, `npm`, `pnpm`, `yarn`,
   `npx`), call APIs, query databases, inspect prompt dumps, run git, or
   synthesize artifact content. Use `Read`/`Write`/`Edit` for artifact files and
   MCP tools for product actions.
-- `brief-v1.md` is the user-facing brief. `brief.md` is the stable downstream
-  input and remains the thesis source.
+- `brief.md` is the single user-facing brief and stable downstream thesis
+  source.
 - `lead-review.md` and `lead-sample.json` are the required outputs of `find leads`.
 - `lead-filter.md` is the primary output of `filter leads`.
 - `rubric.json` is optional and secondary to `lead-filter.md`.

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

@@ -12,7 +12,7 @@
   ],
   "events": [
     "bootstrap_complete",
-    "brief_v1_ready",
+    "brief_ready",
     "source_intake_ready",
     "user_brief_confirmed",
     "lead_review_ready",
@@ -139,7 +139,7 @@
             "campaignBrief": "~1-2 min"
           },
           "forbiddenWording": [
-            "brief-v1.md",
+            "brief.md",
             "lead-review.md",
             "lead-sample.json",
             "message-validation.md"
@@ -150,14 +150,24 @@
           "target": "create-campaign-brief"
         },
         {
-          "action": "write_artifact",
-          "artifact": "brief-v1.md"
+          "action": "render_brief_preview_before_artifact_write",
+          "requiredVisibleContent": [
+            "Campaign brief",
+            "Decision",
+            "Target",
+            "Pain",
+            "Offer",
+            "Proof",
+            "Lead plan",
+            "Risks",
+            "After approval"
+          ],
+          "mustRunBefore": ["write_artifact", "Bash", "mkdir"],
+          "chatRenderRule": "After synthesizing the brief, render the approval-ready brief in chat before any visible local folder creation, file write, or artifact copy. The user should see useful brief content before local persistence chrome. Do not ask the user to approve a hidden artifact."
         },
         {
-          "action": "copy_artifact",
-          "from": "brief-v1.md",
-          "to": "brief.md",
-          "reason": "brief.md remains the canonical downstream artifact name"
+          "action": "write_artifact",
+          "artifact": "brief.md"
         },
         {
           "action": "ask_source_intake_after_strategy_batch",
@@ -183,7 +193,7 @@
         }
       ],
       "requiredArtifacts": [],
-      "producesArtifacts": ["brief-v1.md", "brief.md"],
+      "producesArtifacts": ["brief.md"],
       "allowedTools": [
         "get_subskill_prompt",
         "get_subskill_asset",
@@ -211,9 +221,9 @@
         "start_campaign"
       ],
       "watchRequired": false,
-      "waitFor": ["brief_v1_ready", "confirm_with_user"],
+      "waitFor": ["brief_ready", "confirm_with_user"],
       "transitions": {
-        "brief_v1_ready": "brief-review",
+        "brief_ready": "brief-review",
         "confirm_with_user": "brief-review"
       },
       "optionalProducesArtifacts": ["lead-source-intake.json"]
@@ -224,7 +234,7 @@
       "onEnter": [
         {
           "action": "show_brief_summary",
-          "artifact": "brief-v1.md"
+          "artifact": "brief.md"
         },
         {
           "action": "render_brief_approval_checkpoint",
@@ -243,7 +253,7 @@
             "then I will find good-fit leads"
           ],
           "minimumVisibleBriefDetail": "full_readable_brief_before_question",
-          "requiredArtifactLinks": ["brief-v1.md", "brief.md"],
+          "requiredArtifactLinks": ["brief.md"],
           "artifactLinkTiming": "before_approval_question",
           "avoidQuestionWhenOnlyUsefulAnswerIs": "looks good"
         },
@@ -257,7 +267,7 @@
           }
         }
       ],
-      "requiredArtifacts": ["brief-v1.md", "brief.md"],
+      "requiredArtifacts": ["brief.md"],
       "producesArtifacts": [],
       "allowedTools": [
         "AskUserQuestion",
@@ -326,7 +336,7 @@
           "artifacts": ["lead-review.md", "lead-sample.json"]
         }
       ],
-      "requiredArtifacts": ["brief-v1.md", "brief.md"],
+      "requiredArtifacts": ["brief.md"],
       "producesArtifacts": ["lead-review.md", "lead-sample.json"],
       "allowedTools": [
         "get_subskill_prompt",

package/skills/create-campaign-v2/core/policy.md

@@ -52,7 +52,7 @@ gate is the only mandatory pre-mint approval gate.
 The minimum pre-approval chain is:
 
 ```text
-brief-v1.md / brief.md
+brief.md
 lead-review.md
 lead-sample.json
 lead-filter.md