@sellable/install 0.1.149 → 0.1.150

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

@@ -37,14 +37,13 @@ the branch input.
 
 ## Required First Steps
 
-1. Load the compact normal-path message prompt:
+1. Load the full normal-path message prompt:
 
-   `get_subskill_prompt({ subskillName: "generate-messages-compact" })`
+   `get_subskill_prompt({ subskillName: "generate-messages" })`
 
-2. Use that prompt as the drafting contract. Load
-   `generate-messages-compact/references/examples-critique-revision.md` only for
-   critique, revision, or close-call examples. Do not use create-campaign
-   safety/checklist instructions as a substitute for the message 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,8 +56,8 @@ Return the following to the parent thread:
 - token fill rules and fallbacks
 - 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-compact quality gates
-- compact runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
+- pass/fail notes against the generate-messages quality gates
+- 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
@@ -78,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.
@@ -137,7 +136,7 @@ enablement`, or omit it.
 
 Return a concise status with:
 
-- prompt basis loaded: `generate-messages-compact`
+- prompt basis loaded: `generate-messages`
 - live campaign basis used
 - proposed template
 - token fill rules/fallbacks

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

@@ -1110,8 +1110,8 @@ updates.
 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
-   \`mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages-compact" })\`.
-   Load lazy examples/critique/revision references only when needed. Message review requires Message Draft Builder output:
+   \`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.149",
+  "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

@@ -270,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
@@ -755,8 +760,8 @@ updates.
 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
-   `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages-compact" })`.
-   Load lazy examples/critique/revision references only when needed. Message review requires Message Draft Builder output:
+   `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