Updated source, static export and documentation. Wheel play now works independently of settlement errors. Current rounds use validated status—237 observed—with saved history labelled local. Saves, practice, scoring and watermarks are preserved.

The live feed returns schema 4 and omits identities; the official schema still specifies 3. Only settlement unlocks remain paused.

Build, typecheck, 42 tests and 14 DOM checks passed, including real-API IDLE/0 play. Browser and taste checks could not run; rendered mobile behavior remains unverified.

Not delivered: artifacts/api-research.json, artifacts/api-research.md, artifacts/api/events-request.json, artifacts/api/events-schema-request.json, artifacts/api/events-schema.json, artifacts/api/events.json, artifacts/api/status-request.json, artifacts/api/status-schema-request.json and 12 more. Under artifacts/, only this step's named outputs leave the machine.

Area	Result
Requirements	19 met; 0 missing; 0 faked
Broken features	1 medium display bug
First screen at 390	Product and action visible
taste@1	16/16 passed
Copy findings	0
Share card	Present; 5/5 metadata checks

Recorded in .imd-findings.json.

Medium — bug: idle readings always display “0 RPM”. At src/App.tsx:564, the start panel hardcodes zero. At 390×844, a valid IDLE/rpmMilli: 77005 response displays 0 RPM there and 77.005 RPM in “Behind the wheel.” Display the validated RPM value while retaining zero additional power for IDLE. The JSON contains the exact reproduction and source snippet.

The requested fresh IDLE/0 case passed. The observed public status used schema 1 and round 238. Events returned schema 4, catalog public-activity-v4, and settlement event version 2. The official schemas still describe envelope version 3 and require identities; the live response instead supplies deployment and capabilities. Retaining validation and pausing settlement unlocks is appropriate.

The production rebuild matched the delivered HTML, JavaScript and CSS. Typecheck, 42 tests, 14 DOM checks and 13 Chromium checks passed. Real, unmodified API bodies also passed a six-turn Chromium game through a request relay. Direct browser API networking and WebKit remain unverified.

Requirement coverage:

Explicit requirement	Status and evidence
Continue existing Burrow Power	Met — retained App.tsx, game.ts and habitat
Source/site changes only; no contracts	Met — source implementation and README
Inspect both live endpoints and official schemas	Met — independently fetched; comparison confirmed
Accept fresh hardware IDLE/0	Met — real API and rendered game
Identify exact event-validator failure; retain validation	Met — api.ts:191, README
Validate/display status independently; feed errors must not hide it	Met — pending, unsupported and HTTP-500 checks
Pause only settlement unlocks and explain errors	Met — .settlement-note, .source-error
Resume saved watermarks without skipped/duplicate unlocks	Met — two-page recovery, retry and reload checks
Keep 120-second freshness	Met — assertFresh and action guards
Keep practice mode	Met — completed Chromium campaigns
Preserve saves, progress and watermarks	Met — storage and recovery checks
Never present stale data or fixtures as real	Met — stale/simulated rejection; practice labels
Display current validated round, including supplied 219	Met — regression fixture 219; observed API 238
Label retained historical rounds local/last seen	Met — saved 1300 explicitly labelled
Keep local scoring/progress	Met — game.ts:510, separate profiles
No wallet-linked scores/shared leaderboard claims	Met — footer and help disclosures
Update existing site and repository	Met — integrated source and README
Verify requested live, failure, stale, practice and history states	Met — public API, DOM and Chromium evidence above
Report schema, cause, changes, build and limitations honestly	Met — README and this review

The visual idea is a hamster survival game carried by a glowing underground habitat.