@sellable/install 0.1.470 → 0.1.471

package/container/Dockerfile

@@ -3,12 +3,12 @@ FROM ${HERMES_IMAGE}
 
 USER root
 
-ARG INSTALLER_PACKAGE=@sellable/install@0.1.470
+ARG INSTALLER_PACKAGE=@sellable/install@0.1.469
 ARG MCP_PACKAGE=@sellable/mcp@0.1.760-wip.phase143.20260727100513
 ARG INSTALLER_INTEGRITY
 ARG MCP_INTEGRITY=sha512-muNXHuRnLTfsnW+MQUvK+p0VBZETDKeevr70iRliXyqE3/SLrZQJLL1laJzMo+qiUs9jMXMHdKOQfQqLiwJvtg==
 
-RUN test "${INSTALLER_PACKAGE}" = "@sellable/install@0.1.470" \
+RUN test "${INSTALLER_PACKAGE}" = "@sellable/install@0.1.469" \
     && test "${MCP_PACKAGE}" = "@sellable/mcp@0.1.760-wip.phase143.20260727100513" \
     && test -n "${INSTALLER_INTEGRITY}" \
     && test "$(npm view "${INSTALLER_PACKAGE}" dist.integrity)" = "${INSTALLER_INTEGRITY}" \
@@ -23,9 +23,9 @@ RUN test "${INSTALLER_PACKAGE}" = "@sellable/install@0.1.470" \
     && mkdir -p /opt/sellable-agent/install-root /opt/sellable-agent/mcp-root \
     && npm install --prefix /opt/sellable-agent/install-root --omit=dev --ignore-scripts --no-audit --no-fund "${INSTALLER_PACKAGE}" \
     && npm install --prefix /opt/sellable-agent/mcp-root --omit=dev --ignore-scripts --no-audit --no-fund "${MCP_PACKAGE}" \
-    && node --input-type=module -e "import { readFileSync } from 'node:fs'; const install = JSON.parse(readFileSync('/opt/sellable-agent/install-root/node_modules/@sellable/install/package.json')); const mcp = JSON.parse(readFileSync('/opt/sellable-agent/mcp-root/node_modules/@sellable/mcp/package.json')); if (install.name !== '@sellable/install' || install.version !== '0.1.470' || mcp.name !== '@sellable/mcp' || mcp.version !== '0.1.760-wip.phase143.20260727100513') throw new Error('package identity rejected');" \
+    && node --input-type=module -e "import { readFileSync } from 'node:fs'; const install = JSON.parse(readFileSync('/opt/sellable-agent/install-root/node_modules/@sellable/install/package.json')); const mcp = JSON.parse(readFileSync('/opt/sellable-agent/mcp-root/node_modules/@sellable/mcp/package.json')); if (install.name !== '@sellable/install' || install.version !== '0.1.469' || mcp.name !== '@sellable/mcp' || mcp.version !== '0.1.760-wip.phase143.20260727100513') throw new Error('package identity rejected');" \
     && node --input-type=module -e "import { buildExternalRuntimeClosure } from '/opt/sellable-agent/install-root/node_modules/@sellable/install/lib/sellable-agent/external-runtime-builder.mjs'; const built = buildExternalRuntimeClosure({ mcpPackageRoot: '/opt/sellable-agent/mcp-root/node_modules/@sellable/mcp', mcpNodeModulesRoot: '/opt/sellable-agent/mcp-root/node_modules', hermesSourceRoot: '/opt/hermes', ownerUid: 0, ownerGid: 0 }); if (!built.closureDigest) throw new Error('runtime closure rejected');" \
-    && node --input-type=module -e "import { chmodSync, writeFileSync } from 'node:fs'; const release = { installerPackage: '@sellable/install@0.1.470', installerIntegrity: process.argv[1], mcpPackage: '@sellable/mcp@0.1.760-wip.phase143.20260727100513', mcpIntegrity: process.argv[2] }; writeFileSync('/opt/sellable-agent/release.json', JSON.stringify(release) + '\\n', { mode: 0o444 }); chmodSync('/opt/sellable-agent/release.json', 0o444);" "${INSTALLER_INTEGRITY}" "${MCP_INTEGRITY}" \
+    && node --input-type=module -e "import { chmodSync, writeFileSync } from 'node:fs'; const release = { installerPackage: '@sellable/install@0.1.469', installerIntegrity: process.argv[1], mcpPackage: '@sellable/mcp@0.1.760-wip.phase143.20260727100513', mcpIntegrity: process.argv[2] }; writeFileSync('/opt/sellable-agent/release.json', JSON.stringify(release) + '\\n', { mode: 0o444 }); chmodSync('/opt/sellable-agent/release.json', 0o444);" "${INSTALLER_INTEGRITY}" "${MCP_INTEGRITY}" \
     && npm cache clean --force
 
 COPY entrypoint.sh /usr/local/bin/sellable-agent-container-entrypoint

package/container/README.md

@@ -3,13 +3,13 @@
 This image is a dedicated Agent worker/runtime boundary beside an existing Hermes dashboard. It never replaces or reconfigures the dashboard container.
 
 Build from this directory after
-`@sellable/install@0.1.470` is
+`@sellable/install@0.1.469` is
 published:
 
 ```sh
 docker build --platform linux/amd64 \
   --build-arg INSTALLER_INTEGRITY='sha512-…' \
-  --tag sellable-agent-host:0.1.470 .
+  --tag sellable-agent-host:0.1.469 .
 ```
 
 Create a private `bootstrap/` directory owned by root with mode `0700`. It must contain `bootstrap.json`, `provider-auth`, and `slack-app`, each owned by root with mode `0600`. `bootstrap.json` contains only non-secret identities, hashes, package integrities, and the control-plane URL. The other two files contain the provider JSON and global Slack app token whose hashes are pinned by `bootstrap.json`.

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

