@sellable/install 0.1.97 → 0.1.99

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

@@ -11,11 +11,14 @@ campaign state. The main thread owns approval and campaign writes.
 Use the live campaign inputs supplied by the parent thread:
 
 - `campaignId`
+- campaign revision or `campaignUpdatedAt`
 - `campaignBrief` / campaign brief content model
 - selected source decision and provider state
 - `selectedLeadListId` or selected source list context
 - `workflowTableId`
-- imported review-batch rows from that selected list
+- imported review-batch rows from that selected list, including row IDs and a
+  review-batch row hash when available
+- filter basis at branch start: `pending`, `use-filters`, or `skip-filters`
 - any already-saved fit/rubric result summaries supplied by the parent
 
 Do not require or hunt for `brief.md`, `lead-review.md`, or `lead-sample.json`.
@@ -23,6 +26,13 @@ Those files are optional debug context only when the parent explicitly provides
 them. Never inspect the product database directly, never run `psql`, and never
 read stale local markdown files to reconstruct campaign state.
 
+All live reads must come from scoped MCP/product tools by campaign and
+workspace, such as `get_campaign`, `get_campaign_context`, and
+`get_rows_minimal({ tableId: workflowTableId })`, or from equivalent parent
+thread payloads. Reject the task as `blocked` if the campaign id, workspace,
+`selectedLeadListId`, `workflowTableId`, or review-batch row ids do not match
+the branch input.
+
 ## Required First Steps
 
 1. Load the full long-form generate-messages prompt:
@@ -45,11 +55,31 @@ Return the following to the parent thread:
 - one rendered good-fill sample for a plausible passing review-batch row
 - one omit/fallback sample when the row signal is not safe
 - pass/fail notes against the generate-messages quality gates
+- compact runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
+- basis token containing campaign revision/updatedAt, brief hash,
+  `selectedLeadListId`, `workflowTableId`, review-batch row ids/hash, filter
+  choice, and rubric/filter basis when present
+- output timestamp/hash and any retry/error detail
 
 Write `message-validation.md`, `message-prep.md`, or
 `message-candidate-drafts.md` only when the parent explicitly asks for debug
 artifacts. Normal live campaign runs can return the same content directly.
 
+When reporting branch runtime proof, use this shape under
+`watchNarration.workerDetails.messageDraftBuilder`:
+
+- `statusSource`: `branch` or `parent-thread-fallback`
+- `status`: `branch-running`, `fallback-active`, `spawn-failed`,
+  `fallback-superseded`, `branch-superseded`, `ready`, `blocked`,
+  `retry-needed`, or `stale`
+- `runId` or `fallbackId`
+- `startedAt` and `updatedAt`
+- `basisToken` and `basis`
+- optional `compactOutputRef`, `compactOutput`, 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 bounded review batch.
+
 ## Hard Rules
 
 - Do not call product Generate Message cells. This worker drafts the template

package/agents/registry.json

@@ -225,10 +225,10 @@
       ],
       "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only",
       "codex": {
-        "description": "Message Draft Builder for campaign-backed template proposals and sample messages after source approval.",
+        "description": "Message Draft Builder for campaign-backed template proposals after confirm_lead_list imports a non-empty bounded review batch.",
         "model": "gpt-5.5",
         "modelReasoningEffort": "high",
-        "sandboxMode": "workspace-write",
+        "sandboxMode": "read-only",
         "nicknameCandidates": [
           "Message Draft Builder",
           "Draft Builder",
@@ -236,19 +236,17 @@
         ]
       },
       "claude": {
-        "description": "Use proactively as Message Draft Builder after lead source approval to propose an approved-template candidate and sample message from campaign state.",
+        "description": "Use proactively as Message Draft Builder after confirm_lead_list imports a non-empty bounded review batch; load the full generate-messages prompt and draft only from scoped campaign/tool state.",
         "model": "inherit",
         "background": true,
         "maxTurns": 10,
         "color": "magenta",
         "tools": [
           "Read",
-          "Write",
-          "Edit",
-          "Grep",
-          "Glob",
           "mcp__sellable__get_subskill_prompt",
-          "mcp__sellable__get_subskill_asset"
+          "mcp__sellable__get_campaign",
+          "mcp__sellable__get_campaign_context",
+          "mcp__sellable__get_rows_minimal"
         ]
       }
     }

