@sellable/mcp 0.1.438 → 0.1.440

package/dist/tools/prompts.js

@@ -373,7 +373,7 @@ export function getPostFindLeadsScoutRegistry() {
             codex: 'After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn anything before that question. After the answer, launch only Message Drafting. The filter-choice answer is the post-import user gate for this single worker; do not ask another question about starting it in step-wise or YOLO mode. The registry lookup is not a launch: after get_post_find_leads_scout_registry, immediately invoke Task/spawn_agent or the host background-agent mechanism before loading filter-leads.md, before saving rubrics, and before treating skip-filters as ready for message review. Both choices route through this kickoff; do not let filters_skipped jump straight from filter-choice to message-generation. If filters are chosen, the parent stays on Filter Rules and drafts/saves rubrics with MCP tools while Message Drafting runs in the background. If filters are skipped, move to Messages/message review only after Message Drafting has started or is ready; update_campaign(currentStep=messages) is not proof of launch. If the named Message Drafting custom agent is unavailable, spawn a generic gpt-5.5 xhigh Message Drafting background agent with the same lean campaign/table basis. When the background worker starts, persist workerDetails.messageDraftBuilder with statusSource "branch", status "branch-running", runId, startedAt, updatedAt, basisToken when known, and basis containing campaignId, selectedLeadListId, workflowTableId, filterChoice, and reviewBatchRowHash or reviewBatchRowIds; workerStatuses.messageDraftBuilder may be "running" as a simple badge only. Never put rich proof under workerStatuses and never use workerStatuses.messageDrafting. If no background-agent tool is callable, start the same full message branch inline before filter drafting or before skip-filter message review, record workerDetails.messageDraftBuilder with statusSource "parent-thread-fallback" and status "fallback-active", and require the same live context, prompt, assets, and validation gate before message review; do not wait until filters are saved and then call the registry.',
             claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke any Task/Agent before that question. After the answer, invoke only Message Drafting. If filters are chosen, parent drafts/saves rubrics with MCP tools while Message Drafting runs, asks filter approval, then joins Message Drafting. If filters are skipped, invoke only Message Drafting and move to Messages/message review.",
             parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. The only normal background worker is Message Drafting. The filter-choice answer is the campaign-scoped go-ahead for this single post-import worker; do not ask another question to start it in step-wise or YOLO mode. If a named agent is unavailable, use a generic gpt-5.5 xhigh Message Drafting background agent. source work and filter work stay in the parent thread with MCP tools. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. The registry lookup is not a launch: get_post_find_leads_scout_registry only identifies the worker, and Message Drafting counts as started only after Task/spawn_agent or the host background-agent tool is invoked, or after the parent begins the same full message branch inline because no background-agent tool is callable. This launch must happen before loading filter-leads.md, save_rubrics, filter approval, or skip-filter message review; currentStep=messages is not proof of launch. If post-find-leads-message-scout is absent, do not customer-surface install status. Do not silently treat message drafting as started; the main thread must either launch the background worker or execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. For a spawned worker, record workerDetails.messageDraftBuilder with statusSource branch / status branch-running, runId, startedAt, updatedAt, and basis containing campaignId, selectedLeadListId, workflowTableId, filterChoice, and reviewBatchRowHash or reviewBatchRowIds. workerStatuses.messageDraftBuilder is optional simple badge text only ("running", "ready", "blocked", "idle"); never put runId/statusSource/basis under workerStatuses and never use workerStatuses.messageDrafting. If no background-agent tool is callable, start that same full message branch inline before filter drafting or before skip-filter message review, record workerDetails.messageDraftBuilder with statusSource parent-thread-fallback / status fallback-active then ready, and require the same live context, prompt, assets, and validation gate before message review; do not report that as a background worker failure. If neither branch nor inline fallback can run, return blocked/retry-needed; do not wait until filters are saved and then call the registry. The Message Drafting handoff must be lean. Do not paste copied row counts, brief hashes, review-batch hashes, full reviewBatchRowIds, broad row data, or local debug artifacts into the spawn prompt. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), and must load every required message asset named by generate-messages Mode 0 through get_subskill_asset before drafting. Reference Asset Loading means loading the required pre-draft reference pack before drafting; return blocked/retry-needed if required assets cannot be loaded; load ai-tells.md because it is never optional. The branch or parent-thread fallback loads the full generate-messages prompt and every referenced asset through get_subskill_asset. After generating/revising the candidate and before returning ready, must load get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) as the final internal validation gate, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not block when filters were chosen but leadScoringRubrics are not yet visible in the branch read; the parent owns save_rubrics and filter approval in parallel, so Message Drafting should return status ready with basisStatus usable_initial when campaign/list/table identity and the non-empty execution slice match. Do not use any alternate, local-artifact, or examples-only message prompt. User copy feedback, message QA, or rewrite requests before approve-message must be routed back to Message Drafting with the current recommendation, lean campaign/table basis, and latest user text; the parent must not rewrite or QA the template from memory and must not call update_campaign_brief before approve-message. The worker validates internally and returns only templateRecommendation, tokenFillRules, renderedGoodSample, status, approveOrReviseRecommendation, validationStatus, outputAt, outputHash, and blocked/retry detail. Do not render renderedFallbackSample, risk notes, or a qaReceipt on the normal happy path. On the filter path, save_rubrics keeps the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; after saved-filter approval, move to Filter Leads with currentStep=apply-icp-rubric whether Message Drafting is ready or still running. Wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review after Message Drafting has started or is ready and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt, required message assets, and validation gate ran for the current campaign/table execution slice. Do not automatically rerun Message Drafting after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in. Handoff and recommendation output are Markdown with labeled fields, not raw JSON.',
