1 Commits (adbdda7b0eeecaaabce5f5b2fa52c026ff84400a)

Author	SHA1	Message	Date
BoulderBadgeDad	28850672a6	Fix: duplicate detector kept lossy over lossless (rank format first) ... The Duplicate Detector's 'Keep Best' auto-selection ranked copies by highest bitrate -> duration -> track number, with no notion of format. A FLAC whose bitrate the library scan never populated (a common gap) therefore lost to a 282 kbps MP3: 282 > 0, so the MP3 was kept and the FLAC deleted (reported on Havok 'Prepare For Attack', and again on Kendrick GNX). Fix: rank by format/lossless tier FIRST, then bitrate, duration, track number. A lossless file now always beats a lossy one regardless of the recorded bitrate; bitrate/duration/track# only break ties within the same format. - core/library/duplicate_keep.py (new): pure, importable pick_duplicate_to_keep + duplicate_keep_sort_key + format_rank_for_path (extension rank mirroring auto_import_worker._quality_rank: flac=10 ... mp3=5 ... unknown=1). - core/repair_worker.py: _fix_duplicates auto-pick now calls pick_duplicate_to_keep instead of the bitrate-first max(). - webui/static/enrichment.js: the KEEP/REMOVE recommendation mirrors the same format-first ranking so the badge matches what the backend will delete. Parity: Python uses '.ext' keys (os.path.splitext), JS uses 'ext' (split('.').pop()) -> identical results; both keep the first copy on a full tie. Verified the only other dedup path (the standalone Duplicate Cleaner automation, core/library/duplicate_cleaner.py) was already format-priority-first and correct -- no change needed there. Tests: tests/test_duplicate_keep.py (11 -- incl. the exact FLAC-with-missing- bitrate vs 282 kbps MP3 case, format ranking, within-format tie-breakers, and edge cases). 147 repair/duplicate tests still pass. Note: why FLAC bitrate is NULL in the DB is a separate library-scan gap; format-first ranking makes the keep decision correct regardless.	3 weeks ago