2 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	fcf5b7e5a8	docs: wanted, dbtest, recommendation and playlists comments say what the code does (#6277) ... The same rewrite as d191a282, for four packages whose comments carried the most history: tuning stories, quotes from the operator, single-install measurements in library_scale.go, and 'used to' accounts of bugs. The constraint each story protected stays as a present-tense reason (why tier 3 is reduced not removed, why the randomised arms take an order seed, why the seed artist is eligible in Songs-like). Comments naming system_cron.go and config.RecommendationConfig, neither of which holds what they claimed, now name the scheduler and internal/recsettings. Checked: non-comment tokens identical to HEAD; gofmt clean. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-23 12:19:15 -04:00
bvandeusenandClaude Opus 5.5	9be5bbae3c	fix(discover): cap the taste-matched arm per album and artist before its LIMIT (#5356) ... Summed tag weight rewards a track for carrying many of the user's tags, so on the deploy two artists whose every track carries the whole lo-fi profile took all 120 rows of the taste-unheard query. capByAlbumAndArtist ran after the LIMIT and left 6, and the arm with the lowest skip rate (12% against ~23%) handed its slots to dormant and random. The query now ranks within album, then within artist over what the album cap kept, before the LIMIT: the same walk the Go cap makes, so the bucket fills from as many artists as match. The caps come from the Go constants. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 09:24:20 -04:00