Built Squeek Maze Sprint with live data, touch controls, offline fallback, local bests, and result sharing.

Passed: 19 unit tests, 11 Chromium tests, build/typecheck, and all 16 design checks. Bundle: 1.04 MiB. Validation and limitations.

GitHub publication, IPFS pinning, and ENS assignment remain pending external publication.

Not delivered: artifacts/browser-check.json, artifacts/design-probe.json, artifacts/export-check.json, artifacts/licenses/design-guidance.txt, artifacts/live-api-check.json, artifacts/publication.json, artifacts/screenshots/desktop-ready.png, artifacts/screenshots/mobile-playing.png and 6 more. Under artifacts/, only this step's named outputs leave the machine.

Area	Count / result
Requirements	40: 34 met, 2 missing, 0 faked, 3 after review, 1 needs requester
Broken features	1
First screen at 390px	Game and Start visible
taste@1	16/16 passed
Copy	1 low finding
Share card	Working 1200×630 PNG

Saved two verified findings in [.imd-findings.json][findings]. Application files are unchanged.

• High — bug: landscape layout separates the maze from touch controls. At 844×390, the 560px board extends below the viewport and the direction pad starts at y839.5. At 852×393, the board shrinks to 149px and the pad disappears. Fit the existing game controls and board to landscape height.
• Low — bug: singular result counts use plural nouns. A one-pickup run displays and shares “1 Squeeks.” Use singular labels consistently in the result overlay, copied text, and PNG.

All 19 unit tests passed. Chromium and WebKit walkthroughs covered movement, pause, changing wheel state, signal loss, completion, local scores, sharing, and PNG download. Accessibility scans found no violations in the ready screen or either modal.

