# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **Movement (R1).** Build what `R1. Movement` asks for, to the numbers in `design.md`. In particular: Hoppers (`H` and `h` for two colours) slide any number of clear squares along a row, never a column, and never through or onto a blocker (`B`) or another hopper. Check: the `R1. Movement` acceptance checks pass. 3. **A known solvable level (R2).** Build what `R2. A known solvable level` asks for, to the numbers in `design.md`. In particular: Level I1 in the intro pack is the 5 by 5 grid in `design.md`. Check: the `R2. A known solvable level` acceptance checks pass. 4. **A known unsolvable position (R3).** Build what `R3. A known unsolvable position` asks for, to the numbers in `design.md`. In particular: Position U1 in `design.md` is not solvable: a hopper is boxed in with no path to its burrow, even with blocker help. Check: the `R3. A known unsolvable position` acceptance checks pass. 5. **Levels and chrome (R4).** Build what `R4. Levels and chrome` asks for, to the numbers in `design.md`. In particular: Each pack is a file of levels. A level has an id, a grid, and the documented solution length for solvable ones, or `unsolvable`. Check: the `R4. Levels and chrome` acceptance checks pass. 6. **Screenshots and files (R5).** Build what `R5. Screenshots and files` asks for, to the numbers in `design.md`. In particular: Frames: `start` of I1, `mid-solve` after three documented moves, `solved` after seven, `blocked` of U1. Check: the `R5. Screenshots and files` acceptance checks pass. 7. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 8. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.