Numbers Station Log

Build "Numbers Station Log" — a polished, mobile-first portrait web app for the Eazo community.

CONCEPT
A shortwave numbers station broadcasting groups of digits. Logging them accurately and then finding the arithmetic pattern reveals a message, all offline and authored.

RULES & STATES
- Tune the receiver with a drag until the station locks, then tap to log each group as it appears on a scrolling display.
- Twelve broadcasts, each using a different real-world-style scheme: a running key, a book cipher index, a modular sequence.
- A worksheet lets you arrange logged groups into a grid, which is where the pattern becomes visible.
- Fading and interference occasionally corrupt a group, which must be reconstructed from the pattern — the best puzzle in the app.
- Result: the notebook page with broadcasts logged, schemes broken and the message recovered. Share the page.

OPENING
Open with a full-bleed cover artwork that exists only in this app, drawn procedurally in code — no shared layout, no "title + tagline + how-to card + Enter" template: a shortwave receiver with a glowing dial and a notebook filled with columns of five-digit groups written in pencil, a pair of headphones and a wall map with pins, late-night lamp light; the title is written across the top of the notebook page in careful pencil capitals. The title is part of the artwork (integrate it into the composition) and must carry a contrasting outline or glow so it never disappears into the art. Keep the title clear of the top-right corner where the language toggle lives. Under the artwork: at most ONE short tutorial line, then exactly ONE text button that starts play. Both the line and the button must sit fully above the bottom 88px of the viewport, and the artwork must fill the whole screen behind them.

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, never read navigator.language, never default to a "system" preference. Provide one small, comfortably tappable EN / 中文 toggle at the top-right, about 56px down from the top edge, clear of the status bar and the dynamic island. Chinese appears only after the user actively switches. Share output stays English in both locales. 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, image or font services, no remote backend, no login, no analytics. Embed every asset, dataset and piece of content directly in the app code (procedural drawing, inline SVG, emoji or code-generated art only).
- 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 via the Eazo SDK community share — call share.compose({ text, attachments: [{ type: "image", url: dataUrl, caption }] }) and 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 a thrown error keep the original label. Never claim the post was shared on the plain web. Keep a Replay button beside Share.
- Layout contract (this is where most builds fail — follow it exactly): the app root must follow its host container height with position: fixed; inset: 0; height: 100% — NEVER 100dvh or 100svh, because the Eazo host injects a ~60px banner above the app and dvh overflows past the screen. Size every canvas from its PARENT element's clientWidth/clientHeight through a ResizeObserver, and run that fit ONCE on mount as well (a mounted component receives no resize event, so the buffer would otherwise stay at the 300x150 default). Convert every touch point through getBoundingClientRect() read at event time — never cache the rect, never use window.innerWidth/innerHeight for sizing or hit-testing.
- Safe areas: every top-side UI element sits at least 56px below the top edge. NOTHING you draw yourself — buttons, HUD text, score, hints, legends, progress bars, captions — may fall inside the bottom 88px of the viewport, because the Eazo mobile app renders its own native toolbar over that strip and your code cannot detect it. Push the play area up instead of padding it down.
- Fill the screen: the scene must occupy the full viewport height. No dead flat colour bands or empty background strips in the lower half — if the play area has a fixed aspect ratio, extend the artwork (gradients, ground, atmosphere, particles, reflections) into the leftover space. Reviewers reject apps whose bottom half is an empty block.
- No background music and no autoplay audio of any kind. You MAY add very short procedurally synthesized WebAudio blips (oscillator/noise, created lazily inside the first user gesture) as touch feedback, with a mute control; never load an audio file.
- Complete real states: loading, empty, success and error where relevant. Every control must actually work — no alert(), no console.log placeholders, no fake results, no button that does nothing.
- Content depth: give the experience enough material that it does not feel thin — aim for at least 8-12 distinct items / levels / variations of the core content, and make the difficulty ramp gently (the first 20 seconds must be winnable by anyone). Reviewers penalise "too fast", "too few", "only one interaction".
- Visual bar: exactly ONE core rule, understandable in 3 seconds, and generous visual response to every touch — motion, particles, deformation, colour, light, camera. Prefer canvas 2D; use Three.js with primitive/procedural geometry only if the concept is genuinely 3D. Do not use the canvas roundRect API (older iOS Safari lacks it). Never hardcode a light text colour that could land on a light background — derive text colour from the active theme.
- Text must never be clipped (this is the single most common defect): any text you draw on a canvas must be measured with ctx.measureText and its font size reduced in a loop until it fits inside the canvas width minus a 24px margin on each side; DOM text must wrap or shrink rather than overflow. Titles, HUD labels, counters and hints all have to be fully readable at 393px wide. Equally, no drawn text may sit under the top 56px band or inside the bottom 88px band, and HUD chips must not overlap each other or the play area's focal object.
- Determinism: never call Math.random(), Date.now() or locale formatting during SSR render — move them into useEffect or use a seeded generator, so hydration never mismatches. Finish with zero console errors at 393x852 portrait.