fix: align sponsored tempo tx fees with policy

[brendanjryan]

Summary

Align sponsored Tempo transaction construction with fee-payer policy limits, and finish the live integration harness cleanup.

What changed

• Cap sponsored max_priority_fee_per_gas to the chain's fee-payer policy when building 0x78 envelopes
• Add a regression test covering sponsored priority fee capping on a custom/dev chain
• Extend live integration coverage for hash verification memo binding
• Remove stale xfails now that the live devnet behavior has changed
• Fix the premium integration scenario to leave room for gas when the faucet-funded account pays fees in the same token

Why

• The live fee-payer integration was failing on devnet because the client copied eth_gasPrice into max_priority_fee_per_gas, which exceeded the sponsor policy on chain 1337
• Two integration xfails had become stale: wrong-memo rejection now fails earlier during payload validation, and auto-generated attribution memos now verify successfully when the server omits an explicit memo
• The premium integration test was spending the full faucet balance, so the transaction reverted once gas was included

Validation

• uv run ruff check src/mpp/methods/tempo/client.py tests/test_tempo.py tests/test_tempo_integration.py
• uv run pyright
• uv run pytest tests/test_tempo.py -v
• TEMPO_RPC_URL=http://localhost:8545 uv run pytest tests/test_tempo_integration.py -m integration -v

Integration result: 18 passed

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 21eab7c5ad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Run Redis-marked tests in CI integration job

The integration workflow now executes pytest -m integration, but tests/test_stores_redis_integration.py uses the redis marker (not integration), and this commit also deletes tests/test_stores_redis.py. That leaves RedisStore behavior untested in CI (test skips without REDIS_URL, integration excludes non-integration markers), so Redis regressions can merge without detection.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Keep custom rpc_url usable without forcing mainnet chain_id

Defaulting tempo() to chain_id=4217 makes calls like tempo(rpc_url="...", intents=...) implicitly mainnet-bound. That default is propagated into request methodDetails.chainId and client chain-ID validation, so custom/devnet RPC endpoints on non-4217 chains now fail unless callers add an explicit chain_id, which is a regression from the previous None default behavior.

Useful? React with 👍 / 👎.