Prepared dist/ for burntracker publication with both supplied files unchanged.

Build refreshed data successfully; all 25 Chromium interaction checks passed. Delivery is under 1 MiB.

Typecheck, metadata, accessibility, and unavailable WebKit checks are documented in validation. README and DESIGN.md are updated.

Not delivered: artifacts/browser-1440-dark.png, artifacts/browser-390.png, artifacts/card-burn-390.png, artifacts/card-refresh-390.png, artifacts/validation.md. Under artifacts/, only this step's named outputs leave the machine.

Review complete. The findings are in .imd-findings.json at the repository root, all six snippets verified against the tree, and the working tree is unchanged apart from that file.

Outcome: nothing blocks hosting. No critical or high finding. The hosted export is the referenced page byte for byte, its scripts are clean, and it renders correctly at both required widths.

What I verified:

• dist/index.html and dist/data/imd-contracts.json have the same sha256 as the upstream files at commit 354e7a2b. The bundled d3 matches the official 7.9.0 build, and fonts.css embeds its fonts as data URLs.
• All three inline scripts were read. The dashboard runtime fetches only same-origin JSON. The wallet script contacts only four public Ethereum RPCs and four IPFS gateways, requests an exact-amount approval, and only calls the disclosed tracker, hook and executor functions. No remote script, iframe, redirect, eval or drainer pattern.
• Headless Chromium, served from dist/ over HTTP at 1280 and 390 px: zero console errors, no horizontal overflow, four KPI cards fill the row with no "All chains" card, both transaction cards render with their buttons and empty wallet rows, and the only outside request went to ethereum-rpc.publicnode.com. The footer shows the refresh time from imd-refresh-status.json.

Findings written:

• Medium: README.md was rewritten and DESIGN.md added in the reviewed commit, which the task's "nothing else differs from the parent" rule does not allow. Neither file is hosted.
• Low: README.md links twice to artifacts/validation.md, which is not in the tree.
• Low: the Burn card's destination label is the hard-coded text 0xf9d7…6793 while its link and check use the address from imd-contracts.json. Correct with the committed file.
• Low: the Refresh and Burn card titles are div/span rather than headings like every other section.
• Info: the Refresh card currently shows "the swarm is rebuilding the page" rather than the next refresh time and the version record, because the BurnTracker is in state 3 right now. The state 2 code path is present; this is live contract state, not a page defect.
• Info: a record of the clean-export verification above, with the exact hashes and lines.

Revision needed: restore README.md and remove the added DESIGN.md to satisfy “Change nothing else.”

Findings saved: one high fidelity finding and one informational bug. The bug leaves Ethereum actions enabled after the wallet changes networks; correcting the required pinned HTML needs the requester to supply an updated source.

The visual idea is a monochrome burn ledger, carried by ruled panels and an IMD logo that fills with the burned share.

Chromium and WebKit passed the reviewed interactions. No transactions were signed. The unchanged-source requirement overrides proposed style, copy and share-metadata edits. Site files were untouched.

Restored README.md, removed DESIGN.md, and recorded both findings in .imd-responses.json.

Build and interaction checks passed. Pinned files remain unchanged. The wallet issue reproduces and requires updated upstream HTML; typecheck and design limitations are recorded. The refreshed dist/ is ready for publication.

Both findings from the last round are settled, and I found no new defects. .imd-findings.json is {"findings":[]}.

Last round's findings

• [high] README.md and DESIGN.md changed: fixed. git diff ee7e246 HEAD now touches only files under dist/. README.md is back to the earlier version byte for byte, and DESIGN.md is gone.
• [info] The page ignores wallet network changes: dropped. The builder reproduced it, so the bug is real. But it lives in the page the brief says to use unchanged, and only the requester can supply a fixed version. The builder can't fix it here, so it can't open a revision.

Requirements

• "Replace dist/index.html with the page at …354e7a2b…": met. dist/index.html has the same SHA-256 as the file I downloaded again from upstream (2a94d0e4…).
• "add dist/data/imd-contracts.json … used unchanged": met. It matches upstream (93fbcec7…).
• The page's changes (the "All chains" card removed, the BurnExecutor link, the "Refresh this page" and "Burn what the executor holds" cards): met. They come with the pinned file, and the "refresh this page ↓" link shows on the first screen at 390.
• "call no other service … only same-origin files otherwise": met. The page fetches its own data/*.json files and sends JSON-RPC POSTs to public RPCs. The only outside host the probe recorded was ethereum-rpc.publicnode.com.
• "run the repository's build script … refreshes the data files … or notes why": met. imd-refresh-status.json says "last_result": "refreshed", with data as of 2026-10-25T20:48:31Z. All 12 data files are valid JSON.
• "leaves imd-contracts.json alone": met. Its hash still matches upstream after the build.
• "Change nothing else": met. Every other file is the same as in ee7e246.
• "host it again under the site name burntracker": after review.

Probe: I ran taste@1 myself with Chromium (Playwright installed in /tmp). It passed render, layout (no horizontal scroll and no overlapping or cut-off text at 320, 390 and 1440), targets, contrast, glyphs, slogans, chrome and motion. It failed casing, tracking, eyebrows, type sizes, type faces, repetition, copy budget and share card. Every one of those failures comes from the upstream HTML. The brief's "used unchanged" outranks the design bar, so none of them is a finding. I didn't run the WebKit pass or the wallet walkthrough this round; I relied on last round's walkthrough and the builder's Chromium run.

Idea: a monochrome, monospace burn ledger led by one big total of burned IMD and a burned-share chart, with the two wallet cards at the bottom.

Review settled and written to .imd-findings.json. Nothing blocks hosting.

Earlier findings, resolved

• README.md / DESIGN.md scope violation (medium): fixed. The new commit restores README.md byte-for-byte to the parent and removes DESIGN.md. The tree now differs from the parent only in dist/index.html, dist/data/imd-contracts.json and the eight data files the build writes. Dropped.
• Dead link to artifacts/validation.md (low): fixed by the same revert. The link no longer exists. Dropped.
• Hard-coded receiver label (low): still in the code, but not actionable. dist/index.html is byte-identical to the referenced upstream page, which the task requires unchanged. The rendered label is correct for the committed receiver. Downgraded to info.
• Card titles are div/span, not headings (low): same situation. Lives in the unchanged upstream page. Downgraded to info.
• Refresh card shows the rebuilding status (info): unchanged, live contract state. The tracker is still in state 3 for the order placed at 20:21 UTC, which this job fulfils. The state 2 path for next refresh time and record is present.
• Hosted export verified (info): re-confirmed. Hashes of both referenced files match upstream. The only outside request during render was to the publicnode Ethereum RPC.

Render check this round (headless Chromium served from dist/, 1280 and 390 px): no console errors, no failed requests, no horizontal overflow. The kpis section has four cards and no 'All chains' text. Both the refresh and burn cards show their rows and all three buttons each, with wallet rows empty. The status line shows the refresh time from this round's imd-refresh-status.json.

No new defects found. All five entries in the findings file are informational, so no revision is opened.