@@ -5,7 +5,7 @@ USER root
 
 ARG MCP_PACKAGE=@sellable/mcp@0.1.789-wip.phase159.20260729223403
 ARG MCP_INTEGRITY=sha512-KoheQcAQe/c8xzhF3R1ls6nQd11bcQqM3ykOUlzzNX5kykO7rO8RR2KsOvomwMv2Nn5VzvZZx6rGrle/6woKfw==
-ARG INSTALLER_PACKAGE=@sellable/install@0.1.470
+ARG INSTALLER_PACKAGE=@sellable/install@0.1.469
 ARG TUS_JS_CLIENT_VERSION=4.3.1
 ARG HERMES_VERSION=0.19.0
 ARG MCP_TRUST_ROOT_B64

package/lib/sellable-agent/fly-customer-image/customer-runtime.mjs

@@ -69,7 +69,7 @@ const RUNTIME_GENERATION = Number(
 const BOOT_SESSION_ID = randomUUID();
 const HERMES_VERSION = process.env.SELLABLE_AGENT_HERMES_VERSION ?? "0.19.0";
 const INSTALLER_PACKAGE =
-  process.env.SELLABLE_AGENT_INSTALLER_PACKAGE ?? "@sellable/install@0.1.470";
+  process.env.SELLABLE_AGENT_INSTALLER_PACKAGE ?? "@sellable/install@0.1.469";
 const MCP_PACKAGE =
   process.env.SELLABLE_AGENT_MCP_PACKAGE ??
   "@sellable/mcp@0.1.789-wip.phase159.20260729223403";

package/lib/sellable-agent/host-bootstrap.mjs

@@ -38,7 +38,7 @@ import { installAgentHostServices } from "./service-installer.mjs";
 const PACKAGE_ROOT = resolve(dirname(fileURLToPath(import.meta.url)), "../..");
 const VERSION = "sellable-agent-host-bootstrap/v1";
 const RECEIPT_VERSION = "sellable-agent-host-registration/v1";
-const INSTALLER_PACKAGE = "@sellable/install@0.1.470";
+const INSTALLER_PACKAGE = "@sellable/install@0.1.469";
 const MCP_PACKAGE = "@sellable/mcp@0.1.760-wip.phase143.20260727100513";
 const HERMES_VERSION = "0.18.0";
 const SHA256 = /^[a-f0-9]{64}$/;

package/lib/sellable-agent/host-worker.mjs

@@ -1540,7 +1540,7 @@ export function compileClaimToProfileDesired(activeClaim, config) {
       ]) ||
       pinned.hermesCli !== "hermes" ||
       pinned.hermesVersion !== "0.18.0" ||
-      pinned.installerPackage !== "@sellable/install@0.1.470" ||
+      pinned.installerPackage !== "@sellable/install@0.1.469" ||
       pinned.mcpPackage !==
         "@sellable/mcp@0.1.760-wip.phase143.20260727100513" ||
       !Array.isArray(policy.toolInclude) ||

package/lib/sellable-agent/profile-materializer.mjs

@@ -197,7 +197,7 @@ function validateDesired(desired) {
     desired.serviceCredentialGeneration < 1 ||
     desired.hermesCli !== "hermes" ||
     desired.hermesVersion !== "0.18.0" ||
-    desired.installerPackage !== "@sellable/install@0.1.470" ||
+    desired.installerPackage !== "@sellable/install@0.1.469" ||
     desired.mcpPackage !==
       "@sellable/mcp@0.1.760-wip.phase143.20260727100513" ||
     !Array.isArray(desired.toolInclude) ||

package/lib/sellable-agent/provisioning-adapter.mjs

@@ -25,7 +25,7 @@ import { fileURLToPath } from "node:url";
 import { deriveContainedProfileId } from "./profile-materializer.mjs";
 
 export const PROVISIONING_ACTION = "PROVISION_HERMES_PROFILE";
-export const PINNED_INSTALL_PACKAGE = "@sellable/install@0.1.470";
+export const PINNED_INSTALL_PACKAGE = "@sellable/install@0.1.469";
 export const PINNED_MCP_PACKAGE =
   "@sellable/mcp@0.1.760-wip.phase143.20260727100513";
 
@@ -612,7 +612,7 @@ function inspectProvisionedProfile({
       !matchesReadback(manifest, request) ||
       manifest.serviceCredentialReference !== serviceCredentialReference ||
       manifest.installerPackage !== PINNED_INSTALL_PACKAGE ||
-      manifest.installerVersion !== "0.1.470" ||
+      manifest.installerVersion !== "0.1.469" ||
       manifest.mcpPackage !== PINNED_MCP_PACKAGE ||
       manifest.credentialKeyVersion !== credentialKeyVersion ||
       !/^[a-f0-9]{16}$/.test(manifest.credentialFingerprint) ||
@@ -826,7 +826,7 @@ function successReceipt({
     subject: `agent-profile:${observed.profileId}`,
     cli: {
       installPackage: PINNED_INSTALL_PACKAGE,
-      installVersion: "0.1.470",
+      installVersion: "0.1.469",
       mcpPackage: PINNED_MCP_PACKAGE,
       command: "hermes profile bootstrap",
     },
@@ -874,7 +874,7 @@ function failure(code, stages, extra = {}, request = null) {
       : "agent-profile:unbound",
     cli: {
       installPackage: PINNED_INSTALL_PACKAGE,
-      installVersion: "0.1.470",
+      installVersion: "0.1.469",
       mcpPackage: PINNED_MCP_PACKAGE,
       command: "hermes profile bootstrap",
     },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.470",
+  "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.