Show1D scientific review lacks calibrated, responsive linked traces and snapshots

[bobleesj]

Problem

Show1D cannot yet reliably carry the scientific context needed for reconstruction review: multi-series time/defocus traces, calibrated labels and units, and linked image/snapshot panels are incomplete, while high-frequency hover work and repeated snapshot FFTs can make long traces or active playback sluggish. The current narrow/mobile layout and HTML-export contract also leave scientists without a clear, portable way to review large linked snapshot sets.

This blocks a dependable Show1D review surface for quantem.live C10/defocus and SSB time-series reports.

Proposed solution

Extend Show1D as one focused scientific-review workflow:

• preserve calibrated axis labels/units, explicit colormaps, and multiple visible series;
• link trace hover/selection to image, snapshot, profile, notes, and review panels;
• schedule hover work per animation frame and bound/reuse snapshot FFT cache work;
• keep controls and labels usable on narrow/mobile layouts;
• expose package-standard single-file HTML export with explicit linked-image downsampling;
• document the API, tutorial behavior, export limits, and network dependency;
• cover Python state/export behavior and frontend performance contracts with focused tests.

Expected user behavior

A scientist can open a multi-series time or defocus trace, inspect calibrated values without cursor lag, see the matching linked snapshots and profiles, preserve an explicitly selected colormap, use the review on a narrow screen, and export a kernel-free single HTML file with an explicit image downsample factor. Long trace hover and snapshot playback remain responsive, and quantem.live can use the widget as its linked review surface.

Acceptance checks

• Focused Show1D Python and frontend tests pass.
• TypeScript checking and the production frontend build pass.
• Exported HTML is browser-driven with long traces, linked snapshots, cache stress, and narrow responsive layout.
• Physical iPhone Safari, live Jupyter state handoff, and true network-offline behavior remain separately identified release gates rather than being inferred from Chromium emulation or unit tests.