@sellable/mcp 0.1.362 → 0.1.363

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

@@ -7,9 +7,6 @@ allowed-tools:
   - mcp__sellable__get_campaign_refill_state
   - mcp__sellable__fill_campaign_horizon
   - mcp__sellable__get_campaign
-  - mcp__sellable__get_campaign_context
-  - mcp__sellable__update_campaign
-  - mcp__sellable__get_provider_prompt
   - mcp__sellable__get_campaign_message_preparation_status
   - mcp__sellable__start_campaign_message_preparation
   - mcp__sellable__cancel_campaign_message_preparation
@@ -17,7 +14,6 @@ allowed-tools:
   - mcp__sellable__wait_for_lead_list_ready
   - mcp__sellable__confirm_lead_list
   - mcp__sellable__search_signals
-  - mcp__sellable__select_promising_posts
   - mcp__sellable__fetch_post_engagers
   - mcp__sellable__search_sales_nav
   - mcp__sellable__lookup_sales_nav_filter
@@ -31,10 +27,6 @@ allowed-tools:
   - mcp__sellable__get_rows
   - mcp__sellable__get_rows_minimal
   - mcp__sellable__get_table_rows
-  - mcp__sellable__get_campaign_table_schema
-  - mcp__sellable__select_campaign_cells
-  - mcp__sellable__wait_for_campaign_processing
-  - mcp__sellable__get_sender
 ---
 
 # Refill Sends Workflow
@@ -109,42 +101,6 @@ Source replenishment choices:
   source prospects into the same campaign/source-list path, then confirm
   readiness.
 
-### Running Campaign Signal Discovery Recovery
-
-For an already-running regular campaign that needs same-campaign Signal
-Discovery replenishment, treat the watch/current-step transition as a guarded
-repair, not as normal create-campaign navigation.
-
-Do not call `search_signals` with `currentStep:"signal-discovery"` directly from `currentStep:"running"`. The campaign step guard intentionally rejects that
-backwards transition. After exact approval and a fresh refill-state reread, clear `currentStep` only if it still exactly matches `running`:
-
-```text
-update_campaign({ campaignId, currentStep:null, clearCurrentStepIfMatches:"running" })
-```
-
-Then register provider preflight and run a campaign-scoped `search_signals` so
-post rows exist in the campaign's Signal Discovery state:
-
-```text
-get_provider_prompt({ provider:"signal-discovery", campaignOfferId, confirmed:true })
-search_signals({ campaignOfferId, currentStep:"signal-discovery", confirmed:true, ... })
-```
-
-Use `select_promising_posts` before importing. For a fresh source refill, prefer
-`selectionMode:"replace"` and `scrapePlanMode:"capacity-target"` with the
-approved `targetEngagerCount` and `maxPostsToScrape`. If the approved post set cannot cover the target, do not knowingly run an under-capacity scrape; ask for approval to expand the selected post set or switch source.
-
-If `import_leads` returns `reusedExistingSourceList` but the user explicitly
-approved a different selected-post scrape, retry `import_leads` with the existing `sourceLeadListId` from that response or from refill state. For Signal
-Discovery this bypasses the stale reuse guard and materializes the newly
-selected campaign-scoped posts into a fresh source list.
-
-After `wait_for_lead_list_ready`, call `confirm_lead_list` with the new
-source-list id and same campaign id. Pass `currentStep:"running"` to `confirm_lead_list` for an ACTIVE already-running campaign so the watched state
-returns to Running after same-campaign source rows are copied. Do not call
-`update_campaign` to fake this after the copy; `confirm_lead_list` owns the
-post-copy state transition.
-
 Before any source mutation, show exact approval evidence: workspace id,
 campaign id, workflow table id, source/provider id, source-list id when known,
 import caps, target dates/caps, dedupe/DNC/provider exclusion expectations, and
@@ -179,28 +135,11 @@ Before prep or approval mutation, reread `get_campaign_refill_state` and compare
 If they changed, stop. A second concurrent refill run must see the first run's
 import/prep state on reread and avoid duplicate work.
 
