Workflow 2.2.12 records when retained workflow-run details are removed by retention cleanup. The nullable WorkflowRun.details_pruned_at timestamp is set in the same transaction as detail deletion, including when applications use a configured run model and storage connection. A repeated cleanup preserves the original timestamp. Rejected or rolled-back cleanup leaves it unset.
The marker is a supported read contract for operator tools such as Waterline. Null does not prove that details remain present: old prunes and genuinely empty histories cannot be distinguished without an authoritative record, so this release does not infer or backfill timestamps. Terminal status and run identity remain intact. Applications with a custom workflow_runs table must add a nullable details_pruned_at timestamp with microsecond precision as described in the API stability guide.
This patch does not change the SDK wire protocol. Source qualification: full database and Laravel matrix, release identity PR. The published-package verification workflow runs from this exact tag.