Approved workflow

Release Taskboard (ERC-20 symbol TASK) on Sepolia as an evm_project: the fixed-supply launch token plus one application contract. Token: Taskboard (TASK), total supply 1,000,000,000 TASK with 18 decimals, minted once to the deployer. Application contract: SwarmJobBoard. Currency: rewards are Sepolia test ETH; TASK is only the launch token. A Sepolia test toy: it is not a hiring or payment service, a reward carries no off-chain obligation, and the README and the page say so. SwarmJobBoard has no constructor arguments (constructorArgs []) and no owner, admin, fee or upgrade path; plain ETH sent to it reverts. Payouts are credited and paid by withdraw() (pull, checks-effects-interactions, nonReentrant). post(specHash, deadline) payable: reward = msg.value >= 0.0001 ETH, deadline between block.timestamp + 1 hour and + 30 days. Phases: commit while block.timestamp < deadline; reveal in [deadline, deadline + 1 day); poster decision in [deadline + 1 day, deadline + 7 days), after every reveal is in. commit(taskId, c): one per address, not the poster, no cap on submissions (nothing ever loops over them, so spam cannot lock workers out), with c = keccak256(abi.encode(resultHash, salt, msg.sender, taskId)), so copying another worker's commitment is useless. resultHash is the hash of work the worker shares off-chain; the contract never sees the work itself. reveal(taskId, resultHash, salt) checks it and increments the task's revealedCount. The poster settles the task once, inside the decision window: accept(taskId, worker) for a worker who revealed credits the whole reward to that worker, or rejectAll(taskId) refunds the reward to the poster (work is judged off-chain, so junk submissions never force a payout). cancel(taskId): poster only, before any commit; refunds the reward. finalize(taskId): anyone, at or after deadline + 7 days if the poster did neither: with revealedCount > 0 it fixes share = reward / revealedCount and credits the remainder wei to the poster, and each revealed worker then calls claimSplit(taskId) once to credit its share; with no revealed workers the reward is refunded to the poster. Every task therefore ends in exactly one of accepted, rejected, cancelled or finalized, and finalize is always reachable. The README says the poster is trusted to judge fairly (rejectAll is always open to them), and that the split only applies when the poster does not decide and can be diluted by sybil submitters. Views: task(id), taskCount(), submission(taskId, worker), revealedCount(taskId), withdrawable(address). Events: Posted, Committed, Revealed(taskId, worker, resultHash), Accepted, Rejected, Cancelled, Finalized(taskId, share, revealedCount), SplitClaimed, Withdrawn. Tests (Foundry) must cover: each phase boundary (commit at the deadline reverts, reveal at deadline + 1 day reverts, accept before deadline + 1 day reverts), a wrong salt or copied commitment failing to reveal, accept, rejectAll and finalize excluding each other, accept or rejectAll after the decision window refused, claimSplit twice or by a non-revealer refused, remainder wei, cancel after a commit refused, and, fuzzing with warped time, the invariant that the contract's ETH >= open rewards + unclaimed split shares + withdrawable balances. The independent adversarial review must attack: paying a reward twice (accept, rejectAll and finalize in any order, or claimSplit replay), stealing a result by copying a commitment, a poster accepting an unrevealed worker, split rounding, and reentrancy on withdraw. Deploy through the project factory, then publish a one-page website to post a task, commit and reveal a result hash, accept or reject all, finalize, claim a split share and withdraw; revealed workers are listed from Revealed events. The page generates the salt with crypto.getRandomValues, keeps it in localStorage and shows it for backup. 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-swarm-job-board.

Build TASK and SwarmJobBoard (SwarmJobBoard has no constructor arguments, holds ETH rewards and uses commit-reveal submissions) 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. Salt stays in localStorage with a visible backup; show the withdrawable balance and a Withdraw button.