@sellable/install 0.1.76 → 0.1.77

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

@@ -20,11 +20,11 @@ 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 Fast Path below. Do not load the full
-   long-form `generate-messages` subskill in the normal path. Load it only when
-   the fast path is missing a needed campaign-specific rule, the user explicitly
-   asks for deep calibration, or the first fast-path draft fails quality gates
-   and no local reference explains how to repair it.
+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:
 
@@ -46,8 +46,8 @@ Do not write or modify:
 
 Process:
 
-1. Run the embedded fast-path workflow in dry mode from the approved brief,
-   lead-review source decision, and `lead-sample.json`.
+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,
@@ -69,7 +69,8 @@ Process:
 Return a concise final status with:
 
 - artifacts written
-- whether embedded fast-path rules were used or the full fallback was needed
+- 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
@@ -78,12 +79,12 @@ Return a concise final status with:
 Quality bar:
 
 - Do not synthesize a lightweight message from general knowledge. The artifact
-  must prove the embedded fast-path workflow ran.
+  must prove the embedded message-review safety-gate workflow ran.
 - 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 Fast Path
+## 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

package/bin/sellable-install.mjs

@@ -843,15 +843,21 @@ updates.
 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-fast-path.md" })\`.
+   \`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.
    Do not synthesize \`message-validation.md\` from the brief, lead review, or
    general knowledge.
-5. Treat message quality as the gate before minting. Do not create a campaign,
-   show a commit gate, or mint anything until \`message-validation.md\` proves
-   the fast-path message workflow ran and \`message-review.md\` recommends
-   \`approve-message\` against the gold-standard rules.
-6. Do not create or mutate the live campaign until the approval gate returns
-   \`approve\`.
+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
+   \`message-validation.md\` proves the message-review safety-gate workflow ran,
+   \`message-review.md\` approves the template, rubrics are saved, and the
+   approved message set is synced into the campaign brief.
+6. Keep \`selectedLeadListId\` as the source list and \`workflowTableId\` as the
+   campaign table. Do not use disk files as the post-mint source of truth.
 7. Do not ask the user to run another command.
 
 ## Fallback

package/package.json

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

package/skill-templates/create-campaign.md

@@ -490,14 +490,17 @@ updates.
 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-fast-path.md" })`.
+   `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.
    Do not synthesize `message-validation.md` from the brief, lead review, or
    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
-   `message-validation.md` proves the fast-path message workflow ran,
+   `message-validation.md` proves the message-review safety-gate workflow ran,
    `message-review.md` approves the template, rubrics are saved, and the
    approved message set is synced into the campaign brief.
 6. Keep `selectedLeadListId` as the source list and `workflowTableId` as the