Approved workflow

Committed as f243798 on main. The working tree is clean and the staged tree contains zero gitlink (submodule) entries.

What was delivered

• src/LaunchToken.sol: Noughts (NGHT), an OpenZeppelin ERC-20 with no constructor arguments, 18 decimals, and exactly 10^27 minor units minted to the deployer. No mint, owner, pause, fee or upgrade surface.
• src/TicTacToeWager.sol: the single application contract. It takes the NGHT address as its only constructor argument, holds no ETH and no tokens at deploy, packs the board into two bits per cell in one word, and pays out only through a nonReentrant withdraw(). It has no owner or admin path.
• docs/abi/LaunchToken.json and docs/abi/TicTacToeWager.json: ABI exports.
• README.md: rules, deployment parameters for the manifest assignment (constructorArgs ["$token"], no $owner), timeout semantics, assumptions, and operational responsibilities.
• script/Deploy.s.sol: a local helper with no environment reads, covered by its own test. The production path is the factory.
• lib/: forge-std 1.11.0 and OpenZeppelin 5.4.0 vendored as plain files with git metadata stripped.

Verification results

The suite covers every win line for both players, a draw, a win on the ninth cell, out-of-turn and stranger moves, occupied and out-of-range cells, self-join, cancel after join, the timeout boundary at exactly one hour and one second before it, wrong-party timeout claims, win-then-timeout double-pay, moves after the end, and a hostile-token reentrancy on withdraw. A handler-driven invariant confirms NGHT held equals open stakes plus twice the active stakes plus all credits.

One design decision to flag for review

The move clock is a claimable right, not an automatic end. A late player may still move while the game is active if the opponent has not yet claimed, and the first transaction mined decides. This is documented in the README with the mempool race it implies, and the website should show the timer so players see it coming.

What remains for other assignments

The manifest assignment writes launch.json naming LaunchToken and TicTacToeWager with ["$token"]. The independent review, factory deployment and website follow this stage.

Created launch.json for Noughts (NGHT) and TicTacToeWager(["$token"]).

• Supplied schema, refinements and constructor ABI checks passed.
• forge build succeeded with existing warnings.
• forge test: 63 passed, 0 failed.
• Only launch.json changed outside permitted scratch artifacts.

Wrote one low-severity finding to .imd-findings.json: a direct token.transfer(wager, 1) breaks the asserted balance equality, but the invariant handler cannot generate this input. Other players’ payouts remain unaffected.

For approved players X/O calling open(1e18) then join(id):

• Packed-bit win forgery: X:3 → O:4 → X:5 → O:0 remains active without winner credit. Independent checks matched all 19,683 boards for both players.
• Unauthorized/early timeout: O’s claim at deadline−1 reverts; X’s and a stranger’s claims at the deadline revert. O’s claim exactly at the deadline succeeds.
• Double payout: X:0 → O:3 → X:1 → O:4 → X:2, followed by either player claiming timeout two hours later, reverts with GameNotActive. Credit is issued once.
• Withdrawal reentrancy: attacker opens, cancels, and withdraws; a hostile-token callback reenters withdraw(). The guard rejects it, pays once, and preserves another player’s credit.

Timeouts remain claim-based: an overdue move mined before the timeout claim resets the clock.

launch.json correctly supplies ["$token"] to constructor(address token_). LaunchToken has no constructor arguments. Neither constructor grants privileged roles, and both exported ABIs match compilation.

Only the findings report was created.

The frontend is built, validated and committed as 56eb7c4 on top of the pinned source commit. The working tree is clean and the submission bundle is about 2.1 MiB, well inside the 8 MiB limit.

What was delivered

• web/: Vite + React + TypeScript source, package.json, package-lock.json, tests and the manifest tooling. Nothing under node_modules or generated public/ files is tracked.
• dist/: the static export with a relative base, plus dist/imd-deployment.json and dist/abi/*.json. The manifest copies launch id, chain, source commit, attestation hash, the two contracts with their attested ABI hashes, the untouched network block, and SHA-256 hashes for all 7 other exported files.
• docs/validation.md, docs/validation/e2e-report.json and 16 screenshots, plus docs/DESIGN.md and web/README.md.

How the page works

The app fetches imd-deployment.json at runtime, verifies each ABI's canonical keccak against the attested hash, and refuses to run on a mismatch. Addresses, chain id, public RPCs, explorer and Uniswap v4 addresses all come from that file. The page shows NGHT balance, allowance to the game and withdrawable credit, requires an explicit exact-stake approval before open and join, renders the board with turn and move clock, offers cancel, timeout claim and withdraw, and quotes the pool rate through the vetted quoter. There is no in-page swap, following the approved workflow. A wallet on another chain gets one "Switch to Sepolia" control, with wallet_addEthereumChain offered after a 4902 failure.

Validation results

The Better Interface review found and fixed three product issues: a stale approve button that stayed enabled, a board-cell border below 3:1 component contrast, and short addresses breaking mid-token at 320px.

Two things to know

• DESIGN.md is at docs/DESIGN.md, not the repository root, because the root was outside the allowed write paths. The reason is recorded in the validation file.
• Not exercised: a real wallet extension, any broadcast Sepolia transaction, screen readers, forced-colors mode and native zoom. These are listed as limitations in docs/validation.md.