@sellable/install 0.1.94 → 0.1.96

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

@@ -80,6 +80,9 @@ 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.
@@ -128,6 +131,13 @@ Quality gates:
   `[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:

package/bin/sellable-install.mjs

@@ -687,7 +687,7 @@ After every \`update_campaign({ campaignId, currentStep })\`, use
 \`get_campaign_navigation_state\` when available as a compact orientation check:
 match the saved campaign state to the expected watch-link step, explain the
 current state in one sentence, and only then continue. Sender selection belongs
-at Settings after message approval and 10-row validation. After message
+at Settings after message approval and 15-row validation. After message
 validation, use Settings to help the user connect or select a LinkedIn sender.
 Explain Slack reply review before launch. After sender selection, attach the
 recommended sequence and move the watched UI to Send. Do not start the campaign
@@ -929,18 +929,28 @@ updates.
    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
    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 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
+   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
+   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
+   review batch, \`messages\` for the Use Template / AI Generated mode choice,
+   \`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.
+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.
-7. Do not ask the user to run another command.
+8. Do not ask the user to run another command.
 
 ## Fallback
 

package/package.json

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

package/skill-templates/create-campaign.md

@@ -71,8 +71,10 @@ Disk artifacts are optional debug/UAT diagnostics; normal customer runs should
 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, and enrichment/message generation waits until rubrics and
-the approved message template are saved on the campaign.
+first review batch. After that, the user chooses whether to use filters or skip,
+then Messages first shows Use Template and AI Generated. The Message Draft
+Builder may work in the background, but template review waits for the filter
+path and an explicit Use Template choice.
 
 ## Opening Turn Contract
 
@@ -145,9 +147,13 @@ registry pattern for the two post-lead branches. The create-campaign-v2 subskill
 calls `get_post_find_leads_scout_registry`, then launches the returned
 filter-leads scout and message-generation scout together when real subagents are
 available and the current session exposes the returned names. Message
-generation must not wait for the filter unless the host cannot run the two
-branches concurrently. If the post-lead agents are absent, the main thread still
-orchestrates the same branches from the compact context with MCP tools/assets.
+generation is the provisional Message Draft Builder: it may start after the
+review batch exists, including while the user is on filter choice, but template
+review cannot start until the user answers filter choice and chooses Use
+Template in Messages. AI Generated is an explicit opt-out that cancels or
+ignores the background template draft. 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
 lines short, use indexed section labels and bullets, and translate internal
@@ -200,7 +206,7 @@ After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
 match the saved campaign state to the expected watch-link step, explain the
 current state in one sentence, and only then continue. Sender selection belongs
-at Settings after message approval and 10-row validation. After message
+at Settings after message approval and 15-row validation. After message
 validation, use Settings to help the user connect or select a LinkedIn sender.
 Explain Slack reply review before launch. After sender selection, attach the
 recommended sequence and move the watched UI to Send. Do not start the campaign
@@ -561,26 +567,31 @@ updates.
    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
    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 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.
+   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.
    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 10-row review batch, `messages` or
-   `auto-execute-messaging` for message work, `validate-sample` for validation,
-   `awaiting-user-greenlight` for the final handoff, `settings` for sender
-   selection, `sequence` after sender attach, and `send` once the recommended
-   sequence is attached. Do not advance the step backward.
+   `filter-choice` after the 15-row review batch, `messages` for the Use
+   Template / AI Generated mode choice, `auto-execute-messaging` for approved
+   message work or the product's AI-generated path, `awaiting-user-greenlight`
+   for the final handoff, `settings` for sender selection, `sequence` after
+   sender attach, and `send` once the recommended sequence is attached.
+   `validate-sample` is recovery/legacy only if reached. 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.