@sellable/install 0.1.257 → 0.1.258

package/package.json

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

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

@@ -21,7 +21,14 @@ long-form contract below:
 
 1. Resolve the active workspace and explicit sender scopes, then call
    `setup_evergreen_campaigns({ mode:"plan", yolo:true, postEngagerSenderIds,
-   sharedSenderIds })`.
+   sharedSenderIds })`. If the user did not name senders but
+   `get_campaign_waterfall` returns an active managed evergreen/prod waterfall
+   for the workspace, derive exact sender scopes from the waterfall `senderRefs`
+   and canonical Post Engagers/shared slots before the first setup plan. Match
+   `senderRefs` to `list_senders` by LinkedIn public identifier, display name,
+   or obvious handle/name alias; record the mapping in the plan notes. Do not
+   call setup with empty sender arrays when product-visible waterfall evidence
+   identifies the evergreen sender scope.
 2. If the plan is not current, lacks lane packets, or has
    `autoExecutable:false`, return the exact blocker before mutation.
 3. Choose the worker runtime immediately. When running under Codex CLI or on VPS,
@@ -92,14 +99,24 @@ connected senders", "every connected sender", "all seats", or names an
 equivalent all-sender scope. If the user says "all 4 campaigns", "the four
 evergreen campaigns", or names specific senders, resolve those exact senders
 and pass explicit `postEngagerSenderIds` plus `sharedSenderIds`; do not broaden
-the plan to every connected sender. In non-interactive or `--yolo` mode, when
-more than two connected senders exist and the prompt does not explicitly
-authorize all connected senders, stop before mutation with
+the plan to every connected sender. If the prompt does not name senders but the
+active workspace has a product-visible managed evergreen/prod waterfall, derive
+the exact scope from that waterfall instead of using all connected senders:
+Post Engagers sender scope is the senderRefs that own person-specific
+Post Engagers slots; shared sender scope is the union of senderRefs on the
+shared Signal Discovery and Shared Cold Fallback waterfall slots. If the
+waterfall has one clear production evergreen program for the workspace, this is
+not ambiguous even when `list_senders` returns additional connected senders.
+In non-interactive or `--yolo` mode, when more than two connected senders exist
+and neither the prompt nor product-visible waterfall evidence identifies exact
+evergreen sender scope, stop before mutation with
 `blocked: ambiguous_post_engager_sender_scope` and report the sender ids/names
 needed for approval. Never let "workspace default" silently create Post
 Engagers lanes for extra senders.
 Short form: Do not pass `allConnectedSenders:true` unless the prompt explicitly says all/every connected sender.
 Short form: "all 4 campaigns" means explicit sender scope plus two shared lanes, not all connected senders.
+Short form: Product-visible managed evergreen/prod waterfall senderRefs are exact sender scope.
+Short form: Do not report `no_senders` while waterfall senderRefs can be mapped to list_senders.
 Short form: In `--yolo`, ambiguous multi-sender scope blocks before mutation.
 </inputs>
 
@@ -114,6 +131,13 @@ error, or does not return a current `planRevision` with lane packets, stop
 immediately with `blocked: setup_evergreen_campaigns_unavailable`. Do not fall
 back to ad hoc create-campaign calls, inventory-only guesses, or direct shell
 creation when the command-backed plan is missing.
+Exception: if an initial unscoped plan returns only `blocked:no_senders`, and
+the parent has already read `list_senders` plus a product-visible managed
+evergreen/prod waterfall with mappable `senderRefs`, immediately re-run the
+plan once with explicit derived `postEngagerSenderIds` and `sharedSenderIds`.
+Do not report `no_senders` to the user until that scoped plan has also failed.
+If senderRef mapping is partial, stop with
+`blocked: ambiguous_post_engager_sender_scope` and include the unmapped refs.
 
 MCP/product-visible proof only: every success claim must be observable through
 the installed Sellable MCP tools and product-visible readbacks a normal user or