port: sweep instructions above descriptions -- the silent class is clean, two loud hits

Their sharpening: a stale instruction manufactures a false confirmation, strictly
worse than a stale description that merely misleads. Applied to my instruction
surface, the documented invocations in tool and script headers.

All fifteen distinct flags across those examples are parsed, so nothing in my
headers can produce their failure mode by being inert. But 'parsed' is a proxy and
its gap is known -- --shots parses and does nothing on the --boot path -- so I ran
two documented examples end to end rather than trusting the grep, and both produce
a 1280x720 frame.

Two hits, both loud rather than silent: 11 references to tools/verify-capture and
tools/verify-screen, paths that do not exist since the tools are under tools/port/
(fixed in 4 files); and check-all claiming eleven tools where there are fourteen
(now states both so the sentence dates itself).

The distinction worth recording: mine fail loudly, theirs failed silently. A wrong
path announces itself; an inert environment variable returns a clean wrong result.
Both are stale instructions and only one manufactures evidence.

Honest limit: I tested the flag surface plus two examples end to end, not all
thirteen documented invocations -- the --boot ones take 156 s each. That is a
judgement about cost, not a claim of coverage.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF

tools/port/check-all

@@ -3,7 +3,9 @@
 #
 #   tools/port/check-all
 #
-# There are eleven tools under `tools/port/` and nothing ran them together, so
+# There are fourteen tools under `tools/port/` (eleven when this was written --
+# the count is stated because it dates the sentence) and nothing ran them
+# together, so
 # each had to be remembered individually. That is the ninth instance of this
 # port's recurring shape -- something correct, documented and unexercised -- one
 # level up: the checks themselves were the thing nobody was running.

tools/port/verify-capture

@@ -5,7 +5,7 @@
 #   tools/port/verify-capture               # every screen with a capture
 #
 # THIS IS THE CORRECTNESS CHECK. `verify-screen` is the consistency one, and its
-# own header has pointed at this file since P1 -- `tools/verify-capture` -- while
+# own header has pointed at this file since P1 -- `tools/port/verify-capture` -- while
 # this file did not exist. The port has had a harness comparing two renderers
 # that share its assumptions, and none comparing it to the game.
 #

tools/port/verify-screen

@@ -27,14 +27,14 @@
 # concluded the port had drifted away from the game -- r +0.7462 against the
 # reference's +0.8727. Posed as it SHIPS, the same block scores **+0.9994**.
 # The conclusion was an artefact of the pose, and it was written up as a finding.
-# Correctness questions go to `tools/verify-capture`, which poses as shipped.
+# Correctness questions go to `tools/port/verify-capture`, which poses as shipped.
 #
 # So: a DIFFERS row means "we moved apart, go find out which of us moved". It
 # does not mean the port is wrong. Where a capture and this tool disagree, the
-# capture wins. Use `tools/verify-capture` for the correctness question.
+# capture wins. Use `tools/port/verify-capture` for the correctness question.
 #
-#   tools/verify-screen                 # every screen in the manifest
-#   tools/verify-screen main_menu title # named screens
+#   tools/port/verify-screen                 # every screen in the manifest
+#   tools/port/verify-screen main_menu title # named screens
 #
 # Writes <screen>.godot.png, <screen>.ref.png and <screen>.diff.png into
 # $OUT (default: a directory under /tmp) and prints, per screen, the largest