@sellable/install 0.1.233 → 0.1.235

package/bin/sellable-install.mjs

@@ -37,7 +37,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.50";
+const CODEX_PLUGIN_VERSION = "0.1.51";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",

package/package.json

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

package/skill-templates/create-evergreen-campaigns.md

@@ -344,17 +344,29 @@ not a parent-thread summary. The receipt must include:
   `senderIds`, or non-empty `senderIdentityBasis`, plus `identityBasis`.
 - `campaignBriefReceipt`: the CampaignOffer/campaign id, current
   workflowTableId, brief hash or updated-at marker, delivery format, token
-  rules, hard avoids, source-use rules, and first-message template state. If
-  the tool output uses `approvedFirstMessageTemplate`, copy it to canonical
-  `firstMessageTemplate`; if it uses `deliveryFormatIncluded`,
-  `tokenRulesIncluded`, `hardAvoidsIncluded`, or `sourceUseRulesIncluded`, copy
-  those to canonical `deliveryFormat`, `tokenRules`, `hardAvoids`, and
-  `sourceUseRules`. Before the worker exits, the durable JSON must contain the
-  exact canonical leaf keys `briefHash`, `deliveryFormat`, `tokenRules`,
-  `hardAvoids`, `sourceUseRules`, and `firstMessageTemplate` inside
-  `createCampaignStepReceipt.campaignBriefReceipt`; do not leave those only in
+  rules, hard avoids, source-use rules, and lane-appropriate first-message
+  state. Post Engagers lanes require `campaignBriefReceipt.firstMessageTemplate`
+  because they are sender-owned warm lanes. Shared Signal Discovery and Shared
+  Cold Fallback lanes must not set `campaignBriefReceipt.firstMessageTemplate`;
+  instead set `campaignBriefReceipt.firstMessageTemplateState` to the exact
+  no-preset marker
+  `not preset; generate-messages branch selected the final message approach`.
+  If the tool output uses `approvedFirstMessageTemplate`, copy it to canonical
+  `firstMessageTemplate` only for Post Engagers lanes. For shared lanes, treat a
+  raw approved template as a quality issue unless it is only a no-preset or
+  generate-messages state marker. If the tool output uses
+  `deliveryFormatIncluded`, `tokenRulesIncluded`, `hardAvoidsIncluded`, or
+  `sourceUseRulesIncluded`, copy those to canonical `deliveryFormat`,
+  `tokenRules`, `hardAvoids`, and `sourceUseRules`. Before the worker exits, the
+  durable JSON must contain the exact canonical leaf keys `briefHash`,
+  `deliveryFormat`, `tokenRules`, `hardAvoids`, and `sourceUseRules` inside
+  `createCampaignStepReceipt.campaignBriefReceipt`, plus
+  `firstMessageTemplate` only for Post Engagers lanes or
+  `firstMessageTemplateState` for shared lanes; do not leave those only in
   narrative text, `briefIncludes`, `currentApprovedBriefHash`, or other aliases
   for the parent/verifier to infer.
