krino.git/docs/design.md, 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:02:24Za symlink in the sorted directory no longer redirects a step2026-09-17T12:02:24ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:02:24Zurn: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.
a duplicate test in an exclude protects like one in a rule2026-09-17T11:59:52ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:59:52Zurn: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.
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.
release notes and version mentions for 0.0.92026-09-15T20:35:09ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:35:09Zurn:sha1:1b39b2683eb820560ba882936d4818af0dcfcec7krino.conf(5): WRITING RULES guide; reference corrected against the code2026-09-15T20:18:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:18:06Zurn:sha1:1a1dc05b5250c6a281736fa6b706f74721f83847docs: make ci passes on OpenBSD and FreeBSD; OpenBSD's go needs GOTOOLCHAIN=auto2026-09-15T07:32:16ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T07:32:16Zurn:sha1:5d77c5b247b6da7a1d49c23b03d5522e398c7d73release notes and version mentions for 0.0.82026-09-14T22:42:58ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:42:58Zurn:sha1:e879f2cb348f9cc4d7bc0b44071fb8b5ccf1361donly where an earlier directory's files ended up stays claimed2026-09-14T22:41:00ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:41:00Zurn:sha1:2e812847572839e6c8097a7ecf5c4a469222087aa permanently deleted file's steps do not keep a run partly undone2026-09-14T22:33:47ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:33:47Zurn:sha1:2a7452c3fd83000f239755825f38246f8537b6cc