@sellable/install 0.1.430 → 0.1.431-wip.146.20260728003748

package/bin/sellable-install.mjs

@@ -40,7 +40,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.72";
+const CODEX_PLUGIN_VERSION = "0.1.71";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -96,7 +96,6 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.68",
   "0.1.69",
   "0.1.70",
-  "0.1.71",
   "0.1.70-phase981.20260711223346+codex.20260712010246",
 ];
 const RAW_INSTALL_PACKAGE_SPEC =
@@ -1194,6 +1193,9 @@ const CREATE_EVERGREEN_CAMPAIGNS_ALLOWED_TOOLS = [
 ];
 
 const REFILL_SENDS_ALLOWED_TOOLS = [
+  "mcp__sellable__refill_v3_sender_date_eligibility",
+  "mcp__sellable__refill_v3_supply_assessment",
+  "mcp__sellable__refill_v3_workspace_inventory",
   "mcp__sellable__refill_sends",
   "mcp__sellable__get_auth_status",
   "mcp__sellable__start_cli_login",

package/container/Dockerfile

@@ -3,13 +3,13 @@ FROM ${HERMES_IMAGE}
 
 USER root
 
-ARG INSTALLER_PACKAGE=@sellable/install@0.1.430
-ARG MCP_PACKAGE=@sellable/mcp@0.1.760-wip.phase143.20260727100513
+ARG INSTALLER_PACKAGE=@sellable/install@0.1.418
+ARG MCP_PACKAGE=@sellable/mcp@0.1.644
 ARG INSTALLER_INTEGRITY
-ARG MCP_INTEGRITY=sha512-muNXHuRnLTfsnW+MQUvK+p0VBZETDKeevr70iRliXyqE3/SLrZQJLL1laJzMo+qiUs9jMXMHdKOQfQqLiwJvtg==
+ARG MCP_INTEGRITY=sha512-Q2+bBeQCKy/tZ9hMslOZ1Tw/kTLKBjiv77zQqX38IFrNevLiOhRG4rsxvVPqfHkOIIOSKFl/ECTgFD0pcmhAXg==
 
-RUN test "${INSTALLER_PACKAGE}" = "@sellable/install@0.1.430" \
-    && test "${MCP_PACKAGE}" = "@sellable/mcp@0.1.760-wip.phase143.20260727100513" \
+RUN test "${INSTALLER_PACKAGE}" = "@sellable/install@0.1.418" \
+    && test "${MCP_PACKAGE}" = "@sellable/mcp@0.1.644" \
     && test -n "${INSTALLER_INTEGRITY}" \
     && test "$(npm view "${INSTALLER_PACKAGE}" dist.integrity)" = "${INSTALLER_INTEGRITY}" \
     && test "$(npm view "${MCP_PACKAGE}" dist.integrity)" = "${MCP_INTEGRITY}" \
@@ -23,9 +23,9 @@ RUN test "${INSTALLER_PACKAGE}" = "@sellable/install@0.1.430" \
     && 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.430' || 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.418' || mcp.name !== '@sellable/mcp' || mcp.version !== '0.1.644') 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.430', 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.418', installerIntegrity: process.argv[1], mcpPackage: '@sellable/mcp@0.1.644', 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.430` is
+`@sellable/install@0.1.418` is
 published:
 
 ```sh
 docker build --platform linux/amd64 \
   --build-arg INSTALLER_INTEGRITY='sha512-…' \
