summaryrefslogtreecommitdiff
path: root/internal/engine/session_test.go
Commit message (Collapse)AuthorAgeFilesLines
* {now} is the start of the run, as the spec always saidLukasz Kasprzak2 days1-0/+53
| | | | | | | | | | | | | The clock was read once per directory, so a run of several directories stamped several different times - and a review that took a few seconds could put one run's files into two folders, or at midnight two dates. The spec (§7.3) says "the start of the run"; krino.conf(5) documented the behaviour rather than the intent, so the two contradicted each other. The session now carries the run's clock and every directory plans with it. Engine.Plan keeps its meaning for a caller with no session of its own; Session.Plan passes the run's own start.
* comments that explain the code, not how it was writtenLukasz Kasprzak2 days1-2/+2
| | | | | | | | | | | | | | | | | | About 340 comments cited the development process: task and plan numbers, fix waves, rulings, reviewers, and the author in the third person with a date. None of that exists outside the work itself, so to a reader it pointed at nothing. Each one now states the engineering reason it was standing in front of; where a comment was provenance and nothing else, it is gone. References to docs/design.md and docs/gui-design.md by section stay: both ship with the repository. The design documents lose their amendment diaries - CHANGELOG.md is that record - and the GUI's says plainly that the window has gone further than the document. Only comments changed. Every .go file was parsed and its code printed with comments stripped, before and after: the two hashes are identical across all 175 files.
* milestone 1 review: claims span the run, explain's chain is opt-in and its ↵Lukasz Kasprzak4 days1-0/+90
| | | | own, overrides keyed by clean path, splice and enum guards
* undo runs through the same sessionLukasz Kasprzak4 days1-0/+63
|
* the engine owns a run: lock, log, run id, claimsLukasz Kasprzak4 days1-0/+119