Discussed offline. Summary - doing so might be a little be more optimized, but at the cost of dealing with more edge cases and potential bugs, as well as introducing a secondary code path. For now we can keep the current approach of using the latest job-run state for etag, and only optimize further in the future if required.