-            prepareMessagesRule: `Default create-campaign stays on the existing reviewBatchLimit:15 first campaign-table execution slice. For plain post-mint fill/load/refill requests, load get_subskill_prompt({ subskillName: "refill-sends-workflow" }), then call resolve_campaign_fill_route({ intent:"plain" }), list_senders, and get_campaign_refill_state for enough candidate campaigns to identify the campaign that most recently had scheduler-owned sends for the relevant sender set before any mutation. Route outcomes are route:"evergreen_horizon", route:"active_campaigns", and route:"ask_create"; if a plain managed-waterfall route has archived/completed skipped slots or does not cover the named sender set, immediately refetch with resolve_campaign_fill_route({ intent:"active" }) and inspect current dashboard-active ACTIVE/PAUSED campaign-backed sequence campaigns before declaring a sender blocked; stay in the same campaignOfferId/campaignId context after minting. Plain fill is not an alias for fill_campaign_horizon or campaign creation. fill_campaign_horizon is evergreen-only and is not the generic regular-campaign fill path. Campaign creation is allowed only after route:"ask_create" and explicit user selection; it is never the default response to plain fill. Treat "fill up/load sends" as capacity-fill preparation, and treat "refill senders", "fill senders", "max out senders", and "load everyone up" as sender-scoped capacity-fill preparation. For sender-scoped requests with no named senders, --yolo means all eligible healthy senders enrolled in active campaign-backed sequence campaigns in the active workspace; without --yolo, ask which eligible enrolled senders to refill before choosing campaigns or mutating. In non-yolo interactive Codex or Claude Code sessions, the sender/campaign/action approval packet must be asked through request_user_input/AskUserQuestion with exactly Accept and Decline; do not use plain chat approval. The approval question body must show workspace, sender scope, a campaign-by-campaign table, exact ids/caps/dates, side effects, forbidden actions, and stop condition before mutation. Default --yolo horizon is a two-send-day horizon: two sender-local send days, skipping no-send-hour days. For campaign-scoped fill/refill, select the best recent-send campaign and calculate the bounded gap from healthy sender daily capacity minus future scheduler-owned scheduled sends and ready-to-schedule rows, then prepare only that gap. For sender-scoped fill/refill, calculate the bounded gap per eligible sender across active enrolled campaigns, counting future scheduled and ready-to-schedule rows across those campaigns, then choose the best same-sender campaign to fill each sender gap: prefer recent/future scheduler-owned sends for that sender, then strongest recent result evidence, then source health. Do not stop after filling only one sender when the request was sender-scoped. In --yolo, continue through every safe selected sender/campaign action covered by the rendered packet, reread after each terminal apply/prep/start result, and when no safe in-packet action remains return concrete continuation options with campaign names, exact ids, and which options require a new approval packet. Use the refill workflow to decide whether to enrich/prep more rows in that same recent-send/best-result campaign, add/import more rows to that same campaign/source path, use a different existing campaign only when the selected same-sender lane is blocked/exhausted/already loaded while the sender still has a gap, or ask what to create. Do not create warm-post-engager side campaigns. Surface sender-health blockers separately from prepared/approved/scheduled counts. User-facing refill decisions must be campaign-name-first and sender-name-first, with ids as proof/execution targets only. For already-running regular campaigns that need Signal Discovery source replenishment, use the guarded currentStep clear with clearCurrentStepIfMatches:"running", campaign-scoped provider prompt/search/select, and import_leads with the existing sourceLeadListId when a newly approved selected-post scrape would otherwise return reusedExistingSourceList. After confirm_lead_list copies rows into an existing table, avoid fixed maxRowsToCheck:100; if confirm_lead_list returns USER_ADDED_ROWS_LIMIT_EXCEEDED, create a bounded same-source split from selectedLeadListId with get_rows_minimal/load_csv_linkedin_leads, confirm that smaller source list into the same campaign, and operate on the reviewBatch first; inspect reviewBatch/table selectors or use adaptive/wider bounded prep so appended rows are included. Do not interpret checkedRows as enriched rows; it is only the table cursor. Prepared, approved, and ready_to_schedule rows are intermediate states; never call them scheduled unless a re-read proves scheduler-owned scheduled cells with non-null scheduledFor. Before source import, prep, approval, or selected paused campaign start, require exact visible approval or --yolo packet auto-accept and a fresh get_campaign_refill_state reread; stop if freshness.stateHash or exact ids changed. For "approve X messages", use approvalMode:approve only when explicitly requested. For "schedule X sends" or "fill sender sends", approve only when explicitly requested, then re-read campaign/table scheduled counts; if scheduler-owned scheduledFor cells are not present, report prepared/approved/ready - awaiting scheduler instead of success. start_campaign is allowed in refill only for exact selected PAUSED, dashboard-active, campaign-backed sequence targets named in the bounded packet, and the packet must state that starting can let the product scheduler schedule/send approved eligible sequence actions. Never start unrelated, archived, completed, draft, direct, or non-selected campaigns, never broad approve-all, and never use direct scheduler writes. campaignId is CampaignOffer.id. If the user asks to stop preparation, the target is wrong, or status shows the wrong campaign/table, use cancel_campaign_message_preparation only for the exact active job. Low-level selectors are diagnostics and recovery only for this lane.`,
+            prepareMessagesRule: `Default create-campaign stays on the existing reviewBatchLimit:15 first campaign-table execution slice. For plain post-mint fill/load/refill requests, load get_subskill_prompt({ subskillName: "refill-sends-workflow" }), then call resolve_campaign_fill_route({ intent:"plain" }), list_senders, and get_campaign_refill_state for enough candidate campaigns to identify the campaign that most recently had scheduler-owned sends for the relevant sender set before any mutation. Route outcomes are route:"evergreen_horizon", route:"active_campaigns", and route:"ask_create"; if a plain managed-waterfall route has archived/completed skipped slots or does not cover the named sender set, immediately refetch with resolve_campaign_fill_route({ intent:"active" }) and inspect current dashboard-active ACTIVE/PAUSED campaign-backed sequence campaigns before declaring a sender blocked; stay in the same campaignOfferId/campaignId context after minting. Plain fill is not an alias for fill_campaign_horizon or campaign creation. fill_campaign_horizon is evergreen-only and is not the generic regular-campaign fill path. Campaign creation is allowed only after route:"ask_create" and explicit user selection; it is never the default response to plain fill. Treat "fill up/load sends" as capacity-fill preparation, and treat "refill senders", "fill senders", "max out senders", and "load everyone up" as sender-scoped capacity-fill preparation. For sender-scoped requests with no named senders, --yolo means all eligible healthy senders enrolled in active campaign-backed sequence campaigns in the active workspace; without --yolo, ask which eligible enrolled senders to refill before choosing campaigns or mutating. In non-yolo interactive Codex or Claude Code sessions, the sender/campaign/action approval packet must be asked through request_user_input/AskUserQuestion with exactly Accept and Decline; do not use plain chat approval. The approval question body must show workspace, sender scope, a campaign-by-campaign table, exact ids/caps/dates, side effects, forbidden actions, and stop condition before mutation. Default --yolo horizon is a two-send-day horizon: two sender-local send days, skipping no-send-hour days. For campaign-scoped fill/refill, select the best recent-send campaign and calculate the bounded gap from healthy sender daily capacity minus future scheduler-owned scheduled sends and ready-to-schedule rows, then prepare only that gap. For sender-scoped fill/refill, calculate the bounded gap per eligible sender across active enrolled campaigns, counting future scheduled and ready-to-schedule rows across those campaigns, then choose the best same-sender campaign to fill each sender gap: prefer recent/future scheduler-owned sends for that sender, then strongest recent result evidence, then source health. Maintain a horizon saturation ledger per selected sender with selected send days, gross capacity, future scheduler-owned scheduled counts, ready-to-schedule buffer, remaining scheduled gap, remaining ready-or-scheduled gap, and the next MCP primitive. Do not stop after filling only one sender when the request was sender-scoped. In --yolo, continue through every safe selected sender/campaign action covered by the rendered packet, reread after each terminal apply/prep/start result, recompute the horizon saturation ledger, and keep going until scheduler-owned scheduledFor cells fill the requested horizon or a concrete blocker/timeout is proven. Ready-to-schedule rows are buffer, not completion; if ready covers the gap but scheduled cells do not, run a bounded scheduler-settle loop and report awaiting_scheduler_after_ready_buffer as not complete when timeout is reached. When no safe in-packet action remains return concrete continuation options with campaign names, exact ids, and which options require a new approval packet. Use the refill workflow to decide whether to enrich/prep more rows in that same recent-send/best-result campaign, add/import more rows to that same campaign/source path, use a different existing campaign only when the selected same-sender lane is blocked/exhausted/already loaded while the sender still has a gap, or ask what to create. Do not create warm-post-engager side campaigns. Surface sender-health blockers separately from prepared/approved/scheduled counts. User-facing refill decisions must be campaign-name-first and sender-name-first, with ids as proof/execution targets only. For already-running regular campaigns that need Signal Discovery source replenishment, use the guarded currentStep clear with clearCurrentStepIfMatches:"running", campaign-scoped provider prompt/search/select, and import_leads with the existing sourceLeadListId when a newly approved selected-post scrape would otherwise return reusedExistingSourceList. After confirm_lead_list copies rows into an existing table, avoid fixed maxRowsToCheck:100; if confirm_lead_list returns USER_ADDED_ROWS_LIMIT_EXCEEDED, create a bounded same-source split from selectedLeadListId with get_rows_minimal/load_csv_linkedin_leads, confirm that smaller source list into the same campaign, and operate on the reviewBatch first; inspect reviewBatch/table selectors or use adaptive/wider bounded prep so appended rows are included. Do not interpret checkedRows as enriched rows; it is only the table cursor. Prepared, approved, and ready_to_schedule rows are intermediate states; never call them scheduled or complete unless a final re-read proves scheduler-owned scheduled cells with non-null scheduledFor fill the requested horizon. Before source import, prep, approval, or selected paused campaign start, require exact visible approval or --yolo packet auto-accept and a fresh get_campaign_refill_state reread; stop if freshness.stateHash or exact ids changed. For "approve X messages", use approvalMode:approve only when explicitly requested. For "schedule X sends" or "fill sender sends", approve only when explicitly requested, then re-read campaign/table scheduled counts; if scheduler-owned scheduledFor cells are not present, report prepared/approved/ready - awaiting scheduler instead of success. start_campaign is allowed in refill only for exact selected PAUSED, dashboard-active, campaign-backed sequence targets named in the bounded packet, and the packet must state that starting can let the product scheduler schedule/send approved eligible sequence actions. Never start unrelated, archived, completed, draft, direct, or non-selected campaigns, never broad approve-all, and never use direct scheduler writes. campaignId is CampaignOffer.id. If the user asks to stop preparation, the target is wrong, or status shows the wrong campaign/table, use cancel_campaign_message_preparation only for the exact active job. Low-level selectors are diagnostics and recovery only for this lane.`,
         },
     };
 }

