Visual signoff: drive Show2D/Show3D user-flow stories before closing

[bobleesj]

Problem

Several Show2D and Show3D user-facing workflows are being designed or implemented together. Unit tests and typechecks are necessary, but they are not enough for these widgets. A scientist must be able to drive the widget visually in JupyterLab or exported HTML and see the expected behavior with real interactions.

This issue tracks the visual signoff pass for the related user-flow issues:

• Show2D: saved microscope-stage view states from the widget UI #155
• Show2D: ratio-based display padding for drift-correction review #156
• Show3D: playback dynamics presets for time-series review #157

Proposed solution

Run a focused, browser-driven widget review that produces screenshots or an HTML report. Treat visual evidence as required for closing the related issues.

Expected user behavior

A user opens the widget, interacts normally, and sees the scientific view stay honest and stable:

• Show2D saved states restore the exact inspection state the user saved.
• Show2D padding changes the displayed canvas naturally without changing raw data.
• Show3D playback dynamics help a user inspect temporal structure without crowding the UI.

Agent visual verification checklist

• Use live JupyterLab for kernel-backed behaviors, not only static HTML.
• Use exported HTML where the issue explicitly includes collaborator/report review.
• Open the latest target in the in-app browser or Chrome and drive it as a user: clicks, sliders, toggles, save/load, delete, playback, scrub, loop, bounce, FFT, and resize.
• Capture screenshots after meaningful interactions.
• Attach a single consolidated HTML report when multiple widgets or screenshots are involved.
• Include Computer HTML and iPhone HTML links when the report is served for both local and phone review.
• Record browser console errors/warnings and widget debug counters where relevant.
• Report what was visually verified, what was only unit-tested, and what remains unverified.
• Do not close Show2D: saved microscope-stage view states from the widget UI #155, Show2D: ratio-based display padding for drift-correction review #156, or Show3D: playback dynamics presets for time-series review #157 only from green tests; close them only after this visual pass or an equivalent issue-specific visual report.

Suggested review scenes

1. Show2D single-image ROI state: ROI + FFT + padding + save/load state.
2. Show2D 3-panel drift gallery: all-panel padding and selected-panel padding.
3. Show3D time-series stack: linear, slow, bounce, focus range, and hold-key-frame playback paths.
4. Repeat with FFT visible and at least one hidden panel where applicable.

[bobleesj]

Partial visual signoff after pushing 8d39b01 to main:

• Opened the Show2D padding review report in the in-app browser at http://127.0.0.1:8795/index.html.
• Browser console warnings/errors: 0.
• Screenshot captured locally: /private/tmp/quantem-widget-push-visual-20260712/show2d-padding-report.png.

This is not full closure-level visual signoff. Still needed:

• Live Jupyter drive of Show2D More → Save State / Load / Update / Delete / Delete All.
• Live Jupyter drive of Show2D View → Padding with FFT and scale bar toggled.
• Show3D Playback Dynamics UI is not implemented yet; once it is, drive Linear/Slow/Bounce/Focus/Hold paths visually.