amyboard: clear AMY sequences on restart_sketch so factory reset stops old loops

restart_sketch only stopped the Python loop() callback; the AMY-side sequences
the old sketch registered (AMYSequence drum loops etc.) kept firing. Hardware
factory reset reboots the board so AMY starts fresh, but the web simulator's
"Reset to factory defaults" (and any on-device sketch restart) runs in place --
the old pattern kept playing over the new sketch.

Send RESET_SEQUENCER on restart (scoped to AMY sequences; not
sequencer.clear(), whose seq_remove_callbacks would also kill UI
TulipSequences like show_midi), and restart the AMYSequence tag counter so
repeated sketch saves don't creep toward AMY's max_sequencer_tags.

Verified in the web simulator: drum sketch loops, factory reset clears all
sequence tags (D1 dump shows highest_tag -1) and silences the loop, and a
sketch installed after reset registers tags starting from 0 again.

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

Author: bwhitman

tulip/shared/amyboard-py/amyboard.py

@@ -758,6 +758,17 @@ def stop_sketch():
 def restart_sketch():
     """Reload and restart sketch.py."""
     stop_sketch()
+    # Clear the AMY-side sequences the old sketch registered (AMYSequence drum
+    # loops etc.). Hardware factory reset reboots the board so AMY starts
+    # fresh, but sketch restarts on-device and everything in the web simulator
+    # happen in-place -- without this the old sketch's pattern keeps playing
+    # over the new one. Scoped to AMY sequences only (not sequencer.clear(),
+    # whose seq_remove_callbacks would also kill UI TulipSequences like
+    # show_midi). With all entries gone the sequence tag counter can restart
+    # from 0, so repeated sketch saves don't creep toward AMY's max tag.
+    amy.send(reset=amy.RESET_SEQUENCER)
+    if 'sequencer' in sys.modules:
+        sys.modules['sequencer'].AMYSequenceEvent.SEQUENCE_TAG = 0
     if 'sketch' in sys.modules:
         del sys.modules['sketch']
     run_sketch()