@sellable/install 0.1.264 → 0.1.266

package/package.json

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

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

@@ -14,6 +14,29 @@ producing duplicates. This skill never launches campaigns; customer-visible
 completion stops at paused send review.
 </role>
 
+## Invocation Mode Gate
+
+Before any setup plan, classify the invocation mode.
+
+- **Interactive approval mode is the default.** A bare user invocation such as
+  `$sellable:create-evergreen-campaigns`, "create evergreen campaigns", or
+  "set up evergreen" is interactive unless the prompt explicitly says `--yolo`,
+  scheduled, cron, automation, fresh-thread, run without approval, no user input,
+  or the host injects an equivalent trusted automation marker.
+- In interactive approval mode, first call
+  `setup_evergreen_campaigns({ mode:"plan", depth:"customer_visible", ... })`
+  **without** `yolo:true`, render the returned `approvalSummary`, and wait for
+  explicit operator approval before dispatching any lane worker or creating
+  product state.
+- In automation or explicit `--yolo` mode, pass `yolo:true` in plan mode only
+  and proceed without intermediate approval only when the plan returns
+  `autoExecutable:true`.
+
+Short form: no explicit automation/`--yolo` marker means plan-and-ask, not run.
+Short form: never infer `yolo:true` from a bare command invocation.
+Short form: command hosts that want Custer-style unattended execution must
+inject explicit automation context before invoking this skill.
+
 ## Operational Fast Path
 
 In automation or `--yolo` customer-visible setup, use this path before the
@@ -51,6 +74,21 @@ directory setup or product mutation.
 <inputs>
 The invoking prompt names the senders ("create evergreen campaigns for csreyes92 and thomas"). Resolve each via `list_senders`.
 
+If the invoking prompt is a normal user chat without an explicit automation or
+`--yolo` marker, run **interactive approval mode**:
+
+- Call `setup_evergreen_campaigns({ mode:"plan", depth:"customer_visible", ... })`
+  without `yolo:true`.
+- Render `approvalSummary.approvalQuestion` and the approval buckets
+  (`campaignsToCreate`, `campaignsToUpdate`, `campaignsToVerifyOnly`,
+  `campaignsLeftUntouched`, sender scopes, selected action ids, allowed and
+  forbidden side effects, blockers, and stop conditions).
+- Wait for an explicit approval that names or clearly accepts the rendered plan
+  before dispatching lane workers or mutating product state.
+- After approval, execute only the current `planRevision` and
+  `selectedActionIds`; re-plan if the planRevision, action ids, sender scopes,
+  blockers, side-effect classes, or lane bindings drift.
+
 If the invoking prompt says scheduled, automation, cron, heartbeat, fresh-thread,
 run without user input, or similar, run in **automation mode**:
 
@@ -269,11 +307,23 @@ 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
-asking for each substep. The approval packet must name the workspace id, sender
-ids, lane keys, campaign/table ids or create intents, source/import caps,
-generate-message caps, route-proof approval policy, selectedActionIds,
-planRevision, allowed side-effect classes, and stop conditions. After that one
-approval covers the current planRevision, the parent may act on behalf of the
+asking for each substep. The approval request must be rendered from the plan's
+`approvalSummary`, not handwritten from raw lane packets alone. Show:
+
+- `workspaceId`, `planRevision`, and `selectedActionIds`.
+- Sender scopes with display names and ids: Post Engagers senders and shared-lane senders.
+- `campaignsToCreate`: each campaign/lane name, action id, create intent, attached senders, and allowed side effects.
+- `campaignsToUpdate`: each existing campaign/table id, current status/step, attached senders, and exact repairs or setup side effects.
+- `campaignsToVerifyOnly`: existing campaigns that will only be verified/read.
+- `campaignsLeftUntouched`: existing campaigns attached to selected senders but excluded from the current selected lane scope, with the reason.
+- Source/import caps, generate-message caps, route-proof approval policy, allowed side-effect classes, forbidden side effects, blockers, and stop conditions.
+
+If `approvalSummary.approvalQuestion` is present, use it as the short approval
+question and put the detailed buckets underneath. Do not ask a vague yes/no
+question that only says "run evergreen setup" or "approve this plan" without
+naming the campaigns to create, existing campaigns to update/verify, campaigns
+left untouched, and attached senders. After that one approval covers the current
+planRevision and selectedActionIds, the parent may act on behalf of the
 operator and execute the selectedActionIds end to end. Do not ask again for
 substep approvals for source import, create-campaign choices, Message Drafting,
 sequence attach/precheck, or exactly one route-proof approval when those actions
@@ -283,6 +333,7 @@ workspace id, sender ids, source/list id, campaign/table id, new campaign/table
 id, planRevision, actionId, selectedActionIds, allowed side effects, caps,
 status, or blocker set outside the approved packet.
 The short rule: one approval covers the current planRevision and selectedActionIds.
+The approval clarity rule: the operator approves named campaign create/update/verify/untouched buckets and attached senders, not a generic evergreen run.
 The execution rule: act on behalf of the operator; do not ask again for substep approvals while work stays within the lane packet, approved caps, approved side-effect classes, and route-proof approval policy.
 The drift rule: stop and re-plan when ids, caps, blockers, side-effect classes, or any new campaign/table id leave the approved packet.
 
