@sellable/mcp 0.1.337 → 0.1.338

package/dist/server.js

@@ -9,7 +9,7 @@ import { prepareCampaignAbTest } from "./tools/campaign-ab-test.js";
 import { resolveCampaignFillRoute } from "./tools/campaign-fill-routing.js";
 import { fillCampaignHorizon } from "./tools/campaign-horizon-fill.js";
 import { cancelPrepareCampaignMessages, getPrepareCampaignMessagesStatus, startPrepareCampaignMessages, } from "./tools/campaign-message-preparation.js";
-import { refillCampaignSends } from "./tools/refill-campaign-sends.js";
+import { getCampaignRefillState } from "./tools/campaign-refill-state.js";
 import { getCampaignTableSchema, queueCampaignCells, recordCampaignReviewBatch, reviseMessageTemplateAndRerun, selectCampaignCells, waitForCampaignProcessing, } from "./tools/campaign-processing.js";
 import { createCampaign, duplicateCampaign, getCampaign, getCampaignMessagesPreview, getCampaigns, pauseCampaign, startCampaign, updateCampaign, updateCampaignBrief, } from "./tools/campaigns.js";
 import { queueCells, updateCell } from "./tools/cells.js";
@@ -184,13 +184,8 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
             case "resolve_campaign_fill_route":
                 result = await resolveCampaignFillRoute(args);
                 break;
-            case "refill_campaign_sends":
-                result = await refillCampaignSends(args);
-                if (args?.mode === "apply" && Array.isArray(result?.appliedCampaignIds)) {
-                    for (const campaignId of result.appliedCampaignIds) {
-                        markCampaignContextDirty(campaignId, "refill_campaign_sends");
-                    }
-                }
+            case "get_campaign_refill_state":
+                result = await getCampaignRefillState(args);
                 break;
             case "fill_campaign_horizon":
                 result = await fillCampaignHorizon(args);

package/dist/tools/campaign-refill-state.d.ts

@@ -0,0 +1,25 @@
+type GetCampaignRefillStateInput = {
+    campaignId?: string;
+    tableId?: string;
+};
+export declare const campaignRefillStateToolDefinitions: {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            campaignId: {
+                type: string;
+                description: string;
+            };
+            tableId: {
+                type: string;
+                description: string;
+            };
+        };
+        required: never[];
+        additionalProperties: boolean;
+    };
+}[];
+export declare function getCampaignRefillState(input: GetCampaignRefillStateInput): Promise<unknown>;
+export {};

package/dist/tools/campaign-refill-state.js

@@ -0,0 +1,32 @@
+import { getApi } from "../api.js";
+async function postCampaignRefillState(body) {
+    const api = getApi();
+    return api.post("/api/v3/mcp/campaign-refill-state", body);
+}
+export const campaignRefillStateToolDefinitions = [
+    {
+        name: "get_campaign_refill_state",
+        description: "read-only refill research primitive to call after resolve_campaign_fill_route and before any source import, message preparation, approval, scheduling, or horizon fill decision. It returns current campaign/table/source/sender/funnel/scheduler diagnostics plus freshness state for one exact campaignId or tableId only. This tool does not create rows, does not import leads, does not prepare messages, does not approve messages, does not schedule sends, does not launch campaigns, and does not expose direct campaign types as refillable targets. Exact targeting uses campaignId or tableId only; never pass campaign names or table names.",
+        inputSchema: {
+            type: "object",
+            properties: {
+                campaignId: {
+                    type: "string",
+                    description: "Optional exact CampaignOffer.id from resolve_campaign_fill_route. Do not pass campaign names.",
+                },
+                tableId: {
+                    type: "string",
+                    description: "Optional exact WorkflowTable.id from resolve_campaign_fill_route. Do not pass table names.",
+                },
+            },
+            required: [],
+            additionalProperties: false,
+        },
+    },
+];
+export function getCampaignRefillState(input) {
+    return postCampaignRefillState({
+        campaignId: input.campaignId,
+        tableId: input.tableId,
+    });
+}

package/dist/tools/prompts.d.ts

@@ -137,7 +137,7 @@ export interface PostFindLeadsScoutRegistryResponse {
 }
 export declare const DEFAULT_SUBSKILL_PROMPT_CHUNK_CHARS = 48000;
 export declare const MAX_SUBSKILL_PROMPT_CHUNK_CHARS = 48000;
