@sellable/install 0.1.469 → 0.1.471

package/lib/sellable-agent/fly-admin-image/Dockerfile

@@ -16,6 +16,8 @@ ARG ADMIN_ARTIFACT_DIGEST
 ARG ADMIN_PACKAGE_LOCK_B64
 ARG ADMIN_PROFILE_CONTRACT_TEMPLATE_B64
 ARG TUS_JS_CLIENT_VERSION=4.3.1
+ARG STRIPE_CLI_PACKAGE=@stripe/cli-linux-x64@1.45.0
+ARG STRIPE_CLI_INTEGRITY=sha512-1ZhoPpoweYfynqsvhCLlTjZ7lPz5IKtxqAMT5MBy6zrwLRTP9x0T6r8h/jLYL8lRH1c7zC/6X6/XUu2V+r9Bog==
 
 RUN set -eux; \
     test -n "${ADMIN_PACKAGE_LOCK_B64}"; \
@@ -24,6 +26,7 @@ RUN set -eux; \
     test "$(npm view "${PRODUCT_INSTALL_PACKAGE}" dist.integrity)" = "${PRODUCT_INSTALL_INTEGRITY}"; \
     test "$(npm view "${ADMIN_MCP_PACKAGE}" dist.integrity)" = "${ADMIN_MCP_INTEGRITY}"; \
     test "$(npm view "${ADMIN_INSTALL_PACKAGE}" dist.integrity)" = "${ADMIN_INSTALL_INTEGRITY}"; \
+    test "$(npm view "${STRIPE_CLI_PACKAGE}" dist.integrity)" = "${STRIPE_CLI_INTEGRITY}"; \
     mkdir -p /usr/local/lib/sellable-agent/admin-artifact; \
     node -e 'const fs=require("fs"); const specs=process.argv.slice(1); fs.writeFileSync("/usr/local/lib/sellable-agent/admin-artifact/package.json", JSON.stringify({name:"sellable-admin-runtime-artifact",private:true,version:"1.0.0",dependencies:Object.fromEntries(specs.map((spec)=>{const at=spec.lastIndexOf("@"); return [spec.slice(0,at),spec.slice(at+1)];}))},null,2)+"\n");' \
       "${PRODUCT_MCP_PACKAGE}" \
@@ -48,6 +51,18 @@ RUN set -eux; \
       --no-audit \
       --no-fund \
       "tus-js-client@${TUS_JS_CLIENT_VERSION}"; \
