@sellable/install 0.1.259 → 0.1.261

package/bin/sellable-install.mjs

@@ -1944,7 +1944,8 @@ ${allowedToolsYaml(REFILL_SENDS_ALLOWED_TOOLS)}
 
 Use this as the customer-facing entrypoint for the Sellable \`refill-sends\`
 workflow. It supports \`--yolo\` and optional repeated \`--sender <name-or-id>\`
-selectors.
+selectors. It also supports \`--until YYYY-MM-DD\` to fill through a specific
+sender-local date instead of the default two send-day horizon.
 
 ## Bootstrap
 
@@ -1960,7 +1961,7 @@ Desktop, then start a new thread.
 ## Execute Workflow
 
 1. Call \`mcp__sellable__get_auth_status({})\`.
-2. Normalize invocation arguments with \`mcp__sellable__refill_sends({ yolo, senders, senderIds, senderNames })\` when the host exposes typed MCP tools.
+2. Normalize invocation arguments with \`mcp__sellable__refill_sends({ yolo, senders, senderIds, senderNames, untilDate })\` when the host exposes typed MCP tools.
 3. Load the canonical prompt via
    \`mcp__sellable__get_subskill_prompt({ subskillName: "refill-sends" })\`,
    then load \`mcp__sellable__get_subskill_prompt({ subskillName: "refill-sends-workflow" })\`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.259",
+  "version": "0.1.261",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/refill-sends.md

@@ -66,14 +66,18 @@ Accepted invocation flags in the same user request:
   fresh state reread.
 - `--sender <name-or-id>`: scope to a specific sender; repeat for multiple
   senders.
+- `--until <YYYY-MM-DD>`: fill through that sender-local date, inclusive,
+  instead of the default two send-day horizon.
 - `senderIds: <id>, <id>` or `senderNames: <name>, <name>`: explicit selector
   alternatives when the host preserves natural-language arguments better than
   shell-style flags.
+- `untilDate: YYYY-MM-DD`: explicit date selector alternative when the host
+  preserves natural-language arguments better than shell-style flags.
 
 When the host can call typed MCP tools, start with:
 
 ```text
-refill_sends({ yolo?: boolean, senders?: string[], senderIds?: string[], senderNames?: string[], horizonSendDays?: number })
+refill_sends({ yolo?: boolean, senders?: string[], senderIds?: string[], senderNames?: string[], horizonSendDays?: number, untilDate?: "YYYY-MM-DD" })
 ```
 
 That command helper only normalizes arguments and returns the execution
@@ -132,13 +136,16 @@ reassignment, or campaigns outside those selected for the eligible sender set.
 Stop and re-plan if the route, sender set, ids, caps, blockers, or side-effect
 class drift before mutation.
 
-In `--yolo`, the default two-day fill horizon is two send days. For each target
-sender, compute the bounded gap from that sender's healthy daily capacity,
-existing future scheduler-owned scheduled sends, and rows already ready to
-schedule across active campaigns enrolled with that sender. Then pick the best
-same-sender campaign to fill the 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. If a
+In `--yolo`, the default two-day fill horizon is two send days unless
+`--until`/`untilDate` is provided. If an until date is provided, compute bounded
+gaps through that sender-local date inclusive, skipping no-send days and never
+extending beyond that date without a new packet. For each target sender, compute
+the bounded gap from that sender's healthy daily capacity, existing future
+scheduler-owned scheduled sends, and rows already ready to schedule across
+active campaigns enrolled with that sender. Then pick the best same-sender
+campaign to fill the 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. If a
 same-source copy hits the campaign-table row cap, split the current source into
 a bounded LinkedIn profile source list, confirm only that smaller list into the
 same campaign, and operate on the copied review batch. Do not fall back to