@sellable/mcp 0.1.66 → 0.1.67

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.66",
+  "version": "0.1.67",
   "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,8 +363,18 @@ 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.
+  `mkdir`, `Write`, artifact-copy, or similar local draft setup. When the host
+  supports sidecar/background work, let a background writer persist `brief.md`
+  while the main thread keeps the brief review moving. If no background writer
+  is available, write `brief.md` synchronously only after the visible brief is
+  already in chat. File/folder creation is not the user's value moment; the
+  brief is.
+
+  The approval question can be based on the rendered brief in chat. Do not wait
+  for file-write chrome before asking for approval. Before lead sourcing or any
+  downstream step reads `brief.md`, reconcile that the persisted file matches
+  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:
   `Cool. Now I'm going to find people who are both a good fit and likely to

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

@@ -162,12 +162,17 @@
             "Risks",
             "After approval"
           ],
-          "mustRunBefore": ["write_artifact", "Bash", "mkdir"],
+          "mustRunBefore": ["start_background_artifact_writer", "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": "write_artifact",
-          "artifact": "brief.md"
+          "action": "start_background_artifact_writer",
+          "artifact": "brief.md",
+          "mode": "sidecar_when_host_supports_background_agents",
+          "shouldNotBlockMainThread": true,
+          "allowedToRunWhileUserReviewsInlineBrief": true,
+          "fallback": "If no background writer is available, write brief.md synchronously only after the approval-ready brief is already visible in chat.",
+          "chatRenderRule": "Do not surface folder/file-write progress in chat unless the write fails or the user asks. The main thread should keep the brief review moving while the sidecar persists brief.md."
         },
         {
           "action": "ask_source_intake_after_strategy_batch",
@@ -254,7 +259,7 @@
           ],
           "minimumVisibleBriefDetail": "full_readable_brief_before_question",
           "requiredArtifactLinks": ["brief.md"],
-          "artifactLinkTiming": "before_approval_question",
+          "artifactLinkTiming": "when_ready_before_downstream",
           "avoidQuestionWhenOnlyUsefulAnswerIs": "looks good"
         },
         {
@@ -265,9 +270,16 @@
             "noOpenStrategicTradeoff": true,
             "noMissingRequiredInputs": true
           }
+        },
+        {
+          "action": "ensure_background_artifact_ready",
+          "artifacts": ["brief.md"],
+          "requiredBeforeTransition": "find-leads",
+          "reconcileRule": "Before lead sourcing reads brief.md, verify the sidecar persisted the same brief shown in chat. If the sidecar is still running, wait quietly or finish the write synchronously; if it differs, reconcile to the visible approved brief.",
+          "chatRenderRule": "Do not block the brief approval question on this step. Only mention artifact persistence if it fails or needs user action."
         }
       ],
-      "requiredArtifacts": ["brief.md"],
+      "requiredArtifacts": [],
       "producesArtifacts": [],
       "allowedTools": [
         "AskUserQuestion",