@sellable/install 0.1.235 → 0.1.236

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.235",
+  "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
@@ -691,7 +695,24 @@ 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.