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 v22 site, 3038c97): apply it exactly, rebuild, rerun the checks and deliver. It adds the pages for ITEM, the reward token this account launched in job f74046f2-c50a-427c-95b4-3f8762f59392 (source https://github.com/identity-md-launches/launch-2241-item at commit f0f84fcd6637ea334d50af06b8f694c19b643461): an Earn page, a Transparency page and a Find ITEM panel in Docs, with reads of the five ITEM contracts and 17 wallet sends to them and to the Uniswap v2 router. Every existing vault send keeps its calldata for the same inputs; the vault's reads, wallet flows, pending-transaction guard and storage keys are unchanged.

1. Patch. Download https://gateway.pinata.cloud/ipfs/bafybeigp7ajnbc43kawwhuvacs74cqyilrigptywhlia3zndjo4pu4ai7e (if that fails: https://ipfs.filebase.io/ipfs/bafybeigp7ajnbc43kawwhuvacs74cqyilrigptywhlia3zndjo4pu4ai7e). It must be 8,040,187 bytes with SHA-256 95255121cde00b4958ed1a0ef69f566ca108105a480dea76b644c70f944a1e35; if not, stop and report. On 3038c97 run git apply --check, then git apply (it carries binary files). Apply it as it is: do not restyle, re-word or rewrite anything it changes, never change the look or a text to make a check pass. It touches 96 files: 16 under web/src, 13 check and walk scripts, two pictures and the font licence under web/public (line endings normalised), three notes, and under artifacts/ the final run's evidence, so every check below can pass from the patch alone (a walk run here regenerates it).

2. Addresses (all in web/src/itemConstants.ts, the only place an ITEM address lives, each with its pinned runtime code hash checked on chain before every ITEM send): ITEM 0x4F1b7a5aAF3768F7500E9ab5CBBF3762834e8B57; ItemStaking 0x7e82d352d3f6336e474ba28040785414a8e2e1d3; BaskUsdgGauge 0xf5ebbf7a60b22fb38270ab4942585ad1654a9a11; ItemEthGauge 0x5a2fc207f7d9f84426b8c0f7908a492450e0add6; DevVesting 0xf1670d095d32b1011aa843e7b7d44eeb7ba222c7; ITEM/ETH Uniswap v2 pair 0x9a2B386290Cbfeb40be6EDA694de73B97D66B269 (= getPair(ITEM, WETH)); BASK/USDG pair 0xCC23688c49D58c5FF1f3Bf77e3cAB1927cBa6e70; Uniswap v2 router 0x89e5DB8B5aA49aA85AC63f691524311AEB649eba (hash pinned too, as USDG's).

3. What it does. Earn (#earn; in the navigation): a Pool selector (BASK/USDG, ITEM/ETH) shows one of two pool cards; a pool card has tabs Add liquidity, Stake, Manage, Pool stats (Approve for the exact amount to that gauge only, Stake, Withdraw, Claim ITEM, off until the gauge starts; Add liquidity: one amount typed, the other matched from the reserves read at the press, exact approvals to the router only, minimums 0.5% under, a 600-second deadline, off without a wallet or an unseeded pool; a link to Uniswap); the ITEM staking card has tabs Stake, Manage, Staking stats (the wallet's stake and unclaimed BASK with an indicative USD value; Approve to ItemStaking only, Stake, Unstake, Claim BASK). Figures: ITEM per day per pool token and for the wallet; the BASK fee pot, the wallet's share and estimated BASK. Transparency (#transparency; footer link, not in the navigation): one "Contracts and source" panel. Docs: a "Find ITEM" panel after "ITEM risks"; "the Earn page" in the ITEM panels links to #earn; the Tokenomics live figures now show; the footer and Find Basket gain a "Basket Protocol on Medium" link (medium.com/@protocolbasket, new tab) after Telegram. Sends, 17: approve, stake, withdraw, claim on each gauge; approve, stake, unstake, claim(BASK) on ItemStaking; BASK, USDG and ITEM approve to the router; the router's addLiquidity and addLiquidityETH (the only send carrying ETH); approvals exact, never unlimited; no start, fund, release, sync, swap or removeLiquidity. Each ITEM send checks chain id 4663, the account and the target's code hash and simulates before the wallet prompt. New reads: the existing RPC path plus eth_getBalance; no polling. Checks, re-scoped, nothing loosened: check-calldata has HEAD 3038c97, unlisted web/src sources byte-identical, the vault's sends equal case by case (496 identical, 1,773 refused), the 17 ITEM actions, 51 encodings and 15 null-slot guards pinned, no vault send builder carries a value; check-visibility and check-art compare with 3038c97 outside the new parts, v22's assertions kept; run-browser.mjs keeps every previous check in order and its 70 sends.

4. First copy the 3038c97 dist outside the tree; BASKET_BASELINE_DIST= for the vault walk, check-art and check-visibility. Then in web/: npm ci, npm run typecheck, npm run build. The vault walk first, on a build with every LAUNCH value in src/itemConstants.ts null (its fork block 83874298 predates ITEM): copy the file outside the tree, null the values, npm run build, npx tsx scripts/run-browser.mjs (95 checks, one more outside the vault's deposit hours; 70 sends; 24 screenshots; needs the archive RPC and Python 3 with Pillow, or BASKET_SCREENSHOT_PYTHON), then restore the copy and npm run build. Then the ITEM walk: item-walk.json, outside the tree, = every LAUNCH entry of src/itemConstants.ts as written (15 keys) plus "RPC":"https://rpc.mainnet.chain.robinhood.com" and "BLOCK_NUMBER":"92775649"; BASKET_ITEM_CONFIG= npx tsx scripts/run-item-browser.mjs (anvil forks that block; 45 checks, 17 sends, 23 states). Then every check in web/validation/README.md, plus npx tsx scripts/check-item.ts and check-calldata also with BASKET_ITEM_FINAL=1; check-bundle (7,904,218 of 8,388,608 bytes here). Commit the rebuilt dist and every regenerated artifact with the patched sources; the build should give index-Dj-S4okR.js 9f2e0d70df68479406373cc0ecb4c57114f0907ac820d4d9fc2d661bcf34e420, index-iwMuzi_G.css c5fffa787f4bd972bb636887fe5051064164cca4e6b2e25cb7593251071f4e9d, index.html 2de25c03b3afd9ceeee78f95d9938273d7911feb63bedfac9bbf77067bda8409; the ccip chunk only re-points to the new index file, the share card unchanged (say how if any differs). Never loosen a check; if one fails, report it instead of changing the patched code. Only a walk this machine cannot run (no archive RPC, no Pillow) may be skipped, reported: both walk records and every capture in the patch are from the final run.

5. 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; no ITEM address outside web/src/itemConstants.ts and the generated artifacts.

6. Review step. The owner's decisions, accepted, not grounds to send the build back: Transparency is not in the navigation; no setup page or button (the owner sets up by hand); the ITEM staking card shows BASK rewards only, with a USD estimate from the vault's figures; the Add liquidity form has no zap, swap, removal or APR; ITEM firs