@sellable/mcp 0.1.535 → 0.1.536

package/dist/tools/refill-target-plan.js

@@ -1026,6 +1026,16 @@ function sanitizeRefillTargetPlanResult(result) {
         mcpSanitizedRefillLanes: true,
     };
 }
+function stripInternalTargetDateKeys(value) {
+    if (Array.isArray(value)) {
+        return value.map((item) => stripInternalTargetDateKeys(item));
+    }
+    if (!isRecord(value))
+        return value;
+    return Object.fromEntries(Object.entries(value)
+        .filter(([key]) => key !== "targetDateKey")
+        .map(([key, nested]) => [key, stripInternalTargetDateKeys(nested)]));
+}
 export const refillTargetPlanToolDefinitions = [
     {
         name: "get_refill_target_plan",
@@ -1042,7 +1052,7 @@ export const refillTargetPlanToolDefinitions = [
                     type: "number",
                     minimum: 1,
                     maximum: 7,
-                    description: "Compatibility override for explicit sender-local send-day horizon planning. Omit for the default scheduler-forward 48-hour target window; no-send days contribute zero target.",
+                    description: "Compatibility override for explicit next N sender-local send days. Omit for the default scheduler-forward 48-hour target window; no-send days are skipped while choosing the requested send days.",
                 },
                 untilDate: {
                     type: "string",
@@ -1052,7 +1062,7 @@ export const refillTargetPlanToolDefinitions = [
                 targetDate: {
                     type: "string",
                     pattern: "^\\d{4}-\\d{2}-\\d{2}$",
-                    description: "Optional exact sender-local YYYY-MM-DD date to fill. Distinct from untilDate: targetDate asks how many scheduler-fillable slots exist on only this date.",
+                    description: "Optional one exact sender-local date (YYYY-MM-DD) to fill. Distinct from untilDate: targetDate asks how many scheduler-fillable slots exist on only this date.",
                 },
                 campaignId: {
                     type: "string",
@@ -1102,11 +1112,14 @@ export const refillTargetPlanToolDefinitions = [
 ];
 export async function getRefillTargetPlan(input = {}) {
     const workspaceId = normalizeExplicitWorkspaceId(input.workspaceId);
+    const targetDate = input.targetDate;
+    const untilDate = targetDate ? undefined : input.untilDate;
+    const horizonSendDays = targetDate || untilDate ? undefined : input.horizonSendDays;
     const result = await postRefillTargetPlan({
         intent: input.intent,
-        horizonSendDays: input.horizonSendDays,
-        untilDate: input.untilDate,
-        targetDate: input.targetDate,
+        horizonSendDays,
+        untilDate,
+        targetDate,
         campaignId: input.campaignId,
         tableId: input.tableId,
         senderIds: input.senderIds,
@@ -1117,7 +1130,7 @@ export async function getRefillTargetPlan(input = {}) {
         paidInmailCreditsMaxStalenessSeconds: MCP_PAID_INMAIL_CREDITS_MAX_STALENESS_SECONDS,
         ...(workspaceId ? { workspaceId } : {}),
     }, workspaceId ?? undefined);
-    const sanitized = sanitizeRefillTargetPlanResult(result);
+    const sanitized = stripInternalTargetDateKeys(sanitizeRefillTargetPlanResult(result));
     if (!workspaceId || !isRecord(sanitized))
         return sanitized;
     return {

package/dist/tools/registry.d.ts

@@ -2758,6 +2758,22 @@ export declare const allTools: ({
                 enum: string[];
                 description: string;
             };
+            targetDate: {
+                type: string;
+                pattern: string;
+                description: string;
+            };
+            untilDate: {
+                type: string;
+                pattern: string;
+                description: string;
+            };
+            horizonSendDays: {
+                type: string;
+                minimum: number;
+                maximum: number;
+                description: string;
+            };
             journal: {
                 type: string;
                 description: string;
@@ -7370,6 +7386,29 @@ export declare const allTools: ({
         };
         required: string[];
     };
+} | {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            workspaceId: {
+                type: string;
+                description: string;
+            };
+            action: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            targetDate: {
+                type: string;
+                description: string;
+            };
+        };
+        required: string[];
+        additionalProperties: boolean;
+    };
 } | {
     name: string;
     description: string;
@@ -7407,6 +7446,22 @@ export declare const allTools: ({
                 type: string;
                 enum: string[];
             };
+            targetDate: {
+                type: string;
+                pattern: string;
+                description: string;
+            };
+            untilDate: {
+                type: string;
+                pattern: string;
+                description: string;
+            };
+            horizonSendDays: {
+                type: string;
+                minimum: number;
+                maximum: number;
+                description: string;
+            };
         };
         required: string[];
         additionalProperties: boolean;

package/dist/tools/registry.js

@@ -40,6 +40,7 @@ import { refillTargetPlanToolDefinitions } from "./refill-target-plan.js";
 import { rowToolDefinitions } from "./rows.js";
 import { rubricToolDefinitions } from "./rubrics.js";
 import { schedulerFillCapacityToolDefinitions } from "./scheduler-fill-capacity.js";
+import { schedulerRunToolDefinitions } from "./scheduler-run.js";
 import { senderRoutingToolDefinitions } from "./sender-routing.js";
 import { senderToolDefinitions } from "./senders.js";
 import { sequencerToolDefinitions } from "./sequencer.js";
@@ -57,6 +58,7 @@ export const allTools = [
     ...refillPlanV2ToolDefinitions,
     ...refillTargetPlanToolDefinitions,
     ...schedulerFillCapacityToolDefinitions,
+    ...schedulerRunToolDefinitions,
     ...refillSendsToolDefinitions,
     ...refillSendsV2ToolDefinitions,
     ...setupEvergreenCampaignsToolDefinitions,

package/dist/tools/scheduler-fill-capacity.js

@@ -10,7 +10,7 @@ async function postSchedulerFillCapacity(body, workspaceId) {
 export const schedulerFillCapacityToolDefinitions = [
     {
         name: "get_scheduler_fill_capacity",
-        description: "read-only scheduler capacity query for refill-sends before any refill mutation. It asks the product scheduler model how many additional cells the scheduler will try to place for exact sender/action requests, using the default scheduler-forward horizon or one exact targetDate. It returns scheduler-fillable slots, occupied scheduled/processing slots, sender sendability gates, cooldowns, Sales Navigator status for paid InMail, cached paid-InMail credit feasibility, threshold source, blockers, warnings, and explicit sideEffects false. This tool does not create rows, import leads, prepare messages, approve messages, does not schedule sends, does not refresh paid InMail credits, mutate thresholds, start campaigns, launch, or send. Use exact senderId values only; never pass sender names.",
+        description: "read-only scheduler capacity query for refill-sends before any refill mutation. It asks the product scheduler model how many additional cells the scheduler will try to place for exact sender/action requests, using the default scheduler-forward horizon or one exact targetDate. Use get_refill_target_plan for multi-day untilDate or horizonSendDays planning. It returns scheduler-fillable slots, occupied scheduled/processing slots, sender sendability gates, cooldowns, Sales Navigator status for paid InMail, cached paid-InMail credit feasibility, threshold source, blockers, warnings, and explicit sideEffects false. This tool does not create rows, import leads, prepare messages, approve messages, does not schedule sends, does not refresh paid InMail credits, mutate thresholds, start campaigns, launch, or send. Use exact senderId values only; never pass sender names.",
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/scheduler-run.d.ts

@@ -0,0 +1,32 @@
+type SchedulerRunAction = "run" | "status";
+type RunSchedulerSweepInput = {
+    workspaceId: string;
+    action?: SchedulerRunAction;
+    targetDate?: string | null;
+};
+export declare const schedulerRunToolDefinitions: {
+    name: string;
+    description: string;
+    inputSchema: {
+        type: string;
+        properties: {
+            workspaceId: {
+                type: string;
+                description: string;
+            };
+            action: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            targetDate: {
+                type: string;
+                description: string;
+            };
+        };
+        required: string[];
+        additionalProperties: boolean;
+    };
+}[];
+export declare function runSchedulerSweep(input: RunSchedulerSweepInput): Promise<unknown>;
+export {};

package/dist/tools/scheduler-run.js

@@ -0,0 +1,68 @@
+import { getApi } from "../api.js";
+import { normalizeExplicitWorkspaceId, workspaceRequestOptions, } from "./workspace-context.js";
+async function postSchedulerRun(body, workspaceId) {
+    const api = getApi();
+    const requestOptions = workspaceRequestOptions(workspaceId);
+    return requestOptions
+        ? api.post("/api/v3/mcp/scheduler-run", body, requestOptions)
+        : api.post("/api/v3/mcp/scheduler-run", body);
+}
+export const schedulerRunToolDefinitions = [
+    {
+        name: "run_scheduler_sweep",
+        description: 'Trigger the product scheduler placement sweep for one explicit workspace now, or read the last on-demand scheduler run status with action "status". By default a run is workspace-wide, not a scoped run for one campaign/table. Pass targetDate to scope placement to one exact sender-local date while still remaining workspace-wide inside that date. Multi-day untilDate or horizonSendDays planning should come from get_refill_target_plan, then use exact per-date run_scheduler_sweep calls only for dates that still need scheduler placement. The synchronous envelope includes status ran, attached, backoff, window_closed_noop, or failed; retryAfterMs for matching-scope backoff replays; and a backward-compatible receipt with public scope metadata. In v2 receipts, readyCellsFound is total scheduler-ready supply found before filters, cellsConsidered is the allocation-attempt count that survived prefilters, prefiltered means ready cells removed before allocation such as no capacity, stale paid InMail credit facts, or sender mismatch, skipped means considered cells rejected by hard scheduler gates, and deferred means considered cells waiting on windows/capacity/cooldown. campaignScopeSummary lists bounded tables/campaigns the workspace-wide run inspected; absence there is not a scoped-run guarantee that the target was ready. The receipt can include readyCellsByType, consideredCellsByType, prefilterReasons, skippedReasons, deferredReasons, summary, and nextAction. It places cells within existing scheduler gates only: it can move placement earlier, but it cannot bypass sending windows, daily limits, cooldowns, sender gates, billing, or credit thresholds, and it never sends messages directly. Repeated calls inside the backoff window replay the last receipt only when the recorded public scope matches this request. Status is read-only and scoped to the last on-demand run only; cron sweeps are not recorded here.',
+        inputSchema: {
+            type: "object",
+            properties: {
+                workspaceId: {
+                    type: "string",
+                    description: "Explicit request-scoped workspace id for scheduled/yolo refill automation. Pass this instead of switching the shared active workspace.",
+                },
+                action: {
+                    type: "string",
+                    enum: ["run", "status"],
+                    description: 'Use "run" to trigger a placement sweep now. Use "status" for a read-only view of the last on-demand run. Defaults to "run".',
+                },
+                targetDate: {
+                    type: "string",
+                    description: "Optional one exact sender-local date (YYYY-MM-DD) to scope scheduler placement/status. The run remains workspace-wide inside that date.",
+                },
+            },
+            required: ["workspaceId"],
+            additionalProperties: false,
+        },
+    },
+];
+function isValidDateKey(value) {
+    if (!/^\d{4}-\d{2}-\d{2}$/.test(value))
+        return false;
+    const [year, month, day] = value.split("-").map(Number);
+    const date = new Date(Date.UTC(year, month - 1, day));
+    return (date.getUTCFullYear() === year &&
+        date.getUTCMonth() === month - 1 &&
+        date.getUTCDate() === day);
+}
+function normalizeTargetDate(value) {
+    if (value === undefined)
+        return undefined;
+    if (typeof value !== "string" || !isValidDateKey(value)) {
+        throw new Error("targetDate must be a valid YYYY-MM-DD calendar date.");
+    }
+    return value;
+}
+export async function runSchedulerSweep(input) {
+    const workspaceId = normalizeExplicitWorkspaceId(input.workspaceId);
+    if (!workspaceId) {
+        throw new Error("workspaceId is required for run_scheduler_sweep.");
+    }
+    const action = input.action ?? "run";
+    if (action !== "run" && action !== "status") {
+        throw new Error('action must be "run" or "status" for run_scheduler_sweep.');
+    }
+    const targetDate = normalizeTargetDate(input.targetDate);
+    return postSchedulerRun({
+        workspaceId,
+        action,
+        targetDate,
+    }, workspaceId);
+}

package/dist/tools/senders.d.ts

@@ -52,22 +52,16 @@ export type PaidInmailCreditStatus = {
 };
 export type RefreshPaidInmailCreditsResponse = {
     senderId: string;
-    refreshed: boolean;
-    error?: string | null;
+    refreshed: true;
     credits: PaidInmailCreditStatus;
-    receipt?: {
-        status?: string;
-        refreshed?: boolean;
-        error?: string;
-        [key: string]: unknown;
-    } | null;
+    receipt?: unknown;
     sideEffects: {
-        refreshedLinkedInDerivedCreditFacts: boolean;
-        updatedSenderCreditCache: boolean;
-        campaignMutation: boolean;
-        schedulerMutation: boolean;
-        thresholdMutation: boolean;
-        sendMutation: boolean;
+        refreshedLinkedInDerivedCreditFacts: true;
+        updatedSenderCreditCache: true;
+        campaignMutation: false;
+        schedulerMutation: false;
+        thresholdMutation: false;
+        sendMutation: false;
     };
 };
 export declare const senderToolDefinitions: ({

package/dist/tools/senders.js

@@ -237,21 +237,6 @@ function normalizeCreditStatus(raw) {
         needsRefresh: raw?.needsRefresh === true,
     };
 }
-function normalizeRefreshReceipt(raw) {
-    if (!raw || typeof raw !== "object")
-        return null;
-    return raw;
-}
-function normalizeCreditRefreshSideEffects(raw, receiptRefreshed) {
-    return {
-        refreshedLinkedInDerivedCreditFacts: raw?.refreshedLinkedInDerivedCreditFacts === true || receiptRefreshed,
-        updatedSenderCreditCache: raw?.updatedSenderCreditCache === true || receiptRefreshed,
-        campaignMutation: raw?.campaignMutation === true,
-        schedulerMutation: raw?.schedulerMutation === true,
-        thresholdMutation: raw?.thresholdMutation === true,
-        sendMutation: raw?.sendMutation === true,
-    };
-}
 export async function refreshPaidInmailCredits(input) {
     const senderId = input.senderId?.trim();
     if (!senderId) {
@@ -283,14 +268,18 @@ export async function refreshPaidInmailCredits(input) {
     if (threshold !== null)
         body.threshold = threshold;
     const result = await api.post(`/api/v3/mcp/senders/${encodeURIComponent(senderId)}/refresh-inmail-credits`, body, requestOptions);
-    const receipt = normalizeRefreshReceipt(result?.receipt);
-    const receiptRefreshed = result?.refreshed === true || receipt?.refreshed === true;
     return {
         senderId,
-        refreshed: receiptRefreshed,
-        error: pickString(result?.error, receipt?.error),
+        refreshed: true,
         credits: normalizeCreditStatus(result?.credits),
-        receipt,
-        sideEffects: normalizeCreditRefreshSideEffects(result?.sideEffects, receiptRefreshed),
+        receipt: result?.receipt,
+        sideEffects: {
+            refreshedLinkedInDerivedCreditFacts: true,
+            updatedSenderCreditCache: true,
+            campaignMutation: false,
+            schedulerMutation: false,
+            thresholdMutation: false,
+            sendMutation: false,
+        },
     };
 }

package/package.json

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

package/skills/refill-sends/SKILL.md

@@ -6,6 +6,7 @@ allowed-tools:
   - mcp__sellable__refill_sends
   - mcp__sellable__get_refill_target_plan
   - mcp__sellable__get_scheduler_fill_capacity
+  - mcp__sellable__run_scheduler_sweep
   - mcp__sellable__refresh_paid_inmail_credits
   - mcp__sellable__get_subskill_asset
   - mcp__sellable__get_auth_status
@@ -86,6 +87,12 @@ Accepted invocation flags in the same user request:
   preserves natural-language arguments better than shell-style flags.
 - `targetDate: YYYY-MM-DD`: exact-date selector alternative when the host
   preserves natural-language arguments better than shell-style flags.
+- `horizonSendDays: N`: compatibility selector for the next N sender-local send
+  days when no exact or through-date selector is present.
+
+Date selector precedence is `targetDate > untilDate > horizonSendDays`. Use
+`targetDate` for one exact sender-local date, `untilDate` for an inclusive
+through-date, and `horizonSendDays` for the next N sender-local send days.
 
 When the host can call typed MCP tools, start with:
 
@@ -114,10 +121,11 @@ or install-time workspace mapping. Pass `workspaceId` on every scheduled or
 `--yolo` refill tool call, including setup/read calls such as
 `refill_sends`, `get_refill_target_plan`, `list_senders`,
 `get_sender_routing`, `resolve_campaign_fill_route`,
-`get_campaign_refill_state`, `get_scheduler_fill_capacity`, and any later
-refill mutation covered by the packet. Missing `workspaceId` in scheduled or
-`--yolo` mode is a blocker; stop with `WORKSPACE_REQUIRED` instead of running
-against an implicit or guessed workspace.
+`get_campaign_refill_state`, `get_scheduler_fill_capacity`,
+`run_scheduler_sweep`, and any later refill mutation covered by the packet.
+Missing `workspaceId` in scheduled or `--yolo` mode is a blocker; stop with
+`WORKSPACE_REQUIRED` instead of running against an implicit or guessed
+workspace.
 
 Do not solve scheduled or `--yolo` workspace uncertainty by changing the shared
 active workspace. Manual interactive workspace switching remains a separate
@@ -269,6 +277,25 @@ need raw proof, call the read-only `get_scheduler_fill_capacity` query for the
 same sender/action/date; it tells the MCP how many cells the product scheduler
 will try to place and does not import, approve, schedule, refresh credits, or
 mutate.
+When the refill loop has ready rows and needs scheduler pickup now, use
+`run_scheduler_sweep({ workspaceId, targetDate })` for exact-date requests. For
+`untilDate` or `horizonSendDays` requests, sweep each planner-selected
+`targetDate` with the same explicit `workspaceId`. The sweep can place cells
+within existing scheduler gates and returns the receipt, but it never sends or
+bypasses limits.
+Scheduler-run receipt interpretation: `cellsConsidered is allocation-attempt
+count`, not total ready supply, while `readyCellsFound` is ready inventory found
+before prefilters. Inspect `campaignScopeSummary` before assuming the selected
+refill campaign/table was included; if absent, do not infer that target was
+ready-but-blocked. Interpret `prefiltered` as ready cells removed before
+allocation, `skipped` as considered cells blocked by scheduler gates, and
+`deferred` as considered cells waiting on windows/capacity/cooldown. For ready
+closed-InMail cells with stale paid-credit prefilter/defer reasons, refresh
+paid-InMail credits once through existing tools, then rerun `run_scheduler_sweep`
+or read `action:"status"`; `refresh_paid_inmail_credits_then_rerun` is that
+path. `wait_for_capacity_or_window` means report loaded/capped/waiting and do
+not source or prep more rows; `no_ready_cells_continue_refill_prep` means return
+to the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
 If the target plan is complete by projected coverage, report that the selected
 target is already filled and no-op without asking for approval. If the ready
 buffer covers the projected gap, paid InMail credit facts are fresh for every

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

@@ -37,16 +37,21 @@ active workspace readback. Scheduled or autonomous usage must carry
 `workspaceId` on every tool call. If the workspace is missing or ambiguous, stop
 with `WORKSPACE_REQUIRED`; do not switch the shared active workspace.
 
+Date selectors are sender-local and mutually exclusive by precedence:
+`targetDate > untilDate > horizonSendDays`. Use `targetDate` for one exact sender-local date, `untilDate` for an inclusive through-date, and `horizonSendDays` for the next N sender-local send days. If none is provided, the planner uses the default scheduler-forward 48-hour behavior.
+
 For a real refill run:
 
 ```text
-refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode? })
+refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode?, targetDate?, untilDate?, horizonSendDays? })
+refill_sends_v2({ workspaceId, targetDate:"2026-07-07" })
+refill_sends_v2({ workspaceId, untilDate:"2026-07-09" })
 ```
 
 For read-only inspection:
 
 ```text
-refill_sends_v2({ workspaceId, dryRun:true, intent:"auto", senderIds? })
+refill_sends_v2({ workspaceId, dryRun:true, intent:"auto", senderIds?, targetDate?, untilDate?, horizonSendDays? })
 ```
 
 To resume an in-progress run, pass the handle back exactly:
@@ -55,6 +60,11 @@ To resume an in-progress run, pass the handle back exactly:
 refill_sends_v2({ workspaceId, runId, fence })
 ```
 
+The original run's date window is stored in the run record. On resume, the
+stored window is reused and conflicting resume input is blocked; do not add,
+change, or remove `targetDate`, `untilDate`, or `horizonSendDays` while passing
+an existing `{ runId, fence }`.
+
 If a stale handle loses the lease, the tool reports the holder status and the
 approximately 10 minute lockout window. Reinvoke with the current handle or wait
 for lease expiry; never guess a fence.
@@ -125,9 +135,23 @@ host guard, heartbeats the run lease, and may return:
 ```
 
 Reinvoke with that handle. The approximately five minute scheduler budget is at
-the run level, not one tool call. A window-closed or loaded-awaiting scheduler
-report must include remaining-ready count, exact expected pickup time, and the
-resume handle; never treat bare "awaiting scheduler" copy as a final answer.
+the run level, not one tool call. Exact-date runs request pickup with
+`run_scheduler_sweep({ workspaceId, targetDate })`; `untilDate` and
+`horizonSendDays` runs sweep each planner-selected exact target date. A
+window-closed or loaded-awaiting scheduler report must include remaining-ready
+count, exact expected pickup time, and the resume handle; never treat bare
+"awaiting scheduler" copy as a final answer.
+Scheduler-run receipt interpretation still applies to terminal progress:
+`cellsConsidered is allocation-attempt count`, not total ready supply, while
+`readyCellsFound` is ready inventory found before prefilters. Inspect
+`campaignScopeSummary` before assuming the selected refill campaign/table was
+included; if absent, do not infer that target was ready-but-blocked. Interpret
+`prefiltered`, `skipped`, and `deferred` separately. For ready closed-InMail
+cells with stale paid-credit reasons, route to
+`refresh_paid_inmail_credits_then_rerun` once, then rerun/status.
+`wait_for_capacity_or_window` means report loaded/capped/waiting and do not
+source or prep more rows; `no_ready_cells_continue_refill_prep` means return to
+the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
 
 After the first prep batch, read the conversion-verdict journal line. It is
 rendered from packet facts: `supplyCensus`, `censusReason`, and

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

@@ -33,10 +33,16 @@ local files or memory.
 Resolve request-scoped `workspaceId` using read-only auth and workspace tools.
 Scheduled or autonomous runs must not rely on implicit workspace state.
 
+Carry the request date selector through bootstrap, planning, execution, and
+resume. Date selector precedence is `targetDate > untilDate > horizonSendDays`:
+`targetDate` is one exact sender-local date, `untilDate` is an inclusive
+through-date, and `horizonSendDays` is the next N sender-local send days. If no
+selector is present, use the default scheduler-forward 48-hour behavior.
+
 Start or resume the execution loop:
 
 ```text
-refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode?, runId?, fence? })
+refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode?, targetDate?, untilDate?, horizonSendDays?, runId?, fence? })
 ```
 
 Use `dryRun:true` only when the user asked for read-only inspection. A dry run
@@ -44,6 +50,11 @@ writes a journal only. A real run creates or resumes a run record, refreshes
 paid-credit trust only when packet facts require it, and returns a resume handle
 when the current invocation must pause.
 
+The run record stores the selected date window. On resume, reuse that stored
+window and block conflicting resume input; do not accept a changed
+`targetDate`, `untilDate`, or `horizonSendDays` with an existing `{ runId,
+fence }`.
+
 ## G1 Plan
 
 The loop reads `get_refill_plan_v2` with runState fed back from the run record.
@@ -116,7 +127,21 @@ outcome, then verifies before replanning.
 Scheduler wait is cross-invocation. If the tool returns `in_progress` with
 sweep guidance, re-invoke `refill_sends_v2` with `{runId, fence}`. The scheduler
 budget is cumulative at the run level. Zero pickup after a confirmed sweep is
-debugged from `pipelineDiagnosis`; it is not waited out forever.
+debugged from `pipelineDiagnosis`; it is not waited out forever. Exact-date
+runs request pickup with `run_scheduler_sweep({ workspaceId, targetDate })`;
+`untilDate` and `horizonSendDays` runs sweep each planner-selected exact target
+date.
+Scheduler-run receipt interpretation still applies to terminal progress:
+`cellsConsidered is allocation-attempt count`, not total ready supply, while
+`readyCellsFound` is ready inventory found before prefilters. Inspect
+`campaignScopeSummary` before assuming the selected refill campaign/table was
+included; if absent, do not infer that target was ready-but-blocked. Interpret
+`prefiltered`, `skipped`, and `deferred` separately. For ready closed-InMail
+cells with stale paid-credit reasons, route to
+`refresh_paid_inmail_credits_then_rerun` once, then rerun/status.
+`wait_for_capacity_or_window` means report loaded/capped/waiting and do not
+source or prep more rows; `no_ready_cells_continue_refill_prep` means return to
+the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
 
 ## G4 Report
 

package/skills/refill-sends-v2-workflow/core/flow.v1.json

@@ -1,7 +1,7 @@
 {
   "version": "v1.0",
   "workflow": "refill-sends-v2-workflow",
-  "principle": "Execute refill sends v2 through a fenced run record: bootstrap, plan, execute, verify, and report. Dry runs stay read-only; real runs execute only packet-named bounded work.",
+  "principle": "Execute refill sends v2 through a fenced run record: bootstrap, plan, execute, verify, and report. Dry runs stay read-only; real runs execute only packet-named bounded work. Date selectors use targetDate > untilDate > horizonSendDays precedence.",
   "laneSources": [
     "managed_waterfall",
     "dashboard_evergreen",
@@ -50,6 +50,9 @@
     "repair rungs come from the plan packet; the loop bounds and refuses, never self-emits repair actions",
     "capped_by_scheduler is complete, never poll",
     "awaiting scheduler is not an end state; window-closed reports name remaining-ready, expected pickup time, and resume handle",
+    "date selectors resolve by targetDate > untilDate > horizonSendDays; targetDate is one exact sender-local date, untilDate is an inclusive through-date, and horizonSendDays means next N sender-local send days",
+    "dateWindow is stored on the run record and conflicting resume input is blocked",
+    "exact-date scheduler pickup uses run_scheduler_sweep({ workspaceId, targetDate }); untilDate and horizonSendDays runs sweep each planner-selected exact targetDate",
     "honest-rubric-fail means a human updates the rubric or changes lead source",
     "source replenishment beyond same-source-automatic is a scoped create-campaign handoff, never refill-owned provider search",
     "no campaign creation, provider-family switch, threshold lowering, scheduler writes, sends, archives, deletes, or brief/filter/message/sequence/sender mutation without a separate approval packet"
@@ -143,7 +146,16 @@
         },
         {
           "tool": "refill_sends_v2",
-          "requiredFields": ["workspaceId"]
+          "requiredFields": ["workspaceId"],
+          "optionalFields": [
+            "senderIds",
+            "approvalMode",
+            "targetDate",
+            "untilDate",
+            "horizonSendDays",
+            "runId",
+            "fence"
+          ]
         },
         {
           "tool": "get_subskill_prompt",
@@ -176,6 +188,9 @@
           "optionalFields": [
             "intent",
             "senderIds",
+            "targetDate",
+            "untilDate",
+            "horizonSendDays",
             "runState",
             "journal",
             "journalNote"
@@ -311,7 +326,7 @@
     },
     {
       "id": "verify",
-      "description": "Verify whole-row outcomes before another plan read. Reattach to an own active prep job by requestSource/requestHash; never re-dispatch prep while a matching job is active. Foreign prep waits until clear or blocks foreign_prep_active. wait_for_active_work and wait_for_source_import reread the plan on bounded cadence. wait_for_scheduler is cross-invocation: each tool call polls briefly under the host guard, heartbeats the lease, and returns in_progress sweep guidance so the agent re-invokes refill_sends_v2 with {runId,fence}. The approximately five minute scheduler budget is cumulative at the run level.",
+      "description": "Verify whole-row outcomes before another plan read. Reattach to an own active prep job by requestSource/requestHash; never re-dispatch prep while a matching job is active. Foreign prep waits until clear or blocks foreign_prep_active. wait_for_active_work and wait_for_source_import reread the plan on bounded cadence. wait_for_scheduler is cross-invocation: each tool call polls briefly under the host guard, heartbeats the lease, and returns in_progress sweep guidance so the agent re-invokes refill_sends_v2 with {runId,fence}. Exact-date scheduler pickup uses run_scheduler_sweep({ workspaceId, targetDate }); untilDate and horizonSendDays runs sweep each planner-selected exact targetDate. The approximately five minute scheduler budget is cumulative at the run level.",
       "allowedTools": ["refill_sends_v2", "get_refill_plan_v2"],
       "onEnter": [
         {
@@ -322,6 +337,7 @@
       "hardRules": [
         "do not re-dispatch prep when an own active job exists; reattach and poll status",
         "capped_by_scheduler is complete",
+        "resume uses the stored dateWindow; conflicting resume input is blocked",
         "replan-driven repair: the planner names rerun_errored_cells, approve_messages, start_campaign, or source work; the loop bounds and refuses",
         "conversion verdict is journaled from packet facts after the first prep batch; the plan gate withholds a second unproven prep batch",
         "zero pickup after a confirmed sweep is debugged from pipelineDiagnosis, not waited out forever",

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

@@ -6,6 +6,7 @@ allowed-tools:
   - mcp__sellable__get_subskill_asset
   - mcp__sellable__get_refill_target_plan
   - mcp__sellable__get_scheduler_fill_capacity
+  - mcp__sellable__run_scheduler_sweep
   - mcp__sellable__refresh_paid_inmail_credits
   - mcp__sellable__list_senders
   - mcp__sellable__get_sender_routing
@@ -67,11 +68,12 @@ request-scoped `workspaceId`. Pass that same `workspaceId` on every refill tool
 call in this workflow: `get_refill_target_plan`, `list_senders`,
 `get_sender_routing`, `resolve_campaign_fill_route`,
 `get_campaign_refill_state`, `get_scheduler_fill_capacity`,
-`refresh_paid_inmail_credits`, source import/readiness calls, preparation calls,
-approval calls, and campaign start calls. Missing `workspaceId` in scheduled or
-`--yolo` mode is a blocker; return or report `WORKSPACE_REQUIRED` instead of
-falling back to shared config state. Manual interactive workspace switching is
-diagnostic setup only and is not an automation control path.
+`run_scheduler_sweep`, `refresh_paid_inmail_credits`, source import/readiness
+calls, preparation calls, approval calls, and campaign start calls. Missing
+`workspaceId` in scheduled or `--yolo` mode is a blocker; return or report
+`WORKSPACE_REQUIRED` instead of falling back to shared config state. Manual
+interactive workspace switching is diagnostic setup only and is not an
+automation control path.
 
 Goal-mode continuation: a skill cannot create or invoke `/goal` by itself. When
 this workflow is already running inside an active Codex goal, keep that goal
@@ -186,6 +188,26 @@ files or memory.
    how many cells the product scheduler will try to place for that sender; it
    does not create rows, import, approve, schedule, refresh paid-InMail credits,
    or mutate thresholds.
+   When ready rows exist and the wait is for scheduler pickup, call
+   `run_scheduler_sweep({ workspaceId, targetDate })` for exact-date requests
+   to request the product scheduler placement pass now and read its receipt. For
+   `untilDate` or `horizonSendDays` requests, sweep each planner-selected
+   `targetDate` with the same explicit `workspaceId`. This may place cells
+   within existing gates, never sends messages, and never bypasses limits.
+   Scheduler-run receipt interpretation: `cellsConsidered is
+   allocation-attempt count`, not total ready supply, while `readyCellsFound`
+   is ready inventory found before prefilters. Inspect `campaignScopeSummary`
+   before assuming the selected refill campaign/table was included; if absent,
+   do not infer that target was ready-but-blocked. Interpret `prefiltered` as
+   ready cells removed before allocation, `skipped` as considered cells blocked
+   by scheduler gates, and `deferred` as considered cells waiting on
+   windows/capacity/cooldown. For ready closed-InMail cells with stale
+   paid-credit prefilter/defer reasons, refresh paid-InMail credits once through
+   existing tools, then rerun `run_scheduler_sweep` or read `action:"status"`;
+   `refresh_paid_inmail_credits_then_rerun` is that path.
+   `wait_for_capacity_or_window` means report loaded/capped/waiting and do not
+   source or prep more rows; `no_ready_cells_continue_refill_prep` means return
+   to the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
    If `status:"complete"`, report the target, selected dates, sent count,
    scheduled count, projected count, campaign ids, and no-op proof without
    asking for approval or mutating.