@sellable/install 0.1.203 → 0.1.204

package/bin/sellable-install.mjs

@@ -743,9 +743,15 @@ Before any provider prompt, search, or signal-discovery call, show
 one source-plan gate and ask for approval. Write this like a fifth grader could
 understand it: short sentences, no internal labels, and no GTM shorthand. The
 order is strict: first show the plan in chat, then open the approval question.
-Do not open a generic approval first and reuse it after the plan. This first
-approval only authorizes finding the best places to look for buyers. It does
-not add anyone to the campaign yet. The gate should say:
+There must be exactly one structured source-plan approval question for this
+step. Do not open a generic approval first and reuse it after the plan. Do not
+open a second identical source-plan question after the plan. If a source-plan
+question was accidentally opened before the plan, recover by showing the plan
+and continuing from that already-selected source choice when it exactly matches
+the visible recommendation; otherwise ask the user to choose a different source
+in normal chat instead of opening another identical question. This first
+approval only authorizes finding the best places to look for buyers. It does not
+add anyone to the campaign yet. The gate should say:
 
 - the buyer groups or places we could check
 - the best place to start
@@ -818,6 +824,10 @@ review will inspect, cleanup risk, and fallback. N must be the smallest
 right-content post set that clears the source target, not the default 3
 promoted sample posts. For Sales Nav or Prospeo, name the specific approved
 import path and source lead count.
+If you render a selected-post table for LinkedIn engagement, show public
+activity beside estimated likely prospects, not a second people-to-check count.
+Calculate row-level likely prospects from the sampled fit rate when available or
+the stated starting estimate.
 Do not call \`import_leads\` or \`confirm_lead_list\` until this second approval is
 granted.
 

package/package.json

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

package/skill-templates/create-campaign.md

@@ -208,9 +208,15 @@ Before any provider prompt, search, or signal-discovery call, show
 one source-plan gate and ask for approval. Write this like a fifth grader could
 understand it: short sentences, no internal labels, and no GTM shorthand. The
 order is strict: first show the plan in chat, then open the approval question.
-Do not open a generic approval first and reuse it after the plan. This first
-approval only authorizes finding the best places to look for buyers. It does
-not add anyone to the campaign yet. The gate should say:
+There must be exactly one structured source-plan approval question for this
+step. Do not open a generic approval first and reuse it after the plan. Do not
+open a second identical source-plan question after the plan. If a source-plan
+question was accidentally opened before the plan, recover by showing the plan
+and continuing from that already-selected source choice when it exactly matches
+the visible recommendation; otherwise ask the user to choose a different source
+in normal chat instead of opening another identical question. This first
+approval only authorizes finding the best places to look for buyers. It does not
+add anyone to the campaign yet. The gate should say:
 
 - the buyer groups or places we could check
 - the best place to start
@@ -400,8 +406,11 @@ summary should be a compact `## Source Recommendation` block with:
 - first review: after the source list exists, add confirmed source rows to the
   campaign and review the first 15 leads before scaling
 - a selected-post table with post author/topic, why it fits, public activity,
-  and people we can check
-- total public activity and likely prospect pool
+  and estimated likely prospects. Calculate each row's estimated likely
+  prospects from the sampled fit rate when available, otherwise from the stated
+  starting estimate; never duplicate public activity or people-to-check counts in
+  this column.
+- total public activity, people to check, and likely prospect pool
 - next step: build the source list, add it to the campaign, and review the
   first 15 leads before scaling
 - fallback: switch to active LinkedIn profiles if the first sample is too noisy
@@ -933,17 +942,14 @@ updates.
    through `mcp__sellable__get_subskill_asset`, and before returning
    `mcp__sellable__get_subskill_prompt({ subskillName: "create-campaign-v2-validation" })`
    as the final internal validation gate.
-   In Codex, YOLO/autonomous mode counts as campaign-scoped permission to use
-   this single Message Drafting background agent. If the user has not enabled
-   YOLO and has not explicitly asked for background agents, subagents, parallel
-   agents, delegation, or a message/bg agent in this campaign, ask once for
-   permission before loading the long message prompt in the parent. If
-   permission is granted but the named custom agent is not
+   In Codex, the filter-choice answer is the campaign-scoped go-ahead to use
+   this single Message Drafting background agent in step-wise and YOLO modes.
+   Do not ask a separate question to start it. If the named custom agent is not
    available, spawn a generic background agent with `model: "gpt-5.5"` and
-   `reasoning_effort: "xhigh"` using the same lean campaign/table basis. Do not
-   silently fall back to parent-thread message drafting; parent fallback is
-   allowed only when the user explicitly says to continue without a background
-   agent.
+   `reasoning_effort: "xhigh"` using the same lean campaign/table basis. If no
+   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"`.
    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