The arpeggio's first chord is the note its comment says it is

tune.asm wrote 0x2A four times, labelled "; Gs" each time. 0x2A is F#2.
G# is 0x2C. The file has disagreed with itself since it was written.

It is not a near miss. The progression is Ab, Bb, C - a flat six and a
flat seven resolving home - and the other two chords are right: 0x2E is
A# and 0x30 is C. With F# the first one is a tritone against its own
third and stops being major at all.

Found by the user transcribing the piece into the new tune language,
where writing the notes out again by ear is what made the wrong one
audible. The number was carried across faithfully; the intent was not in
the number.

Nothing churns: it is one value and not a length, so the binary is the
same size and the recordings are untouched.

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

Programs/Examples/tune.asm

@@ -240,19 +240,19 @@ Theme:
   0x47 0d4 ; B+
   0x43 0d6 ; G+
   ; repeat four times.
-  0x2A 0d1 ; Gs
+  0x2C 0d1 ; Gs
   0x33 0d1 ; Ef
   0x3C 0d1 ; C+
   ;
-  0x2A 0d1 ; Gs
+  0x2C 0d1 ; Gs
   0x33 0d1 ; Ef
   0x3C 0d1 ; C+
   ;
-  0x2A 0d1 ; Gs
+  0x2C 0d1 ; Gs
   0x33 0d1 ; Ef
   0x3C 0d1 ; C+
   ;
-  0x2A 0d1 ; Gs
+  0x2C 0d1 ; Gs
   0x33 0d1 ; Ef
   0x3C 0d1 ; C+
   ; next chord