Report
One record in the single-app post-run reporting history. Records are appended on every successful materialise (auto-render after a run, or user-initiated from the post-run reporting UI) and survive until the next Simulate click clears the list, the user removes them, or the host's bound (typically MAX_RECENT_REPORT_SAVES on its controller) evicts the oldest.
Substrate-level DTO so any single-app host (Swing today; web / CLI / headless tomorrow) reuses the same record shape. Files on disk are NOT removed when a record is dropped — that's the user's domain. The list is a session-level navigation aid, not the source of truth for what's been published.
Parameters
wall-clock time of the save
the file's name (no directory component)
absolute path to the file on disk
Origin.AUTO for auto-rendered files (post-run completion), Origin.MANUAL for user-initiated saves