Merge branch 'main' into link-workflow

# Conflicts:
#	delegation-toolkit/index.md

Author: alexandratran

.github/PULL_REQUEST_TEMPLATE.md

@@ -18,3 +18,10 @@ Fixes #
 
 - [ ] If this PR updates or adds documentation content that changes or adds technical meaning, it has received an approval from an engineer or DevRel from the relevant team.
 - [ ] If this PR updates or adds documentation content, it has received an approval from a technical writer.
+
+## External contributor checklist
+
+<!-- If you are an external contributor (outside of the MetaMask organization), complete the following checklist. -->
+
+- [ ] I've read the [contribution guidelines](https://github.com/MetaMask/metamask-docs/blob/main/CONTRIBUTING.md).
+- [ ] I've created a new issue (or assigned myself to an existing issue) describing what this PR addresses.

delegation-toolkit/concepts/erc7715.md …toolkit/concepts/advanced-permissions.mddelegation-toolkit/concepts/erc7715.md renamed to delegation-toolkit/concepts/advanced-permissions.md delegation-toolkit/concepts/erc7715.md renamed to delegation-toolkit/concepts/advanced-permissions.md

@@ -1,15 +1,15 @@
 ---
-description: Learn about MetaMask ERC-7715 permissions.
+description: Learn about MetaMask Advanced Permissions (ERC-7715).
 keywords: [ERC-7715, 7715, permissions, wallet, smart account]
 ---
 
-# ERC-7715 permissions
+# Advanced Permissions (ERC-7715)
 
