The Weird Auction

Build "The Weird Auction" — a polished mobile-first portrait web app for the Eazo community.

CONCEPT
An auction house of the absurd: each lot is a procedurally-illustrated oddity with a deadpan catalog description — "Napoleon’s toothbrush (bristles: original)", "A ghost in a bottle (bottle included)", "One (1) haunted violin, self-playing". Drag the golden bid-slider to guess its final hammer price, then the auctioneer’s gavel falls and the "real" price is revealed with a dramatic paddle-war animation. Close guesses build your appraiser reputation.

RULES & STATES
- 12 lots per run from 24+ embedded oddities, each with a plausibility-engineered price and one absurd provenance line.
- Scoring by log-distance from the true price: within 25% = Expert Eye, an order of magnitude off = the audience gasps.
- Between lots the auctioneer delivers one-line commentary on your bid style.
- Result card: "Appraiser License" — accuracy grade, best call, most catastrophic miss, and a title from Flea-Market Rookie to Sotheby’s Nightmare.

OPENING
Open with a full-bleed cover artwork unique to this app, drawn procedurally in code: a velvet-draped auction stage under a single chandelier spotlight, a pedestal holding a taxidermied "questionable artifact" under a glass dome, paddles raised in silhouette, the title lettered on the auctioneer’s podium plaque. Give the title a contrasting outline or glow so it never dissolves into the background, and keep its center above 20% screen height from the top edge is NOT required — instead keep it clear of the top-right corner (language toggle lives there). Below the artwork: at most ONE short tutorial line, then exactly ONE text button that starts play. The button must sit fully above the bottom 88px of the viewport.

GLOBAL REQUIREMENTS
- Language: ship a lightweight built-in i18n layer with exactly two locales, English (en) and Chinese (zh). The app ALWAYS opens in English — never auto-detect or follow the system/browser language. Provide one small, comfortably tappable EN / 中文 toggle placed top-right, about 56px down from the top edge, clear of the device status bar. Chinese appears only after the user actively switches. All share output stays English regardless of locale. Never mix two languages on one screen.
- Fully self-contained: absolutely no external APIs of any kind — no AI calls, no third-party data, media or font services, no remote backend, no login. Embed all data and content in the app code.
- Real Share to the Eazo Community: on the result screen add a real Share button. Compose the result card as an image on a canvas and share it through the Eazo SDK community share (share.compose with the image attachment plus a short English text). Read the resolved { accepted } value: only when accepted is true may the button say "Sent to Eazo"; when accepted is false the button must read "Open in the Eazo app to share"; on error keep the original button. Never claim the post was shared on the plain web. Keep a Replay button next to Share.
- Mobile-first portrait, touch-only, no hover dependence. The app root must follow the host container height (position: fixed; inset: 0; height: 100%) — never 100dvh or 100svh. Size any canvas from its PARENT element using a ResizeObserver (run the fit once on mount), and convert every touch event through getBoundingClientRect() read at event time — never cache the rect and never use window.innerWidth/innerHeight for canvas sizing.
- Safe areas: keep all top UI at least 56px from the top edge. Keep every core interactive control (start button, submit, share, play controls) fully above the bottom 88px of the viewport — the Eazo mobile app overlays a native toolbar there that your code cannot detect.
- No background music and no autoplay audio.
- Complete real states: loading, empty, success, error where relevant. Every control must actually work — no alerts, console-log placeholders or fake results.
- Visual bar: rich, generous visual feedback on every touch (motion, particles, deformation, color, light) while keeping exactly ONE core rule understood within 3 seconds. Canvas 2D preferred for effects; do not use the canvas roundRect API (older iOS Safari lacks it). Never hardcode light text colors onto possibly-light backgrounds — derive text color from the theme.