package/dist/tools/refill-sends.js

@@ -151,10 +151,12 @@ export function refillSendsCommand(input = {}) {
             "Read get_campaign_refill_state for enough exact candidate campaigns to pick the best per-sender target by recent/future scheduler-owned sends, then recent result evidence, then source health.",
             "Treat current dashboard-active PAUSED campaign-backed sequence campaigns as start-eligible candidates: read refill state before deciding whether to prep, approve, start, or skip.",
             "Fresh reread get_campaign_refill_state immediately before any import, prep, approval, or horizon-fill mutation.",
+            "Maintain a horizon saturation ledger per selected sender: selected send days, gross capacity, future scheduler-owned scheduled counts, ready-to-schedule buffer, remaining scheduled gap, remaining ready-or-scheduled gap, and next MCP primitive.",
             "In --yolo, continue through every safe selected sender/campaign action covered by the rendered packet; when no safe in-packet action remains, return concrete continuation options instead of silently stopping.",
+            "Do not complete a fill/schedule request until a final get_campaign_refill_state reread proves scheduler-owned scheduledFor cells fill the horizon, or report a concrete blocker such as awaiting_scheduler_after_ready_buffer.",
         ],
         approvalContract: yolo
-            ? "Auto-accept only the rendered bounded refill packet after fresh reread. Continue through every safe apply/prep/start action inside that packet, including start_campaign only for exact selected PAUSED campaign-backed sequence refill targets named in the packet. If no safe in-packet action remains, return concrete continuation options and stop. Stop immediately if sender set, route, ids, caps, dates, blockers, or side-effect class drift."
+            ? "Auto-accept only the rendered bounded refill packet after fresh reread. Continue through every safe apply/prep/start action inside that packet, including start_campaign only for exact selected PAUSED campaign-backed sequence refill targets named in the packet. After each action, recompute the per-sender horizon saturation ledger and keep going until scheduler-owned scheduledFor cells fill the requested horizon or a concrete blocker/timeout is proven. Ready-to-schedule rows are buffer, not completion. If no safe in-packet action remains, return concrete continuation options and stop. Stop immediately if sender set, route, ids, caps, dates, blockers, or side-effect class drifts."
             : hasSenderSelectors
                 ? "Ask the final Accept/Decline structured approval question before mutation, including workspace, sender scope, campaign table, exact ids, caps/dates, side effects, forbidden actions, and stop condition."
                 : "Ask which eligible enrolled senders to refill first, then ask the final Accept/Decline structured approval question before mutation.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.438",
+  "version": "0.1.440",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/references/gold-standard-message-examples.md

@@ -214,7 +214,7 @@ Subject: initiatives + business outcomes + one live picture
 
 Hey {{first_name}},
 
