Implemented Squeek Pulse with live metrics, real top-10 rankings, a responsive dark theme, and 20-second refresh. Complete export in dist/; source, lockfile, README, and DESIGN.md included.

Build, typecheck, 12 interaction groups, and all 16 design checks passed. Delivery is about 1 MiB. WebKit remains unverified because system libraries were unavailable.

Validation report

The Squeek Pulse build meets every requirement in the brief. Nothing is missing, faked or broken, and the dashboard is on the first screen at 390 wide. I recorded six findings, none of them high; they are in .imd-findings.json.

I couldn't run the probe or watch the page myself. Every Bash call failed with a sandbox error ("Failed to create bridge sockets"), the browser tool has no Chromium installed, and both feed URLs return 403 to my fetch tool. So I judged from the source, the builder's screenshots at 390 and 1440, and the builder's own artifacts/taste-checks.json and live-check.json. For the same reason I didn't check the main interaction in WebKit. I changed no files apart from the findings file.

Area	Count
Brief requirements	13 met · 0 missing · 0 faked · 1 after review (hosting)
Broken features	0
Product on the first screen at 390	yes (wheel status, RPM and block height above the fold)
taste@1 checks passed	probe did not run here; the builder's own run passed 16/16
Copy findings	3
Share card	present (title, favicon, og:title, og:image 1200×630, description)

Requirements

• "single-page website called Squeek Pulse": met. Header brand at src/main.ts:15 and <title> in index.html:17.
• "fetch data from https://api.squeekchain.com/v1/status": met. src/api.ts:2; the builder's live check recorded HTTP 200.
• "…and https://community.squeekchain.com/v1/community/stats": met. src/api.ts:3; HTTP 200.
• "hamster running status (SPINNING/IDLE with RPM)": met. #state-label and #rpm in main.ts:52-54.
• "block height with progress bar": met. #block-height and <progress id="block-progress"> in main.ts:67-70.
• "distance run": met. #distance in main.ts:77.
• "settled rounds": met. #rounds in main.ts:78.
• "community members count": met. #members in main.ts:79.
• "badges earned": met. #badges in main.ts:80.
• "top 10 leaderboard": met. #leaderboard-body is filled from the community leaderboard feed (api.ts:4, limit=10), with real entries in the builder's capture. That feed is a third URL the brief didn't name; it answered 200.
• "Dark theme": met. color-scheme: dark in styles.css:10.
• "responsive": met. There are breakpoints at 66, 53, 38 and 22rem, and the builder's probe found no horizontal scroll at 320, 390 or 1440.
• "auto-refresh every 20 seconds": met. REFRESH_MS = 20_000 in api.ts:7, with a visible switch and countdown.
• Hosting or a live URL: after review.

The idea in one sentence: a calm dark dashboard carried by the hamster-wheel illustration that spins only when the live feed says SPINNING. The journey card's cubes, its second headline and the slogans compete with that and should go.

Findings

1. Medium, taste: the "Small paws. Real progress." explainer card is marketing on a dashboard and adds about 630px at 390. Delete it and let the leaderboard take the full row.
2. Medium, copy: the page has a stack of slogans: three while the wheel is idle, plus the "Every revolution counts." footer line and "Tiny feet. Steady momentum." when it spins. The finding gives the plain replacement text for each.
3. Low, copy: the metric captions are mood lines; they should say where each number comes from (for example, a snapshot time).
4. Low, taste: at 390, "Community members" wraps to two lines, so its value sits about 18px lower than Badges earned. Hiding the label icons at the 38rem breakpoint, as the site already does at 22rem, fixes it.
5. Low, copy: "Through round #242" and the "#366" under the progress bar repeat the number just above them.
6. Low, accessibility: the Refresh button disables itself while it fetches, which drops keyboard focus. This one comes from reading the code; I couldn't confirm it in a browser.

The distance card shows 0.000 km in the builder's screenshots. The page explains that the hardware counter can reset, and I couldn't reach the feed to check the real value, s