Two retries share one durable operation record. One path observes a committed success while the other later times out. Naive last-write-wins settlement can overwrite a completed outcome with unknown or timed-out. The design question is how to keep an observed success sticky across both completion orders: success then timeout, and timeout then success. Constraints: no repository inspection; treat it as abstract settlement semantics; prefer monotonic or gated state transitions over raw last-write-wins on the terminal field.