WEBSITE: Sorphera - coherent 360-degree plush globes and draw countdowns

Update the EXISTING website; preserve newer work.

Repo: https://github.com/identity-md-launches/launch-961-build-sorphera-smart-contracts

PR #7: https://github.com/identity-md-launches/launch-961-build-sorphera-smart-contracts/pull/7

Demo: https://sorphera-a-world-of-possibility.sites.imd.fun/

ONE Website task. Keep Sorphera and "Weekly ETH & NFT lottery ball jackpots. Powered by FWA.", ice-blue wording, pink accents, USD, budgets, buy-12-get-1 Passport and the Atlas teaser.

1. FINISH THE ENTIRE PLUSH GLOBE

The user wants the SAME plush globe all the way around. Preserve PR #7's improved front; fix the rear/side material change.

Evidence:

• web/scripts/plush-materials.py mirrors one small felt swatch across the unseen hemisphere.
• web/public/brand/plush/albedo.webp has a photographic middle and visibly tiled, darker outer areas.
• web/evidence/revision/plush-comparison.jpg shows the defect at 90, 135 and 180 degrees.

Use existing references: web/public/brand/sorphera-brand-board-ice-blue.webp, eth-ball.webp, nft-ball.webp and web/artwork/plush-source.webp. Originals:

https://drive.google.com/drive/folders/1AbFGlSeh_epw4TgeGRen4C4aHgP65v0N?usp=sharing

Preserve the approved front. Complete one coherent 360-degree object: matching felt fibres/scale, ice-blue ocean, raised pink applique continents, rounded edges/contact shadows, stitched panel seams, soft silhouette and lighting on front, sides, back and poles. Natural shading is fine; a different material or colour is not. Apply the same standard to the pink/cream bonus in BOTH games.

Remove mirror tiling, kaleidoscope/diamond patterns, flat rear continents and the transition into the photographed front. Recolouring the tiled back is insufficient. Use coherent materials/relief and non-repeating, seamlessly blended textures. Keep ONE padded cream badge with dynamic black digits attached to the curved front; do not duplicate it around the globe.

Fix the maps and generation recipe, preserving renderer/API/caches where possible. Allow necessary renderer fixes. Rebuilding must not restore the defect.

Preserve badge-away entry, smooth rotation/deceleration, stop, number callout, hold and travel to slot. Never conceal the back with faster motion, a cut, an image swap or a flat-disc flip. Keep one asset family across picker, stage, slots, baskets, receipts and fallbacks. Preserve performance, pause/resume/replay/skip, muted-default audio, reduced motion and gated announcements/results.

2. DISPLAY BOTH SALES CUTOFF AND DRAW TIMING

Verified gap: Home, Play and receipts show a cutoff countdown. The frontend Round type and ContractAdapter omit earliestDraw although the contract returns it. Draw Room defaults to a round-41 sample replay with no upcoming schedule.

Preserve contract semantics:

• Purchases require block.timestamp < round.cutoff. Sales stop at cutoff even before close() runs.
• earliestDraw = cutoff + the round's frozen drawDelay.
• earliestDraw is the earliest REQUEST time, not guaranteed availability of winning numbers. FWA reconciliation must finish; randomness must be requested, fulfilled and finalized. NFT ties may need another request.
• ETH/NFT schedules are independent. Client clocks never select results or authorize purchases.

Carry existing timing fields through the frontend model/adapter. Display authoritative round data; no Solidity or ABI change is needed for this.

DEMO schedule: retain existing cutoff anchors, ETH Sunday 00:00 UTC and NFT Sunday 01:00 UTC. Add an explicit illustrative 30-minute gap to each draw-window opening. This is a prototype choice, not a production policy or result-time guarantee. Label the schedule simulated. Keep a round's timestamps stable across navigation/reload; do not reset its deadline into the future. Later demo rounds need distinct identities. Preserve existing records safely.

Each game/round should show: "Ticket sales close in [countdown]" + exact date/time.

"Draw window opens in [countdown]" + exact date/time.

"Numbers follow once the prize pool and draw are confirmed. Delays are possible."

Use "Draw scheduled for" only if a separate presentation schedule is explicitly supplied. Never relabel earliestDraw as guaranteed showtime or use cutoff as draw time. Show missing schedule data honestly.

Use local time with an explicit time zone and UTC timestamps internally. Show days/hours/minutes, adding seconds for the final hour. Timers must recover after tab suspension and never go negative.

Make both times obvious beside homepage jackpots, on Play/checkout, receipts, My tickets and Draw Room. Give the upcoming draw countdown visual priority in Draw Room. Keep mobile cards compact. Earlier "no countdown pressure" guidance means no sales-pressure gimmicks; factual schedule timers are required.

3. AN UPCOMING-DRAW JOURNEY

Default Draw Room to upcoming rounds with an ETH/NFT switch, round identity, both times and status. Keep past/sample replays clearly separate and preserve direct replay links/scenarios.

"View your draw" must open the ticket's exact game and round. Never silently open another round or present invented results for an open round. Optional fixture previews remain explicitly labelled simulations.

Use shared, state-aware timing across pages:

• Before cutoff: entries open, both times visible.
• At cutoff: disable paid/reward confirmation, show "Entries closed", preserve drafts/unused rewards. Recheck at confirmation; an old open modal must not succeed.
• Before earliestDraw: countdown to the draw window.
• Once the window opens without results: show the known state, such as "Preparing the prize pool" or "Waiting for the draw result". Do not claim randomness was requested unless known.
• With confirmed results: enable the existing reveal experience. Demo fixtures remain labelled simulated.
• NFT tie-break, rollover, cancellation and paused sales have accurate states.

A timer reaching zero must never fabricate results, announce a winner, reopen sales, reset a deadline or show a misleading LIVE badge.

Add a clearly named calendar action for the draw-window opening, including the exact game/round link and delay caveat. Keep any sales-closing reminder separately named. Do not relabel the current cutoff calendar event as a draw appointment.

4. ACCEPTANCE

Provide reference/front/side/back comparisons at actual picker and draw sizes for blue and pink. Include a full-turn contact sheet at 45-degree intervals and a normal-speed 25+ fps clip through entry, turn, stop and landing. Inspect the back as closely as the front, in WebGL and software fallback. Front screenshots alone cannot prove this fixed.

Check desktop/390px mobile, keyboard and reduced motion. Use controlled clocks to test cutoff with an open checkout, draw-window opening, delayed result, NFT tie-break, sales pause, tab resume, reload, game/round links and distinct calendar events. Closed/delayed states must preserve Pa