krino.git/internal/engine/undo_identity_test.go, 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-17T10:54:06Zthe 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.
tests: apply error exits 1 and w stops krino through the real command; undo projection occupied half2026-09-14T21:58:43ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:58:43Zurn:sha1:67ada0b5bc25cb6cff3ab780d82cb0bfe64e4968plan 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:c66a842ce4679a3ffa5504dad39b1402bea75e9fplan 10: missing and weak tests (per-step logging, trash path, fuzz oracle, w after error)2026-09-14T20:39:27ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:39:27Zurn:sha1:9e65644f473d75ceb7e3ef67302189eeaba0f922plan 10: resumed undo re-checks what an earlier undo put back; occupied directory removals are not offered forever2026-09-14T20:28:03ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:28:03Zurn:sha1:3315b98bd9bbd71f480280102188c33193d91728plan 10: a damaged log line refuses only its file, not the run2026-09-14T20:26:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:26:23Zurn:sha1:21339a73f5cd592ebd92937a1440aa9f13e75bbbplan 10: a step that ran but could not be logged is named in the error2026-09-14T20:24:38ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:24:38Zurn:sha1:d50f3670bf2ccb843e9001321d072a2d5680cb2aplan 9: an interrupted or failed undo can be finished2026-09-14T19:33:39ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T19:33:39Zurn:sha1:93cf0729ec7cf3129de0808cbcc3403b86d86fffplan 9: undo checks trash identity, groups by directory, re-checks at execution, removes directories it recreates2026-09-14T19:30:49ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T19:30:49Zurn:sha1:643eac4a2cba7b34b8a33af1b3dbdc54d9816a53