@sellable/install 0.1.96 → 0.1.97

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

@@ -1,144 +1,87 @@
 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. 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:
-
-1. Read the three required inputs.
-2. Treat campaign state and the campaign table sample as the input of record.
-   Disk files are context/debug aids, not durable state.
-3. Use the embedded Message Review Safety Gate below. Do not load the full
-   long-form `generate-messages` subskill in this `create-campaign-v2` path. If
-   a needed rule is missing or the draft fails quality gates, return
-   `revise-messaging` with the exact failure instead of pulling the long prompt
-   into this worker.
-
-Owned outputs:
-
-- 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:
-
-- `lead-filter.md`
-- `rubric.json`
-- `message-review.md`
-- `approval-packet.md`
-- `brief.md`
-- `lead-review.md`
-- `lead-sample.json`
-
-Process:
-
-1. Run the embedded message-review safety-gate workflow in dry mode from the
-   approved brief, lead-review source decision, and `lead-sample.json`.
-2. Use `lead-sample.json` as the only lead sample source. Do not fetch new
-   prospects or invent richer row signals.
-3. Build proof inventory, token fill rules, token adherence, angle drafts,
-   kill/combine review, skeptical-prospect review, winner gate, and a raw
-   sendable selected winner.
-4. If `lead-filter.md` already exists, cite only basis rows that pass it. If it
-   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 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 embedded message-review safety-gate rules passed or returned
-  `revise-messaging`
-- lead sample basis used
-- proposed template and one sample message
-- selected winner summary
-- whether final reconciliation with `lead-filter.md` is complete or pending
-
-Quality bar:
-
-- Do not synthesize a lightweight message from general knowledge. The artifact
-  must prove the embedded message-review safety-gate workflow ran.
-- There is no generate-message fast mode in this path. The embedded gate is the
-  same campaign-launch quality contract used by the parent-thread compatibility
-  path, not a lower-quality shortcut.
-- Message generation can start before `lead-filter.md`, but message review
-  cannot start until the parent verifies the selected basis rows still pass the
-  final filter.
-
-## Embedded Message Review Safety Gate
-
-Use this campaign-launch subset to produce a truthful first-send message,
-rendered token examples, and a decision without loading the full long-form
-message prompt.
-
-Required `message-validation.md` 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`
-
-Quality gates:
+Your job starts only after the source is approved and the bounded review batch
+exists in the campaign table. Work only on the message-generation branch. Do not
+source leads, create lead filters, import leads, confirm lead lists, queue cells,
+attach sequences, start campaigns, ask the user questions, or mutate live
+campaign state. The main thread owns approval and campaign writes.
 
-- The selected winner is one first outbound send only. No post-accept DM,
-  follow-up, cadence branch, or sequence copy.
-- Explain what the product is and what it does in plain language before asking
-  for a call.
-- Use only proof from the brief, source review, sample, campaign state, or
-  explicit user answers. Unsupported reply-rate, meeting-rate, ROI, revenue,
-  and customer-logo claims are blocked.
-- Include at least one supported `{{token}}` when templating, plus a complete
-  rendered good-fill example and a complete rendered omit/fallback example.
+## Source Of Truth
+
+Use the live campaign inputs supplied by the parent thread:
+
+- `campaignId`
+- `campaignBrief` / campaign brief content model
+- selected source decision and provider state
+- `selectedLeadListId` or selected source list context
+- `workflowTableId`
+- imported review-batch rows from that selected list
+- any already-saved fit/rubric result summaries supplied by the parent
+
+Do not require or hunt for `brief.md`, `lead-review.md`, or `lead-sample.json`.
+Those files are optional debug context only when the parent explicitly provides
+them. Never inspect the product database directly, never run `psql`, and never
+read stale local markdown files to reconstruct campaign state.
+
+## Required First Steps
+
+1. Load the full long-form generate-messages prompt:
+
+   `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.
+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.
+
+## Owned Output
+
+Return the following to the parent thread:
+
+- proposed first-message template using supported `{{...}}` tokens
+- token fill rules and fallbacks
+- one rendered good-fill sample for a plausible passing review-batch row
+- one omit/fallback sample when the row signal is not safe
+- pass/fail notes against the generate-messages quality gates
+
+Write `message-validation.md`, `message-prep.md`, or
+`message-candidate-drafts.md` only when the parent explicitly asks for debug
+artifacts. Normal live campaign runs can return the same content directly.
+
+## Hard Rules
+
+- Do not call product Generate Message cells. This worker drafts the template
+  recommendation only.
+- Do not call `update_campaign_brief`; the main thread writes the approved
+  template after user approval.
+- Do not overwrite an existing approved message/template.
+- Do not use unsupported reply-rate, meeting-rate, ROI, revenue, or
+  customer-logo claims.
 - 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]`, or `[generated]`.
-- Optional row-specific personalization must be grounded in a row field or
-  omitted entirely.
 - 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.
-- Subjects 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`.
+  default hook. Only refer to 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.
+- The selected winner is one first outbound send only. No post-accept DM,
+  follow-up, cadence branch, sequence copy, or launch copy.
+
+## Final Response
+
+Return a concise status with:
+
+- prompt basis loaded: `generate-messages`
+- live campaign basis used
+- proposed template
+- token fill rules/fallbacks
+- one rendered passing-row sample
+- one rendered omit/fallback sample
+- quality-gate pass/fail summary
+- whether final template review is ready or needs revision

