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, 3 insertions, 3 deletions

diff --git a/internal/plan/chain_test.go b/internal/plan/chain_test.go
index 28c208f..0c89987 100644
--- a/internal/plan/chain_test.go
+++ b/internal/plan/chain_test.go
@@ -118,9 +118,9 @@ func TestBuildRenameWithSlash(t *testing.T) {
 	}
 }
 
-// TestBuildKeepsSteplessChains is D6: Build returns one Chain per Input even
-// when a file's rules contribute no actions, so a caller can tell "matched a
-// rule that does nothing" (an exclusion) from "not matched at all". Plan 3's
+// TestBuildKeepsSteplessChains: Build returns one Chain per Input even
+// when a file's rules contribute no actions, so a caller can tell "matched
+// a rule that does nothing" (an exclusion) from "not matched at all". The
 // "to act on" count and the JSON document's empty steps array both rest on
 // this.
 func TestBuildKeepsSteplessChains(t *testing.T) {