Lunar Porter flies on a controller

A held thruster burns every tick it is held for, which is the whole reason
the pad exists: the console can only say a key went down, so a thruster
driven by it could be pumped and never leaned on.

The burn happens on the same tick gravity does, and for the same reason -
a sixteenth of a pixel is the smallest step this arithmetic takes, and
applied sixty times a second it is an enormous acceleration. On the tick,
thrust and gravity are two numbers whose RATIO is the whole feel of the
thing. Position still moves every frame; only the acceleration is stepped,
and nothing can see that.

Two against gravity's one, so climbing and falling are the same speed.
Three was the first try and it left the moon after about a second of
holding.

If there is a pad the console's arrows are ignored, because under a window
the same keypress reaches both - the pad as a level, the console as a byte
- and a thruster that fired twice for one press would be a mystery to
anybody tuning it. q still quits, since a pad has no letter for it. With
no pad the arrows still burn once a press, which is the most that can be
done down a wire.

And break.sh now rebuilds the disk images as well as the binaries. Half
the things worth breaking here are SplitBit assembly rather than C, and
those live on the fixture disks - so an edit to a .asm file changed
nothing the suite could see, and the tool reported that nothing caught the
break. That is the exact lie it was written to prevent, turning up in a
new place. With the disks rebuilt it catches this one: the lander falls
between the two captures instead of climbing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW

Tests/break.sh

@@ -44,7 +44,10 @@ FILE="$1"; ANCHOR="$2"; REPLACEMENT="$3"; shift 3
 # working tree that looks fine is worse than any failing test.
 KEEP="$(mktemp)"
 cp "$FILE" "$KEEP"
-restore() { cp "$KEEP" "$FILE"; rm -f "$KEEP"; (cd "$ROOT" && make >/dev/null 2>&1); }
+restore() {
+    cp "$KEEP" "$FILE"; rm -f "$KEEP"
+    (cd "$ROOT" && make >/dev/null 2>&1 && ./Tests/makedisks.sh Tests/build >/dev/null 2>&1)
+}
 trap restore EXIT INT TERM
 
 # ---- The edit, and proof it happened ----
@@ -63,6 +66,12 @@ open(path, "w").write(text.replace(anchor, replacement))
 PY
 
 # ---- The build, and proof of that too ----
+#
+# And the disk images after it, because half the things worth breaking are SplitBit assembly
+# rather than C, and those live on the fixture disks rather than in the binaries. Rebuilding
+# only the emulator meant an edit to a .asm file changed nothing the suite could see and the
+# tool reported that nothing caught the break - which is the exact lie it exists to prevent,
+# turning up in a new place.
 if ! (cd "$ROOT" && make) > "$KEEP.build" 2>&1; then
     printf '%sbreak.sh: the broken version does not build, so nothing was tested%s\n' \
         "$RED" "$RESET" >&2
@@ -72,6 +81,14 @@ if ! (cd "$ROOT" && make) > "$KEEP.build" 2>&1; then
 fi
 rm -f "$KEEP.build"
 
+if ! (cd "$ROOT" && ./Tests/makedisks.sh Tests/build) > "$KEEP.disks" 2>&1; then
+    printf '%sbreak.sh: the disks did not build, so nothing was tested%s\n' "$RED" "$RESET" >&2
+    tail -5 "$KEEP.disks" >&2
+    rm -f "$KEEP.disks"
+    exit 2
+fi
+rm -f "$KEEP.disks"
+
 # ---- And then the suites ----
 #
 # A suite that fails is the GOOD outcome here, so the exit status is inverted: this reports