gui: name every outcome the manifest can record, in the manifest's own words

From an outside review of #125, and the remark was true and smaller than the
defect. Measured: internal/recipe declares FOUR outcomes - accept, reject,
sanitize, unspecified - and the third step of "How to use it" named two of
them, invented a third word for one of those ("turn it away" for reject) and
left sanitize out altogether. The remark was about the word. The defect was
the list.

It is pitfall 15 in its plainest form: a list copied by hand out of a closed
set, with nothing comparing it to the source. A fifth outcome would have left
that sentence untrue and nothing in the tree would have said so.

Fixed twice over. The sentence names all four with the spelling the manifest
uses - sanitize, not sanitise, because that is the value rather than a
preference in the surrounding prose. And the new guard reads recipe.Outcomes()
from the REGISTRY and asks that every outcome it declares is named on the
screen, so a fifth is caught by being declared. Mutation: sanitize dropped
from the sentence - caught.

guitext_test.go leaves notYetJustified, because the verdict written for the
second remark cites it. That list may only shrink.

The other two remarks are recorded as FALSE in docs/REGRESSION.md, each with
the measurement that settles it rather than with an opinion.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: donislawdev

internal/guard/aboutuse_test.go

@@ -6,6 +6,7 @@ import (
 
 	_ "github.com/donislawdev/TestingFilesGenerator/internal/format/all"
 	"github.com/donislawdev/TestingFilesGenerator/internal/gui/text"
+	"github.com/donislawdev/TestingFilesGenerator/internal/recipe"
 )
 
 // The screen that says what this program is also says what to do with it.
@@ -63,3 +64,35 @@ func TestTheAboutScreenSaysHowToUseTheProgram(t *testing.T) {
 		t.Errorf("the About screen no longer says what this program is:\n%s", said)
 	}
 }
+
+// TestTheStepsNameEveryOutcomeTheManifestCanRecord.
+//
+// The third step tells somebody what they will find in the manifest, which
+// makes it a list copied out of a closed set - and a list copied by hand that
+// nothing compares with its source goes stale on green. The set is
+// recipe.Outcomes(), four values today, and the first version of that step
+// named two of them, invented a third word for one ("turn it away" for
+// reject) and left sanitize out altogether. Nothing in the tree would have
+// said so.
+//
+// Read from the REGISTRY rather than from a list here, so a fifth outcome is
+// caught by being declared. That is the whole reason this is a guard and not
+// a proofread.
+func TestTheStepsNameEveryOutcomeTheManifestCanRecord(t *testing.T) {
+	content, _ := laidOutWindow(t)
+	about := tabContent(t, content, text.TabAbout())
+	said := shownText(about)
+
+	outcomes := recipe.Outcomes()
+	if len(outcomes) < 2 {
+		t.Fatalf("the recipe package declares %d outcome(s), which is too few for this to compare anything", len(outcomes))
+	}
+	for _, outcome := range outcomes {
+		if !strings.Contains(said, outcome) {
+			t.Errorf("the manifest can record outcome %q and the About screen never uses that word, "+
+				"so somebody reading the steps meets it for the first time in the JSON.\nThe screen says:\n%s",
+				outcome, said)
+		}
+	}
+	t.Logf("%d outcome(s) named on the screen: %v", len(outcomes), outcomes)
+}

internal/guard/regressiontable_test.go

@@ -55,7 +55,6 @@ var notYetJustified = []string{
 	"exeproperties_test.go",
 	"foldedsections_test.go",
 
-	"guitext_test.go",
 	"keyboard_test.go",
 	"livecheck_test.go",
 	"openlist_test.go",

internal/guard/testdata/screens/about.png

@@ -90,8 +90,8 @@
 													<container size="777x29">
 														<widget size="777x29" type="*widget.Label">
 															<widget size="777x29" type="*widget.RichText">
-																<text color="placeholder" size="753x14" textSize="12">Point your test at the manifest. For every file it says what the system under test should do with it - accept it, turn it away, or leave the</text>
-																<text color="placeholder" pos="0,14" size="220x14" textSize="12">answer to the application's own policy.</text>
+																<text color="placeholder" size="751x14" textSize="12">Point your test at the manifest. For every file it says what the system under test should do with it - accept it, reject it or sanitize it - or</text>
+																<text color="placeholder" pos="0,14" size="570x14" textSize="12">records the outcome as unspecified, where the right answer belongs to the application's own policy.</text>
 															</widget>
 														</widget>
 													</container>

internal/guard/testdata/screens/about.xml

@@ -298,7 +298,7 @@
   },
   "HowToUseRead": {
     "description": "Shown in the window.",
-    "other": "Point your test at the manifest. For every file it says what the system under test should do with it - accept it, turn it away, or leave the answer to the application's own policy."
+    "other": "Point your test at the manifest. For every file it says what the system under test should do with it - accept it, reject it or sanitize it - or records the outcome as unspecified, where the right answer belongs to the application's own policy."
   },
   "ManifestNamed": {
     "description": "Shown in the window. Carries one value, {{.Name}}, which has to stay spelled exactly that way.",

internal/gui/text/locale/en.json

@@ -61,14 +61,23 @@ func SectionHowToUse() string { return say("SectionHowToUse", "How to use it") }
 // application's own policy (manifest rule MF5), and a person writing a test
 // against the file would otherwise meet that for the first time in the JSON.
 //
+// It names the outcomes with the SPELLING THE MANIFEST USES, and both halves
+// of that were wrong when this was written on 2026-09-23. It said "turn it
+// away" for an outcome the document calls reject, which is a second word for
+// a contract value somebody is about to read - and it left "sanitize" out
+// altogether, so the list promised three answers where the closed set has
+// four (internal/recipe: accept, reject, sanitize, unspecified). The first
+// half came from an outside review of #125, the second was found while
+// checking it. American spelling because that is the value, not a preference.
+//
 // A list of sentences rather than one paragraph per step: the window draws
 // these as the bullets the preset screen already uses for what a set
 // typically finds, so the three steps are read at a glance rather than read.
 func HowToUseSteps() []string {
 	return []string{
 		say("HowToUseChoose", "Choose a preset, or fill in one batch on the first screen."),
 		say("HowToUsePress", "Press Generate. The files and a manifest land in the output folder."),
-		say("HowToUseRead", "Point your test at the manifest. For every file it says what the system under test should do with it - accept it, turn it away, or leave the answer to the application's own policy."),
+		say("HowToUseRead", "Point your test at the manifest. For every file it says what the system under test should do with it - accept it, reject it or sanitize it - or records the outcome as unspecified, where the right answer belongs to the application's own policy."),
 	}
 }