Dev log

One entry per work session: what was done, what was checked, what is next

The dev log is the team’s memory. Every time someone works on the project, they add a short post here (a folder under devlog/posts/ with an index.qmd), following the loop the course teaches: what was asked, what the agent or the person produced, how it was verified, and what changed as a result. Entries are dated and tagged by phase so the activities page and the log can be read side by side.