@sellable/install 0.1.204 → 0.1.205

package/agents/post-find-leads-message-scout.md

@@ -165,10 +165,15 @@ When reporting branch runtime proof, use this shape under
 - `runId` or `fallbackId`
 - `startedAt` and `updatedAt`
 - `basisToken` and `basis`
+- `basis.selectedLeadListId`, `basis.workflowTableId`, and either
+  `basis.reviewBatchRowHash` or non-empty `basis.reviewBatchRowIds`
 - optional `messageDraftOutputRef`, `messageDraftOutput`, and `error`
 
 Do not tell the UI to show Message Draft Builder as running unless this proof
 exists and points at the current non-empty campaign-table execution slice.
+Use `workerStatuses.messageDraftBuilder` only for simple badge text such as
+`running`; never put `runId`, `statusSource`, `status`, or `basis` under
+`workerStatuses`, and never use a `messageDrafting` key.
 If the host cannot launch a background branch and the parent thread runs this
 same contract inline, report `statusSource: "parent-thread-fallback"` and
 `status: "fallback-active"` while working, then `status: "ready"` when the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.204",
+  "version": "0.1.205",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -950,6 +950,13 @@ updates.
    background-agent tool is callable, start the same full message branch inline
    before filter drafting or skip-filter message review and record it as
    `statusSource: "parent-thread-fallback"`.
+   After a spawned branch starts, persist rich proof under
+   `watchNarration.workerDetails.messageDraftBuilder` with
+   `statusSource: "branch"`, `status: "branch-running"`, `runId`, timestamps,
+   selectedLeadListId, workflowTableId, filterChoice, and reviewBatchRowHash or
+   reviewBatchRowIds. `workerStatuses.messageDraftBuilder` is only the optional
+   simple badge (`running`); never put rich proof under `workerStatuses` or use
+   a `messageDrafting` key.
    Do not use any alternate, examples-only, or local-artifact message prompt. Message review and
    message QA require Message Drafting output:
    do not draft from a checklist, local markdown artifact, or parent-thread