-Saw you in a few conversations about {{signal_topic}}, so hope this is relevant.
+Saw you might be interested in {{signal_topic}}, so hope this is relevant.
 
 I helped build {{credible_prior_company}}, so I've seen firsthand where {{buyer_category}} tools fall short.
 
@@ -238,11 +238,11 @@ Why it works:
 
 Transfer limits:
 
-- Use `Saw you in a few conversations about/around [topic], so hope this is
+- Use `Saw you might be interested in [topic], so hope this is relevant` or
+  `Saw you in a few conversations about/around [topic], so hope this is
   relevant` only for Shared Signal Discovery when the source evidence supports
   the topic and the line does not claim a reaction, comment, sender-authored
   post, or other unproven engagement.
-- Do not use `might be interested`; that assumes intent from weak evidence.
 - Do not use `found you in a thread`; that exposes sourcing mechanics.
 - Do not use founder/operator proof unless the brief supports it and every
   attached sender can credibly send the line.

package/skills/create-campaign-v2/references/gold-standard-message-patterns.md

@@ -210,7 +210,10 @@ Shared Evergreen Signal Discovery override:
   relevant` is allowed when the source evidence supports the topic and the line
   does not claim a reaction, comment, sender-authored post, or other unproven
   engagement.
-- Do not use `might be interested`; that assumes intent from weak evidence.
+- The Dotwork opener `Saw you might be interested in [topic], so hope this is
+  relevant` is also allowed for Shared Signal Discovery when the source
+  evidence supports the topic. Do not use bare `might be interested` as a
+  generic intent claim.
 - Do not use `found you in a thread`; that exposes sourcing mechanics.
 - Do not use `I'm building`, `I've mapped`, `my company`, or `my team`.
 - Prefer the Dotwork shape when the message is InMail: a concrete A + B + C

package/skills/create-campaign-v2/references/sellable-cleanup-rules.md

@@ -88,14 +88,15 @@ Revise or reject the sample when any of these happen.
   LinkedIn is becoming more of a GTM channel for [company]"`. For Shared Signal
   Discovery and non-evergreen third-party LinkedIn-post-sourced campaigns, a
   topic-level bridge is allowed when it explains why the note exists and stays
-  apologetically uncertain: `"saw you in a few conversations about [topic], so
-  may be off, but this seemed relevant."`, `"saw you in a few conversations
-  around [topic], so hope this is relevant."`, or `"hope this is relevant if
-  [topic] is still on your plate."` Shared evergreen signal override:
-  topic-level `saw you in a few conversations... hope this is relevant` is
-  allowed for Shared Signal Discovery when evidence-backed; `might be
-  interested` remains blocked because it assumes intent, and `found you in a
-  thread` remains blocked because it exposes sourcing mechanics.
+  apologetically uncertain: `"saw you might be interested in [topic], so hope
+  this is relevant."`, `"saw you in a few conversations about [topic], so may be
+  off, but this seemed relevant."`, `"saw you in a few conversations around
+  [topic], so hope this is relevant."`, or `"hope this is relevant if [topic] is
+  still on your plate."` Shared evergreen signal override: Dotwork-style `saw
+  you might be interested` can be used for Shared Signal Discovery when the
+  named Dotwork pattern applies, topic-level and evidence-backed; otherwise
+  prefer the conversation/topic bridge. `found you in a thread` remains blocked
+  because it exposes sourcing mechanics.
   Shared Cold Fallback should use a concrete signal/problem
   bridge or omit the source line. Reserve `"raise your hand"` language for
   explicit lead-magnet comments, replies, or opt-ins. Translate the signal into
@@ -403,8 +404,8 @@ sentence].`
 still on your plate.` Shared Signal Discovery or non-evergreen weak-signal only.
 - `Hey {{first_name}}, may be off, but if [workflow] is relevant to what
 you're working on, this might be useful.`
