docs: server comments say what the code does, not how it came to be (#6277)

Comment blocks in cmd/minstrel and 30 smaller internal packages, rewritten
to rule 32's standard with each citation read in context: task, milestone
and rule ids go, and so do the stories they were attached to ("used to",
"Before #N", measurements from one install, quotes, pointers to Fabled
Librarian's records and to docs/superpowers files that are not in the
repo). Where a story wrapped a real constraint, the constraint stays as a
present-tense fact.

Comments that had gone stale are corrected:
- taste.Config: the tuned values are overlaid by internal/recsettings;
  it is no longer "a later follow-up".
- StorageConfig: the data dir holds art, caches and the stream secret,
  not only playlist covers.
- the Subsonic album list and getUser comments describe what they do
  today rather than a milestone that would change it.

Checked: the non-comment token stream of every changed file matches
HEAD, and gofmt -l is empty.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

internal/release/version.go

@@ -5,7 +5,7 @@ import "strings"
 // TitleVersion is the version of a recording a release group's title names
 // in its qualifier: the words in brackets, or after a dash. MusicBrainz
 // does not always type such a group: My Chemical Romance's "Common People
-// (Recorded For BBC Radio 1)" is a plain Single (#5573). Typ is the
+// (Recorded For BBC Radio 1)" is a plain Single. Typ is the
 // MusicBrainz secondary type the version is, or "" for one no type names
 // (an acoustic or instrumental version); Word is the word that said so.
 type TitleVersion struct {