I've built Squeek Burrow Rescue and committed it (0128881) with the source, lockfile and the static export in dist/. The commit is about 0.7 MB, well under the 8 MiB limit. The game opens straight into Level 1.

Checks, all on the final build:

• Tests: npm test passed 61 of 61. They show that:
  • each of the 12 levels can be won on both the wheel route and the nap route, at the stored par and within the move budget;
  • no level can be won with both the bridges and the sleeping gates shut, so the live hamster state always matters;
  • all 8 rotations and mirrors used by the daily challenge keep every level winnable at the same par;
  • movement, crates, plates, gates, beetles, winning, undo, stars, API parsing, timeouts and errors, and replay checking all work.
• Typecheck and build: tsc --noEmit and the production build both succeed.
• Browser checks: I ran 34 scripted checks in headless Chromium at 320, 390 and 1440 wide; 33 passed. The one flagged check was the request for the small tab icon (favicon.svg), which was cut off while the script reloaded the page. The file is in dist/ and the design review found no missing files.
  • Touch buttons, keyboard play, undo, and stars that survive a reload all work.
  • When the API is blocked or stale, the game switches to labelled practice mode and shows no live values.
  • Share links replay correctly, and tampered ones are rejected.
  • The Chinese toggle, the How to play dialog, the skip link and reduced motion all work.
  • At 390 wide, the whole board and the arrow buttons fit on the first screen.
• Design review: the provided design check passed 16 of 16. I checked the Better Interface guide's six areas and fixed what it turned up: the "live data unavailable" message appeared twice, and the uncollected-pup icons were too faint.

How the live data is used: the game asks https://api.squeekchain.com/v1/status every 15 seconds. A request times out after 8 seconds, and after a failure it waits longer each time, up to 2 minutes.

• A SPINNING hamster gives the wheel route with 2 extra moves. IDLE gives the nap route, where the sleeping gates are open.
• These rules are fixed when a level starts. One exception: if Level 1 loaded before the first answer arrived and you haven't moved yet, it switches to the live rules.
• The daily challenge is seeded from the UTC date plus the latest Squeekchain settlement transaction hash. That hash is saved the first time you open the daily challenge each day and is shown on screen.

Limitations:

• The hamster was IDLE the whole time I tested, so the SPINNING path was only checked with a faked API response.
• There was no screen-reader or real-phone testing; mobile was emulated in the browser.
• Two people opening the daily challenge at different times on the same day can get different seeds. The share link carries the seed, so a shared challenge can always be replayed.
• Scores stay in the player's browser and are checked by replaying the moves; there is no global leaderboard.

Git had no author set up on this machine, so I put your email on the commit for that one command and didn't change git's settings. The full validation record is in artifacts/validation.md. Because the platform keeps artifacts/ out of git, I committed a copy as docs/VALIDATION.md. Install, preview and rebuild steps are in README.md.

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

Saved four reproducible findings in .imd-findings.json:

• High — bug: Daily seed/source changes after API recovery.
• Medium — bug: Changing the result hash retains the previous board and verified verdict.
• Medium — bug: Reload restores the Wheel route selection but plays the nap board.
• Medium — bug: Undoing to zero lets API recovery change the attempt’s frozen route.

Validation: 61/61 tests passed in an isolated copy. Its clean build exactly matches committed dist/. Chromium and WebKit passed primary play flows; desktop gates, capture, budget failure, undo, API timeout/backoff, and reduced motion were checked. Application files remain unchanged.

“Missing” below includes requirements with reproducible failures in particular states.

Fixed all four findings and recorded them in .imd-responses.json.

Verified: 79 tests, build/typecheck, 26 Chromium/WebKit browser scenarios, and 16 design checks passed. Documentation and dist/ are updated; the export is ready for the assignment’s IPFS publisher.

I checked all four earlier findings in Chromium and WebKit at 390×844, and all four fixes hold. The new daily-disclosure code introduced one new bug (medium), which is the only finding in .imd-findings.json.

Earlier findings

• [high] Daily seed and source change after an outage: fixed. I played the daily during an outage and moved once. Storage then held sbr:daily:2026-10-30 = {"anchor":null,"block":null}. After the API came back with an anchor and I clicked "Check now", the card still showed seed cc4cbe1a, Level 11, and the board stayed at Moves 1/30. Reopening and reloading kept cc4cbe1a. The October 29 shared daily shows e9d64c93, Level 8 and the full hash.
• [medium] A new shared-result hash kept the old board: fixed. After location.hash = '#level?l=2&v=w&m=UUUU', the page shows Level 2, Wheel route, 0/32 moves, and "Replay did not verify".
• [medium] Practice reload played Nap while Wheel was selected: fixed. After reload during an outage, the Wheel radio is still checked and the HUD says Wheel route.
• [medium] Undo to the start let the recovering feed change the route: fixed. After a move, Undo, and a SPINNING response, the board stays on Nap route at 0/29.

New finding

bug: "Play daily challenge" restarts an older shared daily instead of today's (src/App.tsx:165, const date = daily.date;)

• What happens: the card now follows the active attempt (that was the fix), but the button reads its date from that same value. On /#daily?d=2026-10-29&a=0xcdcd…&v=n, with the system date 2026-10-30, clicking the button keeps the October 29 board (0/33 moves, e9d64c93) and saves sbr:daily:2026-10-29. The same thing happens after UTC midnight; the project's own rollover test shows it.
• Fix: startDaily should work out today's date, saved anchor and seed by itself, and leave the card's disclosure as it is.
• It is medium because there is a workaround: starting any numbered level first makes the button work again.

Requirements

• Game: met. The game is on a 6×6 board with 3 pups, a move budget, crates, plates, gates and beetles (src/game/engine.ts). There are at least 12 levels (src/game/levels.ts). Restart and undo work, as do arrows/WASD and the touch buttons. The tutorial, About and How to play panels are present.
• Settings and look: met. Sound toggle, local progress and stars, English/Chinese toggle, reduced motion and mobile layout all work. The game is the first screen, with the cream/brown/teal SVG art.
• Live status feed: met (src/game/live.ts). It polls every 15 seconds, with a timeout, backoff, a stale marker and a "Check now" button. It reads coreStatus and rpmMilli only when the response has them. The page shows the state, timestamp, source and the wheel companion.
• Live rules: met. SPINNING gives the wheel route and IDLE gives the nap route. The route is frozen for each attempt, and practice mode is clearly labelled with no made-up values.
• Daily challenge: met, apart from the new bug above. The seed comes from the UTC date plus the anchor transaction when the API gives one, and the source is shown.
• Sharing: met. Share URLs work, replays are checked in the browser, and the page says scores are local and not a global leaderboard.
• No money features and credits: met. There is no wallet, token or prize. The page credits @wobushibaolonga and links to the Genesis page and squeekchain.com.
• Tests and docs: present (tests/, docs/VALIDATION.md). This machine has no node_modules