-- `Hey {{first_name}}, saw you in a few conversations about [topic], so hope
-this is relevant.` Shared Signal Discovery or non-evergreen weak-signal only.
+- `Hey {{first_name}}, saw you might be interested in [topic], so hope
+this is relevant.` Dotwork Shared Signal Discovery or non-evergreen weak-signal only.
 - `Hey {{first_name}}, saw you in a few conversations around [topic],
 so hope this is relevant.` Shared Signal Discovery or non-evergreen weak-signal only.
 - `Hey {{first_name}}, found you in a thread about [topic], so may be

package/skills/create-evergreen-campaigns/SKILL.md

@@ -938,32 +938,48 @@ verify and do not repair by summarizing product readback in the parent.
 Message Drafting runtime rule: the preferred proof source is the normal
 create-campaign branch handoff (`watchNarration.workerDetails.messageDraftBuilder`
 or equivalent) with `statusSource:"branch"`. If that internal branch handoff is
-not callable or not exposed in the packaged MCP runtime, do **not** stop after
-creating/importing rows. The lane worker must run the packaged message-drafting
-path itself in the worker thread:
-
-1. Load `get_subskill_prompt({ subskillName:"generate-messages" })` until
-   `hasMore:false`.
-2. Load the required message assets and `create-campaign-v2-validation`.
-3. Call `start_campaign_message_preparation({ campaignId, tableId,
+not callable or not exposed in the packaged MCP runtime, do **not** substitute
+plain row generation. The lane worker must inline the same
+`post-find-leads-message-scout` contract in the worker thread before any
+`start_campaign_message_preparation` call:
+
+1. Run the `post-find-leads-message-scout` branch, or inline its packaged
+   contract when branch launch is unavailable, from the current campaign/table,
+   selected lead list, saved filters, review batch row ids/hash, brief hash,
+   `mode:"create-campaign-v2"`, and lane type.
+2. Load `get_subskill_prompt({ subskillName:"generate-messages" })` until
+   `hasMore:false`, all required message assets, and
+   `create-campaign-v2-validation`.
+3. Produce a concrete `messageDraftRecommendation` before row generation. It
+   must include the selected message approach/template recommendation,
+   token/fill rules, source-use rules, hard avoids, at least one rendered good
+   sample, current campaign/table/source basis, and validation status. Shared
+   lanes still use `firstMessageTemplateState:"not preset; generate-messages
+   branch selected the final message approach"`; do not set
+   `firstMessageTemplate` for shared lanes.
+4. Persist the recommendation into the campaign brief/message generation basis
+   with the packaged create-campaign tools before generating rows. If the
+   generated copy fails review, update the campaign brief/message template with
+   `update_campaign_brief` or `revise_message_template_and_rerun`, then rerun
+   Generate Message and review current-revision generated output.
+5. Only after the scout recommendation and persisted basis exist, call
+   `start_campaign_message_preparation({ campaignId, tableId,
    targetPreparedMessages, maxRowsToCheck, approvalMode:"mark_ready",
    autoContinue:true })` inside the same lane worker, with bounded caps from the
-   lane packet.
-   Never call `start_campaign_message_preparation` with `approvalMode:"approve"`
-   for evergreen setup. Generate/readiness and approval are separate safety
-   steps: first mark rows ready, then inspect generated copy, then approve
-   exactly one semantic Approved cell through `select_campaign_cells` and
-   `update_cell`.
+   lane packet. `start_campaign_message_preparation` is row execution proof
+   only; it is not Message Drafting proof and cannot satisfy this step by
+   itself. Never call `start_campaign_message_preparation` with
+   `approvalMode:"approve"` for evergreen setup.
+   Generate/readiness and approval are separate safety steps: first mark rows
+   ready, then inspect generated copy, then approve exactly one semantic
+   Approved cell through `select_campaign_cells` and `update_cell`.
    Approval shorthand: approve exactly one semantic Approved cell.
    In this message-drafting path, `update_cell` is allowed only for the semantic
    Approved checkbox. Do not use `update_cell` or any row/cell write to edit
    generated message text, sample copy, or final message bodies in automation.
-   If generated copy fails review, update the campaign brief/message template
-   with `update_campaign_brief` or `revise_message_template_and_rerun`, then
-   rerun Generate Message and review current-revision generated output. Receipt
-   `sampleMessages` must come from generated current-revision cells after the
-   brief/template rerun, not from hand-edited message cell overrides. If a lane
-   used a generated-message body override, report
+   Receipt `sampleMessages` must come from generated current-revision cells
+   after the brief/template rerun, not from hand-edited message cell overrides.
+   If a lane used a generated-message body override, report
    `blocked: generated_message_cell_override` instead of success.
    Do not repair by overwriting bad generated message cells and then calling the
    overwritten cells `sampleMessages`.
@@ -974,9 +990,9 @@ path itself in the worker thread:
    Short form: `update_cell` is allowed only for the semantic Approved checkbox.
    Short form: Do not use `update_cell` to edit generated message text.
    Short form: Bad copy requires brief/template revision plus Generate Message rerun.
-4. Poll `get_campaign_message_preparation_status` until no queued/active cells
+6. Poll `get_campaign_message_preparation_status` until no queued/active cells
    remain or a bounded stop reason is returned.
-5. Use `get_campaign_messages_preview` or `select_campaign_cells` to inspect
+7. Use `get_campaign_messages_preview` or `select_campaign_cells` to inspect
    generated rows, quality-review at least 3 samples, approve exactly one
    quality-valid route-proof row when none is already approved, and prove no
    broad approve-all happened.
@@ -986,16 +1002,21 @@ path itself in the worker thread:
    approvedGeneratedMessageCount exactly 1. Do not report completion with 2+
    approved rows.
    Approval shorthand: Do not report completion with 2+ approved rows.
-6. Continue to `attach_recommended_sequence({ campaignId, currentStep:"send" })`
+8. Continue to `attach_recommended_sequence({ campaignId, currentStep:"send" })`
    and, if the campaign is still `DRAFT`, `pause_campaign({ campaignId })`.
    Reread the campaign/table before claiming completion.
 
 That packaged worker path must return `messageDraftingReceipt.statusSource:
 "packaged-generate-messages-worker"`. It is accepted only when the receipt
-includes the same prompt/assets/validation proof, current campaign/table/source
-basis, generated review rows, sample messages, quality review, route-proof
-approval evidence, sequence proof, and final paused-send proof required of the
-branch handoff. `statusSource:"parent-thread-fallback"` is still invalid.
+includes branch-equivalent `post-find-leads-message-scout` proof, the
+`messageDraftRecommendation`, proof the recommendation was persisted into the
+brief/message basis before row generation, the prompt/assets/validation proof,
+current campaign/table/source basis, generated review rows, sample messages,
+quality review, route-proof approval evidence, sequence proof, and final
+paused-send proof required of the branch handoff. `statusSource:
+"parent-thread-fallback"` is still invalid. If neither branch handoff nor
+inline scout proof can run, stop with `blocked:
+missing_message_drafting_branch`; do not shortcut through row prep.
 The only accepted statusSource values are exactly `branch` and
 `packaged-generate-messages-worker`; descriptive aliases such as
 `package-readback-local-thread` are rejected.
@@ -1232,7 +1253,7 @@ Message, and verify current-revision sample messages before final completion.
      Short form: Do not pass the warm template into Shared Signal Discovery or Shared Cold Fallback.
      Short form: Shared lanes must reject generic product-summary samples.
      Short form: Shared lanes must reject three nearly identical samples.
-     Short form: Shared lanes must reject intent-assumptive hedges such as "might be interested"; Shared Signal Discovery may use topic-level bridges like "saw you in a few conversations about [topic], so hope this is relevant" or "hope this is relevant if [topic] is part of the plan" when the source evidence supports the topic and the line does not claim engagement or expose source mechanics.
+     Short form: Shared lanes must reject unsupported intent-assumptive hedges; Shared Signal Discovery may use Dotwork-style topic bridges like "saw you might be interested in [topic], so hope this is relevant", "saw you in a few conversations about [topic], so hope this is relevant", or "hope this is relevant if [topic] is part of the plan" when the source evidence supports the topic and the line does not claim engagement or expose source mechanics.
      Short form: Shared lanes must reject internal workflow vocabulary.
      Short form: revise or rerun the packaged create-campaign/generate-messages path.
    - **Post Engagers** first-message style: short, casual, references the
@@ -1298,7 +1319,7 @@ Message, and verify current-revision sample messages before final completion.
      Short form: Shared Signal Discovery uses no self-intro such as "I'm building Sellable".
      Short form: Shared Signal Discovery uses no self-intro such as "We're building Sellable".
      Short form: Shared Signal Discovery uses no "I've put together".
-     Short form: topic-level bridges, including "saw you in a few conversations about/around [topic], so hope this is relevant" and "hope this is relevant if [topic] is part of the plan", are allowed for Shared Signal Discovery when evidence-backed and not engagement-claiming; "might be interested" is not allowed.
+     Short form: topic-level bridges, including "saw you might be interested in [topic], so hope this is relevant", "saw you in a few conversations about/around [topic], so hope this is relevant", and "hope this is relevant if [topic] is part of the plan", are allowed for Shared Signal Discovery when evidence-backed and not engagement-claiming; do not use bare "might be interested" as a generic intent claim.
      Short form: no internal workflow vocabulary such as "Codex-style workflow", "MCP", "agent workflows", "Claude Code", or "Claude-style agent workflows".
    - **Shared Cold Fallback** first-message style: cold, direct, and cohesive.
      It must not pretend there was engagement, must not say "saw you pop up",
@@ -1365,16 +1386,25 @@ Message, and verify current-revision sample messages before final completion.
       Short form: missing or skipped filter proof is `blocked: missing_filter_setup`.
       Short form: run Message Drafting only after saved filters are applied.
     - Every customer-visible lane must run Message Drafting from the current
-      campaign/table basis after source rows exist. The worker must load the full
-      packaged `generate-messages` prompt, every required asset, and
-      `create-campaign-v2-validation`; if the internal branch handoff is not
-     callable in the packaged runtime, the worker must call
-     `start_campaign_message_preparation` and poll
-     `get_campaign_message_preparation_status` from the lane worker. The
-     returned receipt must include `statusSource:"branch"` or
-     `statusSource:"packaged-generate-messages-worker"`, at least 3 concrete
-     reviewed sample messages, a passed validation result, and a passed quality
-     review. Row/message counts alone are not enough.
+      campaign/table basis after source rows exist and saved filters are
+      applied. The worker must use the normal
+      `post-find-leads-message-scout` branch handoff or inline that same scout
+      contract when branch launch is unavailable. Plain
+      `start_campaign_message_preparation` is row execution proof only; it is
+      not a fallback substitute for Message Drafting. The worker must load the
+      full packaged `generate-messages` prompt, every required asset, and
+      `create-campaign-v2-validation`; before row generation, the receipt must
+      show branch-equivalent scout proof, a concrete
+      `messageDraftRecommendation`, and proof that recommendation was persisted
+      into the campaign brief/message generation basis. Only then may the
+      worker call `start_campaign_message_preparation` and poll
+      `get_campaign_message_preparation_status` from the lane worker. The
+      returned receipt must include `statusSource:"branch"` or
+      `statusSource:"packaged-generate-messages-worker"`, at least 3 concrete
+      reviewed sample messages, a passed validation result, and a passed quality
+      review. Row/message counts alone are not enough. If the branch handoff and
+      inline scout contract are both unavailable, report
+      `blocked: missing_message_drafting_branch`.
 
    - **The brief must declare the delivery format** so Generate Message writes copy suited to how it actually sends:
      - DM lanes: add a `Delivery format:` line — either `multiline (each paragraph sends as its own DM message)` or `single message`. When multiline, the template's blank-line paragraphs ARE the message boundaries — write each one as a standalone typed message.
@@ -1412,12 +1442,15 @@ Message, and verify current-revision sample messages before final completion.
      `hasMore:false`, required message assets were loaded, and
      `create-campaign-v2-validation` ran through
      `workerDetails.messageDraftBuilder` with `statusSource:"branch"` or
-     through the lane worker's packaged message-prep path with
-     `statusSource:"packaged-generate-messages-worker"`,
-     `start_campaign_message_preparation`, and
+     through the lane worker's inline `post-find-leads-message-scout` contract
+     with `statusSource:"packaged-generate-messages-worker"`. For the packaged
+     worker path, proof must include branch-equivalent scout proof, a concrete
+     `messageDraftRecommendation`, template/basis persistence proof before row
+     generation, `start_campaign_message_preparation`, and
      `get_campaign_message_preparation_status`. The generated-message cells are
      not prompt proof; `currentRevisionGeneratedMessages` and row previews are
-     only downstream cell evidence. The proof must include
+     only downstream cell evidence. Row prep alone is not prompt proof. The
+     proof must include
       `validationResult:"passed"`, a passed quality review, and at least 3
       reviewed sample messages. For Shared Cold Fallback, reject samples that
       open with a standalone name followed by "Hey there" or a similarly generic

package/skills/generate-messages/SKILL.md

@@ -270,10 +270,11 @@ multiple senders, so the first line cannot sound like a scraped-activity excuse
 or a founder self-intro.
 
 - For Shared Signal Discovery, low-certainty topic bridges are allowed when
-  evidence-backed: `saw you in a few conversations about/around [topic], so
-  hope this is relevant` and `hope this is relevant if [topic] is part of the
-  plan`. The line must not claim a reaction, comment, sender-authored post,
-  other engagement that is not proven, or that the buyer `might be interested`.
+  evidence-backed: `saw you might be interested in [topic], so hope this is
+  relevant`, `saw you in a few conversations about/around [topic], so hope this
+  is relevant`, and `hope this is relevant if [topic] is part of the plan`. The
+  line must not claim a reaction, comment, sender-authored post, or other
+  engagement that is not proven.
 - `found you in a thread` is blocked for Shared Signal Discovery because it
   exposes source mechanics. Shared Cold Fallback should use concrete
   role/company/problem context instead of source-thread phrasing.
@@ -299,10 +300,10 @@ or a founder self-intro.
 
 Short form: shared evergreen copy must start from buyer context or an
 evidence-backed topic bridge, not assumed intent.
-Short form: Shared Signal Discovery may use `saw you in a few conversations
-about/around [topic], so hope this is relevant` or `hope this is relevant if
-[topic] is part of the plan` when it is topic-level and evidence-backed; do not
-use `saw you might be interested`.
+Short form: Shared Signal Discovery may use `saw you might be interested in
+[topic], so hope this is relevant`, `saw you in a few conversations
+about/around [topic], so hope this is relevant`, or `hope this is relevant if
+[topic] is part of the plan` when it is topic-level and evidence-backed.
 Short form: shared evergreen copy cannot use `I'm building`.
 Short form: write a concrete signal/problem bridge instead of a rejected relevance hedge.
 
@@ -325,11 +326,11 @@ conditional good/bad fill reference.
 note to why this might matter now. DO: connect one observable role/company/
 activity signal to the buyer problem or offer with a permissioned bridge. For
 shared evergreen lanes, do not use source-thread disclaimers that expose
-mechanics. For Shared Signal Discovery, `saw you in a few conversations
-about/around [topic], so hope this is relevant` and topic-backed `hope this is
-relevant` bridges are allowed when topic-level and evidence-backed; do not use
-`saw you might be interested`. Use a concrete buyer/problem bridge when that is
-stronger. Low-certainty language like
+mechanics. For Shared Signal Discovery, `saw you might be interested in [topic],
+so hope this is relevant`, `saw you in a few conversations about/around [topic],
+so hope this is relevant`, and topic-backed `hope this is relevant` bridges are
+allowed when topic-level and evidence-backed. Use a concrete buyer/problem
+bridge when that is stronger. Low-certainty language like
 "so may be off, but this seemed relevant" can be considered only for
 non-evergreen weak-signal campaigns when the source is otherwise awkward. DON'T: recap their resume, list companies, compliment their
 background, name a product their company sells, use source-citation phrasing, or
@@ -493,7 +494,7 @@ artifact.**
    Safer shapes:
 
    - `hope this is relevant if {{signal_topic}} is part of the plan` for Shared Signal Discovery or non-evergreen weak-signal campaigns only
-   - `saw you might be interested in {{signal_topic}}, so hope this is relevant` for non-evergreen weak-signal campaigns only
+   - `saw you might be interested in {{signal_topic}}, so hope this is relevant` for Shared Signal Discovery or non-evergreen weak-signal campaigns only
    - `saw you in a few conversations around {{signal_topic}}, so hope this is relevant` for Shared Signal Discovery or non-evergreen weak-signal campaigns only
    - `saw you in a few conversations about {{signal_topic}}, so may be off, but this seemed relevant` for non-evergreen weak-signal campaigns only
    - `appreciate you showing some love on my post about {{signal_topic}}` only when the sender/client authored the source post and the row proves a reaction or comment
@@ -1575,9 +1576,9 @@ Before `confirmed`, run the selected winner against these gates:
   `hope this is relevant if...`, `saw you might be interested in...`,
   `saw you in a few conversations around...`, `figured this might matter if...`,
   or `if you've ever wanted...`. Exception: for Shared Signal Discovery,
-  topic-backed `hope this is relevant` and `saw you in a few conversations
-  around...` are allowed when topic-level and evidence-backed; do not use `saw
-  you might be interested`. Other shared evergreen lanes should start from the
+  topic-backed `hope this is relevant`, `saw you might be interested in...`, and
+  `saw you in a few conversations around...` are allowed when topic-level and
+  evidence-backed. Other shared evergreen lanes should start from the
   public business theme, row role/company context, or buyer problem.
 - **Buyer-first opener:** after the greeting, the first substantive line
   should usually enter the buyer's world: a real signal, current-state
@@ -1881,9 +1882,9 @@ about`, or `clearly relevant` are BLOCKED. Source-y phrases such as
   in a few conversations about [topic], so may be off, but this seemed
   relevant`, `figured this might matter if [workflow] is live at [company]`, or
   a similarly natural line. For Shared Signal Discovery, topic-backed `hope this
-  is relevant` and `saw you in a few conversations ... hope this is relevant`
-  are allowed when they stay topic-level and avoid false engagement claims; do
-  not use `saw you might be interested`. Other shared evergreen lanes should use
+  is relevant`, `saw you might be interested ... hope this is relevant`, and
+  `saw you in a few conversations ... hope this is relevant` are allowed when
+  they stay topic-level and avoid false engagement claims. Other shared evergreen lanes should use
   the concrete bridge version. Longer
   source-recap forms such as `you
   might not remember the thread,
@@ -2032,7 +2033,7 @@ led to it. Acceptable openers:
 
 - `Hey {{first_name}}, [one plain sentence about what we built].`
 - `Hey {{first_name}}, hope this is relevant if [buyer context] is still on your plate.` For Shared Signal Discovery or non-evergreen weak-signal campaigns only.
-- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.` For non-evergreen weak-signal campaigns only.
+- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.` For Shared Signal Discovery or non-evergreen weak-signal campaigns only.
 - `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.` For Shared Signal Discovery or non-evergreen weak-signal campaigns only.
 - `Hey {{first_name}}, found you in a thread about [topic], so may be off, but this seemed relevant.`
 - `Hey {{first_name}}, saw you raise your hand for [topic], so figured this was (hopefully) worth sending.` Only use this for explicit lead-magnet comments, replies, or opt-ins.
@@ -2295,7 +2296,7 @@ Rules:
 - default placement is **Block 3**, not Block 1. Keep Block 1 substance-first unless the archived motion clearly earns a signal-led opener without falling into source-citation / talk-at phrasing.
 - acceptable signal use by default:
   - `"Hope this is relevant if [topic] is part of the plan."`
-  - `"Saw you might be interested in [topic], so hope this is relevant."` Non-evergreen weak-signal only.
+  - `"Saw you might be interested in [topic], so hope this is relevant."` Shared Signal Discovery or non-evergreen weak-signal only.
   - `"Saw you in a few conversations around [topic], so hope this is relevant."` Shared Signal Discovery or non-evergreen weak-signal only.
   - `"Saw you in a few conversations about [topic], so may be off, but this seemed relevant."` Shared Signal Discovery or non-evergreen weak-signal only.
   - `"Found you in a thread about [topic], so may be off, but this seemed relevant."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
@@ -2315,10 +2316,10 @@ Rules:
   - `"Figured this was worth sending."`
 - signal-led opener shape is a **special case**, not the default. Use it only when the archived motion truly depends on it and the line can stay natural. For Shared Signal Discovery and non-evergreen LinkedIn-post-sourced campaigns, source bridges such as `"saw you in a few conversations around [topic], so hope this is relevant"` or `"saw you in a few conversations about [topic], so may be off, but this seemed relevant"` can be used when referencing the source makes the outreach feel less random. Avoid activity-log phrasing such as `"you commented on..."`, `"you reacted to..."`, or `"your LinkedIn activity..."` unless the approved motion is the deliberately self-aware raise-hand line for an explicit lead-magnet comment, reply, or opt-in.
 - For Shared Evergreen Signal Discovery, topic-backed weak signal-led openers
-  such as `hope this is relevant if [topic] is part of the plan` and `saw you
-  in a few conversations about/around [topic], so hope this is relevant` are
-  allowed when evidence-backed and not engagement-claiming; do not use `might be
-  interested`. Translate the source into a
+  such as `hope this is relevant if [topic] is part of the plan`, `saw you
+  might be interested in [topic], so hope this is relevant`, and `saw you in a
+  few conversations about/around [topic], so hope this is relevant` are allowed
+  when evidence-backed and not engagement-claiming. Translate the source into a
   concrete problem bridge when that is stronger, e.g.
   `"The AI-assisted GTM conversations keep coming back to one problem: turning
   good LinkedIn signal into review-ready pipeline without another dashboard."`
@@ -2332,9 +2333,9 @@ this is relevant`, `saw you in a few conversations around [topic], so hope this
 is relevant`, `saw you in a few conversations about [topic], so may be off,
 but this seemed relevant`, or `found you in a thread about [topic], so may be
 off, but this seemed relevant`. For Shared Signal Discovery, topic-backed `hope
-this is relevant` and `saw you in a few conversations ... hope this is relevant`
-are allowed when topic-level and evidence-backed; do not use `might be
-interested`. Other shared evergreen lanes should use a concrete signal/problem bridge. Use
+this is relevant`, `saw you might be interested ... hope this is relevant`, and
+`saw you in a few conversations ... hope this is relevant` are allowed when
+topic-level and evidence-backed. Other shared evergreen lanes should use a concrete signal/problem bridge. Use
 the self-aware raise-hand shapes only when
 the source was an explicit lead-magnet comment, reply, or opt-in: `saw you raise
 your hand for [topic], so figured this was (hopefully) worth sending` or `saw you

package/skills/refill-sends/SKILL.md

@@ -157,6 +157,19 @@ return concrete continuation options with campaign names, exact ids, which optio
 is already covered by the current packet, and which option needs a new approval
 packet.
 
+For `--yolo` fill/schedule requests, completion means scheduler-proven horizon
+saturation, not merely prepared/approved/ready rows. Maintain a horizon
+saturation ledger per selected sender: selected send days, gross capacity,
+future scheduler-owned scheduled cells with non-null `scheduledFor`,
+ready-to-schedule buffer, remaining scheduled gap, remaining ready-or-scheduled
+gap, and the next MCP primitive that can reduce the gap. After every
+apply/prep/start result, wait for processing, reread refill state, recompute the
+ledger, then keep applying safe bounded actions until the scheduled count fills
+the horizon or a concrete blocker/timeout is proven. If ready rows cover the
+horizon but the scheduler has not picked them up yet, run a bounded scheduler
+settle loop and report `awaiting_scheduler_after_ready_buffer` as not complete
+when the timeout is reached.
+
 In `--yolo`, the default two-day fill horizon is two send days unless
 `--until`/`untilDate` is provided. If an until date is provided, compute bounded
 gaps through that sender-local date inclusive, skipping no-send days and never

package/skills/refill-sends-workflow/SKILL.md

@@ -123,6 +123,11 @@ Use the refill-state response as the current facts receipt:
   cursor/inventory state, dedupe/DNC/provider exclusions, good-prospect yield,
   scan/import caps, and proof;
 - sender ids, healthy senders, disconnected senders, and daily capacity;
+- horizon saturation ledger per target sender: sender-local send days in scope,
+  gross horizon capacity, future scheduler-owned scheduled counts in that
+  window, ready-to-schedule buffer, remaining scheduled gap, remaining
+  ready-or-scheduled gap, and the next smallest MCP primitive that can reduce
+  the gap;
 - row/stage counts: source available, rows, enriched, passed, generated,
   approved, ready to schedule, scheduled;
 - active message prep job;
@@ -176,6 +181,18 @@ in the best same-sender campaign and keep all source-copy/prep caps tied to that
 two-day packet.
 Short form: default `--yolo refill senders` target is each eligible sender's two-send-day gap.
 
+For `--yolo` fill/schedule requests, do not treat "ready" as completion. Build
+and maintain a horizon saturation ledger for every selected sender. A sender is
+complete only when a final `get_campaign_refill_state` reread proves
+scheduler-owned scheduled cells with non-null `scheduledFor` meet or exceed the
+sender's horizon capacity for the selected send days. Ready-to-schedule rows are
+only buffer for the product scheduler. If ready plus scheduled covers the
+horizon but scheduled cells do not yet, run a bounded scheduler settle loop:
+wait, reread, recompute the ledger, and continue until scheduled coverage is
+proved or the loop reaches an explicit timeout/blocker. Timeout is
+`awaiting_scheduler_after_ready_buffer`, not success.
+Short form: `--yolo refill senders` completes only on scheduled horizon saturation or a concrete blocker.
+
 Rank candidates in this order:
 
 1. **Sender match**: campaigns whose healthy sender ids match the user-named
@@ -393,9 +410,12 @@ same refill request, do not ask the `Accept` / `Decline` question. Instead:
    packet;
 4. execute only the exact packet;
 5. after each terminal apply/prep/start result, reread state, settle processing
-   when needed, and continue with the next smallest safe action inside the same
-   bounded packet until every selected sender is loaded/awaiting scheduler,
-   scheduled, or blocked by evidence.
+   when needed, recompute the horizon saturation ledger, and continue with the
+   next smallest safe action inside the same bounded packet until every selected
+   sender is scheduled through the horizon or blocked by evidence. Do not stop
+   at "loaded" or "awaiting scheduler" unless no in-packet MCP action remains
+   and the scheduler-settle loop times out; report that as a blocker, not a
+   completed refill.
 
 In `--yolo`, do not stop after the first selected campaign if the request was
 sender-scoped and more selected senders or same-packet start-eligible campaigns
@@ -468,6 +488,19 @@ After a prep job reaches a terminal state, run `wait_for_campaign_processing`
 when generated/pass counts are still settling, then poll `get_campaign_refill_state` until `readyToSchedule` drops, scheduled counts increase, or the state clearly
 remains awaiting scheduler. Do not force scheduler fields directly.
 
+For requested fill/refill completion, continue the saturation loop after each
+poll: recompute scheduled horizon coverage by sender and date, subtract it from
+the requested horizon capacity, and decide whether another safe prep/import/
+approval pass is required. If scheduled coverage is still short and ready buffer
+is also short, run the next bounded MCP primitive that can create more eligible
+rows: `fill_campaign_horizon` for the selected evergreen target, or
+`start_campaign_message_preparation`, source import/replenishment, and bounded
+approval for the selected regular target. If scheduled coverage is short but
+ready buffer covers the gap, keep polling the scheduler until it fills or the
+explicit scheduler-settle timeout is hit. Never mark the refill complete while a
+daily limit/readback equivalent would still show the selected send day below
+capacity.
+
 ## Evergreen Campaign Discipline
 
 `fill_campaign_horizon` is a legacy evergreen-only lower-level primitive. Call it