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

diff --git a/cmd/krino/render_test.go b/cmd/krino/render_test.go
index 1b2f8cc..7c2072e 100644
--- a/cmd/krino/render_test.go
+++ b/cmd/krino/render_test.go
@@ -31,7 +31,7 @@ import (
 //
 // "excluded.txt" matched a rule with no actions (an exclusion, spec §4.5):
 // it has zero steps, so it must not appear in the table and must not
-// inflate "to act on" (ruling 2026-09-12).
+// inflate "to act on".
 func TestPrintPlan(t *testing.T) {
 	h := home(t)
 	root := filepath.Join(h, "downloads")
@@ -78,7 +78,7 @@ func TestPrintPlan(t *testing.T) {
 	dp := &engine.DirPlan{
 		Dir:     &engine.Dir{Name: "downloads", Root: root},
 		Chains:  []plan.Chain{scan001, fv123, setup, excluded},
-		Elapsed: 420 * time.Millisecond, // D12: the counts line renders DirPlan.Elapsed (Match plus Build), not Result.Elapsed alone
+		Elapsed: 420 * time.Millisecond, // the counts line renders DirPlan.Elapsed (Match plus Build), not Result.Elapsed alone
 		Result: &engine.Result{
 			Matched: []engine.FileMatch{
 				{File: scan.File{Rel: "scan001.pdf"}, Warnings: []string{"acme: content unreadable: needs pdftotext, not installed"}},
@@ -380,7 +380,7 @@ func TestSkipSummaryLineAccountsForEveryFile(t *testing.T) {
 
 // TestWrappedNameCannotFakeAStepLine: a long name's continuation lines start
 // at the value column, not at the column step labels use, so a name holding
-// "rename  → x" cannot pass for a step of its own block (triage 28l).
+// "rename  → x" cannot pass for a step of its own block.
 func TestWrappedNameCannotFakeAStepLine(t *testing.T) {
 	home(t)
 	name := strings.Repeat("a", 30) + " rename  → evil.pdf"
@@ -401,7 +401,7 @@ func TestWrappedNameCannotFakeAStepLine(t *testing.T) {
 // TestColumnsCountWideAndCombiningCharacters: widths and wrapping count
 // terminal columns - two for a CJK character, none for a combining mark -
 // so a name in a wide script neither overruns the terminal nor misaligns
-// its column (triage 28j).
+// its column.
 func TestColumnsCountWideAndCombiningCharacters(t *testing.T) {
 	if n := cols("漢字"); n != 4 {
 		t.Errorf("cols(漢字) = %d, want 4", n)
@@ -411,7 +411,7 @@ func TestColumnsCountWideAndCombiningCharacters(t *testing.T) {
 	}
 	// A format character is counted as one column: a terminal may draw it
 	// (a soft hyphen), and counting one too many only wraps a line early,
-	// while one too few lets it run past the edge (plan 11 review L4).
+	// while one too few lets it run past the edge.
 	if n := cols("a\u00adb"); n != 3 {
 		t.Errorf("cols(a + soft hyphen + b) = %d, want 3", n)
 	}