primcli 1.11.0 → 1.13.0

package/README.md

@@ -98,8 +98,16 @@ cat challenge.json | primitive payments pay
 # 1,000,000: 0.01 USDC is --amount 10000.
 primitive payments create-email-challenge --from payee@your-domain.example \
   --to payer@their-domain.example --amount 10000 --network base-sepolia
-# Payer: sign a received email challenge into an interaction.json payment step.
-# This does NOT send; attach the output to your reply (e.g. with `primitive reply`).
+# Payer (recommended): pay the email challenge in one step. Signs the challenge
+# locally with your wallet key AND sends the signed interaction.json as an
+# in-thread reply, so you skip the manual sign-then-reply dance. --in-reply-to
+# is the inbound challenge email you received; the reply is threaded to it and
+# addressed to the payee, and From defaults to the payer it was sent to.
+primitive payments pay-email --challenge-file challenge.json \
+  --in-reply-to <inbound-challenge-email-id> --wait
+
+# Advanced: sign only, without sending. Emits the portable interaction.json
+# artifact you can attach to a reply yourself (e.g. with `primitive reply`).
 primitive payments pay-email-step --challenge-file challenge.json > interaction.json
 
 # Inspect a challenge by id, or list your registered payout addresses.
@@ -114,7 +122,7 @@ primitive payments update-spend-policy --max-per-payment 5000000
 
 `charge` is the friendly verb that matches the SDK `charge` and accepts `--amount-usdc`; `create-challenge` is the lower-level command that takes base-unit `--amount`. Either creates a challenge. The signing commands print a human-readable summary by default; pass `--json` for raw JSON suitable for piping.
 
-The two signing commands (`register-payout-address` and `pay`) need your wallet key. Set it in `PRIMITIVE_X402_PRIVATE_KEY` (a `0x`-prefixed hex private key) so it never lands in shell history or the process list:
+The signing commands (`register-payout-address`, `pay`, `pay-email`, and `pay-email-step`) need your wallet key. `pay-email` is the recommended payer path for the email-native flow: it signs and replies in one step. `pay-email-step` signs only and emits the `interaction.json` artifact for advanced use where you want to deliver it yourself. Set the key in `PRIMITIVE_X402_PRIVATE_KEY` (a `0x`-prefixed hex private key) so it never lands in shell history or the process list:
 
 ```bash
 export PRIMITIVE_X402_PRIVATE_KEY=0x...