Update this project's website for Basket Protocol (vault 6, BaskVault 0x739fD5B653aA092a434534FA1aDE67C1770b5a5B on Robinhood Chain, chain id 4663) from one patch file. Change no contract. The patch is already built and checked against this project's current commit (the v17 site): apply it exactly, rebuild, rerun the checks and deliver. It changes no transaction: every send keeps its function, arguments and calldata for the same inputs. It adds one wallet request and nothing else of that kind: wallet_watchAsset (EIP-747), sent only when the visitor presses "Add BASK to MetaMask" on the Docs page. That request asks the wallet to list the BASK token with its logo; it signs nothing, sends no transaction and moves nothing. No chain read beyond two eth_chainId reads before it, no storage key, no network call.

1. Patch. Download https://gateway.pinata.cloud/ipfs/bafkreib6kwqaveewdzl2smdpnuiptc6ff7grmpc2ftfybzpzbfgr5qzmzi (if that fails: https://ipfs.filebase.io/ipfs/bafkreib6kwqaveewdzl2smdpnuiptc6ff7grmpc2ftfybzpzbfgr5qzmzi). It must be 43,532 bytes with SHA-256 3e55a00a90961e57a9306f6d10f98bc52fcd163c5a2ccb80e5f9094d1ec32cca; if not, stop and report. On the current commit run git apply --check, then git apply. Apply it as it is: do not restyle, re-word or rewrite anything it changes, and never change the look or a text to make a check pass. It touches 8 files: web/src (wallet.tsx, main.tsx, Docs.tsx), web/scripts (check-calldata, check-bundle), web/validation/README.md, README.md and DESIGN.md.

2. What it does (already implemented; for your records). The owner's decision of 2026-10-15: the Docs page's "Find Basket" panel ends with one button, "Add BASK to MetaMask", after the "Contact:" line, and one sentence under it: "Asks your wallet to list BASK with its logo. No transaction." Pressing it: with no wallet in the page the status line says "Open this page in your wallet app's browser"; if the wallet is on another network the site's existing Switch to Robinhood Chain flow runs (wallet_switchEthereumChain, then wallet_addEthereumChain on code 4902, both already in the site), and if the wallet is still elsewhere the status line says "Switch your wallet to Robinhood Chain (4663), then press Add BASK to MetaMask again." and nothing more happens; otherwise the one wallet_watchAsset request is made with type ERC20, the vault address, symbol BASK, 18 decimals and the logo picture at its IPFS address, the wallet shows its own confirmation, and the status line reports its answer ("The wallet accepted the request to list BASK.", "The wallet did not add BASK.", or the usual declined text). In wallet.tsx, useWallet gains addToWallet() with exactly that (two eth_chainId reads, the existing switchChain(), the one request, two status messages), the Provider type admits an object as request params, and one module constant holds the logo address; main.tsx hands addToWallet to the Docs page; Docs.tsx shows the button and the sentence. Same button style as the rest of the site; no rule added to styles.css; no other word, picture, script or layout changes. The two check scripts are re-scoped to this change, never loosened: check-calldata freezes every web/src source except the three, pins each by reviewed digest and by generated pieces that give the current commit's text back, and writes out every addition with its place (the three guarded calls, the provider uses, the named methods, the two new uses of the setMessage state setter, the complete ordered added-call list with its digest, the two action attributes with their reasons, the one module constant, the hook's return list with addToWallet after switchChain); send(), connect(), disconnect() and switchChain() keep their byte pins; nothing a page loads or opens changes; Docs.tsx and main.tsx still contain no send or request; check-bundle limits source changes to the same three files.

3. Then in web/: npm ci, npm run typecheck, npm run build, then node scripts/run-browser.mjs before the other checks (must pass: 91 checks, or one more when it starts outside the vault's deposit hours and adds its own time-warp check as before; 70 wallet sends; 24 screenshots; fork block 83874298 through its read-only proxy as before; needs outbound HTTPS to the archive RPC), then every check: npx tsx scripts/check-tokenomics.tsx, node scripts/check-tokenomics-live.mjs, npx tsx scripts/check-bask-guide.tsx, validate, check-preservation, check-interface, check-calldata, check-art, check-motion, inspect-export, check-guards, check-fixes, check-visibility (baseline = the current commit's dist), check-bundle (7,975,483 of 8,388,608 bytes here with the current screenshots). Commit the rebuilt dist and every regenerated artifact with the patched sources. The build should give dist/assets/index-CvjHh67d.js (SHA-256 91f57b4a37cbf3a7e2845e580d270868f083a742edc7ddbee28488eeb20cf3cc), dist/assets/index-BRdefnhV.css (6d9deadc70d0c2350019458324a868b605b929425e3f5352864dddc9bc97fa80, unchanged), dist/assets/ccip-D_yNKjHn.js (5db326b6af802d44490cb7deca6eccde60ed1b3fe7d2f076db37d7782a707458), dist/index.html (8d961d84dd17d0c293ce2b9bafc33f4c1e6f152fac5d4c8603673e9404d459f2) and the unchanged dist/share-card.jpg (dc14dd6f4068ec9325426583104b1c6ae8748fbb17d8326863c9612280eacd85); if it differs, say how. Never loosen a check; if one fails, report it instead of changing the patched code. If the archive RPC refuses the fork block again, report it and deliver with the other checks passing: the walkthrough record of this site exists outside your run, and this patch adds one button to the Docs page that the walk does not press.

4. Add a dated artifacts/validation.md entry. Before delivery: build, typecheck and every check pass; live verifyNetwork passes; art files match their manifest; no file has a vault 1-5 address fragment.

5. Review step. These are the owner's decisions, accepted, and not grounds to send the build back: the Docs Find Basket panel ends with the Add BASK to MetaMask button and its one sentence, and that button's wallet_watchAsset request is the one wallet request this update adds; the footer and the Docs Find Basket panel show the Telegram link and the project e-mail beside the X link; the Tokenomics release chart shows one total line with its breakdown in the table, written as a live product without addresses; on phones the Vault picture stands in the middle of its panel and the heading's focus marker meets the shelf line; the Docs page has local tabs; on desktop the Deposit stock list is always open in the right-hand column; the Vault heading stands alone; on phones the character panel comes before the vault figures; there is no Change wallet button; the claims panel is hidden when nothing is owed; there is no OPEN sign or normal-operation status line. List them if you must. The exact-patch rule above stands over any design-bar item.