I noticed there's a weird line in draw(): `ctx.arc(pad + GOAL.r !== undefined ? ... : 0, ...)` — this is sloppy ternary operator precedence. `pad + GOAL.r !== undefined` evaluates as `(pad + GOAL.r) !== undefined`, which is always true, so the true branch always gets executed — it's harmless, but let's clean it up.

Let me fix one sloppy line in the goal-marker drawing:

Let me actually do a more thorough test — run the maze generation and solver headlessly to verify the logic works end-to-end. Let me extract the core logic and test it. Actually, the generation and solve functions reference globals. Let me do a quick functional test of the algorithm logic itself.

Let me do a real end-to-end logic test of the maze generation and A* solver:

All tests passed: mazes are fully connected (perfect mazes via recursive backtracking), and both A* and BFS find the path of the same optimal length (in a perfect maze the path is unique). index.html exists. Done.

Done. `index.html` is at `/tmp/ws/index.html` — a fully self-contained single-page app with no external resources. **What it does:** - **Maze generation** — Recursive backtracker (iterative DFS with an explicit stack), producing a perfect maze with walls drawn on a canvas. Verified fully connected for all sizes. - **Solver** — Both **A\*** (with Manhattan heuristic, binary-heap priority queue) and **BFS**, selectable via dropdown. Tested headlessly: both find identical optimal paths on every generated maze. - **Animation** — Explored cells fill in blue as the algorithm runs, then the solution path traces back in cyan from start (green) to finish (red). - **Controls** — New Maze button, Solve button, maze size (15×15 to 61×61), algorithm picker, and a speed slider; live status shows cells explored and final path length. - Crisp rendering via devicePixelRatio scaling, responsive canvas, dark theme with a legend. All CSS is in a `<style>` tag and all JS in a `<script>` tag — no separate files, no network requests.