@sellable/mcp 0.1.435 → 0.1.437

package/dist/tools/campaign-fill-routing.js

@@ -6,7 +6,7 @@ async function postCampaignFillRoute(body) {
 export const campaignFillRoutingToolDefinitions = [
     {
         name: "resolve_campaign_fill_route",
-        description: 'Audit-only resolver to call before interpreting plain "fill campaigns", "load everyone up", or similar fill requests. It decides whether the workspace has evergreen/horizon targets, currently active campaign-backed sequence targets, or no targets so the agent must ask what to create. It does not create, append, prepare, approve, schedule, launch, archive, delete, send, or call lower-level fill tools. Only call fill_campaign_horizon when this resolver returns route "evergreen_horizon" or the user explicitly requested evergreen/horizon and the returned target is eligible; otherwise route plain fill through regular campaign refill before any two-send-day horizon preparation. Exact target narrowing uses campaignId or tableId only; never fuzzy campaign names.',
+        description: 'Audit-only resolver to call before interpreting plain "fill campaigns", "load everyone up", or similar fill requests. It decides whether the workspace has evergreen/horizon targets, current dashboard-active campaign-backed sequence targets, start-eligible PAUSED targets, or no targets so the agent must ask what to create. It does not create, append, prepare, approve, schedule, launch, archive, delete, send, or call lower-level fill tools. Only call fill_campaign_horizon when this resolver returns route "evergreen_horizon" and the selected returned target is eligible; use start_campaign only for exact returned startEligible PAUSED targets after the refill workflow approval/reread packet proves starting is needed. Exact target narrowing uses campaignId or tableId only; never fuzzy campaign names.',
         inputSchema: {
             type: "object",
             properties: {

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"; 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.`,
         },
     };
 }

package/dist/tools/refill-sends.js

@@ -143,21 +143,24 @@ export function refillSendsCommand(input = {}) {
         firstOperationalSteps: [
             'Load get_subskill_prompt({ subskillName: "refill-sends-workflow" }) before any product operation.',
             `Resolve route with resolve_campaign_fill_route({ intent: "${intent}"${input.campaignId ? `, campaignId: "${input.campaignId}"` : ""}${input.tableId ? `, tableId: "${input.tableId}"` : ""} }).`,
+            'If the plain route shows stale managed waterfall evidence, archived/completed shared slots, or targets that do not cover the selected sender set, immediately call resolve_campaign_fill_route({ intent: "active" }) and inspect current dashboard-active ACTIVE/PAUSED campaign-backed sequence campaigns before declaring a sender blocked.',
             "Call list_senders and get_sender_routing, then resolve sender selectors against active enrolled campaign-backed sequence senders.",
             untilDate
                 ? `Use fill window untilDate="${untilDate}" as the inclusive sender-local through date; do not extend beyond that date without a new approval packet.`
                 : `Use the default fill window of ${horizonSendDays} sender-local send days.`,
             "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.",
+            "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.",
         ],
         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. 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."
             : 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/package.json

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

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
@@ -107,6 +108,13 @@ step using campaign names first, and stop before mutation unless the user has
 explicitly approved the exact workspace, campaign/table/source ids, caps/dates,
 approval mode, expected side effects, and stop/rollback condition.
 
+If the plain route's managed waterfall targets are stale, for example skipped
+targets show archived/completed shared slots or the returned targets do not cover
+the named sender, immediately run the active route refetch before declaring a
+sender blocked. Current dashboard-active `PAUSED` campaign-backed sequence
+campaigns are start-eligible refill candidates; read refill state before deciding
+whether to prep, approve, start, or skip. Do not treat them as archived inventory.
+
 For interactive Codex or Claude Code sessions, that approval must use the
 host-native structured question gate, not plain chat:
 
@@ -130,11 +138,24 @@ 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`, continue as far as the rendered packet safely allows. After each
+apply/prep/start result, reread state, settle processing when needed, and move to
+the next selected sender or start-eligible same-packet campaign instead of
+stopping after the first partial result. If no in-packet safe action remains,
+return concrete continuation options with campaign names, exact ids, which option
+is already covered by the current packet, and which option needs a new approval
+packet.
 
 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
@@ -59,8 +60,16 @@ campaign.
 
 1. Call `resolve_campaign_fill_route` first. Use `intent:"plain"` for generic
    fill/load language, `intent:"active"` only when the user explicitly narrowed
-   to active regular campaigns, and `intent:"evergreen"` only when the user
-   explicitly asked for evergreen or horizon work.
+   to active regular campaigns or when the plain route has stale managed
+   waterfall evidence, and `intent:"evergreen"` only when the user explicitly
+   asked for evergreen or horizon work. The resolver must refetch current
+   dashboard-active campaigns as well as managed waterfall state. If the plain
+   route returns managed waterfall targets but skipped targets include
+   archived/completed waterfall slots, or if the returned targets do not cover a
+   named sender, immediately call `resolve_campaign_fill_route({ intent:"active" })`
+   and inspect current dashboard-active `ACTIVE` and `PAUSED` campaign-backed
+   sequence campaigns before declaring a sender blocked.
+   Short form: stale waterfall bindings do not overrule current dashboard-active campaigns.
 2. Resolve sender context before choosing a target. Call `list_senders`; when a
    managed program is involved, also call `get_campaign_waterfall`, and call
    `get_sender_routing` when territory rules may constrain sender eligibility.
@@ -75,12 +84,18 @@ campaign.
    refill-state readbacks and report that inference.
    Short form: `--yolo refill senders` means all eligible enrolled senders; non-yolo asks which enrolled senders.
 3. Read `get_campaign_refill_state` for candidate campaigns from the resolver
-   result. For a broad `active_campaigns` route, inspect enough candidates to
-   identify the campaign or small campaign set that most recently had
-   scheduler-owned sends for the relevant sender set. Do not stop after the
+   result and from the required active-route refetch when managed waterfall
+   evidence looks stale. For a broad `active_campaigns` route, inspect enough
+   candidates to identify the campaign or small campaign set that most recently
+   had scheduler-owned sends for the relevant sender set. Do not stop after the
    first resolver target unless it is also the most recent sender-relevant send
-   lane.
+   lane. A current dashboard-active `PAUSED` campaign-backed sequence campaign is
+   a start-eligible refill candidate, not an archived blocker; read its refill
+   state first, then include a bounded `start_campaign` packet only when the
+   state proves healthy senders, sequence, source/list, ready/preparable rows,
+   and starting is needed for the product scheduler to schedule/send.
    Short form: Do not stop after the first resolver target unless recent-send evidence supports it.
+   Short form: `PAUSED` dashboard-active campaigns are start-eligible candidates, not skipped archived inventory.
    In `--yolo` sender-scoped mode, selecting every active campaign is still a
    scope error, but selecting one best refill campaign per eligible sender is
    expected. Pick the single highest-ranked recent-send or best-result campaign
@@ -102,7 +117,8 @@ campaign.
 Use the refill-state response as the current facts receipt:
 
 - campaign status/current step, workflow table id, table config type, and public
-  type;
+  type, including whether the route target is dashboard-active `PAUSED` and
+  start-eligible;
 - selected source list/provider identity, source id, target prospect gap,
   cursor/inventory state, dedupe/DNC/provider exclusions, good-prospect yield,
   scan/import caps, and proof;
@@ -118,9 +134,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
 
@@ -132,6 +149,13 @@ was actually sending most recently for the relevant available senders", not
 "fill every eligible target sender from the best enrolled active campaign for
 that sender", not "fill only the first/best campaign globally".
 
+When managed waterfall bindings point at archived/completed campaigns but the
+dashboard has current unarchived `ACTIVE` or `PAUSED` campaigns for the same
+sender/shared lane, prefer the current dashboard-active campaign for target
+discovery. The stale waterfall slot remains diagnostic proof, not a reason to
+skip a visible paused shared campaign that can be started through a bounded
+packet.
+
 Default `--yolo` horizon is two send days when the user asks to fill, refill,
 load, or max sends without naming a different horizon. Send days are sender-local
 days with configured sending hours; do not treat weekends or other no-send-hour
@@ -300,7 +324,30 @@ 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 route or active-campaign refetch marks a target as start-eligible, read
+  `get_campaign_refill_state` for that campaign/table before deciding whether to
+  start, prep, or skip it.
+- 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.
@@ -344,15 +391,38 @@ same refill request, do not ask the `Accept` / `Decline` question. Instead:
 3. verify the route, workspace id, campaign id, table id, source/action ids,
    caps/dates, approval mode, blockers, and side-effect class still match the
    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.
+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.
+
+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
+remain. If the first candidate is duplicate-only, already loaded, awaiting
+scheduler, source-exhausted, or otherwise blocked, continue to the next
+same-sender candidate that was already in the rendered packet and still matches
+the fresh route/refill-state evidence. If no in-packet safe action remains, stop
+before mutation and return continuation options instead of guessing.
+
+Continuation options must be campaign-name-first and concrete. For each blocked
+sender/campaign, list the next viable options with exact ids and the approval
+boundary, for example: start an already selected start-eligible paused campaign,
+repair stale waterfall bindings, replenish the current source, expand Signal
+Discovery post selection, use the next same-sender campaign, or run evergreen
+setup/repair. Mark which options are covered by the current `--yolo` packet and
+which require a new approval packet.
+Short form: in `--yolo`, go as far as the packet safely allows, then give exact continuation options.
+
+`--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 +483,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 +497,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
 
@@ -440,6 +512,10 @@ Report in campaign-name-first language:
   create;
 - source state, blockers, exact next primitive, approval required, and the
   freshness hash used.
+- for `--yolo`, how far the run continued automatically, which selected senders
+  are loaded/scheduled/awaiting scheduler, and the exact continuation options for
+  any sender/campaign that remains blocked.
 
 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.

package/skills/research/config.json

@@ -1,9 +0,0 @@
-{
-  "parallelMode": "wide",
-  "agentCount": 6,
-  "maxToolCallsPerAgent": 2,
-  "senderMaxAgents": 2,
-  "senderMaxToolCallsPerAgent": 3,
-  "progressMode": true,
-  "debugMode": true
-}