krino.git/cmd/krino, branch mainrule-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=main2026-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
the directory lock is the kernel's, not a pid we believe2026-09-17T11:34:20ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:34:20Zurn:sha1:6971543d4749574d4ca575c4e8acf04f9e86d6bb
flock(2) on the lock file's descriptor replaces "write my pid, and
decide whether the pid in the file is still alive". The kernel drops
the lock when the process ends, however it ends, so there is no stale
krino lock to detect and no takeover to race over.
What that fixes:
- Two runs that both judged a lock stale could remove and recreate it
and both believe they held it. Remove-then-create cannot be made
atomic; there is nothing to make atomic now. Pinned by a test with
eight callers over twenty rounds.
- A pid reused after a crash made the lock live for ever, and the
message named neither the file nor the pid, so there was nothing to
act on. The message now names both.
- Signal(0) reads EPERM as "not running", so a lock held by another
user was taken over. There is no such judgement left to get wrong.
A run that waits for a held lock now says so first. Waiting is what
the spec asks for, but the wait has no timeout, and in silence it is
indistinguishable from a hang - I spent two minutes on one myself
today, waiting on a lock the window was holding.
Tests that faked a held lock by writing a file now hold a real one.
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:d6a280d87a274abc8d9cab9956d2af1c845f83d1an undecided (stop) rule ends the search for that file2026-09-15T20:11:33ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:11:33Zurn:sha1:77a015b96db8727bb12d0869f180a44d087f6319only where an earlier directory's files ended up stays claimed2026-09-14T22:41:00ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:41:00Zurn:sha1:2e812847572839e6c8097a7ecf5c4a469222087areview and undo headings wrap past the label column; format characters take a column2026-09-14T22:29:09ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:29:09Zurn:sha1:17e933a16ff7de1b06d62504e78c40e615c8b553