@sellable/install 0.1.147 → 0.1.148

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.
@@ -701,9 +701,10 @@ label it explicitly as not estimated from this run.
701
701
  Before any provider prompt, search, source scout, or signal-discovery call, show
702
702
  one source-plan gate and ask for approval. Write this like a fifth grader could
703
703
  understand it: short sentences, no internal labels, and no GTM shorthand. The
704
- plan must be visible before the question, and this first approval only
705
- authorizes finding the best places to look for buyers. It does not add anyone
706
- to the campaign yet. The gate should say:
704
+ order is strict: first show the plan in chat, then open the approval question.
705
+ Do not open a generic approval first and reuse it after the plan. This first
706
+ approval only authorizes finding the best places to look for buyers. It does
707
+ not add anyone to the campaign yet. The gate should say:
707
708
 
708
709
  - the buyer groups or places we could check
709
710
  - the best place to start
@@ -752,9 +753,11 @@ instead and explain it in plain words once. Do not call \`search_signals\`,
752
753
  \`fetch_post_engagers\`, or provider-scoped subagents until the user approves this
753
754
  source plan or explicitly chooses a different source.
754
755
 
755
- If the user already answered a provider approval such as "Approve Prospeo plan",
756
- that answer satisfies the source-plan gate. Persist the approved provider and
757
- run the scouting/search next; do not ask a second source-plan approval question.
756
+ If the user answers a provider approval such as "Approve Prospeo plan" after
757
+ seeing the source plan, that answer satisfies the source-plan gate. Persist the
758
+ approved provider and run the scouting/search next; do not ask a second
759
+ source-plan approval question. A brief approval, generic "approve plan", or
760
+ provider state from before the visible source plan does not satisfy this gate.
758
761
 
759
762
  For hiring-led campaigns, do not default to Sales Nav just because the target is
760
763
  a role search. Prospeo is the primary lane when the brief asks for companies
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.147",
3
+ "version": "0.1.148",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
@@ -132,9 +132,10 @@ label it explicitly as not estimated from this run.
132
132
  Before any provider prompt, search, source scout, or signal-discovery call, show
133
133
  one source-plan gate and ask for approval. Write this like a fifth grader could
134
134
  understand it: short sentences, no internal labels, and no GTM shorthand. The
135
- plan must be visible before the question, and this first approval only
136
- authorizes finding the best places to look for buyers. It does not add anyone
137
- to the campaign yet. The gate should say:
135
+ order is strict: first show the plan in chat, then open the approval question.
136
+ Do not open a generic approval first and reuse it after the plan. This first
137
+ approval only authorizes finding the best places to look for buyers. It does
138
+ not add anyone to the campaign yet. The gate should say:
138
139
 
139
140
  - the buyer groups or places we could check
140
141
  - the best place to start
@@ -183,9 +184,11 @@ instead and explain it in plain words once. Do not call `search_signals`,
183
184
  `fetch_post_engagers`, or provider-scoped subagents until the user approves this
184
185
  source plan or explicitly chooses a different source.
185
186
 
186
- If the user already answered a provider approval such as "Approve Prospeo plan",
187
- that answer satisfies the source-plan gate. Persist the approved provider and
188
- run the scouting/search next; do not ask a second source-plan approval question.
187
+ If the user answers a provider approval such as "Approve Prospeo plan" after
188
+ seeing the source plan, that answer satisfies the source-plan gate. Persist the
189
+ approved provider and run the scouting/search next; do not ask a second
190
+ source-plan approval question. A brief approval, generic "approve plan", or
191
+ provider state from before the visible source plan does not satisfy this gate.
189
192
 
190
193
  For hiring-led campaigns, do not default to Sales Nav just because the target is
191
194
  a role search. Prospeo is the primary lane when the brief asks for companies