@sellable/mcp 0.1.80 → 0.1.82

package/agents/post-find-leads-filter-scout.md

@@ -1,28 +1,35 @@
-You are the Post-Lead Filter Scout for Sellable create-campaign-v2.
+You are Lead Fit Builder for Sellable create-campaign-v2.
 
 Your job starts only after find-leads has produced `lead-review.md` and
 `lead-sample.json`, and the lead source has been approved or auto-confirmed.
 Work only on the lead filter branch. Do not source new leads, draft messages,
-import leads, create campaigns, ask the user questions, or mutate live campaign
-state.
+import leads, create campaigns, or ask the user questions. Your only live
+campaign mutation is calling `save_rubrics` after the production rubrics are
+ready.
 
 Required inputs:
 
 - `brief.md`
 - `lead-review.md`
 - `lead-sample.json`
+- campaign state from the parent thread
+- campaign table sample from the parent thread
 
 Required first steps:
 
 1. Read the three required inputs.
 2. Load the filter-leads reference before writing artifacts:
    `get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/filter-leads.md" })`.
+3. Treat campaign state and the campaign table sample as the input of record.
+   Disk files are context/debug aids, not durable state.
 
 Owned outputs:
 
-- `lead-filter.md`
-- `rubric.json` when the filter is confirmed and production-shaped rubrics are
-  safe to write
+- Durable campaign rubrics via `save_rubrics({ campaignOfferId, leadScoringRubrics })`
+  when the filter is confirmed and production-shaped rubrics are safe to write.
+  `save_rubrics` is the durable writer.
+- `lead-filter.md` debug artifact after the durable campaign write
+- `rubric.json` debug artifact after the durable campaign write
 
 Do not write or modify:
 
@@ -46,12 +53,16 @@ Process:
 5. Keep source mechanics out of production rubrics. Engagement, provider,
    priority, or first-send ordering can inform prioritization, but they are not
    standalone ICP qualification rules.
-6. Write `lead-filter.md` first. If status is `confirmed`, also write
-   `rubric.json` with 2-5 production-shaped `leadScoringRubrics`.
+6. If status is `confirmed`, call `save_rubrics` with 2-5 production-shaped
+   active `leadScoringRubrics` before reporting success. If `save_rubrics`
+   fails, stop and report the blocker; do not claim the filter is persisted.
+7. Write `lead-filter.md` and `rubric.json` only as debug artifacts after
+   campaign persistence succeeds.
 
 Return a concise final status with:
 
 - filter status: `confirmed`, `confirm-with-user`, or `revise-find-leads`
+- whether `save_rubrics` succeeded and how many active rubrics were persisted
 - artifacts written
 - strongest keep rules
 - strongest exclusion rules

package/agents/post-find-leads-message-scout.md

@@ -1,16 +1,19 @@
-You are the Post-Lead Message Scout for Sellable create-campaign-v2.
+You are Message Draft Builder for Sellable create-campaign-v2.
 
 Your job starts only after find-leads has produced `lead-review.md` and
 `lead-sample.json`, and the lead source has been approved or auto-confirmed.
 Work only on the message generation branch. Do not source new leads, create lead
 filters, import leads, create campaigns, ask the user questions, or mutate live
-campaign state.
+campaign state. Do not call `update_campaign_brief`; the main thread owns the
+approval write.
 
 Required inputs:
 
 - `brief.md`
 - `lead-review.md`
 - `lead-sample.json`
+- campaign state from the parent thread
+- campaign table sample from the parent thread
 
 Required first steps:
 
