Releases: ark-forge/arkforge-agent-client
v1.6.0 — Fix Mode B receipt flow
Breaking change
Removed the auto-attach of ArkForge credit purchase receipts as payment_evidence.
Before (wrong): After agent.py credits, the Stripe receipt URL was saved locally and automatically attached to all subsequent scan and pay calls as payment_evidence.
After (correct): payment_evidence is only attached when explicitly passed via --receipt-url. The receipt must come from a direct Stripe payment to the provider — not from buying credits at ArkForge.
Why
ArkForge does not handle money. The two payment flows are completely separate:
- ArkForge credits: fee to ArkForge for the certification service (0.10 EUR/proof)
- Provider payment (Mode B): direct Stripe payment from agent to provider — the agent attaches this receipt to prove the payment
Attaching the ArkForge credit receipt as payment_evidence was architecturally incorrect.
Changes
- Removed:
RECEIPT_FILE,_save_receipt(),_load_receipt(),_key_mode() - Simplified:
_resolve_receipt()— only extracts explicit--receipt-url - Updated:
_cmd_credits()— displays receipt with clarifying note (not for Mode B) - Updated: docstring and help text
- Version: 1.6.0
v1.4.0 — Auto-attach Stripe receipt
What's new
Auto-receipt: after buying credits (credits command), the Stripe receipt URL is automatically saved locally and attached to subsequent scan/pay calls as payment evidence — zero extra flags needed.
Features
- Receipt auto-saved to
.last_receipt.jsonaftercreditspurchase - Auto-attached as
payment_evidenceonscanandpaycommands --receipt-url URLto override with a specific receipt--no-receiptto skip auto-attach for a single call.gitignoreadded (runtime state, pycache, logs, proofs)
Previous (v1.3.0)
--receipt-urlmanual flag for external receipt verification- Payment evidence display in scan/pay/verify output