@sellable/mcp 0.1.298 → 0.1.299

package/dist/tools/model-quality.js

@@ -0,0 +1,72 @@
+const normalize = (value) => String(value ?? "")
+    .trim()
+    .toLowerCase();
+const normalizeHost = (host) => {
+    const normalized = normalize(host);
+    if (normalized.includes("claude") || normalized.includes("clod")) {
+        return "claude";
+    }
+    if (normalized.includes("codex") ||
+        normalized.includes("gpt") ||
+        normalized.includes("openai")) {
+        return "codex";
+    }
+    return "unknown";
+};
+const isHighClaudeReasoning = (reasoning) => {
+    const normalized = normalize(reasoning).replace(/[_\s-]+/g, "");
+    return ["high", "xhigh", "extrahigh"].includes(normalized);
+};
+const isExtraHighCodexReasoning = (reasoning) => {
+    const normalized = normalize(reasoning).replace(/[_\s-]+/g, "");
+    return ["xhigh", "extrahigh"].includes(normalized);
+};
+export function evaluateCampaignModelQuality(input = {}) {
+    const host = normalizeHost(input.host);
+    const model = input.model?.trim() || null;
+    const reasoningEffort = input.reasoningEffort?.trim() || null;
+    const recommendedModel = host === "claude" ? "Opus 4.8" : "GPT 5.5";
+    const recommendedReasoningEffort = host === "claude" ? "high or extra high" : "extra high";
+    if (!model && !reasoningEffort) {
+        return {
+            status: "unknown",
+            host,
+            model,
+            reasoningEffort,
+            recommendedModel,
+            recommendedReasoningEffort,
+            confirmationRequired: true,
+            message: "Model settings were not provided by the host. Before campaign-critical generation, confirm the user is using Claude Opus 4.8 at high/extra high or Codex GPT 5.5 at extra high.",
+        };
+    }
+    const normalizedModel = normalize(model);
+    const ok = host === "claude"
+        ? normalizedModel.includes("opus") &&
+            normalizedModel.includes("4.8") &&
+            isHighClaudeReasoning(reasoningEffort)
+        : normalizedModel.includes("gpt") &&
+            normalizedModel.includes("5.5") &&
+            isExtraHighCodexReasoning(reasoningEffort);
+    if (ok) {
+        return {
+            status: "ok",
+            host,
+            model,
+            reasoningEffort,
+            recommendedModel,
+            recommendedReasoningEffort,
+            confirmationRequired: false,
+            message: "Recommended campaign-quality model settings are active.",
+        };
+    }
+    return {
+        status: "warn",
+        host,
+        model,
+        reasoningEffort,
+        recommendedModel,
+        recommendedReasoningEffort,
+        confirmationRequired: true,
+        message: `For best campaign quality, switch to ${recommendedModel} with ${recommendedReasoningEffort} reasoning before lead filtering, message generation, or launch review.`,
+    };
+}

package/dist/tools/prompts.js

