mppx 0.0.0-main-20260715214817

package/CHANGELOG.md

@@ -0,0 +1,841 @@
+# mppx
+
+## 0.0.0-main-20260715214817
+
+### Patch Changes
+
+- c40a0fc: Added continuous `main` snapshot releases.
+- 7207c0f: Added local Tempo charge fee-token selection with a pathUSD preference and an explicit override.
+- 98abd92: Extracted session SSE payment handling into a response-preserving driver.
+
+## 0.8.10
+
+### Patch Changes
+
+- a6969b8: Added account resolution to Tempo session managers.
+- fa73305: `mppx validate`: retry on 422, resolve `$ref` in body generation, add `--header`/`-H` flag, fix x402 validation for non-EVM chains.
+
+## 0.8.9
+
+### Patch Changes
+
+- 978f580: Fixed hosted fee-payer relays for TIP-1034 session opens and top-ups.
+- 2fb3fa8: Normalize hosted fee-payer JSON-RPC signature parity before recovery.
+
+## 0.8.8
+
+### Patch Changes
+
+- be7d166: `mppx validate`: Stripe testmode payment support. Auto-detects Stripe CLI test keys and completes card payment flows end-to-end using a test card, with graceful livemode detection.
+
+## 0.8.7
+
+### Patch Changes
+
+- 38c8229: Added Celo and Celo Sepolia to known EVM chains and assets: `chains.celo`, `chains.celoSepolia`, `assets.celo.USDC`, `assets.celo.USDT`, and `assets.celoSepolia.USDC`.
+- 264f079: Fixed session voucher replay checks for settled vouchers and mismatched credential sources.
+- 89bd31e: Fixed empty Tempo session voucher POSTs being treated as application requests by HTTP adapters that expose empty body streams.
+- 33a7c52: Updated client negotiation to prefer Payment-auth challenges before x402 challenges.
+- d3d9d81: `mppx validate`: Multi-challenge support (parses all payment methods from WWW-Authenticate), per-method field validation for Stripe/EVM/Tempo, streaming CLI output, fixed URL resolution for subpaths, and improved error reporting for malformed challenges.
+- 1157a26: `mppx validate`: EVM payment testing support. Uses the same wallet as Tempo to sign EIP-3009 authorizations, with pre-flight ERC-20 balance checks and chain-aware explorer links.
+- fd45726: Added programmatic validation API (`mppx/validation` export), OpenAPI path parameter substitution, x402 protocol detection, multi-path discovery fallback, and `--outputJson` CLI flag.
+- 86eb98c: `mppx validate`: Stream results as each phase completes instead of batching until the end. Discovery and challenge checks now appear before the payment prompt.
+
+## 0.8.6
+
+### Patch Changes
+
+- adf5207: Preserve raw response bytes when writing CLI response bodies to stdout.
+- 5e27d04: Fixed payment-aware fetch to return a post-payment `402` response with no actionable challenge instead of throwing `No method found for challenges`.
+- 8958754: Fixed Tempo session receipt waits after consecutive same-nonce transactions.
+- a2bfcc5: Normalize sponsored Tempo charge transactions before client signing.
+- 591ecf4: Preserved method-specific extension fields on receipts. `Receipt.from`, `Receipt.deserialize`, and `Receipt.fromResponse` previously stripped fields outside the base set; they now pass unknown fields through, per the core spec's Payment-Receipt provision ("Payment method specifications MAY define additional fields for receipts").
+- 7fd4ecb: Removed the mainnet network option from `mppx account fund`.
+- 00d72b0: Fixed a read-after-write race in Tempo session channel open/top-up verification. The on-chain read-back now pins to the block that included the management transaction (instead of reading `latest`) and retries transient failures, so a lagging load-balanced RPC replica can no longer reject a valid open with `on-chain channel state does not match open receipt`.
+
+## 0.8.5
+
+### Patch Changes
+
+- 754b491: Added viem token definitions and token sets to make managing tokens simpler.
+
+## 0.8.4
+
+### Patch Changes
+
+- 3136195: Fixed Tempo auto-swap call building with `viem@>=2.54` and hardened account balance metadata formatting.
+- 86b6586: Fixed Stripe CLI live-mode Shared Payment Token creation. SPT requests now send the preview `Stripe-Version` header, live-mode requests target the issued-tokens endpoint with `seller_details[network_business_profile]`, and restricted test keys (`rk_test_...`) are recognized as test mode.
+- cdd989e: Added a `mppx validate` CLI command for discovering paid endpoints, validating payment challenges, checking malformed-credential handling, and exercising Tempo payment flows end to end.
+
+## 0.8.3
+
+### Patch Changes
+
+- be8a655: Fixed Tempo charge credential creation with `viem@>=2.54` transfer call builders.
+
+## 0.8.2
+
+### Patch Changes
+
+- 80ed268: Added CLI selection of payable Tempo charge challenges and a currency override.
+- 24ddf52: Filtered unsupported x402 accepts during HTTP client challenge extraction.
+- 24ddcca: Rejected non-canonical fee-payer calldata and client-supplied access lists before sponsorship.
+- 685f698: Fixed MCP payment-aware fetch retries for tool results with payment-required metadata.
+- 8305a05: Added configurable incremental payment challenge retries for client fetch, defaulting to three.
+
+## 0.8.1
+
+### Patch Changes
+
+- 2c4086f: Disabled automatic CLI configuration discovery from local directories.
+- 2158a40: Enforced sponsor fee policies before hosted fee-payer signing.
+- ca8687b: Validated session open deposit and voucher amounts before sponsored broadcast.
+
+## 0.8.0
+
+### Minor Changes
+
+- daab9b8: **Breaking:** Collapsed `McpClient.wrap` and the in-place `wrapClient` variant into a single `McpClient.wrap` API on the `mppx/mcp/client` entrypoint.
+
+  `McpClient.wrap` now adds payment handling to an MCP SDK client in place: the client is mutated and the same reference is returned, so surfaces that keep using the original client become payment-aware (e.g. when another SDK owns the client reference, like Cloudflare Agents). The MCP SDK `callTool(params, resultSchema?, options?)` signature is preserved, payment challenges are handled whether they arrive as payment-required errors or as tool results carrying `org.paymentauth/payment-required` metadata, and the config accepts `orderChallenges` and `paymentPreferences` alongside `methods` and `onPaymentRequired`. Calling `wrap` on the same client again replaces its payment configuration.
+
+  Migration: move per-call options from the second argument to the third — `mcp.callTool(params, undefined, { context, timeout })` — and replace the approval-first overload `mcp.callTool(onPaymentRequired, params, options)` with the `onPaymentRequired` option: `mcp.callTool(params, undefined, { onPaymentRequired })` (pass `null` to bypass a configured hook). The MCP entrypoints moved to `mppx/mcp/client` and `mppx/mcp/server`; the `mppx/mcp-sdk/*` specifiers remain as aliases.
+
+- e755222: Settled MCP-over-HTTP payment challenges in the same payment-aware fetch as HTTP `402`s, so `Transport.http()` can extract JSON-RPC `-32042` challenges and retry with credentials in MCP metadata.
+- 18b57cc: Added a pluggable `channelStore` for persisting reusable payer session channels and removed the client-side `authorizedSigner` override so voucher authority is derived from the selected account.
+
+### Patch Changes
+
+- 4c79a78: Rejected empty Payment challenge IDs during construction and deserialization.
+- 7c38c17: Deprecated uppercase asset and chain aliases in favor of lowercase exports.
+- 0e88d07: Corrected PaymentRequest documentation examples to use the exported namespace name.
+- 8da60b5: Documented explicit server secret key configuration in README examples.
+- 7ab4e00: Fixed legacy session manager close amounts when receipts reported per-request spent deltas.
+- b5d8657: Updated Hono dependencies to patched versions.
+- 5e27ef2: Fixed SSE session accounting so voucher management posts no longer consumed stream charges.
+- ec1ad50: Hardened server secret-key validation and capped oversized `WWW-Authenticate` request parameters.
+- 11db0bd: Removed now-unused `wallet_authorizeChallenge` support.
+- a1199b0: Added credential-required Tempo subscription reuse and signed-source lookup support so active subscriptions could be bound to the recovered payer instead of request metadata alone.
+- e80feeb: The Tempo fee-payer (sponsor) pre-broadcast simulation now simulates the co-signed transaction the sponsor actually broadcasts — with the concrete fee payer and chosen fee token — instead of the pre-cosign `0x78` envelope, for both local and hosted (`feePayerUrl`) fee payers. This catches reverts in the exact transaction the sponsor pays gas for, and fails closed (no broadcast) when the simulation reverts.
+- c2611f6: Added `tempo.common()` as an explicit alias for the Tempo charge and session method bundle.
+- b84cc06: Added generic Tempo account resolution for charge/session credentials and primitive session voucher signatures.
+- 034315e: Updated proxy route examples to use current route handler APIs.
+- 4e5abf4: Hardened confirmed Tempo subscription settlement against T6 (TIP-1028) receive policies. Activation and renewal payments that wait for confirmation now verify that a TIP-20 `TransferWithMemo` log credits the intended recipient for the expected amount with the generated settlement memo, instead of trusting transaction success alone. Transfers held by a receiver's receive policy (redirected to `ReceivePolicyGuard`) are now rejected rather than treated as paid, and the memo binding excludes unrelated transfer effects in the same receipt. Documented that the optimistic `waitForConfirmation: false` mode cannot prove recipient credit under T6.
+- c15be54: Added `wallet_authorizeChallenge` support. JSON-RPC accounts now delegate Tempo charge and session challenges to wallets that advertise MPP support via `wallet_getCapabilities`, falling back to local signing otherwise.
+- d14d933: Bound Tempo zero-amount proof credentials to the payer wallet. The EIP-712 `Proof` typed-data now includes an `account` field (domain version bumped to `3`), so a proof signature commits to a specific payer address and can no longer be replayed against a different account — including across an access key authorized for multiple accounts. Exposed the canonical proof contract via `tempo.Proof` (`types`, `domain`, `primaryType`, `message`, `typedData`, `hash`) and added deterministic conformance vectors covering the wallet-binding property.
+
+## 0.7.0
+
+### Minor Changes
+
+- 6ae92c4: Added TIP-1034-backed Tempo sessions as the default `tempo.session` interface and moved the previous session flow to `tempo.sessionLegacy`.
+
+### Patch Changes
+
+- da6383e: Defaulted account faucet funding to testnet unless a network or RPC URL was specified.
+- 64e9d5f: Fixed hosted Tempo fee-payer fills for sender-signed sponsored charge transactions and validated sponsored fee tokens against pathUSD and chain default currencies.
+- eaac057: Added MCP client payment approval callbacks before credential creation.
+- 77520fa: Changed the Tempo session client API so `tempo.session()` created the low-level Mppx client method and `tempo.session.manager()` created the managed session lifecycle client.
+- 9859f8f: Fixed payment-aware fetch to refuse credential retries when a redirected 402 challenge response resolves to a different origin.
+- ef81337: Send the SSE `Accept` header on automatic session voucher POST updates.
+- f0ff266: Declared `@stripe/stripe-js` as a dependency so the shipped sources type-check for consumers resolving the `src` export condition. The import is type-only, so no runtime code is added.
+- 5a35a02: Added client-side Tempo chain pinning. `tempo.charge({ expectedChainId })` rejects charge challenges whose `methodDetails.chainId` conflicts with the configured chain ID, and signs on the pinned chain when the challenge omits it.
+
+## 0.6.31
+
+### Patch Changes
+
+- 1c286cd: Fixed host confusion in the Node adapter (`Request.fromNodeListener`/`toNodeListener`). Protocol-relative (`//evil.com/x`), triple-slash (`///evil.com/x`), backslash (`/\evil.com/x`), and embedded-authority (`//a//evil.com/x`) request targets could previously override the request host derived from the `Host` header, which in turn poisoned the auto-detected challenge `realm`. The adapter now copies only the parsed path and query onto a trusted origin, so the request target's authority can never influence the resulting URL host.
+- e03f5c5: Fixed `tempo.session` voucher verification to treat lower-amount voucher replays idempotently. Per the session spec's idempotency requirement, a non-advancing voucher (with a `cumulativeAmount` at or below the highest accepted amount, but above the on-chain settled amount) now returns a 200 OK receipt with the current highest amount instead of being rejected as an error. Forged or at-or-below-settled vouchers are still rejected, and the at-or-below-settled rejection reason was clarified to match the inclusive (`<=`) bound.
+- f7bf20c: Fixed SSE session voucher updates being charged as content requests.
+
+## 0.6.30
+
+### Patch Changes
+
+- 77eac81: Added the root EVM charge method export for direct `mppx/evm` helper access.
+
+## 0.6.29
+
+### Patch Changes
+
+- aca0e4a: Fixed challenge header serialization type checking for ES2020 TypeScript targets.
+- 1edd30e: Fixed WWW-Authenticate challenge serialization to escape quoted-string values and reject CRLF.
+- 5aed74b: Replaced Tempo session `authorizedSigner` options with `voucherSigner` accounts and added raw access-key voucher signing.
+- d337c11: Preserved charge supported modes and split payment defaults in challenges.
+- c95f4e2: Applied strict session fee-payer call validation to relay-sponsored transactions.
+- 2f5b92a: Bound session voucher verification to stored channel chain metadata.
+- 165bc9c: Required expiring nonce keys for fee-sponsored transactions.
+- a171438: Blocked WebSocket session metering after channel close requests.
+- ae76fb4: Retried payment credentials against the final challenge response URL.
+- 6715802: Stripped caller-supplied OpenAI tenant headers before proxying requests.
+- fbb7057: Added EVM charge support with x402 exact compatibility and resource-bound payment payload verification.
+- bf72175: Added an x402 and mpp example server/client, fixed HTTP clients to parse x402 offers when Payment-auth challenges were also present, and fixed repeated x402 EIP-3009 payments for live facilitators.
+
+## 0.6.28
+
+### Patch Changes
+
+- 6c789fa: Added store key prefix options for Store constructors and Tempo charge, session, and subscription stores.
+- b051e6c: Stripped `Set-Cookie` from upstream responses in `Proxy.scrubResponse` so an upstream service cannot set cookies under the proxy's origin.
+- 1ee47a2: Added server-side Stripe Connect settlement options for Stripe charges.
+
+## 0.6.27
+
+### Patch Changes
+
+- 27d9218: Updated Tempo chain imports to use the `viem/tempo/chains` entrypoint.
+- 22d8eed: Updated viem and ox dependencies to their latest published versions and fixed sponsored Tempo transaction gas estimation with the new versions.
+
+## 0.6.26
+
+### Patch Changes
+
+- 3d9a9cf: Added `dev_second` subscription periods.
+  Added `mppx.tempo.subscription.renew`.
+  Raised default sponsor limits for subscription payments.
+
+## 0.6.25
+
+### Patch Changes
+
+- 6c4af82: Fixed Tempo charge hash receipt verification to collapse paired transfer logs before matching expected transfers.
+- d378d68: Added a Tempo charge sender validation hook for accepting authorized third-party transfer senders.
+
+## 0.6.24
+
+### Patch Changes
+
+- bec7b56: Added challenge ordering hooks for client-side challenge filtering and sorting.
+- 8f766f8: Fixed bug where forged scope metadata could result in cross route bypass of requests.
+
+## 0.6.23
+
+### Patch Changes
+
+- c370c93: Added fee payer support and an optional `feePayerPolicy` parameter to `tempo.subscription` so activation and renewal payments can be sponsored without consuming the access key's spending limit.
+
+## 0.6.22
+
+### Patch Changes
+
+- 281fc16: Fixed Tempo subscription `wallet_authorizeAccessKey` RPC payload to send `scopes` (the spec-compliant field) instead of `allowedCalls`, and to hex-encode `limits[].limit` so the parameters match the encoded variant of the `wallet_authorizeAccessKey` schema.
+
+## 0.6.21
+
+### Patch Changes
+
+- d752fb5: Added typed client payment events for challenge handling, credential creation, payment responses, and failures.
+- 55a5b8f: Added typed server events for payment challenges, failed payments, and verified payments.
+
+## 0.6.20
+
+### Patch Changes
+
+- 868c2bf: Added Date challenge expirations and numeric Tempo subscription period counts.
+- 868c2bf: Added Tempo subscription key authorization, subscription receipt identifiers, activation replay protection, renewal idempotency, and dynamic access key handling.
+
+## 0.6.19
+
+### Patch Changes
+
+- 4fffc6a: Fixed pre-broadcast simulation in `tempo.charge` and `tempo.session` by stripping `feeToken` and `feePayerSignature` from the simulation request, so the node does not try to recover `feePayerSignature` against a sender signature that viem's `call` action never includes.
+
+## 0.6.18
+
+### Patch Changes
+
+- d365b41: Added Tempo CLI auto-swap and payment source token options.
+- 9f660c2: Added Tempo CLI network shortcuts and challenge chain mismatch checks.
+- 538c7fb: Added CLI commands for browsing the MPP services registry.
+
+## 0.6.17
+
+### Patch Changes
+
+- 33df58b: Fixed Tempo session close and settle transactions to resolve funded Tempo fee tokens before signing.
+
+## 0.6.16
+
+### Patch Changes
+
+- b711dc5: Preserved raw challenge opaque values when parsing and echoing credentials.
+- 5059bfa: Fixed Tempo charge push verification for smart-account transaction hashes.
+
+## 0.6.15
+
+### Patch Changes
+
+- 2b1cf51: Rejected expired challenges before client-side credential creation.
+
+## 0.6.14
+
+### Patch Changes
+
+- ddf590e: Hardened Tempo session billing against concurrent replay, bodyless POST bypasses, inflated receipts, and close races.
+- e53d3cd: Fixed Express middleware to short-circuit Tempo session management responses before route handlers run.
+- 02663ab: Hardened fee-payer gas sponsorship validation.
+
+## 0.6.13
+
+### Patch Changes
+
+- Blocked Tempo session charges after a channel force-close was requested and rejected reserved SSE charges during pending close.
+
+## 0.6.12
+
+### Patch Changes
+
+- Fixed missing challenge-bound memo validation for Tempo pull transactions.
+
+## 0.6.11
+
+### Patch Changes
+
+- Fixed Tempo clients and the CLI to prioritize local escrow and deposit configuration over server-provided session challenge overrides.
+
+## 0.6.10
+
+### Patch Changes
+
+- Fixed SSE message encoding so multiline payloads could not forge downstream payment control events.
+
+## 0.6.9
+
+### Patch Changes
+
+- Fixed Stripe proxy to strip caller-supplied `Stripe-Account` headers before forwarding requests upstream.
+
+## 0.6.8
+
+### Patch Changes
+
+- b5561f5: Added an actionable error when Linux account storage cannot find secret-tool.
+
+## 0.6.7
+
+### Patch Changes
+
+- Fixed zero-amount Tempo proof verification to validate non-keychain signature envelopes before trusting their signer address.
+
+## 0.6.6
+
+### Patch Changes
+
+- 78bb8c8: Bumped `ox` to `0.14.18` so the bundled Tempo payment UI preserves `limits[].period` in the on-chain `KeyAuthorization`. Without this, per-period access keys failed signer recovery and silent signing fell back to the wallet approval dialog.
+
+## 0.6.5
+
+### Patch Changes
+
+- 3c5cd4b: Fixed zero-amount Tempo proof credentials to bind signatures to the challenge realm.
+- 24604ff: Fixed MCP stdio startup and returned structured CLI command results without writing raw tool output to stdout.
+
+## 0.6.4
+
+### Patch Changes
+
+- 0d1e548: Fixed credential `opaque` serialization to use the spec-compliant base64url string shape, while keeping deserialization backward-compatible with legacy object-shaped credentials.
+- 9536014: Added canonical discovery output using `x-payment-info.offers[]` while continuing to accept the legacy flat shorthand during validation and parsing.
+
+## 0.6.3
+
+### Patch Changes
+
+- 530a6ff: Validate session settle/close senders against the channel payee so raw delegated access-key accounts fail fast with a clear error, and use the raw Tempo transaction path for access-key-compatible settlement and close flows.
+
+## 0.6.2
+
+### Patch Changes
+
+- 57354de: Added scope-bound challenge metadata for route replay protection, scope-aware `verifyCredential()` checks, and adapter auto-scoping for Hono and proxy routes.
+
+## 0.6.1
+
+### Patch Changes
+
+- Fixed cross-route credential replay checks by binding `unitType` and allowing `verifyCredential()` to validate credentials against expected route context.
+
+## 0.6.0
+
+### Minor Changes
+
+- e606fa9: **Breaking:** Removed default `Accept-Payment` headers on every outgoing request for polyfilled fetch in browsers. Now defaults to same-origin requests in browser environments. Non-browser environments are unaffected. Use `acceptPaymentPolicy` to control supported payment origins.
+
+### Patch Changes
+
+- e606fa9: Added `acceptPaymentPolicy` option to control when the `Accept-Payment` header is injected on outgoing requests, mitigating CORS preflight failures on non-payment-aware servers.
+
+  - In browsers, `Fetch.polyfill` and `Mppx.create` (with `polyfill: true`) default to `'same-origin'`, preventing cross-origin CORS issues.
+  - Non-browser environments and `Mppx.create` with `polyfill: false` default to `'always'`.
+  - Supported values: `'always'`, `'same-origin'`, `'never'`, `{ origins: string[] }` (with `*.` wildcard support).
+  - Exported `Fetch` namespace from `mppx/client`.
+
+- 1a831eb: Fixed Tempo session content gating and SSE plain-response billing to share request-body detection so HTTP/2 POST requests without Content-Length were classified consistently.
+
+## 0.5.17
+
+### Patch Changes
+
+- 3259157: Added `mppx account export` command for exporting the private key of local keychain-backed accounts.
+
+## 0.5.16
+
+### Patch Changes
+
+- 5b6a938: Thread context through pinned requests so MCP tool calls and HEAD requests cannot bypass the shared management-vs-content gate.
+- 22be301: Preserve `keyAuthorization` in fee-sponsored Tempo charge transactions and reject unsupported transaction fields instead of silently dropping them.
+- 3e7320d: Charge `tempo/session` SSE streams with `unitType: "request"` once per streamed response instead of once per emitted SSE data event.
+
+## 0.5.15
+
+### Patch Changes
+
+- 7aff8ab: Prevented default HTTP `tempo.session()` content requests from replaying the same accepted voucher without advancing request/response accounting.
+- 7aff8ab: Pinned credential verification and compose dispatch to challenge `opaque` metadata so same-economics sibling routes could not replay each other's credentials.
+
+## 0.5.14
+
+### Patch Changes
+
+- 1ba7af2: Hardened sponsored Tempo session `open` and `topUp` flows by enforcing fee-payer policy limits, blocking call smuggling, and adding `feePayerPolicy` support.
+- 1ba7af2: Fixed fee-sponsored Tempo charge flows by simulating sponsored transactions before broadcast and binding swap approvals to the DEX input token.
+- 1ba7af2: Normalized Tempo session channel IDs across storage and verification paths, preventing case-variant aliases from creating duplicate channel state.
+
+## 0.5.13
+
+### Patch Changes
+
+- 7e16df7: Make Tempo charge fee-sponsorship policy resolve per chain and allow overriding it with `feePayerPolicy`.
+- 13d2851: Fixed Tempo HTML pay button text overrides and make the HTML page title follow a custom `paymentRequired` label when `title` is omitted.
+- e81f45c: Add Tempo charge `supportedModes` request support so clients and servers can explicitly negotiate `push` vs `pull` settlement.
+
+## 0.5.12
+
+### Patch Changes
+
+- f6ce313: Add typed `paymentPreferences` support that emits `Accept-Payment` on client requests and filters composed server challenges accordingly.
+- 7059598: Accept zero-dollar proof credentials signed by authorized Tempo access keys and export Tempo proof DID helpers from `mppx/tempo`.
+- b6a18c4: Raised too low fee-payer `maxTotalFee` policy
+
+## 0.5.11
+
+### Patch Changes
+
+- 2aff2c0: Handled malformed Host headers in the Node request listener instead of letting them crash the process.
+
+## 0.5.10
+
+### Patch Changes
+
+- d95c01c: Pruned internal dependencies.
+
+## 0.5.9
+
+### Patch Changes
+
+- 4d7fe94: Bumped internal deps
+
+## 0.5.8
+
+### Patch Changes
+
+- 00572a0: Normalized Tempo fee-payer co-signing for charge flows so the final sponsored transaction is rebuilt from validated fields with centralized fee-payer policy checks.
+- 7d4fdab: Centralize the authoritative challenge verification inputs by adding captured-request and verified-envelope context plumbing, shared canonical HMAC input generation, and a single pinned-request comparison path without changing the existing server hook model.
+- b087c21: Add an optional atomic `Store.update()` primitive for custom store backends and use it to make Tempo replay protection and channel state updates safe across distributed deployments.
+
+## 0.5.7
+
+### Patch Changes
+
+- 9cffd24: Added `Config`, `Text`, and `Theme` type exports to `mppx/html` entrypoint.
+
+## 0.5.6
+
+### Patch Changes
+
+- 0c4ce6f: Added `.compose` support to HTML payment links.
+
+## 0.5.5
+
+### Patch Changes
+
+- e7147c2: Bind attribution memo nonce to challenge ID. The 7-byte nonce field (bytes 25–31) is now derived from `keccak256(challengeId)[0..6]` instead of random bytes, preventing transaction hash stealing in push mode. `Attribution.encode()` now requires `challengeId`. The server verifies challenge binding and server fingerprint for `hash` (push) credentials. Pull-mode `transaction` credentials are not affected — the server controls broadcast, so there is no hash-stealing risk.
+
+  **Breaking:** `Attribution.encode()` now requires `challengeId` — callers must pass the challenge ID to generate a memo. Old push-mode clients that generate random attribution nonces or plain transfers without memos are rejected by the server. Pull-mode clients are unaffected.
+
+## 0.5.4
+
+### Patch Changes
+
+- c3f522c: Fixed CLI defaulting to testnet when `--rpc-url` is omitted. The CLI now defaults to Tempo mainnet. Also added `resolveRpcUrl` helper so `MPPX_RPC_URL` and `RPC_URL` env vars are respected consistently across all commands.
+- f086276: Added theming to automatic HTML payment links.
+
+## 0.5.3
+
+### Patch Changes
+
+- ba0bb60: Override vulnerable `lodash` (`<=4.17.23`) to `>=4.18.0` in pnpm overrides. Fixes code injection via `_.template` ([GHSA-r5fr-rjxr-66jc](https://github.com/advisories/GHSA-r5fr-rjxr-66jc)) and prototype pollution via `_.unset`/`_.omit` ([GHSA-f23m-r3pf-42rh](https://github.com/advisories/GHSA-f23m-r3pf-42rh)).
+
+## 0.5.2
+
+### Patch Changes
+
+- 2a7dbd3: Added experimental support for payment links
+- 20f3fe4: Hardened credential verification, transport billing, error responses, and proxy routing. Credential request binding now verifies fields match the actual incoming request. SSE transport derives billing context directly from the verified credential payload. 402 error responses no longer leak internal details. Proxy routing binds management POST fallback to the credential's payment method and intent for correct disambiguation.
+
+## 0.5.1
+
+### Patch Changes
+
+- dd27cb1: Validate the `did:pkh:eip155` source DID on zero-dollar Tempo proof credentials. Servers now reject malformed proof source DIDs and chain ID mismatches between the source DID and the challenge signing domain.
+
+## 0.5.0
+
+### Minor Changes
+
+- 5e7750b: Added a `proof` credential type for zero-amount Tempo charge requests. Clients now sign an EIP-712 proof over the challenge ID instead of creating a broadcastable transaction, and servers verify the proof against the credential source DID before accepting the request. This prevents zero-dollar auth flows from burning gas when the payer would otherwise have been the fee payer.
+
+## 0.4.12
+
+### Patch Changes
+
+- 5684b94: Fixed `settleOnChain` and `closeOnChain` to use the payee account as
+  `msg.sender` instead of the fee payer when submitting fee-sponsored
+  transactions. Previously, `sendFeePayerTx` used the fee payer as both
+  sender and gas sponsor, causing the escrow contract to revert with
+  `NotPayee()`. Added `account` option to `tempo.settle()` so callers can
+  specify the signing account separately from the fee payer.
+- 3bc8657: Added compile-time guard to `tempo.session()` and `tempo.charge()`. Unknown properties (e.g. `stream` instead of `sse`) now cause a type error instead of being silently accepted.
+- 0531edd: Added split-payment support to Tempo charge requests, including client transaction construction and stricter server verification for split transfers.
+- 6188184: Added `realm` auto-detection from the request `Host` header when not explicitly configured. Resolution order: explicit value → env vars (`MPP_REALM`, `FLY_APP_NAME`, `VERCEL_URL`, etc.) → request URL hostname → `"MPP Payment"` fallback with a one-time warning. Removed the hard-coded `"MPP Payment"` default and deprioritized `HOST`/`HOSTNAME` env vars in favor of platform-specific alternatives.
+- ba79504: Return `410 ChannelClosedError` instead of `402 AmountExceedsDepositError` when a channel's on-chain deposit is zero but the channel still exists (payer is non-zero). This handles a race window during settlement where the escrow contract zeros the deposit before setting the finalized flag.
+
+## 0.4.11
+
+### Patch Changes
+
+- Fixed close voucher validation to reject vouchers equal to the on-chain settled amount. ([GHSA-mv9j-8jvg-j8mr](https://github.com/wevm/mppx/security/advisories/GHSA-mv9j-8jvg-j8mr))
+- Added Stripe credential replay protection via the `Idempotent-Replayed` header. ([GHSA-8mhj-rffc-rcvw](https://github.com/wevm/mppx/security/advisories/GHSA-8mhj-rffc-rcvw))
+
+## 0.4.10
+
+### Patch Changes
+
+- b4e1a3d: Add OpenAPI-first discovery tooling via `mppx/discovery`, framework `discovery()` helpers, and `mppx discover validate`.
+
+  This also changes `mppx/proxy` discovery routes:
+
+  - `GET /openapi.json` is now the canonical machine-readable discovery document.
+  - `GET /llms.txt` remains available as the text-friendly discovery view.
+  - Legacy `/discover*` routes now return `410 Gone`.
+
+- 70f6595: Fix two production session/SSE robustness issues.
+
+  1. Accept exact voucher replays (`cumulativeAmount == highestVoucherAmount`) as idempotent success after signature verification, while still rejecting lower cumulative amounts and preserving monotonic state advancement rules.
+  2. Prevent invalid null-body response wrapping in SSE receipt transport by returning `101/204/205/304` responses directly instead of stream-wrapping them.
+
+- 3c713c9: `tempo.session()` now throws immediately at initialization if no viem `Account` is provided, instead of failing later with an opaque error during channel close. The error message includes an example fix.
+
+## 0.4.9
+
+### Patch Changes
+
+- d9b651d: Added `Store.redis()` adapter for standard Redis clients (ioredis, node-redis, Valkey) with BigInt-safe serialization.
+- b69bbee: Fixed Express middleware hanging by constructing a Fetch `Request` directly from Express's `req` API.
+- 7da6cfd: Fixed SSE header normalization.
+- a2c6cc9: Skipped route amount/currency/recipient validation for topUp and voucher credentials. These `POST`s carry no application body so the route's request hook may produce a different amount than the challenge echoed from the original request. The on-chain voucher signature is the real validation.
+
+## 0.4.8
+
+### Patch Changes
+
+- 99920d0: Updated validation. ([GHSA-8x4m-qw58-3pcx](https://github.com/wevm/mppx/security/advisories/GHSA-8x4m-qw58-3pcx))
+
+## 0.4.7
+
+### Patch Changes
+
+- 2a0b88e: Fixed cooperative close to sign the server-reported spent amount instead of the high-water mark (`cumulativeAmount`), preventing overcharging when actual usage was below the pre-authorized voucher amount.
+
+## 0.4.6
+
+### Patch Changes
+
+- 281005c: Added support for `feePayer` as a URL string on `tempo` method.
+
+## 0.4.5
+
+### Patch Changes
+
+- bbd4b3f: Updated Moderato (testnet) escrow contract address to `0xe1c4d3dce17bc111181ddf716f75bae49e61a336`.
+
+## 0.4.4
+
+### Patch Changes
+
+- b09a35a: fix: update getChannel ABI field order to match new escrow contract
+- c520705: Fixed `Client.getResolver` to inject Tempo serializers onto clients missing them, preventing the default serializer from rejecting Tempo-specific transaction fields.
+- b09a35a: chore: update mainnet escrow contract address
+
+## 0.4.3
+
+### Patch Changes
+
+- 7f8d103: chore: update mainnet escrow contract address
+
+## 0.4.2
+
+### Patch Changes
+
+- c089da5: Added CLI config via `mppx.config.(js|mjs|ts)`. Allows for extending `mppx` CLI to support non-built-in methods.
+
+## 0.4.1
+
+### Patch Changes
+
+- f2bc051: Support keychain V2 (`0x04`) signatures via ox 0.14 upgrade
+
+## 0.4.0
+
+### Minor Changes
+
+- 143ebc9: Support handler function refs in `compose()`.
+  - **`[mppx.tempo.charge, { amount: '1' }]` syntax** — `compose()` now accepts handler function references (e.g. `mppx.tempo.charge`) as the first element of entry tuples, in addition to `Method.AnyServer` objects and `"name/intent"` string keys.
+  - **`_method` metadata on nested handlers** — nested handler functions are tagged with their source `Method.AnyServer`, enabling `compose()` to resolve the correct handler.
+
+### Patch Changes
+
+- db2033c: Set `feeToken` during server co-sign and simulation for fee-payer transactions.
+
+  When the client sends a fee-payer (0x78) envelope, `feeToken` is intentionally omitted. The server must set it at co-sign time, but previously never did — causing "Fee token spending limit exceeded" errors. Now resolves `feeToken` from the deserialized transaction or falls back to the chain's default currency.
+
+## 0.3.16
+
+### Patch Changes
+
+- 79bbfc6: Added multi-challenge `mppx.challenge()` combinator for presenting multiple payment methods in a single 402 response, nested accessors (`mppx.tempo.charge(...)`), `Mppx.challenge()` static, `Challenge.fromResponseList()`, and automatic client preference-based challenge selection.
+- b4f3c92: Migrated to use `call` instead of manual `eth_estimateGas`.
+
+## 0.3.15
+
+### Patch Changes
+
+- cd42c28: Added `rawFetch` property to the client `Mppx` instance, exposing the original unwrapped fetch function for requests that should bypass 402 payment interception.
+- 230ef16: Moved CLI payment logs (Payment Required, Payment Receipt, channel open/close) behind `-v` flag. Added `-vv` for full HTTP headers.
+
+## 0.3.14
+
+### Patch Changes
+
+- 345425f: Removed `expires` from charge request schemas (tempo, stripe). Expiry is now conveyed exclusively via the `expires` auth-param on the Challenge, not duplicated in the request body. Server handlers default to `Expires.minutes(5)` when `expires` is not explicitly provided.
+- eb19f32: Added `mode` parameter to `tempo.charge()` client — `'push'` (client broadcasts tx, sends hash) and `'pull'` (client signs tx, server broadcasts). Defaults to `'push'` for JSON-RPC accounts, `'pull'` otherwise.
+
+## 0.3.13
+
+### Patch Changes
+
+- 82206f5: Made `constantTimeEqual` isomorphic by replacing `node:crypto` with `ox` sha256 and a custom constant-time comparison.
+
+## 0.3.12
+
+### Patch Changes
+
+- c28944e: Added `autoSwap` flag to `tempo` method. When enabled, the client automatically swaps from supported currencies via the DEX if the payer lacks the target token.
+- 9c23cb7: Fixed fetch polyfill to pass `init` through unmodified for non-402 responses. Previously, every request eagerly destructured `init` to strip the `context` property, creating a new object that could break libraries relying on object identity (e.g. WebSocket upgrade handshakes).
+
+## 0.3.11
+
+### Patch Changes
+
+- fd466c3: Added `waitForConfirmation` option to `session()` and `charge()` payment methods. When `false`, transactions are simulated via `eth_estimateGas` and broadcast without waiting for on-chain confirmation, reducing latency.
+- ddb7057: Fixed `Handlers` type to omit shorthand intent keys when multiple methods share the same intent, matching runtime behavior and preventing `TypeError` on collision.
+
+## 0.3.10
+
+### Patch Changes
+
+- 558279e: Added `closeRequestedAt` check in session voucher handler with configurable `channelStateTtl` (default: 60s). Prevented payers from using a channel after initiating a forced close.
+- 558279e: Added expiration check on credentials in the core handler. Expired credentials are now rejected with `PaymentExpiredError` instead of being processed.
+- 558279e: Added token address validation in `broadcastTopUpTransaction` fee-payer logic. Prevented approve calls to arbitrary contracts in fee-sponsored topUp transactions.
+- 558279e: Bound credential verification to the route's configured request. Prevented cross-route scope confusion where a credential issued for one route could be presented at another.
+- 558279e: Removed insecure hardcoded `'tmp'` fallback for `secretKey`. `Mppx.create()` now throws a clear error if neither `MPP_SECRET_KEY` env var nor explicit `secretKey` is provided.
+- 5d4bb93: Removed `realm` from `PaymentRequiredError` detail message to avoid leaking deployment URLs and hostnames in error responses.
+
+## 0.3.9
+
+### Patch Changes
+
+- a016e1f: Added fee payer support to `settleOnChain` and `closeOnChain` for server-originated transactions on chains where the server EOA has no native tokens. Transactions are built using `prepareTransactionRequest` → dual-sign → `sendRawTransactionSync` with an explicitly resolved fee token.
+
+## 0.3.8
+
+### Patch Changes
+
+- 7cb0d5f: Fixed CLI failing with "No account found" when `MPPX_PRIVATE_KEY` is set to an empty string.
+
+## 0.3.7
+
+### Patch Changes
+
+- e4f0138: Added `nonceKey: 'expiring'` to tempo charge transactions to avoid nonce collisions on parallel requests.
+
+## 0.3.6
+
+### Patch Changes
+
+- d2fb5e3: Fixed issue where mainnet would not default to USDC unless `testnet: false` was explicitly passed.
+
+## 0.3.5
+
+### Patch Changes
+
+- 6e2be11: Replaced `--channel <id>` and `--deposit <amount>` CLI flags with `-M`/`--method-opt` for passing method-specific options.
+
+  ```diff
+  # Before
+  - mppx example.com/content --channel 0x123 --deposit 1000000
+
+  # After
+  + mppx example.com/content -M channel=0x123 -M deposit=1000000
+  ```
+
+- 6e2be11: Added Stripe payment method support to the CLI.
+
+  ```bash
+  # Set your Stripe test-mode secret key
+  export MPPX_STRIPE_SECRET_KEY=sk_test_...
+
+  # Make a request to a Stripe-enabled endpoint
+  mppx https://example.com/content
+  ```
+
+- 955deb2: Renamed USDC.e to USDC in account view token list.
+
+## 0.3.4
+
+### Patch Changes
+
+- 9cf4943: Added USDC.e to account view mainnet token list and use `MPPX_RPC_URL` for default mainnet balance fetching.
+- 11c0422: Renamed internal `stream` terminology to `session` to align with the MPP spec. This includes renaming the `src/tempo/stream/` directory to `src/tempo/session/`, updating all problem type URIs from `…/problems/stream/…` to `…/problems/session/…`, and renaming associated types (e.g., `StreamCredentialPayload` → `SessionCredentialPayload`). No public API changes.
+
+## 0.3.3
+
+### Patch Changes
+
+- 04b04c9: Added auto-detection of `realm` and `secretKey` from environment variables in `Mppx.create()`.
+  - **Realm**: checks `MPP_REALM`, `FLY_APP_NAME`, `HEROKU_APP_NAME`, `HOST`, `HOSTNAME`, `RAILWAY_PUBLIC_DOMAIN`, `RENDER_EXTERNAL_HOSTNAME`, `VERCEL_URL`, `WEBSITE_HOSTNAME`
+  - **Secret key**: checks `MPP_SECRET_KEY`
+
+## 0.3.2
+
+### Patch Changes
+
+- b927c06: - `mppx/proxy`: Modified routes to show service in path for completeness (e.g. `POST /openai/v1/chat/completions` instead of `POST /v1/chat/completions`).
+
+## 0.3.1
+
+### Patch Changes
+
+- e6c9f85: Fixed `/discover.md` route returning 404.
+
+## 0.3.0
+
+### Minor Changes
+
+- d60f623: - **`mpp/proxy` (Breaking):** Renamed `/services*` discovery routes to `/discover*`.
+  - `mpp/proxy`: Simplified `llms.txt` to a brief service overview, linking each service to `/discover/<id>`.
+  - `mpp/proxy`: Added `/discover` and `/discover/<id>` endpoints with content negotiation (JSON by default, markdown for `Accept: text/markdown`/`text/plain` or bot/CLI user agents).
+  - `mpp/proxy`: Added `.md` extension variants (`/discover.md`, `/discover/<id>.md`) for explicit markdown.
+  - `mpp/proxy`: Added `/discover/all` for full markdown listing with route details.
+
+## 0.2.6
+
+### Patch Changes
+
+- 83c3bab: - Added `title` and `description` options to `Proxy.create` config, used to populate the `llms.txt` heading and description.
+
+  ```ts
+  const proxy = Proxy.create({
+    title: 'My AI Gateway',
+    description: 'A paid proxy for LLM and AI services.',
+    services: [...]
+  })
+  ```
+
+  - Added `title`, `description`, and `docsLlmsUrl` properties to `Service` type and `Service.from` config.
+
+  ```ts
+  Service.from('my-api', {
+    baseUrl: 'https://api.example.com',
+    title: 'My API',
+    description: 'A custom API service.',
+    docsLlmsUrl: 'https://example.com/llms.txt',
+    routes: { ... },
+  })
+
+  // or with per-endpoint docs
+  Service.from('my-api', {
+    baseUrl: 'https://api.example.com',
+    docsLlmsUrl: (endpoint) =>
+      endpoint
+        ? `https://example.com/api/${encodeURIComponent(endpoint)}.md`
+        : 'https://example.com/llms.txt',
+    routes: { ... },
+  })
+  ```
+
+## 0.2.5
+
+### Patch Changes
+
+- 01fa8ba: Added fallback `authorizedSigner` to `account.accessKeyAddress` when not explicitly provided.
+
+## 0.2.4
+
+### Patch Changes
+
+- 83d0175: Bumped `viem` peer dependency to `>=2.46.2`.
+
+## 0.2.3
+
+### Patch Changes
+
+- c0aa6ad: Fixed Stripe `createWithClient` to use `shared_payment_granted_token` instead of `payment_method` when creating a PaymentIntent with an SPT. This aligns the SDK client path with the raw fetch path and fixes 402 errors on credential retry.
+- e7f5985: Rejected keychain and non-secp256k1 signatures in `verifyVoucher`.
+
+## 0.2.2
+
+### Patch Changes
+
+- 360fc03: Added `Json.canonicalize` from `ox`
+
+## 0.2.1
+
+### Patch Changes
+
+- eb72c76: **Breaking:**
+  - Renamed `Challenge.fromIntent` to `Challenge.fromMethod`.
+  - Renamed `PaymentRequest.fromIntent` to `PaymentRequest.fromMethod`.
+
+## 0.2.0
+
+### Minor Changes
+
+- 627f5ec: **Breaking:**
+  - Renamed `Intent` and `MethodIntent` modules to `Method`.
+  - Removed `Intent` export from `mppx`. Use `Method` instead.
+  - Removed `MethodIntent` export from `mppx`. Use `Method` instead.
+  - Renamed `MethodIntents` export to `Methods` in `mppx/tempo` and `mppx/stripe`.
+
+## 0.1.1
+
+### Patch Changes
+
+- 910102d: Fixed SSE streaming reliability: pass `signal` through `SessionManager.sse()` so HTTP connections close on abort, snapshot challenge at SSE open time to prevent concurrent requests from corrupting voucher credentials, and forward `request.signal` to `Sse.serve()` so `chargeOrWait` breaks on disconnect.
+
+## 0.1.0
+
+### Minor Changes
+
+- badab1a: Initial release.