# 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 payload (R1).** Build what `R1. The payload` asks for, to the numbers in `design.md`. In particular: The world, the textures, and a tiny engine are packed into a documented payload of at most 2,953 bytes (QR version 40, binary, if `code` is `qr`; the raw file must be the same bytes). Check: the `R1. The payload` acceptance checks pass. 3. **Boot and walk (R2).** Build what `R2. Boot and walk` asks for, to the numbers in `design.md`. In particular: Boot shows `title` for 2 seconds (tests may skip the wait) and then the first-person view at the spawn in `design.md`. Check: the `R2. Boot and walk` acceptance checks pass. 4. **Frames and rights (R3).** Build what `R3. Frames and rights` asks for, to the numbers in `design.md`. In particular: Frames: the QR image, the boot title, the corridor at spawn, and the view at the pickup step. Check: the `R3. Frames and rights` acceptance checks pass. 5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in `design.md`. In particular: One command packs, decodes, walks, scans, and writes the frames. No network. No camera. 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.