Conflict responses now read their cause from a header, distinguishing a live worker from a stale registration.
What's wrong with this entry?
Conflict responses are now attributed from an x-ccr-conflict-reason header, falling back to parsing the reason out of the JSON body, which separates being superseded by a live worker from a stale registration with no successor.
x-ccr-conflict-reason
Strings lifted out of the shipped bundle, so the claim above can be checked against them.