-After same-campaign source copy, inspect the actual campaign-table position of
-the copied rows before starting prep. Newly copied rows often land after the first 100 table rows. Use `get_campaign_table_schema` to read the `reviewBatch`,
-then use `select_campaign_cells` diagnostics against
-`rowSelector:{ type:"reviewBatch" }` for `enrich`, `generateMessage`, and
-`approved` roles when needed.
-
-If review-batch enrich cells are pending or Generate Message cells are
-dependency-blocked, omit `maxRowsToCheck` so the adaptive prep job can cover the
-bounded table scan, or set a bounded cap high enough to include appended rows
-when row count evidence requires it. Do not run a fixed `maxRowsToCheck:100` prep pass after appending rows to a larger existing campaign table; it can spend
-the whole budget on older rows and miss the refill batch.
-
 Scheduled success requires a post-action reread proving scheduler-owned cells
 with non-null `scheduledFor`. Prepared, approved, and ready-to-schedule rows are
 intermediate states; report them as awaiting scheduler unless scheduled cells
 are present.
 
-preparedMessages can remain 0 while scheduler-ready state changes downstream.
-After a prep job reaches a terminal state, run `wait_for_campaign_processing`
-when generated/pass counts are still settling, then poll `get_campaign_refill_state` until `readyToSchedule` drops, scheduled counts increase, or the state clearly
-remains awaiting scheduler. Do not force scheduler fields directly.
-
 ## Evergreen Campaign Discipline
 
 `fill_campaign_horizon` is a legacy evergreen-only lower-level primitive. Call it

package/dist/tools/setup-evergreen-campaigns.d.ts

@@ -1,113 +0,0 @@
-type SetupEvergreenCampaignsInput = {
-    mode?: "plan" | "verify";
-    depth?: "structure_only" | "customer_visible";
-    yolo?: boolean;
-    allConnectedSenders?: boolean;
-    selectedSenderIds?: string[];
-    postEngagerSenderIds?: string[];
-    sharedSenderIds?: string[];
-    bindings?: Array<{
-        laneKey: string;
-        campaignId: string;
-        tableId: string;
-    }>;
-    planRevision?: string;
-    selectedActionIds?: string[];
-    receipts?: unknown[];
-};
-export declare const setupEvergreenCampaignsToolDefinitions: {
-    name: string;
-    description: string;
-    inputSchema: {
-        type: string;
-        properties: {
-            mode: {
-                type: string;
-                enum: string[];
-                description: string;
-            };
-            depth: {
-                type: string;
-                enum: string[];
-                description: string;
-            };
-            yolo: {
-                type: string;
-                description: string;
-            };
-            allConnectedSenders: {
-                type: string;
-                description: string;
-            };
-            selectedSenderIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            postEngagerSenderIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            sharedSenderIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            bindings: {
-                type: string;
-                maxItems: number;
-                items: {
-                    type: string;
-                    properties: {
-                        laneKey: {
-                            type: string;
-                        };
-                        campaignId: {
-                            type: string;
-                        };
-                        tableId: {
-                            type: string;
-                        };
-                    };
-                    required: string[];
-                    additionalProperties: boolean;
-                };
-                description: string;
-            };
-            planRevision: {
-                type: string;
-                description: string;
-            };
-            selectedActionIds: {
-                type: string;
-                items: {
-                    type: string;
-                };
-                maxItems: number;
-                description: string;
-            };
-            receipts: {
-                type: string;
-                maxItems: number;
-                items: {
-                    type: string;
-                };
-                description: string;
-            };
-        };
-        required: never[];
-        additionalProperties: boolean;
-    };
-}[];
-export declare function setupEvergreenCampaigns(input: SetupEvergreenCampaignsInput): Promise<unknown>;
-export {};

package/dist/tools/setup-evergreen-campaigns.js

