Software delivery gets easier to improve once you make the timing visible.
One thing I’m starting to like in our dark factory workflow is recording delivery timing directly on the PR.

Not just token usage or the final diff, but how the work actually moved:
context gathering,
implementation,
verification,
external wait,
and total elapsed to green.

The point is not precision for the sake of it.

It is to make the delivery system more visible.

Once you can see where time is really going, you can start improving the workflow itself:
reduce unnecessary waiting,
tighten validation,
spot bottlenecks,
and understand whether a task was slowed by execution, verification, or process overhead.

The screenshot is a small example of that idea in practice.

PRs are starting to become more than code artifacts.
They are becoming workflow artifacts too.