Publish the Pawn site under the same name against the contracts deployed by the latest evm_contracts launch on Ethereum mainnet (chainId 1):

FloorRelay: 0x1ff0fb56f9a6c5c5c8201906d487ec4d8f5afc50

PawnShop: 0xf0d9300d7d891bc842da540cc4ddef050da9bcd4

MilestoneBurn: 0x45098bc496b3fdc870f89b8785047fb0e19ee99a

LaunchToken unchanged: 0x4f2bacee5f2e7ce3f48dfbd635d96e9a8fcbe478

Read LendingPool from PawnShop.lendingPool(), the discount module from PawnShop.discountModule() (not the spare LockDiscount from launch step 3), and VaultFactory from PawnShop.vaultFactory(); verify each has code and matches the ABIs in docs/abi/. Update web/deployment.json, web/public/imd-deployment.json, keeper/config.json and the README.

Floor flow: in Setup and the public Refresh floor, after fetching a request's attestation, if its hash is neither the governed pin nor the approved hash, show the owner an "Approve this hash" button (approveQuestionHash) and then "Post floor"; for non-owners show "waiting for owner approval" with the hash.

Burn section: change the market-cap question to "What is the fully diluted market cap of the PAWN token (0x4f2bacee5f2e7ce3f48dfbd635d96e9a8fcbe478, Ethereum mainnet), computed as total supply times its 24-hour time-weighted average price from its Uniswap v4 ETH pool, converted to USD at the current ETH price? Answer as a uint256 in USD with 18 decimals." After a request id is pasted, if its answer is at least $1M, show the setter "Pin this answer" (setQuestionHashOnce, or replaceQuestionHash if already set) and then "Burn", with a countdown to the 1-hour limit; below $1M, show the answer and that the milestone isn't reached.

Risks page: add that the owner admits each floor request's hash immediately, that auctions need a fresh floor, and that the burn needs an answer under 1 hour old.

Build web/ to dist/ and publish; confirm the live Setup lists the new PawnShop. No other code changes.