When an artifact can't be made from a type in a cloud session, you're pointed at a skill or file instead.
What's wrong with this entry?
When creating an artifact from a type is not available in a cloud session, the refusal now points you at a local alternative ("a skill or a file is fine for that") instead of only saying nothing was created. Failures also report a category alongside the message.
- The failure payload carries
files_error(the message) plus an optionalfiles_error_kindnaming the class of failure. - A new preamble warns that published artifacts do not honour a
<base href>written by the author.
so nothing was created; do not retry here
Strings lifted out of the shipped bundle, so the claim above can be checked against them.