@sellable/mcp 0.1.474 → 0.1.475

package/dist/tools/refill-sends.js

@@ -214,6 +214,7 @@ export function refillSendsCommand(input = {}) {
             "Fresh reread get_campaign_refill_state immediately before any import, prep, approval, or horizon-fill mutation.",
             "Maintain a target-window saturation ledger per selected sender from get_refill_target_plan: selected days, gross capacity, actual sent counts, future scheduler-owned scheduled counts, projected counts, ready-to-schedule buffer, remaining projected gap, paid InMail threshold feasibility, targetShapeRevision, stateRevision, and next MCP primitive.",
             "In --yolo, this tool automatically maintains a run-local refreshedPaidInmailSenderIds set: when the first target plan returns refresh_paid_inmail_credits candidates for selected paid-InMail lanes, it refreshes each exact sender at most once, reruns get_refill_target_plan, and returns the post-refresh targetPlan before any prep/import/approval/start action is chosen.",
+            "Do not present paid-credit refresh as the next operator action after refill_sends returns autoPaidInmailRefresh and the post-refresh targetPlan.",
             "If paid InMail feasibility remains below threshold after that automatic refresh, report the exact sender/campaign/table/column threshold action or connection fallback; --yolo must not lower paid InMail thresholds or create campaigns.",
             "In --yolo or after one Accept, continue through every safe selected sender/campaign action covered by the rendered target packet; sent/scheduled-count progress changes stateRevision and should continue while targetShapeRevision is stable.",
             "Do not complete a fill/schedule request until a final get_refill_target_plan or refill-state reread proves projected coverage (sent + scheduled) fills the scheduler-forward target window. Treat awaiting_scheduler_after_ready_buffer as loaded, awaiting scheduler when ready buffer covers the gap; do not import/prep more rows in that state, and keep polling unless Christian stops/statuses the run or a concrete non-scheduler blocker such as paid_inmail_below_threshold appears.",

package/package.json

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

package/skills/refill-sends/SKILL.md

@@ -195,7 +195,9 @@ report. Treat `awaiting_scheduler_after_ready_buffer` as an in-progress wait
 state, not a close-out condition.
 If paid InMail credit facts are stale or missing and the first target plan
 contains `refresh_paid_inmail_credits`, do not present that as the operator's
-next action in `--yolo`. Trust `refill_sends.autoPaidInmailRefresh`: it should
+next action in `--yolo`. Do not present paid-credit refresh as the next operator
+action after `refill_sends` returns `autoPaidInmailRefresh` and the
+post-refresh `targetPlan`. Trust `refill_sends.autoPaidInmailRefresh`: it should
 show the exact sender ids refreshed once, sender-credit-cache write receipts,
 and a returned post-refresh `targetPlan`. Continue from that post-refresh packet.
 If paid InMail is below threshold after the fresh credit read, report the exact

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

@@ -141,10 +141,12 @@ in-progress wait state, not a reason to mark the goal complete or blocked.
    close-out condition.
    If paid InMail credit facts are stale or missing and the first target plan
    contains `refresh_paid_inmail_credits`, do not present that as the operator's
-   next action in `--yolo`. Trust `refill_sends.autoPaidInmailRefresh`: it should
-   show the exact sender ids refreshed once, sender-credit-cache write receipts,
-   and a returned post-refresh `targetPlan`. Continue from that post-refresh
-   packet. If paid InMail is below threshold after the fresh credit read, report
+   next action in `--yolo`. Do not present paid-credit refresh as the next
+   operator action after `refill_sends` returns `autoPaidInmailRefresh` and the
+   post-refresh `targetPlan`. Trust `refill_sends.autoPaidInmailRefresh`: it
+   should show the exact sender ids refreshed once, sender-credit-cache write
+   receipts, and a returned post-refresh `targetPlan`. Continue from that
+   post-refresh packet. If paid InMail is below threshold after the fresh credit read, report
    the exact campaign/table/column threshold action or
    connection fallback; `--yolo` does not lower paid-InMail thresholds or create campaigns.
 2. Call `resolve_campaign_fill_route`. Use `intent:"plain"` for generic