Problem
When a step fails mid-render, you get the single failure-<step>.png (great), but no contact sheet — the post phase never runs, so --contact-sheet produces nothing for that render.
In the 0.9.0 session, run-an-event failed at step 12/13 (add-organizer). The single failure screenshot showed that step, but to understand how the run got there I wanted the labeled per-step thumbnails — which only exist on a successful render.
Why it matters
The failing run is exactly when you most want the at-a-glance "what did each step actually frame" view that the contact sheet (#9) provides. The settled end-of-step screenshots are already being captured during recording; on failure they're just discarded.
Suggested direction
On a step failure (when --contact-sheet / contactSheet is on), emit a partial contact sheet of the steps that completed, plus the failure frame as the last cell. Cheap, and it pairs naturally with the existing failure diagnostics (#6).
Follow-up to #9.
Problem
When a step fails mid-render, you get the single
failure-<step>.png(great), but no contact sheet — the post phase never runs, so--contact-sheetproduces nothing for that render.In the 0.9.0 session,
run-an-eventfailed at step 12/13 (add-organizer). The single failure screenshot showed that step, but to understand how the run got there I wanted the labeled per-step thumbnails — which only exist on a successful render.Why it matters
The failing run is exactly when you most want the at-a-glance "what did each step actually frame" view that the contact sheet (#9) provides. The settled end-of-step screenshots are already being captured during recording; on failure they're just discarded.
Suggested direction
On a step failure (when
--contact-sheet/contactSheetis on), emit a partial contact sheet of the steps that completed, plus the failure frame as the last cell. Cheap, and it pairs naturally with the existing failure diagnostics (#6).Follow-up to #9.