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/sync/changes.go

@@ -38,9 +38,9 @@ func LogChange(ctx context.Context, dbtx dbq.DBTX, entityType EntityType, entity
 
 // LogChanges is LogChange for a set of entities of one type sharing one op.
 //
-// Exists because the scan's reconcile pass can mark a quarter of a library
-// missing in a single sweep (#2704), and a per-row loop there would be
-// thousands of round-trips inside an operation that is already slow. Every
+// Exists because the scan's reconcile pass can mark a large part of a library
+// missing in a single sweep, and a per-row loop there would be thousands of
+// round-trips inside an operation that is already slow. Every
 // other caller mutates one entity and should keep using LogChange.
 //
 // A no-op on an empty set, so callers don't have to guard.