krino.git/internal/engine/session.go, branch v0.0.12rule-based file sorter in Go, shows the plan before touching anything, applies only the files you choose, and can undo any run, with s-expression rules and a GTK 4 windowhttps://git.labunix.xyz/krino.git/atom?h=v0.0.122026-09-17T12:03:44Z{now} is the start of the run, as the spec always said2026-09-17T12:03:44ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:03:44Zurn:sha1:33d771438f1da363af7c9ff2d5f4c368c326e84d
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.
the module path is git.labunix.xyz/krino2026-09-17T10:54:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:54:06Zurn:sha1:1884d56b0d399e9cdb80016a9c166b0120989933
So that go install can find it. cgit serves no go-import meta tag, so
nginx answers a ?go-get=1 request for /NAME with one pointing at
https://git.labunix.xyz/NAME.git; the alternative was carrying a .git
suffix through every import line forever.
One sed over the imports, both go.mod files, and the dependency gate's
whitelist. Nothing else depends on the path. go install works from the
next tag, the first release whose go.mod carries it.
comments that explain the code, not how it was written2026-09-17T10:11:42ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:11:42Zurn:sha1:bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd
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 own, overrides keyed by clean path, splice and enum guards2026-09-15T23:34:45ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T23:34:45Zurn:sha1:ecfaeabf2a92e26c6a521d5fac404a0fff6263b6undo runs through the same session2026-09-15T22:59:08ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T22:59:08Zurn:sha1:40ecbfae85c4c76a8ed944a91f8c000b4ec55fc5the engine owns a run: lock, log, run id, claims2026-09-15T22:57:03ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T22:57:03Zurn:sha1:d6a280d87a274abc8d9cab9956d2af1c845f83d1