@sellable/mcp 0.1.150 → 0.1.151

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

@@ -40,8 +40,8 @@ the branch input.
    `get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
    until `hasMore` is false.
 
-2. Use that prompt as the drafting contract. The create-campaign safety gate may
-   be used as an approval checklist, but it does not replace the long prompt.
+2. Use that prompt as the drafting contract. Do not use create-campaign
+   safety/checklist instructions as a substitute for the full prompt.
 3. Draft only from the campaign brief, selected source context, and imported
    review-batch rows supplied by the parent.
 4. Keep the work provisional until the user chooses `Use Template` in Messages.

package/dist/tools/prompts.d.ts

@@ -134,6 +134,7 @@ export interface PostFindLeadsScoutRegistryResponse {
         forbiddenStarts: string[];
         runtimeProofTransport: string;
         runtimeProofRequiredFields: string[];
+        promptRequired?: string;
         basisFields: string[];
         compactOutputFields: string[];
         reusePolicy?: string;

package/dist/tools/prompts.js

@@ -315,6 +315,7 @@ export function getPostFindLeadsScoutRegistry() {
                 "basis.workflowTableId",
                 "basis.reviewBatchRowHash or basis.reviewBatchRowIds",
             ],
+            promptRequired: 'get_subskill_prompt({ subskillName: "generate-messages", offset, limit }) until hasMore=false',
             basisFields: [
                 "campaign revision or updatedAt",
                 "brief hash",
@@ -341,7 +342,7 @@ export function getPostFindLeadsScoutRegistry() {
         usage: {
             codex: "After confirm_lead_list imports a non-empty bounded review batch and get_rows_minimal proves rows for workflowTableId, ask the filter-choice question immediately. Do not spawn returned post-lead scout names before that question. Once the user answers, spawn Message Draft Builder from the same campaign/table basis. If the user chooses filters, also spawn Lead Fit Builder, move to Filter Rules, save rubrics, then keep the browser on Filter Leads while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
             claude: "After confirm_lead_list imports a non-empty bounded review batch and get_rows_minimal proves rows for workflowTableId, ask the filter-choice question immediately. Do not invoke returned post-lead Task/Agent names before that question. Once the user answers, invoke Message Draft Builder from the same campaign/table basis. If the user chooses filters, also invoke Lead Fit Builder, move to Filter Rules, save rubrics, then keep the browser on Filter Leads while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
-            parentThreadRule: "Named agents are optional acceleration. If they are absent, do not customer-surface install status; the main thread still orchestrates filter and message branches from CampaignOffer state, selected source state, workflowTableId, and imported review-batch rows. 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, filter references, or the full generate-messages prompt before it. Message drafting starts after the filter-choice answer, must load the full generate-messages prompt, must read live campaign/review-batch state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. On the filter path, keep the browser on Filter Rules then Filter Leads while the background message agent prepares the template; enrichment/filtering/Generate Message cells wait for template approval. On the skip path, move to Messages/message review and wait for template approval before enrichment. Template approval in the parent thread uses the create-campaign-v2 message-review safety gate; do not load the full generate-messages prompt for approval-only review. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.",
+            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. If it is absent, do not customer-surface install status; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and imported review-batch rows. 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, filter references, or the full generate-messages prompt before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages", offset, limit }) until hasMore=false, must read live campaign/review-batch state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. On the filter path, keep the browser on Filter Rules then Filter Leads while the background message agent prepares the template; enrichment/filtering/Generate Message cells wait for template approval. On the skip path, move to Messages/message review and wait for template approval before enrichment. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the full generate-messages prompt ran for the current campaign/table/review batch. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.',
         },
     };
 }

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -640,12 +640,12 @@ updates.
    available. The worker and parent-thread fallback must load the full
    long-form `generate-messages` prompt with
    `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages", offset, limit })`
