krino.git/internal/journal/read.go, branch mainrule-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=main2026-09-17T11:58:25Za chain that deletes itself still gives back the file it displaced2026-09-17T11:58:25ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:58:25Zurn:sha1:9ab6686b98499c745024a474a71e3d99b6e14973
(on-conflict overwrite) trashes the file in the way; §7.4 promises undo
restores it. Walking a file's log entries stopped dead at a permanent
delete, so the displace written earlier in the same chain was never
reached: the user's file stayed in the Trash, the refusal named only
the file they did not care about, and krino log called the run undone.
The displaced file is a different file, so it is offered as its own
entry in the undo plan, keyed by its own path - the deleted file stays
refused, since nothing of it can come back, and the copy or move that
preceded the delete stays unreversed too (undoing a copy whose original
was then deleted would destroy the last remaining copy).
The accounting matched: every reversible step of a deleted file was
subtracted, its displace included, so the run read (undone). Only what
genuinely cannot come back is subtracted now.
End to end, the scenario from the review: the only copy of a file is
displaced by an incoming one that is then permanently deleted.
before: archive/ empty, "(undone)", nothing offered
after: archive/a.pdf restored, run reads partly undone
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.
a permanently deleted file's steps do not keep a run partly undone2026-09-14T22:33:47ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:33:47Zurn:sha1:2a7452c3fd83000f239755825f38246f8537b6cckrino log marks a run partly undone while reversible steps remain2026-09-14T22:00:05ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:00:05Zurn:sha1:5310c857d7531986c806404103f118b3c5e364f3plan 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: a damaged log line refuses only its file, not the run2026-09-14T20:26:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:26:23Zurn:sha1:21339a73f5cd592ebd92937a1440aa9f13e75bbbplan 9: an interrupted or failed undo can be finished2026-09-14T19:33:39ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T19:33:39Zurn:sha1:93cf0729ec7cf3129de0808cbcc3403b86d86fffkrino: acting — trash, journal, apply, lock, review, undo2026-09-12T18:14:47ZLukasz Kasprzaklukas@labunix.xyz2026-09-12T18:14:47Zurn:sha1:3f8679be9373ee7508d512dfdfc1dda0839c7f90