docs: query comments say what each query selects and why, not how it came to be (#6277)

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>

internal/db/dbq/songs.sql.go

@@ -33,7 +33,7 @@ type LinkTracksAsSongRow struct {
 	Moved   int64
 }
 
-// Song links (M498 #5438): copies of one song on different releases share a
+// Song links: copies of one song on different releases share a
 // song_key (migration 0076).
 // Links the tracks into one song, joining any songs they already belong to.
 // The song keeps the lowest key among them, so linking the same set again
@@ -57,7 +57,7 @@ type ListTrackSongKeysRow struct {
 }
 
 // What the mix writer needs to place a track: its song, and whether it is a
-// video rip held back from the mixes (#5439).
+// video rip held back from the mixes.
 func (q *Queries) ListTrackSongKeys(ctx context.Context, ids []pgtype.UUID) ([]ListTrackSongKeysRow, error) {
 	rows, err := q.db.Query(ctx, listTrackSongKeys, ids)
 	if err != nil {