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

diff --git a/internal/apply/apply.go b/internal/apply/apply.go
index a93aad4..d7bf71e 100644
--- a/internal/apply/apply.go
+++ b/internal/apply/apply.go
@@ -52,13 +52,13 @@ func Chain(c plan.Chain) []StepResult {
 // ChainLogged is Chain, calling done with each step's result as soon as
 // that step has run or been skipped, before the next one starts - so a
 // caller that logs from done never has a completed step missing from the
-// log when the process dies mid-chain (review M9). An error from done stops
-// the chain at once and is returned with the results so far.
+// log when the process dies mid-chain. An error from done stops the chain
+// at once and is returned with the results so far.
 //
 // A move or rename that had to take a free name at apply time, because its
 // planned destination was taken since planning, stops the chain too: every
 // later step was planned against the name the file did not get, and must
-// not act on whatever is at that path (review M3).
+// not act on whatever is at that path.
 //
 // Once ctx is cancelled (an interrupt), the step already under way finishes
 // and every later step is skipped as "interrupted": an interrupt stops after
@@ -160,8 +160,8 @@ func runFileStep(step plan.Step) StepResult {
 	var displacedEntry string
 
 	if step.Displaces != "" {
-		// Re-checked at apply time (review M4): only a regular file may be
-		// trashed to make room, never a directory or link put there since.
+		// Re-checked at apply time: only a regular file may be trashed to
+		// make room, never a directory or link put there since.
 		if fi, err := os.Lstat(step.Displaces); err != nil || !fi.Mode().IsRegular() {
 			return StepResult{Step: step, Status: "failed", Detail: "the file to replace is gone or no longer a regular file"}
 		}
@@ -224,8 +224,8 @@ func runFileStep(step plan.Step) StepResult {
 // journal columns describe the file at Dst after the step, and after a
 // trash step the file genuinely lives there, so recording it is more
 // useful than an empty column and stays greppable. It also cannot confuse
-// undo: Task 5's refusal condition for reversing a trash step is "the
-// entry is gone, or Src now exists" — it reads Entry and Src, never Dst.
+// undo: the refusal condition for reversing a trash step is "the entry is
+// gone, or Src now exists" — it reads Entry and Src, never Dst.
 func runTrashStep(step plan.Step) StepResult {
 	entry, err := trash.Put(step.Src)
 	if err != nil {