Rewrites the internal/db/queries comments to rule 32 and regenerates
dbq, whose doc comments and embedded SQL carry them. The bugs behind the
tiered mixes, the md5 order seed, the score bands and the round-robin
arms are restated as the constraint each one enforces; counts from one
library and stale cross-references are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The operator's library had 536 groups waiting for review, 2026-10-19. A sample
showed most were one recording under two titles on two releases.
- The headline and the Duplicates count leave out cross-release groups, which
the resolver keeps and links: the headline read 3,479 when 536 needed review.
- Any group spanning albums is cross_release and is linked as one song,
whatever its titles say. Nothing is deleted.
- One album, two versions named as such ("Lovesick (Instrumental)") and not
byte-identical: a new class, distinct, dismissed by the resolver.
- One album, one recording under different song titles (mismatch): the
album's cached MusicBrainz track list decides. When exactly one slot's song
is as long as the file and every other slot's song is clearly not, the other
copies are removed and their tracks marked missing, so the reacquisition
sweeper wants the album back. Otherwise the group stays for review.
- The duplicates_found notice moves from the sweep to the resolver: it names
only groups a pass first left for review.
- Resolved automatically lists dismissals and wrong-slot removals beside
merges.
Migration 0094 adds 'distinct' to the class CHECK (rule 36).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Migration 0091 drops lidarr_config and renames the quarantine tables, types,
indexes and the history column off the Lidarr name. The Integrations Lidarr
card, the Reports "Delete via Lidarr" action, the merge and remove-track
unmonitor options, the Lidarr audit actions and error codes go, on the
server, web and Android. The README describes acquisition as it is now.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /admin/reports folds the quarantine queue and the unresolved playback
errors into one row per track, newest first: who flagged it and why,
what failed and for whom, the file, with Resolve (clears the reports and
marks the errors fixed), Play, Copy details, Delete file and, for an album
Lidarr holds, Delete via Lidarr.
- One delete path: Delete file removes the track, and its reports and
errors go with the row.
- A Handled tab shows what was done: reports cleared, files deleted,
errors marked fixed or ignored.
- The summary counts reports by track across both sources, so the rail,
the Overview and the page agree.
- /admin/quarantine and /admin/playback-errors redirect to Reports: the
notifications and the Android app link to them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- GET /api/admin/summary: every admin queue (requests, reported tracks,
playback errors, duplicates, suspect sources, missing files) with its
count and the age of its oldest item, in one query.
- The admin layout drops the 11-tab strip for SectionRail, as Settings and
the Collection have, with each queue's count as its badge; the counts
refresh on each admin navigation and every 30s.
- The Overview leads with "Nothing needs you." or "N things need you.",
lists each waiting queue with "oldest 3d ago" and a link to it, counts a
failed library scan as a problem, and names the empty queues on one line.
The request and quarantine previews and the stat tiles are gone; those
queues are worked on their own pages. A failed summary says so with Try
again instead of reading as all-clear.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bvandeusenandClaude Opus 5.5