@@ -250,7 +250,7 @@ export function getSourceScoutRegistry() {
                 filename: String(agent.codex?.filename || `${agent.name}.toml`),
                 description: String(agent.codex?.description || ""),
                 model: String(agent.codex?.model || "gpt-5.5"),
-                modelReasoningEffort: String(agent.codex?.modelReasoningEffort || "high"),
+                modelReasoningEffort: String(agent.codex?.modelReasoningEffort || "xhigh"),
             },
             claude: {
                 filename: String(agent.claude?.filename || `${agent.name}.md`),
@@ -365,7 +365,7 @@ export function getPostFindLeadsScoutRegistry() {
         usage: {
             codex: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn anything before that question. After the answer, launch only Message Drafting whenever Codex agent-launch policy is satisfied. The registry lookup is not a launch: after get_post_find_leads_scout_registry, immediately invoke Task/spawn_agent or the host background-agent mechanism before loading filter-leads.md, before saving rubrics, and before treating skip-filters as ready for message review. Both choices route through this kickoff; do not let filters_skipped jump straight from filter-choice to message-generation. If filters are chosen, the parent stays on Filter Rules and drafts/saves rubrics with MCP tools while Message Drafting runs in the background. If filters are skipped, move to Messages/message review only after Message Drafting has started or is ready; update_campaign(currentStep=messages) is not proof of launch. Treat YOLO/autonomous mode as campaign-scoped permission for this single post-import worker; do not ask for another permission click in YOLO. If the user has not enabled YOLO and has not explicitly asked for background agents/subagents/parallel agents/delegation/message bg agent in this campaign, ask once before loading the long message prompt in the parent. If permission is granted and the named Message Drafting custom agent is unavailable, spawn a generic gpt-5.5 xhigh Message Drafting background agent with the same lean campaign/table basis. If no background-agent tool is callable, start the same full message branch inline before filter drafting or before skip-filter message review, record it as statusSource parent-thread-fallback, and require the same live context, prompt, assets, and validation gate before message review; do not wait until filters are saved and then call the registry.",
             claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke any Task/Agent before that question. After the answer, invoke only Message Drafting. If filters are chosen, parent drafts/saves rubrics with MCP tools while Message Drafting runs, asks filter approval, then joins Message Drafting. If filters are skipped, invoke only Message Drafting and move to Messages/message review.",
-            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. The only normal background worker is Message Drafting. YOLO/autonomous mode counts as campaign-scoped permission for this single post-import worker; do not ask for another permission click in YOLO. If a named agent is unavailable after permission, use a generic gpt-5.5 xhigh Message Drafting background agent. source work and filter work stay in the parent thread with MCP tools. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. The registry lookup is not a launch: get_post_find_leads_scout_registry only identifies the worker, and Message Drafting counts as started only after Task/spawn_agent or the host background-agent tool is invoked, or after the parent begins the same full message branch inline because no background-agent tool is callable. This launch must happen before loading filter-leads.md, save_rubrics, filter approval, or skip-filter message review; currentStep=messages is not proof of launch. If post-find-leads-message-scout is absent, do not customer-surface install status. Do not silently fall back to parent-thread message drafting; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. If no background-agent tool is callable, start that same full message branch inline before filter drafting or before skip-filter message review, record statusSource parent-thread-fallback / status fallback-active then ready, and require the same live context, prompt, assets, and validation gate before message review; do not report that as a background worker failure. If neither branch nor inline fallback can run, return blocked/retry-needed; do not wait until filters are saved and then call the registry. The Message Drafting handoff must be lean. Do not paste copied row counts, brief hashes, review-batch hashes, full reviewBatchRowIds, broad row data, or local debug artifacts into the spawn prompt. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), and must load every required message asset named by generate-messages Mode 0 through get_subskill_asset before drafting. Reference Asset Loading means loading the required pre-draft reference pack before drafting; return blocked/retry-needed if required assets cannot be loaded; load ai-tells.md because it is never optional. The branch or parent-thread fallback loads the full generate-messages prompt and every referenced asset through get_subskill_asset. After generating/revising the candidate and before returning ready, must load get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) as the final internal validation gate, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not block when filters were chosen but leadScoringRubrics are not yet visible in the branch read; the parent owns save_rubrics and filter approval in parallel, so Message Drafting should return status ready with basisStatus usable_initial when the campaign/list/table and non-empty execution slice match. Do not use any alternate, local-artifact, or examples-only message prompt. User copy feedback, message QA, or rewrite requests before approve-message must be routed back to Message Drafting with the current recommendation, lean campaign/table basis, and latest user text; the parent must not rewrite or QA the template from memory and must not call update_campaign_brief before approve-message. The worker validates internally and returns only templateRecommendation, tokenFillRules, renderedGoodSample, status, approveOrReviseRecommendation, validationStatus, outputAt, outputHash, and blocked/retry detail. Do not render renderedFallbackSample, risk notes, or a qaReceipt on the normal happy path. On the filter path, save_rubrics keeps the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads, show `Filters saved + waiting for message approval`, and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review after Message Drafting has started or is ready and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt, required message assets, and validation gate ran for the current campaign/table execution slice. Do not automatically rerun Message Drafting after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in. Handoff and recommendation output are Markdown with labeled fields, not raw JSON.',
+            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. The only normal background worker is Message Drafting. YOLO/autonomous mode counts as campaign-scoped permission for this single post-import worker; do not ask for another permission click in YOLO. If a named agent is unavailable after permission, use a generic gpt-5.5 xhigh Message Drafting background agent. source work and filter work stay in the parent thread with MCP tools. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. The registry lookup is not a launch: get_post_find_leads_scout_registry only identifies the worker, and Message Drafting counts as started only after Task/spawn_agent or the host background-agent tool is invoked, or after the parent begins the same full message branch inline because no background-agent tool is callable. This launch must happen before loading filter-leads.md, save_rubrics, filter approval, or skip-filter message review; currentStep=messages is not proof of launch. If post-find-leads-message-scout is absent, do not customer-surface install status. Do not silently fall back to parent-thread message drafting; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. If no background-agent tool is callable, start that same full message branch inline before filter drafting or before skip-filter message review, record statusSource parent-thread-fallback / status fallback-active then ready, and require the same live context, prompt, assets, and validation gate before message review; do not report that as a background worker failure. If neither branch nor inline fallback can run, return blocked/retry-needed; do not wait until filters are saved and then call the registry. The Message Drafting handoff must be lean. Do not paste copied row counts, brief hashes, review-batch hashes, full reviewBatchRowIds, broad row data, or local debug artifacts into the spawn prompt. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), and must load every required message asset named by generate-messages Mode 0 through get_subskill_asset before drafting. Reference Asset Loading means loading the required pre-draft reference pack before drafting; return blocked/retry-needed if required assets cannot be loaded; load ai-tells.md because it is never optional. The branch or parent-thread fallback loads the full generate-messages prompt and every referenced asset through get_subskill_asset. After generating/revising the candidate and before returning ready, must load get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) as the final internal validation gate, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not block when filters were chosen but leadScoringRubrics are not yet visible in the branch read; the parent owns save_rubrics and filter approval in parallel, so Message Drafting should return status ready with basisStatus usable_initial when the campaign/list/table and non-empty execution slice match. Do not use any alternate, local-artifact, or examples-only message prompt. User copy feedback, message QA, or rewrite requests before approve-message must be routed back to Message Drafting with the current recommendation, lean campaign/table basis, and latest user text; the parent must not rewrite or QA the template from memory and must not call update_campaign_brief before approve-message. The worker validates internally and returns only templateRecommendation, tokenFillRules, renderedGoodSample, status, approveOrReviseRecommendation, validationStatus, outputAt, outputHash, and blocked/retry detail. Do not render renderedFallbackSample, risk notes, or a qaReceipt on the normal happy path. On the filter path, save_rubrics keeps the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only after saved-filter approval and a ready message recommendation, move to Messages with currentStep=messages and template-approval waiting copy. Wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review after Message Drafting has started or is ready and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt, required message assets, and validation gate ran for the current campaign/table execution slice. Do not automatically rerun Message Drafting after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in. Handoff and recommendation output are Markdown with labeled fields, not raw JSON.',
             prepareMessagesRule: 'Default create-campaign stays on the existing reviewBatchLimit:15 first campaign-table execution slice. Only call start_campaign_message_preparation when the user explicitly asks for more prepared messages or a send count. For "prepare/generate X messages", set targetPreparedMessages:X, omit maxRowsToCheck so the backend calibrates on at least 100 rows, estimates the row budget from observed rubric/pass yield, caps maxRowsToCheck at 2500, and use approvalMode:mark_ready. After the calibration sample settles, the backend adapts later batches up to 250 rows while recalculating yield. Poll get_campaign_message_preparation_status and summarize preparation-job status: checked rows, passed/prepared/approved count, target, estimated row budget remaining, and stop reason. For "approve X messages", use approvalMode:approve but still do not launch. For "schedule X sends", use approvalMode:approve to approve exactly the bounded X-message cohort during preparation, then continue through sender, sequence, and final launch greenlight; final launch must verify that bounded cohort and must not broad approve-all. campaignId is CampaignOffer.id. If the user asks to stop preparation, the target is wrong, or status shows the wrong campaign/table, call cancel_campaign_message_preparation; otherwise do not cancel a healthy prepare run. cancel_campaign_message_preparation cancels the same pending workflow-table cells as the UI Cancel Pending Cells action. Low-level selectors are diagnostics and recovery only for this lane. start_campaign remains forbidden until final launch greenlight.',
         },
     };

