@sellable/mcp 0.1.415 → 0.1.416

package/README.md

@@ -66,8 +66,9 @@ reader value, validates proof/AI tells, and saves content artifacts under
 
 The refill-sends public command wrapper plans and executes approval-gated send
 refills. It supports `--yolo` and optional sender selectors such as
-`--sender "Christian Reyes"` or typed MCP calls to `refill_sends({ yolo,
-senders })` from:
+`--sender "Christian Reyes"`, optional through-date selectors such as
+`--until 2026-06-30`, or typed MCP calls to `refill_sends({ yolo, senders,
+untilDate })` from:
 
 - `mcp/sellable/skills/refill-sends/SKILL.md`
 
@@ -296,6 +297,7 @@ Use the refill command for sender send refills:
 
 ```
 /sellable:refill-sends --yolo
+/sellable:refill-sends --yolo --until 2026-06-30
 /sellable:refill-sends --sender "Christian Reyes" --sender "Thomas Nobbs"
 ```
 
@@ -323,6 +325,7 @@ Use the Codex refill command with the same flags:
 
 ```
 $sellable:refill-sends --yolo
+$sellable:refill-sends --yolo --until 2026-06-30
 $sellable:refill-sends --sender "Christian Reyes" --sender "Thomas Nobbs"
 ```
 

package/dist/tools/refill-sends.d.ts

