@sellable/install 0.1.303 → 0.1.305

package/lib/runtime-verify.mjs

@@ -32,6 +32,7 @@ export const REQUIRED_SELLABLE_MCP_TOOLS = [
   "get_campaign_refill_state",
   "get_refill_target_plan",
   "get_scheduler_fill_capacity",
+  "run_scheduler_sweep",
   "refill_sends",
   "setup_evergreen_campaigns",
   "start_campaign_message_preparation",
@@ -188,6 +189,10 @@ function summarizeToolResult(name, result) {
     return {
       ...summary,
       authOk: parsed.ok === true,
+      configPath: parsed.configPath || null,
+      configExists: parsed.configExists === true,
+      configsDir: parsed.configsDir || null,
+      tokenPresent: parsed.tokenPresent === true,
       errorType: parsed.error?.type || null,
       activeWorkspaceId: parsed.activeWorkspaceId || null,
       activeWorkspaceName: parsed.activeWorkspaceName || null,

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.303",
+  "version": "0.1.305",
   "type": "module",
-  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
+  "description": "One-command installer for Sellable MCP in Claude Code, Codex, and Hermes",
   "bin": {
     "sellable": "bin/sellable-install.mjs"
   },
@@ -18,13 +18,15 @@
     "README.md"
   ],
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.25.2"
+    "@modelcontextprotocol/sdk": "^1.25.2",
+    "yaml": "^2.8.1"
   },
   "keywords": [
     "sellable",
     "mcp",
     "claude-code",
     "codex",
+    "hermes",
     "linkedin",
     "outbound"
   ],

package/skill-templates/refill-sends-v2.md

@@ -128,6 +128,17 @@ Reinvoke with that handle. The approximately five minute scheduler budget is at
 the run level, not one tool call. A window-closed or loaded-awaiting scheduler
 report must include remaining-ready count, exact expected pickup time, and the
 resume handle; never treat bare "awaiting scheduler" copy as a final answer.
+Scheduler-run receipt interpretation still applies to terminal progress:
+`cellsConsidered is allocation-attempt count`, not total ready supply, while
+`readyCellsFound` is ready inventory found before prefilters. Inspect
+`campaignScopeSummary` before assuming the selected refill campaign/table was
+included; if absent, do not infer that target was ready-but-blocked. Interpret
+`prefiltered`, `skipped`, and `deferred` separately. For ready closed-InMail
+cells with stale paid-credit reasons, route to
+`refresh_paid_inmail_credits_then_rerun` once, then rerun/status.
+`wait_for_capacity_or_window` means report loaded/capped/waiting and do not
+source or prep more rows; `no_ready_cells_continue_refill_prep` means return to
+the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
 
 After the first prep batch, read the conversion-verdict journal line. It is
 rendered from packet facts: `supplyCensus`, `censusReason`, and

package/skill-templates/refill-sends.md

@@ -6,6 +6,7 @@ allowed-tools:
   - mcp__sellable__refill_sends
   - mcp__sellable__get_refill_target_plan
   - mcp__sellable__get_scheduler_fill_capacity
+  - mcp__sellable__run_scheduler_sweep
   - mcp__sellable__refresh_paid_inmail_credits
   - mcp__sellable__get_subskill_asset
   - mcp__sellable__get_auth_status
@@ -114,10 +115,11 @@ or install-time workspace mapping. Pass `workspaceId` on every scheduled or
 `--yolo` refill tool call, including setup/read calls such as
 `refill_sends`, `get_refill_target_plan`, `list_senders`,
 `get_sender_routing`, `resolve_campaign_fill_route`,
-`get_campaign_refill_state`, `get_scheduler_fill_capacity`, and any later
-refill mutation covered by the packet. Missing `workspaceId` in scheduled or
-`--yolo` mode is a blocker; stop with `WORKSPACE_REQUIRED` instead of running
-against an implicit or guessed workspace.
+`get_campaign_refill_state`, `get_scheduler_fill_capacity`,
+`run_scheduler_sweep`, and any later refill mutation covered by the packet.
+Missing `workspaceId` in scheduled or `--yolo` mode is a blocker; stop with
+`WORKSPACE_REQUIRED` instead of running against an implicit or guessed
+workspace.
 
 Do not solve scheduled or `--yolo` workspace uncertainty by changing the shared
 active workspace. Manual interactive workspace switching remains a separate
@@ -269,6 +271,23 @@ need raw proof, call the read-only `get_scheduler_fill_capacity` query for the
 same sender/action/date; it tells the MCP how many cells the product scheduler
 will try to place and does not import, approve, schedule, refresh credits, or
 mutate.
+When the refill loop has ready rows and needs scheduler pickup now, use
+`run_scheduler_sweep` with the same explicit `workspaceId`; it can place cells
+within existing scheduler gates and returns the receipt, but it never sends or
+bypasses limits.
+Scheduler-run receipt interpretation: `cellsConsidered is allocation-attempt
+count`, not total ready supply, while `readyCellsFound` is ready inventory found
+before prefilters. Inspect `campaignScopeSummary` before assuming the selected
+refill campaign/table was included; if absent, do not infer that target was
+ready-but-blocked. Interpret `prefiltered` as ready cells removed before
+allocation, `skipped` as considered cells blocked by scheduler gates, and
+`deferred` as considered cells waiting on windows/capacity/cooldown. For ready
+closed-InMail cells with stale paid-credit prefilter/defer reasons, refresh
+paid-InMail credits once through existing tools, then rerun `run_scheduler_sweep`
+or read `action:"status"`; `refresh_paid_inmail_credits_then_rerun` is that
+path. `wait_for_capacity_or_window` means report loaded/capped/waiting and do
+not source or prep more rows; `no_ready_cells_continue_refill_prep` means return
+to the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
 If the target plan is complete by projected coverage, report that the selected
 target is already filled and no-op without asking for approval. If the ready
 buffer covers the projected gap, paid InMail credit facts are fresh for every