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/server/release_version_test.go

@@ -10,17 +10,10 @@ import (
 	"testing"
 )
 
-// Guards the version derivation that stamps every build.
-//
-// These assertions used to be impossible to run. The derivation lived inline
-// in release.yml, which triggers only on `main` and on tags — so a mistake in
-// it could not surface until a release was already under way, and its failure
-// mode is silence: a version nobody can compare looks exactly like being up to
-// date, and nobody reports an update they were never offered.
-//
-// Moving it to ci/version.sh made it executable, so this runs on every push
-// that touches the release machinery. That is the whole point of the file; the
-// specific assertions below matter less than the fact that they run at all.
+// Guards the version derivation that stamps every build, in ci/version.sh.
+// Its failure mode is silence: a version nobody can compare looks exactly
+// like being up to date, and nobody reports an update they were never
+// offered. Keeping it in a script lets these tests run it on every push.
 //
 // The tests EXECUTE the script rather than asserting on its text, so they
 // break when the behaviour changes rather than when the wording does.
@@ -188,8 +181,7 @@ var jobBoundary = regexp.MustCompile(`\n\n  [^ \n]`)
 //
 // The naive cut — "up to the next `- name:`" — silently returns an EMPTY body
 // for the last step in a job, and every assertion over it then passes
-// vacuously. That is the failure rule 167 names: a check that reads as
-// coverage while asserting on nothing. Cutting at a blank line followed by
+// vacuously: a check that reads as coverage while asserting on nothing. Cutting at a blank line followed by
 // job-level indentation handles the last-step case, which is exactly where
 // `Build and push` sits.
 func stepBody(t *testing.T, yaml, name string) string {
@@ -274,7 +266,7 @@ func TestDevChannel_PublishesDevAloneAndNeverLatest(t *testing.T) {
 	if strings.Contains(arm, ":latest") {
 		t.Errorf("dev arm moves :latest — that ships dev code to every stable operator\n%s", arm)
 	}
-	// Rule 145: a rolling channel gets no commit-addressable tag.
+	// A rolling channel gets no commit-addressable tag.
 	if strings.Contains(arm, "GITHUB_SHA") {
 		t.Errorf("dev arm publishes a per-commit tag; a rolling channel should not\n%s", arm)
 	}
@@ -367,21 +359,19 @@ func TestMainChannel_PublishesLatestAndTheRollbackUnit(t *testing.T) {
 	if !strings.Contains(arm, "${IMAGE}:${GITHUB_SHA}") {
 		t.Errorf("main arm publishes no commit-addressable image; there is no rollback target for production commits\n%s", arm)
 	}
-	// Rule 147: :latest tracks main's tip, and a second name for the same
+	// :latest tracks main's tip, and a second name for the same
 	// image sends readers looking for a distinction that does not exist.
 	if strings.Contains(arm, "${IMAGE}:main") {
 		t.Errorf("main arm publishes :main — rule 147 says that tag should not exist\n%s", arm)
 	}
 }
 
-// A release refreshes the CHANNEL and mints nothing else (rules 145 + 146).
+// A release refreshes the CHANNEL and mints nothing else.
 //
-// The specific regression: re-adding :<sha> here. The tag build rebuilds the
-// SAME SOURCE as main's build minutes earlier, differing only in which APK is
-// baked in — so a :<sha> minted here would overwrite main's immutable rollback
-// target with different contents, under the same name. That is the exact thing
-// rule 145's immutability clause exists to prevent, and it is the half with
-// the incidents behind it.
+// The regression to guard: a :<sha> tag here. The tag build rebuilds the SAME
+// SOURCE as main's build minutes earlier, differing only in which APK is baked
+// in — so a :<sha> minted here would overwrite main's immutable rollback
+// target with different contents, under the same name.
 func TestReleaseBuild_RefreshesTheChannelAndMintsNothingElse(t *testing.T) {
 	arm, _, _ := imageTagArms(t, releaseYAML(t))
 
@@ -393,8 +383,8 @@ func TestReleaseBuild_RefreshesTheChannelAndMintsNothingElse(t *testing.T) {
 	}
 }
 
-// No version-numbered image tags anywhere, on any arm (rule 145, and the
-// operator's 2026-09-10 decision to drop them across every project).
+// No version-numbered image tags anywhere, on any arm: the build's version is
+// self-reported, and the tag map is :latest, :<sha> and :dev.
 //
 // Asserted across the whole step rather than per-arm because the mistake this
 // catches is re-adding one ANYWHERE, and the tag arm is only the likeliest
@@ -441,9 +431,9 @@ func TestVerifyJob_ChecksTheRollbackImageNotAVersionTag(t *testing.T) {
 	}
 }
 
-// The server's self-reported version is now the ONLY thing that identifies a
+// The server's self-reported version is the ONLY thing that identifies a
 // build, so a lane that stamps a channel word instead of a version silently
-// removes that ability. It used to stamp the literal "main"/"dev".
+// removes that ability.
 func TestImageBuild_StampsADerivedVersionAndAChannel(t *testing.T) {
 	yaml := releaseYAML(t)