2 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	7e6228c13f	docs: library comments say what the scanner and resolver do, not how they came to be (#6277) ... Rewrites the internal/library comment blocks to rule 32. Task, milestone, decision and rule ids are gone; the incidents behind them are restated as the constraint they left (why a file is deleted before its row, why the missing mark is a mark, why duplicates block on duration). Counts and album names from one library are dropped from production comments; test comments keep the names their fixtures use. The tagReadVersion log keeps each version's before and after, without the measurements. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-23 12:27:34 -04:00
bvandeusenandClaude Opus 5.5	b9684e6d12	fix: a group of one recording in several slots is settled by getting the album again, not merged (#6184) ... The duplicates review offered only Merge for a wrong-slot group. A merge keeps one copy's title whether or not it is the audio's, and neither sets the release aside nor wants the missing song back. For class mismatch the page now asks which song the recording is. "Get it again" (the operator can't tell) removes every copy; "Keep <title>" keeps that copy and removes the ones under other titles. Either way it runs the resolver's own path: the release the files came from is set aside, the removed copies' tracks stay marked missing and emptied, and the album is wanted again. - library.SettleWrongSlot, POST /api/admin/library/duplicates/{id}/refetch - ListDuplicateGroupsForResolve takes an optional group_id - removeWrongSlots takes the acting operator (manual: not automatic, actor in the audit row) and removes files through removeTrackFileOnDisk, so a read-only library answers library_not_writable Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-21 13:47:43 -04:00