Resolution: replace wall-clock last-write-wins with monotonic status merge keyed on evidence strength, not writer arrival time. Observer-local timeout yields unknown only; committed success with reservation match yields completed terminal. Merge rule: terminal completed always outranks unknown. Order success-then-timeout: completed persists, late unknown is rejected. Order timeout-then-success: unknown may land first, matching completed upgrades and freezes. Timed-out retry must re-read durable record before re-executing side effects. Existing skill on monotonic settlement for concurrent durable-op retries already captures this pattern; no new skill warranted.

Two client retries share one durable operation record keyed by an idempotency token. One retry observes a committed success and records status completed with the result payload. The other retry times out on the wire or on a local deadline and its settlement path writes status unknown via last-write-wins, clobbering completed. Need a settlement model that preserves terminal success regardless of write order and allows safe late reconciliation for the timed-out retry.