-  --tag sellable-agent-host:0.1.430 .
+  --tag sellable-agent-host:0.1.418 .
 ```
 
 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/external-runtime-builder.mjs

@@ -28,7 +28,7 @@ import {
 
 const MANIFEST_VERSION = "sellable-agent-external-runtime-closure/v1";
 const MCP_PACKAGE = "@sellable/mcp";
-const MCP_VERSION = "0.1.760-wip.phase143.20260727100513";
+const MCP_VERSION = "0.1.644";
 const SAFE_COMPONENT = /^[A-Za-z0-9@._+-]+$/;
 const HERMES_EXCLUDES = new Set([".git", ".playwright", "node_modules"]);
 

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

@@ -3,9 +3,9 @@ FROM ${HERMES_IMAGE}
 
 USER root
 
-ARG MCP_PACKAGE=@sellable/mcp@0.1.771
-ARG MCP_INTEGRITY=sha512-8+N7NpFenz9QYCtGqE0IVIsj9ZaKEzu3NxbIYwjWqrAMLyB5yiCKtW0+/VYrkkrjnkFrbukaIIvwHr3jDTq7eg==
-ARG INSTALLER_PACKAGE=@sellable/install@0.1.430
+ARG MCP_PACKAGE=@sellable/mcp@0.1.755
+ARG MCP_INTEGRITY=sha512-ryrP8FpK+4LjnqqeCTnP8+6bZwPk9u7Owtw/orEJVM9SOLJ7q8FjA/ox5ySLq79GTtAlIID5HC6vOpsvLqhQtA==
+ARG INSTALLER_PACKAGE=@sellable/install@0.1.418
 ARG HERMES_VERSION=0.19.0
 ARG MCP_TRUST_ROOT_B64
 ARG TIRITH_VERSION=0.3.3

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

@@ -62,9 +62,9 @@ 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.430";
+  process.env.SELLABLE_AGENT_INSTALLER_PACKAGE ?? "@sellable/install@0.1.418";
 const MCP_PACKAGE =
-  process.env.SELLABLE_AGENT_MCP_PACKAGE ?? "@sellable/mcp@0.1.771";
+  process.env.SELLABLE_AGENT_MCP_PACKAGE ?? "@sellable/mcp@0.1.755";
 
 const sha256 = (value) => createHash("sha256").update(value).digest("hex");
 const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));

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

@@ -38,8 +38,9 @@ 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.430";
-const MCP_PACKAGE = "@sellable/mcp@0.1.760-wip.phase143.20260727100513";
+const INSTALLER_PACKAGE =
+  "@sellable/install@0.1.418";
+const MCP_PACKAGE = "@sellable/mcp@0.1.644";
 const HERMES_VERSION = "0.18.0";
 const SHA256 = /^[a-f0-9]{64}$/;
 const SHA256_16 = /^[a-f0-9]{16}$/;

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

@@ -1513,9 +1513,9 @@ export function compileClaimToProfileDesired(activeClaim, config) {
       ]) ||
       pinned.hermesCli !== "hermes" ||
       pinned.hermesVersion !== "0.18.0" ||
-      pinned.installerPackage !== "@sellable/install@0.1.430" ||
-      pinned.mcpPackage !==
-        "@sellable/mcp@0.1.760-wip.phase143.20260727100513" ||
+      pinned.installerPackage !==
+        "@sellable/install@0.1.418" ||
+      pinned.mcpPackage !== "@sellable/mcp@0.1.644" ||
       !Array.isArray(policy.toolInclude) ||
       policy.toolInclude.length === 0 ||
       !Number.isSafeInteger(slack.generation) ||

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

@@ -23,12 +23,12 @@ import {
   relative,
   resolve,
 } from "node:path";
+import { HERMES_AGENT_BRIDGE_CONTRACT } from "./hermes-bridge.mjs";
 import {
   FLY_CUSTOMER_MODEL_ID,
   FLY_CUSTOMER_MODEL_PROVIDER,
   FLY_CUSTOMER_MODEL_REASONING_EFFORT,
 } from "./fly-customer-model.mjs";
-import { HERMES_AGENT_BRIDGE_CONTRACT } from "./hermes-bridge.mjs";
 
 export const PROFILE_MATERIALIZER_PORTS = Object.freeze({
   hostAppSecret: ["resolveHostSecret"],
@@ -192,9 +192,9 @@ function validateDesired(desired) {
     desired.serviceCredentialGeneration < 1 ||
     desired.hermesCli !== "hermes" ||
     desired.hermesVersion !== "0.18.0" ||
-    desired.installerPackage !== "@sellable/install@0.1.430" ||
-    desired.mcpPackage !==
-      "@sellable/mcp@0.1.760-wip.phase143.20260727100513" ||
+    desired.installerPackage !==
+      "@sellable/install@0.1.418" ||
+    desired.mcpPackage !== "@sellable/mcp@0.1.644" ||
     !Array.isArray(desired.toolInclude) ||
     desired.toolInclude.length === 0 ||
     desired.toolInclude.some((tool) => !/^[a-z][a-z0-9_]{0,127}$/.test(tool)) ||

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

@@ -25,9 +25,9 @@ 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.430";
-export const PINNED_MCP_PACKAGE =
-  "@sellable/mcp@0.1.760-wip.phase143.20260727100513";
+export const PINNED_INSTALL_PACKAGE =
+  "@sellable/install@0.1.418";
+export const PINNED_MCP_PACKAGE = "@sellable/mcp@0.1.644";
 
 export function deriveAgentProfileId(workspaceId, agentId, hostId) {
   return deriveContainedProfileId(workspaceId, agentId, hostId);
@@ -612,7 +612,8 @@ function inspectProvisionedProfile({
       !matchesReadback(manifest, request) ||
       manifest.serviceCredentialReference !== serviceCredentialReference ||
       manifest.installerPackage !== PINNED_INSTALL_PACKAGE ||
-      manifest.installerVersion !== "0.1.430" ||
+      manifest.installerVersion !==
+        "0.1.418" ||
       manifest.mcpPackage !== PINNED_MCP_PACKAGE ||
       manifest.credentialKeyVersion !== credentialKeyVersion ||
       !/^[a-f0-9]{16}$/.test(manifest.credentialFingerprint) ||
@@ -826,7 +827,7 @@ function successReceipt({
     subject: `agent-profile:${observed.profileId}`,
     cli: {
       installPackage: PINNED_INSTALL_PACKAGE,
-      installVersion: "0.1.430",
+      installVersion: "0.1.418",
       mcpPackage: PINNED_MCP_PACKAGE,
       command: "hermes profile bootstrap",
     },
@@ -874,7 +875,7 @@ function failure(code, stages, extra = {}, request = null) {
       : "agent-profile:unbound",
     cli: {
       installPackage: PINNED_INSTALL_PACKAGE,
-      installVersion: "0.1.430",
+      installVersion: "0.1.418",
       mcpPackage: PINNED_MCP_PACKAGE,
       command: "hermes profile bootstrap",
     },

package/package.json

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

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

@@ -0,0 +1,24 @@
+---
+name: refill-sends-evergreen
+description: Deprecated alias for refill-sends-v2.
+visibility: public
+allowed-tools:
+  - mcp__sellable__get_subskill_prompt
+---
+
+# Refill Sends Evergreen
+
+Superseded by refill-sends-v2. The prompt name now redirects through
+`DEPRECATED_SUBSKILL_PROMPT_REPLACEMENTS`; do not call this deprecated prompt
+directly.
+
+Use `refill-sends-v2` instead:
+
+```text
+get_subskill_prompt({ subskillName: "refill-sends-v2" })
+```
+
+The alias must not strip exact `targetConfig`, server `runHandle`,
+`reportingContext`, canonical `refill_reporting.v2`, or an explicit
+`messageTemplateRevision`. It never infers revision authority from
+`forceRerun`.

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

@@ -0,0 +1,207 @@
+---
+name: refill-sends-v2
+description: Execute refill sends v2 through the fenced evergreen refill loop, with dry-run and resume support.
+visibility: public
+allowed-tools:
+  - mcp__sellable__refill_sends_v2
+  - mcp__sellable__get_refill_plan_v2
+  - mcp__sellable__get_subskill_prompt
+  - mcp__sellable__get_subskill_asset
+  - mcp__sellable__get_auth_status
+  - mcp__sellable__get_active_workspace
+  - mcp__sellable__list_workspaces
+  - mcp__sellable__get_workspace
+---
+
+# Refill Sends V2
+
+Use this command for refill requests such as "refill sends", "fill evergreen
+senders", "load everyone up", "run Damiano", or "show a dry run for this
+workspace".
+
+Host command names:
+
+- Claude Code: `/sellable:refill-sends-v2`
+- Codex: `$sellable:refill-sends-v2`
+
+`refill_sends_v2` is the execution surface. In real-run mode it starts or
+resumes a fenced refill run, reads a fresh packet, executes only the packet's
+named bounded work, verifies the result, and returns either a terminal report, a
+blocked report, or an in-progress resume handle. In dry-run mode it stays
+read-only and writes only a dry-run journal.
+
+## Entry
+
+Resolve the explicit `workspaceId` from the request, automation config, or
+active workspace readback. Scheduled or autonomous usage must carry
+`workspaceId` on every tool call. If the workspace is missing or ambiguous, stop
+with `WORKSPACE_REQUIRED`; do not switch the shared active workspace.
+
+For a real refill run:
+
+```text
+refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode? })
+```
+
+For read-only inspection:
+
+```text
+refill_sends_v2({ workspaceId, dryRun:true, intent:"auto", senderIds? })
+```
+
+To resume an in-progress run, pass the handle back exactly:
+
+```text
+refill_sends_v2({ workspaceId, runHandle:{runId,fence}, targetConfig, reportingContext, messageTemplateRevision? })
+```
+
+`targetConfig` and the server-issued `runHandle` are separate authorities. Keep
+both byte-for-byte through every continuation and takeover; never fold the
+rotating fence into target configuration.
+
+An approved copy change is reachable only through an explicit
+`messageTemplateRevision` object with `version:1`, `source:"user_approved"`,
+the approved `templateMarkdown`, `messageTemplateRevision` identity,
+`priorTemplateAuthorityDigest`, `nextTemplateAuthorityDigest`, 1–500 exact
+`cohortRowIds`, and `requestId`, `effectId`, and `revisionOperationId`. Pass it
+with the exact `targetConfig` and `reportingContext`; the command obtains or
+resumes the server run handle and lets the planner name
+`revise_message_template_and_rerun`. Missing or partial input means no revision.
+`forceRerun:true` on a queue operation never authorizes or implies a template
+change.
+
+After a committed and dispatched revision receipt, continue only with the
+planner-provided revision-derived `approve_messages` action. It must preserve
+the exact revision cohort as `rowSelector:{type:"rowIds",rowIds:[...]}` plus
+`approvalMode:"approve"`, the compiled readiness identity, and the canonical
+`reportingContext`, even when the ordinary sender lane is ineligible. Do not
+replace it with `queue_campaign_cells` on Approved cells; that path cannot mint
+the authoritative approval/lane-scope receipt. Require `laneScope` in the
+bounded preparation receipt before the lane is considered approved. A
+disconnected or zero-capacity sender still blocks scheduling and does not
+authorize reconnecting, campaign start, or direct send.
+
+If a stale handle loses the lease, the tool reports the holder status and the
+approximately 10 minute lockout window. Reinvoke with the current handle or wait
+for lease expiry; never guess a fence.
+
+The default `intent:"auto"` inspects `managed_waterfall`,
+`dashboard_evergreen`, and `active_campaign` lane sources. Report the lane
+source and lane chain as proof for every selected sender.
+Connection-only evergreen lanes are invite-only refill targets. When the packet
+or campaign proof shows exactly `["send_invite"]`, report and execute only
+`selectedLane:"send_invite"` work; do not infer DM, InMail, Sales Nav cascade,
+paid-credit refresh, message generation, follow-up, sequence mutation,
+launch/start beyond packet authority, scheduler writes, or direct sends.
+
+If membership blocks a workspace read, report the structured
+`workspace_access` blocker instead of retrying auth or switching workspaces.
+
+## Authority
+
+The run may execute only packet-named bounded work:
+
+- approve generated messages that are ready for review (`approve_messages`);
+- enrich the next batch of unenriched rows (`enrich_more`);
+- copy leads already found into the campaign table (`reconcile_source_copy`);
+- re-run errored enrichment/message cells (`rerun_errored_cells`);
+- find more leads via this campaign's original source (`add_leads_same_source`)
+  only for mechanical same-source continuations;
+- start the paused campaign so ready rows can schedule (`start_campaign`) only
+  when the campaign is in the packet's pinned lane chain;
+- refresh paid InMail credit facts during bootstrap and once per scheduler-wait
+  entry when the packet requires it.
+- apply `revise_message_template_and_rerun` only when the packet contains the
+  complete explicit user-approved revision envelope and exact fenced target.
+- after that revision commits, apply only its exact-row, readiness-bound
+  `approve_messages` continuation and require the returned lane-scope receipt.
+
+The loop records planned -> did -> outcome before and after every foreign
+mutation. It refuses stale packets by fingerprint and validates packet
+coherence before dispatch. The planner owns repair decisions: if a batch needs
+repair, the next packet names the repair rung; the loop bounds and refuses, it
+does not improvise fixes.
+
+Do not create campaigns, switch provider families, lower thresholds, write
+scheduler fields, send messages, archive/delete campaigns, or mutate
+brief/filter/message/sequence/sender config unless a separate exact approval
+packet explicitly authorizes that work. In short: no campaign creation, no
+provider-family switch, no threshold lowering, no scheduler writes, no
+launch/send/archive/delete, and no brief/filter/message/sequence/sender
+mutation.
+
+## Continuations
+
+Sales Nav and Prospeo source continuations that are not yolo-safe are blocked
+as executable scoped handoffs. The report will include text shaped like:
+
+```text
+$sellable:create-campaign [campaignId]
+```
+
+That handoff is run in a separate thread only after explicit approval. Scope is
+strict: add leads through this campaign's existing source, keep the same
+saved-search identity, import mode `add` into the same source list, and do
+source work only. It is never a new campaign, provider-family switch, brief
+change, rubric change, message change, sequence change, or sender change.
+
+## Verification
+
+The loop verifies whole rows before replanning. It reattaches to an own active
+prep job instead of re-dispatching, waits on foreign prep jobs without adopting
+their outcomes, waits on active enrichment/import work by rereading the packet,
+and treats capped scheduler capacity as complete.
+
+Scheduler waits are cross-invocation. Each tool call polls briefly under the
+host guard, heartbeats the run lease, and may return:
+
+```text
+{ status:"in_progress", runId, fence, gate, guidance }
+```
+
+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
+`pipelineDiagnosis.firstFailing`. If the verdict is honest rubric failure, the
+human decision is to update the rubric or change lead source; refill does not
+mutate those automatically.
+
+## Results
+
+Terminal reasons are:
+
+- `complete`
+- `capped_by_scheduler`
+- `loaded_awaiting_scheduler`
+- `lanes_exhausted`
+- `blocked`
+- `no_refillable_campaigns`
+- `not_an_evergreen_workspace`
+
+Report campaign names and sender names first, ids second. Include the terminal
+reason or resume handle, lane source, lane chain, chosen label with token
+secondary, plan revision, journal path, blocked continuation packets, and
+firstFailing checklist when present.
+
+Preserve `refill_reporting.v2` exactly in progress, continuation, replay, and
+terminal results. Do not recompute its semantic counts or drop live-preparation
+epoch, snapshot sequence, reset reason, watermark, blockers, compatibility, or
+terminal fields. Never surface raw prospect or message-copy fields.
+
+Real-run journals live under `~/.sellable/refill/runs` by default and append an
+index line. Dry runs include the dry marker and do not create run records.

package/skill-templates/refill-sends.md

@@ -3,6 +3,9 @@ name: refill-sends
 description: Refill projected sends across a workspace or selected senders through the canonical fenced coordinator.
 visibility: public
 allowed-tools:
+  - mcp__sellable__refill_v3_sender_date_eligibility
+  - mcp__sellable__refill_v3_supply_assessment
+  - mcp__sellable__refill_v3_workspace_inventory
   - mcp__sellable__refill_sends
   - mcp__sellable__get_refill_target_plan
   - mcp__sellable__get_scheduler_fill_capacity
@@ -30,6 +33,53 @@ Host commands:
 - Claude Code: `/sellable:refill-sends`
 - Codex: `$sellable:refill-sends`
 
+## Refill v3 Calls 1–3a — progressive observation gate
+
+For every new fill or refill intent, use this gate instead of the legacy flow
+below while the Refill v3 observation rollout is current:
+
+1. Call `get_auth_status`. If Sellable authentication is not valid, run only
+   the returned login flow and recheck authentication.
+2. Load
+   `get_subskill_asset({ subskillName: "refill-sends", assetPath: "core/flow.v3.json" })`
+   completely. Require `workflow:"refill-sends-v3"` and `version:3`. Follow
+   only the current state's `allowedTools`, `doNotLoad`, and transition.
+3. Resolve the exact workspace by explicit ID, exact name, install mapping, or
+   an unambiguous accessible-workspace match using `get_active_workspace` and
+   `list_workspaces`. Never change the active workspace.
+4. Call
+   `refill_v3_workspace_inventory({ workspaceId, detail: "concise" })` exactly
+   once.
+5. For each globally eligible sender and requested sender-local date, call
+   `refill_v3_sender_date_eligibility` exactly once with the server-issued
+   `runId` and `fence`. Never call it for a globally ineligible sender.
+6. Only for a positively eligible lane, call `refill_v3_supply_assessment`
+   exactly once for each campaign/lane tuple issued by inventory. Pass the
+   backend-applied quota as the assessment bound; never invent or substitute a
+   campaign, lane, sender, date, run identity, or fence.
+7. Render the complete inventory, sender/date eligibility, and supply result,
+   including every typed blocker, then stop at `observed` or `blocked`.
+
+A sender whose LinkedIn account is connected but whose Sales Navigator status
+is disconnected remains eligible for real non-Sales-Nav lanes. For Thomas or
+any equivalent sender, paid InMail must return `sales_nav_disconnected` at
+eligibility and transition directly to terminal `blocked`: do not call supply,
+refresh a provider, invoke Sales Navigator, or schedule or place anything.
+
+Do not load `refill-sends-workflow`, call `get_refill_target_plan`, or call
+`refill_sends` for a new fill or refill intent at this rollout stage. Calls 1–3a
+are backend-owned observation calls; they may append their fenced decision
+ledger and Call 2 may perform its bounded single-flight paid-credit cache
+refresh. They never approve or enrich rows, acquire supply, change campaign
+state, invoke a Sales Navigator provider action, schedule, place, or send.
+Between calls, retain the server-issued `runId` and `fence`; never reconstruct
+downstream policy in the host.
+
+The legacy sections below remain reference documentation for explicitly
+authorized legacy execution only. `refill_sends` remains the only mutation
+execution owner on that legacy path; this observation gate does not introduce
+another mutation owner.
+
 ## Entry and exact scope
 
 Accepted request fields are `--yolo`, `workspaceId`, `--sender`/`senderIds`/
@@ -76,7 +126,7 @@ get_subskill_asset({ subskillName: "refill-sends-workflow", assetPath: "core/flo
 
 Continue chunks until `hasMore:false`; require `workflow:"refill-sends-workflow"`
 and a COMPATIBLE version: same major (`v1`) and minor at or above the minimum
-`v1.9` — so `v1.9`, `v1.10` pass while `v1.8` and `v2.x` do not. Report the
+`v1.8` — so `v1.8`, `v1.9`, `v1.10` all pass and `v2.x` does not. Report the
 verified version before D1. A missing, unparseable, wrong-major, or
 below-minimum version is `workflow_version_mismatch`: stop before
 `get_refill_target_plan` or mutation. Do NOT require exact string equality: the
@@ -400,7 +450,7 @@ flowchart TD
     DATE -- No --> WAIT["Enter coordinator-owned bounded scheduler wait"]
     SWEEP --> RECEIPT{"Receipt state?"}
     RECEIPT -- Terminal --> READ["Canonical target-plan and request/effect readback"]
-    RECEIPT -- Active --> POLL["Return in_progress and poll only the same request key"]
+    RECEIPT -- Active --> POLL["Poll only issued continuation until wait.deadlineAt"]
     RECEIPT -- uncertain_outcome --> RECON["Reconcile same request key read-only; never redispatch"]
     POLL --> RECEIPT
     RECON --> TERM["Terminal: blocked_retryable with request identity intact"]
@@ -410,7 +460,7 @@ flowchart TD
     FULL -- No --> READY{"Ready buffer still covers gap?"}
     READY -- Yes --> OTHER{"Any other workspace target still needs preparation or an executable gate?"}
     OTHER -- Yes --> PREP["Continue next planner-ranked exact target"]
-    OTHER -- No --> BLOCK["Terminal: receipt-backed blocked_retryable scheduler gap"]
+    OTHER -- No --> LOADED["Terminal: loaded_awaiting_scheduler"]
     READY -- No --> PREP["Return to row lifecycle"]
 ```
 
