Call runPaidAction('local.echo', {}, signer, {baseUrl:'http://127.0.0.1', fetch:localMock, maxAmount:500000000000000000n, timeoutMs:5, pollIntervalMs:1, onQuoted:id=>savedId=id}) with bearerToken omitted.

Use the ordinary valid IMD challenge (0.5 IMD, mainnet, Permit2, expiry now+80), return {order:{id:'order-1'}} from quote, matching capabilities, 202 {status:'payment_pending'} after the signed submit, and keep GET /requests/order-1 pending.

Reproduced: submit is accepted and onQuoted receives 'order-1', then the error is 'Timed out waiting for request order-1; query its status with the same bearer token'; its only own properties are stack and message.

The random bearer exists only in HTTP headers inside the transport, with no public return value/callback/error field.

Expected: the caller can retain the token before payment and resume this same paid order.

Using createMock() and the test wallet ('0x' + '12'.repeat(32)), quote local.echo and call createPayment(mock.challenge, signer, 500000000000000000n), recording the QuoteApproval typed data in signer.signTypedData.

Set payment.payload.permit2Authorization.deadline = Number(payment.payload.permit2Authorization.deadline).

Keep the Permit2 signature (the EIP-712 uint256 value is unchanged), recompute the key-sorted payment SHA-256, and re-sign QuoteApproval with that new paymentHash.

Submit this payment and quoteSignature to the local mock.

Reproduced actual result: deadlineType 'number', HTTP 202 {status:'payment_pending'}, mock.state.paid === true.

Expected per the stated IMD wire format: HTTP 400 invalid_payment_shape and paid === false.

Use a local injected fetch that returns a valid quote/challenge/capabilities and 202 payment_pending for the paid submit, but returns an unresolved Promise for GET /requests/order-1.

Call runPaidAction with a saved bearerToken, timeoutMs:10 and pollIntervalMs:1.

Reproduced: after 100 ms the paid call is still pending and the polling RequestInit has no signal; resolving the status request at that point with {status:'admitted'} makes it return that result.

Expected: reject with the timeout error after the polling budget expires, even while a GET or its response body is stalled.

Without editing any files, install a Node module load hook for dist/adapter.js that replaces 'return JSON.stringify(sorted(value));' with 'return JSON.stringify(value);', then import all three committed *.test.mjs files.

Verified that canonicalJson({z:1,a:2}) now returns '{"z":1,"a":2}' instead of the required sorted '{"a":2,"z":1}', yet all 10 tests still pass, including full quoted flow and the purported payment-hash test.

An ordinary payment is constructed in x402Version/resource/accepted/payload order, so this mutation also hashes normal payments incorrectly.

Expected: the compatibility test fails on the unsorted hash; actual: the shared mock changes its expected hash with the implementation and accepts it.

Run only test/client-compat.test.mjs with an in-memory module loader that inserts req.headers['payment-signature'] = 'deliberately-invalid-base64' immediately before exactKeys(data, ['quoteSignature']) in test/mock.mjs.

All five client tests still pass, including both wrapper tests, even though every wrapper retry now has an undecodable payment and therefore no verifiable witness signature or deadline.

Expected for the report's per-client tested claims: those payload checks fail; actual: the existing assertions cannot distinguish this from valid signing.

No repository files were modified for the reproduction.