# 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. **The bench (R1).** Build what `R1. The bench` asks for, to the numbers in `design.md`. In particular: At start, one tile per id in `starting_pack` is on the bench, with the label from the table. Check: the `R1. The bench` acceptance checks pass. 3. **The recipe table (R2).** Build what `R2. The recipe table` asks for, to the numbers in `design.md`. In particular: A recipe is an unordered pair of ids and a product id, or a miss (no product). Check: the `R2. The recipe table` acceptance checks pass. 4. **Discoveries (R3).** Build what `R3. Discoveries` asks for, to the numbers in `design.md`. In particular: A discovery is a product the person has made at least once. It is recorded even if `discoveries` is off. Check: the `R3. Discoveries` acceptance checks pass. 5. **Unknown pairs (R4).** Build what `R4. Unknown pairs` asks for, to the numbers in `design.md`. In particular: A pair with no recipe is a miss. The two tiles stay where they are. A short miss note appears for one second and then leaves. Check: the `R4. Unknown pairs` acceptance checks pass. 6. **Inputs (R5).** Build what `R5. Inputs` asks for, to the numbers in `design.md`. In particular: A `starting_pack` id that is not in the chosen table is refused before the bench loads, with a message that names the id. Check: the `R5. Inputs` acceptance checks pass. 7. **Files (R6).** Build what `R6. Files` asks for, to the numbers in `design.md`. In particular: One command runs the table tests, the UI combine tests, and writes the four screenshots. No network. Check: the `R6. Files` acceptance checks pass. 8. **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. 9. **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.