@sellable/install 0.1.201 → 0.1.203

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

@@ -1147,7 +1147,15 @@ updates.
    copies of this file; packaged Claude Code and Codex runs must use the MCP
    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
+4. For filter and message setup, keep the parent thread as a lean orchestrator.
+   The only normal background agent is \`post-find-leads-message-scout\` for
+   Message Drafting. Both post-import choices must launch Message Drafting.
+   When filters are chosen, launch Message Drafting, then keep filters in the
+   parent thread: load \`references/filter-leads.md\`, draft production rubrics,
+   call \`save_rubrics\`, ask filter approval, and then join Message Drafting for
+   template review. When filters are skipped, launch only Message Drafting
+   before treating the campaign as in Messages/message review.
+5. 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" })\`,
    then every required message asset named by \`generate-messages\` Mode 0 before
@@ -1163,7 +1171,7 @@ updates.
    local markdown such as \`message-validation.md\`, inspect the database
    directly, or synthesize local validation artifacts from general knowledge.
    The message recommendation handoff is labeled Markdown, not raw JSON.
-5. Create the campaign shell early with the v1 brief so the user can open the
+6. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Materialize the approved
    source list, copy confirmed rows into the campaign, and internally process the
    first campaign-table execution slice after the source is attached to the
@@ -1176,22 +1184,23 @@ 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.
-   If filters are skipped, move to Messages/message review. Queue the bounded
-   campaign-table execution-slice \`enrichCellId\` cells only after message approval. Move to
-   Messages only after at least one review row passes and one generated message
-   is ready.
+   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
+   execution-slice \`enrichCellId\` cells only after message approval. Move to the
+   generated-row Messages review only after at least one review row passes and
+   one generated message is ready.
    Do not ask the user to approve the brief before shell creation unless they
    explicitly requested a no-write draft; the shell itself is the review surface.
-6. The main thread owns watch navigation. Call
+7. The main thread owns watch navigation. Call
    \`mcp__sellable__update_campaign({ campaignId, currentStep })\` before major
    visible work so the user can watch progress in the app: \`create-offer\` for
    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
@@ -2482,10 +2491,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"
@@ -2941,7 +2947,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.201",
+  "version": "0.1.203",
   "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
@@ -427,14 +428,16 @@ After confirmed source rows exist in the campaign table, do not load the
 message registry or any deep filter/message prompt
 before the filter-choice question. After `confirm_lead_list`, ask add filters
 vs skip filters immediately. Once the user answers, launch only Message Drafting
-from the same campaign/table basis. If the user chooses filters, the parent
+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, move to
-Messages/message review. 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
@@ -915,11 +918,12 @@ updates.
 3. Follow that prompt and workflow config exactly.
 4. For filter and message setup, keep the parent thread as a lean orchestrator.
    The only normal background agent is `post-find-leads-message-scout` for
-   Message Drafting. When filters are chosen, launch Message Drafting, then keep
-   filters in the parent thread: load `references/filter-leads.md`, draft
-   production rubrics, call `save_rubrics`, ask filter approval, and then join
-   Message Drafting for template review. When filters are skipped, launch only
-   Message Drafting.
+   Message Drafting. Both post-import choices must launch Message Drafting.
+   When filters are chosen, launch Message Drafting, then keep filters in the
+   parent thread: load `references/filter-leads.md`, draft production rubrics,
+   call `save_rubrics`, ask filter approval, and then join Message Drafting for
+   template review. When filters are skipped, launch only Message Drafting
+   before treating the campaign as in Messages/message review.
 5. For message generation, keep the parent thread as a lean orchestrator and
    use the `post-find-leads-message-scout` compatibility agent for Message
    Drafting whenever the host exposes it
@@ -966,12 +970,14 @@ 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.
-   If filters are skipped, move to Messages/message review. Queue the bounded
-   campaign-table execution-slice `enrichCellId` cells only after message approval. Move to
-   Messages only after at least one review row passes and one generated message
-   is ready.
+   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
+   execution-slice `enrichCellId` cells only after message approval. Move to the
+   generated-row Messages review only after at least one review row passes and
+   one generated message is ready.
    Do not ask the user to approve the brief before shell creation unless they
    explicitly requested a no-write draft; the shell itself is the review surface.
 7. The main thread owns watch navigation. Call
@@ -980,8 +986,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