examples(scenarios): HTTP-wire capture — cross-package integration test for the @x402 ↔ @x402r/evm seam

examples/package.json

@@ -17,6 +17,7 @@
     "scenario:atomic-charge": "tsx scenarios/atomic-charge.ts",
     "scenario:partial-refund-flow": "tsx scenarios/partial-refund-flow.ts",
     "scenario:permit2-charge": "tsx scenarios/permit2-charge.ts",
+    "scenario:http-wire-capture": "tsx scenarios/http-wire-capture.ts",
     "scenarios:ci": "tsx scripts/scenarios-ci.ts"
   },
   "dependencies": {
@@ -27,6 +28,13 @@
     "viem": "^2.46.3"
   },
   "devDependencies": {
-    "@types/node": "^22.12.0"
+    "@types/express": "^5.0.0",
+    "@types/node": "^22.12.0",
+    "@x402/core": "2.12.0",
+    "@x402/evm": "2.12.0",
+    "@x402/express": "2.12.0",
+    "@x402/fetch": "2.12.0",
+    "@x402r/evm": "0.2.0-alpha.0",
+    "express": "^5.0.0"
   }
 }

examples/scenarios/README.md

@@ -41,6 +41,20 @@ Demonstrates the atomic settlement path. In production the merchant advertises t
 
 The new authCapture partial-refund pattern. Replaces the old single-tx `refundInEscrow(amount)` with a two-tx flow: merchant captures the amount they keep, then `voidPayment()` returns the remainder to the payer. No allowance setup, no ReceiverRefundCollector — the escrow handles it. Asserts payer net loss equals merchant-keep, receiver delta + fee delta equals merchant-keep.
 
+### permit2-charge
+
+2-role atomic-charge flow routed through Uniswap Permit2 instead of EIP-3009.
+
+Demonstrates the two payer-side moves Permit2 requires: a one-time `ERC20.approve(PERMIT2, MAX)` so the canonical Permit2 contract can pull tokens for any Permit2 spender, then a per-payment `signPermit2Authorization(...)` that the merchant consumes via `payment.charge()`. Asserts payer ↓ amount, receiver Δ + fee Δ === amount, fee Δ > 0.
+
+### http-wire-capture
+
+Cross-package integration test exercising the real HTTP 402 wire end-to-end against an in-process facilitator and resource server.
+
+Boots `@x402/express`'s `paymentMiddleware` + `x402ResourceServer` (with `AuthCaptureServerScheme` from `@x402r/evm/authCapture/server`) on one port, `@x402/core`'s `x402Facilitator` (with `AuthCaptureFacilitatorScheme` from `@x402r/evm/authCapture/facilitator`) on another, and a payer client using `@x402/fetch`'s `wrapFetchWithPayment` + `AuthCaptureEvmScheme` from `@x402r/evm/authCapture/client`. The payer's `fetch` returns HTTP 402, the wrapper signs an authorization, retries, and the facilitator settles on-chain. Asserts the settle tx targets the canonical AuthCaptureEscrow, payer ↓ amount, receiver unchanged (autoCapture left unset), the `PaymentAuthorized` event's `paymentInfo` fields match the resource server's published requirements, and `paymentState(paymentInfoHash)` on the escrow has `hasCollectedPayment === true` and `capturableAmount === amount`.
+
+This is the only scenario that exercises the `@x402/express` ↔ `@x402r/evm` integration seam — wire-format mismatches, scheme registration drift, or signer-interface changes between the upstream packages and `@x402r/evm` surface here and nowhere else in the suite.
+
 ## Running
 
 ```bash
@@ -49,6 +63,8 @@ pnpm scenario:capture
 pnpm scenario:dispute
 pnpm scenario:atomic-charge
 pnpm scenario:partial-refund-flow
+pnpm scenario:permit2-charge
+pnpm scenario:http-wire-capture
 ```
 
 All scenarios run against a local Anvil fork — no real testnet funds needed.