@sellable/mcp 0.1.427 → 0.1.429

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"; 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. 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, or approval, require exact visible approval 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, but still do not launch. 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. Do not call start_campaign as part of fill/schedule horizon. Do not call start_campaign as part of refill sends. Launch/start is a separate explicit human action after the operator intentionally wants sends to go out, and it must still verify that the bounded cohort is the only approved cohort and must not broad approve-all. 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. start_campaign remains forbidden until explicit launch/start approval outside refill sends.`,
+            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"; 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. 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.`,
         },
     };
 }

package/dist/tools/refill-sends.js

@@ -151,13 +151,13 @@ export function refillSendsCommand(input = {}) {
             "Fresh reread get_campaign_refill_state immediately before any import, prep, approval, or horizon-fill mutation.",
         ],
         approvalContract: yolo
-            ? "Auto-accept only the rendered bounded refill packet after fresh reread. Stop if sender set, route, ids, caps, dates, blockers, or side-effect class drift."
+            ? "Auto-accept only the rendered bounded refill packet after fresh reread. This may include start_campaign only for exact selected PAUSED campaign-backed sequence refill targets named in the packet. Stop if sender set, route, ids, caps, dates, blockers, or side-effect class drift."
             : 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.",
         forbiddenActions: [
-            "start_campaign",
-            "launch or send",
+            "start_campaign outside an exact selected PAUSED campaign-backed refill packet",
+            "manual launch/send or direct sending outside product scheduler side effects",
             "archive or delete cleanup",
             "direct scheduler writes",
             "sender reassignment",

package/dist/tools/setup-evergreen-campaigns.d.ts

@@ -1,6 +1,7 @@
 type SetupEvergreenCampaignsInput = {
     mode?: "plan" | "verify";
     depth?: "structure_only" | "customer_visible";
+    handoffMode?: "create_campaign_goals";
     yolo?: boolean;
     allConnectedSenders?: boolean;
     selectedSenderIds?: string[];
@@ -31,6 +32,11 @@ export declare const setupEvergreenCampaignsToolDefinitions: {
                 enum: string[];
                 description: string;
             };
+            handoffMode: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             yolo: {
                 type: string;
                 description: string;

package/dist/tools/setup-evergreen-campaigns.js

@@ -20,6 +20,11 @@ export const setupEvergreenCampaignsToolDefinitions = [
                     enum: ["structure_only", "customer_visible"],
                     description: 'Use "customer_visible" for full setup proof or "structure_only" when only ensuring lane shells/config.',
                 },
+                handoffMode: {
+                    type: "string",
+                    enum: ["create_campaign_goals"],
+                    description: 'plan mode only. When set to "create_campaign_goals", returns concise per-lane `$sellable:create-campaign` goal prompts and required inputs for testing simplified worker handoffs without changing verification behavior.',
+                },
                 yolo: {
                     type: "boolean",
                     description: "plan mode only. Requests auto-executable lane packets when state is safe; never authorizes cleanup, launch, scheduling, sending, or ambiguous target choice.",
@@ -88,6 +93,7 @@ export function setupEvergreenCampaigns(input) {
         mode: input.mode,
         yolo: input.mode === "verify" ? undefined : input.yolo,
         depth: input.depth,
+        handoffMode: input.mode === "verify" ? undefined : input.handoffMode,
         allConnectedSenders: input.allConnectedSenders,
         selectedSenderIds: input.selectedSenderIds,
         postEngagerSenderIds: input.postEngagerSenderIds,

package/package.json

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

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

@@ -926,48 +926,32 @@ 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** 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,
+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,
    targetPreparedMessages, maxRowsToCheck, approvalMode:"mark_ready",
    autoContinue:true })` inside the same lane worker, with bounded caps from the
-   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`.
+   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`.
    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.
-   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
+   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
    `blocked: generated_message_cell_override` instead of success.
    Do not repair by overwriting bad generated message cells and then calling the
    overwritten cells `sampleMessages`.
@@ -978,9 +962,9 @@ plain row generation. The lane worker must inline the same
    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.
-6. Poll `get_campaign_message_preparation_status` until no queued/active cells
+4. Poll `get_campaign_message_preparation_status` until no queued/active cells
    remain or a bounded stop reason is returned.
-7. Use `get_campaign_messages_preview` or `select_campaign_cells` to inspect
+5. 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.
@@ -990,21 +974,16 @@ plain row generation. The lane worker must inline the same
    approvedGeneratedMessageCount exactly 1. Do not report completion with 2+
    approved rows.
    Approval shorthand: Do not report completion with 2+ approved rows.
-8. Continue to `attach_recommended_sequence({ campaignId, currentStep:"send" })`
+6. 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 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.
+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.
 The only accepted statusSource values are exactly `branch` and
 `packaged-generate-messages-worker`; descriptive aliases such as
 `package-readback-local-thread` are rejected.
@@ -1358,25 +1337,16 @@ 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 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`.
+      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.
 
    - **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.
@@ -1414,15 +1384,12 @@ 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 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
+     through the lane worker's packaged message-prep path with
+     `statusSource:"packaged-generate-messages-worker"`,
+     `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. Row prep alone is not prompt proof. The
-     proof must include
+     only downstream cell evidence. 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/refill-sends/SKILL.md

@@ -24,6 +24,7 @@ allowed-tools:
   - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_campaign_message_preparation_status
   - mcp__sellable__start_campaign_message_preparation
+  - mcp__sellable__start_campaign
   - mcp__sellable__cancel_campaign_message_preparation
   - mcp__sellable__import_leads
   - mcp__sellable__wait_for_lead_list_ready
@@ -130,11 +131,16 @@ the active workspace. Without `--yolo`, if Christian did not name senders, ask
 which eligible enrolled senders to refill before choosing campaigns or mutating.
 
 `--yolo` only covers the exact sender set, per-sender target campaigns, caps,
-approval mode, and side effects in the packet. It does not authorize
-launch/start, sending, archive or delete cleanup, direct scheduler writes, sender
-reassignment, or campaigns outside those selected for the eligible sender set.
-Stop and re-plan if the route, sender set, ids, caps, blockers, or side-effect
-class drift before mutation.
+approval mode, and side effects in the packet. It may authorize `start_campaign`
+only for selected `PAUSED`, dashboard-active, campaign-backed sequence refill
+targets when the rendered packet names the exact campaign ids and start side
+effect. Starting a paused campaign can let the product scheduler schedule/send
+approved eligible sequence actions, so include that expected side effect in the
+packet. It does not authorize starting unrelated, archived, completed, draft, or
+direct campaigns, separate launch/send actions, archive or delete cleanup,
+direct scheduler writes, sender reassignment, or campaigns outside those
+selected for the eligible sender set. Stop and re-plan if the route, sender set,
+ids, caps, blockers, or side-effect class drift before mutation.
 
 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

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

@@ -15,6 +15,7 @@ allowed-tools:
   - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_campaign_message_preparation_status
   - mcp__sellable__start_campaign_message_preparation
+  - mcp__sellable__start_campaign
   - mcp__sellable__cancel_campaign_message_preparation
   - mcp__sellable__import_leads
   - mcp__sellable__wait_for_lead_list_ready
@@ -118,9 +119,10 @@ Use the refill-state response as the current facts receipt:
 - `freshness.stateHash` and exact campaign/table/workspace ids.
 
 Empty or unsafe states stop with the blocker: no fillable target, missing or deleted campaign,
-missing table, paused/archive campaign, zero sender capacity, zero source candidates,
-zero viable rows, no approved/preparable rows, active prep job, awaiting
-scheduler, or unsupported direct campaign type.
+missing table, archived/completed campaign, paused campaign without an explicit
+selected-start packet, zero sender capacity, zero source candidates, zero viable
+rows, no approved/preparable rows, active prep job, awaiting scheduler, or
+unsupported direct campaign type.
 
 ## Regular Campaign Decision
 
@@ -300,7 +302,27 @@ Approval mode:
 - default is `approvalMode:"mark_ready"`, not approve;
 - use `approvalMode:"approve"` only when the user explicitly asks to approve
   messages or schedule sends and has approved the exact bounded cohort;
-- never launch/start a campaign from refill.
+- `start_campaign` is allowed only as a bounded start/resume step for a
+  selected `PAUSED`, dashboard-active, campaign-backed sequence refill target;
+- never launch/start unrelated, archived, completed, draft, direct, or
+  non-selected campaigns from refill.
+
+Paused campaign start discipline:
+
+- `PAUSED`, dashboard-active campaign-backed sequence campaigns are existing
+  refill targets, not archived inventory.
+- If the selected refill target is `PAUSED` and has healthy senders, sequence,
+  source/list, and ready/preparable rows or a bounded source/prep packet, the
+  final packet may include `start_campaign` when starting is needed for the
+  scheduler to schedule/send approved eligible rows.
+- In non-yolo mode, the `Accept` choice must say that starting the paused
+  campaign can let the product scheduler schedule/send approved eligible
+  sequence actions.
+- In `--yolo`, `start_campaign` is auto-accepted only for the exact selected
+  paused campaign ids, sender scope, caps, approval mode, and start side effect
+  named in the packet after the final reread.
+- Do not start if the campaign is archived, completed, draft, direct, lacks a
+  sequence/senders/source, has no viable row path, or state drifts.
 
 Before prep or approval mutation, reread `get_campaign_refill_state` and compare
 `freshness.stateHash`, campaign id, table id, workspace id, source id, and caps.
@@ -346,13 +368,15 @@ same refill request, do not ask the `Accept` / `Decline` question. Instead:
    packet;
 4. execute only the exact packet.
 
-`--yolo` never authorizes launch/start, sending, archive/delete cleanup, raw
-scheduler writes, sender reassignment, unrelated campaigns, extra senders beyond
-the eligible sender set, or higher caps than the packet named. In sender-scoped
-`--yolo`, a bounded packet containing all eligible enrolled senders and at most
-one best campaign per sender is covered; arbitrary expanded campaign sets are
-not. If any state or scope drifts, stop and re-plan instead of auto-accepting the
-changed action.
+`--yolo` authorizes `start_campaign` only for selected `PAUSED` refill targets
+named in the exact packet. It never authorizes starting unrelated, archived,
+completed, draft, or direct campaigns, separate launch/send actions,
+archive/delete cleanup, raw scheduler writes, sender reassignment, extra senders
+beyond the eligible sender set, or higher caps than the packet named. In
+sender-scoped `--yolo`, a bounded packet containing all eligible enrolled
+senders and at most one best campaign per sender is covered; arbitrary expanded
+campaign sets are not. If any state or scope drifts, stop and re-plan instead of
+auto-accepting the changed action.
 Short form: all eligible enrolled senders are covered by sender-scoped `--yolo`; arbitrary expanded campaign sets are not.
 Short form: direct scheduler writes are not covered by `--yolo`.
 Short form: stop and re-plan instead of auto-accepting the changed action.
@@ -413,7 +437,9 @@ the current source or ask for more research instead of walking the ladder.
 
 ## Hard Safety Rules
 
-- Never call start or launch tools.
+- Never call launch/start tools except `start_campaign` for an exact selected
+  `PAUSED`, dashboard-active, campaign-backed sequence refill target in the
+  rendered packet.
 - Never raw-write `scheduledFor`, `scheduledAt`, scheduled status, or sender
   assignment fields.
 - Never expose internal direct campaign types as an operator refill path.
@@ -425,8 +451,8 @@ the current source or ask for more research instead of walking the ladder.
 - In interactive Codex or Claude Code, that explicit approval must be collected
   through the host-native `Accept` / `Decline` question gate.
 - `--yolo` in the current refill request is explicit auto-accept for the
-  rendered bounded refill packet only; it does not loosen the launch/send,
-  scheduler-write, archive/delete, or drift rules above.
+  rendered bounded refill packet only; it does not loosen the unrelated-campaign
+  start/send, scheduler-write, archive/delete, or drift rules above.
 
 ## Report
 
@@ -442,4 +468,5 @@ Report in campaign-name-first language:
   freshness hash used.
 
 Keep ids visible but secondary: show them under "Exact target" or "Proof", not
-as the main decision text. Say explicitly: nothing was launched and nothing was sent.
+as the main decision text. Say explicitly whether a selected paused campaign was
+started; otherwise say nothing was started and nothing was sent.