package/agents/registry.json

@@ -46,6 +46,7 @@
           "Glob",
           "mcp__sellable__get_provider_prompt",
           "mcp__sellable__search_signals",
+          "mcp__sellable__select_promising_posts",
           "mcp__sellable__fetch_post_engagers"
         ]
       }
@@ -205,14 +206,20 @@
       "displayName": "Message Draft Builder",
       "target": "generate-messages",
       "inputs": [
-        "brief.md",
-        "lead-review.md",
-        "lead-sample.json"
+        "campaignId",
+        "campaignBrief",
+        "selected source state",
+        "selectedLeadListId",
+        "workflowTableId",
+        "imported review-batch rows"
       ],
       "producesArtifacts": [
-        "message-validation.md"
+        "template recommendation",
+        "token fill rules",
+        "rendered sample"
       ],
       "optionalProducesArtifacts": [
+        "message-validation.md",
         "message-prep.md",
         "message-candidate-drafts.md"
       ],

package/bin/sellable-install.mjs

@@ -923,24 +923,25 @@ updates.
    asset loader so they share the same config.
 3. Follow that prompt and workflow config exactly.
 4. For message generation, use the \`post-find-leads-message-scout\` agent when
-   available; its prompt carries the campaign-launch message rules. In the
-   parent-thread fallback, load
-   \`mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-safety-gate.md" })\`.
-   Do not load the full long-form \`generate-messages\` subskill in this
-   create-campaign path; if the safety gate cannot safely approve the draft, route
-   to revise messaging with the concrete failure.
-   This compatibility path is not a generate-message fast mode.
-   Do not synthesize \`message-validation.md\` from the brief, lead review, or
+   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,
+   inspect the database directly, or synthesize \`message-validation.md\` 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
    queue workflow cells, attach a sequence, or start until filter choice is
    resolved, Messages has shown Use Template / AI Generated, template/token
-   rules are approved when Use Template is chosen, rubrics are saved when
-   filters are enabled, and the approved message set is synced into the campaign
-   brief. Product Generate Message cells must not run from the background
-   template path before that template/token approval. AI Generated uses the
+   rules are approved when Use Template is chosen, rubrics are saved and the
+   bounded review-batch \`enrichCellId\` cells have been queued when filters are
+   enabled, and the approved message set is synced into the campaign brief.
+   Product Generate Message cells must not run from the background template
+   path before that template/token approval. AI Generated uses the
    product's AI-generated path and cancels or ignores the background template
    draft.
 6. The main thread owns watch navigation: use \`filter-choice\` after the 15-row

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.96",
+  "version": "0.1.97",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -561,24 +561,25 @@ updates.
    asset loader so they share the same config.
 3. Follow that prompt and workflow config exactly.
 4. For message generation, use the `post-find-leads-message-scout` agent when
-   available; its prompt carries the campaign-launch message rules. In the
-   parent-thread fallback, load
-   `mcp__sellable__get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/message-review-safety-gate.md" })`.
-   Do not load the full long-form `generate-messages` subskill in this
-   create-campaign path; if the safety gate cannot safely approve the draft,
-   route to revise messaging with the concrete failure.
-   This compatibility path is not a generate-message fast mode.
-   Do not synthesize `message-validation.md` from the brief, lead review, or
+   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,
+   inspect the database directly, or synthesize `message-validation.md` 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
    queue workflow cells, attach a sequence, or start until the filter choice is
    resolved, Messages has shown Use Template / AI Generated, template/token
-   rules are approved when Use Template is chosen, rubrics are saved when
-   filters are enabled, and the approved message set is synced into the campaign
-   brief. Product Generate Message cells must not run from the background
-   template path before that template/token approval.
+   rules are approved when Use Template is chosen, rubrics are saved and the
+   bounded review-batch `enrichCellId` cells have been queued when filters are
+   enabled, and the approved message set is synced into the campaign brief.
+   Product Generate Message cells must not run from the background template
+   path before that template/token approval.
    Do not ask the user to approve the brief before shell creation unless they
    explicitly requested a no-write draft; the shell itself is the review surface.
 6. The main thread owns watch navigation. Call