krino.git - 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

	Commit message (Collapse)	Author	Age	Files	Lines
*	comments that explain the code, not how it was written	Lukasz Kasprzak	6 days	1	-9/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	gui: name the other copy of a duplicate, and offer to keep this one instead	Lukasz Kasprzak	6 days	1	-0/+12
\|
*	a rule's duplicate check failure shortens the path too	Lukasz Kasprzak	8 days	1	-8/+30
\|
*	(matched) is unknown after an undecided rule, so a catch-all leaves an ↵	Lukasz Kasprzak	8 days	1	-6/+9
\| \| \| \|	unreadable file alone
*	duplicate warnings share one format	Lukasz Kasprzak	8 days	1	-2/+19
\|
*	content tests are three-valued: unknown when unreadable or read in part	Lukasz Kasprzak	8 days	1	-2/+7
\|
*	plan 10: a format with no text is no match, not unreadable	Lukasz Kasprzak	8 days	1	-1/+8
\|
*	plan 9: keyword cache keys on extension, max-read and Unicode tables, trims ↵	Lukasz Kasprzak	8 days	1	-1/+1
\| \| \| \|	removed keywords
*	krino: 0.0.5 — keyword cache, t and d in reviewv0.0.5	Lukasz Kasprzak	8 days	1	-28/+83
\|
*	krino: 0.0.3 — the plan as one block per file, wrapped, and -Pv0.0.3	Lukasz Kasprzak	9 days	1	-2/+2
\| \| \| \| \| \| \| \|	Each file shows its steps, then the rule and the reason it matched, one field per line; on a terminal every line wraps to its width with continuation lines under their own column, and piped output is never wrapped. Choosing per file shows the same block. -P / --no-pager prints the plan without the pager. A duplicate's original is shown with ~.
*	krino: planning — chains, placeholders, conflicts, JSON	Lukasz Kasprzak	11 days	1	-11/+2
\|
*	krino: matching — scan, ignore, conditions, extraction, duplicates, ↵	Lukasz Kasprzak	11 days	1	-0/+204
	explain, dry run