fix(simulator): show a banner, not a traceback, when the REPL is output-only

PyScript's input() raises on the main thread, so code.interact() dies on its
first prompt and Pyodide's REPL pane filled with a traceback -- the run looked
broken when in fact the install, the demo and the display had all succeeded.

Catch that one failure and print what is actually true: the script finished and
this runtime's REPL is output-only. Any other exception still reports normally
through _report().

Verified under Playwright: the Pyodide pane now ends with the 3.14.2 banner and
the notice, after PSDisplay initialises and the LVGL demo draws.

This is cosmetic only. Making the Pyodide REPL genuinely interactive still needs
one of the two parity options: make psdisplay worker-safe (it stores a Python
object on the canvas element, which cannot cross the worker boundary), or drive
an InteractiveConsole from xterm's onData the way sim.lvgl.io feeds characters
into MicroPython.

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

Author: bdbarnett

simulator/index.html

@@ -282,7 +282,21 @@
 
 import code
 
-code.interact(local=globals())
+try:
+    code.interact(local=globals())
+except Exception as exc:
+    # PyScript's input() raises on the main thread, so code.interact() dies on
+    # its first prompt and Pyodide's REPL pane would otherwise show a traceback
+    # instead of a banner. The runtime stays on the main thread on purpose:
+    # a worker would fix input(), but psdisplay stores a Python object on the
+    # canvas element, and a PyProxy cannot cross the worker boundary.
+    if "input()" in str(exc):
+        print()
+        print("--- Script finished. This runtime's REPL is output-only. ---")
+        print("Switch to MicroPython for an interactive prompt, or press RESET")
+        print("to run your edited code again.")
+    else:
+        _report(exc)
 </template>
 
     <!-- Toast Notification -->