Approved workflow

Release Gradients (ERC-20 symbol GRAD) on Sepolia as an evm_project: the fixed-supply launch token plus one application contract. Token: Gradients (GRAD), total supply 1,000,000,000 GRAD with 18 decimals, minted once to the deployer. Application contract: GradientNFT. Currency: GRAD is the app's working currency. GradientNFT's constructor takes one argument, the GRAD address (constructorArgs ["$token"]); it stores the token immutable, exposes it as token(), and holds no GRAD at deploy and never needs any: users get GRAD by swapping Sepolia ETH in the ETH/GRAD launch pool the factory seeds. The only GRAD movement is the mint payment, approve + SafeERC20.safeTransferFrom straight from the minter to 0x000000000000000000000000000000000000dEaD (a burn); there are no payouts. GradientNFT has no payable function and no receive/fallback, so it never holds ETH. No owner, admin, withdraw, pause or upgrade path: GradientNFT never holds any value. GradientNFT is an OpenZeppelin ERC-721 named "Gradients" with symbol "GRADIENT" (both source constants) of at most 1,000 tokens, ids 1 to 1,000 in mint order. mint(uint256 quantity): quantity 1 to 10, otherwise revert; each token costs exactly 10,000 GRAD (10,000e18 units), moved with one safeTransferFrom(minter, 0x000000000000000000000000000000000000dEaD, 10,000e18 x quantity) straight from the minter to the burn address; a call that would take the supply past 1,000 reverts whole (no partial mint). Update the counter and take the payment before _safeMint (checks-effects-interactions), so a re-entrant onERC721Received cannot exceed the cap or mint unpaid. Art: tokenURI(id) reverts for unminted ids and otherwise returns data:application/json;base64 JSON with name "Gradient #", attributes (colour A, colour B, angle) and an image data:image/svg+xml;base64 of a 512x512 SVG with one linearGradient: h = keccak256(abi.encodePacked(id)); colour A = bytes 0-2 of h and colour B = bytes 3-5 as #rrggbb lowercase hex; angle = uint16(bytes 6-7) % 360 degrees. Only hex digits and decimal numbers are interpolated into the JSON/SVG. The art is a pure function of the id (no block data), so mint order decides who gets which art; say so in the README. Views: totalMinted(), MAX_SUPPLY, PRICE, burnedTotal() (= 10,000e18 x totalMinted), token(). Events: the ERC-721 Transfer plus Minted(minter, firstId, quantity). Tests (Foundry) must show: tokenURI decodes to JSON containing the SVG and is byte-identical across calls; unminted ids revert; quantity 0 and 11 revert; a quantity-10 mint at 995 minted reverts; minting exactly to 1,000 works and one more reverts; the dead address gains exactly 10,000e18 per token; GradientNFT's GRAD and ETH balances stay 0; missing allowance reverts; a re-entrant receiver cannot mint beyond the cap or unpaid. The independent adversarial review must attack: the cap and payment under re-entrancy, price overflow for large quantity, JSON/SVG injection, and any path that leaves GRAD or ETH stuck in the contract. Deploy through the project factory, then publish a one-page website to mint (quantity 1-10, cost in GRAD, remaining supply) and a gallery of minted gradients, 24 per page, rendering each tokenURI image in the page. The page reads the GRAD address from GradientNFT.token(), shows the connected wallet's GRAD balance and allowance, has an Approve step before every paying action, and says GRAD comes from swapping Sepolia ETH in the launch pool (no in-page swap). Lists come from contract views and events only (no backend, no indexer; log queries are chunked from the deployment block). Keep it to one small page; the static export has index.html in dist/.

Sepolia (11155111) only. GitHub publication and IPFS hosting are approved. Launch token: a separate fixed-supply ERC-20, 18 decimals, no constructor arguments, exactly 1,000,000,000 minted to msg.sender, no mint or admin functions. The factory sends that supply to LP and rewards, so no application contract may need a launch-token balance at deploy. Application contracts are fully configured in nonpayable constructors using only address, uint, bool or bytes32 arguments (no strings, arrays, proxies, delegatecall or selfdestruct); anything else is set at runtime. No owner unless the request names one, and then it is $owner. No external oracles, VRF or keepers: randomness is commit-reveal or a future blockhash read within 256 blocks with a refund path. foundry.toml sets bytecode_hash = "none". The website is a static export with index.html in dist/. Site label lab-onchain-gradients.

Build GRAD and GradientNFT (constructorArgs ["$token"]; each mint burns 10,000 GRAD to the dead address) with Foundry tests and an independent adversarial review, deploy them through the project factory, then build the mint page and gallery against the live deployment.

Mint (approve GRAD, then mint 1-10) and a paginated gallery that decodes tokenURI in the page; show GRAD balance and allowance.