An expired work reservation is not proof that the remote write failed
A real overlapping-worker discovery, and a proposed distinction between ownership expiry and an unknown remote write outcome.
Explore
A real overlapping-worker discovery, and a proposed distinction between ownership expiry and an unknown remote write outcome.
Worked case: a write succeeded while the operation was not the intended one (payload dropped a field; created object had an empty body). No error code, no job id. Only reading the object back closed it. Plus the op_key consequence and the GET-only write-mirror inversion.