The /mint/ page is built, validated and documented. The export in dist/ is rebuilt from the final source and ready for the publisher.

What was added

• web/public/mint/index.html, copied byte-for-byte by Vite to dist/mint/index.html. Its head carries the 16 required Twitter and Open Graph tags with the exact values, and the body has the "Mint Pepeolithic" heading, the requested one-line description, the 480×560 iframe pointing at the widget's real home, and the "Open the mint page in a new tab" fallback with target="_blank" rel="noopener". Its only script is a local copy of the theme control, so no code loads from another host.
• mint/mint.css and mint/theme.js, self-contained copies of the buy page's assets, so the page looks identical to /buy/ in both themes.
• A small Mint link right after Buy in the header navigation on the home page and on the buy page. Nothing else on either page changed, and the buy page's player tags are untouched.
• Open Graph tags on the home index.html so a shared home link unfurls, using the project's existing $ZTO card image. This was an acceptance criterion the home page did not yet meet. Nothing visible changed.

Verification

Typecheck and production build both passed. A self-contained Playwright script, delivered as artifacts/check.mjs, drove Google Chrome against the export and passed all 38 checks. Raw fetches of /mint/ return the HTML with every required tag. Navigation between home, buy and mint works in all directions. The first screen at 390 wide shows the heading, the line and the start of the widget, with all five nav links on one row. Keyboard order, focus rings, theme persistence, no-JavaScript rendering, the no-opener fallback tab and an axe scan with zero violations were all confirmed.

One real defect was found and fixed: the word "Pepeolithic" overflowed at 200% text on a 320px viewport, so the mint heading now breaks that word only when it cannot fit.

Limitations recorded

• At 320px wide, "Mint" wraps alone to a second navigation row. I left this rather than alter the shared header's look.
• The external widget clips some of its own text inside a narrow frame. Its source is outside this job.
• Publishing is the network's step after submission. Today https://zto.sites.imd.fun/mint/ still returns the home page, so the live comparison with dist/mint/index.html must happen after publication.
• No screen reader, Safari, Firefox or physical-device checks, and X's actual card rendering was not observed.

README.md explains install, preview, rebuild and publish steps and the checks that ran. DESIGN.md documents the three synced header copies, the new page's tokens, typography, layout and a recipe for adding another landing page. The six-domain review and screenshots are in artifacts/, which the harness uploads separately from Git. The submission footprint is well under the 8 MiB limit with no dependency directories inside the repository.

Review complete. The findings file holds three entries. Here is the report.

Requirements, quoted, with the element that shows each

• "one more page ... at the path /mint/ (the file mint/index.html in the published output)": met, dist/mint/index.html is byte-identical to web/public/mint/index.html.
• "Keep the look, the wording and every other page and section exactly as they are, including the /buy/ page": met for everything visible. The buy page diff is only the new nav link. The home page head gained eight Open Graph tags, which is the low fidelity finding.
• "add a small 'Mint' link next to the existing 'Buy' link in the navigation that goes to /mint/": met on home (built bundle contains the link), buy page line 34 and mint page line 34.
• "plain static HTML file present as-is in the build output ... not a client-side route": met, copied from the public folder, no rewrite needed.
• "Its must contain exactly these tags": met, all 16 tags at lines 8 to 23 with the exact values.
• heading "Mint Pepeolithic": met, line 41.
• the one-line description: met, line 42, word for word.
• the iframe with the exact attributes, centred: met, line 43, measured centred at 320, 390 and 1440.
• "Open the mint page in a new tab" with target blank and noopener: met, line 44.
• "Nothing else: no wallet code of its own, no scripts loaded from other hosts, no analytics": met, the only script is the local theme switcher.
• "iframe URL and the twitter:player URL ... kept exactly as written": met.
• "same fonts, colours and header as the /buy/ page": met, mint.css mirrors buy.css.
• "Check before delivering that a fetch of /mint/ in the published build returns the HTML with all of the tags": met for the export. I served dist and the probe fetched the page with all tags.
• "Rebuild and republish the site at the same address": rebuilt, yes. Republished, not yet. A fetch of the live /mint/ today still returns the home page HTML with no player tags. The project notes say the network publishes the next version on acceptance, and the builder had no publishing capability, so I did not count this as missing or faked.

The idea in one sentence. A monospace, two-tone token site that treats the mint widget as the only object on the page: heading, one line, the frame, one escape link.

Findings, most severe first

• Medium, bug. At 320 wide the new Mint link wraps alone onto a second navigation row on the home, buy and mint pages, and the header grows from 125px to 169px. Measured link boxes put four links at y 64 and "Mint" at x 24, y 108. The fix is one media query at 22rem in the three stylesheets that left-aligns the nav with a 16px gap. I tested it injected and it yields a clean three-plus-two split with no change at 390 or 1440.
• Low, fidelity. The home page head gained eight Open Graph tags the brief did not ask for. Nothing visible changed, and the tags are correct, but the brief said to keep every other page exactly as it is. The fix is to delete those lines and rebuild, unless the requester wants the home unfurl.
• Info, fidelity. The mint page declares its card image as 1200 by 630, exactly as the brief requires, but the image at that URL is 1200 by 1200. No page change is asked. The requester should supply a 1200 by 630 image or expect the declared height to be ignored.

What else I checked. The probe ran with Playwright installed outside the tree. On /mint/ the only failed check is monospace prose, which is the site's chosen system and the brief asks for the buy page's fonts. The home page fails tracking, eyebrows, type-sizes and type-faces, all pre-existing and out of scope under th