@@ -422,11 +472,7 @@ allocation-attempt count`; `readyCellsFound` is prefilter inventory. Inspect
 closed-InMail cells with stale paid-credit evidence, use
 `refresh_paid_inmail_credits_then_rerun`. `wait_for_capacity_or_window` means do
 not source or prep more rows; `no_ready_cells_continue_refill_prep` returns to
-the row lifecycle. `cellsScheduled:0` alone is not failure. Once a sweep is
-dispatched, a host wait budget yields an `in_progress` continuation carrying
-the same run identity. Keep polling that request key until its official
-terminal receipt, then reread the full target plan. Never convert an active
-sweep into `loaded_awaiting_scheduler`.
+the row lifecycle. `cellsScheduled:0` alone is not failure.
 
 ## Explicit message-template revision
 
@@ -491,12 +537,15 @@ flowchart TD
 ```
 
 One scheduler-loaded exact lane is not a workspace terminal: skip it and
-continue other planner-ranked lanes. Workspace `loaded_awaiting_scheduler` is
-admissible only when no refill-owned scheduler request is active. After refill
-dispatches a sweep, keep the same fence alive until the official terminal
-receipt; then return `complete` from the post-receipt readback or a concrete
-receipt-backed retryable scheduler blocker if coverage remains short. The sole
-refill-ladder expansion
+continue other planner-ranked lanes. Do not keep polling after the coordinator
+returns workspace `loaded_awaiting_scheduler`. That terminal is admissible by
+either path: every remaining exact target is complete or scheduler-owned and
+workspace `remainingReadyOrProjectedGap` is zero, OR every gap-bearing sender
+lane is already prepared and its residue is `ready_to_schedule` surplus, so the
+remaining gap is scheduler/pacing-bound rather than unexposed supply — on that
+second path `remainingReadyOrProjectedGap` is not necessarily zero. Neither path
+means unexposed actionable supply, and neither is permission for a host-owned
+loop. The sole refill-ladder expansion
 that asks the user in `--yolo` is `new_campaign_required`; refill itself never
 creates that campaign. `new_campaign_required` is also the truthful terminal
 when receipts prove every existing lane is spent but the planner has no