I found 5 problems in Blocklight. One is high: the README sends readers to validation evidence that isn't in the repository. The game itself works: the tests pass and a full win, loss and replay plays cleanly at 390 wide in Chromium. WebKit would not launch on this machine, so Safari behaviour is unchecked. The findings are in .imd-findings.json, and no tracked file was changed.

Area	Count
Brief requirements (24)	16 met · 1 missing · 0 faked · 4 after review · 3 partly met
Broken features	3: board ignores taps before Play puzzle, a double tap costs a hint, the result dialog shows an out-of-date status line
Game on the first screen at 390	Yes. Headline, Play puzzle at y=328 and the board at y=476–802, all within 844
taste@1 checks passed	16/16
Copy findings	2 (the out-of-date "Round started" line, three extra slogans)
Share card	Present (title, description, og:title, og:image, favicon)

Requirements

Brief says	Status	What shows it
"production site through IMD IPFS hosting"	after review; export is ready	dist/ uses relative paths (base: './')
README "setup/build/test commands"	met	README.md:13–33
"architecture"	met	README table at about line 64
"exact API-to-game mapping"	met	README field table; src/data/rpc.ts
"scoring/seed formulas"	met	README formulas and sample values
"known limits"	met	README "Known limits"
"two-minute reviewer walkthrough"	met	Its winning move list really scores 1,000 at par 10
Tests: solvability, repeat samples, epoch/reset/stale, archive reproducibility	met	tests/*.test.ts; I ran them: 39/39 passed
"Run the production build and tests"	met	The dist/ build and tests are committed; tests re-run here
Browser check on desktop and mobile	partly met	It works in Chromium at 390. The recorded results are in missing files (finding 1)
Keyboard and touch flows	partly met	Tiles ignore taps until Play puzzle (finding 4)
A complete win/loss/restart	met	Win at 1,000 points; loss after 18 presses of A1; Play again works
"idle live input"	met in the code	Tests cover stale feeds; the live API was not reachable from here
"unavailable API"	met	With the API blocked, the page reads "Ethereum API unavailable" and offers Retry API
"honest demo labels"	met	"Demo · offline practice"; demos carry no fake block data
"overlay"	met, taken to mean the in-page dialogs	The brief's meaning is unclear (it starts mid-sentence)
"PNG export"	met	Download blocklight-demo-1-won.png
"record actual results and any unavailable checks in README"	partly met	A summary paragraph only; its sources are missing (finding 1)
Fix critical gameplay/usability errors	after review (this report)	Findings 2–4
Return job URL, live site URL, public source/commit	after review ×3	README says these come from IMD after publishing
"validation evidence"	missing	artifacts/ does not exist (finding 1)
No TODOs, no fake data shown as live	met	Live, Demo and Archive labels are kept apart

The idea: Blocklight is a 5×5 Lights Out game seeded from an Ethereum block, built around one image: a dark board of lime lights. It has no extra effects (no gradient, glow or badges).

Findings

1. High – fidelity: README.md:31, 170, 188 and 194 link to five artifacts/ files, none of which exist. These are the validation results, browser results, export checks, size limits and the design-guidance license notice. Commit the files, or put the results table into the README itself.
2. Medium – bug: after a win or loss, the result dialog still says "Round started. Turn every light off." (src/App.tsx:196). It should be cleared when the round ends.
3. Medium – bug: once a round starts, the big lime button in the same spot becomes "Show a hint −100 pts". At 390, tapping that spot twice dropped the score from 100

I fixed all five review findings, rebuilt dist/, and re-ran the full check suite. All executed checks passed; WebKit could not run. Nothing is committed: changes are left in the working tree for the network to bundle, as in the previous round.

The README evidence links (high): the accepted tree had no artifacts/ directory, so every evidence and license link in the README was broken. The README no longer points there:

• Evidence in the README: the Validation section now has a table of commands and results, a table of the 8 browser test groups, and a list of the checks that did not run. It also has a short design-review table with file:line fixes.
• License notice: now committed at LICENSES/Design-guidance-LICENSE.txt.
• Size budget: moved to scripts/path-budget.json, which scripts/check-export.mjs now reads.
• Script output: the validation scripts write their reports to test/scratch/validation/, which is not committed.

The four advisory findings (all real, all fixed):

• Stale line in the win/loss dialog: "Round started…" no longer appears there (src/App.tsx:64).
• Hint button: it's now the bordered secondary style instead of the lime primary style, and keeps the "−100 pts" label (src/App.tsx:145). I chose this over the borderless style the reviewer suggested because a full-width borderless button reads as plain text.
• Board before Play puzzle: tapping a tile now starts the round and counts as move 1 (src/components/Board.tsx:11, src/App.tsx:90). Tiles are disabled only after a win or loss.
• Extra slogans: I removed the header and footer lines and their CSS, and the help dialog is now titled "How to play".

Check results (2026-11-03, after the last source change):

Check	Result
Typecheck and production build	Passed
Unit tests	39/39 passed
Export integrity	Passed: 9 runtime files, relative asset URLs, 691,795 of 8,388,608 bytes
npm audit	0 vulnerabilities
Browser tests (Chromium)	8/8 groups passed
Design probe at 320/390/1440	16/16 checks passed

• Browser tests: they now also check that a tile tap starts the round, that no stale line shows in either dialog, and that the hint button isn't lime. A separate run of the reviewer's exact steps on demo 1 at 390 wide matched.
• Live API check: a real Ethereum block was received. On this machine the request went through the contributor's RPC; the shipped site only calls PublicNode.
• First screen at 390 wide: I looked at the screenshot. The product, Play puzzle and the top of the board are all visible.

Not checked: WebKit wouldn't launch because system libraries are missing and I can't install them here, so Safari behaviour is unverified in this round. A physical phone, a screen reader and browser zoom were also not tested. All of this is stated in the README.

Not filled in: the job URL, live site URL, public source link and commit only exist once the network publishes, so I left them blank rather than inventing them.

My answers to each finding are in .imd-responses.json; all five are marked fixed.

Area	Previous review	This review
Requirements	1 missing reported; full totals unavailable	26 assessed: 22 met, 0 missing, 0 faked, 4 after review
Broken features	3	0 reproduced
First screen at 390	Not supplied	Product and action visible
taste@1	Not supplied	16/16 passed
Copy findings	1	0
Share card	Not supplied	Present; 1200×630 PNG

All five previous findings are fixed. No new reproducible defects were found. .imd-findings.json contains {"findings":[]}. Application files are unchanged.

Brief requirement	Status	Evidence
“production site through IMD IPFS hosting”	After review	Publication belongs to IMD; README:228
“README with setup/build/test commands”	Met	README:7–57; commands executed
“architecture and exact API-to-game mapping”	Met	README:69–113; engine and RPC adapter
“scoring/seed formulas”	Met	README:115–144; golden-vector tests
“known limits”	Met	README:214–222
“two-minute reviewer walkthrough”	Met	README:161–167; reproduced
“meaningful deterministic engine/adapter tests for solvability”	Met	tests/engine.test.ts; independent solver comparisons
“repeat samples”	Met	Engine and adapter tests
“epoch/reset/stale behavior”	Met	tests/adapter.test.ts; browser virtual-clock checks
“archive reproducibility”	Met	tests/archive.test.ts; browser JSON/link replay
“Run the production build and tests”	Met	Build, typecheck and 39/39 tests passed
“Browser-check desktop and mobile”	Met	Chromium at 1440 and 390; responsive checks at five widths
“keyboard/touch flows”	Met	Arrow/Space/Enter navigation, focus trapping and touch passed
“a complete win/loss/restart”	Met	Demo 1: 10-move win, 18-move loss, restored starting board
“idle live input”	Met	New/repeated headers preserve the board; stale input disables loading
“unavailable API”	Met	Controlled 503, retry and continued demo play passed
“honest demo labels”	Met	“Demo · offline practice”; archive explicitly unverified
“overlay and PNG export”	Met	Dialog interaction and downloaded 1200×1000 PNG verified
“record actual results and any unavailable checks in README”	Met	Inline command/browser tables and explicit limitations
“Independently review…fix critical gameplay/usability errors”	Met	All five prior findings independently settled
“Return job URL”	After review	Not supplied; IMD publication output
“live site URL”	After review	Not supplied; IMD publication output
“public source/commit”	After review	Not supplied; IMD publication output
“validation evidence”	Met	README tables and fresh evidence linked below
“Prefer a complete reliable core game”	Met	Complete playable board, replay and recovery flows
“All required functionality…no TODOs, fabricated passing test results, or fake data presented as live”	Met in exercised scope	Core checks passed; direct PublicNode response observed; limitations disclosed

Blocklight is an Ethereum-seeded Lights Out game carried by one visual idea: lime lights against a dark green board.

The original reproductions now show:

• README evidence: no remaining artifacts/ references; all local documentation links resolve. License and budget files exist.
• Stale result notice: at 390, both the documented win sequence and 18 A1 presses produce result dialogs without “Round started.”
• Hint styling: the control uses button-outline, retains “−100 pts,” and no longer uses the primary style.
• First tile press: A1 is enabled before starting. Tapping changes moves 0 → 1 and board 29810256 → 29810291.
• Extra slogans: the three reported lines are removed; the help heading is “How to play.”

Fresh validation pass