package/dist/tools/readiness.js

@@ -186,10 +186,10 @@ export async function waitForLeadListReady(input) {
     if (input.campaignOfferId && (!leadListId || !provider)) {
         const campaign = await api.get(`/api/v2/campaign-offers/${input.campaignOfferId}`);
         if (!leadListId) {
-            leadListId = campaign.selectedLeadListId ?? undefined;
+            leadListId = campaign?.selectedLeadListId ?? undefined;
         }
         if (!provider) {
-            provider = normalizeLeadSourceProvider(campaign.leadSourceProvider);
+            provider = normalizeLeadSourceProvider(campaign?.leadSourceProvider);
         }
     }
     if (!leadListId) {

package/dist/tools/registry.d.ts

@@ -395,6 +395,18 @@ export declare const allTools: ({
                 type: string;
                 description: string;
             };
+            host: {
+                type: string;
+                description: string;
+            };
+            model: {
+                type: string;
+                description: string;
+            };
+            reasoningEffort: {
+                type: string;
+                description: string;
+            };
         };
         additionalProperties: boolean;
     };
@@ -860,6 +872,8 @@ export declare const allTools: ({
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
             senderIds?: undefined;
+            currentStepTransition?: undefined;
+            clearCurrentStepIfMatches?: undefined;
             interactionMode?: undefined;
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
@@ -896,6 +910,8 @@ export declare const allTools: ({
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
             senderIds?: undefined;
+            currentStepTransition?: undefined;
+            clearCurrentStepIfMatches?: undefined;
             interactionMode?: undefined;
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
@@ -932,6 +948,8 @@ export declare const allTools: ({
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
             senderIds?: undefined;
+            currentStepTransition?: undefined;
+            clearCurrentStepIfMatches?: undefined;
             interactionMode?: undefined;
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
@@ -1011,6 +1029,8 @@ export declare const allTools: ({
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
             senderIds?: undefined;
+            currentStepTransition?: undefined;
+            clearCurrentStepIfMatches?: undefined;
             interactionMode?: undefined;
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
@@ -1119,6 +1139,8 @@ export declare const allTools: ({
             leadLimit?: undefined;
             page?: undefined;
             filters?: undefined;
+            currentStepTransition?: undefined;
+            clearCurrentStepIfMatches?: undefined;
             interactionMode?: undefined;
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
@@ -1163,6 +1185,15 @@ export declare const allTools: ({
                 type: string[];
                 description: string;
             };
+            currentStepTransition: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
+            clearCurrentStepIfMatches: {
+                type: string;
+                description: string;
+            };
             watchNarration: {
                 type: string;
                 description: string;
@@ -1270,6 +1301,8 @@ export declare const allTools: ({
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
             senderIds?: undefined;
+            currentStepTransition?: undefined;
+            clearCurrentStepIfMatches?: undefined;
             interactionMode?: undefined;
             enableICPFilters?: undefined;
             useMessagingTemplate?: undefined;
@@ -2290,6 +2323,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -2483,6 +2517,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -2575,6 +2610,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -2739,6 +2775,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -2845,6 +2882,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -2960,6 +2998,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -3064,6 +3103,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -3173,6 +3213,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -3270,6 +3311,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -4159,6 +4201,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -4265,6 +4308,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -5309,6 +5353,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -5384,6 +5429,11 @@ export declare const allTools: ({
                 type: string[];
                 description: string;
             };
+            currentStepTransition: {
+                type: string;
+                enum: string[];
+                description: string;
+            };
             page: {
                 type: string;
                 description: string;
@@ -5606,6 +5656,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             tableId?: undefined;
             campaignName?: undefined;
             keepInSync?: undefined;
@@ -5694,6 +5745,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
@@ -5819,6 +5871,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             headlineICPCriteria?: undefined;
             rubricGuidelines?: undefined;
             mode?: undefined;
@@ -5949,6 +6002,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;
@@ -6043,6 +6097,7 @@ export declare const allTools: ({
             profileUrl?: undefined;
             postUrl?: undefined;
             companyUrl?: undefined;
+            currentStepTransition?: undefined;
             rubricGuidelines?: undefined;
             sourceLeadListId?: undefined;
             targetLeadCount?: undefined;

package/package.json

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

package/skills/building-gtm-tables/SKILL.md

@@ -204,11 +204,14 @@ production behavior.
 - `sellable:add_column`: add one column to an already-committed table when the
   user explicitly asks for a narrow column edit outside this full-table skill.
 - `sellable:list_column_types`: discover visible createable column options, with
-  optional hidden/deprecated rows for existing-table safety.
+  optional hidden/deprecated rows for existing-table safety. The only arguments
+  are `includeHidden` and `includeDeprecated`.
 - `sellable:get_column_schema`: inspect one column option, including default
-  config, create/edit fields, run behavior, and safety verdict.
+  config, editor contract, mutation capabilities, editable fields, full
+  replacement config mode, run behavior, and safety verdict.
 - `sellable:update_column`: update an existing column's name or full replacement
-  config; use `runCells:true` when the edit should reprocess eligible cells.
+  config after checking `sellable:get_column_schema`; use `runCells:true` when
+  the schema says edit reprocessing is supported.
 - `sellable:delete_column`: delete a column through backend cleanup and inspect
   affected dependencies, cancelled cells, and cleanup warnings.
 - `sellable:reorder_columns`: submit the exact full column ID order for a table.

package/skills/building-gtm-tables/references/column-type-catalog.md

@@ -4,8 +4,9 @@ Display names in this catalog are sourced from
 `getColumnTypeConfig(type).displayName`. Do not paraphrase them.
 
 MCP create targets are the visible options returned by
-`sellable:list_column_types()` with `createable:true`. Hidden active/system rows
-and deprecated/load-only aliases may appear when requested for existing-table
+`sellable:list_column_types()`. The tool only accepts `includeHidden` and
+`includeDeprecated` arguments. Hidden active/system rows and
+deprecated/load-only aliases may appear when requested for existing-table
 read/edit/delete safety, but they are not valid `add_column` or
 `commit_blueprint` create targets.
 

package/skills/create-campaign/SKILL.md

@@ -93,8 +93,9 @@ message-template approval before enrichment/filtering or Generate Message cells.
 Filter work stays in the parent thread and must inspect visible campaign rows
 with `get_rows_minimal` / `get_rows` before drafting and saving rubrics; use at
 most one direct `enrich_with_prospeo` sample when row evidence is too thin.
-After filter approval, Filter Leads should show `Filters saved + waiting for
-message approval` until the template is approved.
+After filter approval and once the message review candidate exists, the browser
+should move to Messages with `currentStep: "messages"` and show template
+approval waiting copy until the template is approved.
 The default path stays the existing first campaign-table execution slice:
 review the normal `reviewBatchLimit:15`, approve reviewed draft rows, then move
 to Settings/sequence/final greenlight. Only call
@@ -430,14 +431,14 @@ vs skip filters immediately. Once the user answers, launch only Message Drafting
 from the same campaign/table basis. This kickoff is required for both answers:
 `Use filters` and `Skip filters`. If the user chooses filters, the parent
 thread moves to Filter Rules, loads the filter reference, saves rubrics, then
-asks for filter approval while Message Drafting runs. After approval, move to
-Filter Leads and show `Filters saved + waiting for message approval` while the
-message recommendation is reviewed. If the user skips filters, start Message
-Drafting first, then move to Messages/message review after it has started or
-returned a ready recommendation. `update_campaign({ currentStep: "messages" })`
-is not proof of kickoff. Enrichment/filtering and Generate Message cells wait
-for message approval. AI Generated is an explicit opt-out from the template
-path.
+asks for filter approval while Message Drafting runs. After approval and once
+the message recommendation is ready, move to Messages with
+`currentStep: "messages"` and template-approval waiting copy while the message
+recommendation is reviewed. If the user skips filters, start Message Drafting
+first, then move to Messages/message review after it has started or returned a
+ready recommendation. `update_campaign({ currentStep: "messages" })` is not
+proof of kickoff. Enrichment/filtering and Generate Message cells wait for
+message approval. AI Generated is an explicit opt-out from the template path.
 
 The Message Drafting handoff must stay lean. Include only `campaignId`,
 `workflowTableId`, a concise brief summary, concise source summary/source-use
@@ -969,9 +970,10 @@ updates.
    call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
    so the watched app moves to Filter Rules while the parent drafts/saves
    rubrics and Message Drafting runs.
-   After rubrics save, keep Filter Rules visible for approval; after approval,
-   move to Filter Leads and show `Filters saved + waiting for message approval`
-   until the template is approved.
+   After rubrics save, keep Filter Rules visible for approval; after approval
+   and once Message Drafting has a review candidate, move to Messages with
+   `currentStep: "messages"` and template-approval waiting copy until the
+   template is approved.
    If filters are skipped, launch Message Drafting before moving to
    Messages/message review; updating `currentStep` to `messages` is not proof
    that the background worker started. Queue the bounded campaign-table
@@ -986,8 +988,8 @@ updates.
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after source rows are copied into the campaign table, `create-icp-rubric` as soon
    as filters are chosen and while saved filters await approval,
-   `apply-icp-rubric` after filter approval while message approval is pending,
-   and after message approval while bounded enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
+   `messages` after filter approval while message approval is pending,
+   `apply-icp-rubric` after message approval while bounded enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
    observation state,
    `auto-execute-messaging` after at least one row passes and initial campaign-row
    messages are being generated or reviewed, `awaiting-user-greenlight` only

package/skills/create-campaign-v2/SKILL.md

@@ -41,7 +41,7 @@ active flow. Legacy packet/mint artifacts stay in
 6. Approve the Find Buyers Plan, then approve Start Import.
 7. Materialize the source list and confirm 15 campaign-table rows for setup.
 8. Ask whether to use filters or skip them.
-9. Persist rubrics, approve saved criteria, then move to Filter Leads.
+9. Persist rubrics, approve saved criteria, then move to Messages.
 10. Review and approve/revise the message template.
 11. Sync the approved template into the brief, then queue bounded filtering.
 12. After one generated pass, review it, then hand off to Settings and launch.
@@ -293,11 +293,11 @@ customer-facing source-choice labels.
 
 ## Prospect Setup Workstreams
 
-After `confirm_lead_list` copies source rows and records the review batch, ask the filter-choice question immediately. Do not call `get_post_find_leads_scout_registry`, load filter/message prompts, or spawn Message Drafting before that question. Before the question: short setup summary plus add filters, skip filters, or revise source; no extra watch link.
+After `confirm_lead_list` copies source rows and records the review batch, ask the filter-choice question immediately. Do not call `get_post_find_leads_scout_registry`, load filter/message prompts, or spawn Message Drafting before that question. Before it: short setup summary plus add filters, skip filters, or revise source; no extra watch link.
 
 After filter choice, the only normal background worker is Message Drafting (`post-find-leads-message-scout`). The registry lookup is not a launch. Both choices must run this kickoff: call the registry, then start Message Drafting via `Task`/`spawn_agent` before filter refs, `save_rubrics`, or skip review. YOLO: do not ask for another permission click. If no background tool is callable, run the same full branch inline as `parent-thread-fallback`; otherwise return `blocked` / `retry-needed`. `update_campaign({ currentStep: "messages" })` is not proof of kickoff.
 
-The parent thread is the orchestrator and the filter writer. On the filters path, start Message Drafting, load `references/filter-leads.md`, save rubrics, and ask users to approve saved criteria. Keep `currentStep` on Filter Rules and show `Filters saved + waiting for message approval`; do not queue cells until message approval. Tell the user Message Drafting is preparing the template in the background.
+Parent thread writes filters. On the filters path, start Message Drafting, load `references/filter-leads.md`, save rubrics, and ask users to approve saved criteria. Keep Filter Rules until criteria are approved. Then, once Message Drafting has a review candidate, move to `currentStep: "messages"` with template approval copy; do not queue cells until message approval. Say Message Drafting is preparing the template.
 
 Message Drafting must not wait for `save_rubrics` or require visible
 `leadScoringRubrics` before returning a reusable template. The parent waits for

package/skills/create-campaign-v2/SOUL.md

@@ -308,11 +308,12 @@ tools, and asks for filter approval while Message Drafting runs.
 
 The parent thread is the orchestrator and the filter writer. On the filters path
 it must verify `save_rubrics`, keep the browser on Filter Rules, and ask for
-filter approval. Only after saved filters are approved should it move the
-browser to Filter Leads and join/wait for Message Drafting. The join gate is
-saved-filter approval or a resolved skip-filter choice, plus a message
-recommendation grounded in the same campaign/table basis. Enrichment, filtering,
-and Generate Message cells wait for template approval on the Use Template path.
+filter approval. Only after saved filters are approved and a message review
+candidate exists should it move the browser to Messages with durable
+`currentStep: "messages"`. The join gate is saved-filter approval or a resolved
+skip-filter choice, plus a message recommendation grounded in the same
+campaign/table basis. Enrichment, filtering, and Generate Message cells wait for
+template approval on the Use Template path.
 Message Drafting does not wait for `save_rubrics`: if filters were chosen but
 saved `leadScoringRubrics` are not visible yet, it should still return the
 initial reusable template from the campaign-table execution slice with