Redo Clanker Coffee's website

the prompt

Redo the website for Clanker Coffee Co. and make it the best coffee store site on the internet. Context you should know: this is going into a video watched by a large audience. Your site is put on screen next to the company's current site and next to three other frontier models given this identical prompt. The comparison is blind. Never put your model name, your company's name, or any mention of which AI made it anywhere in what you build: not in on-screen text, credits, the page title, file names, code comments, or metadata. Clanker Coffee Co. is a specialty roaster in Chicago's West Loop. Its current site is live at https://clanker-coffee.vercel.app. Study it, then build its replacement. Everything the company owns is in `./clanker-kit/`: the brand book (`BRAND.md`), logos, the six bag labels, a photoreal scene for each blend, the product lineup, fonts, colors, and `PRODUCTS.md` with every product, price, the Autopilot subscription and the wholesale terms. Use all of it. Requirements: 1. **Research first.** Look at how the best real coffee companies sell online and decide what Clanker's site should do better than its current one. Write that plan to `PLAN.md` before you build. 2. **It is a store.** The coffee and the shopping are the point. A shop with every product at its real price, a product page for each blend with tasting notes, sizes and an add-to-cart that works, a working cart, the Autopilot subscription with its 2- or 4-week choice, a wholesale page with an inquiry form, and an about page for the roastery. 3. **On brand, and better.** World's Fair art deco, the brand's colors and type, Sterling as the brand's host, the product photography front and center. Copy is confident and quiet, with at most one joke per screen. The brand's AI puns belong on the bags, not in every headline. 4. **Make it feel expensive.** Motion, scroll choreography and transitions are expected. Any new imagery you need, you make with code, Blender or the image generator, consistent with the kit's look. 5. **Desktop and mobile.** Every page works and looks right at both. Check it in a real headless browser at both sizes and fix what you see. 6. **Ship it runnable** as a static build with a documented run command, a working cart that keeps its state between pages, and a README that says what you changed from the current site and why. DONE when: every page in requirement 2 exists and works at desktop and mobile, add-to-cart and the subscription flow work end to end, it runs from a documented command, and it is clearly better than the current site at full screen.

…