feat: align with 7715 specification

[MoMannn]

Explanation

What is the current state of things and why does it need to change?

The @metamask/eth-json-rpc-middleware package currently supports two EIP-7715 methods:

• wallet_requestExecutionPermissions — for requesting new execution permissions
• wallet_revokeExecutionPermission — for revoking existing execution permissions

However, the EIP-7715 specification also defines two additional "discoverability" methods that allow dApps to query the wallet about its execution permission capabilities. Without these methods, dApps have no way to:

1. Discover which permission types the wallet supports and on which chains
2. Retrieve the list of currently granted (non-revoked) permissions for the user

What is the solution your changes offer and how does it work?

This PR adds support for the two missing EIP-7715 discoverability methods:

• wallet_getSupportedExecutionPermissions — Returns an object keyed by permission type (e.g., native-token-allowance, erc20-token-allowance) with their supported chain IDs and rule types. This allows dApps to understand what the wallet can handle before making permission requests.

• wallet_getGrantedExecutionPermissions — Returns an array of all currently active (non-revoked) execution permissions. Each permission includes chain ID, addresses, permission details, context, dependencies, and delegation manager information.

The implementation follows the established patterns in this package:

• Each method has a dedicated handler file with a factory function (createWallet*Handler)
• Hook-based architecture allows consumers to provide their own processing logic
• Superstruct schemas are defined for result types, enabling runtime validation
• Types and structs are exported from the package index for consumer use

EIP-7715 spec alignment for wallet_requestExecutionPermissions

The request/response schema has been updated to align with the latest EIP-7715 specification:

• Simplified address fields: Replaced the nested address + signer: { type, data: { address } } structure with flat from (optional) and to (required) fields
• Removed isAdjustmentAllowed from rules: This property is only relevant at the permission level, not individual rules
• Extended result type: Added dependencies (array of { factory, factoryData }) and delegationManager to the response
• New export: Added PermissionDependency type export for consumers
• Consistent address validation: Updated GrantedExecutionPermissionStruct to use HexChecksumAddressStruct for address fields

Are there any changes whose purpose might not obvious to those unfamiliar with the domain?

The handlers don't perform parameter validation since these methods don't accept parameters (they're pure query methods). This is intentional and differs from wallet_requestExecutionPermissions and wallet_revokeExecutionPermission which validate their params using Superstruct schemas.

References

• Needed for: feat: align with updated 7715 standard metamask-extension#39176
• Related to: feat: add 7715 discoverability methods snap-7715-permissions#249

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Implements EIP-7715 discoverability methods and integrates them into the wallet middleware.

• New handlers: createWalletGetSupportedExecutionPermissionsHandler and createWalletGetGrantedExecutionPermissionsHandler using hook-based processing and NoParamsStruct validation
• Exports new types and structs from index.ts (SupportedExecutionPermissionConfig*, GrantedExecutionPermission*, results)
• Adds EmptyArrayStruct/NoParamsStruct in utils/structs for "no params" validation
• Wires methods into createWalletMiddleware via optional processGet* hooks
• Unit tests for both methods: hook invocation, result passthrough, missing-hook error, and params validation
• Changelog updated to note new RPC support

^{Written by Cursor Bugbot for commit 8e94f86. This will update automatically on new commits. Configure here.}

[mj-kiwi]

Let's go

[V00D00-child]

LGTM

[mcmire]

LGTM.

[jiexi]

we can probably just forgo validation in this case?

[jiexi]

PermissionDependency is also exported now

[jiexi]

nit. if we add, id, jsonrpc, and method, we can drop the typecast here and the several below. Seems like the trouble might be worth it