Persist breakpoints and add go-to-address to the debugger

[asterick]

Summary

Debugger follow-ups from the rewrite:

• Breakpoints persist across reloads via the existing preserve()/restore() localStorage path (alongside EEPROM/RTC)
• Found & fixed a chicken-and-egg flaw that persistence surfaced: halting at a breakpoint stops the CPU before the instruction executes, so on a fresh classification map the breakpoint's own byte never becomes code — and markers only rendered on code lines. The breakpoints that fire are exactly the ones that were invisible. Markers now render on any line whose byte range contains a breakpoint; double-click clears from any marked line, setting stays code-line-only per the spec
• Go-to-address in the toolbar (hex; 0x/h decorations accepted): jumping unfollows the PC and scrolls by exact offset (fixed-height rows; scrollToIndex estimates can land a row short)
• window.minimon exposes the system instance for console debugging

Verification

Headless, in-context reloads:

• Set breakpoint → reload → marker present (live: [3388] restored, ● rendered on the halted-at row even though it classifies as hex)
• Double-click a marked hex row clears it; code-row toggling unchanged
• goto 0000 → unfollows, scrollTop 0, first row 0000; goto 0x2100 lands the target in view while running
• npm run check + vite build clean

🤖 Generated with Claude Code