Explicit requirement	Status	Evidence
“real playable game rather than a read-only dashboard”	Met	[Game engine][game] and browser walkthrough
Deterministic maze and collectibles from the current round at run start	Met	[API seed][api], [generator][maze]
“latest available Squeek block hash”	Needs requester	API exposes settlement hashes; implementation discloses a round-boundary settlement anchor instead
Players in the same round receive the same board	Met	[Round anchor][api], deterministic tests
Control a hamster with keyboard	Met	[Keyboard handlers][app]
Touch controls	Met	[Direction pad and gestures][app]
Collect Squeeks	Met	[Collection and scoring][game]
Avoid moving hazards	Met	[Hazard patrols][game], browser walkthrough
Finish a 60-second run with a score	Met	[Timer and completion][game]
Read official round, height, hash and wheel data	Met	[Three official API endpoints][api]
Running grants a small movement bonus	Met	[10% movement bonus][game]
Resting slows moving hazards	Met	[35% longer hazard steps][game]
Avoid encouraging or influencing the animal	Met	Read-only requests and [welfare copy][app]
Refresh live state during play	Met	[Polling][app]
Show observation timestamp	Met	[Signal strip and provenance][app]
Link to the official source	Met	[Official-source links][app]
Labelled offline fallback only when API unavailable	Met	[Fallback handling][api], failure walkthrough
Never present simulated data as live	Met	[Hardware provenance checks][api] and demo labels
Local best scores by round using localStorage	Met	[Score storage][storage]
Shareable result card	Met	[PNG generation][share], downloaded in both browsers
Concise rules modal	Met	[Rules dialog][app]
Source and data provenance	Met	[Source dialog][app], verified source ZIP
Responsive mobile and desktop controls	Missing	Landscape failure in finding 1
Accessible contrast	Met	taste@1 contrast and accessibility scans
Reduced-motion support	Met	[Motion rules][styles]; WebKit measured 0s transitions
Dark arcade panel, charcoal, yellow, cyan and pixel display typography	Met	[Style tokens][styles], screenshots
Restrained motion	Met	[Limited transitions][styles]
Dominant full-viewport board	Missing	Landscape failure in finding 1
Avoid purple gradients, decorative cards, oversized marketing copy and clutter	Met	[Rendered interface][app], taste@1
No token, payments, custody, gambling, fabricated rewards, admin or marketing landing page	Met	[Application][app] and read-only integration
Game itself is the first screen	Met	390×844 browser checks
Complete source published to public GitHub	After review	[Publication handoff][

I reproduced both findings and fixed them. Typecheck is clean, 20/20 unit tests and 12/12 Chromium tests pass, the design probe passes 16/16, and the export check passes (714 KB, well under 8 MiB). Answers to both findings are in .imd-responses.json.

Landscape phone layout (high): fixed. On the old export I got the reviewer's exact numbers. At 844×390 the board ran from y202 to y762 and the direction pad was at y840–932, both well below a 390px-tall screen. At 852×393 the board shrank to 149×149 and the pad was hidden.

I added two layout rules in src/styles.css:

• Short landscape screens (sideways phones, and touch tablets in landscape up to 896px tall) now get their own game view:
  • The score and timer sit left of the board.
  • The board's size comes from the screen height.
  • The live signal, speed-bonus text and direction pad sit on the right.
  • The information sidebar is hidden, as it already is on portrait phones.
• Touch screens 848px wide or more keep the direction pad under the board instead of hiding it.

Measured on the rebuilt export:

Screen	Board	Start button bottom	Direction pad
844×390	y54–372, 318px	251	y280–372
852×393	321px	253	y283–375
667×375	253px	238	y230–322
1024×768 touch	610px	397	y572–664

932×430 and a 1440×900 touchscreen also fit. A new browser test checks six landscape and touch sizes: the board, Start and all four arrows must be on screen, and an arrow tap must move the hamster during a run. Mouse-only desktops keep the old layout.

"1 Squeeks" / "1 bumps" (low): fixed. The result screen, the copied share text, the saved PNG card and the screen-reader status now say "1 Squeek" and "1 bump". A new unit test (tests/share.test.ts) covers this, and the 60-second browser test checks the result screen.

Other changes:

• Build script: npm run build crashed on a missing artifacts/ folder. scripts/source-archive.mjs now skips folders that don't exist.
• Flaky test: the 60-second-run test also failed on the untouched code. It skipped the clock ahead before the round data loaded, which tripped the app's 6-second timeout and dropped into demo mode. It now waits for the run to start.
• Docs: DESIGN.md has the two new layout rules. The README has the new test counts and no longer links to artifacts/publication.json, which never existed. artifacts/validation.md records this revision's measurements and results.

Not checked:

• WebKit wouldn't start on this machine (missing system libraries), so Safari's engine wasn't tested this round.
• Touch was simulated in Playwright; no real phones were used.
• On a 320×568 portrait phone the direction pad still sits below the fold. That layout wasn't part of the findings, so I left it alone.

Nothing is committed; the changes are in the working tree.

Not delivered: artifacts/validation.md. Under artifacts/, only this step's named outputs leave the machine.

Area	Previous review	This review
Requirements	Full counts not supplied	38: 34 met, 0 missing, 0 faked, 3 after review, 1 needs requester
Broken features	2	0 reproduced
Product and action on first screen at 390px	Yes	Yes
taste@1	Passed; total not supplied	16/16 passed
Copy findings	1	0
Share card	Present; singular-count defect	PNG and Open Graph present; defect fixed

Both previous findings are settled:

• bug: landscape sizing — fixed. At 844×390, the maze measures 318×318 at y=54–372; the direction pad ends at y=372. At 852×393, the maze measures 321×321 and both end at y=375. Start and all four directions fit, and touch movement works. Seven viewport sizes passed with both official fixtures and forced API failure. See [styles.css][css].
• bug: singular result counts — fixed. The original one-pickup, 60-second reproduction produces “1 Squeek · 0 bumps” in the result and clipboard, and “1 Squeek / 0 bumps” in the downloaded 1200×630 PNG. The one-bump formatter test also passes. See [share.ts][share].

All 20 unit tests passed. Chromium verification completed; WebKit could not launch because required system libraries were unavailable. No source files changed. [.imd-findings.json][findings] contains {"findings":[]}.

Explicit requirement	Status and evidence
“polished browser game” / “real playable game”	Met — playable maze, movement, scoring and results in [App.tsx][app] and [game.ts][game].
“powered by live Squeekchain data”	Met — current official responses loaded successfully through [api.ts][api].
“At the start of a run” derive deterministic maze and collectibles from the current round	Met — fresh snapshot in startRun; seeded generation in [maze.ts][maze].
“latest available Squeek block hash”	Needs the requester: exact per-Squeek-block hash data. The existing implementation transparently substitutes a round-boundary Ethereum settlement hash; it separately shows the latest settlement hash. See [README][readme], provenance dialog and official API documentation.
“players in the same round receive the same board”	Met — fixed round anchor; same-round settlement test in [api.test.ts][apitest].
“controls a hamster with keyboard and touch controls”	Met — keyboard movement and direction-pad taps verified; [App.tsx][app].
“collects Squeeks”	Met — reproduced pickup adds 10 points; [game.ts][game].
“avoids moving hazards”	Met — moving patrols, collisions and penalties; [game.ts][game].
“finishes a 60-second run with a score”	Met — original reproduction reaches the result at 60 seconds.
Read official API for “current round, chain height, block hash and live hamster wheel state”	Met, with hash qualification above — three official endpoints in [api.ts][api].
State “must visibly affect gameplay”	Met — modifier labels and actual timing changes; [App.tsx][app], [game.ts][game].
“without encouraging or attempting to influence the animal”	Met — read-only requests and welfare wording in rules/footer.
Running grants “a small movement bonus”	Met — 10% movement bonus; speedsFor.
Resting “slow[s] moving hazards”	Met — hazard steps take 35% longer; speedsFor.
“Refresh live state during play”	Met — five-second polling in [App.tsx][app].
“show the observation timestamp”	Met — original observation time appears in the signal strip.
“link to the official source”	Met — official endpoint links in the panel and provenance dialog.
Labelled fallback “only when … unavailable”; never simulated data as live	Met — forced failures show “Offline demo”; simulated observations grant no live bonus; [api.test.ts][apitest].
“local best scores by round using localStorage”	Met — complet