@sellable/mcp 0.1.46 → 0.1.47

package/package.json

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

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

@@ -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-v1.md` is an internal first-draft snapshot; `brief.md` is
+the current customer-facing and 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 /
@@ -317,7 +317,7 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   persistence in this preamble.
 
 - Before asking for brief approval, render a slim approval brief in the chat and
-  keep the rich brief in `brief-v1.md` / `brief.md`. Do not ask the user to
+  keep the rich current brief in `brief.md`. Do not ask the user to
   approve a one-paragraph direction, a risk note, or hidden artifact they cannot
   inspect. The chat approval view should be skimmable in under 45 seconds; full
   reasoning, source notes, and robustness stay in the artifacts. Include these
@@ -357,7 +357,7 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   brief, include only:
 
   ```text
-  Open artifacts: [brief-v1.md] and [brief.md]
+  Open artifact: [brief.md]
   ```
 
   If clickable links cannot be created, show one compact fallback line:
@@ -377,8 +377,7 @@ me`, `I’ll paste a different sender profile`, and `Other / custom`.
   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`.
-  Include `Open artifacts:` links to `brief-v1.md` and `brief.md` before the
-  approval question.
+  Include an `Open artifact:` link to `brief.md` before the approval question.
 
 - 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
@@ -412,8 +411,13 @@ should test for this campaign. Those can run in parallel and usually take
   `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-v1.md` is only an internal first-draft snapshot. Do not show it in the
+  normal user-facing approval view. `brief.md` is the stable downstream input,
+  current user-facing brief, and thesis source.
+- On brief edits or revisions, update `brief.md` directly. Do not run another
+  long brief-generation pass just to create `brief-v2.md`. If version history is
+  ever needed, create it only as a cheap local copy after the edit; never spend
+  model/research time writing duplicate versions.
 - `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/SOUL.md

@@ -94,9 +94,10 @@ Every customer-facing update should answer one of these:
 - What is protected until approval?
 
 Before a brief approval, the user should see a slim approval brief in chat. The
-rich brief still exists in `brief-v1.md` / `brief.md`; the chat view is the
-decision surface, not the full working memo. It should be skimmable in under 45
-seconds and include:
+rich current brief exists in `brief.md`; the chat view is the decision surface,
+not the full working memo. `brief-v1.md` is an internal first-draft snapshot, not
+part of the normal approval UI. It should be skimmable in under 45 seconds and
+include:
 
 - who we are targeting
 - why they should care

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

@@ -206,26 +206,26 @@
       "onEnter": [
         {
           "action": "show_brief_summary",
-          "artifact": "brief-v1.md"
+          "artifact": "brief.md"
         },
         {
           "action": "render_brief_approval_checkpoint",
           "requiredVisibleContent": [
             "Campaign brief",
-            "Who we are targeting",
-            "Why they should care",
+            "Target",
+            "Core pain",
             "Offer / CTA",
-            "Proof to use",
-            "Lead source hypothesis",
+            "Proof",
+            "Lead plan",
             "Message angle",
-            "Risks / assumptions",
-            "What happens after approval",
+            "Risks",
+            "After approval",
             "approve this brief",
             "revise the brief",
             "then I will find good-fit leads"
           ],
-          "minimumVisibleBriefDetail": "full_readable_brief_before_question",
-          "requiredArtifactLinks": ["brief-v1.md", "brief.md"],
+          "minimumVisibleBriefDetail": "slim_approval_brief_before_question",
+          "requiredArtifactLinks": ["brief.md"],
           "artifactLinkTiming": "before_approval_question",
           "avoidQuestionWhenOnlyUsefulAnswerIs": "looks good"
         },