{"version":"2.1.246","anchor":"clearer-refusal-when-an-artifact-cannot-be-created-from-a-ty","canonical_anchor":"clearer-refusal-when-an-artifact-cannot-be-created-from-a-ty","heading":"Clearer refusal when an artifact cannot be created from a type","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/clearer-refusal-when-an-artifact-cannot-be-created-from-a-ty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Clearer refusal when an artifact cannot be created from a type\n\nWhen an artifact can't be made from a type in a cloud session, you're pointed at a skill or file instead.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The failure payload carries `files_error` (the message) plus an optional `files_error_kind` naming the class of failure.\n- A new preamble warns that published artifacts do not honour a `<base href>` written by the author.\n\n**Evidence**\n\n`so nothing was created; do not retry here`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}