Make source and website changes only. Do not create, change, or deploy contracts.

Fix Squeekchain data integration:

• Inspect the live responses and current official schemas for /v1/status and /v1/events?category=protocol&limit=100.
• The supplied /v1/status response is valid schemaVersion 1 data. An online, fresh hardware reading with coreStatus IDLE and rpmMilli 0 is a valid stopped-wheel reading.
• Find exactly why the event feed fails the current schemaVersion 3 validator. Compare the real response with current official docs; do not guess or remove validation.
• Validate and display wheel status independently from settlement events. An event-feed error must not hide valid wheel status.
• If settlements cannot be verified, pause only settlement-based unlocks and explain the feed error. Resume from saved watermarks without skipped or duplicate unlocks.
• Keep the 120-second freshness rule, practice mode, existing saves, progress and watermarks. Never show stale readings as live or fixtures as real.
• Fix the displayed “Confirmed round 1300”: show the current validated round from the live API (219 in the supplied response); label any retained local historical value as local/last seen.
• Keep the current local progress and scoring system. Do not claim wallet-linked scores or a shared leaderboard.

Update the existing site and repository. Verify with the real public API that a fresh IDLE/0-RPM reading displays correctly, valid status remains visible when events are unavailable or unsupported, stale readings pause live play, practice still works, and old local round data is not shown as current. Report the actual event schema and cause, changes, build result, and any remaining limitation. Do not claim verification without evidence.