+  Short form: Post Engagers lanes require `campaignBriefReceipt.firstMessageTemplate`.
+  Short form: Shared Signal Discovery and Shared Cold Fallback lanes must not set `campaignBriefReceipt.firstMessageTemplate`.
 - `sourceDecisionReceipt`: selected source/list id, provider, cursor/inventory
   state, import/copy caps, explicit `dedupeDncProviderExclusions:true` or an
   equivalent exclusions object, row ids or row-count evidence (`rowCount`,
@@ -419,9 +431,10 @@ before writing JSON; do not leave only raw objects like
 Self-check shorthand: top-level `planRevision`, `actionId`, `laneKey`, `laneType`, `workspaceId`, and `senderIds` must exist before worker completion.
 Self-check shorthand: `campaignBriefReceipt.briefHash`,
 `campaignBriefReceipt.deliveryFormat`, `campaignBriefReceipt.tokenRules`,
-`campaignBriefReceipt.hardAvoids`, `campaignBriefReceipt.sourceUseRules`, and
-`campaignBriefReceipt.firstMessageTemplate` must exist as exact canonical keys
-before worker completion.
+`campaignBriefReceipt.hardAvoids`, and `campaignBriefReceipt.sourceUseRules`
+must exist as exact canonical keys before worker completion, plus
+`campaignBriefReceipt.firstMessageTemplate` only for Post Engagers lanes and
+`campaignBriefReceipt.firstMessageTemplateState` for shared lanes.
 Self-check shorthand: `sourceDecisionReceipt.dedupeDncProviderExclusions`,
 `sourceDecisionReceipt.sourceLadderReason`, and one of
 `sourceDecisionReceipt.rowCount`, `sourceDecisionReceipt.rowIdsHash`, or
@@ -493,7 +506,8 @@ verification unless the same object also appears inside
       "tokenRules": true,
       "hardAvoids": true,
       "sourceUseRules": true,
-      "firstMessageTemplate": "<template or template state>"
+      "firstMessageTemplate": "<Post Engagers only warm template; omit for shared lanes>",
+      "firstMessageTemplateState": "<Shared lanes only: not preset; generate-messages branch selected the final message approach>"
     },
     "sourceDecisionReceipt": {
       "sourceId": "<source id>",
@@ -646,6 +660,11 @@ such as "my post", "thanks for showing support", "saw you pop up", or any copy
 that implies the sending sender authored the source post or personally received
 the prospect's engagement unless the selected source evidence proves that exact
 sender authored the post.
+Shared lanes must reject generic product-summary samples that explain the
+product in the same broad words for every row. Shared lanes must reject three
+nearly identical samples after stripping the leading name. If either failure
+appears, revise or rerun the packaged create-campaign/generate-messages path
+from the lane worker before writing a success receipt.
 The generated-message cells are not prompt proof: `currentRevisionGeneratedMessages`,
 Generate Message column counts, `messagesCount`, or rendered row previews prove
 only that table cells exist from the current brief/template, not that the
@@ -678,6 +697,15 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
    - Post Engagers lanes: that sender's ID only. Shared lanes: all the senders' IDs.
    - The brief and message direction are lane-specific. Never reuse the Post
      Engagers opening for Shared Cold Fallback.
+   - The warm post-engager first-message template is allowed only for
+     sender-owned Post Engagers lanes. Do not pass the warm template into Shared
+     Signal Discovery or Shared Cold Fallback; those shared lanes must arrive at
+     their copy through Message Drafting and generated-message validation.
+     Short form: warm post-engager first-message template is allowed only for sender-owned Post Engagers lanes.
+     Short form: Do not pass the warm template into Shared Signal Discovery or Shared Cold Fallback.
+     Short form: Shared lanes must reject generic product-summary samples.
+     Short form: Shared lanes must reject three nearly identical samples.
+     Short form: revise or rerun the packaged create-campaign/generate-messages path.
    - **Post Engagers** first-message style: short, casual, references the
      sender-authored post they engaged with, closed question, **no internal
      vocabulary, no pitch, no meeting ask** in message one:
@@ -696,13 +724,20 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      "my post" unless the selected source post was actually authored by the
      sending sender. Do not thank the prospect for showing support, reacting,
      commenting, or popping up unless this is a sender-owned Post Engagers lane
-     with sender-authored source evidence.
+     with sender-authored source evidence. When the shared lane has multiple
+     senders, the copy must be safe for every attached sender to send. Do not
+     use founder-only first person such as "I'm building", "my company", "my
+     team", or "I have a framework" unless every attached sender can credibly
+     say it. Prefer sender-agnostic company/team language such as "we're
+     helping CX teams..." or "at cxconnect.ai, we help..." and one clear
+     problem question.
    - **Shared Cold Fallback** first-message style: cold, direct, and cohesive.
      It must not pretend there was engagement, must not say "saw you pop up",
      and must not use a standalone name line followed by "Hey there" or other
      generic greeting. It should open with a light role/company/problem
-     observation, avoid awkward phrases like "looks like a team where", and ask
-     one clear problem question. This is a single-message
+     observation, avoid awkward phrases like "looks like a team where", avoid
+     founder-only first person unless every attached sender can credibly say it,
+     and ask one clear problem question. This is a single-message
      cold path unless the approved create-campaign message workflow proves a
      better delivery format.
    - Every customer-visible lane must run Message Drafting from the current
@@ -731,7 +766,10 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      already launched and must be reported separately, and `ARCHIVED` must be
      repaired only when the prompt explicitly allows dashboard visibility repair.
    - A full campaign brief exists, including delivery format, token rules,
-     hard avoids, source-use rules, and the approved first-message template.
+     hard avoids, and source-use rules. Post Engagers require an approved warm
+     first-message template. Shared Signal Discovery and Shared Cold Fallback
+     require `firstMessageTemplateState` with the no-preset generate-messages
+     marker instead of a copied first-message template.
    - A source/list decision has been resolved and campaign rows are loaded. If
      there is no approved source or no rows can be copied, report `blocked` with
      the missing source detail; do not call the campaign complete.
@@ -753,10 +791,13 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
      `get_campaign_message_preparation_status`. The generated-message cells are
      not prompt proof; `currentRevisionGeneratedMessages` and row previews are
      only downstream cell evidence. The proof must include
-     `validationResult:"passed"`, a passed quality review, and at least 3
-     reviewed sample messages. For Shared Cold Fallback, reject samples that
-     open with a standalone name followed by "Hey there" or a similarly generic
-     greeting.
+      `validationResult:"passed"`, a passed quality review, and at least 3
+      reviewed sample messages. For Shared Cold Fallback, reject samples that
+      open with a standalone name followed by "Hey there" or a similarly generic
+      greeting. For all shared lanes, reject generic product-summary samples,
+      repeated near-identical samples, and any preserved Post Engagers opener;
+      revise or rerun the packaged create-campaign/generate-messages path before
+      reporting completion.
    - The first review batch exists and at least 3 review rows have generated
      messages from the approved brief. If fewer than 3 usable rows exist, report
      the actual count and why.