krino.git/internal/plan, 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.
the suffix search continues instead of starting again at _12026-09-17T11:50:01ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:50:01Zurn:sha1:78d8313791f05defc9e0a9f2bad8e9710f741a60
Every file renamed onto one name probed stem_1, stem_2, ... from the
beginning, so N files cost N^2/2 Exists calls - a test here counts 1890
of them for 60 files. The search now continues from the highest suffix
already tried for that stem.
Within one plan that is the same answer: the taken set only grows while
a plan is built and the disk is not being written to, so a suffix taken
once stays taken. Proved rather than argued - with same_1 and same_3
already on disk and same_2 free, both versions put a file in the gap,
and the two plans are byte-identical.
1500 files renamed to one name: 2.63s -> 0.05s
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.
check refuses an empty time format; krino.conf(5) corrected from the re-audit2026-09-15T20:32:35ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:32:35Zurn:sha1:8d0a4024b76b7e85c0ccede853fc2cdcceea2afbcheck refuses placeholders that could never expand2026-09-15T20:12:31ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:12:31Zurn:sha1:88cbe4e623eab9adb608566ac636d36eed72e551an earlier directory's applied results stay claimed for later ones2026-09-14T22:26:36ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:26:36Zurn:sha1:f12f3f1356e4e96d419d66d13c2e67b73a50346f--json carries exclusions and matching warnings2026-09-14T21:47:15ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:47:15Zurn:sha1:89c1fcd8fae93a64d304251a35a65763818aa8b1literal braces are text, not placeholders, for containment and walk exclusion2026-09-14T21:45:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:45:23Zurn:sha1:97c8164bc81e0a438dab92d7244485005dac4ff2plan 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:c66a842ce4679a3ffa5504dad39b1402bea75e9f