From bf76c55dcec0ce407dec47bda8eb5e7bc4f95e2d Mon Sep 17 00:00:00 2001
From: Tom Ra <tomtom@reown.com>
Date: Wed, 21 Oct 2026 13:20:19 -0300
Subject: [PATCH 1/2] Document committed lockfile and self-hosted assets in
 AGENTS.md

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---
 AGENTS.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 60cbe21..18fc188 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -29,6 +29,8 @@ pnpm generate      # refetch the OpenAPI specs and regenerate the API reference
 
 Before finishing a change, run `pnpm build` for content changes, and `pnpm lint` plus `pnpm types:check` for code changes. For changes to routing, redirects, `next.config.mjs`, `worker/` or `wrangler.jsonc`, also check them in `pnpm preview`.
 
+`pnpm-lock.yaml` is committed and CI installs with `--frozen-lockfile`. When you change `package.json`, commit the updated lockfile.
+
 ## Project layout
 
 | Path | What it is |
@@ -160,6 +162,8 @@ Always wrap `<Accordion>` in `<Accordions>`. Use them for FAQs and optional deta
 
 - Prefer Markdown images, `![Copy the Project ID from the dashboard](/images/cloud/1.png)`: they get dimensions at build time and click-to-zoom. A raw `<img>` has neither, so use it only when you need attributes Markdown can't express.
 - Always write alt text that describes what the image shows.
+- Put every image and video in `public/images/` and reference it as `/images/...`. Don't link to Mintlify's CDN (`mintcdn.com`, `mintlify.s3...`): those files are going away.
+- Videos go in `public/images/videos/`, each under 25 MiB (Cloudflare's per-file limit). Use a `<video>` tag with `controls`.
 - Diagrams: a ` ```mermaid ` code block.
 - Math: `$$ ... $$` (KaTeX).
 

From bc840468ed9c9c0ede9166937742f37c3bddf6c1 Mon Sep 17 00:00:00 2001
From: Tom Ra <tomtom@reown.com>
Date: Wed, 21 Oct 2026 13:33:09 -0300
Subject: [PATCH 2/2] Reword chain abstraction diagram intro to match the
 sequence diagram

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---
 content/docs/wallets/features/chain-abstraction.mdx | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/content/docs/wallets/features/chain-abstraction.mdx b/content/docs/wallets/features/chain-abstraction.mdx
index 33eb78a..3282422 100644
--- a/content/docs/wallets/features/chain-abstraction.mdx
+++ b/content/docs/wallets/features/chain-abstraction.mdx
@@ -24,8 +24,7 @@ making the experience seamless for both the user and the application.
 For example, in given scenario, you need to have enough gas fees on OP Mainnet and Arbitrum. 
 </Callout>
 
-The diagram below shows an example scenario where a user is interacting with an app and is asked to transfer 225 USDC to the app on Base Network. 
-The user does not have any USDC on Base, but their wallet seamlessly allows them to source the funds from other networks. 
+The diagram below shows how the wallet, WalletKit and RPC work together when a transfer needs funds from another network.
 
 ![Sequence diagram of the chain abstraction flow between the user, app, wallet, WalletKit and RPC](/images/chain-abstraction-sequence.png)