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

• High — fidelity: identical API data produces different boss HP and settlement outcomes in different browsers.
• High — fidelity: “All time” silently excludes attacks older than 5,000 rounds.
• Medium — bug: expired telemetry continues showing live speed, damage rate, and animation after API failures.

The visual idea is a communal hamster raid carried by chunky pixel creatures and a cream-and-orange palette.

The site source remains unchanged. Wallet signing was not exercised; WebKit interaction testing was unavailable.

Fixed all three findings: shared Boss HP/results, full-history leaderboard indexing, and telemetry expiry. Rebuilt dist/ and wrote the required responses and documentation.

Build, typecheck, 11 unit tests, Chromium regressions, and all 16 design checks passed. WebKit’s runtime was unavailable; live wallet signing remains untested.

All three earlier findings are fixed, verified in Chromium and WebKit:

• Shared boss: independent visitors show identical HP, 30,115 wheel damage and settlement results.
• All time: both historical and current attackers appear with 1,000 and 500 damage.
• Expired telemetry: readings become unavailable, animation stops, and counted damage remains.

One new high bug: outage readings overlap adjacent labels at 320, 361 and 375px. At 320px, “Unavailable” overlaps “damage” by approximately 5px horizontally. A tested CSS proposal removes the collision while keeping Attack visible.

The reproduction, source citation and exact proposed change are in .imd-findings.json. No website files were changed.

The visual idea is a shared hamster-powered raid carried by pixel creatures and square arcade controls.

Wallet signing was not performed; transaction construction and unsigned interaction states were reviewed.

I reproduced the reported bug and fixed it. On narrow phones the wheel now sits above the stats, so "Unavailable" no longer paints over the "Hamster damage" label. The change is committed as 595910d.

Reproducing it: The existing browser test only checked that the page didn't scroll sideways, which is why the bug got through. I added a check to tests/raid.browser.mjs that compares where each label's and value's text actually draws against its own cell and against the other stats. I ran it in Chromium at 320, 361, 375 and 390 wide, with the live API down for 3 minutes. Against the previous build it failed at 320: both "Unavailable" values ran outside their cells.

Fix: I made the reviewer's proposed change at src/styles.css:119. For screens 420px wide and narrower, the wheel row is now one full-width column, so the 48px wheel sits above the stats. The gap, wheel size, two-column stats and text sizes are unchanged.

Results after rebuilding dist/:

• Browser test (Chromium): passes, with no overlap or text running out of its cell at any of the four widths. At 390 wide the Attack button still ends inside the first screen.
• Unit tests: 11 of 11 pass.
• Design probe (taste.mjs): 16 of 16 checks pass.
• Screenshots: I looked at the 320 (normal) and 390 (API down) screenshots myself. Labels and values are separate in both.

Not checked:

• WebKit: it isn't installed on this machine, so I couldn't recheck the reviewer's WebKit result. That's noted in VALIDATION.md.
• Playwright path: the one the README names doesn't exist here, so I used another local install (version 1.64.1). The README still names the old path.

I also updated the responsive section of DESIGN.md, added this revision's evidence to VALIDATION.md, and wrote .imd-responses.json marking the finding as fixed. The setup excludes that file from git on purpose, so it's in the working tree but not in the commit. Git had no author identity configured, so I committed under the same "IdentityMD Worker" identity as the earlier commits.

The reported overlap is fixed in src/styles.css:119. Replaying API 503 responses and advancing the clock 180 seconds produced no text spill or collision at 320, 361, 375 or 390 pixels. At 390×844, Attack ended at y=604px. The author’s browser regression suite also passed.

Requirements assessed from source and browser states, including controlled fixtures:

The visual idea is a shared hamster raid presented through pixel creatures and a warm burrow palette.

WebKit could not run, so Safari remains unverified. No wallet transaction was signed. Earlier counts marked “—” were not supplied.

.imd-findings.json contains {"findings":[]}. Site files are unchanged.