@@ -6,6 +6,7 @@ type RefillSendsCommandInput = {
     senderIds?: string[];
     senderNames?: string[];
     horizonSendDays?: number;
+    untilDate?: string;
     campaignId?: string;
     tableId?: string;
     intent?: RefillSendsIntent;
@@ -48,6 +49,11 @@ export declare const refillSendsToolDefinitions: {
                 maximum: number;
                 description: string;
             };
+            untilDate: {
+                type: string;
+                pattern: string;
+                description: string;
+            };
             campaignId: {
                 type: string;
                 description: string;
@@ -78,7 +84,19 @@ export declare function refillSendsCommand(input?: RefillSendsCommandInput): {
     workflowPromptName: string;
     yolo: boolean;
     intent: RefillSendsIntent;
-    horizonSendDays: number;
+    untilDate: string | null;
+    horizonSendDays: number | null;
+    fillWindow: {
+        mode: string;
+        untilDate: string;
+        description: string;
+        horizonSendDays?: undefined;
+    } | {
+        mode: string;
+        horizonSendDays: number | null;
+        description: string;
+        untilDate?: undefined;
+    };
     approvalMode: RefillSendsApprovalMode;
     campaignId: string | null;
     tableId: string | null;
@@ -101,7 +119,8 @@ export declare function refillSendsCommand(input?: RefillSendsCommandInput): {
                 senders: string[];
                 senderIds: string[];
                 senderNames: string[];
-                horizonSendDays: number;
+                untilDate: string | null;
+                horizonSendDays: number | null;
                 campaignId: string | undefined;
                 tableId: string | undefined;
                 intent: RefillSendsIntent;

package/dist/tools/refill-sends.js

@@ -14,6 +14,25 @@ function normalizeHorizonSendDays(value) {
     }
     return Math.max(1, Math.min(7, Math.floor(value)));
 }
+function normalizeUntilDate(value) {
+    if (value === undefined || value === null || value === "")
+        return null;
+    if (typeof value !== "string") {
+        throw new Error("untilDate must be a string in YYYY-MM-DD format.");
+    }
+    const trimmed = value.trim();
+    if (!/^\d{4}-\d{2}-\d{2}$/.test(trimmed)) {
+        throw new Error("untilDate must use YYYY-MM-DD format.");
+    }
+    const [year, month, day] = trimmed.split("-").map((part) => Number(part));
+    const parsed = new Date(Date.UTC(year, month - 1, day));
+    if (parsed.getUTCFullYear() !== year ||
+        parsed.getUTCMonth() !== month - 1 ||
+        parsed.getUTCDate() !== day) {
+        throw new Error("untilDate must be a valid calendar date.");
+    }
+    return trimmed;
+}
 export const refillSendsToolDefinitions = [
     {
         name: "refill_sends",
@@ -44,7 +63,12 @@ export const refillSendsToolDefinitions = [
                     type: "number",
                     minimum: 1,
                     maximum: 7,
-                    description: "Number of sender-local send days to fill. Defaults to 2.",
+                    description: "Number of sender-local send days to fill. Defaults to 2 when untilDate is not provided.",
+                },
+                untilDate: {
+                    type: "string",
+                    pattern: "^\\d{4}-\\d{2}-\\d{2}$",
+                    description: "Optional sender-local YYYY-MM-DD date to fill through, inclusive. Overrides the default two send-day horizon.",
                 },
                 campaignId: {
                     type: "string",
@@ -76,7 +100,10 @@ export function refillSendsCommand(input = {}) {
     const senderNames = normalizeStrings(input.senderNames);
     const hasSenderSelectors = senders.length > 0 || senderIds.length > 0 || senderNames.length > 0;
     const yolo = input.yolo === true;
-    const horizonSendDays = normalizeHorizonSendDays(input.horizonSendDays);
+    const untilDate = normalizeUntilDate(input.untilDate);
+    const horizonSendDays = untilDate
+        ? null
+        : normalizeHorizonSendDays(input.horizonSendDays);
     const intent = input.intent ?? "plain";
     const approvalMode = input.approvalMode ?? (yolo ? "approve" : "mark_ready");
     const senderScope = hasSenderSelectors
@@ -91,7 +118,19 @@ export function refillSendsCommand(input = {}) {
         workflowPromptName: "refill-sends-workflow",
         yolo,
         intent,
+        untilDate,
         horizonSendDays,
+        fillWindow: untilDate
+            ? {
+                mode: "until_date",
+                untilDate,
+                description: "Fill through this sender-local date inclusive, skipping no-send days and never extending beyond the date without a new packet.",
+            }
+            : {
+                mode: "horizon_send_days",
+                horizonSendDays,
+                description: "Fill the default bounded horizon by sender-local send days.",
+            },
         approvalMode,
         campaignId: input.campaignId ?? null,
         tableId: input.tableId ?? null,
@@ -105,6 +144,9 @@ export function refillSendsCommand(input = {}) {
             'Load get_subskill_prompt({ subskillName: "refill-sends-workflow" }) before any product operation.',
             `Resolve route with resolve_campaign_fill_route({ intent: "${intent}"${input.campaignId ? `, campaignId: "${input.campaignId}"` : ""}${input.tableId ? `, tableId: "${input.tableId}"` : ""} }).`,
             "Call list_senders and get_sender_routing, then resolve sender selectors against active enrolled campaign-backed sequence senders.",
+            untilDate
+                ? `Use fill window untilDate="${untilDate}" as the inclusive sender-local through date; do not extend beyond that date without a new approval packet.`
+                : `Use the default fill window of ${horizonSendDays} sender-local send days.`,
             "Read get_campaign_refill_state for enough exact candidate campaigns to pick the best per-sender target by recent/future scheduler-owned sends, then recent result evidence, then source health.",
             "Fresh reread get_campaign_refill_state immediately before any import, prep, approval, or horizon-fill mutation.",
         ],
@@ -125,10 +167,12 @@ export function refillSendsCommand(input = {}) {
         hostExamples: {
             claude: [
                 "/sellable:refill-sends --yolo",
+                "/sellable:refill-sends --yolo --until 2026-06-30",
                 '/sellable:refill-sends --sender "Christian Reyes" --sender "Thomas Nobbs"',
             ],
             codex: [
                 "$sellable:refill-sends --yolo",
+                "$sellable:refill-sends --yolo --until 2026-06-30",
                 '$sellable:refill-sends --sender "Christian Reyes" --sender "Thomas Nobbs"',
             ],
             mcpTool: {
@@ -138,6 +182,7 @@ export function refillSendsCommand(input = {}) {
                     senders,
                     senderIds,
                     senderNames,
+                    untilDate,
                     horizonSendDays,
                     campaignId: input.campaignId,
                     tableId: input.tableId,

package/package.json

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

package/skills/create-campaign-v2/references/ai-tells.md

@@ -55,12 +55,6 @@ raise your hand for X (creepy to reach out based on that, i know) - but
 this felt too on the nose to ignore"` shapes only when the source was an
 explicit lead-magnet comment, reply, or opt-in.
 
-Shared evergreen exception: for Shared Signal Discovery and other shared
-evergreen lanes, the weak-signal permissioned bridge above is still a tell.
-Reject `hope this is relevant`, `might be interested`, and `saw you in a few
-conversations` as openers; require a concrete signal/problem bridge or omit the
-source line.
-
 **Severity:** REJECT
 
 ## Tell #3 — Explicit date or duration references about the recipient

package/skills/create-campaign-v2/references/gold-standard-message-examples.md

@@ -203,32 +203,6 @@ Why it works:
 **Proof ranks used:** rank 1 (mechanism - 1,000+ conditions from one blood
 draw), rank 3 (risk before claims).
 
-Do not use the Superpower weak-signal hedge pattern for Shared Evergreen Signal Discovery. Shared evergreen lanes are reused across multiple senders and must not open with `hope this is relevant`, `might be interested`, or `saw you in a few conversations`. Use the safe pattern below instead.
-
-### Shared Evergreen Signal Discovery Safe Pattern
-
-Use when the campaign is a shared evergreen signal lane and the source signal is
-real but not sender-owned.
-
-```text
-Hey {{first_name}},
-
-The AI-assisted GTM conversations keep coming back to one problem: turning good LinkedIn signal into review-ready pipeline without another outbound dashboard.
-
-Sellable helps teams find signal-matched prospects, filter for fit, and generate reviewed LinkedIn copy from one workflow.
-
-Curious if LinkedIn outbound is a channel you're trying to make more reliable this quarter?
-```
-
-Why it works:
-
-- no low-confidence relevance hedge
-- no `I'm building` or founder-only first person
-- no internal workflow vocabulary such as Codex, MCP, agent workflows, workflow
-  table, lead source, or signal discovery
-- the signal becomes a buyer problem instead of an activity-log opener
-- safe for multiple senders attached to the same shared lane
-
 ## Conditional Examples
 
 Use these only when the campaign motion matches.
@@ -445,25 +419,24 @@ Tokenized shape:
 Hey there
 
 Thanks for the support on my post about {{post_topic_line}}
+
+Curious, is this something you're dealing with right now?
 ```
 
 Transfer rules:
 
 - Do not hardcode a post topic. Fill `{{post_topic_line}}` from the actual
   selected sender-authored post or use a safer source-specific phrase.
-- Do not add a relevance question, CTA, product line, or extra paragraph after
-  the thank-you line. The reply-rate lesson is the casual warm acknowledgment,
-  not a cold pitch appended to it.
 - Do not use "showing some love"; it reads too casual for executive/VP/director
   contacts.
 - Keep the thank-you line. The point of this motion is acknowledging real
-  sender-owned support without appending a cold relevance question. Do not
-  flatten it back to "saw you pop up" unless the sender specifically asks for
-  that wording.
+  sender-owned support before asking a light relevance question. Do not flatten
+  it back to "saw you pop up" unless the sender specifically asks for that
+  wording.
 - Do not copy this shape into shared lanes, third-party thread sources, or cold
   fallback campaigns.
-- Do not pitch, ask for a meeting, or mention internal product vocabulary in
-  message one.
+- Keep the question closed and problem-oriented; do not pitch, ask for a
+  meeting, or mention internal product vocabulary in message one.
 
 ## Useful CTA Shapes
 

package/skills/create-campaign-v2/references/gold-standard-message-patterns.md

@@ -199,21 +199,11 @@ Shape:
 Prefer:
 
 - lowercase or casual casing when the motion supports it
-- an honest line like "hope this is relevant" or "so may be off, but this seemed relevant" only for non-evergreen weak-signal campaigns
+- an honest line like "hope this is relevant" or "so may be off, but this seemed relevant"
 - a concrete CTA that names the useful conversation or asset
 - binary options only when the brief explicitly supports two real next steps
 - direct wording over polished marketing language
 
-Shared Evergreen Signal Discovery override:
-
-- Do not use `hope this is relevant`, `might be interested`, or `saw you in a
-  few conversations` as the opener.
-- Do not use `I'm building`, `I've mapped`, `my company`, or `my team`.
-- Turn the source topic into a buyer problem bridge, then write the product line
-  in team/company voice.
-- If the source topic cannot support a concrete bridge, omit the source line and
-  start from a role/company/problem observation.
-
 Avoid:
 
 - copying a gimmick like "from a claude code terminal" unless the brief

package/skills/create-campaign-v2/references/sellable-cleanup-rules.md

@@ -74,7 +74,7 @@ Revise or reject the sample when any of these happen.
 - **actions are implied, not stated** — e.g. "runs that chain as AI agents" when a clearer version would name the specific actions (verb + object, one per line)
 - **category-level opener used when a per-lead signal exists** — if `lead-sample.json` carries any per-lead signal (post, hire, visible tool, topic engagement), the opener must reference it. Category-level openers of shape `"Most [category] teams still do X by hand"` are only acceptable when zero per-lead signal is in the sample. When a category-level opener is used as fallback, Findings must flag it explicitly
 - **mind-reading from engagement signals** — a topic engagement, post, public activity, role, company, or hiring trigger does not prove buyer intent. Reject phrases like `"AI-GTM stack is clearly on your mind"`, `"you're clearly focused on..."`, `"obviously relevant"`, or `"already thinking about..."` unless that exact priority is explicitly present in `lead-sample.json`. Translate to low-certainty buyer context or omit the signal from copy.
-- **source-y signal narration** — reject `"saw you on..."`, `"saw you engaging with..."`, `"you commented on..."`, `"your LinkedIn activity..."`, `"you might not remember the thread..."`, `"found you through [source] and your role looked close..."`, or any line that makes the recipient feel watched unless the chosen archived motion is intentionally self-aware about the signal. For sender-owned LinkedIn post sources, a light first-person acknowledgment is allowed when row data proves a reaction/comment: `"appreciate you showing some love on my post about [topic]"` or `"thanks for showing support on my [topic] post"`. Do not name a comment unless comment text is present. Follow the acknowledgment with a soft relevance bridge before broad pain/product copy, e.g. `"figured this might be relevant if LinkedIn is becoming more of a GTM channel for [company]"`. For third-party LinkedIn-post-sourced campaigns, a topic-level bridge is allowed when it explains why the note exists and stays apologetically uncertain: `"saw you in a few conversations about [topic], so may be off, but this seemed relevant."`, `"saw you in a few conversations around [topic], so hope this is relevant."`, or `"found you in a thread about [topic], so may be off, but this seemed relevant."` Shared evergreen signal exception: these hedges are blocked for Shared Signal Discovery and other shared evergreen lanes; use a concrete signal/problem bridge or omit the source line. Reserve `"raise your hand"` language for explicit lead-magnet comments, replies, or opt-ins. Translate the signal into natural buyer context or omit it.
+- **source-y signal narration** — reject `"saw you on..."`, `"saw you engaging with..."`, `"you commented on..."`, `"your LinkedIn activity..."`, `"you might not remember the thread..."`, `"found you through [source] and your role looked close..."`, or any line that makes the recipient feel watched unless the chosen archived motion is intentionally self-aware about the signal. For sender-owned LinkedIn post sources, a light first-person acknowledgment is allowed when row data proves a reaction/comment: `"appreciate you showing some love on my post about [topic]"` or `"thanks for showing support on my [topic] post"`. Do not name a comment unless comment text is present. Follow the acknowledgment with a soft relevance bridge before broad pain/product copy, e.g. `"figured this might be relevant if LinkedIn is becoming more of a GTM channel for [company]"`. For third-party LinkedIn-post-sourced campaigns, a topic-level bridge is allowed when it explains why the note exists and stays apologetically uncertain: `"saw you in a few conversations about [topic], so may be off, but this seemed relevant."`, `"saw you in a few conversations around [topic], so hope this is relevant."`, or `"found you in a thread about [topic], so may be off, but this seemed relevant."` Reserve `"raise your hand"` language for explicit lead-magnet comments, replies, or opt-ins. Translate the signal into natural buyer context or omit it.
 - **sender-owned source rendered as third-party** — hard fail when the source post is sender-owned and the draft says `"found you in a thread"`, `"saw you in a thread"`, `"saw you in conversations"`, or `"saw you in a few conversations"` as if the post were third-party. For sender-owned sources, the copy must either use a light first-person acknowledgment plus a soft relevance bridge, or omit the source line. If multiple senders may send the campaign, or the final sender/source-owner match is ambiguous, do not assume a specific `my post` voice or name a specific sender; omit the sender-owned source line until row-level sender ownership is proven. Neutral low-certainty thread/source language is only for truly third-party sources.
 - **fake line-to-line continuity** — reject line stacks where the source acknowledgment, relevance bridge, product line, and CTA do not actually build on each other. Each line must make the next line feel earned. If two adjacent lines could be swapped, deleted, or joined with `"anyway"` without changing the meaning, the transition is fake. In sender-owned post campaigns, the chain should be: support on my post -> why this topic may matter for the company -> what the product/problem does about that same topic -> low-friction next step.
 - **assumptive title-fit opener** — reject `"Your [role] role at [company] looked close to this problem"` or `"looked close to this outbound campaign problem"`. This asserts fit from title/company. Keep the apologetic uncertainty instead: `"may be off, but if [workflow] is relevant to what you're working on..."`.