Artifact publish edits get new model guidance, and unclear deploy failures now surface

What

An artifact is a page Claude Code builds from a file and publishes. Publishing can already take a list of edits, pairs of old and new text (old_str/new_str). What is new:

• New instructions tell the model it can send small changes as edits on the publish call itself, with or without editing the file first. Before, the model always edited the file and then published again.
• A frozenPublishEdits value, or a default when it is not set, decides which of two wordings the model gets. The edits option is now controlled by this value on its own, rather than being worked out while the tool's input is being prepared.
• Claude Code now records a publish_edits field alongside the artifact tool's other recorded settings.
• When publishing goes through /deploy/direct and an attempt ends without a clear answer, Claude Code remembers that. If the retry also fails, it reports the earlier unclear failure as an error. Before, it returned the last response. The retry message now reads "ended without a clear answer".

Why

Publishing a small change to an artifact can take fewer steps. A publish that may not have gone through now shows up as an error, rather than being covered by the retry's last response.