The GitHub copy of the repository already shows the same description and topics as the Gitea repository. This project did not set them; in the day-20 repository a workflow on the git host does, so no task is added. The Version History gets a row, accepted by S01 in chat.
The Status block now says the game is finished and checked against the day-21 lectures, and a table shows where each lesson lives in the code (inheritance, collisions with the food, the scoreboard, the wall, the tail and slicing). No source file changes: the comparison with the lectures found no difference.
Task: MIL-003#7
Closes#21
The Status, Run and Project layout sections now describe python -m snake_game, the keys, the food, the score and the game-over rules, taken from the base README. MIL-003 finishes the README for the whole game.
Task: MIL-002#6
Closes#13
Copied unchanged from the base: screen set-up, key bindings, the animation loop with game_is_on, the eating check, the game-over check, the wait for a click and the quiet exit when the window is closed. main imports food and scoreboard only when it runs, so importing it needs neither turtle nor tkinter.
Task: MIL-002#5
Closes#12
Copied unchanged from the base: class Scoreboard(Turtle) with update_scoreboard, increase_score and game_over. MIL-003 checks the values against the day-21 lectures.
Task: MIL-002#4
Closes#11
Copied unchanged from the base: class Food(Turtle) with refresh, and one random_coordinate function that the tests replace. MIL-003 checks the values against the day-21 lectures.
Task: MIL-002#3
Closes#10
Copied unchanged from the base: create_snake, add_segment, extend, move, hits_wall, hits_tail, up, down, left and right, with the segments list and the head. The tail check loops over the slice segments[1:]. snake.py does not import turtle until a real segment is made.
Task: MIL-002#2
Closes#9
Copied unchanged from the base (020-snake-game, commit 1a638c9): the fake segment, the fake screen and the fake Turtle base class that record their calls, so every test runs without a display. The fake turtle module is installed with monkeypatch, so it is undone after each test.
Task: MIL-002#1
Closes#8
Python code reviewed against QC-PY-001 with the verdict Go. The repository description and topics (task 7) have no file in the repository; they were set on the git host on 2026-10-08.
Task: MIL-001#7
Closes#7
Identical to the base: Gitea Actions installs .[dev] on Python 3.13 and runs pytest, ruff (lint and format check) and mypy. It lives in .gitea/workflows, not .github/workflows, so the push mirror to GitHub needs no workflow scope.
Task: MIL-001#6
Closes#6
Follows the Product Owner's template, with the .venv set-up for Windows PowerShell, Linux Debian and macOS. It describes only what exists at this milestone; the Run section is completed when the game is added in MIL-002 and finished in MIL-003.
Task: MIL-001#4
Closes#4
Copied from the base with identity-only edits: the docstrings name days 20 and 21, and the package main page describes the whole game. The values are unchanged; MIL-003 checks them against the day-21 lectures.
Task: MIL-001#3
Closes#3
Adopted from the base (020-snake-game): requires-python >=3.13, no runtime dependencies, a dev extra with pytest, ruff and mypy. Only the description (day 21) and the repository URL differ from the base.
Task: MIL-001#1
Closes#1
Adds the Business Case, Stakeholder Analysis, Domain Dictionary, Project Plan and milestones MIL-001 to MIL-003, with the review records RC-001 to RC-006 (all Go). The repository starts from the finished main of 020-snake-game, as S01 decided on 2026-10-08. The milestones and their 22 issues were synced to the git host.
Tirsvad