Merge branch 'main' into 2955-add-openfort-signer-guide

Author: joalavedra

.cursor/rules/content-types.mdc

@@ -68,15 +68,15 @@ Examples:
 - Describe and only describe. Be austere, neutral, and factual.
 - Match the parameter format used in surrounding reference pages. Some areas use tables (name,
   type, required/optional, description); others use nested bulleted lists (for example, JSON-RPC
-  method docs in Services). Be consistent with the existing convention in the same product section.
+  method docs in Snaps). Be consistent with the existing convention in the same product section.
 - Adopt standard patterns. Consistent structure lets readers find information quickly.
 - Mirror the structure of the API or code itself (for example, one section per method or endpoint).
 - Include short usage examples to illustrate parameters and return values.
 - Keep explanatory prose to the minimum needed to use the API correctly.
 - Do not include tutorials or extended how-to steps.
 - Examples: `snaps/reference/config-options.md`,
   `smart-accounts-kit/reference/delegation/delegation-scopes.md`,
-  `services/reference/solana/json-rpc-methods`
+  `snaps/reference/snaps-api/wallet_snap`
 
 ### `tutorials/` - Tutorial
 

.cursor/rules/contributor-workflow.mdc

@@ -12,15 +12,16 @@ the requirements that are most often missed.
 
 Every new documentation page must be added to the appropriate sidebar file:
 
