@sellable/install 0.1.202 → 0.1.204

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

@@ -169,6 +169,13 @@ When reporting branch runtime proof, use this shape under
 
 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.
+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
+inline recommendation passes. A validated parent-thread fallback is not a
+background worker failure; it must satisfy the same live-context, prompt,
+reference-asset, and validation requirements before the parent shows message
+review.
 
 ## Basis Changes And Rewrites
 

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.
 
@@ -1184,8 +1194,8 @@ updates.
    call \`mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })\`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, keep Filter Rules visible for approval; after approval,
-   move to Filter Leads and show \`Filters saved + waiting for message approval\`
-   until the template is approved.
+   move to Filter Leads with \`currentStep: "apply-icp-rubric"\` and wait there
+   while Message Drafting finishes or the template is approved.
    If filters are skipped, launch Message Drafting before moving to
    Messages/message review; updating \`currentStep\` to \`messages\` is not proof
    that the background worker started. Queue the bounded campaign-table
@@ -1200,8 +1210,7 @@ updates.
    the brief, \`pick-provider\` or the selected provider step while sourcing,
    \`filter-choice\` after source rows are copied into the campaign table, \`create-icp-rubric\` as soon
    as filters are chosen and while saved filters await approval,
-   \`apply-icp-rubric\` after filter approval while message approval is pending,
-   and after message approval while bounded enrichment/filter scoring runs, \`validate-sample\` only as a recovery/legacy
+   \`apply-icp-rubric\` after filter approval while message approval is pending and while bounded enrichment/filter scoring runs after approval, \`validate-sample\` only as a recovery/legacy
    observation state,
    \`auto-execute-messaging\` after at least one row passes and initial campaign-row
    messages are being generated or reviewed, \`awaiting-user-greenlight\` only
@@ -2492,10 +2501,7 @@ function verify(opts) {
     const pluginMcpContent = existsSync(pluginMcpPath)
       ? readFileSync(pluginMcpPath, "utf8")
       : "";
-    const hasCodexMcpDriver = hasWatchModeDriverMarker(
-      configContent,
-      "codex"
-    );
+    const hasCodexMcpDriver = hasWatchModeDriverMarker(configContent, "codex");
     const hasCodexPluginDriver = hasWatchModeDriverMarker(
       pluginMcpContent,
       "codex"
@@ -2951,7 +2957,9 @@ async function main() {
       const token = rawArgs[2];
       const authSetFlags = rawArgs.slice(3);
       const dryRun = authSetFlags.includes("--dry-run");
-      const unknownAuthSetFlag = authSetFlags.find((arg) => arg !== "--dry-run");
+      const unknownAuthSetFlag = authSetFlags.find(
+        (arg) => arg !== "--dry-run"
+      );
       if (unknownAuthSetFlag) {
         console.error(`Unknown auth set option: ${unknownAuthSetFlag}`);
         process.exit(2);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.202",
+  "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

@@ -93,8 +93,9 @@ message-template approval before enrichment/filtering or Generate Message cells.
 Filter work stays in the parent thread and must inspect visible campaign rows
 with `get_rows_minimal` / `get_rows` before drafting and saving rubrics; use at
 most one direct `enrich_with_prospeo` sample when row evidence is too thin.
-After filter approval, Filter Leads should show `Filters saved + waiting for
-message approval` until the template is approved.
+After filter approval, the browser should move to Filter Leads with
+`currentStep: "apply-icp-rubric"` and show template waiting/approval copy until
+the template is approved.
 The default path stays the existing first campaign-table execution slice:
 review the normal `reviewBatchLimit:15`, approve reviewed draft rows, then move
 to Settings/sequence/final greenlight. Only call
@@ -207,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
@@ -399,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
@@ -431,13 +441,12 @@ from the same campaign/table basis. This kickoff is required for both answers:
 `Use filters` and `Skip filters`. If the user chooses filters, the parent
 thread moves to Filter Rules, loads the filter reference, saves rubrics, then
 asks for filter approval while Message Drafting runs. After approval, move to
-Filter Leads and show `Filters saved + waiting for message approval` while the
-message recommendation is reviewed. If the user skips filters, start Message
-Drafting first, then move to Messages/message review after it has started or
-returned a ready recommendation. `update_campaign({ currentStep: "messages" })`
-is not proof of kickoff. Enrichment/filtering and Generate Message cells wait
-for message approval. AI Generated is an explicit opt-out from the template
-path.
+Filter Leads with `currentStep: "apply-icp-rubric"` and wait there while Message
+Drafting finishes or the recommendation is reviewed. If the user skips filters, start Message Drafting
+first, then move to Messages/message review after it has started or returned a
+ready recommendation. `update_campaign({ currentStep: "messages" })` is not
+proof of kickoff. Enrichment/filtering and Generate Message cells wait for
+message approval. AI Generated is an explicit opt-out from the template path.
 
 The Message Drafting handoff must stay lean. Include only `campaignId`,
 `workflowTableId`, a concise brief summary, concise source summary/source-use
@@ -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
@@ -970,8 +976,8 @@ updates.
    so the watched app moves to Filter Rules while the parent drafts/saves
    rubrics and Message Drafting runs.
    After rubrics save, keep Filter Rules visible for approval; after approval,
-   move to Filter Leads and show `Filters saved + waiting for message approval`
-   until the template is approved.
+   move to Filter Leads with `currentStep: "apply-icp-rubric"` and wait there
+   while Message Drafting finishes or the template is approved.
    If filters are skipped, launch Message Drafting before moving to
    Messages/message review; updating `currentStep` to `messages` is not proof
    that the background worker started. Queue the bounded campaign-table
@@ -986,8 +992,7 @@ updates.
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after source rows are copied into the campaign table, `create-icp-rubric` as soon
    as filters are chosen and while saved filters await approval,
-   `apply-icp-rubric` after filter approval while message approval is pending,
-   and after message approval while bounded enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
+   `apply-icp-rubric` after filter approval while message approval is pending and while bounded enrichment/filter scoring runs after approval, `validate-sample` only as a recovery/legacy
    observation state,
    `auto-execute-messaging` after at least one row passes and initial campaign-row
    messages are being generated or reviewed, `awaiting-user-greenlight` only