+    npm install \
+      --prefix /usr/local/lib/sellable-agent/stripe-cli \
+      --omit=dev \
+      --ignore-scripts \
+      --no-audit \
+      --no-fund \
+      "${STRIPE_CLI_PACKAGE}"; \
+    install -m 0755 \
+      /usr/local/lib/sellable-agent/stripe-cli/node_modules/@stripe/cli-linux-x64/bin/stripe \
+      /usr/local/bin/stripe; \
+    stripe_cli_version="$(node -p "require('/usr/local/lib/sellable-agent/stripe-cli/node_modules/@stripe/cli-linux-x64/package.json').version")"; \
+    test "$(stripe version | head -n 1)" = "stripe version ${stripe_cli_version}"; \
     test "$(node -p "require('/usr/local/lib/sellable-agent/node_modules/tus-js-client/package.json').version")" = "${TUS_JS_CLIENT_VERSION}"; \
     test -f /usr/local/lib/sellable-agent/admin-artifact/node_modules/@sellable/install/lib/sellable-agent/admin-runtime-reconciler.mjs; \
     test -f /usr/local/lib/sellable-agent/admin-artifact/node_modules/@sellable/admin-mcp/dist/index.js; \

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.469",
+  "version": "0.1.471",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code, Codex, and Hermes",
   "bin": {

package/skill-templates/refill-sends.md

@@ -4,6 +4,8 @@ description: Refill projected sends across a workspace or selected senders throu
 visibility: public
 allowed-tools:
   - mcp__sellable__refill_sends
+  - mcp__sellable__refill_v3_advance
+  - mcp__sellable__refill_v3_continue
   - mcp__sellable__get_refill_target_plan
   - mcp__sellable__get_scheduler_fill_capacity
   - mcp__sellable__get_subskill_asset
@@ -21,17 +23,43 @@ allowed-tools:
 # Refill Sends
 
 Use this skill for “fill”, “refill sends”, “max out sends”, “load everyone up”,
-or “fill horizon sends”. `refill_sends` is the only execution owner. The host
-resolves the request, invokes the coordinator, and follows its exact
-continuation; it never reconstructs the refill ladder from low-level tools.
+or “fill horizon sends”. Exactly one coordinator owns execution: `refill_v3_advance`
+on the V3 route, `refill_sends` on the V1 route. The host resolves the request,
+invokes that coordinator, and follows its exact continuation; it never
+reconstructs the refill ladder from low-level tools.
 
 Host commands:
 
 - Claude Code: `/sellable:refill-sends`
 - Codex: `$sellable:refill-sends`
 
+## Route selection — do this FIRST
+
+Decide the route before parsing scope, before loading any flow asset, and before
+any tool call other than auth/workspace resolution. The predicate is
+MECHANICAL and observable in the connected Sellable MCP tool list:
+
+> **Is `refill_v3_advance` one of the tools this server exposes?**
+
+- **Yes → take the Refill V3 route.** This is the default for every workspace on
+  a server that exposes the tool. Go to [Refill V3](#refill-v3) and follow it;
+  the V1 ladder in the rest of this document does not apply.
+- **No → take the V1 route.** The installed server predates Refill V3, so
+  `refill_sends` is the only coordinator available. Follow this document from
+  [Entry and exact scope](#entry-and-exact-scope) onward.
+
+Never infer the route from a workspace flag, a campaign field, a tool result, or
+the operator's wording: no such cutover signal exists, and guessing at one is
+what makes an ordinary refill request silently take the wrong route. Report the
+selected route explicitly before the first coordinator call.
+
 ## Entry and exact scope
 
+Everything from here down to [Refill V3](#refill-v3) is the **V1 route**. Skip it
+entirely when route selection chose V3. On this route `refill_sends` is the only
+execution owner and the host follows its exact continuation; it never
+reconstructs the refill ladder from low-level tools.
+
 Accepted request fields are `--yolo`, `workspaceId`, `--sender`/`senderIds`/
 `senderNames`, `actionTypes`, `--until`/`untilDate`, `--target-date`/
 `targetDate`, and compatibility `horizonSendDays`. Omitted dates mean the
@@ -55,7 +83,9 @@ flowchart TD
     SENDERS --> SG{"Every selector resolves exactly?"}
     SG -- No --> SB["Output: blocked_retryable / sender_selector_unresolved with candidates"]
     SG -- Yes --> DATE["Normalize 48h, exact targetDate, or inclusive untilDate in sender-local time"]
-    DATE --> D1["D1: call get_refill_target_plan read-only with exact scope"]
+    DATE --> ROUTE{"Does this server expose refill_v3_advance?"}
+    ROUTE -- Yes --> V3["Refill V3 route: load core/flow.v3.json and call refill_v3_advance"]
+    ROUTE -- No --> D1["D1: call get_refill_target_plan read-only with exact scope"]
     D1 --> RENDER["Render sender/campaign waterfall, coverage ledger, first action, side effects, forbidden actions, and stop condition"]
     RENDER --> D2["D2: call refill_sends with workspaceCoordinator true plus displayed targetShapeRevision and actionKey"]
 ```
@@ -551,3 +581,58 @@ available work.
   sweep/status, and bounded receipts. Never use individual cell ids, Prisma,
   SQL, direct database access, or production-environment scripts as completion
   proof. Redact raw copy and prospect fields.
+
+## Refill V3
+
+This is the DEFAULT route whenever `refill_v3_advance` is exposed (see
+[Route selection](#route-selection--do-this-first)). `refill_v3_advance` is then
+the only execution owner and `refill-sends-workflow` plus its `core/flow.v3.json`
+asset is the contract to load — load the prompt and that asset, verify the `v3`
+compatible range, and report the version before the first call. Call
+`refill_v3_advance` with `{workspaceId, scope}` — plus `yolo: true` only when the
+operator asked for `--yolo` — and call it again after each `advanced` or
+`campaign_attention_required` result until it answers `awaiting_external_change`,
+`complete`, or `blocked`.
+
+Resolve the workspace BEFORE the first call, exactly as the V1 route already
+requires. `workspaceId` must be an exact id on every automation call: when the
+operator names a workspace, call `list_workspaces` first and match that name to
+its id, and use the configured or active workspace only when the operator named
+none. If nothing accessible matches the name, or more than one does, stop and say
+so — do not fall back to the configured workspace — and never change the shared
+active workspace to steer an automation.
+
+Map the rest of the request onto those keys and nothing else: the sender/date
+envelope becomes `scope` (a 1-3 day `sender_local_horizon`, or
+`exact_sender_dates` when the operator named exact senders or dates). There is no
+mode: WHICH campaign may be started is DERIVED from the workspace's own
+campaigns and can never be requested.
+
+`--yolo` still means what it has always meant, and it is the ONE remaining
+execution input. It is the operator's AUTONOMY GRANT, read from their words
+alone, and it decides two things together:
+
+- **Granted** (`yolo: true` on every call of that run): after a row's active
+  campaigns are exhausted, one derived-evergreen start-eligible campaign may be
+  started, and you receive it as an ordinary executed `start_evergreen_campaign`
+  action. Keep calling advance until a terminal without checking back.
+- **Withheld** (omit the key): no paused campaign is started — the backend
+  refuses it and answers the exhaustion terminal instead — and you surface each
+  result and ASK before calling advance again.
+
+Never infer the grant from a workspace flag, a campaign field, a tool result, an
+idle-looking workspace, or a previous terminal, and never set it to make a run
+finish. Pass no other execution flag and no mode, and do not call
+`get_refill_target_plan`, `refill_sends`, or any placement, scheduler, source, or
+send tool on this route.
+
+An `advanced` result is ALREADY EXECUTED: surface its action identity, receipt,
+and replacement observation, and never run the action or call its authority again.
+Only `campaign_attention_required` needs you — route its one selected campaign to
+`refill-sends-work-campaign` and return the chosen action through
+`refill_v3_continue`, which first revalidates the packet against fresh world
+state and then executes at most one existing authority.
+
+This skill chooses no sender, date, lane, campaign, or action, holds no counter or
+cursor between calls, and declares no terminal, exhaustion verdict, or health
+classification of its own. V1 `refill_sends` behavior is unchanged.