NFT Pulse is built, verified in a real browser, documented and committed. The working tree is clean and the submission bundle is about 119 KB, far under the 8 MiB limit.

What was delivered (commit 1603624 on main)

• A Vite + React + TypeScript one-page site. The user pastes an ERC-721 or ERC-1155 contract address, and the site reads the last 24 hours of transfer logs from a public JSON-RPC endpoint in the browser. No wallet, keys or signatures are involved.
• Dashboard: transfer count, unique wallets, most active hour, largest burst in a 10-minute window, an activity meter labelled Quiet / Active / Hot / Explosive from transfers per hour over the last six hours, a pulse animation whose period shortens with that rate, an hourly bar chart with a table alternative, and a newest-first timeline with token ID, sender, receiver, timestamp, Etherscan link and copy buttons.
• Clear states: progress text while scanning, a skeleton layout, inline field errors, and distinct messages for wallet addresses, fungible-token contracts and RPC failures. Deep links via #/0x… work on load and on hash change.
• dist/ is committed with relative asset URLs, alongside the source and lockfile. README.md covers install, preview, rebuild and publish plus the validation record. DESIGN.md documents the tokens, typography, layout, components and responsive behaviour of the final source.

How it was checked

• Typecheck, 12 unit tests and the production build all pass with exit 0.
• Since the assignment's browser tool blocks file: URLs and no managed preview was provided, a bounded foreground Playwright script served dist/ under a /preview/ subpath and drove headless Chromium. It passed 40 of 40 checks with no console errors or failed requests, covering the error paths, a live collection scan, copy buttons (clipboard verified), pause control, hourly table, show-more, hashchange navigation, keyboard order with visible focus at 16 stops, reduced-motion, and overflow plus hit-area sweeps at 320, 375, 768 and 1280 px. Rendered contrast was measured; the lowest text pair is 7.57:1.
• The Better Interface review across all six domains found 12 issues, all fixed before the final build. The most consequential were out-of-gamut accent colours, a too-faint input border, a focus ring invisible on the primary button, and hash deep links that only worked on first load. The full record with coverage, findings and screenshots is in artifacts/validation.md and artifacts/screenshots/, which the repo's own exclude file keeps untracked for separate upload.

Stated limitations: no screen-reader session, physical device, native 200% zoom, high-contrast mode or automated accessibility scanner was run. The Hot and Explosive levels and the ERC-1155 path were verified through unit tests and CSS review rather than observed on a live collection, and results depend on the public RPC's 24-hour log range.