6 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	3a16732883	feat: Minstrel no longer talks to Lidarr: its connection, Delete via Lidarr and the unmonitor options are gone, and the track reports are plain quarantine (M502 #5525) ... 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>	2026-10-11 13:48:20 -04:00
bvandeusenandClaude Opus 5.5	069baeb14d	feat(notifications): requests and flags reach the people who act on them (#5340) ... - A new request still pending after any auto-approval notifies the admins (request_pending), but not the requester if they are an admin. A request that dedups into one already in flight is not announced again. - Approving or rejecting a request notifies the requester, and a rejection carries the admin's notes as the reason. An admin deciding their own request gets nothing. - The reconciler notifies the requester when their request arrives (request_completed), linking the matched album or artist. - A request the re-acquisition sweeper files and cannot approve itself notifies the admins. - A quarantine flag notifies every admin except the flagger, naming the track, the flagger and the reason. lidarrrequests.Service.CreateTracked reports whether a request was inserted or deduped; Create wraps it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 07:17:11 -04:00
bvandeusenandClaude Opus 4.7	ee7f0cdb42	feat(#392): publish quarantine + playlist mutation events ... Slice 3a — extends the producer set onto the SSE bus. quarantine events (5 producer sites): - quarantine.flagged (user-side flag): broadcast so the flagger's other clients invalidate their Hidden tab and admins' clients invalidate their queue. - quarantine.unflagged (user-side unflag): scoped to the user. - quarantine.resolved / .file_deleted / .deleted_via_lidarr (admin actions): broadcast because a single admin action can affect every user who'd flagged that track. playlist events (6 producer sites): - playlist.created / .updated / .deleted: owner-scoped. - playlist.tracks_changed: emitted for AppendTracks / RemoveTrack / Reorder. Owner-scoped. Single kind for all three mutations because the client invalidation logic is identical (refetch the detail). Public-playlist subscribers (other users viewing someone else's public playlist) intentionally left out — needs a separate broadcast kind, not exercised yet at single-household scale. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 21:28:05 -04:00
bvandeusen	dde3dd2804	refactor(server/api): migrate requests/quarantine/me_token/listenbrainz/admin_invites preludes (A2 3/N)	2026-05-08 08:26:43 -04:00
bvandeusen	754a7955cc	refactor(server): final writeErr migration + ErrNotFound aliases (T3c)	2026-05-07 21:19:35 -04:00
bvandeusen	6fedd495be	feat(api): /api/quarantine user + admin endpoints + Service wiring ... User-facing /api/quarantine handlers (POST flag, DELETE unflag, GET mine) plus the five /api/admin/quarantine endpoints (queue, resolve, delete-file, delete-via-lidarr, actions). Mount() and the handlers struct now accept the lidarrquarantine.Service, constructed in server.go alongside the existing lidarrrequests wiring.	2026-04-30 20:19:39 -04:00