package/agents/source-scout-linkedin-engagement.md

@@ -8,9 +8,10 @@ Required first step:
   draft `campaignOfferId`, call `get_provider_prompt({ provider:
 "signal-discovery", campaignOfferId, confirmed: true })` and include that same
   `campaignOfferId` plus `currentStep: "signal-discovery"` in `search_signals`
-  so the user can watch source work in the campaign UI. Treat that as a
-  campaign-attached persisted search; do not run a post-mint search without the
-  campaign ID. If no campaign ID is supplied, run campaignless preview mode.
+  so the owning search route can show the source lane with current find-leads
+  narration and user options. Treat that as a campaign-attached persisted
+  search; do not run a post-mint search without the campaign ID. If no campaign
+  ID is supplied, run campaignless preview mode.
 
 Use the inherited Sellable MCP tools when available:
 
@@ -44,6 +45,8 @@ sales Claude`; do not treat broad anchor-only lanes like `Claude Code`, `MCP`,
 campaignOfferId, selectionMode: "replace", selections, headlineICPCriteria,
 currentStep: "signal-discovery" })` before sampling so the watched Signal
    Discovery table shows the promoted posts and the exact posts being tested.
+   Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
+   visible transition after source approval.
 6. Fetch or sample engagers for promoted posts and score rough ICP fit from
    visible headline/display-name cues only. Do not enrich people during
    viability estimation.

package/agents/source-scout-prospeo-contact.md

@@ -8,10 +8,12 @@ Required first step:
   draft `campaignOfferId`, call `get_provider_prompt({ provider: "prospeo",
 campaignOfferId, confirmed: true })` and include that same `campaignOfferId`
   plus `currentStep: "prospeo"` in `search_prospeo` so the user can watch source
-  work in the campaign UI. If no campaign ID is supplied, run campaignless
-  preview mode. Treat post-mint
+  work in the campaign UI with source-lane narration owned by the search route.
+  If no campaign ID is supplied, run campaignless preview mode. Treat post-mint
   searches with `campaignOfferId` as campaign-attached persisted search tabs;
   do not run a live campaign search without the campaign ID.
+  Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
+  visible transition after source approval.
 
 Use the inherited Sellable MCP tools when available:
 

package/agents/source-scout-sales-nav.md

@@ -8,10 +8,12 @@ Required first step:
   draft `campaignOfferId`, call `get_provider_prompt({ provider: "sales-nav",
 campaignOfferId, confirmed: true })` and include that same `campaignOfferId` in
   `search_sales_nav` with `currentStep: "sales-nav"` so the user can watch
-  source work in the campaign UI. If no campaign ID is supplied, run
-  campaignless preview mode. Treat post-mint
+  source work in the campaign UI with source-lane narration owned by the search
+  route. If no campaign ID is supplied, run campaignless preview mode. Treat post-mint
   searches with `campaignOfferId` as campaign-attached persisted search tabs;
   do not run a live campaign search without the campaign ID.
+  Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
+  visible transition after source approval.
 
 Use the inherited Sellable MCP tools when available:
 

package/bin/sellable-install.mjs

@@ -509,7 +509,6 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__get_provider_prompt",
   "mcp__sellable__get_source_scout_registry",
   "mcp__sellable__get_post_find_leads_scout_registry",
-  "mcp__sellable__get_message_prompt",
   "mcp__sellable__get_active_workspace",
   "mcp__sellable__list_senders",
   "mcp__sellable__get_sender",
@@ -936,10 +935,11 @@ updates.
    watch link and see useful setup state immediately. Import only the first
    bounded review batch after the source is attached to the campaign; do not
    queue workflow cells, attach a sequence, or start until filter choice is
