VisualProbe runs against the real save file — probe input mutates the saved song nf-4v56 ← Beads

Twinned from https://github.com/cfsh/ninefold/issues/128 by tools/beads/import_github.py's reconcile pass.

Found while probing on #127: probe scripts drive real input, and Tonapse autosaves (issue #51), so a probe's ui_accept on a song cell edits the persisted song — an early probe run placed a "reply" pattern into lead bar-0 and it stuck across launches until a reset-to-demo.

For inspection probes that's survivable but dirty; for future pixel-diff baselines it's disqualifying (state drifts run to run).

Proposal: a "scratchSave": true probe-script flag (or make it the default) that redirects the Store/PersistenceDriver save path to a temp file for the probe process — real save untouched, every probe starts from the seeded demo. Needs a small seam in PersistenceDriver/Store for the save path.

Refs #120 (probe infra), #127 (where it was noticed).