krino.git/internal/engine/plan.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.
explain reports captures and the chain a file would get2026-09-15T22:55:01ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T22:55:01Zurn:sha1:86e55e31f6905ae997619aa095706674e2ffe623krino: duplicates are found, never deleted2026-09-14T08:56:21ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T08:56:21Zurn:sha1:1506c7dcd6032c04c1df6f5785b6dd3dfe4511cc
A rule combining (duplicate) with a delete action is refused at load, and a
file that is a duplicate under any duplicate scope its directory uses gets no
delete step from any rule: the plan shows it skipped and the chain continues.
A failed duplicate check blocks the delete too. Tests cover (matched), another
rule's own condition, a test evaluation skipped, two scopes and a failed
check, each checking every copy is still on disk.
krino: planning — chains, placeholders, conflicts, JSON2026-09-12T10:58:14ZLukasz Kasprzaklukas@labunix.xyz2026-09-12T10:58:14Zurn:sha1:24a84671ace373ae331fa83a1ff484990f4dff0e