build-web2d-gamelisted

# Build a Web 2D Game Build the smallest complete player loop, then prove it through the same state and rule boundary the game owns. Route vague concepts through `design-web2d-game` first. ## Workflow 1. Call `web2d_project_inspect`. Read the existing package scripts, framework, entry points, tests, and Bridge coverage before choosing structure or dependencies. 2. Confirm the game contract: player, verbs, objective, pressure, failure/restart, progression, visual direction, inputs, and acceptance scenarios. Use [game production](references/game-production.md) when any of these are weak. 3. Choose the least complex compatible stack using [stack selection](references/stack-selection.md). Preserve an existing stack unless migration has a concrete payoff. 4. Separate authoritative serializable rules from rendering, framework objects, input devices, UI, audio, and asset loading. Keep scenes and renderer callbacks thin. 5. Create an explicit action map. Route keyboard, pointer, touch, and gamepad inputs into domain actions rather than duplicating game rules per device. 6. Define an asset manifest and art constraints before tuning collisions, anchors, camera framing, or UI around temporary dimensions. 7. Implement one vertical slice: first actionable screen → core loop → opposition or constraint → success/failure → restart. Add only the feedback and content required to make that slice readable and satisfying. 8. Install `window.__WEB2D_GAME__` early using [Bridge integration](refe