krino.git/internal/engine/apply.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-17T11:58:25Za chain that deletes itself still gives back the file it displaced2026-09-17T11:58:25ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:58:25Zurn:sha1:9ab6686b98499c745024a474a71e3d99b6e14973
(on-conflict overwrite) trashes the file in the way; §7.4 promises undo
restores it. Walking a file's log entries stopped dead at a permanent
delete, so the displace written earlier in the same chain was never
reached: the user's file stayed in the Trash, the refusal named only
the file they did not care about, and krino log called the run undone.
The displaced file is a different file, so it is offered as its own
entry in the undo plan, keyed by its own path - the deleted file stays
refused, since nothing of it can come back, and the copy or move that
preceded the delete stays unreversed too (undoing a copy whose original
was then deleted would destroy the last remaining copy).
The accounting matched: every reversible step of a deleted file was
subtracted, its displace included, so the run read (undone). Only what
genuinely cannot come back is subtracted now.
End to end, the scenario from the review: the only copy of a file is
displaced by an incoming one that is then permanently deleted.
before: archive/ empty, "(undone)", nothing offered
after: archive/a.pdf restored, run reads partly undone
a file trashed to make room is logged the moment it is trashed2026-09-17T11:53:01ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:53:01Zurn:sha1:a80d470cbad7335fd5e534f32d935e5a49aadb24
The displace was carried out first and logged only when the whole step
finished - for a copy or a cross-device move, the entire data transfer
later. A process killed in that window left the user's file in the
Trash with nothing recording it: krino log said "nothing applied" and
undo offered nothing.
It is its own action with its own line (spec §9), so it is now written
the moment trash.Put returns, through a hook ChainLogged calls before
the step that needed the name begins. A displace that cannot be logged
fails the step rather than compounding an unrecorded destructive act
with a second one.
Verified by killing krino -9 mid-copy with 600 MB in flight:
before: krino log "nothing applied", 0 displace lines
after: krino log "1 displaced", 1 displace line
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.
gui: History and undo tab; each plan and undo is its own run2026-09-16T07:39:59ZLukasz Kasprzaklukas@labunix.xyz2026-09-16T07:39:59Zurn:sha1:6ef83d6bdfb6120f9e1fbd145e0bc463196103d1plan 10 re-check: cut run column, damaged undo run, emptied directory cleanup, text turning binary, explain flags, interrupt docs2026-09-14T21:07:57ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:07:57Zurn:sha1:c66a842ce4679a3ffa5504dad39b1402bea75e9fplan 10: an interrupt stops between steps; nohup keeps ignoring hangups2026-09-14T20:29:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:29:06Zurn:sha1:c03a72f1d7b598c1fe8fd01bb1f5bbfbd0256313plan 10: resumed undo re-checks what an earlier undo put back; occupied directory removals are not offered forever2026-09-14T20:28:03ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:28:03Zurn:sha1:3315b98bd9bbd71f480280102188c33193d91728plan 10: a damaged log line refuses only its file, not the run2026-09-14T20:26:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:26:23Zurn:sha1:21339a73f5cd592ebd92937a1440aa9f13e75bbbplan 10: a step that ran but could not be logged is named in the error2026-09-14T20:24:38ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:24:38Zurn:sha1:d50f3670bf2ccb843e9001321d072a2d5680cb2a