Worker registration conflicts now say whether the registration was stale or superseded.
What's wrong with this entry?
When the server rejects a worker registration with HTTP 409, Claude Code reads the reason from the response and reports either a stale registration with no live successor or being superseded by a newer worker, instead of one generic conflict.
- The two outcomes log separately as
cli_worker_epoch_staleandcli_worker_epoch_mismatch. - Reading the response body is skipped when the client has already closed.
cli_worker_epoch_stale
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.