-| Product             | Sidebar file              |
-| ------------------- | ------------------------- |
-| MetaMask Connect    | `mm-connect-sidebar.js`   |
-| Embedded Wallets    | `ew-sidebar.js`           |
-| Smart Accounts Kit  | `gator-sidebar.js`        |
-| Agent Wallet        | `agent-wallet-sidebar.js` |
-| Services            | `services-sidebar.js`     |
-| Developer dashboard | `dashboard-sidebar.js`    |
-| Snaps               | `snaps-sidebar.js`        |
+| Product            | Sidebar file              |
+| ------------------ | ------------------------- |
+| MetaMask Connect   | `mm-connect-sidebar.js`   |
+| Embedded Wallets   | `ew-sidebar.js`           |
+| Smart Accounts Kit | `gator-sidebar.js`        |
+| Agent Wallet       | `agent-wallet-sidebar.js` |
+| Agent Wallet       | `agent-wallet-sidebar.js` |
+| Snaps              | `snaps-sidebar.js`        |
+
+Infura API and dashboard documentation is maintained in [docs.infura](https://github.com/INFURA/docs.infura), not in this repository. Link to `https://docs.infura.io/` from MetaMask docs when referencing Infura APIs or the Infura dashboard.
 
 ## Redirects
 
@@ -43,7 +44,6 @@ Place images in the product's designated asset folder:
 - `metamask-connect/*/_assets/`
 - `static/img/embedded-wallets/` (Embedded Wallets product images)
 - `smart-accounts-kit/assets/`
-- `services/images/`
 - `snaps/assets/`
 - `static/img/` (for site-wide assets)
 
@@ -85,6 +85,13 @@ that enforces Microsoft style, Consensys terminology, and spelling. Fix any lint
 requesting review. If a warning is a false positive, add the term to the Vale vocabulary file rather
 than rewriting valid technical language.
 
+> **Warning:** Do not wire Vale into the Husky `pre-commit` hook (`lint-staged` in `package.json`).
+> Vale is intentionally CI-only. It frequently reports false positives on valid technical content
+> (for example, code identifiers like `wagmi-tab`, product names, and intentional ellipses) and lints
+> the entire staged file rather than just your diff, so running it on commit blocks unrelated,
+> pre-existing content and stalls otherwise-valid commits. Let the PR CI run Vale; contributors can
+> still run it on demand with `npm run docs:ci`.
+
 ## Pull requests
 
 - Summarize what changed and why in the PR description. Do not just list files.

.cursor/rules/product-infura.mdc

@@ -0,0 +1,22 @@
+---
+description: Infura documentation has moved to docs.infura.io. Do not add Infura API or dashboard content to metamask-docs.
+alwaysApply: true
+---
+
+# Infura documentation
+
+Infura API reference, guides, and dashboard documentation are published at [docs.infura.io](https://docs.infura.io/).
+
+- **Repository:** [INFURA/docs.infura](https://github.com/INFURA/docs.infura)
+- **Dashboard:** [app.infura.io](https://app.infura.io/)
+
+When MetaMask product docs need to reference Infura:
+
+- Use absolute links to `https://docs.infura.io/` (for example, `https://docs.infura.io/dashboard/get-started/create-api/`).
+- Do not recreate Infura content under `services/` or `developer-tools/dashboard/` in this repository.
+- The faucet remains on MetaMask docs at `/developer-tools/faucet/`.
+
+Cross-domain redirects in `vercel.json` send legacy `/services/*` and `/developer-tools/dashboard/*`
+URLs to `https://docs.infura.io/`. List specific rules before the catch-all fallbacks; map renamed
+paths (for example `/services/gas-api/` → `https://docs.infura.io/reference/gas-api/`). The faucet
+stays on MetaMask docs at `/developer-tools/faucet/` and is not redirected.

.cursor/rules/product-services.mdc

@@ -19,7 +19,8 @@ Help create a new documentation page that follows MetaMask editorial standards f
 Ask the user for any information they have not already provided:
 
 1. **Product area** - which product is this for? (MetaMask Connect, Embedded Wallets,
-   Smart Accounts Kit, Services, Snaps, Developer Tools)
+   Smart Accounts Kit, Agent Wallet, Snaps). Infura API and dashboard docs live at
+   [Infura documentation](https://docs.infura.io/) and are not authored in this repository.
 2. **Content type** - what kind of page? (concept/explanation, how-to guide, quickstart,
    reference, tutorial, troubleshooting)
 3. **Topic** - what is the page about?
@@ -43,9 +44,9 @@ front-matter fields, intro style, and parameter formats.
 
 Create the file with the correct structure for its content type.
 
-### Frontmatter
+### Page metadata
 
-Follow **Frontmatter** in `.cursor/rules/markdown-formatting.mdc` (required `description`,
+Follow page metadata rules in `.cursor/rules/markdown-formatting.mdc` (required `description`,
 recommended `keywords`, optional `sidebar_label` only when the nav label would otherwise be too
 long or wordy, and the `title` vs duplicate H1 rule). Do not repeat or contradict that rule here.
 
@@ -217,11 +218,11 @@ description: <one sentence>
 
 Fill in the scaffold with content based on what the user provides. Follow these rules:
 
-- **Voice**: active, present tense, second person ("you"). Use contractions naturally.
+- **Voice**: active, present tense, second person ("you"). Use contractions where appropriate.
 - **First sentence**: get to the point. Answer "what" or "why" immediately.
 - **No em/en dashes**: use commas, parentheses, or semicolons.
 - **Sentence case** for all headings.
-- **One sentence per line**, wrapped at roughly 100 columns.
+- **One sentence per line**, wrapped at about 100 columns.
 - **Code blocks**: always include a language tag. Use `bash npm2yarn` for install commands.
 - **Terminology**: use the required forms from `terminology.mdc`.
 - **No marketing language**: no "powerful," "seamless," "best-in-class."
@@ -232,7 +233,7 @@ Fill in the scaffold with content based on what the user provides. Follow these
 
 Before finishing, check:
 
-- [ ] Frontmatter has `description`; add `sidebar_label` only when the default nav label would be
+- [ ] Page metadata includes `description`; add `sidebar_label` only when the default nav label would be
       too long or wordy (see `markdown-formatting.mdc`).
 - [ ] Opening paragraph answers "what" and "why" in the first 1-2 sentences.
 - [ ] Structure matches the content type.

.cursor/skills/author-page/SKILL.md

@@ -21,8 +21,9 @@ The user provides a file path or directory to review. If not provided, ask what
 Read the file path to determine:
 
 1. **Product area** - which product folder the file lives in (for example, `metamask-connect/`,
-   `services/`, `snaps/`). Load the corresponding product rule from `.cursor/rules/product-*.mdc`.
-2. **Content type** - which subfolder determines the expected structure (for example, `concepts/`,
+   `snaps/`, `agent-wallet/`). Load the corresponding product rule from `.cursor/rules/product-*.mdc`.
+   For Infura content, use `.cursor/rules/product-infura.mdc` and link to Infura documentation.
+2. **Content type** - which folder determines the expected structure (for example, `concepts/`,
    `how-to/`, `reference/`). Use `.cursor/rules/content-types.mdc` for the mapping.
 
 ## Step 2: Run Vale (if available)
@@ -44,7 +45,7 @@ source of truth for full criteria, examples, and edge cases.
 
 - Active voice and present tense used throughout.
 - Second person ("you"), not "the developer" or "users."
-- Contractions used naturally.
+- Contractions used where appropriate.
 - No marketing language, superlatives, or promotional tone.
 - No em dashes or en dashes; use commas, parentheses, or semicolons.
 - First sentence of each section gets to the point.
@@ -57,16 +58,16 @@ source of truth for full criteria, examples, and edge cases.
   "Chain Agnostic Improvement Proposal 25 (CAIP-25)"), short form on subsequent references.
 - Product-specific terminology matches the corresponding `product-*.mdc` rule file.
 
-### Markdown formatting (markdown-formatting.mdc)
+### Markdown formatting (`markdown-formatting.mdc`)
 
-- Lines wrapped at roughly 100 columns.
+- Lines wrapped at about 100 columns.
 - Each sentence on its own line.
 - Code blocks have a language tag.
 - Links use relative paths within the product, absolute paths across products.
 - Descriptive link text; no "click here" or bare URLs.
 - Admonitions use Docusaurus syntax and are not nested.
 - Tables are aligned in source Markdown.
-- No duplicate H1 if frontmatter contains a `title` field.
+- No duplicate H1 if page metadata contains a `title` field.
 
 ### Content type compliance (content-types.mdc)
 
@@ -77,11 +78,11 @@ source of truth for full criteria, examples, and edge cases.
 - Quickstart pages: complete, copy-paste-and-run code.
 - Troubleshooting pages: symptom/error first, then fix.
 
-### Frontmatter
+### Page metadata
 
 - `description` field present (one sentence for SEO).
 - `sidebar_label` only when needed (default nav label would be too long or wordy); otherwise omit.
-- No duplicate H1 if `title` is set in frontmatter.
+- No duplicate H1 if `title` is set in page metadata.
 
 ### Contributor workflow (contributor-workflow.mdc)
 
@@ -94,7 +95,7 @@ source of truth for full criteria, examples, and edge cases.
 Present findings as a structured report grouped by category. For each issue:
 
 1. **Line number** - approximate location in the file.
-2. **Category** - Voice/Tone, Terminology, Formatting, Content Type, Frontmatter, or Workflow.
+2. **Category** - Voice/Tone, Terminology, Formatting, Content Type, Page metadata, or Workflow.
 3. **Issue** - what is wrong.
 4. **Suggestion** - how to fix it.
 
@@ -123,7 +124,7 @@ Present findings as a structured report grouped by category. For each issue:
 - Page is in `concepts/` but contains numbered step-by-step instructions. Move steps to a
   how-to page and link to it.
 
-### Frontmatter
+### Page metadata
 - Missing `description` field.
 ```
 

.cursor/skills/style-review/SKILL.md

@@ -102,18 +102,75 @@ jobs:
         if: steps.changed-files.outputs.any_changed != 'true'
         run: echo "No matching changed files; Prettier check skipped."
 
+  # Vale checks spelling/style on changed .md/.mdx files and fails on real Vale errors,
+  # matching what runs locally (scripts/docs-pre-commit-check.sh) so "passes locally"
+  # means "passes on CI". The matrix keeps the required check names "Spelling (.md)" and
+  # "Spelling (.mdx)". Vale runs directly (not via the reviewdog-based composite action)
+  # so large PRs do not hit GitHub's 300-file diff limit, which is an infrastructure
+  # failure unrelated to content.
   spelling:
     name: Spelling
     runs-on: ubuntu-latest
     strategy:
+      fail-fast: false
       matrix:
         file-extensions: ['.md', '.mdx']
     steps:
       - uses: actions/checkout@v6
         with:
           fetch-depth: 0
-      - name: Vale
-        uses: Consensys/github-actions/docs-spelling-check@main
+      - name: Checkout Vale config
+        uses: actions/checkout@v6
+        with:
+          repository: Consensys/github-actions
+          path: .github-actions
+      - name: Changed files
+        id: changed-files
+        uses: tj-actions/changed-files@22103cc46bda19c2b464ffe86db46df6922fd323 # 47.0.5; pin matches docs-spelling-check
+        with:
+          path: .
+          files: '**/*${{ matrix.file-extensions }}'
+          separator: ','
+      - name: Install Vale
+        if: steps.changed-files.outputs.any_changed == 'true'
+        env:
+          VALE_VERSION: '3.15.1'
+        run: |
+          set -euo pipefail
+          curl -sSfL "https://github.com/errata-ai/vale/releases/download/v${VALE_VERSION}/vale_${VALE_VERSION}_Linux_64-bit.tar.gz" -o /tmp/vale.tar.gz
+          sudo tar -xzf /tmp/vale.tar.gz -C /usr/local/bin vale
+          vale --version
+          (cd .github-actions/docs-spelling-check && vale sync)
+      - name: Run Vale
+        if: steps.changed-files.outputs.any_changed == 'true'
+        # Vale is advisory only and must not block merges: it produces false positives on
+        # valid technical content (code identifiers like `wagmi-tab`, product names,
+        # intentional ellipses). `continue-on-error` MUST be at the step (not the job) so
+        # the job still concludes "success" and the required "Spelling" check passes while
+        # findings stay visible in the logs. Job-level `continue-on-error` does not work
+        # here: it only keeps the overall run green, but the job's own check run stays
+        # "failure" and a required status check keeps blocking the merge.
+        continue-on-error: true
+        env:
+          ALL_CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
+        run: |
+          set -euo pipefail
+          files=()
+          IFS=',' read -ra raw <<< "$ALL_CHANGED_FILES"
+          for f in "${raw[@]}"; do
+            f="${f#"${f%%[![:space:]]*}"}"
+            f="${f%"${f##*[![:space:]]}"}"
+            [ -z "$f" ] && continue
+            [ -f "$f" ] && files+=("$f")
+          done
+          if [ ${#files[@]} -eq 0 ]; then
+            echo "No existing ${{ matrix.file-extensions }} files to check."
+            exit 0
+          fi
+          vale --config .github-actions/docs-spelling-check/.vale.ini "${files[@]}"
+      - name: No spelling-scoped files changed
+        if: steps.changed-files.outputs.any_changed != 'true'
+        run: echo 'No matching changed files; Vale check skipped.'
 
   linkCheck:
     name: Link Checking

.github/workflows/ci.yml

@@ -1,9 +1,7 @@
 dirs:
   - ./smart-accounts-kit
-  - ./developer-tools
   - ./embedded-wallets
   - ./metamask-connect
-  - ./services
   - ./snaps
 excludedDirs:
   - ./build
@@ -22,14 +20,15 @@ ignorePatterns:
   - pattern: '^http(s)?://help.figma.com'
   - pattern: '^http(s)?://metamask.io'
   - pattern: '^http(s)?://rivet.cloud'
+  - pattern: '^http(s)?://tenderly\.co'
+  - pattern: '^http(s)?://docs\.tenderly\.co($|/.*)'
   - pattern: '^http(s)?://app\.infura\.io($|/.*)'
   - pattern: '^http(s)?://docs.arbitrum.io($|/.*)'
   - pattern: '^/img/'
   - pattern: '^/smart-accounts-kit/'
   - pattern: '^/developer-tools/'
   - pattern: '^/embedded-wallets/'
   - pattern: '^/metamask-connect/'
-  - pattern: '^/services/'
   - pattern: '^/snaps/'
   - pattern: '^/wallet/'
   - pattern: '^/tutorials/'
@@ -38,6 +37,7 @@ ignorePatterns:
   - pattern: 'https://0xfury.com/privacy'
   - pattern: '^https://docs.arbitrum.io'
   - pattern: '^https://nodefleet.org'
+  - pattern: '^https://bwarelabs.com'
 aliveStatusCodes:
   - 200
   - 206