chore: comments say what the code does, not which task produced it

A comment that reads "MUST stay in lockstep with TryGetActiveCrossfade (K8)"
helps nobody outside the plan that used to have a K8 in it, and the plans are
not in this repo. Same for "Spec FR-4", "plan §B.2", "Sub-Task 4.4" and the
F/R/M/A/S round codes scattered through the style engine and the self-tests.

Personal names go too. "tester feedback from Jin (v1.4.7)" and "Flo decision
2026-06-15" carry the reason fine without naming anyone -- the version and the
reason are the parts a reader can act on, and a public repo should not need a
cast list to be read.

The rule applied throughout: keep the why, drop the reference. Version numbers
stay, since those resolve through the changelog. 77 files.

ChunkUtil also carried 281 lines of commented-out code -- an older ToChunks
variant and two helpers with no callers, inherited and never removed. Deleted;
git remembers them.
This commit is contained in:
2026-08-19 21:50:31 +02:00
parent 52237fda7e
commit 5b738e6885
48 changed files with 113 additions and 397 deletions
+1 -1
View File
@@ -54,7 +54,7 @@ internal sealed class InputPreview : Window
DisableWindowSounds = true;
IsOpen = true;
// TODO Polish-Sweep: remove discard once logging call-sites exist
// TODO: remove discard once logging call sites exist
_ = _logger;
}