@sellable/install 0.1.148 → 0.1.150

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

@@ -37,13 +37,13 @@ the branch input.
 
 ## Required First Steps
 
-1. Load the full long-form generate-messages prompt:
+1. Load the full normal-path message prompt:
 
-   `get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
-   until `hasMore` is false.
+   `get_subskill_prompt({ subskillName: "generate-messages" })`
 
-2. Use that prompt as the drafting contract. Do not use create-campaign
-   safety/checklist instructions as a substitute for the full prompt.
+2. Use that prompt as the drafting contract. Do not use any alternate prompt,
+   examples-only shortcut, or create-campaign safety/checklist instructions as a
+   substitute for the full message prompt.
 3. Draft only from the campaign brief, selected source context, and initial
    campaign-table execution slice rows supplied by the parent.
 4. Keep the work provisional until the user chooses `Use Template` in Messages.
@@ -57,7 +57,7 @@ Return the following to the parent thread:
 - one rendered good-fill sample for a plausible passing campaign-table 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`
+- message-draft runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
 - basis token containing campaign revision/updatedAt, brief hash,
   `selectedLeadListId`, `workflowTableId`, execution-slice row ids/hash, filter
   choice, and rubric/filter basis when present
@@ -77,7 +77,7 @@ When reporting branch runtime proof, use this shape under
 - `runId` or `fallbackId`
 - `startedAt` and `updatedAt`
 - `basisToken` and `basis`
-- optional `compactOutputRef`, `compactOutput`, and `error`
+- 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.

package/agents/registry.json

@@ -197,7 +197,7 @@
       "kind": "post-find-leads-scout",
       "promptFile": "post-find-leads-message-scout.md",
       "displayName": "Message Draft Builder",
-      "target": "generate-messages",
+      "target": "generate-messages-compact",
       "inputs": [
         "campaignId",
         "campaignBrief",
@@ -225,7 +225,7 @@
         ]
       },
       "claude": {
-        "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.",
+        "description": "Use proactively as Message Draft Builder after confirm_lead_list imports a non-empty bounded review batch; load generate-messages-compact and draft only from scoped campaign/tool state.",
         "model": "inherit",
         "background": true,
         "maxTurns": 10,

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

@@ -43,7 +43,7 @@ sales Claude`; do not treat broad anchor-only lanes like `Claude Code`, `MCP`,
 5. Promote the first narrow sample set when campaign-attached. If a
    `campaignOfferId` was supplied, call `select_promising_posts({
 campaignOfferId, selectionMode: "replace", selections, headlineICPCriteria,
-currentStep: "signal-discovery" })` before sampling so the watched Signal
+scrapePlanMode: "all-selected", 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.

package/bin/sellable-install.mjs

@@ -592,7 +592,11 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__check_rubric",
   "mcp__sellable__create_campaign",
   "mcp__sellable__save_rubrics",
-  "mcp__sellable__wait_for_rubric_results",
+  "mcp__sellable__get_campaign_table_schema",
+  "mcp__sellable__select_campaign_cells",
+  "mcp__sellable__queue_campaign_cells",
+  "mcp__sellable__wait_for_campaign_processing",
+  "mcp__sellable__revise_message_template_and_rerun",
   "mcp__sellable__update_campaign_brief",
   "mcp__sellable__update_campaign",
   "mcp__sellable__get_campaign",
@@ -608,7 +612,6 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
   "mcp__sellable__get_table_rows",
   "mcp__sellable__load_csv_linkedin_leads",
   "mcp__sellable__load_csv_domains",
-  "mcp__sellable__queue_cells",
   "mcp__sellable__get_campaign_messages_preview",
   "mcp__sellable__attach_sequence",
   "mcp__sellable__attach_recommended_sequence",
@@ -1106,10 +1109,9 @@ updates.
    asset loader so they share the same config.
 3. Follow that prompt and workflow config exactly.
 4. For message generation, use the \`post-find-leads-message-scout\` agent when
-   available. The worker and parent-thread fallback must load the full
-   long-form \`generate-messages\` prompt with
-   \`mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages", offset, limit })\`
-   until \`hasMore=false\`. Message review requires Message Draft Builder output:
+   available. The worker and parent-thread fallback must load
+   \`mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages" })\`.
+   Do not use any alternate or examples-only message prompt. Message review requires Message Draft Builder output:
    do not draft from a checklist, local markdown artifact, or parent-thread
 	   intuition. Use campaign state, campaign brief content, selected source state,
 	   and initial campaign-table execution slice rows as the source of truth; do not read stale

package/package.json

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

package/skill-templates/create-campaign.md

@@ -36,7 +36,11 @@ allowed-tools:
   - mcp__sellable__check_rubric
   - mcp__sellable__create_campaign
   - mcp__sellable__save_rubrics
-  - mcp__sellable__wait_for_rubric_results
+  - mcp__sellable__get_campaign_table_schema
+  - mcp__sellable__select_campaign_cells
+  - mcp__sellable__queue_campaign_cells
+  - mcp__sellable__wait_for_campaign_processing
+  - mcp__sellable__revise_message_template_and_rerun
   - mcp__sellable__update_campaign_brief
   - mcp__sellable__update_campaign
   - mcp__sellable__get_campaign
@@ -52,7 +56,6 @@ allowed-tools:
   - mcp__sellable__get_table_rows
   - mcp__sellable__load_csv_linkedin_leads
   - mcp__sellable__load_csv_domains
-  - mcp__sellable__queue_cells
   - mcp__sellable__get_campaign_messages_preview
   - mcp__sellable__attach_sequence
   - mcp__sellable__attach_recommended_sequence
@@ -267,8 +270,13 @@ only an internal approval proof.
 
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with `select_promising_posts` before `fetch_post_engagers` so the user can see
-which posts are being sampled in the watched app. The watch guide should say
-that we are checking people from these posts to confirm the right people are
+which posts are being sampled in the watched app. Use
+`selectionMode: "replace"` for a fresh absolute promoted set and
+`selectionMode: "add"` only when intentionally expanding existing promoted
+posts. Use `scrapePlanMode: "all-selected"` when the approval/import should use
+every promoted post; use `scrapePlanMode: "capacity-target"` only when source
+math should import the smallest set that covers a target. The watch guide should
+say that we are checking people from these posts to confirm the right people are
 actually engaging and the source is viable.
 
     After confirmed source rows exist in the campaign table, use the same registry pattern for
@@ -751,10 +759,9 @@ updates.
    asset loader so they share the same config.
 3. Follow that prompt and workflow config exactly.
 4. For message generation, use the `post-find-leads-message-scout` agent when
-   available. The worker and parent-thread fallback must load the full
-   long-form `generate-messages` prompt with
-   `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
-   until `hasMore=false`. Message review requires Message Draft Builder output:
+   available. The worker and parent-thread fallback must load
+   `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages" })`.
+   Do not use any alternate or examples-only message prompt. Message review requires Message Draft Builder output:
    do not draft from a checklist, local markdown artifact, or parent-thread
    intuition. Use campaign state, campaign brief content, selected source state, and
    initial campaign-table execution slice rows as the source of truth; do not read stale local