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
*	krino: no performance target for 0.0.1	Lukasz Kasprzak	8 days	1	-2/+8
\| \| \| \| \| \| \| \| \| \|	Lukasz: "no performance goal". Section 13s "under 2 s on a 4-core laptop" is replaced with the decision and its evidence, so it is not reinstated later: measured throughput is dominated by the external extractors, not by krino. A real folder of 265 files with 164 needing pdftotext at roughly 80 ms each takes 12-17 s; a synthetic 4405-file tree needing no extraction takes 1.09 s. A single threshold would describe popplers speed and the shape of one folder. The measurement is still reported in the release notes; nothing is promised.
*	krino: acting — trash, journal, apply, lock, review, undo	Lukasz Kasprzak	8 days	1	-2/+4
\|
*	krino: planning — chains, placeholders, conflicts, JSON	Lukasz Kasprzak	9 days	1	-1/+12
\|
*	krino: matching — scan, ignore, conditions, extraction, duplicates, ↵	Lukasz Kasprzak	9 days	1	-4/+11
\| \| \| \|	explain, dry run
*	krino: foundation — sexp reader, config language, init/new/check	Lukasz Kasprzak	10 days	2	-0/+926