@sellable/install 0.1.572-wip.hotfix-runtime-binding-contract.20260807222000 → 0.1.573

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.572-wip.hotfix-runtime-binding-contract.20260807222000",
+  "version": "0.1.573",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code, Codex, and Hermes",
   "bin": {

package/skill-templates/refill-sends.md

@@ -594,9 +594,9 @@ compatible range, and report the version before the first call. Call
 operator asked for `--yolo` — and call it again after each `advanced` or
 settled `campaign_attention_required` result. A `run_step_pending` result means
 the server is still completing the already-consumed step: wait its
-`retryAfterMs`, then call advance with that result's identical `runToken`.
-Never omit the token, open another run, route to AI, or execute an authority for
-this transport-reconciliation wait. `refill_v3_continue` itself
+`retryAfterMs`, then call advance with the same public inputs. The MCP retains
+the identical token internally; never copy a token, route to AI, or execute an
+authority for this transport-reconciliation wait. `refill_v3_continue` itself
 settles the exact packet action before it returns. Bounded enrichment and an
 already-active preparation job use the shared Create Campaign waiter and
 durable preparation owner; directly queued row repair uses the campaign waiter.
@@ -690,11 +690,16 @@ 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, executes at most one existing authority, and settles that exact campaign
-through the shared Create Campaign waiter before a sibling may be considered.
+For `campaign_attention_required`, first call `refill_v3_continue` with the
+same workspace/scope and no `decision`; the MCP supplies the exact retained
+packet and token. After fresh revalidation it owns live-job waiting,
+exact actionable enrichment, and same-template generation deterministically. If
+it returns `model_decision_required`, route that returned accurate packet to
+`refill-sends-work-campaign`, then call `refill_v3_continue` once with the
+chosen decision. This is the only
+ordinary model-decision boundary. The continuation executes at most one
+existing authority and settles that exact campaign through the shared Create
+Campaign waiter before a sibling may be considered.
 If it returns `attention_correction_required` with
 `correction.kind:"signal_keyword_collision"`, route the returned same packet
 and exact correction through `refill-sends-work-campaign` once, then call