@sellable/install 0.1.112 → 0.1.114

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/bin/sellable-install.mjs

@@ -978,41 +978,48 @@ 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
    load post-lead registries/prompts before asking add filters vs skip filters.
    Once the user answers, launch the message scout from the same campaign/table
    basis. If filters are approved, also launch the filter scout. Do not queue
-   workflow cells, attach a sequence, or start until filter choice is resolved,
-   rubrics are saved when filters are enabled, template/token rules are approved
-   on the default Use Template path, and the approved message set is synced into
-   the campaign brief. When filters are approved, immediately
+   workflow cells, attach a sequence, or start until filter choice is resolved
+   and rubrics are saved when filters are enabled. Template/token rules on the
+   default Use Template path gate only Generate Message cells, sender setup,
+   sequence attach, and launch. When filters are approved, immediately
    call \`mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })\`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, move the watched app to \`apply-icp-rubric\` / Filter
    Leads and say the fit rules are saved; the background message scout is
    preparing the message recommendation and approval comes next while the
-   browser stays on Filter Leads. If filters are skipped, move to
-   Messages/message review and wait for message approval there. After approval,
-   queue the bounded review-batch \`enrichCellId\` cells to kick off
-   enrichment/filtering.
+   browser stays on Filter Leads. Queue the bounded review-batch
+   \`enrichCellId\` cells to kick off enrichment/filtering after rubrics are
+   saved, without waiting for template approval. If filters are skipped, move to
+   Messages/message review and wait for message approval before Settings.
    Product Generate Message cells must not run before that template/token
-   approval. AI Generated uses the product's AI-generated path and skips the
-   template path.
-6. The main thread owns watch navigation: use \`filter-choice\` after the review
-   batch, \`create-icp-rubric\` as soon as filters are approved,
-   \`apply-icp-rubric\` after rubrics save on the filter path, \`messages\` for
-   skipped filters and message-template review,
-   \`auto-execute-messaging\` for approved message work or the product's
-   AI-generated path, and \`awaiting-user-greenlight\` for the final handoff.
-   \`validate-sample\` is recovery/legacy only if reached.
+   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
+   \`mcp__sellable__update_campaign({ campaignId, currentStep })\` before major
+   visible work so the user can watch progress in the app: \`create-offer\` for
+   the brief, \`pick-provider\` or the selected provider step while sourcing,
+   \`filter-choice\` after the review batch, \`create-icp-rubric\` as soon
+   as filters are approved, \`apply-icp-rubric\` after rubrics save while bounded
+   enrichment/filter scoring runs on Filter Leads, \`validate-sample\` only as a
+   recovery/legacy observation state,
+   \`auto-execute-messaging\` after at least one row passes and review-batch
+   messages are being generated or reviewed, \`awaiting-user-greenlight\` only
+   after generated review-batch messages are approved, \`settings\` for sender
+   selection, \`sequence\` after sender attach, and \`send\` once the recommended
+   sequence is attached. Do not advance the step backward.
 7. Keep \`selectedLeadListId\` as the source list and \`workflowTableId\` as the
    campaign table. Do not use disk files as the post-mint source of truth.
 8. Do not ask the user to run another command.

package/package.json

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

package/skill-templates/create-campaign.md

@@ -72,10 +72,10 @@ not create, link, or surface local draft files unless the user explicitly asks
 for them. Resume, gating, and handoff read campaign state first. The
 watchable campaign exists after the short brief; lead import is bounded to the
 first review batch. After that, the user chooses whether to use filters or skip.
-When filters are chosen, save rubrics, then pause before queueing enrichment or
-filtering: tell the user the fit rules are saved, the message template needs
-approval next, and enrichment/filtering will start after that approval. Use
-Template is the default message path; AI Generated is only an explicit opt-out.
+When filters are chosen, save rubrics, then queue enrichment/filtering only from
+workflow-table run conditions. Message approval gates Generate Message cells,
+sender setup, sequence attach, and launch, not enrichment/filtering. Use Template
+is the default message path; AI Generated is only an explicit opt-out.
 
 ## Opening Turn Contract
 
@@ -224,9 +224,10 @@ vs skip filters immediately. Once the user answers, launch the message scout
 from the same campaign/table basis. If the user chooses filters, also launch the
 filter-leads scout, move to Filter Rules, save rubrics, then keep the browser on
 Filter Leads while the message recommendation is reviewed. If the user skips
-filters, move to Messages/message review. Workflow cell execution still waits
-for filter and template approval. AI Generated is an explicit opt-out from the
-template path. If the post-lead agents are absent, the main thread still
+filters, move to Messages/message review. Enrichment/filtering cell execution
+runs from saved rubrics and workflow-table run conditions; template approval
+only gates Generate Message cells and send setup. AI Generated is an explicit
+opt-out from the template path. If the post-lead agents are absent, the main thread still
 orchestrates the same branches from the compact context with MCP tools/assets.
 
 Use rendered Markdown for user review surfaces, not fenced code blocks. Keep
@@ -640,30 +641,30 @@ 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
    queue workflow cells, attach a sequence, or start until the filter choice is
-   resolved, rubrics are saved when filters are enabled, template/token rules
-   are approved on the default Use Template path, and the approved message set
-   is synced into the campaign brief. When filters are approved, immediately
+   resolved and rubrics are saved when filters are enabled. Template/token rules
+   on the default Use Template path gate only Generate Message cells, sender
+   setup, sequence attach, and launch. When filters are approved, immediately
    call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
    so the watched app moves to Filter Rules while rubrics are drafted/saved.
    After rubrics save, move the watched app to `apply-icp-rubric` / Filter
    Leads and say the fit rules are saved; the background message scout is
-   preparing the message recommendation and approval comes next while the
-   browser stays on Filter Leads. If filters are skipped, move the watched app to
-   Messages/message review and wait for message approval there. After approval,
-   save the template to the campaign brief, then queue the bounded review-batch
-   `enrichCellId` cells to kick off enrichment/filtering. Move to Messages only
-   after at least one review row passes and Generate Message cells are running or
-   ready.
+   preparing the message recommendation while the bounded Filter Leads batch can
+   be queued from run conditions. If filters are skipped, move the watched app to
+   Messages/message review and wait for message approval before Settings. Queue
+   the bounded review-batch `enrichCellId` cells to kick off
+   enrichment/filtering after rubrics are saved, without waiting for template
+   approval. Move to Messages only after at least one review row passes and
+   Generate Message cells are running or ready.
    Product Generate Message cells must not run before that template/token
    approval.
    Do not ask the user to approve the brief before shell creation unless they
@@ -673,9 +674,9 @@ updates.
    visible work so the user can watch progress in the app: `create-offer` for
    the brief, `pick-provider` or the selected provider step while sourcing,
    `filter-choice` after the review batch, `create-icp-rubric` as soon
-   as filters are approved, `apply-icp-rubric` after rubrics save and while
-   waiting for message-template approval, `validate-sample` while the approved
-   template unlocks bounded enrichment/filter scoring on Filter Leads,
+   as filters are approved, `apply-icp-rubric` after rubrics save while bounded
+   enrichment/filter scoring runs on Filter Leads, `validate-sample` only as a
+   recovery/legacy observation state,
    `auto-execute-messaging` after at least one row passes and review-batch
    messages are being generated or reviewed, `awaiting-user-greenlight` only
    after generated review-batch messages are approved, `settings` for sender