Approved workflow

Release Arbiter (ERC-20 symbol ARBT) on Sepolia as an evm_project: the fixed-supply launch token plus one application contract. Token: Arbiter (ARBT), total supply 1,000,000,000 ARBT with 18 decimals, minted once to the deployer. Application contract: ArbiterEscrow. Currency: ARBT is the app's working currency. ArbiterEscrow takes the ARBT address as its only constructor argument (constructorArgs ["$token"]), stores it immutable, exposes it as token(), and holds no ARBT at deploy; users get ARBT by swapping Sepolia ETH in the launch pool the factory seeds. Every payment in is approve + SafeERC20.safeTransferFrom (permit not required). ArbiterEscrow 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. No owner, admin, pause or upgrade path. Escrows in ARBT with a third-party arbiter, many escrows by id; states Funded, Delivered, Disputed, Closed. The buyer is whoever calls open and names the seller and the arbiter; the seller accepts those terms, arbiter included, by calling markDelivered, and a seller who does not accept them refunds. Delivery is agreed off-chain; the contract only records the seller's markDelivered. open(seller, arbiter, amount): buyer, seller and arbiter non-zero and pairwise distinct; amount > 0 ARBT is pulled; state Funded; records openedAt; ids from 1. markDelivered(id): seller only, Funded -> Delivered, records deliveredAt. release(id): buyer only, Funded or Delivered -> Closed, the full amount credited to the seller. refund(id): seller only, Funded or Delivered -> Closed, the full amount credited to the buyer. cancel(id): buyer only, Funded and block.timestamp >= openedAt + 14 days -> Closed, the full amount credited to the buyer, so a seller who never engages cannot lock the buyer's ARBT. dispute(id): buyer or seller, Delivered only -> Disputed, records disputedAt. resolve(id, buyerBps): arbiter only, Disputed, buyerBps 0 to 10,000 -> Closed: fee = amount x 100 / 10,000 (floor) credited to the arbiter; rest = amount - fee; the buyer is credited rest x buyerBps / 10,000 (floor) and the seller the remainder, so the three always sum to amount. claimAfterDelivery(id): seller only, Delivered and block.timestamp >= deliveredAt + 30 days -> Closed, the full amount credited to the seller. timeout(id): anyone, Disputed and block.timestamp >= disputedAt + 60 days -> Closed, amount split 50/50 with no fee and the odd unit to the buyer (an absent arbiter cannot lock funds). Any other call, role or state reverts. Races are first-transaction-wins and the README documents them: markDelivered against cancel at day 14, and dispute against claimAfterDelivery after day 30. withdraw() pays the caller's credited ARBT. Views: escrow(id), escrowCount(), withdrawable(address), token(). Events: Opened (buyer, seller and arbiter indexed), Delivered, Released, Refunded, Cancelled, Disputed, Resolved, Claimed, TimedOut, Withdrawn. Tests (Foundry) must cover: every transition allowed and denied by role and state, the 14-, 30- and 60-day boundaries at their exact second, fuzzed resolve splits summing exactly to amount, and the invariant that ARBT held equals the amounts of escrows not yet Closed + withdrawable balances. The independent adversarial review must attack: role confusion between the three parties, a buyer naming an arbiter it controls, the cancel/markDelivered and dispute/claim races, rounding in resolve and timeout, settling one escrow twice, and ARBT left in a state with no exit. Deploy through the project factory, then publish a one-page website to open an escrow (approve ARBT), see the connected wallet's escrows as buyer, seller or arbiter, take the actions its role allows in each escrow's state, and withdraw. The page reads the ARBT address from ArbiterEscrow.token(), shows the connected wallet's ARBT balance, allowance and withdrawable balance, has an Approve step before every paying action and a Withdraw button, and says that ARBT 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-arbiter-escrow.

Build ARBT and ArbiterEscrow (ARBT escrows with a buyer-named arbiter, 1% arbiter fee, a 14-day cancel and 30/60-day timeouts, constructorArgs ["$token"]) with Foundry tests and an independent adversarial review, deploy them through the project factory, then build the website against the live deployment.

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