@sellable/install 0.1.281 → 0.1.282

package/bin/sellable-install.mjs

@@ -37,7 +37,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.52";
+const CODEX_PLUGIN_VERSION = "0.1.53";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -74,6 +74,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.40",
   "0.1.41",
   "0.1.51",
+  "0.1.52",
 ];
 const RAW_INSTALL_PACKAGE_SPEC =
   process.env.SELLABLE_INSTALL_PACKAGE_SPEC || "@sellable/install@latest";

package/package.json

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

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

@@ -572,8 +572,15 @@ response, run a local file-existence and JSON self-check for
 receipt there; if any postcondition, quality gate, verifier schema, or file
 write blocks, write a canonical blocked receipt there with `status:"blocked"`,
 `blocker`, `campaignId`, `tableId`, `actionId`, `laneKey`, `planRevision`, and
-the latest product readback. The terminal condition is filesystem proof that
-<receiptArtifactPath> exists.
+the latest product readback. For Post Engagers lanes, no sender-authored posts
+or no sender-owned post-engager source is an acceptable terminal blocked/no-op
+receipt, not a worker crash: use one of
+`post_engagers_no_sender_posts`, `post_engagers_no_recent_sender_posts`,
+`post_engagers_no_sender_owned_posts`, or
+`post_engagers_source_author_mismatch`, include the source/readback evidence,
+and stop without scraping third-party authors or generating misleading warm
+copy. The terminal condition is filesystem proof that <receiptArtifactPath>
+exists.
 WORKER_PROMPT
 
 # Multi-worker launcher equivalent:
@@ -816,6 +823,17 @@ the lane is complete. Do not use `status:"passed"` or
 in a separate `warnings` array, but the completion status stays canonical.
 The backend verifier rejects `status:"passed"`, `status:"pass"`, and
 `status:"passed_with_warnings"` as primary completion statuses.
+Exception: a Post Engagers lane may write `status:"blocked"` when Sellable MCP
+sender-post/source readback proves there are no recent sender-authored posts to
+scrape, no sender-owned post-engager source, or the current source is authored
+by someone else. Use the explicit blocker codes
+`post_engagers_no_sender_posts`, `post_engagers_no_recent_sender_posts`,
+`post_engagers_no_sender_owned_posts`, or
+`post_engagers_source_author_mismatch`. Parent verify treats these as
+`acceptedLaneBlockers`, so the parent can report the truthful no-op instead of
+retrying invalid source repair. This exception does not apply to shared lanes,
+bad generated copy, stale plans, target mismatch, missing receipt files, launch
+or schedule side effects, or arbitrary worker failures.
 
 All step proof objects must live under `createCampaignStepReceipt`. Do not put
 `createCampaignWorkflowReceipt`, `campaignBriefReceipt`,
@@ -1097,8 +1115,13 @@ 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. 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
+and reports only verified completion. If verify returns `verified:true` with
+`acceptedLaneBlockers`, report those lanes as accepted blocked/no-op lanes, not
+completed campaigns. 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
@@ -1530,7 +1553,7 @@ Message, and verify current-revision sample messages before final completion.
      internal-only objects, verify the active waterfall linkage, table ID,
      source type, and priority, and label them `internal source pool` rather
      than treating them as completed campaigns.
-   - Post Engagers lanes are sender-owned source lanes. The selected/source LinkedIn posts must be authored by that exact sender (for example, Thomas post-engager source posts must visibly be Thomas-authored posts). If selected/source posts include another person or company author, mark the slot `blocked`/`flagged` for source repair; do not scrape/import engagers or report completion until the source is sender-owned. Shared Signal Discovery lanes are the only evergreen lanes allowed to mix authors.
+   - Post Engagers lanes are sender-owned source lanes. The selected/source LinkedIn posts must be authored by that exact sender (for example, Thomas post-engager source posts must visibly be Thomas-authored posts). If Sellable MCP readback proves the sender has no recent posts to scrape, no sender-authored posts with usable engagers, no sender-owned post-engager source, or the selected/source posts include another person or company author, write a blocked receipt with the matching accepted blocker code and report that back to the parent as an accepted no-op. Do not scrape/import engagers from third-party authors and do not report completion until the source is sender-owned. Shared Signal Discovery lanes are the only evergreen lanes allowed to mix authors.
 5. **Interactive polish mode only: confirm the message template with the user — and check it reads chat-native.** Show the exact first-message template each created campaign's brief carries and ask the user to confirm or adjust it before moving on. Because DM copy may send paragraph-by-paragraph (each blank-line block becomes its own message), every paragraph must read like something a human literally typed as a separate chat message:
    - **No letter punctuation.** `Hey {{first_name}}` — never `Hey {{first_name}},` (nobody types a trailing comma and hits send). No `Dear`, no sign-offs, no `Best,`.
    - Each paragraph stands alone as a message — short, lowercase-casual is fine, sentence fragments are fine.