-The Delegation Toolkit supports [ERC-7715](https://eips.ethereum.org/EIPS/eip-7715), which lets you request fine-grained permissions from a MetaMask user to execute transactions on their behalf.
+The Smart Accounts Kit supports Advanced Permissions ([ERC-7715](https://eips.ethereum.org/EIPS/eip-7715)), which lets you request fine-grained permissions from a MetaMask user to execute transactions on their behalf.
 For example, a user can grant your dapp permission to spend 10 USDC per day to buy ETH over the course of a month.
 Once the permission is granted, your dapp can use the allocated 10 USDC each day to purchase ETH directly from the MetaMask user's account.
 
-ERC-7715 eliminates the need for users to approve every transaction, which is useful for highly interactive dapps.
+Advanced Permissions eliminate the need for users to approve every transaction, which is useful for highly interactive dapps.
 It also enables dapps to execute transactions for users without an active wallet connection.
 
 :::note
@@ -23,42 +23,42 @@ Dapps can use this method to request a wallet to grant the dapp permission to ex
 `wallet_grantPermissions` requires a `signer` parameter, which identifies the entity requesting or managing the permission.
 Common signer implementations include wallet signers, single key and multisig signers, and account signers.
 
-The Delegation Toolkit supports multiple types of signers, but [an account signer is used in this documentation's examples](../guides/erc7715/execute-on-metamask-users-behalf.md) as a common implementation.
-With an account signer, a session account is created and used for the single purpose of requesting and redeeming ERC-7715 permissions, and does not contain tokens.
+Smart Accounts Kit supports multiple signer types. The documentation uses [an account signer](../guides/advanced-permissions/execute-on-metamask-users-behalf.md) as a common implementation example.
+When you use an account signer, a session account is created solely to request and redeem Advanced Permissions, and doesn't contain tokens
 The session account can be granted with permissions and redeem them as specified in [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710).
 The session account can be a smart account or an externally owned account (EOA).
 
 The MetaMask user that the session account requests permissions from must be upgraded to a [MetaMask smart account](smart-accounts.md).
 
-## ERC-7715 vs. delegations
+## Advanced Permissions vs. delegations
 
-ERC-7715 expands on regular [delegations](delegation/index.md) by enabling permission sharing *via the MetaMask browser extension*.
+Advanced Permissions expand on regular [delegations](delegation/index.md) by enabling permission sharing *via the MetaMask browser extension*.
 
 With regular delegations, the dapp constructs a delegation and requests the user to sign it.
 These delegations are not human-readable, so it is the dapp's responsibility to provide context for the user.
 Regular delegations cannot be signed through the MetaMask extension, because if a dapp requests a delegation without constraints, the whole wallet can be exposed to the dapp.
 
-In contrast, ERC-7715 enables dapps (and AI agents) to request permissions from a user directly via the MetaMask extension.
-ERC-7715 requires a permission configuration which displays a human-readable confirmation for the MetaMask user.
+In contrast, Advanced Permissions enable dapps (and AI agents) to request permissions from a user directly via the MetaMask extension.
+Advanced Permissions require a permission configuration which displays a human-readable confirmation for the MetaMask user.
 The user can modify the permission parameters if the request is configured to allow adjustments.
 
-For example, the following ERC-7715 permission request displays a rich UI including the start time, amount, and period duration for an [ERC-20 token periodic transfer](../guides/erc7715/use-permissions/erc20-token.md#erc-20-periodic-permission):
+For example, the following Advanced Permissions request displays a rich UI including the start time, amount, and period duration for an [ERC-20 token periodic transfer](../guides/advanced-permissions/use-permissions/erc20-token.md#erc-20-periodic-permission):
 
 <p align="center">
 <img src={require("../assets/erc7715-request.png").default} alt="ERC-7715 request" width="450px" class="appScreen" />
 </p>
 
-## ERC-7715 permissions lifecycle
+## Advanced Permissions lifecycle
 
-The ERC-7715 permissions lifecycle is as follows:
+The Advanced Permissions lifecycle is as follows:
 
 1. **Set up a session account** - Set up a session account to execute transactions on behalf of the MetaMask user.
   It can be a [smart account](smart-accounts.md) or an externally owned account (EOA).
 
 2. **Request permissions** - Request permissions from the user.
-  The Delegation Toolkit supports [ERC-20 token permissions](../guides/erc7715/use-permissions/erc20-token.md) and
-  [native token permissions](../guides/erc7715/use-permissions/native-token.md).
+  The Smart Accounts Kit supports [ERC-20 token permissions](../guides/advanced-permissions/use-permissions/erc20-token.md) and
+  [native token permissions](../guides/advanced-permissions/use-permissions/native-token.md).
 
 4. **Redeem permissions** - Once the permission is granted, the session account can redeem the permission, executing on the user's behalf.
 
-See [how to perform executions on a MetaMask user's behalf](../guides/erc7715/execute-on-metamask-users-behalf.md) to get started with the ERC-7715 lifecycle.
+See [how to perform executions on a MetaMask user's behalf](../guides/advanced-permissions/execute-on-metamask-users-behalf.md) to get started with the Advanced Permissions lifecycle.

delegation-toolkit/concepts/delegation/caveat-enforcers.md

@@ -5,7 +5,7 @@ keywords: [caveats, caveat enforcers, delegation]
 
 # Caveat enforcers
 
-The MetaMask Delegation Toolkit provides *caveat enforcers*, which are smart contracts that implement rules and restrictions (*caveats*) on delegations.
+The Smart Accounts Kit provides *caveat enforcers*, which are smart contracts that implement rules and restrictions (*caveats*) on delegations.
 They serve as the underlying mechanism that enables conditional execution within the [Delegation Framework](./index.md#delegation-framework).
 
 A caveat enforcer acts as a gate that validates whether a delegation can be used for a particular execution. When a delegate attempts to execute an action on behalf of a delegator, each caveat enforcer specified in the delegation evaluates whether the execution meets its defined criteria.
@@ -119,7 +119,7 @@ This "all-or-nothing" approach ensures that delegations only execute exactly as
 
 ## Caveat builder
 
-While caveat enforcers operate at the smart contract level, most developers interact with them through the `CaveatBuilder` interface in the MetaMask Delegation Toolkit.
+While caveat enforcers operate at the smart contract level, most developers interact with them through the `CaveatBuilder` interface in the Smart Accounts Kit.
 
 The `CaveatBuilder` provides a developer-friendly TypeScript API that:
 
@@ -152,7 +152,7 @@ When designing delegations with caveats, consider these best practices:
 
 ## Available caveat enforcers
 
-The Delegation Toolkit provides [out-of-the-box caveat enforcers](../../reference/delegation/caveats.md)
+The Smart Accounts Kit provides [out-of-the-box caveat enforcers](../../reference/delegation/caveats.md)
 for common restriction patterns, including:
 
 - Limiting target addresses and methods.

delegation-toolkit/concepts/delegation/index.md

@@ -1,7 +1,7 @@
 ---
 description: Learn about delegation, the delegation lifecycle, and the Delegation Framework.
 toc_max_heading_level: 2
-keywords: [delegation toolkit, delegation, delegator, delegate, delegation framework]
+keywords: [smart accounts kit, delegation, delegator, delegate, delegation framework]
 ---
 
 import Tabs from "@theme/Tabs"; 
@@ -14,7 +14,7 @@ or externally owned account (EOA) to perform specific executions on its behalf.
 The account that grants the permission is called the *delegator account*, while the account that receives the permission
 is called the *delegate account*.
 
-The MetaMask Delegation Toolkit follows the [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710) standard for smart contract delegation.
+The Smart Accounts Kit follows the [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710) standard for smart contract delegation.
 In addition, users can use [caveat enforcers](caveat-enforcers.md) to apply rules and restrictions to delegations.
 For example: Alice delegates the ability to spend her USDC to Bob, limiting the amount to 100 USDC.
 
@@ -65,7 +65,7 @@ You can create the following delegation types:
 
 ## Delegation Framework
 
-The MetaMask Delegation Toolkit includes the Delegation Framework, which is a
+The Smart Accounts Kit includes the Delegation Framework, which is a
 [set of comprehensively audited smart contracts](https://github.com/MetaMask/delegation-framework) that
 collectively handle delegator account creation, the delegation lifecycle,
 and caveat enforcement.
@@ -152,7 +152,7 @@ sequenceDiagram
 ## Execution modes
 
 When redeeming a delegation using [`redeemDelegations`](../../reference/delegation/index.md#redeemdelegations), you must pass an execution mode for each delegation chain you pass to the method.
-The Delegation Toolkit supports the following execution modes, based on [ERC-7579](https://erc7579.com/):
+The Smart Accounts Kit supports the following execution modes, based on [ERC-7579](https://erc7579.com/):
 
 | Execution mode | Number of delegation chains passed to `redeemDelegations` | Processing method | Does user operation continue execution if redemption reverts? |
 |--|--|--|--|

delegation-toolkit/concepts/smart-accounts.md

@@ -5,7 +5,7 @@ keywords: [MetaMask, smart accounts, account abstraction, ERC-4337]
 
 # MetaMask Smart Accounts
 
-The MetaMask Delegation Toolkit enables you to create and manage MetaMask Smart Accounts.
+The Smart Accounts Kit enables you to create and manage *MetaMask Smart Accounts*.
 MetaMask Smart Accounts are [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337) smart contract accounts
 that support programmable account behavior and advanced features such as multi-signature approvals,
 automated transaction batching, and custom security policies.
@@ -37,7 +37,7 @@ ERC-4337 introduces the following concepts:
 
 ## Smart account implementation types
 
-The MetaMask Delegation Toolkit supports three types of MetaMask Smart Accounts, each offering unique features and use cases.
+The toolkit supports three types of MetaMask Smart Accounts, each offering unique features and use cases.
 
 See [Create a smart account](../guides/smart-accounts/create-smart-account.md) to learn how to use these different account types.
 

delegation-toolkit/experimental/erc-7710-redeem-delegations.md

@@ -14,7 +14,7 @@ This is an experimental feature and may change in future releases.
 [ERC-7710](https://eip.tools/eip/7710) introduces a standard way for MetaMask Smart Accounts to delegate capabilities to other
 smart accounts or externally owned accounts (EOAs).
 
-The MetaMask Delegation Toolkit provides two experimental functions, `erc7710BundlerActions()` and `erc7710WalletActions()`, that let
+The MetaMask Smart Accounts Kit provides two experimental functions, `erc7710BundlerActions()` and `erc7710WalletActions()`, that let
 a caller redeem delegations granted by MetaMask's permissions system.
 
 ## Extract relevant data
@@ -65,7 +65,7 @@ This data encodes the authority that lets the delegate redeem the permission.
 ### Security considerations for `accountMeta`
 
 When a user grants a permission, they can provide `accountMeta` which is an array of `factory` and `factoryData` values.
-These calls must be executed before redeeming the permission (this is handled for you in [`sendUserOperationWithDelegation`](../reference/erc7715/bundler-client.md#senduseroperationwithdelegation)).
+These calls must be executed before redeeming the permission (this is handled for you in [`sendUserOperationWithDelegation`](../reference/advanced-permissions/bundler-client.md#senduseroperationwithdelegation)).
 
 Because each `accountMeta` is an arbitrary call specified by the granter, it is important that these are executed carefully.
 We recommend taking the following precautions:
@@ -86,7 +86,7 @@ Redeem a delegation with a [MetaMask smart account](#redeem-with-a-metamask-smar
 To redeem a delegation with a MetaMask smart account, [create a smart account](../guides/smart-accounts/create-smart-account.md)
 and a [Viem Bundler Client](https://viem.sh/account-abstraction/clients/bundler).
 
-After setting up your Bundler Client, you can extend its functionality with `erc7710BundlerActions` actions to support ERC-7710. Once extended, use [`sendUserOperationWithDelegation`](../reference/erc7715/bundler-client.md#senduseroperationwithdelegation) to redeem the permission.
+After setting up your Bundler Client, you can extend its functionality with `erc7710BundlerActions` actions to support ERC-7710. Once extended, use [`sendUserOperationWithDelegation`](../reference/advanced-permissions/bundler-client.md#senduseroperationwithdelegation) to redeem the permission.
 
 <Tabs>
 <TabItem value="example.ts">
@@ -128,8 +128,8 @@ import { createPublicClient, http, createBundlerClient } from "viem";
 import { generatePrivateKey, privateKeyToAccount } from "viem/accounts";
 import { sepolia as chain } from "viem/chains";
 import { createBundlerClient } from "viem/account-abstraction";
-import { erc7710BundlerActions } from "@metamask/delegation-toolkit/experimental";
-import { toMetaMaskSmartAccount, Implementation } from "@metamask/delegation-toolkit";
+import { erc7710BundlerActions } from "@metamask/smart-accounts-kit/actions";
+import { toMetaMaskSmartAccount, Implementation } from "@metamask/smart-accounts-kit";
 
 export const publicClient = createPublicClient({
   chain: chain,
@@ -168,7 +168,7 @@ export const bundlerClient = createBundlerClient({
 
 To redeem a delegation with an EOA, create a [Viem Wallet Client](https://viem.sh/docs/clients/wallet).
 
-After creating your Wallet Client, you can extend its functionality with `erc7710WalletActions` actions to support ERC-7710. Once extended, use [`sendTransactionWithDelegation`](../reference/erc7715/wallet-client.md#sendtransactionwithdelegation) to redeem the permission.
+After creating your Wallet Client, you can extend its functionality with `erc7710WalletActions` actions to support ERC-7710. Once extended, use [`sendTransactionWithDelegation`](../reference/advanced-permissions/wallet-client.md#sendtransactionwithdelegation) to redeem the permission.
 
 <Tabs>
 <TabItem value="example.ts">
@@ -212,7 +212,7 @@ const hash = walletClient.sendTransactionWithDelegation({
 import { http, createPublicClient, createWalletClient } from "viem";
 import { generatePrivateKey, privateKeyToAccount } from "viem/accounts";
 import { sepolia as chain } from "viem/chains";
-import { erc7710WalletActions } from "@metamask/delegation-toolkit/experimental";
+import { erc7710WalletActions } from "@metamask/smart-accounts-kit/actions";
 
 export const publicClient = createPublicClient({
   chain,

delegation-toolkit/experimental/erc-7715-request-permissions.md

@@ -15,7 +15,7 @@ It requires MetaMask Flask 13.5.0 or later, and may change in future releases.
 [ERC-7715](https://eip.tools/eip/7715) introduces a standard way for dapps to request permissions from a wallet to execute
 transactions on a user's behalf.
 
-The MetaMask Delegation Toolkit provides the experimental actions for ERC-7715 that lets a caller request permissions from MetaMask's permissions system.
+The MetaMask Smart Accounts Kit provides the experimental actions for ERC-7715 that lets a caller request permissions from MetaMask's permissions system.
 
 ## Request permissions
 
@@ -63,8 +63,8 @@ const grantedPermissions = await walletClient.grantPermissions([{
 import { createWalletClient, custom, createPublicClient, http } from "viem";
 import { generatePrivateKey, privateKeyToAccount } from "viem/accounts";
 import { sepolia as chain } from "viem/chains";
-import { erc7715ProviderActions } from "@metamask/delegation-toolkit/experimental";
-import { toMetaMaskSmartAccount, Implementation } from "@metamask/delegation-toolkit";
+import { erc7715ProviderActions } from "@metamask/smart-accounts-kit/actions";
+import { toMetaMaskSmartAccount, Implementation } from "@metamask/smart-accounts-kit";
 
 const publicClient = createPublicClient({
   chain: chain,
@@ -165,7 +165,7 @@ You should always verify the granted permissions and adjust your dapp's behavior
 ## Security considerations for `accountMeta`
 
 When a user grants a permission, they can provide [`accountMeta`](erc-7710-redeem-delegations.md#extract-relevant-data) which is an array of `factory` and `factoryData` values.
-These calls must be executed before redeeming the permission (this is handled for you in [`sendUserOperationWithDelegation`](../reference/erc7715/bundler-client.md#senduseroperationwithdelegation)).
+These calls must be executed before redeeming the permission (this is handled for you in [`sendUserOperationWithDelegation`](../reference/advanced-permissions/bundler-client.md#senduseroperationwithdelegation)).
 
 Because each `accountMeta` is an arbitrary call specified by the granter, it is important that these are executed carefully.
 We recommend taking the following precautions:

delegation-toolkit/experimental/store-retrieve-delegations.md

@@ -29,7 +29,7 @@ Create the `DelegationStorageClient` instance, and configure it using your API k
 import { 
   DelegationStorageClient, 
   DelegationStorageEnvironment 
-} from "@metamask/delegation-toolkit/experimental";
+} from "@metamask/smart-accounts-kit/experimental";
 
 const delegationStorageClient = new DelegationStorageClient({
   apiKey: "<YOUR-API-KEY>",
@@ -62,7 +62,7 @@ const delegationHash = await delegationStorageClient.storeDelegation(delegation)
 import { 
   DelegationStorageClient, 
   DelegationStorageEnvironment 
-} from "@metamask/delegation-toolkit/experimental";
+} from "@metamask/smart-accounts-kit/experimental";
 
 export const delegationStorageClient = new DelegationStorageClient({
   apiKey: "<YOUR-API-KEY>",
@@ -90,7 +90,7 @@ A delegation can be a root delegation, where its `authority` is `0xfffffffffffff
 
 ```typescript
 import { delegationStorageClient } from "./config.ts";
-import { getDelegationHashOffchain } from "@metamask/delegation-toolkit";
+import { getDelegationHashOffchain } from "@metamask/smart-accounts-kit";
 
 // Assuming you have the leaf delegation
 const delegationHash = getDelegationHashOffchain(leafDelegation);
@@ -107,7 +107,7 @@ const delegationChain: Delegation[] = await delegationStorageClient.getDelegatio
 import { 
   DelegationStorageClient, 
   DelegationStorageEnvironment 
-} from "@metamask/delegation-toolkit/experimental";
+} from "@metamask/smart-accounts-kit/experimental";
 
 export const delegationStorageClient = new DelegationStorageClient({
   apiKey: "<YOUR-API-KEY>",
@@ -158,7 +158,7 @@ const receivedDelegations = await delegationStore.fetchDelegations(
 import { 
   DelegationStorageClient, 
   DelegationStorageEnvironment 
-} from "@metamask/delegation-toolkit/experimental";
+} from "@metamask/smart-accounts-kit/experimental";
 
 export const delegationStorageClient = new DelegationStorageClient({
   apiKey: "<YOUR-API-KEY>",