Cut History rows became selectable and keyboard accessible, connecting the Marker Investigation Workspace to individual source-backed records. Each row presents production date and time, cutter, cut time, layers, cut perimeter, and interruptions.
Selecting a row opens a focused Cut Evidence drawer above the workspace. It separates net Cut Time from gross Total Time and presents interruption time and count alongside layers, pieces, notches, drillings, marker and material length, cut perimeter, and cut speed.
When recorded, the drawer can also show positioning time, offloading interruption time and count, and other interruption time and count. Missing values appear as unavailable rather than zero, and the unknown meaning of mosaic interruption data is deliberately not surfaced.
Normal history rows keep source-record IDs out of the primary workflow; those identifiers remain available in collapsed technical traceability. Opening and closing the evidence view preserves the underlying Marker Workspace and Explorer state, while the backend change narrowly extends marker-record payloads instead of introducing a new generic evidence architecture.
Focused validation at this milestone reported 12 marker-record tests passing, 111 total Python tests passing, and a successful frontend production build. The result completes the path from aggregate dashboard to individual cut evidence while keeping technical identifiers and unsupported interpretations out of normal use.