@@ -448,10 +499,22 @@ Do not paste the entire wrapper skill into worker prompts. If the parent cannot
 launch at least one visible/durable worker immediately after directory setup,
 stop with `blocked: worker_dispatch_stalled` before any mutation.
 After launching workers, poll only the expected current-run receipt paths from
-`workerDispatch.receiptArtifactHint`. If no worker receipt file appears within a
-bounded wait, for example 10 minutes in automation, stop with
-`blocked: worker_receipt_timeout`, include the worker ids/final-file paths/stderr
-if available, and do not create or repair campaign shells in the parent.
+`workerDispatch.receiptArtifactHint`. Polling is progress-aware, not a blind
+wall-clock cutoff: while a visible/durable worker is still active and recent
+readbacks show forward progress, keep polling the expected path and do not
+report `worker_receipt_timeout`. If a worker is active but the receipt is still
+missing after the product postconditions appear complete, send exactly one
+receipt-write recovery prompt that says the worker must write either a success
+receipt or a blocked receipt at the exact path before ending. If no worker
+receipt file appears after a bounded **no-progress** window, for example 10
+minutes without new tool calls, final-file updates, receipt mtime changes, or
+thread progress, stop with `blocked: worker_receipt_timeout`, include the worker
+ids/final-file paths/stderr if available, and do not create or repair campaign
+shells in the parent.
+If a worker produced partial product state but no receipt, recover through the
+same visible/durable worker or a compact repair worker against the existing
+campaign/table ids; never create a duplicate lane campaign to recover a missing
+receipt.
 Use only the repo-local `workerDispatch.receiptArtifactHint` returned by the
 current lane packet for receipt paths.
 Do not hardcode machine-specific paths, workspace ids, campaign ids, sender ids, or UAT/phase artifact paths in this MCP prompt or any worker prompt.
@@ -477,6 +540,10 @@ Lane key: <laneKey>
 Allowed side effects: <allowedSideEffects JSON>
 Write the durable receipt to this exact path: <receiptArtifactPath>
 
+If your runtime exposes a goal tool, create or maintain this exact goal:
+complete action <actionId> only when <receiptArtifactPath> exists as valid JSON
+for this lane or when a blocked receipt has been written at that same path.
+
 Worker lane packet JSON:
 <lane packet JSON>
 
@@ -485,7 +552,14 @@ Use mcp__sellable only. Do not use admin tools, direct DB, Prisma, SQL, web sear
 Do not launch, start, schedule, send, or use paid InMail.
 For filter proof, durable receipt status must be `filterDecisionReceipt.status:"applied"` only; never `completed`, `confirmed`, `done`, or aliases.
 For generated messages, `update_cell` is allowed only for the semantic Approved checkbox. Never use `update_cell` for generated message text/body/sample copy. Bad copy requires `revise_message_template_and_rerun` or brief/template revision plus Generate Message rerun. Any generated-message cell override is `blocked: generated_message_cell_override`.
-Complete only this lane, write the required durable receipt JSON, and stop.
+Complete only this lane. Do not end with narration only. Before your final
+response, run a local file-existence and JSON self-check for
+<receiptArtifactPath>. If the lane succeeded, write the canonical success
+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.
 WORKER_PROMPT
 
 # Multi-worker launcher equivalent:
@@ -1015,6 +1089,13 @@ every canonical verifier object under `createCampaignStepReceipt`, including
 `campaignBriefReceipt`, `sourceDecisionReceipt`, `filterDecisionReceipt`,
 `messageDraftingReceipt`, `reviewBatchReceipt`, `sequenceReceipt`,
 `finalPausedSendProof`, and `verifyCall`.
+Write the compact verifier payload to a temporary JSON file and load that object
+directly into the MCP verify call. Do not manually paste, retype, truncate, or
+merge full receipt JSON into the tool call. If a verify attempt fails because
+the payload was malformed, overlong, manually edited, missing a receipt, or used
+a later reuse planRevision/actionId set, rebuild the compact payload from the
+durable receipt files and retry once with the original execution
+`planRevision`/`selectedActionIds` before reporting a verifier blocker.
 When compacting, normalize `finalPausedSendProof.currentStep` and
 `finalPausedSendProof.campaignStatus` from nested pause/navigation readbacks if
 the worker receipt stored those values under `pauseCampaignResult`,
@@ -1029,6 +1110,7 @@ Short form: Do not use complex inline `jq` for receipt compaction; use Node.
 Short form: Compact receipts must preserve `researchSenderReceipt`.
 Short form: Compact receipts must preserve direct `finalPausedSendProof.currentStep` and `campaignStatus`.
 Short form: Never change planRevision/actionId/laneKey while compacting receipts.
+Short form: Do not hand-build giant receipt tool-call payloads; load compact JSON from disk.
 
 Parent repair dispatch uses the same compact discipline. If the parent sample
 quality gate fails after a worker receipt, do not launch a repair worker by