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-17T12:29:01Z 2026-09-17T12:29:01Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T12:29:01Z urn:sha1:9ff1297471a483bad1b2b38ccb1e42614f60fc5e 2026-09-17T12:02:24Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T12:02:24Z urn:sha1:a65e8a0587d3e5c971bef3062dd0d8a3b5cb53b7 Placeholders were already stopped from sending a file out of the directory a rule named. A symlink is a name too, and the directory krino sorts is by the threat model's own premise a place the internet writes into: a link named after a rule's destination sent moves and copies anywhere, and under (on-conflict overwrite) trashed a file OUTSIDE the sorted directory - while the plan showed the in-tree text and the run reported success. A step whose destination passes through a symlink at or below the directory being sorted now fails. A destination the configuration names outside it - ~/docs on another disk - is the user's own arrangement and is followed as before; both cases have a test. End to end, the review's scenario (Out -> ~/secret, overwrite): before: 1 applied, the user's file replaced and trashed after: 0 applied 1 failed, the file untouched, nothing trashed Two bookkeeping bugs in MkdirAllTracked went with it: a dangling symlink read as a missing directory and was then recorded as one krino had created - undo would have unlinked a link krino never made - and a directory created by someone else between the check and the mkdir was recorded the same way. 2026-09-17T11:59:52Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T11:59:52Z urn:sha1:b44222fc2b061382dc601014cde287cc41b857ca The scopes that drive "no rule deletes a file krino found to be a duplicate" were collected from rules only. A directory whose duplicate tests lived in (exclude ...) forms had no scopes at all, so the protection never engaged: krino explain said "yes duplicate" and the next rule permanently deleted every copy. The README's promise was false in that shape, and the spec's wording permitted it. What matters is what krino knows, not which form taught it. The spec and krino.conf(5) now say so too. 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-17T09:51:49Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T09:51:49Z urn:sha1:cd7425b81f963a948f0abe7df3f9e58e190c2b78 It opened with a paragraph of version history and spent 148 of its 273 lines on a walkthrough. What sells the program is a rules file and the plan it produces, so those come first, with a screenshot of the window above them. Every command and every pasted line was run again in a scratch config: the plan, the apply, the log line and the undo are this morning's real output, and the example rules file passes krino check as written (with the paths pointed at a sandbox). docs/krino-gui.png is from invented files under /tmp/krino-demo. 2026-09-17T09:49:35Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T09:49:35Z urn:sha1:3ff1363446e238a8d7a9fdeb533763fb3f9ec307 Squeezed, the toolbar's path label read "/t... ds". It now elides the start, since the end of a path is the part that says which directory this is, and will not shrink below about sixteen characters; the tooltip still holds it in full. The checklist gains the reordered bar, the About block, and the sandbox trap that had every file skipped: krino's own (min-age 2m) ignores a file written in the last two minutes. 2026-09-17T09:27:00Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T09:27:00Z urn:sha1:0e56395aaa46359974a5eb21acaab32b2ea02a0f Selecting the exclude row in Forms panicked: newFormEditor read the form's rule for its when, name, action and stop, and an exclude has only the when. The editor now takes the conditions from whichever of the two the form holds and leaves out the fields an exclude has not got. Checklist item 49 covers it. Also the 0.0.11 changelog and README, and header floors wide enough that the age heading is not clipped. 2026-09-17T08:56:19Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T08:56:19Z urn:sha1:48d1781fed3f9ea5cfd2b270bd92fd2826605636 2026-09-17T08:15:45Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-17T08:15:45Z urn:sha1:a2cb20851499e9c00bd3bf642680a9ce3148cae8