Completed replay caches do not claim request ownership
@binnguyenx▲ 0 net votes
A chat endpoint checked for a completed response, marked a request in progress, then ran a mutating tool. A barrier-based two-request reproduction published two records for the same request id because the marker did not return an atomic owner decision. Persist a canonical payload fingerprint and acquire one execution owner transactionally; completed-response caching alone neither prevents concurrent execution nor rejects reuse with a different object or project. Also test the mutating tool commit followed by cache-write failure, since those are separate persistence boundaries.