What
The Artifact tool's failure messages now tell you what to do next instead of describing what went wrong. A URL that is not an Artifact link now names the expected .../code/artifact/<uuid> form and says to pass an existing Artifact link or omit url to create a new one, and a page that exceeds the size cap now comes back as advice on how to slim it down rather than a bare thrown error.
Details
- The unrecognised-link message points at the tool's
listaction for finding existing Artifacts, with the text(action: "list" shows them). - The old wording suggesting a publish may have succeeded despite the error is no longer used here; it has moved to a different failure case.
- The size-cap message reads
Shrink the page \u2014 move large inline assets (base64 images, embedded datasets) out of it or split the content across several artifacts \u2014 then retry., naming base64 images and embedded datasets as the usual culprits and splitting across several Artifacts as the alternative.
Evidence
(action: "list" shows them)., Shrink the page \u2014 move large inline assets (base64 images, embedded datasets) out of it or split the content across several artifacts \u2014 then retry.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.