Continue the existing PRISM RIOT website delivered by job https://explorer.imd.fun/jobs/ac5b29a5-8eef-4672-9982-979dce7ba6b9 . Update its current repository https://github.com/identity-md-launches/launch-1153-build-test-independently-review and publish the improved site under the existing public project URL https://prio.sites.imd.fun/ . Preserve the neon artwork, logo, X link and responsive visual identity. Use existing mainnet contracts only; no token, pool, hook or application redeployment.

Fix the gap between the attractive arcade and actual playable token economy. The owner has now completed Phase A: at Ethereum block 26160643 all nine checked hook/treasury/PRIO/sink/funder/Arena/adapter bindings matched their expected existing addresses. Preserve these correct bindings. Phase B remains incomplete: both executors, treasury IMD and adapter Intake/payment asset are unset; IMD pool and price floors are unconfigured, callbackConfigured and paidRequestsEnabled are false. Treasury totalIncome, operating budgets, staking rewardReserve/rewardRate, Arena roundCount and prize pools are zero. Read fresh chain state; do not assume these observations remain current. Distinguish a missing configuration from a frontend error, RPC failure or absent operator.

Provide Turkish-first explanations with an English toggle. Put three clear navigation items at the top: Free Practice, PRIO Games, Staking. Every game card must have a clearly labelled free practice action and a separate real-PRIO action. Practice spends no tokens and awards no real PRIO; faction selection alone is cosmetic. Real play must show the specific blocking reason when unavailable and link to the relevant readiness detail. Avoid silent clicks and generic 'pending' messages. Explain practice controls before the first action and display validation/errors inline. Use actual Arena scoring; do not advertise unsupported game mechanics.

Preserve the cinematic prism and faction art; improve spacing, typography and hierarchy. The first screen must explain the experience and offer 'Ücretsiz dene', 'PRIO ile oyna', 'Stake et', each with one sentence explaining its purpose. Add 'Nasıl oynanır?' before the first game. Visitors should understand actions, costs and readiness within 15 seconds. Keep controls readable and operational details expandable.

Add lightweight idle/selection reactions: dragon flame, frog bioluminescence, wolf frost and raven lightning, plus choice, attack, reveal and result animations. Effects must follow actual game/transaction states; celebrate real payouts only after confirmed receipts. Label practice celebrations. Bundle finished media, pause offscreen effects, support still/reduced-motion fallbacks and opt-in sound muted by default. Keep mobile loading and wallet actions responsive.

Game cards must show objective/scoring, practice/live status, entry cost, maximum loss, funded prize and entry/reveal countdowns. Explain unavailable values when no round exists; offer rules before wallet connection. Local random practice earns no tokens and does not prove skill. Preserve deployed scoring; never fabricate activity, player counts, prizes or urgency.

Add seasonal leaderboards, achievement badges and new challenges. Derive paid rankings from verified Arena events with documented scoring and dated seasons; label local practice separately and show empty states honestly. Badges are informational, without token value or new reward rights. IMD-generated challenges require real reviewed operator content and owner approval of future-round rules. Use the existing data architecture within this website scope, preserving contracts and fee-funded budgets.

Show a prominent live readiness summary: contract bindings, operating configuration, operator connection, funded prizes and open rounds. Expose the existing owner-only setup panel in top navigation when the owner connects. Keep its simulated, receipt-checked Phase A sequence and irreversible-binding safeguards; skip already-correct settings and stop on conflicts. Explain that owner setup needs wallet signatures and ETH gas and does not itself create a game or reward funding. Keep Phase B budget settings separate with plain-language explanations and reviewed inputs, not guessed values.

Add an owner-only round management panel using the actual deployed ABIs and application deployment guide. Guide the owner through the required OracleAdapter.pinQuestion and Arena.createRound sequence with matching deadlines, published question/scoring and a prize budget actually available on-chain. Simulate each transaction, request wallet confirmation, wait for receipts and refresh state. Display the next required action if no rounds exist. Preserve locked rules, spending caps, player deposits, refunds and prize accounting. Do not open paid rounds without required oracle/operator readiness and funding. When income is insufficient, explicitly show free-practice-only operation.

Configure a single public operator-status endpoint for the project when its separately hosted operator is available; ordinary players must not need to paste a server URL. Preserve signed executor/status verification, expiry checks and offline handling. Document the operator handoff and outstanding setup; never describe static IPFS hosting as a running backend. Never put private keys or paid IMD API credentials in the browser or claim the operator is active without evidence.

Explain real play as enter/commit, reveal before deadline, then claim/refund. Show 100 PRIO escrow + 2 PRIO fee, maximum 22 PRIO loss plus gas, exact approvals, funded prizes and deadline reminders before entry. Keep reveal-secret export/import and independent access to eligible reveals, withdrawals, claims and refunds. Give each transaction a visible pending/success/error status and receipt link.

Staking must prominently say 'Deposits work; rewards are not currently funded or streaming' when applicable. Show actual reserve, stream status and claimable rewards before deposit confirmation; never imply staking alone creates income. Fix the reward-rate display in web/src/panels.tsx: fmt already converts 18-decimal units, so do not divide rewardRate by 10^18 again. Use precise token formatting and distinguish reserved past liabilities from an active new reward stream.

Test production build and mobile/desktop flows: practice without wallet approval, no rounds, incomplete bindings, zero staking rewards, operator offline/expired, RPC failure, wrong owner/network and failed transactions. Test the real funded entry/commit/reveal/claim/refund path on a local fork without broadcasting tests to mainnet. Review desktop/mobile screenshots for readable instructions, distinct practice/live actions, clear game-card costs and consistent branding. Verify visible faction reactions, keyboard controls, reduced motion and opt-in sound. Return updated GitHub source, public site URL and a concise checklist separating delivered UI fixes from owner signatures, funding and server setup still required. Do not bypass readiness checks to make buttons look functional.