# 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 graph (R1).** Build what `R1. The graph` asks for, to the numbers in `design.md`. In particular: A route is a graph of nodes, each with a view image, and edges labelled `left`, `straight`, `right`, or `back` (not every node has every way). Check: the `R1. The graph` acceptance checks pass. 3. **Votes and ties (R2).** Build what `R2. Votes and ties` asks for, to the numbers in `design.md`. In particular: During a turn, each voter id may cast or change one vote. Check: the `R2. Votes and ties` acceptance checks pass. 4. **A scripted session (R3).** Build what `R3. A scripted session` asks for, to the numbers in `design.md`. In particular: `fixtures/coast-session.json` is a list of turns, votes, and the expected node after each turn. Starting from `c0`, the session ends at `c-end` after 8 turns. Check: the `R3. A scripted session` acceptance checks pass. 5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in `design.md`. In particular: One command runs graph, tally, session, and fetch-hook tests, and writes the screenshots. The clock is injected. No network. Check: the `R4. Files` acceptance checks pass. 6. **Inputs (R5).** Build what `R5. Inputs` asks for, to the numbers in `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the `R5. Inputs` 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.