-export declare const ALLOWED_SUBSKILL_PROMPT_NAMES: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+export declare const ALLOWED_SUBSKILL_PROMPT_NAMES: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "refill-sends-workflow", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
 export declare const promptToolDefinitions: ({
     name: string;
     description: string;
@@ -181,7 +181,7 @@ export declare const promptToolDefinitions: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "refill-sends-workflow", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             offset: {
@@ -216,7 +216,7 @@ export declare const promptToolDefinitions: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "refill-sends-workflow", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             assetPath: {

package/dist/tools/prompts.js

@@ -37,6 +37,7 @@ export const ALLOWED_SUBSKILL_PROMPT_NAMES = [
     "interview",
     "load-voice",
     "refresh-sender-engagement",
+    "refill-sends-workflow",
     "research",
     "research-prospect",
     "research-sender",
@@ -371,7 +372,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, first call refill_campaign_sends({ mode:"plan", intent:"plain" }). Plain fill is not an alias for fill_campaign_horizon or campaign creation. If no --yolo is present, report the plan and stop. If --yolo is present, call plan first, inspect blockers, then call refill_campaign_sends({ mode:"apply", yolo:true, planRevision, actionIds }) using only selected immutable actionIds from the fresh plan. Use resolve_campaign_fill_route, fill_campaign_horizon, and start_campaign_message_preparation only as fallback/lower-level diagnostics when refill_campaign_sends is unavailable or when the refill command returns an evergreen subplan. fill_campaign_horizon is evergreen-only and is not the generic regular-campaign fill path. Treat "fill up/load sends" as capacity-fill preparation: calculate the bounded target from sender capacity when needed, then let the command plan source, enrichment, ICP/rubric, Generate Message propagation, approval/ready state, scheduler reread, and blockers. 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. 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 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 and get_campaign_refill_state before any mutation. 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. Treat "fill up/load sends" as capacity-fill preparation: calculate the bounded target from sender capacity when needed, then use the refill workflow to decide same-campaign source replenishment, enrichment/prep, approval/ready state, scheduler reread, and blockers. 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 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.`,
         },
     };
 }

package/dist/tools/registry.d.ts

@@ -236,7 +236,7 @@ export declare const allTools: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "refill-sends-workflow", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             offset: {
@@ -271,7 +271,7 @@ export declare const allTools: ({
         properties: {
             subskillName: {
                 type: string;
-                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
+                enum: readonly ["building-gtm-tables", "content", "create-ab-test", "create-campaign", "create-campaign-brief", "create-campaign-v2", "create-campaign-v2-tail", "create-campaign-v2-validation", "create-evergreen-campaigns", "create-post", "create-rubric", "engage", "enrich-prospects", "fill-send-horizon", "find-leads", "foundation", "generate-messages", "interview", "load-voice", "refresh-sender-engagement", "refill-sends-workflow", "research", "research-prospect", "research-sender", "weekly-campaign-summary", "workflow-sequences"];
                 description: string;
             };
             assetPath: {
@@ -660,82 +660,6 @@ export declare const allTools: ({
         additionalProperties: boolean;
         required?: undefined;
     };
-} | {
-    name: string;
-    description: string;
-    inputSchema: {
-        type: string;
-        properties: {
-            mode: {
-                type: string;
-                enum: string[];
-                default: string;
-                description: string;
-            };
-            intent: {
-                type: string;
-                enum: string[];
-                description: string;
-            };
-            campaignIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            tableIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            sendWindowDays: {
-                type: string;
-                minimum: number;
-                maximum: number;
-                description: string;
-            };
-            targetDates: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            targetScheduledSends: {
-                type: string;
-                minimum: number;
-                maximum: number;
-                description: string;
-            };
-            approvalMode: {
-                type: string;
-                enum: string[];
-                description: string;
-            };
-            yolo: {
-                type: string;
-                description: string;
-            };
-            planRevision: {
-                type: string;
-                description: string;
-            };
-            actionIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                description: string;
-            };
-        };
-        additionalProperties: boolean;
-    };
 } | {
     name: string;
     description: string;

package/dist/tools/registry.js

@@ -5,8 +5,8 @@ import { campaignAbTestToolDefinitions } from "./campaign-ab-test.js";
 import { campaignFillRoutingToolDefinitions } from "./campaign-fill-routing.js";
 import { campaignHorizonFillToolDefinitions } from "./campaign-horizon-fill.js";
 import { campaignMessagePreparationToolDefinitions } from "./campaign-message-preparation.js";
+import { campaignRefillStateToolDefinitions } from "./campaign-refill-state.js";
 import { campaignProcessingToolDefinitions } from "./campaign-processing.js";
-import { refillCampaignSendsToolDefinitions } from "./refill-campaign-sends.js";
 import { campaignToolDefinitions } from "./campaigns.js";
 import { cellToolDefinitions } from "./cells.js";
 import { startCliLoginToolDef, waitForCliLoginToolDef } from "./cli-login.js";
@@ -46,7 +46,7 @@ export const allTools = [
     ...campaignToolDefinitions,
     ...campaignAbTestToolDefinitions,
     ...campaignFillRoutingToolDefinitions,
-    ...refillCampaignSendsToolDefinitions,
+    ...campaignRefillStateToolDefinitions,
     ...campaignHorizonFillToolDefinitions,
     ...campaignMessagePreparationToolDefinitions,
     ...campaignProcessingToolDefinitions,

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -47,8 +47,8 @@ allowed-tools:
   - mcp__sellable__record_campaign_review_batch
   - mcp__sellable__queue_campaign_cells
   - mcp__sellable__wait_for_campaign_processing
-  - mcp__sellable__refill_campaign_sends
   - mcp__sellable__resolve_campaign_fill_route
+  - mcp__sellable__get_campaign_refill_state
   - mcp__sellable__fill_campaign_horizon
   - mcp__sellable__start_campaign_message_preparation
   - mcp__sellable__get_campaign_message_preparation_status
@@ -118,44 +118,35 @@ The default path stays the existing first campaign-table execution slice:
 review the normal `reviewBatchLimit:15`, approve reviewed draft rows, then move
 to Settings/sequence/final greenlight. For any plain post-mint fill request
 such as "fill campaigns", "fill up", "refill sends", "max out sends", or
-"load sends", first call `refill_campaign_sends({ mode:"plan", intent:"plain" })`.
-If the user did not include `--yolo`, report the plan and stop. If the user did
-include `--yolo`, call plan first, inspect blockers, then call
-`refill_campaign_sends({ mode:"apply", yolo:true, planRevision, actionIds })`
-using only the selected immutable action IDs from the fresh plan. Plain fill is
-not an alias for `fill_campaign_horizon` or campaign creation. Keep
-`resolve_campaign_fill_route`, `fill_campaign_horizon`, and
-`start_campaign_message_preparation` as fallback/lower-level diagnostics only
-when `refill_campaign_sends` is unavailable or when the refill command itself
-returns an evergreen subplan. `fill_campaign_horizon` is evergreen-only and
-must not be used for regular campaign refill. When more leads are needed, the
-plan must recommend same-campaign source-ladder replenishment; do not create
-warm-post-engager side campaigns, on-demand campaigns, or unrelated campaigns.
-If fallback `resolve_campaign_fill_route` returns `route:"ask_create"`, ask
-whether to create a normal campaign or evergreen campaigns; campaign creation is
-never the default response to plain fill.
+"load sends", hand off to the skill-led refill workflow:
+
+```text
+get_subskill_prompt({ subskillName: "refill-sends-workflow" })
+resolve_campaign_fill_route
+get_campaign_refill_state
+```
+
+Plain fill is not an alias for `fill_campaign_horizon` or campaign creation.
+`fill_campaign_horizon` is evergreen-only and must not be used for regular
+campaign refill. If route resolution returns `route:"ask_create"`, ask whether
+to create a normal campaign or evergreen campaigns; campaign creation is never
+the default response to plain fill. When more leads are needed, the refill
+workflow must recommend same-campaign source-ladder replenishment; do not
+create warm-post-engager side campaigns, on-demand campaigns, or unrelated
+campaigns.
+
 Treat active fills as capacity-fill preparation: calculate the bounded target
-from sender capacity when needed, then let the preparation job queue pending
-`Enrich Prospect` cells, wait for ICP/rubric and Generate Message cells to
-cascade, and mark ready or approve only the target cohort. Do not count
-`checkedRows` as enriched rows; it is only the table cursor. Use
-`progress.enrichedRows`, `progress.needsEnrichRows`, `activeCellCount`,
-`preparedMessages`, `approvedRows`, active preparation jobs, sender-health
-blockers, target, estimated row budget remaining, and `stopReason` to explain
-progress. If the user says "prepare/generate X messages", set
-`targetPreparedMessages:X`, omit `maxRowsToCheck`, and keep
-`approvalMode:"mark_ready"`. The backend calibrates on at least 100 actually
-enriched rows, estimates the row budget from observed rubric/pass yield, caps
-`maxRowsToCheck` at 300, then continues in batches capped at 100 newly checked
-rows. It will not pull another row batch while the current checked batch still
-has queueable or active cells. If the user says "approve X messages", use
-`approvalMode:"approve"` but still do not launch. If the user says "schedule X
-sends" or asks to fill sender sends, use `approvalMode:"approve"` only when
-the user explicitly asked for approval, approve exactly the bounded X-message
-cohort during preparation, then re-read scheduled counts; if scheduler-owned
-cells are not present, report prepared/approved/ready awaiting scheduler
-instead of success. Final launch remains a separate explicit user greenlight
-and must verify that bounded cohort and must not broad approve-all.
+from sender capacity when needed, then use the refill workflow to decide source
+replenishment, enrichment/prep, approval policy, and scheduler proof. Mutation
+requires exact visible approval and a fresh `get_campaign_refill_state` reread.
+If the user says "prepare/generate X messages", use message-prep primitives with
+`targetPreparedMessages:X` and default `approvalMode:"mark_ready"`. If the user
+says "approve X messages", use `approvalMode:"approve"` only for the bounded
+cohort and still do not launch. If the user says "schedule X sends", approve
+only when explicitly requested, then reread scheduled counts; if
+scheduler-owned cells are not present, report prepared/approved/ready awaiting
+scheduler instead of success. Final launch remains a separate explicit user
+greenlight and must not broad approve-all.
 When approving reviewed draft rows in the campaign table, resolve the actual
 visible `Approved` cells with `select_campaign_cells({ columnRole: "approved",
 rowSelector: { type: "rowIds", rowIds } })` and `update_cell` those returned

package/skills/fill-send-horizon/SKILL.md

@@ -1,94 +1,33 @@
 ---
 name: fill-send-horizon
-description: Compatibility alias for refill-sends. Plain fill, refill sends, max out sends, load everyone up, and fill horizon sends now route to refill_campaign_sends plan mode first. Legacy fill_campaign_horizon remains evergreen-only lower-level audit/apply.
+description: Compatibility alias for refill-sends. Fill horizon requests load the skill-led refill workflow; fill_campaign_horizon remains evergreen-only lower-level execution.
 visibility: internal
 allowed-tools:
-  - mcp__sellable__refill_campaign_sends
+  - mcp__sellable__get_subskill_prompt
   - mcp__sellable__resolve_campaign_fill_route
+  - mcp__sellable__get_campaign_refill_state
   - mcp__sellable__fill_campaign_horizon
 ---
 
 # Fill Send Horizon
 
-<role>
-This is a compatibility alias. For plain operator language, use the new refill
-command first: `refill_campaign_sends({ mode: "plan", intent: "plain" })`.
-The word "horizon" means send window. Do not use `fill_campaign_horizon` as the
-generic regular-campaign fill path.
-</role>
-
-<inputs>
-The invoking prompt (often a scheduled automation) names the targets or gives a
-plain fill request. Route before acting:
-
-- Plain fill/load requests ("fill campaigns", "load everyone up", "fill send horizon") — first call `refill_campaign_sends({ mode: "plan", intent: "plain" })`.
-- If no `--yolo`, report the plan and stop.
-- If `--yolo`, call plan first, then apply only with the returned `planRevision` and selected `actionIds`.
-- If `refill_campaign_sends` is unavailable in an older install, use `resolve_campaign_fill_route` and read-only diagnostics only, then stop before mutation.
-
-Optional inputs: `targetPreparedMessages` (default: leave unset for the adaptive default), an explicit "approve" instruction (see safety rules), and a **waterfall priority order** (see below).
-</inputs>
-
-<objective>
-Route result handling:
-
-1. If `refill_campaign_sends` returns regular campaigns, report the ranked plan.
-2. If it returns evergreen campaigns, report the current-source audit and any legacy evergreen send-window subplan.
-3. If it returns blockers, report them and stop.
-4. If `--yolo` is approved, apply only selected immutable actions from the plan.
-
-For each active campaign target:
-
-1. Confirm workspace, `workflowTableId`, `campaignStatus:"ACTIVE"`, sender IDs, current stats, and scheduled/ready/approved/prepared counts where available. Skip and report PAUSED/DRAFT/ARCHIVED targets separately.
-2. Check `get_campaign_message_preparation_status({ campaignId, tableId })` first. If an active prep job exists for the same target, report it and do not start an overlapping job.
-3. If rows already exist, let `refill_campaign_sends` plan/apply the bounded preparation action. Do not call lower-level preparation manually unless the command is unavailable.
-4. If source is thin and the user asked to add/fill more leads, source fresh Signal Discovery/post engagement leads only into the same `campaignOfferId`/`campaignId` context. Do not create warm-post-engager side campaigns, on-demand campaigns, or unrelated campaigns.
-5. Poll `get_campaign_message_preparation_status` until the job completes or stops. Read `progress.enrichedRows`, `preparedMessages`, `approvedMessages`, `activeCellCount`, active prep blockers, and `stopReason`; never treat `checkedRows` as enriched rows.
-6. After any prep/approval work, re-read campaign/table state. Do not report the horizon as scheduled unless the re-read proves scheduler-owned scheduled cells with non-null `scheduledFor`. If only prepared/approved/ready cells exist, report the exact state as `prepared/approved/ready - awaiting scheduler`, not complete.
-7. Report appended rows, enriched rows, prepared messages, approved messages, ready-to-schedule rows, scheduler-owned scheduled cells, active preparation jobs, and sender-health blockers such as disconnected Sales Nav, deleted LinkedIn accounts, missing sequence state, or exhausted source rows as separate lines.
-</objective>
-
-<waterfall>
-## Campaign hierarchy (waterfall order)
-
-Evergreen/horizon fill order is **stored workspace state** returned by
-`resolve_campaign_fill_route`, not something each automation restates. Resolve
-it in this precedence:
-
-1. **Stored hierarchy (default)**: the resolver reads the stored managed waterfall and returns slots in priority order with campaign offer IDs included. Fill in that order.
-2. **Per-invocation override**: if the invoking prompt states an explicit order ("fill in this order: Signal Discovery, Post Engagers"), use it for this run only and say in the report that the stored order was overridden. To change the order durably, use `set_campaign_waterfall_order` — but only when the user/automation explicitly asks to change the hierarchy, never as a side effect of a fill run.
-3. **No stored hierarchy**: resolver returns active targets or ask-create. Do not invent a conventional evergreen waterfall. Ask whether to create normal campaigns or evergreen campaigns only after `ask_create`.
-
-Fill mechanics, whatever the source of the order:
-
-- **Fill the top lane first.** Move to the next lane ONLY when the current one stops with source exhaustion / no more eligible rows — never because it is merely slow.
-- **Stop descending once the horizon target is met.** If the warm lane alone fills the horizon, the cold lanes get nothing this run — that is correct, not a gap.
-- **Report per lane** so the operator can see the waterfall working:
+This is a compatibility alias. For plain operator language such as "fill",
+"refill sends", "max out sends", "load everyone up", or "fill horizon sends",
+load the canonical workflow first:
 
+```text
+get_subskill_prompt({ subskillName: "refill-sends-workflow" })
 ```
-csreyes92 waterfall (stored order): Post Engagers filled 4/4 (horizon met — lower lanes skipped)
-thomas waterfall (stored order): Post Engagers 1/4 (source thin) → Shared Signal Discovery 3/3 remaining
-```
-</waterfall>
 
-<safety>
-- **Never call `start_campaign`, `start_on_demand_campaign`, or `start_direct_campaign`.** Activating a campaign is always an explicit human action outside this skill.
-- Use `approvalMode: "approve"` ONLY when the invoking prompt explicitly says to auto-approve (e.g. "fill and approve"). Default is `mark_ready` — a human approves in the UI.
-- Auto-approval is not scheduling. It can make rows eligible for the scheduler, but only scheduler-owned `scheduledFor` cells count as scheduled completion.
-- Never use a sender from one workspace for another workspace's campaign. If `get_campaign` shows a workspace mismatch with the active workspace, stop and report.
-- Paid InMail: never opt a campaign into paid-InMail templates or spend credits. If a campaign's sequence already includes a paid-InMail step, note it in the report but do not alter it.
-- Do not write `WorkflowTableCell.scheduledFor` directly. Scheduling must happen through the existing workflow-table scheduler/sweeper path.
-- This skill fills readiness and verifies scheduling; the product's sweeper sends only from ACTIVE campaigns, only approved rows, only inside sending hours. Say so in the report so the operator knows nothing went out.
-</safety>
+Then follow the workflow:
 
-<output>
-One compact report:
+1. Call `resolve_campaign_fill_route`.
+2. Call `get_campaign_refill_state` for the exact selected target.
+3. Treat public targets as regular campaigns or evergreen campaigns only.
+4. Stop on `unsupported_campaign_type` for internal direct campaign tables.
+5. Use `fill_campaign_horizon` only after route and refill-state evidence prove
+   the target is an evergreen campaign.
 
-```
-Fill Send Horizon — {date}
-• {Campaign A}: scheduled {s}/{target} for the horizon ({r} ready, {p} prepared, {a} approved) — {state}
-• {Campaign B}: source thin after {k} prepared — refill via refresh-sender-engagement
-Next operator action: {approve messages | wait for scheduler | refresh source | launch separately if you intentionally want sends to go out}
-Nothing was sent or launched; campaigns remain in their current status. Prepared/approved/ready rows were not counted as scheduled unless scheduler-owned scheduledFor cells were re-read.
-```
-</output>
+Do not start or launch campaigns. Do not raw-write scheduler fields. Do not
+claim scheduled success without rereading scheduler-owned cells with non-null
+`scheduledFor`.

package/skills/refill-sends/SKILL.md

@@ -1,57 +1,54 @@
 ---
 name: refill-sends
-description: Plan and optionally apply bounded campaign send refill work. Plain fill, refill sends, max out sends, load everyone up, and fill send window requests route to refill_campaign_sends plan mode first. Apply requires --yolo, a fresh planRevision, and selected actionIds.
-visibility: internal
+description: Plan regular campaign and evergreen campaign send refill work through the skill-led refill workflow.
+visibility: public
 allowed-tools:
-  - mcp__sellable__refill_campaign_sends
+  - mcp__sellable__get_subskill_prompt
+  - mcp__sellable__search_subskill_prompts
   - mcp__sellable__resolve_campaign_fill_route
+  - mcp__sellable__get_campaign_refill_state
   - mcp__sellable__fill_campaign_horizon
   - mcp__sellable__get_campaign
   - mcp__sellable__get_campaign_message_preparation_status
+  - mcp__sellable__start_campaign_message_preparation
+  - mcp__sellable__cancel_campaign_message_preparation
+  - mcp__sellable__import_leads
+  - mcp__sellable__wait_for_lead_list_ready
+  - mcp__sellable__confirm_lead_list
+  - mcp__sellable__search_signals
+  - mcp__sellable__fetch_post_engagers
+  - mcp__sellable__search_sales_nav
+  - mcp__sellable__lookup_sales_nav_filter
+  - mcp__sellable__search_prospeo
+  - mcp__sellable__search_prospeo_companies
+  - mcp__sellable__confirm_prospeo_company_accounts
+  - mcp__sellable__load_csv_linkedin_leads
+  - mcp__sellable__load_csv_domains
+  - mcp__sellable__list_dnc_entries
+  - mcp__sellable__load_csv_dnc_entries
+  - mcp__sellable__get_rows
+  - mcp__sellable__get_rows_minimal
+  - mcp__sellable__get_table_rows
 ---
 
 # Refill Sends
 
-Use this skill for plain operator requests such as "fill", "refill sends",
+Use this public wrapper for plain operator requests such as "fill", "refill sends",
 "max out sends", "load everyone up", or "fill horizon sends".
 
-## Default Flow
+Load the internal workflow prompt before taking any operational step:
 
-1. Call `refill_campaign_sends({ mode: "plan", intent: "plain" })`.
-2. Report the returned plan and stop when the user did not include `--yolo`.
-3. If the user included `--yolo`, still call plan first. Inspect blockers.
-4. Apply only by calling `refill_campaign_sends({ mode: "apply", yolo: true, planRevision, actionIds })` with action IDs copied from the fresh plan.
+```text
+get_subskill_prompt({ subskillName: "refill-sends-workflow" })
+```
 
-Do not manually chain lower-level tools unless `refill_campaign_sends` is
-unavailable. In that fallback case, run read-only diagnostics only, then stop
-before mutation.
-
-## Public Concepts
-
-- Regular campaign: a campaign with a brief, source, sequence, senders, and a
-  campaign-backed workflow table.
-- Evergreen campaign: a managed always-on send-window lane.
-- Send window: the dates/capacity the operator wants kept full.
-
-Do not expose internal direct campaign types as an operator refill path. If the
-plan reports `unsupported_campaign_type`, report it and stop.
-
-## Safety Rules
-
-- Default mode is read-only plan.
-- Apply requires `yolo: true`, a fresh stable `planRevision`, and selected immutable `actionIds`.
-- Production yolo/apply requires explicit approval of workspace, campaign/table IDs, selected action IDs, caps/dates, and expected side effects.
-- Never create side campaigns.
-- Never call `start_campaign`, `start_on_demand_campaign`, or `start_direct_campaign`.
-- Never raw-write scheduled fields or sender assignment fields.
-- Scheduled success requires rereading scheduler-owned cells with non-null `scheduledFor`.
-- Generate Message normally happens through downstream propagation from enrichment/prep, not as a standalone action.
-
-## Evergreen Source Ladder
-
-For evergreen campaigns, do not move down the source ladder until the plan proves
-the current source is exhausted or cannot produce enough good prospects within
-configured caps. Required evidence includes source ID, target prospect gap,
-cursor/inventory state, dedupe/DNC/provider exclusions, good-prospect yield,
-and scan/import caps.
+Then follow that workflow exactly. The default path is read-only research:
+resolve the route, read target refill state, report the next safe step, 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.
 
+Public concepts are regular campaign and evergreen campaign. Internal direct
+campaign types are unsupported refill targets. `fill_campaign_horizon` is only a
+legacy evergreen-only lower-level primitive after route and refill-state
+evidence proves an evergreen target.

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

@@ -0,0 +1,172 @@
+---
+name: refill-sends-workflow
+description: Internal skill-led refill sends workflow for regular campaigns and evergreen campaigns.
+visibility: internal
+allowed-tools:
+  - mcp__sellable__resolve_campaign_fill_route
+  - mcp__sellable__get_campaign_refill_state
+  - mcp__sellable__fill_campaign_horizon
+  - mcp__sellable__get_campaign
+  - mcp__sellable__get_campaign_message_preparation_status
+  - mcp__sellable__start_campaign_message_preparation
+  - mcp__sellable__cancel_campaign_message_preparation
+  - mcp__sellable__import_leads
+  - mcp__sellable__wait_for_lead_list_ready
+  - mcp__sellable__confirm_lead_list
+  - mcp__sellable__search_signals
+  - mcp__sellable__fetch_post_engagers
+  - mcp__sellable__search_sales_nav
+  - mcp__sellable__lookup_sales_nav_filter
+  - mcp__sellable__search_prospeo
+  - mcp__sellable__search_prospeo_companies
+  - mcp__sellable__confirm_prospeo_company_accounts
+  - mcp__sellable__load_csv_linkedin_leads
+  - mcp__sellable__load_csv_domains
+  - mcp__sellable__list_dnc_entries
+  - mcp__sellable__load_csv_dnc_entries
+  - mcp__sellable__get_rows
+  - mcp__sellable__get_rows_minimal
+  - mcp__sellable__get_table_rows
+---
+
+# Refill Sends Workflow
+
+Default mode is read-only research. This workflow decides the next safe refill
+step in the parent thread; backend tools remain narrow route, state, source,
+prep, readiness, and evergreen primitives.
+
+## Entry
+
+Plain phrases that enter here include "fill", "refill sends", "max out sends",
+"load everyone up", and "fill horizon sends".
+
+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.
+2. Pick exact ids from the resolver result. Do not use campaign names or table
+   names as target identifiers.
+3. Call `get_campaign_refill_state` for the selected `campaignId` or `tableId`.
+   This must be the next target-specific research primitive.
+4. Classify the target from refill state:
+   - regular campaign: campaign-backed workflow table with normal source,
+     sequence, senders, and send/refill stages.
+   - evergreen campaign: managed always-on lane with current source evidence.
+   - `unsupported_campaign_type`: internal direct campaign table; report the
+     blocker and stop without mutation.
+
+## Research Checklist
+
+Use the refill-state response as the current facts receipt:
+
+- campaign status/current step, workflow table id, table config type, and public
+  type;
+- 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;
+- sender ids, healthy senders, disconnected senders, and daily capacity;
+- row/stage counts: source available, rows, enriched, passed, generated,
+  approved, ready to schedule, scheduled;
+- active message prep job;
+- scheduler-owned scheduled counts by date/action from cells with non-null
+  `scheduledFor`;
+- `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.
+
+## Regular Campaign Decision
+
+For regular campaign workspaces, rank regular campaigns from route and
+`get_campaign_refill_state` evidence. Choose the best existing refill target.
+Do not create side campaigns, warm-post-engager side campaigns, on-demand campaigns,
+or unrelated campaigns as the default answer to a fill request.
+
+When the best regular campaign is source-exhausted, recommend same-campaign source-ladder replenishment.
+Keep `selectedLeadListId` source identity distinct
+from the campaign `workflowTableId`.
+
+Source replenishment choices:
+
+- existing source list reuse: append/confirm the existing source list when it
+  has enough eligible rows;
+- CSV path: load CSV profiles/domains, then import into the same campaign/source
+  path;
+- Sales Nav path: use Sales Nav lookup/search, then import selected prospects;
+- Prospeo path: use account/person search as appropriate, then import selected
+  prospects;
+- Signal Discovery path: search/select posts or engagers, import selected
+  source prospects into the same campaign/source-list path, then confirm
+  readiness.
+
+Before any source mutation, show exact approval evidence: workspace id,
+campaign id, workflow table id, source/provider id, source-list id when known,
+import caps, target dates/caps, dedupe/DNC/provider exclusion expectations, and
+expected row side effects. Then reread `get_campaign_refill_state`; if
+`freshness.stateHash` or exact ids changed, stop and ask for a fresh approval.
+
+After source import, call `wait_for_lead_list_ready` and `confirm_lead_list`
+with the source-list id and campaign id. Imports append to the existing
+campaign/source path; they must not reset campaign state, sequence, sender
+assignment, current step, or watch state. If provider auth, rate limit, timeout,
+partial import, duplicate-only import, DNC-only result, CSV parse failure,
+readiness timeout, or `confirm_lead_list` failure occurs, stop before prep and
+report the blocker/retry path.
+
+## Prep, Approval, And Scheduler Proof
+
+Existing rows normally move through enrichment/prep/approval using
+`start_campaign_message_preparation` and
+`get_campaign_message_preparation_status`. Standalone Generate Message is not the normal refill action;
+it is only for a manual/user-authored message path
+that requires it.
+
+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.
+
+Before prep or approval mutation, reread `get_campaign_refill_state` and compare
+`freshness.stateHash`, campaign id, table id, workspace id, source id, and caps.
+If they changed, stop. A second concurrent refill run must see the first run's
+import/prep state on reread and avoid duplicate work.
+
+Scheduled success requires a post-action reread proving scheduler-owned cells
+with non-null `scheduledFor`. Prepared, approved, and ready-to-schedule rows are
+intermediate states; report them as awaiting scheduler unless scheduled cells
+are present.
+
+## Evergreen Campaign Discipline
+
+`fill_campaign_horizon` is a legacy evergreen-only lower-level primitive. Call it
+only after `resolve_campaign_fill_route` and `get_campaign_refill_state` prove an
+evergreen campaign target.
+
+For evergreen campaigns, do not advance down the source ladder while the current source can produce enough good prospects.
+The current source is exhausted, or
+unable to produce enough good prospects, only when evidence includes source id,
+target prospect gap, cursor/inventory state, dedupe/DNC/provider exclusions,
+good-prospect yield, and scan/import caps. If that proof is missing, continue
+the current source or ask for more research instead of walking the ladder.
+
+## Hard Safety Rules
+
+- Never call start or launch tools.
+- Never raw-write `scheduledFor`, `scheduledAt`, scheduled status, or sender
+  assignment fields.
+- Never expose internal direct campaign types as an operator refill path.
+- Never claim scheduled success without rereading scheduler-owned cells with
+  non-null `scheduledFor`.
+- No mutation in production unless Christian explicitly approves exact
+  workspace, campaign/table ids, source/action ids, caps/dates, approval mode,
+  expected side effects, and rollback/stop condition.
+
+## Report
+
+Report the selected target, target type, source state, blockers, exact next
+primitive, approval required, and the freshness hash used. Say explicitly that
+nothing was launched and nothing was sent.