@sellable/install 0.1.229 → 0.1.231

package/bin/sellable-install.mjs

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

package/package.json

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

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

@@ -24,10 +24,19 @@ run without user input, or similar, run in **automation mode**:
 - Reconcile structure and record any template/config polish as `created`,
   `reused`, `repaired`, `flagged`, or `blocked`.
 - Choose the automation depth from the invoking prompt:
+  - Sparse `--yolo` create/repair invocations default to customer-visible completion:
+    when the user says run/create/repair/setup `$sellable:create-evergreen-campaigns`,
+    create evergreen campaigns, or similar without saying heartbeat/structure-only,
+    set `depth:"customer_visible"`. Customers usually expect usable campaigns,
+    not empty shells.
   - **Structure-only reconcile** is for heartbeat prompts that only say to
-    ensure slots exist. It may create/reuse shells and apply metadata repairs,
-    but it does not create rows, generate messages, approve rows, or attach new
-    send work.
+    ensure slots exist. Only choose `depth:"structure_only"` for
+    heartbeat/ensure-slots-only automation where the prompt explicitly says it
+    does not need source rows, generated messages, approvals, or sequence. It may
+    create/reuse shells and apply metadata repairs, but it does not create rows,
+    generate messages, approve rows, or attach new send work.
+    Short form: only choose `depth:"structure_only"` for
+    heartbeat/ensure-slots-only runs.
   - **Customer-visible completion** is required when the prompt says full
     campaign, customer-ready, send-review-ready, went through
     `$sellable:create-campaign`, fill out, approve one, only needs enrich and
@@ -138,6 +147,16 @@ for that shared-only sender. Example: if Justin already has a Post Engagers
 campaign and Jell/Hulan should only participate in the two shared campaigns,
 call `setup_evergreen_campaigns` with `postEngagerSenderIds:["<justin id>"]`
 and `sharedSenderIds:["<justin id>","<jell or hulan id>"]`.
+If the operator says to keep a protected existing Post Engagers campaign unchanged
+and create/repair only the shared lanes, pass `postEngagerSenderIds:[]` and the
+full shared sender set in `sharedSenderIds`. Do not include the protected active
+Post Engagers lane as a reuse packet in that shared-only execution scope: an
+ACTIVE protected lane can correctly produce a backend `launched_campaign`
+blocker and would make the whole yolo plan non-autoExecutable even though the
+operator asked to leave it untouched. Inventory and waterfall proof may mention
+the protected lane, but selectedActionIds and lane workers must cover only the
+shared lane packets.
+Short form: Do not include the protected active Post Engagers lane as a reuse packet when the operator requested only shared lane execution.
 
 When senders are ambiguous, ask which sender ids belong in the Post Engagers
 sender scope and which belong in the shared lane sender scope before planning.
@@ -155,6 +174,12 @@ plan execution, paid InMail spend, or ambiguous target choice. Stop on wrong
 workspace, cleanup/archive/delete need, stale plan, disconnected sender,
 duplicate candidate, unsafe side effect, missing source proof, or missing
 message proof.
+In exec/automation mode, do not call `request_user_input`. If a plan under
+`--yolo` returns `autoExecutable:false` and the run cannot receive interactive
+bounded delegated approval, stop with
+`blocked: bounded_approval_unavailable_in_exec_mode` before any mutation and
+state whether the operator should rerun with a safe autoExecutable plan, narrower
+sender scopes, explicit bindings, or an interactive session.
 
 When safe-yolo is blocked only because the plan needs normal setup work, ask
 for a **bounded delegated approval** over the rendered current plan instead of
@@ -306,31 +331,56 @@ not a parent-thread summary. The receipt must include:
   when using a receipt file, and `notAdHoc:true`.
 - `researchSenderReceipt`: `research-sender` prompt load proof,
   `complete_sender_research` result, sender LinkedIn identity basis, and the
-  notes/proof counts used before the net-new `create_campaign` call.
+  notes/proof counts used before the net-new `create_campaign` call. It must
+  include canonical `promptLoadedToHasMoreFalse:true`,
+  `completeSenderResearch`, and either `senderLinkedinUrl`, non-empty
+  `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.
+  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`.
 - `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`,
   `readyRowCount`, or `rowEvidence`), and the reason no colder source was used
-  before the current source was proven exhausted or insufficient.
+  before the current source was proven exhausted or insufficient. If the raw
+  provider output uses `sourceProvider`, `sourceListId`, `reviewBatchRowIds`, or
+  `rationale`, copy them to canonical `provider`, `sourceId`/`sourceListId`,
+  `rowIdsHash`/`rowCount`, and `sourceLadderReason`.
 - `filterDecisionReceipt`: saved/applied filter ids or explicit skip-filter
   decision with current campaign/table basis.
 - `messageDraftingReceipt`: the Message Drafting proof described below,
