Approved workflow

Release Pyre (ERC-20 symbol PYRE) on Sepolia as an evm_project: the fixed-supply launch token plus one application contract. Token: Pyre (PYRE), total supply 1,000,000,000 PYRE with 18 decimals, minted once to the deployer. Application contract: BurnLeaderboard. Currency: PYRE is the app's working currency. BurnLeaderboard takes the PYRE address as its only constructor argument (constructorArgs ["$token"]), stores it immutable, exposes it as token(), and holds no PYRE at deploy; players get PYRE by swapping Sepolia ETH in the launch pool the factory seeds. Every payment in is approve + SafeERC20.safeTransferFrom (permit not required). BurnLeaderboard has no payable function and no receive/fallback, so it never holds ETH. Payouts are pull-based (the recipient calls to collect; nothing is pushed to third parties), follow checks-effects-interactions and are nonReentrant. Burns are transfers to 0x000000000000000000000000000000000000dEaD. No owner, admin, pause or upgrade path. A burn leaderboard for PYRE with an all-time board and 7-day seasons. burn(amount): amount > 0; the contract moves PYRE straight from the caller to 0x000000000000000000000000000000000000dEaD with safeTransferFrom (it never holds PYRE), adds amount to the caller's lifetime total and current-season total, and updates two sorted top-10 lists (all-time and current season) in place: an address already listed moves up without duplicating, a new total must strictly exceed the 10th entry to enter, and on equal totals the address that reached it first ranks higher. Season = (block.timestamp - deployTimestamp) / 7 days; season boards are kept per season and never change after the season ends. sweep(): anyone may forward any PYRE that was sent to the contract directly to the dead address (credited to nobody), so nothing is stranded. Views: lifetimeOf(account), seasonTotalOf(season, account), topAllTime() and topSeason(season) returning (address, total)[10], currentSeason(), totalBurned(), token(). Events: Burned(account, amount, season, lifetimeTotal), Swept(amount). This redoes the earlier parked burn tracker (launch 122 stranded its supply): here the app needs no PYRE at deploy. Tests (Foundry) must cover: insertion and re-ordering in both top-10 lists, ties, an 11th address that does not exceed the 10th, a season rollover at the exact 7-day boundary, sweep, zero-amount burns, and the invariants that the contract's PYRE balance is 0 after every burn and that totalBurned equals the sum of lifetime totals. The independent adversarial review must attack: top-10 corruption (duplicates, wrong order, lost entries) under fuzzed burn sequences, gas growth of the sorted insert, season boundary off-by-one, and burns credited to the wrong address. Deploy through the project factory, then publish a one-page website to show the all-time and current-season top 10, your totals and rank (computed in the page from Burned events), and a burn form. The page reads the PYRE address from BurnLeaderboard.token(), shows the connected wallet's PYRE balance and allowance, has an Approve step before every paying action, and says that PYRE 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). 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-burn-leaderboard.

Build PYRE and BurnLeaderboard (BurnLeaderboard takes constructorArgs ["$token"] and burns PYRE to the dead address) with Foundry tests and an independent adversarial review, deploy them through the project factory, then build the one-page website against the live deployment.

One static page, no framework beyond what the skill needs, reading the live deployment's ABI and address. Approve PYRE before paying; show PYRE balance and allowance.