comments that explain the code, not how it was written

About 340 comments cited the development process: task and plan
numbers, fix waves, rulings, reviewers, and the author in the third
person with a date. None of that exists outside the work itself, so to
a reader it pointed at nothing. Each one now states the engineering
reason it was standing in front of; where a comment was provenance and
nothing else, it is gone.

References to docs/design.md and docs/gui-design.md by section stay:
both ship with the repository. The design documents lose their
amendment diaries - CHANGELOG.md is that record - and the GUI's says
plainly that the window has gone further than the document.

Only comments changed. Every .go file was parsed and its code printed
with comments stripped, before and after: the two hashes are identical
across all 175 files.

1 files changed, 1 insertions, 1 deletions

diff --git a/internal/config/enum_test.go b/internal/config/enum_test.go
index 2e5b718..06f5640 100644
--- a/internal/config/enum_test.go
+++ b/internal/config/enum_test.go
@@ -13,7 +13,7 @@ import (
 // with their String(), so every Conflict and CaseMode value must print as
 // the word a configuration uses, and parse back as that same value. A value
 // added later without its branch would otherwise print as "Conflict(3)",
-// which krino check refuses (plan 13 review F5).
+// which krino check refuses.
 func TestEverySettingValuePrintsAsItselfInAConfig(t *testing.T) {
 	for _, c := range []struct {
 		typ, form string