krino.git/internal/engine/engine.go, branch main 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=main 2026-09-17T11:59:52Z a duplicate test in an exclude protects like one in a rule 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. the module path is git.labunix.xyz/krino 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. comments that explain the code, not how it was written 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. config and engine can load with unsaved text 2026-09-15T22:53:52Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-15T22:53:52Z urn:sha1:9a77de31dc9759708ce9c2d14ea7c0876c214e71 check refuses placeholders that could never expand 2026-09-15T20:12:31Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-15T20:12:31Z urn:sha1:88cbe4e623eab9adb608566ac636d36eed72e551 main excludes checked with the defaults' case and fold; Latin-1 decoding memory; hardlink election documented 2026-09-14T21:53:54Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-14T21:53:54Z urn:sha1:0b155e8df3205aebf129091b517f4116665a5adc plan 9: content excludes fail closed; krino.conf excludes checked without directories 2026-09-14T19:40:12Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-14T19:40:12Z urn:sha1:360591d6e18d8676a2f86185ed42f46852387f85 krino: 0.0.5 — keyword cache, t and d in review 2026-09-14T13:16:55Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-14T13:16:55Z urn:sha1:0b5d0eb92c5be2f0ddb2fa73990f31e5654e57fe 0.0.4: max-size, exclude forms, --min-age 2026-09-14T12:08:36Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-14T12:08:36Z urn:sha1:1d3f2d1e4c59867024470d3444e12698b7ebb22e krino: duplicates are found, never deleted 2026-09-14T08:56:21Z Lukasz Kasprzak lukas@labunix.xyz 2026-09-14T08:56:21Z urn:sha1:1506c7dcd6032c04c1df6f5785b6dd3dfe4511cc A rule combining (duplicate) with a delete action is refused at load, and a file that is a duplicate under any duplicate scope its directory uses gets no delete step from any rule: the plan shows it skipped and the chain continues. A failed duplicate check blocks the delete too. Tests cover (matched), another rule's own condition, a test evaluation skipped, two scopes and a failed check, each checking every copy is still on disk.