@sellable/mcp 0.1.946 → 0.1.948

package/dist/tools/campaign-message-preparation.js

@@ -269,7 +269,6 @@ export async function startPrepareCampaignMessages(input) {
         effectId: input.effectId,
         ...(reportingContext ? { reportingContext } : {}),
         ...(input.history ? { history: input.history } : {}),
-        ...(input.requestSource ? { requestSource: input.requestSource } : {}),
         ...(workspaceId ? { workspaceId } : {}),
     }, workspaceId ?? undefined);
     return sanitizePreparationResponse(result);
@@ -286,6 +285,7 @@ export async function getPrepareCampaignMessagesStatus(input) {
         tableId: input.tableId,
         ...(reportingContext ? { reportingContext } : {}),
         ...(input.history ? { history: input.history } : {}),
+        ...(input.requestSource ? { requestSource: input.requestSource } : {}),
         ...(workspaceId ? { workspaceId } : {}),
     }, workspaceId ?? undefined);
     return sanitizePreparationResponse(result);

package/package.json

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

package/skills/campaign-daily-review/SKILL.md

@@ -44,12 +44,15 @@ the exact wait or outcome.
      first when it is missing;
    - healthy supplied campaign: maintain it and stay quiet;
    - manual pause: respect it;
-   - missing approval, connection or decision: with `launchConsent.mode: "autopilot"` approve messages that passed the quality check and start or resume the campaign yourself; otherwise retain one exact next step. Ask only for what you cannot do yourself, such as a LinkedIn connection, as one question.
-   Whatever the outcome, also run canonical Refill Sends with `yolo:true` for the
-   workspace's next two sender-local days before you finish. It checks capacity
-   itself and does nothing when queues are full. Keep going until the gap is
-   filled or a real blocker remains; refill results reach the customer in the
-   next results update, not as a separate post.
+   - missing approval, connection or decision: with `launchConsent.mode: "autopilot"` approve messages that passed the quality check and start or resume the campaign yourself. When `launchConsent` has no answer yet, ask the one-time question instead of asking for approval: "I can approve messages that pass my quality check and launch for you, then keep your sends filled. Reply review first if you would rather approve." Save the answer with `save_context` as Create Campaign's Standing Consent does. With `review_first`, retain one exact next step. Ask only for what you cannot do yourself, such as a LinkedIn connection, as one question.
+   A built-in weekday refill job fills sends before this review; do not run
+   Refill Sends again unless `refill` is this review's one outcome. Read
+   `refill_v3_world_state` for the next two sender-local days: a row whose
+   reason names a disconnected sender (`sender_disconnected`), a disconnected
+   Sales Navigator (`sales_nav_disconnected`) or
+   `paid_inmail_connection_health_recheck_required` is a fix only the customer
+   can make. Make it this review's `input`: name the sender and say reconnect
+   LinkedIn or reconnect Sales Navigator in Settings.
 6. Observe the owned operation, then record the outcome against the same review
    effect and fence. The `record_review_outcome` call contains only its action,
    effect, fence, review outcome, summary, and optional decision/operation refs;