@@ -18,12 +21,16 @@ Required first steps:
 2. Load 100% of the real generate-messages prompt with chunked
    `get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
    calls until `hasMore` is false.
+3. Treat campaign state and the campaign table sample as the input of record.
+   Disk files are context/debug aids, not durable state.
 
 Owned outputs:
 
-- `message-validation.md`
-- optional `message-prep.md`
-- optional `message-candidate-drafts.md`
+- proposed template using supported `{{...}}` tokens
+- one sample message rendered from the proposed template
+- `message-validation.md` debug artifact
+- optional `message-prep.md` debug artifact
+- optional `message-candidate-drafts.md` debug artifact
 
 Do not write or modify:
 
@@ -48,13 +55,21 @@ Process:
    does not exist yet, choose probable good-fit rows from `lead-sample.json` and
    mark the final reconciliation as pending.
 5. Write `message-validation.md`. Do not write `message-review.md`; the parent
-   thread owns the joined review after both post-lead scouts finish.
+   thread owns the joined review after both builders finish.
+6. Return the proposed template and one sample message for approval. Do not
+   mutate campaignBrief. The main thread must show readable filters with
+   reasons, show one sample message, ask the user to approve or edit, then write
+   the approved template with `update_campaign_brief` only after approval.
+7. If the user edits the proposal, the main thread updates the proposal and asks
+   again. Do not queue enrichment, validation rows, or Generate Message work
+   until the approved template write succeeds.
 
 Return a concise final status with:
 
 - artifacts written
 - whether the full generate-messages prompt was loaded
 - lead sample basis used
+- proposed template and one sample message
 - selected winner summary
 - whether final reconciliation with `lead-filter.md` is complete or pending
 

package/agents/registry.json

@@ -154,25 +154,33 @@
       "name": "post-find-leads-filter-scout",
       "kind": "post-find-leads-scout",
       "promptFile": "post-find-leads-filter-scout.md",
-      "displayName": "Post-Lead Filter Scout",
+      "displayName": "Lead Fit Builder",
       "target": "filter-leads",
-      "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
-      "producesArtifacts": ["lead-filter.md"],
-      "optionalProducesArtifacts": ["rubric.json"],
+      "inputs": [
+        "brief.md",
+        "lead-review.md",
+        "lead-sample.json"
+      ],
+      "producesArtifacts": [
+        "lead-filter.md"
+      ],
+      "optionalProducesArtifacts": [
+        "rubric.json"
+      ],
       "ownership": "lead quality, false-positive patterns, keep/exclude rules, ability-to-pay checks, and production rubric translation only",
       "codex": {
-        "description": "Sellable post-find-leads scout for lead filtering and rubric generation after source approval.",
+        "description": "Lead Fit Builder for campaign-backed lead filtering and rubric persistence after source approval.",
         "model": "gpt-5.5",
         "modelReasoningEffort": "high",
         "sandboxMode": "workspace-write",
         "nicknameCandidates": [
-          "Lead Filter Scout",
-          "Filter Scout",
-          "Rubric Scout"
+          "Lead Fit Builder",
+          "Fit Builder",
+          "Rubric Builder"
         ]
       },
       "claude": {
-        "description": "Use proactively as a background Sellable post-find-leads scout after lead source approval to produce lead-filter.md and rubric.json from brief.md, lead-review.md, and lead-sample.json.",
+        "description": "Use proactively as Lead Fit Builder after lead source approval to persist campaign rubrics and write lead-filter debug artifacts from campaign state.",
         "model": "inherit",
         "background": true,
         "maxTurns": 8,
@@ -184,7 +192,8 @@
           "Grep",
           "Glob",
           "mcp__sellable__get_subskill_prompt",
-          "mcp__sellable__get_subskill_asset"
+          "mcp__sellable__get_subskill_asset",
+          "mcp__sellable__save_rubrics"
         ]
       }
     },
@@ -193,28 +202,34 @@
       "name": "post-find-leads-message-scout",
       "kind": "post-find-leads-scout",
       "promptFile": "post-find-leads-message-scout.md",
-      "displayName": "Post-Lead Message Scout",
+      "displayName": "Message Draft Builder",
       "target": "generate-messages",
-      "inputs": ["brief.md", "lead-review.md", "lead-sample.json"],
-      "producesArtifacts": ["message-validation.md"],
+      "inputs": [
+        "brief.md",
+        "lead-review.md",
+        "lead-sample.json"
+      ],
+      "producesArtifacts": [
+        "message-validation.md"
+      ],
       "optionalProducesArtifacts": [
         "message-prep.md",
         "message-candidate-drafts.md"
       ],
       "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only",
       "codex": {
-        "description": "Sellable post-find-leads scout for dry-mode message generation after source approval.",
+        "description": "Message Draft Builder for campaign-backed template proposals and sample messages after source approval.",
         "model": "gpt-5.5",
         "modelReasoningEffort": "high",
         "sandboxMode": "workspace-write",
         "nicknameCandidates": [
-          "Message Scout",
-          "Message Generation Scout",
-          "Copy Scout"
+          "Message Draft Builder",
+          "Draft Builder",
+          "Template Builder"
         ]
       },
       "claude": {
-        "description": "Use proactively as a background Sellable post-find-leads scout after lead source approval to run dry-mode message generation from brief.md, lead-review.md, and lead-sample.json.",
+        "description": "Use proactively as Message Draft Builder after lead source approval to propose an approved-template candidate and sample message from campaign state.",
         "model": "inherit",
         "background": true,
         "maxTurns": 10,

package/agents/source-scout-linkedin-engagement.md

@@ -4,11 +4,19 @@ Your job is to test whether active LinkedIn posts and engagers can produce a war
 
 Required first step:
 
-- Load the canonical provider prompt before searching: `get_provider_prompt({ provider: "signal-discovery", confirmed: true })`.
+- Load the canonical provider prompt before searching. If the parent supplies a
+  draft `campaignOfferId`, call `get_provider_prompt({ provider:
+"signal-discovery", campaignOfferId, confirmed: true })` and include that same
+  `campaignOfferId` in `search_signals` so the user can watch source work in the
+  campaign UI. Treat that as a campaign-attached persisted search; do not run a
+  post-mint search without the campaign ID. If no campaign ID is supplied, run
+  campaignless preview mode.
 
 Use the inherited Sellable MCP tools when available:
 
-- `search_signals` to find recent post lanes.
+- `search_signals` to find recent post lanes. Include `campaignOfferId` whenever
+  the parent provides one so selected searches/lists stay attached to the
+  campaign.
 - `fetch_post_engagers` to sample engagers from selected posts.
 
 Process:

package/agents/source-scout-prospeo-contact.md

@@ -4,13 +4,20 @@ Your job is to test whether Prospeo can produce verified-contact scale for the c
 
 Required first step:
 
-- Load the canonical provider prompt before searching: `get_provider_prompt({ provider: "prospeo", confirmed: true })`.
+- Load the canonical provider prompt before searching. If the parent supplies a
+  draft `campaignOfferId`, call `get_provider_prompt({ provider: "prospeo",
+campaignOfferId, confirmed: true })` and include that same `campaignOfferId` in
+  `search_prospeo` so the user can watch source work in the campaign UI. If no
+  campaign ID is supplied, run campaignless preview mode. Treat post-mint
+  searches with `campaignOfferId` as campaign-attached persisted search tabs;
+  do not run a live campaign search without the campaign ID.
 
 Use the inherited Sellable MCP tools when available:
 
 - `load_csv_domains` when the parent supplies a CSV on disk and no `domainFilterId` exists.
 - `save_domain_filters` when the parent supplies pasted/raw include or exclude domains and no `domainFilterId` exists.
-- `search_prospeo` for campaignless people previews.
+- `search_prospeo` for people previews. Include `campaignOfferId` whenever the
+  parent provides one so selected searches/lists stay attached to the campaign.
 
 Process:
 

package/agents/source-scout-sales-nav.md

@@ -4,12 +4,20 @@ Your job is to test whether Sales Navigator filters can produce a scalable, high
 
 Required first step:
 
-- Load the canonical provider prompt before searching: `get_provider_prompt({ provider: "sales-nav", confirmed: true })`.
+- Load the canonical provider prompt before searching. If the parent supplies a
+  draft `campaignOfferId`, call `get_provider_prompt({ provider: "sales-nav",
+campaignOfferId, confirmed: true })` and include that same `campaignOfferId` in
+  `search_sales_nav` so the user can watch source work in the campaign UI. If no
+  campaign ID is supplied, run campaignless preview mode. Treat post-mint
+  searches with `campaignOfferId` as campaign-attached persisted search tabs;
+  do not run a live campaign search without the campaign ID.
 
 Use the inherited Sellable MCP tools when available:
 
 - `lookup_sales_nav_filter` before any dynamic Sales Nav filter.
-- `search_sales_nav` for campaignless preview searches.
+- `search_sales_nav` for preview searches. Include `campaignOfferId` whenever
+  the parent provides one so selected searches/lists stay attached to the
+  campaign.
 
 Process:
 

package/dist/server.js

@@ -170,6 +170,9 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                 break;
             case "attach_recommended_sequence":
                 result = await attachRecommendedSequence(args);
+                if (args?.campaignId) {
+                    markCampaignContextDirty(args.campaignId, "attach_recommended_sequence");
+                }
                 break;
             case "bootstrap_create_campaign":
                 result = await bootstrapCreateCampaign(args);
@@ -194,7 +197,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
             case "update_campaign":
                 result = await updateCampaign(args?.campaignId, args);
                 if (result?._campaign?.id) {
-                    const entry = hydrateCampaignContextFromCampaign(result._campaign, "update_campaign");
+                    const entry = hydrateCampaignContextFromCampaign(result._campaign, "update_campaign", args?.flowVersion === "v2" ? "v2" : "v1");
                     result.navigation = entry.navState;
                     delete result._campaign;
                 }
@@ -204,6 +207,9 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                 break;
             case "start_campaign":
                 result = await startCampaign(args?.campaignId);
+                if (args?.campaignId && result?.success) {
+                    markCampaignContextDirty(args.campaignId, "start_campaign");
+                }
                 break;
             case "pause_campaign":
                 result = await pauseCampaign(args?.campaignId);

package/dist/tools/bootstrap.js

@@ -268,9 +268,9 @@ export async function bootstrapCreateCampaign(input = {}) {
         : "";
     const nextStep = safeToProceed
         ? resumeDetected
-            ? `Bootstrap complete.${workspaceNotice} Resume using campaign context, then load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }); if the response has hasMore=true, continue with nextOffset until hasMore=false.`
+            ? `Bootstrap complete.${workspaceNotice} Resume from campaign state and navigation diagnostics first; treat local draft artifacts as debug-only evidence. Then load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }); if the response has hasMore=true, continue with nextOffset until hasMore=false.`
             : flowVersion === "v2"
-                ? `Bootstrap complete.${workspaceNotice} Load create-campaign-v2 instructions with get_subskill_prompt({ subskillName: "create-campaign-v2" }); if the response has hasMore=true, continue with nextOffset until hasMore=false. Then start with the create-campaign-brief interview stage. Do not call create_campaign until the v2 approval gate returns approve.`
+                ? `Bootstrap complete.${workspaceNotice} Load create-campaign-v2 instructions with get_subskill_prompt({ subskillName: "create-campaign-v2" }); if the response has hasMore=true, continue with nextOffset until hasMore=false. Preserve the pre-intake sequence: confirm auth/workspace status, identity setup, sender discovery/listing, and lightweight profile/company lookup. Then run the short setup/intake, write the campaign brief, call create_campaign once to mint the watchable shell, surface the returned watch link, and hand off to lead finding.`
                 : `Bootstrap complete.${workspaceNotice} Load ${createCampaignSubskill?.name ?? "create-campaign"} instructions with get_subskill_prompt({ subskillName: "${createCampaignSubskill?.name ?? "create-campaign"}" }); if the response has hasMore=true, continue with nextOffset until hasMore=false. Follow that flow before calling create_campaign.`
         : "Bootstrap incomplete. Resolve blockingErrors and rerun bootstrap_create_campaign before provider/search/import tools.";
     // Strip prompt body from createCampaignSubskill — it's loaded via the host

package/dist/tools/campaigns.d.ts

@@ -128,6 +128,7 @@ export interface CreateCampaignInput {
     senderIds?: string[];
 }
 export interface UpdateCampaignInput {
+    flowVersion?: "v1" | "v2";
     offerPositioning?: unknown;
     campaignBrief?: unknown;
     leadSourceType?: string | null;
@@ -170,6 +171,7 @@ export declare const campaignToolDefinitions: ({
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
             rubric?: undefined;
+            flowVersion?: undefined;
         };
         required: never[];
         additionalProperties?: undefined;
@@ -204,6 +206,7 @@ export declare const campaignToolDefinitions: ({
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
             rubric?: undefined;
+            flowVersion?: undefined;
         };
         required: string[];
         additionalProperties?: undefined;
@@ -281,6 +284,7 @@ export declare const campaignToolDefinitions: ({
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
             rubric?: undefined;
+            flowVersion?: undefined;
         };
         required: string[];
         additionalProperties: boolean;
@@ -353,6 +357,7 @@ export declare const campaignToolDefinitions: ({
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
             rubric?: undefined;
+            flowVersion?: undefined;
         };
         required: never[];
         additionalProperties?: undefined;
@@ -416,6 +421,11 @@ export declare const campaignToolDefinitions: ({
                 type: string;
                 description: string;
             };
+            flowVersion: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             limit?: undefined;
             tableId?: undefined;
             leadLimit?: undefined;
@@ -462,6 +472,7 @@ export declare const campaignToolDefinitions: ({
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
             rubric?: undefined;
+            flowVersion?: undefined;
         };
         required: string[];
         additionalProperties?: undefined;
@@ -485,6 +496,7 @@ export interface UpdateCampaignResult {
     name: string;
     currentStep: string | null;
     updatedAt: string;
+    remediation?: string;
     navigation?: unknown;
     _campaign?: CampaignOfferNavigation;
 }

package/dist/tools/campaigns.js

@@ -139,7 +139,7 @@ export const campaignToolDefinitions = [
                 },
                 clientProspectId: {
                     type: "string",
-                    description: "Use this for existing sender prospects. For brand-new senders, pass `senderLinkedinUrl` and the backend will attempt sender lookup/creation during campaign mint.",
+                    description: "Use this for existing sender prospects. For brand-new senders, pass `senderLinkedinUrl` and the backend will attempt sender lookup/creation during campaign creation.",
                 },
                 // `senderLinkedinUrl` (not `linkedinUrl`) to disambiguate from
                 // prospect-side `linkedinUrl` fields used in other tools (research-prospect etc.).
@@ -254,6 +254,11 @@ export const campaignToolDefinitions = [
                     type: "array",
                     description: "Lead scoring rubric entries",
                 },
+                flowVersion: {
+                    type: "string",
+                    enum: ["v1", "v2"],
+                    description: "Framework flow version for returned navigation diagnostics (default: v1).",
+                },
             },
             required: ["campaignId"],
         },
@@ -618,7 +623,7 @@ export async function createCampaign(input) {
             `or all create fields. Missing: ${missing.join(", ")}.\n\n` +
             "Remediation:\n" +
             '- For full workflow, call get_subskill_prompt({ subskillName: "create-campaign" }) and follow it.\n' +
-            "- For net-new campaign creation: run the `research-sender` flow first, call `complete_sender_research`, then pass either `clientProspectId` (preferred) or `senderLinkedinUrl` and let the backend resolve sender context at mint time.\n" +
+            "- For net-new campaign creation: run the `research-sender` flow first, call `complete_sender_research`, then pass either `clientProspectId` (preferred) or `senderLinkedinUrl` and let the backend resolve sender context at campaign creation time.\n" +
             "- For resume, call create_campaign with campaignId only.");
     }
     assertNetNewCreateCampaignResearchReady();
@@ -653,7 +658,7 @@ export async function createCampaign(input) {
     if (isAutonomousMessageMint &&
         !explicitlyAllowsAiGenerated &&
         !hasTemplateToken) {
-        throw new Error("VALIDATION_ERROR: campaignBrief must include at least one supported {{token}} before minting into autonomous messaging.\n\n" +
+        throw new Error("VALIDATION_ERROR: campaignBrief must include at least one supported {{token}} before entering autonomous messaging.\n\n" +
             "Why this is blocked:\n" +
             "- Generate Message enters template mode only when campaignBrief.content contains {{...}}.\n" +
             "- Without a token, the message cascade uses freeform AI generation and may rewrite the approved message.\n\n" +
@@ -707,7 +712,11 @@ export async function createCampaign(input) {
 }
 export async function updateCampaign(campaignId, input) {
     const api = getApi();
-    const { campaignId: _ignore, interactionMode, ...updates } = input;
+    const { campaignId: _ignore, interactionMode, flowVersion: _flowVersion, senderIds, currentStep, ...updates } = input;
+    const hasSenderIds = Object.prototype.hasOwnProperty.call(input, "senderIds");
+    if (!hasSenderIds && currentStep !== undefined) {
+        updates.currentStep = currentStep;
+    }
     // Normalize campaignBrief: if a plain string is passed, wrap it in the
     // { name, content } structure the UI expects.  createCampaign already does
     // this, but updateCampaign was passing the string straight through.
@@ -747,13 +756,39 @@ export async function updateCampaign(campaignId, input) {
         !updates.currentStep) {
         updates.currentStep = "filter-rules";
     }
-    const result = await api.put(`/api/v2/campaign-offers/${campaignId}`, updates);
+    let result = null;
+    let senderRouteResult = null;
+    const shouldPreserveInteractionModePut = typeof interactionMode === "string" &&
+        interactionMode.trim().length > 0 &&
+        !hasSenderIds &&
+        Object.keys(updates).length === 0;
+    if (Object.keys(updates).length > 0 || shouldPreserveInteractionModePut) {
+        result = await api.put(`/api/v2/campaign-offers/${campaignId}`, updates);
+    }
+    if (hasSenderIds) {
+        const senderList = senderIds;
+        const senderCurrentStep = Array.isArray(senderList) && senderList.length === 0
+            ? "settings"
+            : currentStep;
+        const senderPayload = { senderIds: senderList };
+        if (senderCurrentStep !== undefined) {
+            senderPayload.currentStep = senderCurrentStep;
+        }
+        senderRouteResult = await api.patch(`/api/v3/campaigns/${campaignId}/senders`, senderPayload);
+        result = await api.get(`/api/v2/campaign-offers/${campaignId}`);
+    }
+    if (!result) {
+        result = await api.put(`/api/v2/campaign-offers/${campaignId}`, updates);
+    }
     // Serialize to only essential fields for context efficiency
     return {
         id: result.id,
         name: result.name,
         currentStep: result.currentStep,
         updatedAt: result.updatedAt,
+        ...(senderRouteResult?.remediation
+            ? { remediation: senderRouteResult.remediation }
+            : {}),
         // Provide full campaign snapshot for server-side context hydration.
         _campaign: result,
     };

package/dist/tools/context.d.ts

@@ -22,8 +22,8 @@ type CampaignContextEntry = {
     dirty: boolean;
     dirtyReasons: string[];
 };
-export declare function hydrateCampaignContextFromCampaign(campaign: CampaignOfferNavigation, reason: string): CampaignContextEntry;
-export declare function hydrateCampaignContextFromNavigation(navState: Awaited<ReturnType<typeof getCampaignNavigationState>>, reason: string): CampaignContextEntry;
+export declare function hydrateCampaignContextFromCampaign(campaign: CampaignOfferNavigation, reason: string, flowVersion?: "v1" | "v2"): CampaignContextEntry;
+export declare function hydrateCampaignContextFromNavigation(navState: Awaited<ReturnType<typeof getCampaignNavigationState>>, reason: string, flowVersion?: "v1" | "v2"): CampaignContextEntry;
 export declare function markCampaignContextDirty(campaignId: string, reason: string): void;
 export declare const contextToolDefinitions: {
     name: string;
@@ -62,8 +62,8 @@ export declare function getCampaignContext(input: GetCampaignContextInput): Prom
     dirtyReasons: string[];
     navigation: {
         campaignId: string;
-        computedStep: "campaign-created" | "pick-provider" | "provider-search" | "confirm-lead-list";
-        blockedAt: ("campaign-created" | "pick-provider" | "provider-search" | "confirm-lead-list") | null;
+        computedStep: "running" | "messages" | "settings" | "sequence" | "send" | "campaign-created" | "pick-provider" | "provider-search" | "confirm-lead-list" | "filter-rules";
+        blockedAt: ("running" | "messages" | "settings" | "sequence" | "send" | "campaign-created" | "pick-provider" | "provider-search" | "confirm-lead-list" | "filter-rules") | null;
         missing: string[];
         expectedHeadlessStep: string | null;
         headlessCurrentStep: string | null;
@@ -79,6 +79,12 @@ export declare function getCampaignContext(input: GetCampaignContextInput): Prom
             leadSourceProvider: string | null;
             selectedLeadListId: string | null;
             providerCurrentStep: string | null;
+            enableICPFilters: boolean | null;
+            activeRubricCount: number;
+            hasApprovedMessageTemplate: boolean;
+            senderCount: number;
+            hasSequenceTemplate: boolean;
+            campaignStatus: string | null;
         };
         warnings: string[];
     };

package/dist/tools/context.js

@@ -32,7 +32,7 @@ function deriveProviderConfig(framework, navState) {
         return null;
     return framework.providers[providerId] ?? null;
 }
-export function hydrateCampaignContextFromCampaign(campaign, reason) {
+export function hydrateCampaignContextFromCampaign(campaign, reason, flowVersion = "v1") {
     logNavigationDebug("context.hydrate_from_campaign.start", {
         campaignId: campaign.id,
         reason,
@@ -40,7 +40,6 @@ export function hydrateCampaignContextFromCampaign(campaign, reason) {
         workflowTableId: campaign.workflowTableId ?? null,
         leadSourceProvider: campaign.leadSourceProvider ?? null,
     }, campaign.id);
-    const flowVersion = "v1";
     const framework = getFrameworkSnapshot(flowVersion);
     const navState = computeCampaignNavigationStateFromCampaign(campaign, {
         includeTableCheck: false,
@@ -70,7 +69,7 @@ export function hydrateCampaignContextFromCampaign(campaign, reason) {
     }, campaign.id);
     return entry;
 }
-export function hydrateCampaignContextFromNavigation(navState, reason) {
+export function hydrateCampaignContextFromNavigation(navState, reason, flowVersion = "v1") {
     logNavigationDebug("context.hydrate_from_navigation.start", {
         campaignId: navState.campaignId,
         reason,
@@ -78,7 +77,6 @@ export function hydrateCampaignContextFromNavigation(navState, reason) {
         blockedAt: navState.blockedAt,
         missing: navState.missing,
     }, navState.campaignId);
-    const flowVersion = "v1";
     const framework = getFrameworkSnapshot(flowVersion);
     const providerConfig = deriveProviderConfig(framework, navState);
     const entry = {
@@ -178,6 +176,12 @@ export function markCampaignContextDirty(campaignId, reason) {
                 leadSourceProvider: null,
                 selectedLeadListId: null,
                 providerCurrentStep: null,
+                enableICPFilters: null,
+                activeRubricCount: 0,
+                hasApprovedMessageTemplate: false,
+                senderCount: 0,
+                hasSequenceTemplate: false,
+                campaignStatus: null,
             },
             warnings: [],
         },

package/dist/tools/leads.d.ts

@@ -114,6 +114,8 @@ export type ImportLeadsInput = {
     headlineICPCriteria?: string[];
     rubricGuidelines?: string[];
 };
+type ImportLeadProvider = NonNullable<ImportLeadsInput["provider"]>;
+type Phase126ImportProvider = Exclude<ImportLeadProvider, "apollo">;
 export type CancelLeadImportInput = {
     campaignOfferId: string;
     tableId: string;
@@ -2331,7 +2333,7 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     createdLeadList?: undefined;
     jobResult?: undefined;
 } | {
-    provider: "signal-discovery" | "apollo" | "sales-nav" | "prospeo";
+    provider: Phase126ImportProvider;
     leadListId: string;
     existingLeadListId: string;
     needsModeSelection: boolean;
@@ -2379,7 +2381,7 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     createdLeadList?: undefined;
     jobResult?: undefined;
 } | {
-    provider: "apollo" | "sales-nav" | "prospeo";
+    provider: "sales-nav" | "prospeo";
     leadListId: string;
     existingLeadListId: string;
     needsModeSelection: boolean;
@@ -2411,7 +2413,7 @@ export declare function importLeads(input: ImportLeadsInput): Promise<{
     createdLeadList?: undefined;
     jobResult?: undefined;
 } | {
-    provider: "apollo" | "sales-nav" | "prospeo";
+    provider: "sales-nav" | "prospeo";
     leadListId: string;
     createdLeadList: any;
     jobResult: any;
@@ -2471,3 +2473,4 @@ export declare function setHeadlineICPCriteria(input: SetHeadlineICPCriteriaInpu
     criteriaCount: number;
     message: string;
 }>;
+export {};