Every settled round in which the real hamster did work on the wheel is one floor of an endless tower, read from the two SqueekCore contracts on Ethereum Sepolia: the round's work sets the floor type, its hash seeds the enemies, map and weather, and long gaps between rounds leave treasure chests. Players fight turn-based battles with a team of hamster pets, feed them to level up, and climb a public leaderboard. There is no token, no NFT, no real money and no transaction. Coins exist only inside the game and wallet sign in is a signed message.

This repository holds the working game. Its server runs separately at https://hamster-tower-game.vercel.app and is not part of this job: the battle replay, random rolls and player data stay there. This job fixes the four problems below, then builds and hosts the static client, which calls that server.

Fix the four problems below, found by QA at this commit, then rebuild and host the site. Change as little as possible. This is a repair, not a redesign: keep the look, copy, game rules, balance and layout. Only edit client/index.html and client/ui.js. Do not touch shared/, lib/, api/, sql/, scripts/, tools/, tests/ or public/. Do not add a dependency. Do not add console.log. Do not use em dash or en dash characters anywhere. All text stays in English.

PROBLEM 1: shared links have no preview. client/index.html has a description but no Open Graph or Twitter tags, so a link posted on X or Discord shows no picture. Add og:title, og:description, og:type website, og:image and twitter:card summary_large_image, using the existing title and description text. The image must be the absolute address https://hamster-tower-game.vercel.app/art/bg_login.webp, because the site is also served from other addresses.

PROBLEM 2: with JavaScript off the page says "Opening the tower..." forever. Add a noscript message in client/index.html saying the game needs JavaScript. Keep the existing splash.

PROBLEM 3: keyboard focus leaves open dialogs. In client/ui.js, sheets from sheetHTML have role="dialog" and aria-modal="true", but Tab walks out of them into the page behind. The full screen dialogs written into #overlay (spin, forge and wheel runs) never receive focus at all, so a keyboard user stays on a control behind them. While a sheet or overlay dialog is open, Tab and Shift+Tab must cycle through its own buttons and links only, and when an overlay dialog opens focus must move to its first button. render() rebuilds the DOM often, so handle this with one keydown listener on document, not per element. Battles have no dialog and must behave as they do now. Do not move focus while a sheet re-renders unless focus was lost.

PROBLEM 4: Escape closes the wrong thing during an animation. In the keydown handler in client/ui.js, pressing Escape while a spin, forge or wheel run is still playing (SP is set and SP.done is false) falls through and closes the sheet behind the overlay. Escape must act like the Skip button in that case, by calling ACT'spin-skip', and must leave the sheet open. When SP.done is true it keeps closing the overlay as it does now.

Build the site with: npm install && npm run export. The output is dist/, with index.html at its root and relative asset paths. Do not use npm run build for hosting: that one is for the server deployment. dist/ calls the server named in site.config.json, so leave that file as it is. The server already accepts calls from https://hamster-tower.identitymd.eth.limo and https://hamster-tower.imd.site, so host under the label hamster-tower.