-   until `hasMore=false`. The create-campaign message-review safety gate is a
-   supplemental approval checklist, not a replacement for the long prompt. Use
-   campaign state, campaign brief content, selected source state, and imported
-   review-batch rows as the source of truth; do not read stale local markdown
-   such as `message-validation.md`, inspect the database directly, or synthesize
-   local validation artifacts from general knowledge.
+   until `hasMore=false`. Message review requires Message Draft Builder output:
+   do not draft from a checklist, local markdown artifact, or parent-thread
+   intuition. Use campaign state, campaign brief content, selected source state, and
+   imported review-batch rows as the source of truth; do not read stale local
+   markdown such as `message-validation.md`, inspect the database directly, or
+   synthesize local validation artifacts from general knowledge.
 5. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Import only the first
    bounded review batch after the source is attached to the campaign; do not

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

@@ -281,23 +281,18 @@ Lead Fit Builder persists production rubrics with `save_rubrics` when filters
 are enabled. It must not require `brief.md`, `lead-review.md`, or
 `lead-sample.json`.
 
-Message Draft Builder is `post-find-leads-message-scout`. It must load the full
-message prompt:
+Run `post-find-leads-message-scout` as the background Message Draft Builder
+whenever the host exposes it. It must load:
 
 ```text
 get_subskill_prompt({ subskillName: "generate-messages", offset, limit }) until hasMore=false
 ```
 
-It may also load the supplemental approval checklist:
-
-```text
-get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-safety-gate.md" })
-```
-
-Do not load the full `generate-messages` prompt in the create-campaign parent
-thread unless you are executing the parent-thread fallback for the actual
-message-draft branch. Parent-thread template approval uses only the compact
-message-review safety gate.
+No shortcut message instructions are valid. If the host cannot launch the
+agent, the parent fallback must run the same full prompt from live campaign
+state before drafting. Do not render message review until
+`messageDraftRecommendation` proves current campaign/table/review-batch
+`generate-messages` basis.
 
 ## Hard Gates
 
@@ -320,7 +315,6 @@ Load references only when needed:
 - `references/watch-guide-narration.md` for watched-step narration.
 - `references/lead-validation-preview.md` for legacy/debug preview shapes.
 - `references/filter-leads.md` for rubric design and `save_rubrics` rules.
-- `references/message-review-safety-gate.md` for final message approval checks.
 - `references/step-13-import-leads.md` before review-batch import.
 - `references/sample-validation-loop.md` before review-batch validation.
 - `references/final-handoff-contract.md` for Settings, sender, sequence, and

package/skills/create-campaign-v2/core/flow.v2.json

@@ -66,9 +66,7 @@
     "filter": [
       "references/filter-leads.md"
     ],
