Build WHEELWORKS, a complete playable 2D browser puzzle game for the Squeekchain community, not a landing page, token dashboard, or visual mockup. Ship the working game with a public playable HTTPS URL and source repository. Use original or properly licensed art and audio; do not copy Squeekchain's official NFT or other games' assets. No wallet login, token payments, contracts, backend, accounts, leaderboard, or runtime AI.

PLAYER LOOP: In a warm, whimsical hamster-powered workshop, route a limited supply of energy pulses from a fixed wheel to the marked devices. On a compact grid, the player places and rotates a limited inventory of three pieces: straight conveyor (opposite sides), elbow (one 90-degree turn), and alternator (routes successive arrivals to alternating outputs). Fixed walls and sockets are authored per level. Start the machine, inspect moving pulses and which devices received energy, then pause, step, reset, and change the layout. A board wins only when each target receives its displayed pulse quota within the displayed tick budget. If energy falls off the board, hits a wall, or collides, show where and why. Never claim a solution or win without the simulation reaching the quotas.

DETERMINISM: Simulate in discrete ticks, with a documented stable order of emission, movement, piece routing, collisions and target delivery. The same level, part placements, seed, and button sequence must always give the same outcome, independent of frame rate, animation, audio, or network polling. Bound ticks, pulses and events; make loops terminate safely; reset must restore the initial board and alternator state. Pause/step must not skip or duplicate a tick. Render movement smoothly without changing the simulation.

CONTENT AND TEACHING: Ship a short interactive tutorial and at least six handcrafted, solvable levels: begin with a straight route, teach turning, then alternation, then combine them with two goals. Include a level selector, clear goals and piece counts, success/failure feedback, and a restart path. Block out and playtest the puzzles before final art. Make the full level set winnable; store and verify a reference solution for every board. Avoid random unsolvable puzzles or generated filler.

SQUEEKCHAIN INTEGRATION: Read the public GET https://api.squeekchain.com/v1/settlements?range=24h response in the browser, using only documented public fields and validating shape, types and ranges. Find a recent settlement marked safe/confirmed; use its transactionHash and workAdded to select one of a small family of pretested solvable challenge variations/energy budgets. Freeze the chosen settlement and generated challenge when play starts; live updates must not change an active run. Show the real source transaction/round and a link to the appropriate Sepolia explorer after verifying the chain/network and link format. Clearly label fictional in-game energy versus actual chain work. On network error, stale/empty data, or no safe settlement, offer an explicitly labeled offline authored challenge; never fabricate transaction data. The chain connection must affect the challenge a player solves, not just decorate a dashboard. Do not assume mainnet SQK minting is available.

PRESENTATION: A cohesive original 2D clockwork/blueprint style: readable workshop tiles, clear source/targets/part orientation, a distinctive original hamster motif, legible labels, and restrained feedback for placement, pulses, success and failure. Do not rely on color alone. Make it usable on desktop and a narrow phone with real pointer/touch placement and keyboard access; provide visible focus, clear tap targets, sound mute and reduced-motion support. Keep critical game controls visible rather than covered by overlays. No confusing empty menus, fake buttons, placeholder art, dead links, or unimplemented feature claims.

PERSISTENCE AND SHARING: Save only versioned local progress and settings; validate on load. Make a bounded, validated share link for a challenge/board configuration (no arbitrary script or HTML in the URL). It must reopen the same fixed board and seed after reload; no cloud account or authoritative online scores. A share link is not evidence that the player solved it.

DELIVERY AND ACCEPTANCE: Provide a deployed working URL, source code/repository, build/run instructions, licenses/provenance for every shipped asset, and a concise test report. Exercise the tutorial and all levels; include automated tests for the deterministic simulation, at least one known solution per board, loop bounds, share-link validation, and API success/failure/offline fallback. Manually verify actual gameplay on desktop and mobile-width layouts, keyboard and touch, reduced motion, reload and share link, and inspect console/network errors. Do not mark complete if it only displays a design or if critical play/hosting/data features fail. Report any requirement you cannot deliver instead of silently substituting a simpler site.