-   resolved, Messages has shown Use Template / AI Generated, template/token
-   rules are approved when Use Template is chosen, rubrics are saved and the
-   bounded review-batch \`enrichCellId\` cells have been queued when filters are
-   enabled, and the approved message set is synced into the campaign brief.
+   resolved, rubrics are saved when filters are enabled, template/token rules
+   are approved on the default Use Template path, and the approved message set
+   is synced into the campaign brief. After rubrics save, pause and say the fit
+   rules are saved; approve the message template next; after approval, queue the
+   bounded review-batch \`enrichCellId\` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval. AI Generated uses the
    product's AI-generated path and cancels or ignores the background template

package/package.json

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

package/skill-templates/create-campaign.md

@@ -13,7 +13,6 @@ allowed-tools:
   - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_source_scout_registry
   - mcp__sellable__get_post_find_leads_scout_registry
-  - mcp__sellable__get_message_prompt
   - mcp__sellable__get_active_workspace
   - mcp__sellable__list_senders
   - mcp__sellable__get_sender
@@ -71,10 +70,11 @@ Disk artifacts are optional debug/UAT diagnostics; normal customer runs should
 not create, link, or surface local draft files unless the user explicitly asks
 for them. Resume, gating, and handoff read campaign state first. The
 watchable campaign exists after the short brief; lead import is bounded to the
-first review batch. After that, the user chooses whether to use filters or skip,
-then Messages first shows Use Template and AI Generated. The Message Draft
-Builder may work in the background, but template review waits for the filter
-path and an explicit Use Template choice.
+first review batch. After that, the user chooses whether to use filters or skip.
+When filters are chosen, save rubrics, then pause before queueing enrichment or
+filtering: tell the user the fit rules are saved, the message template needs
+approval next, and enrichment/filtering will start after that approval. Use
+Template is the default message path; AI Generated is only an explicit opt-out.
 
 ## Opening Turn Contract
 
@@ -148,12 +148,13 @@ calls `get_post_find_leads_scout_registry`, then launches the returned
 filter-leads scout and message-generation scout together when real subagents are
 available and the current session exposes the returned names. Message
 generation is the provisional Message Draft Builder: it may start after the
-review batch exists, including while the user is on filter choice, but template
-review cannot start until the user answers filter choice and chooses Use
-Template in Messages. AI Generated is an explicit opt-out that cancels or
-ignores the background template draft. If the post-lead agents are absent, the
-main thread still orchestrates the same branches from the compact context with
-MCP tools/assets.
+review batch exists, including while the user is on filter choice, but workflow
+cell execution must wait. After rubrics are saved, do not queue enrichment,
+filtering, or Generate Message cells until the user approves the message
+template. AI Generated is an explicit opt-out that cancels or ignores the
+background template draft. If the post-lead agents are absent, the main thread
+still orchestrates the same branches from the compact context with MCP
+tools/assets.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
 lines short, use indexed section labels and bullets, and translate internal
@@ -574,10 +575,11 @@ updates.
    watch link and see useful setup state immediately. Import only the first
    bounded review batch after the source is attached to the campaign; do not
    queue workflow cells, attach a sequence, or start until the filter choice is
-   resolved, Messages has shown Use Template / AI Generated, template/token
-   rules are approved when Use Template is chosen, rubrics are saved and the
-   bounded review-batch `enrichCellId` cells have been queued when filters are
-   enabled, and the approved message set is synced into the campaign brief.
+   resolved, rubrics are saved when filters are enabled, template/token rules
+   are approved on the default Use Template path, and the approved message set
+   is synced into the campaign brief. After rubrics save, pause and say the fit
+   rules are saved; approve the message template next; after approval, queue the
+   bounded review-batch `enrichCellId` cells to kick off enrichment/filtering.
    Product Generate Message cells must not run from the background template
    path before that template/token approval.
    Do not ask the user to approve the brief before shell creation unless they