-    "message": [
-      "references/message-review-safety-gate.md"
-    ],
+    "message": [],
     "tail": [
       "references/sample-validation-loop.md",
       "references/step-15-re-cascade.md",
@@ -890,8 +888,8 @@
           "action": "run_or_reconcile_message_draft_builder",
           "target": "post-find-leads-message-scout",
           "toolCallRequiredBeforeDraft": [
-            "get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) until hasMore=false",
-            "parent approval uses references/message-review-safety-gate.md only"
+            "run background post-find-leads-message-scout when available",
+            "get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) until hasMore=false"
           ],
           "stateSource": "campaignBrief, source, selectedLeadListId, workflowTableId, review-batch row ids/hash",
           "outputState": "messageDraftRecommendation"
@@ -905,7 +903,6 @@
       ],
       "allowedTools": [
         "get_subskill_prompt",
-        "get_subskill_asset",
         "get_campaign",
         "get_rows_minimal",
         "update_campaign",
@@ -913,9 +910,9 @@
         "request_user_input"
       ],
       "toolRules": [
-        "Message Draft Builder loads full get_subskill_prompt({ subskillName: \"generate-messages\" }) from live state. Parent approval uses message-review-safety-gate only.",
+        "Message Draft Builder must run as the background post-find-leads-message-scout when the host exposes it. If the host cannot launch the agent, the parent-thread fallback must execute the same full get_subskill_prompt({ subskillName: \"generate-messages\" }) from live state before drafting.",
         "Do not use brief.md, lead-review.md, or lead-sample.json as required live state; those files are optional debug context only.",
-        "The compact messageDraftRecommendation must return templateRecommendation, tokenFillRules, renderedSample, concerns, status, basisToken, outputAt, outputHash, and error or retry detail.",
+        "The messageDraftRecommendation must return templateRecommendation, tokenFillRules, renderedSample, concerns, status, basisToken, outputAt, outputHash, and error or retry detail.",
         "If campaign/source/table/review-batch basis does not match, classify the output stale or blocked."
       ],
       "doNotAllow": [
@@ -1005,7 +1002,6 @@
       "allowedTools": [
         "AskUserQuestion",
         "request_user_input",
-        "get_subskill_asset",
         "update_campaign_brief",
         "update_campaign",
         "get_rows_minimal",

package/skills/create-campaign-v2/references/approval-gate-framing.md

@@ -33,14 +33,13 @@ Before showing the commit gate, the draft directory must contain all of:
 - `message-validation.md`
 - `approval-packet.md`
 
-The current run must also have retrieved message-generation rules before
-`message-validation.md`, `approval-packet.md`, or the commit gate is written. In
-`create-campaign-v2`, use the compact
-`references/message-review-safety-gate.md` asset or the embedded
-`post-find-leads-message-scout` prompt. Do not load the full long-form
-`generate-messages` subskill for the hosted campaign launch path. If the message
-template was written directly from memory or planning artifacts, do not show the
-commit gate; route back to message generation.
+The current run must also have retrieved the full message-generation rules
+before `message-validation.md`, `approval-packet.md`, or the commit gate is
+written. In `create-campaign-v2`, use the embedded
+`post-find-leads-message-scout` prompt or load the full long-form
+`generate-messages` subskill. If the message template was written directly from
+memory, checklist instructions, or planning artifacts, do not show the commit
+gate; route back to message generation.
 
 `rubric.json` is optional but strongly preferred — when missing, derive it from
 `lead-filter.md` in the atomic mint step.

package/skills/create-campaign-v2/references/message-review-safety-gate.md

@@ -1,162 +0,0 @@
-# Message Review Safety Gate
-
-Use this reference for `create-campaign-v2` message review only in two cases:
-when these rules are embedded inside the `post-find-leads-message-scout` agent
-prompt, or when the host cannot launch that agent and the parent thread needs a
-self-contained safety gate. It is the campaign-launch subset of
-`generate-messages`: enough to prove a truthful first-send message, rendered
-token examples, and an approval decision without loading the full long-form
-message-generation prompt into the main Claude/Codex thread.
-
-In a normal installed Claude/Codex session, the message scout owns these rules.
-The parent-thread asset is a compatibility safety path, not a fast-mode prompt
-or a shortcut. Do not load the full `generate-messages` subskill in this flow. If
-the safety gate is missing a needed campaign-specific rule or the draft fails
-quality gates, stop at `revise-messaging` with the exact missing rule/failure
-instead of pulling the long prompt into the main thread.
-
-## Required Workflow
-
-1. Read the live campaign basis: campaign id, campaign revision or
-   `campaignUpdatedAt`, campaign brief content, selected source decision,
-   selected lead list/source state, `workflowTableId`, imported review-batch
-   row ids/hash, and any saved rubric/filter summary supplied by the parent.
-2. Pick 2-3 sample rows from the imported review-batch rows, preferring rows
-   that pass the saved rubrics or are likely to pass. Do not invent new rows.
-3. Build the message from the approved campaign brief, selected source context,
-   sampled rows, and explicit user answers. Use only proof that appears in that
-   live basis. Unsupported reply-rate, meeting-rate, ROI, revenue, and
-   customer-logo claims are blocked.
-4. Return a compact message recommendation to the parent thread. Do not write
-   local markdown/json artifacts in normal customer runs; emit debug artifacts
-   only when the parent explicitly asks for debug/UAT output.
-5. Render the customer-facing message review in chat before asking for approval.
-   Keep chat lightweight: show the tokenized template and one strong rendered
-   good-fill example only. Do not print the token notes table, omit/fallback
-   example, or bad-fill analysis in chat unless the user explicitly asks.
-   After approval, the parent persists template, token rules, fallback guidance,
-   and bad-fill avoidance notes into campaign state with `update_campaign_brief`.
-6. Ask exactly `approve-message` or `revise-messaging`. Do not import, queue,
-   attach sequence, or start before `approve-message`.
-
-## Required Message Recommendation Sections
-
-- `Status`
-- `Mode`
-- `Lead Sample Basis`
-- `Strongest Reply Reason`
-- `Campaign Element Pool`
-- `Gold Standard Strategy Map`
-- `Current Campaign Translation`
-- `Token Fill Rules`
-- `Token Adherence Table`
-- `Angle Drafts`
-- `Kill / Combine Review`
-- `Finalizer Pass`
-- `Gold-Standard Quality Gate`
-- `Skeptical Prospect Review`
-- `Winner Gate`
-- `Selected Winner`
-- `Findings`
-- `Recommendation`
-
-Keep this recommendation concise. It should prove the reasoning path, not
-reproduce the full framework.
-
-## Message Quality Gates
-
-- The selected winner must be one first outbound send only. No post-accept DM,
-  follow-up, cadence branch, or sequence copy.
-- The message must explain what the product is and what it does in plain
-  language before asking for a call.
-- The message must use a truthful buyer-side reply reason, not just sender
-  biography.
-- If using a template, include at least one supported `{{token}}` and show a
-  complete rendered good-fill example and complete rendered omit/fallback
-  example.
-- Do not use internal tokens such as `{{profile_signal}}` in customer-facing
-  copy.
-- Do not put bracketed instructions in the message body, such as `[ROW_BRIDGE]`,
-  `[insert]`, `[generated]`, or any instruction for a later model to fill.
-- Optional row-specific personalization must be grounded in a row field or
-  omitted entirely. Never use generic filler like "your work" or "your team."
-- Engagement-source personalization is a special case, not the default opener.
-  Do not write `saw you {{engagement_context}} on {{post_context}}`, `saw you
-reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
-  default hook. Only refer to the prospect's engagement when the line is
-  self-aware and low-certainty, for example `not sure if this is too specific,
-but the [topic] thread felt close enough to send`. Otherwise omit the
-  engagement signal and use role/company/problem context.
-- Subject lines should be short, buyer-relevant, and specific. Avoid
-  `quick question`, `demo`, `founder call`, sender names, and generic `outbound`.
-- If the message is plausible but not ready to send, set
-  `Recommendation: revise-messaging`.
-
-## Internal Message Recommendation
-
-The message scout or parent safety gate should still produce complete internal
-review data: token-fill rules, one rendered omit/fallback example, and bad-fill
-avoidance notes. This data is for campaign-brief persistence and safety checks,
-not for the default chat approval packet.
-
-## Customer-Facing Message Review
-
-Render this in chat before asking. Use Markdown structure so the approval target
-is visually scannable and low-overhead:
-
-````markdown
-Status: message-review
-
-## Message Template
-
-**Subject**
-
-```text
-{{tokenized_subject}}
-```
-
-**Body**
-
-```text
-{{tokenized_message_body}}
-```
-
-## Rendered Example
-
-### Example
-
-Good token fill:
-
-```text
-Subject: ...
-
-Hey First,
-
-...
-```
-
-## Recommendation
-
-**My take:** ...
-
-**Suggested adjustment:** ...
-
-**Question:** approve-message or revise-messaging?
-
-**Recommendation:** approve-message
-````
-
-Formatting requirements:
-
-- Put the tokenized template and rendered example in fenced `text` blocks
-  so chat gives them a distinct background.
-- The chat example must contain a complete rendered subject + body, not a
-  bullet list of token names or a single bridge-line fragment.
-- Do not show `Good omit / fallback`, `Bad fill to avoid`, or `Token Notes` in
-  the default chat approval packet. Keep those in the internal recommendation
-  and persist them to the campaign brief after approval.
-- Keep reasoning outside the code blocks so the blocks are easy to inspect and
-  approve.
-
-`My take` and `Suggested adjustment` must be specific. The adjustment can be
-"approve as-is, or revise once to X if you want Y"; it must not be empty.