@@ -1,100 +0,0 @@
-import { getApi } from "../api.js";
-async function postSetupEvergreenCampaigns(body) {
-    const api = getApi();
-    return api.post("/api/v3/mcp/setup-evergreen-campaigns", body);
-}
-export const setupEvergreenCampaignsToolDefinitions = [
-    {
-        name: "setup_evergreen_campaigns",
-        description: "Evergreen campaign setup plan/verify command. Use plan mode first to inspect exact workspace/sender/campaign/table/source state and receive immutable lane packets. `selectedSenderIds` is a legacy shorthand for both scopes; prefer `postEngagerSenderIds` for the Post Engagers sender scope and `sharedSenderIds` for the shared lane sender scope when they differ. The command plans one Post Engagers lane per post-engager sender plus shared Signal Discovery and Shared Cold Fallback lanes for the shared sender set. yolo is only a parent-skill auto-execution hint for safe lane packets; this backend command remains read-only in plan mode and verifies receipts in verify mode. When safe-yolo needs normal setup work, the parent skill may ask for bounded delegated approval: one approval over the current planRevision, selected action ids, caps, allowed side-effect classes, and stop conditions lets lane workers execute without per-substep approval while staying inside that packet. Lane workers must execute creation, source import, create-campaign workflow steps, generate-messages, sequence attachment, pause_campaign review-state transition when the current table is still DRAFT, and review readiness through existing create-campaign workflow/subskills, then return receipts here for verification. Customer-visible verify receipts must include createCampaignStepReceipt with setupPlanCall, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall. messageDraftingReceipt must use statusSource:'branch' or statusSource:'packaged-generate-messages-worker' and include proof that generate-messages was loaded, start_campaign_message_preparation/get_campaign_message_preparation_status ran when the packaged worker path is used, validationResult:'passed', a passed qualityReview, and at least 3 concrete sampleMessages with row ids, generated message text, pass verdicts, and no issues; Shared Cold Fallback samples with a standalone name followed by 'Hey there' are rejected. This command does not launch campaigns, does not schedule sends, does not assign scheduler-owned send fields, does not raw-write campaign status, does not archive/delete cleanup targets, and does not spend paid credits.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                mode: {
-                    type: "string",
-                    enum: ["plan", "verify"],
-                    description: 'Defaults to "plan". Verify only validates worker receipts.',
-                },
-                depth: {
-                    type: "string",
-                    enum: ["structure_only", "customer_visible"],
-                    description: 'Use "customer_visible" for full setup proof or "structure_only" when only ensuring lane shells/config.',
-                },
-                yolo: {
-                    type: "boolean",
-                    description: "plan mode only. Requests auto-executable lane packets when state is safe; never authorizes cleanup, launch, scheduling, sending, or ambiguous target choice.",
-                },
-                allConnectedSenders: {
-                    type: "boolean",
-                    description: "Plan sender-owned Post Engagers lanes for all eligible connected senders in the active workspace.",
-                },
-                selectedSenderIds: {
-                    type: "array",
-                    items: { type: "string" },
-                    maxItems: 25,
-                    description: "Legacy shorthand: exact OutboundSenderIdentity ids for both sender-owned Post Engagers lanes and shared-lane sender set. Prefer scoped fields when those differ.",
-                },
-                postEngagerSenderIds: {
-                    type: "array",
-                    items: { type: "string" },
-                    maxItems: 25,
-                    description: "Exact OutboundSenderIdentity ids that should receive sender-owned Post Engagers lanes.",
-                },
-                sharedSenderIds: {
-                    type: "array",
-                    items: { type: "string" },
-                    maxItems: 25,
-                    description: "Exact OutboundSenderIdentity ids attached to shared Signal Discovery and Shared Cold Fallback lanes.",
-                },
-                bindings: {
-                    type: "array",
-                    maxItems: 20,
-                    items: {
-                        type: "object",
-                        properties: {
-                            laneKey: { type: "string" },
-                            campaignId: { type: "string" },
-                            tableId: { type: "string" },
-                        },
-                        required: ["laneKey", "campaignId", "tableId"],
-                        additionalProperties: false,
-                    },
-                    description: "Exact existing campaign/table bindings to reuse for lane keys. Do not pass names.",
-                },
-                planRevision: {
-                    type: "string",
-                    description: "Required for verify. Copy from the immediately preceding plan.",
-                },
-                selectedActionIds: {
-                    type: "array",
-                    items: { type: "string" },
-                    maxItems: 20,
-                    description: "Required for verify. Immutable action ids selected from the current plan.",
-                },
-                receipts: {
-                    type: "array",
-                    maxItems: 20,
-                    items: { type: "object" },
-                    description: "Required for verify. Structured lane worker receipts from create-campaign/source/message/sequence execution. Customer-visible lanes must include createCampaignStepReceipt with setupPlanCall, campaignBriefReceipt, sourceDecisionReceipt, filterDecisionReceipt, messageDraftingReceipt, reviewBatchReceipt, sequenceReceipt, and verifyCall.",
-                },
-            },
-            required: [],
-            additionalProperties: false,
-        },
-    },
-];
-export function setupEvergreenCampaigns(input) {
-    return postSetupEvergreenCampaigns({
-        mode: input.mode,
-        yolo: input.yolo,
-        depth: input.depth,
-        allConnectedSenders: input.allConnectedSenders,
-        selectedSenderIds: input.selectedSenderIds,
-        postEngagerSenderIds: input.postEngagerSenderIds,
-        sharedSenderIds: input.sharedSenderIds,
-        bindings: input.bindings,
-        planRevision: input.planRevision,
-        selectedActionIds: input.selectedActionIds,
-        receipts: input.receipts,
-    });
-}