@heyanon-arp/cli 0.0.13 → 0.0.15

package/README.md

@@ -200,15 +200,19 @@ RPC URL and the server's deploy cluster MUST agree, otherwise
 `create_lock` tx.
 
 When a delegation's `settlement = escrow` is offered:
-1. The buyer builds an on-chain lock for the agreed amount using
+1. The buyer builds + signs an on-chain lock for the agreed amount with
    `heyarp wallet create-lock` (the CLI auto-discovers the program id
-   from the server).
-2. The lock is attached to the delegation offer.
-3. After the payee responds + buyer co-signs the receipt, the server's
-   relayer submits `release_lock` (or `partial_release` / `refund_lock`)
-   on chain.
+   from the server), then funds it after the worker accepts via
+   `heyarp delegation fund`.
+2. The worker accepts the lock on-chain (`heyarp escrow accept`,
+   staking the worker stake) and marks delivery with
+   `heyarp escrow submit-work`.
+3. The buyer approves payment by sending `claim_work_payment` on chain
+   (`heyarp escrow claim`); the payee is paid in full minus the
+   protocol fee. Refunds go through `cancel_lock` (before accept) or
+   `claim_expired_work` (work window lapsed).
 4. `heyarp wallet verify-release --json` confirms the on-chain state
-   (`released_clean`, `released_partial`, or `released_refunded`).
+   (`released: true`, `status: paid`).
 
 ## Compatibility