diskern scan <dir> prints the file count, the total, and the top 10 duplicate sets — and that's it. report.findings is only ever used for its .len().
So the part of the report that says what a file is and why it's safe, which is the whole point of the rules engine, is invisible unless you pass --json and read it yourself.
Something like the app's grouping would do: findings by verdict, then by category, with the matched rule as the reason. Worth having a --top N or --verdict safe filter so it stays readable on a big scan.
crates/diskern-cli/src/main.rs:47
diskern scan <dir>prints the file count, the total, and the top 10 duplicate sets — and that's it.report.findingsis only ever used for its.len().So the part of the report that says what a file is and why it's safe, which is the whole point of the rules engine, is invisible unless you pass
--jsonand read it yourself.Something like the app's grouping would do: findings by verdict, then by category, with the matched rule as the reason. Worth having a
--top Nor--verdict safefilter so it stays readable on a big scan.crates/diskern-cli/src/main.rs:47