-  including packaged `generate-messages` prompt/assets and validation.
+  including packaged `generate-messages` prompt/assets and validation. Raw
+  fields like `generateMessagesPromptLoadedToHasMoreFalse`,
+  `requiredAssetsLoadedToHasMoreFalse`,
+  `validationPromptLoadedToHasMoreFalse`,
+  `get_campaign_message_preparation_status`, and
+  `waitForCampaignProcessingProof` are useful, but the receipt must also copy
+  them into canonical `promptLoadedToHasMoreFalse`, `requiredAssetsLoaded`,
+  `validationLoaded`, `reviewBatchRowHash`, and
+  `messageDraftRecommendation`.
 - `reviewBatchReceipt`: review-batch row ids/hash, generated row count,
   quality-valid route-proof row id when approved, and proof that no broad
   approve-all occurred.
 - `sequenceReceipt`: exact current workflowTableId, recommended non-paid
   sequence attach/precheck result, and readback showing `hasSequence:true` when
-  completion is claimed.
+  completion is claimed. If the tool output uses
+  `attachRecommendedSequenceResult.actionTypes` or
+  `nonPaidRecommendedSequence`, copy them to canonical `actionTypes` and
+  `nonPaid`.
 - final paused-send proof: if the current campaign table is `DRAFT` after the
   sequence is attached, call the product `pause_campaign({ campaignId })`
   endpoint/tool to put the unlaunched campaign into `PAUSED` review state, then
   reread the campaign/table. Do not raw-write `campaignStatus`, do not start or
   launch, and do not schedule/send. Completion requires reread proof of
-  `currentStep:"send"` and `campaignStatus:"PAUSED"`.
+  `currentStep:"send"` and `campaignStatus:"PAUSED"`. If the raw output nests
+  this in `finalCampaignRead` or `finalTableRead`, copy it to canonical
+  `finalPausedSendProof.currentStep` and
+  `finalPausedSendProof.campaignStatus`.
 - `verifyCall`: the exact `setup_evergreen_campaigns({ mode:"verify",
   planRevision, selectedActionIds, receipts })` call/result used before the
   parent reports completion.
@@ -345,7 +395,18 @@ substitute `message` for `generatedMessageText`. Do not substitute
 `passVerdict` for `verdict`. If the self-check fails, fix the receipt before
 ending; do not leave the parent to infer canonical fields from top-level
 aliases or narrative text.
+Self-check shorthand: copy raw tool-output aliases into canonical receipt keys
+before writing JSON; do not leave only raw objects like
+`get_campaign_message_preparation_status`, `attachRecommendedSequenceResult`,
+`finalCampaignRead`, or `finalTableRead`.
 Self-check shorthand: top-level `planRevision`, `actionId`, `laneKey`, `laneType`, `workspaceId`, and `senderIds` must exist before worker completion.
+Self-check shorthand: `messageDraftingReceipt.promptLoadedToHasMoreFalse`,
+`requiredAssetsLoaded`, `validationLoaded`, `reviewBatchRowHash`, and
+`messageDraftRecommendation` must exist before worker completion.
+Self-check shorthand: `reviewBatchReceipt.rowIdsHash`,
+`reviewBatchReceipt.generatedCount`, `sequenceReceipt.actionTypes`,
+`sequenceReceipt.nonPaid`, `finalPausedSendProof.currentStep`, and
+`finalPausedSendProof.campaignStatus` must exist before worker completion.
 Self-check shorthand: `sampleMessages[]` must include `rowId`, `generatedMessageText`, `verdict`, and `issues`.
 Self-check shorthand: Do not substitute `message` for `generatedMessageText`.
 Self-check shorthand: Do not substitute `passVerdict` for `verdict`.
@@ -430,9 +491,8 @@ verification unless the same object also appears inside
       "selectedLeadListId": "<source/list id>",
       "reviewBatchRowHash": "<review row ids hash>",
       "messageDraftRecommendation": {"basis": "generate-messages"},
-      "sampleMessages[].verdict": "pass",
       "sampleMessages": [
-        {"rowId": "<row id>", "generatedMessageText": "<message>", "verdict": "pass"}
+        {"rowId": "<row id>", "generatedMessageText": "<message>", "verdict": "passed", "issues": []}
       ]
     },
     "reviewBatchReceipt": {
@@ -442,8 +502,6 @@ verification unless the same object also appears inside
     "sequenceReceipt": {
       "workflowTableId": "<workflow table id>",
       "hasSequence": true,
-      "sequenceReceipt.actionTypes": ["send_invite"],
-      "sequenceReceipt.nonPaid": true,
       "actionTypes": ["send_invite"],
       "nonPaid": true
     },
@@ -571,7 +629,8 @@ The parent then calls
 `setup_evergreen_campaigns({ mode:"verify", postEngagerSenderIds,
 sharedSenderIds, planRevision, selectedActionIds, receipts })` using the same
 sender scopes as the plan call and the original execution planRevision/actionIds,
-and reports only verified completion. A verify call without the same sender scopes can recompute an empty or different plan and is invalid proof. A verify call that uses a later reuse planRevision instead of the original execution planRevision is also invalid proof. Only after verify succeeds, rerun
+and reports only verified completion. Do not include `yolo` in the verify call;
+`yolo` is plan-mode only. A verify call without the same sender scopes can recompute an empty or different plan and is invalid proof. A verify call that uses a later reuse planRevision instead of the original execution planRevision is also invalid proof. Only after verify succeeds, rerun
 `setup_evergreen_campaigns({ mode:"plan", postEngagerSenderIds,
 sharedSenderIds, yolo:true })` without explicit campaign/table bindings. That
 idempotency rerun must return `intent:"reuse"` for every completed lane and no