@sellable/install 0.1.290 → 0.1.292

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.290",
3
+ "version": "0.1.292",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {
@@ -5,6 +5,7 @@ visibility: public
5
5
  allowed-tools:
6
6
  - mcp__sellable__refill_sends
7
7
  - mcp__sellable__get_refill_target_plan
8
+ - mcp__sellable__refresh_paid_inmail_credits
8
9
  - mcp__sellable__get_auth_status
9
10
  - mcp__sellable__start_cli_login
10
11
  - mcp__sellable__wait_for_cli_login
@@ -123,9 +124,14 @@ coverage, report that the selected target is already filled and no-op without
123
124
  asking for approval. If the ready buffer covers the projected gap but scheduled
124
125
  coverage is still short, run only a bounded read-only scheduler settle/reread
125
126
  loop and report `awaiting_scheduler_after_ready_buffer` if it does not settle.
126
- If paid InMail is below threshold, stale, or missing credit facts, report the
127
- exact campaign/table/column threshold action or connection fallback; `--yolo`
128
- does not lower paid-InMail thresholds or create campaigns.
127
+ If paid InMail credit facts are stale or missing and the target plan returns a
128
+ `refresh_paid_inmail_credits` action candidate, include the exact sender id,
129
+ campaign/table/column proof, expected sender-credit-cache writes, and rerun plan
130
+ step in the bounded packet. After `refresh_paid_inmail_credits`, rerun
131
+ `get_refill_target_plan` before any prep/import/approval/start action. If paid
132
+ InMail is below threshold after a fresh credit read, report the exact
133
+ campaign/table/column threshold action or connection fallback; `--yolo` does not
134
+ lower paid-InMail thresholds or create campaigns.
129
135
 
130
136
  If the plain route's managed waterfall targets are stale, for example skipped
131
137
  targets show archived/completed shared slots or the returned targets do not cover
@@ -165,7 +171,8 @@ approved eligible sequence actions, so include that expected side effect in the
165
171
  packet. It does not authorize starting unrelated, archived, completed, draft, or
166
172
  direct campaigns, separate launch/send actions, archive or delete cleanup,
167
173
  direct scheduler writes, sender reassignment, paid-InMail threshold changes,
168
- connection campaign creation, or campaigns outside those
174
+ connection campaign creation, paid-InMail credit refreshes outside the exact
175
+ rendered sender packet, or campaigns outside those
169
176
  selected for the eligible sender set. Stop and re-plan if the route, sender set,
170
177
  ids, caps, blockers, paid-InMail feasibility, action class, or side-effect class
171
178
  drift before mutation. Sent/scheduled counts increasing toward the approved