@sellable/install 0.1.703 → 0.1.704

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.
@@ -1146,6 +1146,10 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
1146
1146
  "mcp__sellable__attach_sequence",
1147
1147
  "mcp__sellable__attach_recommended_sequence",
1148
1148
  "mcp__sellable__start_campaign",
1149
+ "mcp__sellable__add_to_inmail_campaign",
1150
+ "mcp__sellable__add_to_connection_campaign",
1151
+ "mcp__sellable__get_or_create_direct_campaign_table",
1152
+ "mcp__sellable__start_direct_campaign",
1149
1153
  ];
1150
1154
 
1151
1155
  const FIND_LEADS_ALLOWED_TOOLS = [
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.703",
3
+ "version": "0.1.704",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code, Codex, and Hermes",
6
6
  "bin": {
@@ -77,6 +77,10 @@ allowed-tools:
77
77
  - mcp__sellable__attach_sequence
78
78
  - mcp__sellable__attach_recommended_sequence
79
79
  - mcp__sellable__start_campaign
80
+ - mcp__sellable__add_to_inmail_campaign
81
+ - mcp__sellable__add_to_connection_campaign
82
+ - mcp__sellable__get_or_create_direct_campaign_table
83
+ - mcp__sellable__start_direct_campaign
80
84
  ---
81
85
 
82
86
  # Sellable Create Campaign
@@ -86,6 +90,30 @@ It bootstraps auth and host capabilities, then loads the internal
86
90
  the internal campaign workflow prompt and `core/flow.v2.json` through MCP. Keep
87
91
  this wrapper thin; the packaged workflow is the operational source of truth.
88
92
 
93
+ ## Direct Manual-Copy Campaign Routing
94
+
95
+ Route a bounded one-off request to the direct campaign tools when the user
96
+ already supplies the recipients and exact message copy. For InMail, require a
97
+ LinkedIn URL, Subject, and Message per row, select the intended sender, then use
98
+ `add_to_inmail_campaign`. For a connection-plus-DM request, use
99
+ `add_to_connection_campaign`. These tools create or reuse the canonical typed
100
+ execution-queue table; do not call `create_campaign`,
101
+ `create_on_demand_campaign`, or a connection helper first.
102
+
103
+ Do not create a normal Campaign Builder Generate Message column, rewrite the
104
+ approved manual copy, or repair the typed direct table merely because its
105
+ message is stored in a plain `Message` text column. That is the owned schema for
106
+ `inmail_campaign` and `connection_campaign` tables.
107
+
108
+ Show the bounded recipients and exact copy for review before adding rows. Never
109
+ call `start_direct_campaign` until the user explicitly approves launch. When
110
+ approved, start the same direct type used by the add tool; do not call
111
+ `start_campaign` for that table.
112
+
113
+ Billing diagnostics are not launch authority. Honor a billing error returned by
114
+ the actual add/start mutation, but never interpret `billing_required`
115
+ diagnostics as an enforced block when the billing rollout gate is disabled.
116
+
89
117
  ## Inbox Reply Tool Boundary
90
118
 
91
119
  Inbox reply tools are outside campaign creation. If a user asks to search,
@@ -291,6 +319,7 @@ only from a source that can describe this turn:
291
319
  context. Do not infer an ID from the friendly name, do not infer effort from
292
320
  `alwaysThinkingEnabled`, and do not show this self-report to the user during
293
321
  normal campaign setup.
322
+
294
323
  - Do not run a nested `claude -p`, inspect `~/.claude/settings.json`, or read
295
324
  Claude CLI defaults as proof of the user's active Claude Code session. Those
296
325
  checks can validate a new child session or saved defaults, but not this