## Project handoff

### Stack
- Vanilla HTML, CSS, and JavaScript; no framework or build tool is present.
- Browser entry point: `index.html`.
- Game modules under `src/`: state, input, update, render, game loop, and main bootstrap.
- ASCII/semantic rendering with a dark terminal-inspired visual style, green monospace text, bordered dungeon grid, status panel, and message area.

### Existing work
- `index.html` defines the page structure and loads the stylesheet and JavaScript entry module.
- `style.css` contains the responsive terminal-like layout and dungeon presentation.
- `src/state.js` defines game state.
- `src/input.js` handles keyboard input concepts, including arrow keys, WASD, and Space/wait behavior.
- `src/update.js` contains movement/gameplay update logic, including walls, enemies, and exit progression.
- `src/render.js` contains DOM/ASCII rendering logic.
- `src/game.js` contains game-loop orchestration.
- `src/main.js` is the browser bootstrap module.
- `README.md` documents the intended controls and objective.
- `docs/design-reference.png` is available as visual guidance only; the written prompt and current HTML target remain authoritative.

### Constraints and preservation guidance
- Preserve the minimal browser-game scope and ASCII-only dungeon presentation.
- Keep the dark terminal aesthetic, green monospace typography, bordered grid, compact status panel, and message area.
- Maintain responsive readability on mobile.
- Avoid introducing image-based gameplay assets or replacing the semantic HTML/CSS/ASCII approach with canvas unless explicitly required.
- Keep controls accessible through both arrow keys and WASD, with Space available to wait.
- Do not treat the supplied design reference as authoritative over the user request.

### Current blockers / verification status
- The supplied files were not executed during this handoff, so runtime behavior, module loading, and the primary interaction are not verified.
- Confirm that the browser can load the ES modules when opening `index.html` directly; if local-file module restrictions occur, use a small static web server.
- Verify that `src/main.js` actually initializes the state, input, update loop, and renderer against the DOM elements defined in `index.html`.
- Verify event listeners, enemy resolution, wall collision, exit completion, restart behavior (if implemented), and responsive layout in a browser.
- No missing renderer or event loop can be asserted from file listings alone; inspect and test the existing implementations before adding replacements.

## Visual handoff
VISUAL HANDOFF:
- Design reference: `docs/design-reference.png`. It is non-authoritative visual guidance; the user prompt and runnable target remain authoritative.
- Design brief: Build a minimal responsive browser dungeon game rendered entirely with semantic HTML, CSS, and ASCII characters. Use a dark terminal-inspired interface with green monospace text, a bordered dungeon grid, a compact status panel, and a message area. The player moves with arrow keys or WASD, defeats or avoids enemies, and reaches the exit while walls block movement. Keep the game immediately playable, readable on mobile, and free of image assets.