5 Commits

Include renames

Author	SHA1	Message	Date
bvandeusen	c3f3a17c6d	feat(library): a missing file stays in the playlist, greyed and unplayable — #2527 ... Every browse, discover and mix query filters missing_since, so a track whose file vanished disappears from the places Minstrel chooses music. A playlist is different: the entry is there because the user put it there, and silently dropping it rewrites their list behind their back. So playlists keep the row and mark it instead. ListPlaylistTracks now carries missing_since (still deliberately unfiltered), the service layer surfaces it as PlaylistTrack.Unavailable, and the wire gains "unavailable" on each entry. A missing entry also loses its stream_url. Refusing to hand out a URL that cannot serve is stronger than trusting every client to honour the flag, and "stream_url": null is a shape the clients already model -- PlaylistWire.streamUrl is documented nullable for the track-removed case -- so an older build degrades to "present but not playable" with no change. Nothing is deleted here and nothing should be: the row, its play history, its likes and its taste contribution all survive a file going missing, because the file may come back (and #2528 will adopt it if it comes back renamed). Also corrects two comments that had drifted into lying. delete.go still claimed the file-gone case was NOT auto-reconciled and told admins to delete rows by hand -- untrue since f6d1cf24, and that exact staleness is what produced drift #572. It now says what DeleteTrackFile really is: the destructive admin action, which CASCADEs play_events and likes, and is emphatically not the missing-file path. watcher.go claimed the safety-net scan "covers anything missed"; the walk only covers additions, and it is reconcile that covers removals.	2026-08-16 11:43:05 -04:00
bvandeusenandClaude Fable 5	fb4431207d	feat(recommendation): For You exploration attribution — taste vs fresh picks ... Milestone #127 step 2 (#1249). For You deliberately blends two populations — a head of top-scored taste picks and a tail sampled from deeper ranking (the freshness injection) — but the metrics judged it as one blob, so its skip rate couldn't distinguish "the taste engine is missing" from "the freshness tax is too high". That number decides the exploration share before we tune it. - Migration 0038: nullable pick_kind ('taste'|'fresh') on both playlist_tracks (stamped at snapshot build) and play_events (frozen at play-ingestion — the snapshot rebuilds daily, so attribution cannot be reconstructed at read time). - Builder: pickHeadAndTail marks head=taste / tail=fresh; the small-pool fallback is all taste (top-N-by-score IS the taste mechanism). Other variants persist NULL. - Ingestion: for_you plays (live + offline replay) look the track up in the user's current snapshot; not found → unattributed, never guessed. - Metrics: For You's row gains a breakdown (taste / fresh / earlier unattributed plays), parent row stays the sum; web card renders the sub-rows indented with the same baseline deltas + low-data dimming. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TsF3cNoKrqCYsU78cXC8U6	2026-07-02 20:39:41 -04:00
bvandeusenandClaude Opus 4.7	9bf4b504b3	feat(server): GET /api/library/sync endpoint ... Returns batched upserts + deletes since the supplied cursor. Empty cursor returns full snapshot; subsequent calls pull deltas. Per-user entities (likes, playlists) are scoped to the authed user. Composite-key entities (likes, playlist_tracks) use stable string ids encoded by sync.EncodeLikeID / sync.EncodePlaylistTrackID. Behavior: 204 No Content - no changes since cursor 200 OK - JSON syncResponse {cursor, upserts, deletes} 410 Gone - cursor older than oldest log row; client must reset 401 / 500 - standard envelope errors Adds sqlc queries GetAlbumsByIDs, GetTracksByIDs, GetPlaylistsByIDs to mirror the existing GetArtistsByIDs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-09 22:36:26 -04:00
bvandeusenandClaude Sonnet 4.6	3fe929cebd	feat(db/m7-352): sqlc queries for system playlist runs + seed selection ... Adds internal/db/queries/system_playlists.sql with 12 named queries covering active-user enumeration, per-user run tracking (claim/finish/fail), seed-artist/track/cover selection, and playlist CRUD by kind. Runs sqlc generate to emit dbq/system_playlists.sql.go; also updates playlists.sql.go and models.go to reflect the new kind/system_variant/ seed_artist_id columns added in migration 0015. Note: plan specified a.cover_path for PickTopAlbumCoverForArtistByUser but albums uses cover_art_path — corrected in the query file. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-04 08:14:20 -04:00
bvandeusen	1226cb7583	feat(db): playlists schema for M7 #352 slice 1 ... Migration 0014 adds playlists + playlist_tracks. track_id is nullable with ON DELETE SET NULL — tracks can be removed from the library without silently dropping playlist entries; the denormalized snapshot (title/artist/album/duration) keeps the row legible afterwards. UI renders such rows greyed-out. Indexes: playlists by (user_id, updated_at DESC) and a partial public index for cross-user discovery; playlist_tracks partial index on track_id to support the FK SET NULL lookup. Queries provide CRUD + rollup recompute (track_count, duration_sec) + append/remove primitives. Reorder is service-layer orchestrated via raw tx.Exec; no SQL primitive needed.	2026-05-03 10:03:36 -04:00