Impossible Suitcase

Build "Impossible Suitcase" — a polished mobile-first portrait web app for the Eazo community.

CONCEPT
Your flight boards in 90 seconds and EVERYTHING must fit in one suitcase. Drag and rotate absurd items — a cactus (prickly, keep away from the balloon), a grandfather clock, seventeen souvenir spoons, one enormous shoe — into the suitcase grid, Tetris-style. Items have personality: the cactus pops the balloon, the clock chimes when nudged, the spoons scatter. Close the lid and face the airline’s weight-and-chaos verdict.

RULES & STATES
- 10 items per run from 18 embedded shapes on a visible grid; drag to place, double-tap to rotate; incompatible neighbors trigger comic events (pop, chime, scatter).
- 90-second boarding timer with escalating gate announcements in text.
- The lid-close is a physics moment: overstuffed cases bulge, strain the zipper stitch by stitch, and may burst gloriously.
- Result card: "Boarding Verdict" — packed vs abandoned items, chaos incidents, an overweight-fee bill itemized absurdly, and a packer rank (Minimalist Monk to Zipper Criminal).

OPENING
Open with a full-bleed cover artwork unique to this app, drawn procedurally in code: an overhead flat-lay of an open vintage suitcase plastered with travel stickers, surrounded by absurd luggage — a cactus, a grandfather clock, one single enormous shoe — arranged like a puzzle about to happen, the title on a luggage tag tied to the handle. 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.