You'll notice
Artifact publishing now auto-retries on a specific 'content_pending' server refusal, not just unrecognized errors
What
When publishing an artifact (a generated file or document Claude Code creates and sends to a server), the server can reject the request with an HTTP 422 error. The retry logic that double-checks and resends after such a rejection now specifically recognizes a content_pending error code from the server, using a new step that extracts the status code from the response. Previously it only had a generic fallback for 422 responses it didn't recognize.
Why
This makes automatic retries more reliable when the server reports the artifact's content simply isn't ready yet, rather than treating that case as just another unrecognized failure.