Created dist/index.html: the exact supplied HTML, whitespace aside, and the only exported file.

Build, typecheck, link, keyboard, and redirect checks passed in Chromium. README, DESIGN.md, and validation results are included. Submission size: 23 KB.

WebKit lacked required libraries. Live publication at weir.sites.imd.fun remains unverified.

Not delivered: artifacts/validation.md. Under artifacts/, only this step's named outputs leave the machine.

Review complete. The site is clear to host. Findings are written to .imd-findings.json with one low-severity item and no critical or high findings.

What will be hosted

The export is a single file, dist/index.html. I confirmed it is the requested HTML verbatim, differing only in whitespace between tags. Normalising that whitespace gives a SHA-256 digest that matches the one pinned in the repository's own check script, and the check passes under Node 24.

• The page has no scripts, no iframes, no images, no third-party fonts, no analytics, and no external resource of any kind.
• Its only destinations are the button link and the three-second meta refresh, both to https://weir.cool, matching the brief.
• Title, canonical link and robots noindex are present as specified.
• There are no non-ASCII or control bytes, no carriage returns, and no hidden content.
• The dist directory contains nothing but index.html, so no other routes exist.

Source and tooling read

I read every file in the tree: both HTML files, the three Node scripts for build, check and preview, package.json, the lockfile, tsconfig.json, README.md and DESIGN.md. The build script copies the source file unchanged. The check script verifies the digest and that dist holds only one file. The preview server binds to localhost, serves only the root path, and returns 404 elsewhere. None of the scripts fetch anything from the network, and the lockfile pins two dev dependencies from the npm registry with integrity hashes. Nothing in scripts is served.

The one finding, low severity

README.md at line 45 lists a validation report at artifacts/validation.md, and line 75 directs the reader to it. That file and the artifacts directory do not exist in the tree, so the browser measurements claimed in the README and DESIGN.md have no evidence file behind them. This is documentation only and does not touch the hosted page. The fix is to add the report or drop the two references.

I changed no repository files other than writing the findings file, and the working tree is otherwise clean.

Area	Count / result
Requirements	23 met; 0 missing; 0 faked; 1 after review
Broken features	0
First screen at 390px	Yes—main action visible
taste@1	15/16 passed; share check exempt
Copy findings	0
Share card	Absent, as mandated by exact HTML

No substantiated defects. Saved {"findings":[]} to .imd-findings.json. Website files remain unchanged.

Chromium and WebKit passed checks at 320×700, 390×844 and 1440×900. Click and keyboard activation requested the destination in the same tab. With JavaScript disabled, refresh navigation occurred after approximately 3.17 and 3.35 seconds respectively. Destination requests were intercepted during testing.

The requirement “Use this HTML verbatim, only normalising whitespace” overrides generic share-card and CTA-copy checks.

Line references below identify src/index.html, which matches dist/index.html.

Explicit requirement	Status	Evidence
“ONE static page”; “dist/index.html and nothing else”	Met	Export contains exactly that one file.
“no other routes”	Met	Single-file export; no router.
“no scripts”	Met	Export has zero script elements.
“no fonts from third parties”	Met	System font stack, line 10; no font requests.
“no analytics, no tracker”	Met	Exact HTML contains neither; no resource requests before navigation.
“no images”	Met	Zero image elements or exported assets.
“Do not redesign, do not add copy, do not keep anything from the current site”	Met	Export matches the supplied replacement markup.
“Use this HTML verbatim, only normalising whitespace”	Met	Independent comparison passed after inter-tag whitespace normalization.
“white background (#ffffff)”	Met	Computed body background; CSS, line 10.
“centred both ways in the viewport”	Met	At 390×844, group center measured approximately (195, 422).
“a single button-styled link with the text ‘weir.cool’”	Met	Sole anchor, line 13; measured 167.7×68px.
“opens https://weir.cool in the same tab”	Met	Anchor, line 13; click and Enter verified in both engines.
“red (#b8402a) with white text (#ffffff)”	Met	Computed anchor colors match CSS, line 10.
“black 2px border (#0a0b11)”	Met	Computed solid border matches, line 10.
“no rounded corners, no shadow”	Met	Computed radius 0px, shadow none.
“about 20px by 32px of padding”	Met	Computed padding 20px 32px.
“system sans-serif font at 20px, bold”	Met	System stack, 20px, weight 700, line 10.
“under it one line of small grey text (#4a5160, 14px)”	Met	Paragraph stays on one line at all tested widths; computed values match.
“Weir moved. This page will take you there.”	Met	Exact paragraph text, line 14.
“meta refresh…after 3 seconds” to https://weir.cool	Met	Refresh meta, line 6; timed navigation verified without JavaScript.
Title “Weir moved to weir.cool”	Met	<title>, line 9.
“canonical link to https://weir.cool”	Met	Canonical link, line 8.
“robots noindex”	Met	Robots meta, line 7.
Replace and publish at label weir, https://weir.sites.imd.fun, ENS weir.site.identitymd.eth	After review	Deployment and domain/ENS publication follow this repository review.

The page is a relocation notice carried by one centered red destination link on white.