@sellable/install 0.1.221 → 0.1.223

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skill-templates/create-campaign.md +10 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.221",
3
+ "version": "0.1.223",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
package/skill-templates/create-campaign.md CHANGED
@@ -122,18 +122,21 @@ such as "fill campaigns", "fill up", "refill sends", "max out sends", or
122
122
 
123
123
  ```text
124
124
  get_subskill_prompt({ subskillName: "refill-sends-workflow" })
125
- resolve_campaign_fill_route
125
+ resolve_campaign_fill_route({ intent:"plain" })
126
126
  get_campaign_refill_state
127
127
  ```
128
128
 
129
129
  Plain fill is not an alias for `fill_campaign_horizon` or campaign creation.
130
130
  `fill_campaign_horizon` is evergreen-only and must not be used for regular
131
- campaign refill. If route resolution returns `route:"ask_create"`, ask whether
132
- to create a normal campaign or evergreen campaigns; campaign creation is never
133
- the default response to plain fill. When more leads are needed, the refill
134
- workflow must recommend same-campaign source-ladder replenishment; do not
135
- create warm-post-engager side campaigns, on-demand campaigns, or unrelated
136
- campaigns.
131
+ campaign refill. Route outcomes are `route:"evergreen_horizon"`,
132
+ `route:"active_campaigns"`, and `route:"ask_create"`; stay in the same `campaignOfferId`/`campaignId` context after minting. If route resolution
133
+ returns `route:"ask_create"`, ask whether to create a normal campaign or
134
+ evergreen campaigns. Campaign creation is allowed only after this route and
135
+ explicit user selection; it is never the default response to plain fill. When
136
+ more leads are needed, the refill workflow must recommend same-campaign
137
+ source-ladder replenishment; do not create warm-post-engager side campaigns,
138
+ on-demand campaigns, or unrelated campaigns. Surface sender-health blockers
139
+ separately from prepared/approved/scheduled counts.
137
140
 
138
141
  Treat active fills as capacity-fill preparation: calculate the bounded target
139
142
  from sender capacity when needed, then use the refill workflow to decide source