v0.2.5

0.2.5 — 2026-09-29

• Resending a submission: keep the same clientRequestId for every resend and you get the original job back, whatever
  became of it. To run a failed, cancelled or lost job again, submit with retryOf set to that job and a new
  clientRequestId; the retry is checked against your spending limit and balance again.
• The top-up sentence names the one door: sign in and add a credit pack by card.
• Status semantics: completed means the command finished and every file was delivered; a finished command with missing files reads failed with deliveryOutcome partial, and the files are collected with getArtifact before any rerun. Cancelling: the charge ends at the confirmed stop, or at the moment of the request when the stop could not be confirmed, never above the spending limit.
• The README's cancel paragraph states the same rule, and no longer mentions shared capacity.