A tested module computes the next generation of a grid under the standard Conway rules, with a way to set initial patterns. The engine has no dependency on any UI.

This is task 1 of 5 of the project "Game of Life with Fancy Web UI".

Implement game of life with fancy web ui

Navigation map:

1. Build the core Game of Life engine — this task
2. Serve the grid over a web endpoint — a later task, not part of this one
3. Render an interactive board in the browser — a later task, not part of this one
4. Add playback controls and animation — a later task, not part of this one
5. Polish the visual design — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When a session tracks code health, every check scores it as one composite: duplication, complexity and dead code in the code you commit, plus your tests (the share failing) and their coverage once ololo can run them. So name both commands: a test: line that runs the suite and a coverage: line that runs it with coverage measured, in AGENTS.md or README.md (or test and coverage scripts in package.json). The task's health bonus is paid on that score.

When this task is done, write .ololo/task-1-done.md with a short description of what you changed and why (at least 10 words).

A web server exposes the current board state and a way to advance or reset the simulation. Requests return the correct generation for a given starting pattern.

This is task 2 of 5 of the project "Game of Life with Fancy Web UI".

Implement game of life with fancy web ui

Navigation map:

1. Build the core Game of Life engine — done before this task
2. Serve the grid over a web endpoint — this task
3. Render an interactive board in the browser — a later task, not part of this one
4. Add playback controls and animation — a later task, not part of this one
5. Polish the visual design — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-2-done.md with a short description of what you changed and why (at least 10 words).

A page draws the grid on a canvas or in styled cells and lets the user toggle cells by clicking. The board updates as the simulation steps.

This is task 3 of 5 of the project "Game of Life with Fancy Web UI".

Implement game of life with fancy web ui

Navigation map:

1. Build the core Game of Life engine — done before this task
2. Serve the grid over a web endpoint — done before this task
3. Render an interactive board in the browser — this task
4. Add playback controls and animation — a later task, not part of this one
5. Polish the visual design — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-3-done.md with a short description of what you changed and why (at least 10 words).

Users can start, pause, step, reset, and adjust speed, and the board animates smoothly between generations. Controls reflect the current running state accurately.

This is task 4 of 5 of the project "Game of Life with Fancy Web UI".

Implement game of life with fancy web ui

Navigation map:

1. Build the core Game of Life engine — done before this task
2. Serve the grid over a web endpoint — done before this task
3. Render an interactive board in the browser — done before this task
4. Add playback controls and animation — this task
5. Polish the visual design — a later task, not part of this one

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-4-done.md with a short description of what you changed and why (at least 10 words).

The interface has a cohesive, attractive theme with responsive layout, clear typography, and smooth transitions for cell changes. All existing functionality works unchanged across common desktop and mobile widths.

This is task 5 of 5 of the project "Game of Life with Fancy Web UI".

Implement game of life with fancy web ui

Navigation map:

1. Build the core Game of Life engine — done before this task
2. Serve the grid over a web endpoint — done before this task
3. Render an interactive board in the browser — done before this task
4. Add playback controls and animation — done before this task
5. Polish the visual design — this task

You are working in an existing codebase: the repository this session runs in. Do this task only, and keep everything else working.

When this task is done, write .ololo/task-5-done.md with a short description of what you changed and why (at least 10 words).