rule-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 window https://git.labunix.xyz/krino.git/atom?h=v0.0.12 2026-09-17T11:58:25Z 2026-09-17T11:58:25Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T11:58:25Z urn: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 2026-09-17T10:54:06Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T10:54:06Z urn: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. 2026-09-17T10:11:42Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T10:11:42Z urn: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. 2026-09-16T07:39:59Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-16T07:39:59Z urn:sha1:6ef83d6bdfb6120f9e1fbd145e0bc463196103d1 2026-09-14T19:30:49Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-14T19:30:49Z urn:sha1:643eac4a2cba7b34b8a33af1b3dbdc54d9816a53 2026-09-13T00:31:32Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-13T00:31:32Z urn:sha1:26c94eb3db62ec6eebbf8d22c11afe691d9520c4 Also: undo removes the directories its run created; a hardlink is never a duplicate of its own other name; a flag written before "undo" is honoured; --version prints no leading v. Duplicate conditions with different scopes not sharing an original is documented as a known limitation. 2026-09-12T18:14:47Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-12T18:14:47Z urn:sha1:3f8679be9373ee7508d512dfdfc1dda0839c7f90