@sellable/install 0.1.234 → 0.1.236

package/package.json

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

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

@@ -139,6 +139,10 @@ campaigns are not reusable evergreen targets. Only pass an archived
 campaign/table as an explicit binding when the user supplied those exact ids and
 explicitly allowed dashboard visibility repair; otherwise ignore archived
 matches for execution and let the create packet proceed.
+Do not call `get_campaign` on archived waterfall bindings to overrule a create packet.
+Do not re-plan with explicit bindings for archived waterfall slots after an unbound create plan.
+Archived waterfall slot readbacks are diagnostic only; they are not a consistency check that can replace the immutable create packet.
+If an archived waterfall binding makes the agent unwilling to execute the create packet, stop with `blocked: archived_binding_plan_conflict` instead of repairing or reusing the archived campaign/table.
 
 Use `selectedSenderIds` only as a legacy shorthand when the same senders should
 get sender-owned Post Engagers lanes and attach to shared lanes. When the scopes
@@ -344,17 +348,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 +435,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 +510,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 +664,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
@@ -672,12 +695,38 @@ Parent-thread handwritten copy or setting `currentStep` is not proof.
 </command_backed_workflow>
 
 <objective>
-1. **Inventory first**: `get_campaigns` + `list_tables` + `get_campaign_waterfall` in the active workspace. Treat `list_tables` and the managed waterfall as authoritative for older managed slots; `get_campaigns` is a recent campaign page and may miss canonical evergreen lanes. Match existing campaigns/tables/waterfall slots to the plan by name (case-insensitive, ignore suffixes like "(Copy)") and stored slot identity. `list_tables.campaignStatus` and `list_tables.dashboardBucket` are part of the identity check: a matching `ARCHIVED` table/campaign is not a plain `REUSE`. If it is the canonical prod slot and the invocation explicitly allows dashboard visibility repair, repair it to `PAUSED`; otherwise mark it `flagged`/`blocked` and do not create a duplicate. A matching non-archived campaign/table/waterfall slot = REUSE; record it and move on. Never create a second campaign for a slot that already has one in any of those inventories.
+1. **Inventory first, then obey the setup plan**: `get_campaigns` +
+   `list_tables` + `get_campaign_waterfall` in the active workspace. Treat
+   `list_tables` and the managed waterfall as authoritative for orientation
+   before the command-backed plan; `get_campaigns` is a recent campaign page and
+   may miss canonical evergreen lanes. Match existing campaigns/tables/waterfall
+   slots to the plan by name (case-insensitive, ignore suffixes like "(Copy)")
+   and stored slot identity. `list_tables.campaignStatus` and
+   `list_tables.dashboardBucket` are part of the identity check: a matching
+   `ARCHIVED` table/campaign is not a plain `REUSE`. If it is the canonical prod
+   slot and the invocation explicitly allows dashboard visibility repair, repair
+   it to `PAUSED`; otherwise treat it as archived inventory only. After
+   `setup_evergreen_campaigns({ mode:"plan" })` returns, that plan is
+   authoritative: a lane packet with `intent:"create"` must stay a create packet,
+   even when archived waterfall entries or `get_campaign` readbacks prove an old
+   CampaignOffer still exists. A matching non-archived campaign/table/waterfall
+   slot may be reused only when the command-backed plan returns a reuse packet
+   or the user supplied exact current ids. Never create a second campaign for a
+   non-archived slot that the plan selected for reuse.
 2. **Create only the missing slots** through the full `$sellable:create-campaign`
    workflow path for each lane, using the lane packet as the setup basis:
    - 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:
@@ -738,7 +787,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.
@@ -760,10 +812,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.